LOAD (Build CXX or Data Area) › LOAD CXX (Build CXX) › How to Use

How to Use

MUF execution ensures that the MUF is always in control and has knowledge of all information in the CXX (a normal case being a single MUF or MUFplex) to a CXX.

Execute the LOAD function using the following command format:

►►─ LOAD AREA=CXX,DDNAME=d ─┬────────────────────────────┬────────────────────►◄
                            └─ ,DBID=n ─┬──────────────┬─┘
                                        └─ ,NEWDBID=n ─┘

Command

LOAD

Invokes the function to build or restore an area.

Required Keywords

AREA=CXX

Identifies the area to be loaded as the Directory. If the DBID parameter is not specified, the entire Directory is loaded.

,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:

  Any name valid to JCL specifications

  Default Value:

  (No default)

Optional Keywords

,DBID=

Identifies the database selected for loading a specific database to the Directory.

Valid Entries:

DATACOM-ID of the database

Default Value:

(No default)

,NEWDBID=

Specifies a new DBID for the data to be loaded.

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:

Valid DATACOM-ID for a database

Default Value:

(No default)