Running on upgraded operating systems

To run the scheduler on a new version of the z/OS® operating system, you must reassemble the SMF and JES exits mentioned in Step 5. Adding SMF and JES exits for event tracking with the libraries of the new operating system. Load modules EQQTTTOP and EQQPTTCP are pre-linked to support the SOCKET interface. These modules are release-dependent, therefore you must link EQQTTTOP and EQQTTCP if you are installing Tivoli Workload Scheduler for z/OS for the first time and re-link them every time you upgrade to a later version of z/OS or Tivoli Workload Scheduler for z/OS.

If you upgrade the SMP/E environment to a later version of z/OS by using the SMP/E function BUILDMCS, the relink occurs automatically (ensure that the DDDEF entries for the new operating system are set up correctly by specifying the latest SEZACMTX and SCEELKED libraries). If you do not use BUILDMCS, relink the load modules by using the SMP/E function LINK LMODSCALLLIBS. With this function, all the Tivoli Workload Scheduler for z/OS modules are relinked to the latest SEZACMTX and SCEELKED libraries.

After you upgrade to a later version of z/OS, installing any Tivoli Workload Scheduler for z/OS PTF that updates EQQTTTOP and EQQPTTCP causes the automatic relink to these load modules. The automatic relink occurs regardless if you use the APPLY or APPLY REDO command.