CA Datacom Datadictionary Numbered Messages › SDC Message Identifier Format › DDSDCT004A

DDSDCT004A

TABLE xxxx… MAX-RECORD-SIZE IS NOT ZERO

Reason:

The MAX-RECORD-SIZE attribute value of the local TABLE occurrence (xxxx…) is not zero. CA makes an effort to assure that all TABLE occurrences representing entity-types have zero in this attribute as it creates a problem if an upgrade from one version to another requires that the table needs expanding.

Action:

The fact that the MAX-RECORD-SIZE attribute value is zero is a potential problem only if the table needs expanding when upgrading from one version to another. To avoid these problems when upgrading, it would be best to assure that all of the MAX-RECORD-SIZE attributes be set to zero before going into an upgrade.

Rerun the Comparator to complete and confirm any other corrections to the entity-type table that the Comparator indicated before continuing.

Next, compare the LENGTH attribute value of the TABLE occurrence to the first value of the Length field of the CXX Report. If they are equal then the MAX-RECORD-SIZE can simply be set to zero (see below for how to do this) and no other action is required. If these two values are different, there are one or more checks to be made.

If there are no other Comparator messages for this TABLE and the LENGTH attribute value is greater than the Length in the CXX Report, contact CA Support as there should be further investigation to determine what is causing the discrepancy.

It has now been established that the LENGTH attribute value for the TABLE occurrence is less than the Length in the CXX. It is irrelevant what the MAX-RECORD-SIZE attribute value is so it can be set to zero as follows:

Using DDUPDATE in batch execute the following transactions:

-UPD TABLE,xxxx…(ssss,pswd,ovrd)

3151 00000

-END

Where "xxxx…" is the TABLE occurrence name, "ssss" is the Status, "pswd" is the Password and "ovrd" is the site override code.

If the DATA-DICT Structure is not already in PROD Status, use the –CPY batch header to copy it to PROD as described in the CA Datacom/DB Datadictionary Batch User Guide.

Perform the following steps to implement the correct length as established by the LENGTH attribute value (these steps assume the DBID of the DATA-DICT database is 2):

1. Execute the DDCFBLD utility using the following SYSIN cards:

   -USR uuuu…,pswd

   -CXX BUILD,DATABASE,DATA-DICT(ssss,pswd,ovrd)

   See the CA Datacom/DB Datadictionary Batch User Guide for the values of the placeholders.

   Note: The BUILD file from this step is used as input to Step 3.

2. Execute DBUTLTY with the following transactions to back up the DD1 area:

   For z/OS:

   BACKUP AREA=DD1,DBID=002,DDNAME=aaaaaaa,SEQ=ssssss

   For z/VSE:

   BACKUP AREA=DD1,DBID=002,DTFNAME=aaaaaaa,DEVICE=dddd,SEQ=ssssss

   See the CA Datacom/DB Utilities Guide for the values of the placeholders.

3. Execute the DBUTLTY CXXMAINT function using the following SYSIN transactions and the BUILD sequential file from Step 1above.

   COMM OPTION=CLOSE,DBID=002

   XXMAINT OPTION=DDPROD,DDNAME=aaaaaaaa

   See the CA Datacom/DB Utilities Guide for the values of the placeholders.

4. Execute DBUTLTY with the following transactions to initialize the DD1 area and IXX002.

   INIT AREA=DD1,DBID=002

   INIT AREA=IXX,DBID=002

5. Execute DBUTLTY with the following transaction and the backup file from Step 2.

   LOAD AREA=DD1,DBID=002,FORMAT=BACKUP,DDNAME=aaaa…,MISMATCH=IGNORE

   See the CA Datacom/DB Utilities Guide for the value of the placeholder.

6. Rerun Step 2 to get a current backup and include the following transaction to backup the CXX.

   BACKUP AREA=CXX,DDNAME=xxxx…

   See the CA Datacom/DB Utilities Guide for the value of the placeholder.