Processing, DBUTLTY and SQL Messages › DBUTLTY Messages (DB1xxxxc) › DB10059E

DB10059E

DDNAME RESERVED FOR DATACOM AREA

Reason:

The name you have specified for DDNAME= is not acceptable. Your DDNAME= choice is a name reserved for a CA Datacom area and therefore not acceptable as a name for sequential input or output files. Names with the following patterns are not acceptable for DDNAME=:

• 3-byte names that end with XX, meaning they are reserved as either current or future CA Datacom control areas.
• 6-byte names that end with what could be a database ID from 001 through 999.
• 7-byte names that end with what could be a database ID from 1000 through 9999.

The DDNAME= value is verified for acceptability to protect you from unintentionally causing data corruption. The DDNAME check is the default but optional. You can prevent the DDNAME check by using a DBSIDPR parameter (DBUTLTY_EDIT_DDNAME=) for individual MUF environments. However, we recommend that you allow the DDNAME check.

Note: The data corruption risk involves not the DDNAME itself but the content of the data set. For example, suppose that you used the CXX DDNAME as the output of a backup. You then copied the CXX DD statement and changed the DDNAME of the copy to be acceptable, avoiding the DDNAME= error. The backup would, however, then overlay the CXX data set, which is not the intent of a backup.

Action:

Verify what the execution is trying to accomplish. If possible, change your DDNAME= specification to an acceptable value.

Note: We recommend that you allow DDNAME= check protection. You can, however, disable DDNAME= protection. To disable protection, assemble the DBSIDPR module used for this CA Datacom environment and specify NONE for the DBUTLTY_EDIT_DDNAME= parameter. The default is DBUTLTY_EDIT_DDNAME=FULL_1, which allows DDNAME= protection. For more information about DBSIDPR and DBUTLTY_EDIT_DDNAME=, see the CA Datacom/DB Database and System Administration Guide.