001

01

Y

N

An unexpected condition has occurred during CXX processing.

Contact CA Support with the recommended dumps.

002

02

Y

N

A key is being subject to addition, alter, deletion, or swap in violation of a requirement.

During the addition of a new key, reasons include:

• The presented key name is already known to the CXX.
• The presented key name is a native sequence key.
• The presented key name is a master key.
• The presented key name is in a table that is not currently set as loaded.
• The presented key name is in a table that is not currently set as index loaded.
• The presented key is to reside in an index area that is not IXX. However, the index area is not defined for another key or the index area is not in the PREINIT list.

During the alter of a key, reasons include:

• The presented key name is not known to the CXX.
• The presented key name is the native sequence key in the CXX.
• The presented key name is the master key in the CXX.
• Currently, the presented key name is in an 'adding' status in the CXX.
• Currently, the presented key name is in a 'deleting' status in the CXX.

During the deletion of a key, reasons include:

• The presented key name is not known to the CXX.
• The presented key name is the native sequence key in the CXX.
• The presented key name is the master key in the CXX.
• Currently, the presented key name is in a 'deleting'status in the CXX.
• Currently, the presented key name is in a 'key swap' condition in the CXX where the base has not been closed and opened.

During the swap of a key, reasons include:

• The presented key names are not both known to the CXX.
• The presented key names are not both currently in an index loaded status.
• The presented key names are not both defined as not being a relative key.
• The <DD> swap level is not a valid number. (This should not occur).

Do not attempt to request an action not supported.

021

15

Y

N

RECORD WILL NOT FIT IN A BLOCK

Review the definition and correct the fields in the record to be smaller or increase the block size.

027

1B

Y

N

FILE ID IS DUPLICATED IN BASE

Select a different ID for one of the duplicated tables.

031

1F

Y

N

NOT ENOUGH CORE

Allow DBUTLTY or MUF to have additional memory.

033

21

Y

N

TEST VERSION OF DDPROD OVER PROD

This edits protects from errors. Review what is required.

037

25

Y

N

A COMPRESSED TABLE IS BEING ADDED TO A REPLICA DATABASE

Review the definition to not violate the rule.

038

26

Y

N

CREATE TABLE WITH DUPLICATE NAME

Review the definition and correct to not violate the rule.

039

27

Y

N

NULL FIELD IN MASTER KEY OR UNIQUE KEY

Review the definition and correct to not violate the rule.

040

28

Y

N

THE DBRW EXTENSION IS TOO SMALL TO PASS THE REQUESTED INFORMATION BACK TO DD

Contact CA Support with the recommended dumps.

041

29

Y

N

The BASE/AREA being updated using the CA Datacom Datadictionary batch 1000 transaction contained identification information that does not match the Directory (CXX). The information that does not match the CXX is one or more of the following items:

• DATACOM ID (DBID)
• ENTITY OCCURRENCE NAME
• STATUS
• VERSION
• SQL NAME

If you are modifying a data area, the DATACOM NAME (area name) must also match.

Respond as needed to make the information match the CXX.

042

2A

Y

N

The BASE/AREA being updated using the CA Datacom Datadictionary batch 1000 transaction violated a rule, not including matching identification with the CXX. The error is a violation of one of the following restrictions:

• For a database, CA Datacom STAR replication is being changed.
• For a database, CA Datacom STAR partitioning is being changed.
• For a database, SQL security is being changed.
• Currently, the database is less than FORMAT 2.
• The data area being altered is not in URI format.

Respond as needed to avoid violating the restriction.