Load modules

Decide if you want to use the same data set name for the IBM Z Workload Scheduler load modules as your previous environment. However, consider the additional effort required on your part to coordinate the JCL changes required for callers of IBM Z Workload Scheduler services such as:
  • EQQEVPGM
  • EQQUSINx
  • EQQYCOM
  • EQQYLTOP

If the IBM Z Workload Scheduler load library is not referenced in the STEPLIB DD statement, ensure that the IBM Z Workload Scheduler library is listed first in the LNKLST concatenation and that the library remains empty until you are ready to cut over to IBM Z Workload Scheduler on the production system. Then copy the load modules into the library and perform an LLA refresh.

Two IBM Z Workload Scheduler load modules must always be in a LNKLST library:
EQQINITx
The subsystem initialization module.
EQQSSCMx
The subsystem communication module.
However, this does not mean that you must reinitialize the subsystem to cut over IBM Z Workload Scheduler to production. The module names defined for EQQINITx and EQQSSCMx in the SYS1.PARMLIB subsystem name table (IEFSSNnn) can be overridden when an IBM Z Workload Scheduler address space is created.

The EQQMINOx load module requires special attention. EQQMINOx is the scheduler's dialog interface module, is invoked by TSO SERVICES, and passes dialog requests and data to the controller. EQQMINOx must run APF authorized, therefore it must reside in an authorized library. By this token, keep in mind that any unauthorized library in a STEPLIB or LIBDEF concatenation makes the entire concatenation unauthorized. So remember to identify the library where EQQMINOx resides.

Use the BUILDSSX parameter of the OPCOPTS initialization statement to rebuild the environment created during subsystem initialization at the new software level. When the address space is terminated, the previous environment is reinstated, thereby ensuring fallback to a previous release of IBM Z Workload Scheduler.

You can set the SSCMNAME parameter of the OPCOPTS initialization statement to permanently, or temporarily, replace the EQQSSCMx module that was loaded into common storage at IPL. When SSCNAME(TEMPORARY) is set, the named module is loaded into private storage of the IBM Z Workload Scheduler address space, therefore events created while the address space is not active will use the EQQSSCMx from the previous IPL. When SSCNAME(PERMANENT) is set, the old EQQSSCMx in common storage is replaced.

Note: Create backup copies of the old load module library before you replace the objects.