042

2A

Y

N

EXTEND FAILED

In z/OS, a SB37, SD37, or SE37
abend condition was detected
during EXTEND processing.

This error automatically generates
a Master List dump.

See the appropriate IBM documentation to determine the nature of the B37, D37, or E37 abend condition, and correct the problem according to the IBM directions.

043

2B

Y

N

DYNAMIC EXTEND NOT
ALLOWED

In MVS, dynamic extend was
invoked but the area data set had
no secondary allocation defined.

In VSE, dynamic extend was
invoked, but DYNAM/D was not available in the Multi-User Facility partition.

This error automatically generates
a Master List dump.

The area data set has to be extended using the DBUTLTY EXTEND function. To allow future dynamic extension:

MVS

Ensure that secondary allocation is specified for the data set.

VSE

Ensure that the DBDYAPR phase has been link edited and is available to the Multi-User Facility partition.

044

2C

N

N

The open/close subtask abended
for a z/OS Sx37 abend other than SB37, SD37, or SE37. The area
failed to open, but CA Datacom/DB successfully recovered from the
abend and opens continue to
operate. A 2-byte z/OS system
abend code can be found in bytes
26 and 27 of the Request Area.
The reason code associated with
the abend is saved in bytes 28
through 31 of the Request Area.

See the appropriate IBM documentation to determine the nature of the abend. Correct the problem according to the IBM directions.

065

41

Y

N

DD STATEMENT MISSING

In z/OS, a DD statement is missing.
In VSE, the DLBL/EXTENT
statements are missing.

Alternately, CA Datacom/DB could
not locate the data set name in the Directory. Cataloging a database preserves the data set names for all areas in the database structure with
at least one loaded table. An area added to the database after it is cataloged, or any area without
loaded tables, therefore has no
data set name.

Identify the missing statements and add them to the job stream. Use a CXX Report to verify that all expected areas are listed under the correct database and have data set names. Then rerun the failing job.