Version 14.0 › CA Datacom Tools Products › New Features and Enhancements › Datadictionary Features › Datadictionary Report Comparing DATA-DICT › DDSDCLM Processing

DDSDCLM Processing

The DDSDCLM performs two functions:

• Reads the DATA-DICT DATABASE Structure in PROD status at your site. The DDSDCLM compares selected information regarding the structure to the information provided in the module created and delivered by CA Technologies that reflects the minimum expected structure.
• Reads all PRODuction and TEST occurrences of certain entity-types and edits them from compliance with current requirements.

The processing performed by DDSDCLM is as follows:

1. Reads the SYSIN input file and processes the following records:
   1. The first record in the SYSIN file must be a standard USR transaction unless the CA Datacom Datadictionary System Resource Table (DDSYSTBL) indicates that the external security system User ID is used. This transaction is processed as described for all other CA Datacom Datadictionary batch utilities. The user-specified in the USR transaction must have DDADMIN authority or processing does not proceed.
   2. The records described in this section are optional. The records are SET transactions as documented in the CA Datacom/DB System and Database Administration Guide. One additional SET transaction is accepted for this utility which is formatted as follows:
      • Bytes 1-4 contain -SET.
      • Byte 5 is blank.
      • Bytes 6-9 contain Warning Messages OFF (WMOF) specifies that messages indicating differences in the structures that are not incompatible with a valid structure but are not part of the standard installation will not be printed. These are messages that indicate such things as additional tables in the database, additional keys or elements not in the standard structure, and additional columns not in the standard structure. All of these could indicate that you have implemented user-defined extensions. The default is to print these messages.
   3. The final record must be a DDSDCLM transaction that is formatted as follows:

      Comparator Transaction

      -SDC vvv,stat
      

      • Bytes 1-4 contain –SDC
      • Byte 5 is blank
      • Bytes 6-8 contain the version identifier of the DATA-DICT structure being processed (for example, 140, 120, 121)
      • Byte 9 is, optionally, a comma
      • Bytes 10-13 are, optionally, the Status of the DATA-DICT Database Structure to be processed (for example, PROD, T001, and so forth). If not provided, the default status is PROD. History versions are not allowed.

        Verifier Transaction

        -SDC VERIFY
        

      • Bytes 1-4 contain -SDC
      • Byte 5 is blank
      • Bytes 6-11 contain VERIFY
2. For the Comparator Transaction, the following processing is performed:
   1. Loads the Basis module corresponding to the version identifier specified in the DDSDCLM transaction. For example, if the DDSDCLM transaction contained 140, then DDSDCLM attempts to load module DD140SD. If the load fails, an error message is printed describing the problem. For more information, see DDSDC messages in the CA Datacom/DB Message Reference Guide.
   2. Reads the DATA-DICT database structure in PRODuction status in the MUF accessed based on the DBSIDPR module used. DDSDCLM reads through the entire DATA-DICT structure and reports on differences between your DATA-DICT structure and the expected structure as defined by the Basis module.
3. For the Verifier Transaction, the following processing is performed:
   1. Reads all occurrences of the following entity-types:
      • AREA
      • DATABASE
      • CONSTRAINT
      • ELEMENT
      • FILE
      • FIELD
      • KEY
      • PARTITION-COLUMN-VALUE
      • SYNONYM
      • TABLE
      • VIEW
   2. Verifies that each occurrence passes the edit requirements for the current release of CA Datacom Datadictionary.