DBUTLTY LOAD fails with DB13012E - INSUFFICIENT SPACE IN AREA. Why did the LOAD not perform a dynamic extend?

Products

• Datacom
• DATACOM - AD
• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• CA ECOMETER SERVER COMPONENT FOC
• Easytrieve Report Generator for Common Services
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA ON DEMAND PORTAL
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware

Issue/Introduction

Question: 

DBUTLTY LOAD fails with DB13012E - INSUFFICIENT SPACE IN AREA. The area is defined with DYNAMIC-EXTEND YES. Why did the LOAD not perform a dynamic extend on the area?

 

Answer: 

There are some restrictions on when dynamic extend will be attempted for a LOAD.

This is documented in https://Docops.ca.com in section DBUTLTY Dynamic Extend Considerations

• For the RETIX and LOAD functions, the SORT= keyword must be specified, and with a value other than zero. Only the code path using a SORT= contains the option to dynamic extend. There is no message generated if this requirement is not met.
  
  
• Every table in the database must have been defined with the CA Datacom® Datadictionary™ attribute RECOVERY YES. There is no message generated if this requirement is not met.
  
  
• For the RETIX and RECOVERY functions, the area must have been loaded with YES specified for the URI option. For the LOAD function, YES must have been specified for the URI option or allowed to default to YES for URI. There is no message generated if this requirement is not met.

Most likely these conditions are not met so the extend was not performed.

Environment

Release: DATABB00200-14-Datacom/AD
Component: