CXXMAINT (Maintain Directory) › CXXMAINT DDPROD (Update Directory) › How to Use

How to Use

The MUF must be active when you execute this command. Execute DBUTLTY with the command:

►►─ CXXMAINT OPTION=DDPROD,DDNAME=d ─┬──────────────┬─────────────────────────►◄
                                     └─ ,NEWDBID=n ─┘

Command

CXXMAINT

Invokes the function for Directory maintenance.

Required Keywords

OPTION=DDPROD

Requests the option to update the CXX from CA Datacom Datadictionary definitions.

,DDNAME=

Specifies the JCL DDname for the input data set.

A DDNAME is not acceptable for sequential input or output files if it is a name reserved for a CA Datacom area. Names with the following patterns are therefore 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_DATA_SET=) for individual MUF environments. However, we recommend that you allow the DDNAME check.

  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.

  If you specify an unacceptable name for DDNAME=, message DB10059E is generated. For more information about DB10059, see the CA Datacom/DB Message Reference Guide.

  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_DATA_SET= parameter. The default is DBUTLTY_EDIT_DATA_SET=FULL_1, which allows DDNAME= protection. For more information about DBSIDPR and DBUTLTY_EDIT_DATA_SET=, see the CA Datacom/DB Database and System Administrator Guide.

  Valid Entries:

  The name required to access the data set created by the DDCFBLD utility

  Default Value:

  (No default)

Optional Keyword

,NEWDBID=

Specifies a different database ID to be assigned to the definition. Use this keyword to create a set of new definitions quickly that are identical to a production base. Do not use this keyword when performing a normal update.

Note: Do not use this parameter for databases accessed by SQL or CA Dataquery. These products must have the correct DBID to reference additional information from CA Datacom Datadictionary about the production database. If the NEWDBID= parameter is used for a database accessed by CA Ideal, the corresponding ASSIGN DBID or ALTER DBID command must be run before running the application. See CA Ideal documentation for details.

Valid Entries:

DATACOM-ID of the database

Default Value:

When this keyword is not coded, the database is updated as indicated from the input.