DataManager Batch Processing and Reporting › The Archive/Restore Program (CAKSARCH) › The COMMIT Option

The COMMIT Option

DataManager definitions are modified by editing the DEVELOPMENT version of definition records using the DataManager online facility. Definitions in the DEVELOPMENT version are not available for processing until they are committed or frozen.

The commit process:

• Freezes all definitions in the DEVELOPMENT version of DataManager's tables
• Deletes any existing committed definitions from DataManager tables
• Changes the version of DEVELOPMENT definitions. IRD definitions change to the REAL version while ORD definitions change to TEST or PROD (depending on the version specified in the COMMIT control statement)

To commit DEVELOPMENT definitions, execute the Archive/Restore program (CAKSARCH) using the COMMIT control statement described below. The JCL to execute the COMMIT control statement is contained in the CAI.SAMPJCL member called CAKSCOMT.

An optional CA Earl definition file (CAIKSERL) can be generated during the commit process. To generate this file, include an CAIKSERL DD statement in the COMMIT JCL. The resulting CAIKSERL file contains CA Earl record definitions (DEF statements) for all ORD records being committed. These DEF statements are needed to produce CA Earl reports about the contents of the output data file.

┌──────────┐                  ┌──────────┐
| CAKSARCH |                  | CAKSLOAD |
| Commit   |                  |Production|
| program  |                  | Program  |
└────┬─────┘                  └────┬─────┘
     |                             |
     | ┌──────────┐   ┌──────────┐ |
     | |CA EARL   |   |CA PMA/DM | |
     └>|Control   |   |Output    |<┘
       |Statements|   |Data File |
       └────┬─────┘   └────┬─────┘
            |              |
            | ┌──────────┐ |
            | | CA EARL  | |
            └>| Program  |<┘
              | Output   |
              └──────────┘

Commit jobs only require one control statement: COMMIT DM. No matter which form you use, COMMIT erases existing REAL IRDs and moves IRDs from the DEVELOPMENT version into the REAL version. ORD definitions in the DEVELOPMENT version are moved into the TEST or PROD version, depending on which you specify on the COMMIT DM statement. After a CAKSCOMT run, the DEVELOPMENT version is empty: all IRDs and ORDs in the DEVELOPMENT version have been moved.

►►─ COMMIT ─┬─ DM TEST ─┬─────────────────────────────────────────────────────►◄
            └─ DM PROD ─┘

where:

TEST

Moves ORDs from the DEVELOPMENT version into the TEST version and IRDs from the DEVELOPMENT version into the REAL version, leaving the DEVELOPMENT version empty.

PROD

Moves ORDs from the DEVELOPMENT version into the PROD version and IRDs from the DEVELOPMENT version into the REAL version, leaving the DEVELOPMENT version empty.

          COMMIT DM TEST
       ┌─────────────────────┬─────────────────────┐
       |                     |                     |
       |                     v                     v
┌──────┴───────┐      ┌──────────────┐      ┌──────────────┐      ┌──────────────┐
|  DEVELOPMENT |      |              |      |              |      |              |
|    Version   |      | REAL Version |      | TEST Version |      | PROD Version |
|  IRDs & ORDs |      |    (IRDs)    |      |    (ORDs)    |      |    (ORDs)    |
└──────┬───────┘      └──────────────┘      └──────────────┘      └──────────────┘
       |                                                                 v
                             v
       |                     |                                           |
       └─────────────────────┴───────────────────────────────────────────┘
          COMMIT DM PROD