001

01

Y

Y

DATA AREA OPENED IS FOR WRONG DATABASE OR AREA.

The data area opened was built for
a different database or area.

This is a probable JCL error. Review the JCL provided and, if in error, correct it.

In z/OS, dynamic allocation may have been used, and, if so, review the dynamic allocation messages to find the data set name. If dynamic allocation is in error, the data set names can be changed through the CXXMAINT DBUTLTY function.

If all is correct, then the data has been destroyed. Review how this happened and correct the problem. The desired data must be rebuilt from a backup of some type.

002

02

Y

Y

THE DATA AREA OPENED IS CONNECTED TO A DIFFERENT
CXX THAN IS BEING USED.

The data area opened is linked to a Directory (CXX) that is not the same as the Directory being used.

This is a probable JCL error. Verify through the JCL or in z/OS dynamic allocation messages the data set name. Verify that a test area is not linked to a production CXX or the reverse. The names of the CXX being used and the CXX which is linked to the area are provided in the error message. If it is a linkage problem (as in a CXX name change), use the DBUTLTY LINK function to change the link to the correct CXX.

Otherwise, ascertain how the data was destroyed to prevent it from reoccurring. If the data does not exist elsewhere, it has to be rebuilt with a backup.

003

03

Y

Y

INVALID COMPATIBILITY LEVEL

The data area being opened has an invalid compatibility level. As new features are added to CA Datacom/DB, they may require changes to the data area control
block which are incompatible with prior releases. If this is done, a
new compatibility level is set in the data area control block. This message is received when the code you are running does not support
the compatibility level set in the
data area control block.

Ensure that your JCL points to a valid data area. Check to see if you have used new features and are now running with a prior version of the code. If so, check to see if this is allowed, and if it is allowed, ensure that all fallback solutions are in place.

004

04

Y

Y

POSSIBLE JCL ERROR

An error was received while
reading a data area control block.
The problem could have occurred
because of a JCL condition such
as pointing to a wrong data set,
that is to say, the problem is not
with the data set itself but with the JCL.

Ensure that your JCL is correct, for example that it is pointing to the correct data set.

082

52

Y

Y

INVALID DATA AREA CONTROL BLOCK

If this return code is generated
during an attempt to load a data
area, it implies that the area has
not been initialized.

If this code is generated during initialization of a data area, it
implies an error in block size specifications. The minimum block
size for an area is 512 or the space required to hold the largest record, whichever is larger. The maximum block size is the track size or
32,760, whichever is smaller.
Block size is specified as the value
of the BLOCK-SIZE attribute-value when adding the area entity-occurrence to CA Datacom Datadictionary.

If the code was returned during a load, execute the DBUTLTY INIT AREA=aaa function before executing the LOAD AREA=aaa function. Consult the CA Datacom/DB DBUTLTY Reference Guide for more information.

If the code was returned during an initialization, revise the block size specification for the area, then reexecute the INIT AREA=aaa function. Consult the CA Datacom/DB Database and System Administration Guide section on defining a database to CA Datacom Datadictionary for information on revising the BLOCK-SIZE attribute-value.