Step 5. Creating JCL procedures for address spaces

About this task

Perform this task for an IBM Z Workload Scheduler tracker, controller, and server started task. You must define a started task procedure or batch job for each IBM Z Workload Scheduler address space.

The EQQJOBS dialog generates several members in the output sample library that you specified when running the EQQJOBS installation aid program. These members contain started task JCL that is tailored with the values you entered in the EQQJOBS dialog. Tailor these members further, according to the data sets you require. For guidance on adequate memory to allocate for the end-to-end server started task, see z/OS memory requirements for directly connected agents and mailman servers.

Because the end-to-end server started task uses TCP/IP communication, you should do the following:
  1. Modify the JCL of EQQSER (the end-to-end server started task) so that it has access to the C run time libraries, either as STEPLIB (include the CEE.SCEERUN in the STEPLIB concatenation) or by LINKLIST (the CEE.SCEERUN is in the LINKLIST concatenation).

    Use the end-to-end server TOPOLOGY TCPIPJOBNAME() parameter to specify the TCP/IP started task name that is used by the end-to-end server. This parameter can be used if you have multiple TCP/IP stacks or if the TCP/IP started task name is different from TCPIP.

  2. Set up a server started task to handle end-to-end scheduling with fault tolerance capabilities. You can use the same server also to communicate with the Dynamic Workload Console. In fact, the server can also handle APPC communication if configured for this. In IBM Z Workload Scheduler version 8.2, the type of communication that should be handled by the server started task is defined in the new SERVOPTS PROTOCOL() parameter.
    In the PROTOCOL() parameter, you can specify any combination of:
    APPC
    The server should handle APPC communication.
    JSC
    The server should handle Dynamic Workload Console communication.
    E2E
    The server should handle end-to-end communication. The IBM Z Workload Scheduler controller uses the end-to-end server to communicate events to the fault-tolerant agents. The end-to-end server starts multiple tasks and processes using the UNIX™ System Services.
    When you do this, be aware that:
    • The IBM Z Workload Scheduler controller and the end-to-end server use TCP/IP services. Therefore it is necessary that you define a USS segment for the controller and for the end-to-end server started task user IDs. No special authorization is required; it can be defined in USS with any user ID.
    • Although it is possible to handle end-to-end scheduling with fault tolerance capabilities, JSC communication, and APPC communication with the same server started task, you should have a server started task dedicated for end-to-end scheduling with fault tolerance capabilities (SERVOPTS PROTOCOL(E2E)). In this way you do not have to also stop the other server processes when you restart the Dynamic Workload Console server.
    • The server started task is important for handling JSC and end-to-end with fault tolerance capabilities communication. You should set the end-to-end and the Dynamic Workload Console server started tasks as non-swappable and define them with at least the same dispatching priority as the IBM Z Workload Scheduler controller.