Updating the z/OS link-library definition

If you installed IBM Z Workload Scheduler in a separate load-module library, it is recommended that you define this library in the active LNKLSTnn member. Alternatively, you can define the load-module library on the STEPLIB DD statement of the started-task JCL and TSO logon procedures of IBM Z Workload Scheduler dialog users.

If you installed load modules in the data set OPC.SEQQLMD0 and this data set is cataloged in the master catalog, insert this record before the last entry in the LNKLSTnn member to add this library to the link library concatenation:

Adding LINKLIB
OPC.SEQQLMD0
If you choose not to define the IBM Z Workload Scheduler load-module library in the LNKLSTnn member, you must:
  • Copy the tracker modules, EQQINITP and EQQSSCMP, to a library in the z/OS link-library concatenation. EQQINITP is used by the master-scheduler-initialization function when the z/OS system is being IPLed. EQQINITP then loads EQQSSCMP into common storage. EQQSSCMP is about 23KB and is placed above the 16MB line. Remember to copy the modules again whenever they are updated by IBM Z Workload Scheduler maintenance. This is especially important for the EQQSSCMP module, which must be at the same update level as the rest of the IBM Z Workload Scheduler code.
  • Define the IBM Z Workload Scheduler load-module library on a STEPLIB DD statement in the started-task JCL.
  • Define the IBM Z Workload Scheduler load-module library on a STEPLIB DD statement in the TSO logon procedure of all IBM Z Workload Scheduler dialog users.
  • Load the dialog module, EQQMINOP, from an APF-authorized library. If you define the IBM Z Workload Scheduler load-module library on a TSO STEPLIB DD statement, and any of the other libraries defined on this DD statement are not authorized, you must copy EQQMINOP to another library in the LNKLST concatenation so that it is loaded APF authorized. You must also remember to copy the module again whenever it is updated by IBM Z Workload Scheduler maintenance.