001

01

N

N

OPEN ERROR

You attempted to open a Memory Resident Data Facility area for VIRTUAL usage, but the open was unsuccessful because a GETMAIN for storage for control blocks failed.

Note: If you are using 64-bit memory, refer to the Action for the two available options.

Provide a larger memory allocation and re-attempt system startup.

If you are running in a z/OS environment and using 64-bit memory, you can do one of the following:

• Specify YES for the FORCE_NO_64BIT MUF startup option to force data space usage instead of 64-bit usage. This option takes effect only when done as part of a Multi-User Facility enable. Requesting the option later using the console command is allowed but ignored. For more information about FORCE_NO_64BIT and support for z/OS 64-bit, see the CA Datacom/DB Database and System Administration Guide.
• Alternately, you can add MEMLIMIT=nG to your job card, where you replace the n with a value large enough to hold all covered and virtual startup options.

002

02

N

N

OPEN ERROR

While opening a data set, a security validation resulted in a failure of the authorization request.

Consult your Security Administrator.

005

05

Y

N

OPEN ERROR

An error occurred during CA CIS
label processing for dynamic extend for z/VSE.

Check for error messages on the console. Contact CA Support. For information about contacting CA Support, see Troubleshooting.

006

06

Y

N

OPEN ERROR

A data set exceeded the maximum number of extents during dynamic extend for VSE.

Reduce the number of extents by combining multiple extents and reinitializing and loading the area.

007

07

Y

N

OPEN ERROR

An invalid data set name was encountered during dynamic extend for z/VSE.

Ensure that the data set name is not greater than 41 characters. CA Datacom requires 3 characters for the CA Dynam/D for z/VSE catalog option.

009

09

Y

Y

OPEN ERROR, INSUFFICIENT TRACKS OPENED

An Index Area (IXX) or data area that has been initialized with or without extends has been opened, but not all tracks are present. The first block of a data set has information about the number of tracks formatted and accepted as useable within the data set. An open has been done and the operating system has not presented to CA Datacom/DB the full number of tracks that previously existed.

This is a JCL or catalog problem and must be corrected. All tracks expected do or can have data that is now missing.

010

0A

N

N

PREVIOUS OPEN ERROR REQUIRES CLOSE BEFORE NEW OPEN ATTEMPT

After some of the open error conditions, it is required that a close occur to ensure full cleanup of conditions.

Correct the condition of the open error, issue a console or DBUTLTY COMM CLOSE for the base in question, then open the base again.

012

0C

N

N

UNAVAILABLE DATA SET

A data set needed for the current process, either MUF or DBUTLTY, is not available.

Wait for the conflicting action to complete before attempting the current process. Example: If a DBUTLTY function LOAD is loading a data area, it must protect that data set. If another DBUTLTY function such as a RETIX attempts to have access, then it is blocked because it is not reasonable to RETIX a data area while it is being loaded. You can also get an error if a MUF attempts to open the

data set being loaded.

013

0D

N

N

CONFLICT DBDSNPR DSN

A conflict exists between a data set
name being opened as the CXX, Lxx, or fxx and the values
set in the DBSIDPR module in use as
generated by the DBSYSID Macro to
define the environment. The error is
preceded by a message, currently
either DB01409E or DB01410E.

Review the action for the message
mentioned.

014

0E

N

N

CONFLICT DD DSN VS DSN FROM CXX

The CXX knows that an index or data
area has been initialized and has a
specific name. You are attempting to
provide JCL for that index or data area
that is in conflict. This error does not
occur on an INIT function which accepts
a provided DD statement as an
override. This error does not occur on
a temporary data set used for throw
away testing.

Review the JCL being used versus the
CXX report of the database in question.

083

53

Y

N

OPEN ERROR

You attempted to open an Index
Area or a data area, but the open
of the data set was unsuccessful
because either the required DD statement was not found or no
data set name had been saved
in the Directory.

To bypass or override dynamic allocation, add DD statement to JCL. To activate dynamic allocation (z/OS only), catalog z/OS data sets and follow the dynamic data area/Index Area allocation procedure in the CA Datacom/DB Database and System Administration Guide.

If the return code is reissued after corrective measures have been taken, obtain a Statistics and Diagnostics Area (PXX) report and contact CA Support For information about contacting CA Support, see Troubleshooting.