Setup and Initialization Considerations

  • When using IATUTJCT to move the JCT data set, you can pick up the new data set with any type of JES3 start; however, if you perform a hot start with refresh or a warm start, and you use the DYNALLOC statement to define the JES3JCT DD name, you must change the DYNALLOC statement to point to the new JCT data set.
  • The JES3 installation must properly meet specific programming requirements for using IATUTJCT.
    • Place the load library containing IATUTJCT and IATGRCK in the LNKLST concatenation or ensure they are in STEPLIB. JES3 must find these load modules in a normal library search.

      OS/390®, by default, places modules IATUTJCT and IATGRCK in SYS1.VnRnMn.SIATLIB.

    • Ensure that the library containing the IATUTJCT and IATGRCK modules is APF authorized.
    • Ensure that the JES3JCT, NJES3JCT, CHKPNT, and NCHKPNT DD statements are specified. The CHKPNT2 DD statement is optional and should be omitted if you are not using an alternate checkpoint data set or if you will not be using one after changing JES3 to use the new data sets.
    • Ensure that proper CHKPNT and CHKPNT2 DD statements are specified. There is no NCHKPNT2 DD statement. If you are using an alternate checkpoint data set, allocate a new one and leave it empty. When you restart JES3 to pick up the new primary and alternate checkpoint data sets, JES3 will automatically synchronize the new alternate checkpoint data set to the new primary checkpoint data set. Do not use the old alternate checkpoint data set as the new alternate checkpoint data set.
    • The PROC statement in the procedure must define the P= keyword parameter. This parameter controls the migration of a JCT data set from a lower version to a higher version in preparation for installing a new release of JES3 that requires the higher version.