Skip to content

Overview of File Tailoring for Installation JCL

File tailoring for installation JCL builds these jobs:

  1. Builds applicable skeleton jobs, by site configuration, as indicated in the following tables:

    a. At an ALL site

     | Package Type | Job Name (CMNxx)            |
 |:---------------- |:---------------------------------- |
 | PERMANENT        | 20`*`, 30, 50, 55                  |
 | TEMPORARY        | 20T, 31T, 50T, 55T                 |
 | PERMANENT/Db2    | 20, 21, 32, 30, 37, 49, 50, 55, 57 |
 | TEMPORARY/Db2    | 20T, 21, 49, 31T                   |

    b. At a DP site with IEBCOPY (need CMN65 for revert)

     | Package Type | Job Name (CMNxx)  |
 |:--------------- |:----------- |
 | PERMANENT        | 10, 11, 15, 19, 20, 25, 29, 30, 50, 51, 55, 59                 |
 | TEMPORARY        | 10, 11, 15, 19, 20T, 25, 29, 31T, 35, 39                       |
 | PERMANENT/Db2    | 10, 11, 15, 19, 21, 20, 25, 29, 30, 32, 49, 50, 51, 56, 55, 59 |
 | TEMPORARY/Db2    | 10, 11, 15, 19, 21, 20T, 25, 29, 49, 31T, 35, 39               |

    c. At a DP site with OTHER (need CMN64-65 for Revert)

     | Package Type | Job Name (CMNxx) |
 |:------------------ |:---------------- |
 | PERMANENT        | 10, 11, 14, 15, 18, 19, 20, 24, 25, 28, 29, 30, 50, 51, 54, 55, 58, 59                     |
 | TEMPORARY        | 10, 11, 14, 15, 18, 19, 20T, 24, 25, 28, 29, 31T, 34, 35, 38, 39                           |
 | PERMANENT/Db2    | 10, 11, 14, 15, 18, 19, 21, 22, 20, 24, 25, 28, 29, 32, 30, 49, 50, 51, 54, 56, 55, 58, 59 |
 | TEMPORARY/Db2    | 10, 11, 14, 15, 18, 19, 21, 20T, 24, 25, 28, 29, 49, 31T, 34, 35,38, 39                    |

    The following jobs are created in all configurations, in the situations listed.

    • CMN17 is present if an external scheduler is used.

    • CMN30 and CMN55 are present for all permanent packages. (baseline ripple and backout reverse ripple), respectively

    • CMN37and CMN57 are present for all permanent packages. (baseline ripple and backout, respectively, with CMNDSPTM)

  2. Submits, through CMNSCHED, the skeleton jobs at the appropriate time. You can defer splitting the skeleton jobs until the final approval of the package.

  3. The CMN37 or CMN57 jobs are not run if the impact analysis update is successful in the CMN30 job (baseline ripple) or the CMN55 job (reverse baseline ripple). If the impact analysis update is unsuccessful, transactions are written to the CMNDELAY file. The next time that ZMF is started, the transactions in the CMNDELAY file are processed to submit the CMN37 job or the CMN57 job to update impact analysis data.

The scheduling record for a package is created at approve time. This means that updates to the install date of a package in FRZ status being implemented with the ChangeMan ZMF internal scheduler are captured. At approve time, the scheduling record is built with the latest install date originally entered or updated by the user. If your internal scheduler is not ChangeMan ZMF, you can change the scheduled installation date even after a package is frozen.