Updating the z/OS® link-library definition

This section documents what you should do to update the z/OS® link-library definition if you installed the agent for z/OS in a separate load-module library.

If you installed the agent for z/OS in a separate load-module library, you should define this library in the active LNKLSTnn member.

If you installed load modules in the data set TWS.SEELLMD0 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
TWS.SEELLMD0
If you choose not to define the agent for z/OS load-module library in the LNKLSTnn member, you must:
  • Copy the Agent modules, ELLINITN and EELSSCMN, to a library in the z/OS link-library concatenation. ELLINITN is used by the master-scheduler-initialization function when the z/OS system is being IPLed. ELLINITN then loads EELSSCMN into common storage. Remember to copy the modules again whenever they are updated by agent for z/OS maintenance. This is especially important for the EELSSCMN module, which must be at the same update level as the rest of the agent for z/OS code.
  • Define the agent for z/OS load-module library on a STEPLIB DD statement in the started-task JCL.