Activating server support for end-to-end scheduling with fault tolerance capabilities

To set up the required server environment, customize the INIT and SERVOPTS initialization statements. For example: 
SERVOPTS SUBSYS (OPCX)
         PROTOCOL (E2E)
         TPLGYPRM(TPLGY)

You can start the server by using the z/OS® START command, or you can have the controller start and stop the server automatically. In the latter case, include the server (srv1) in the OPCOPTS statement in the IBM Z Workload Scheduler parameter library. The server with TCP/IP support requires access to the C language runtime library (either as STEPLIB or as LINKLIST). If you have multiple TCP/IP stacks, or a TCP/IP started task with a name different from TCPIP, then use the TCPIPJOBNAME parameter of the TOPOLOGY statement.

You are always required to define OMVS segments for server started tasks and ensure that a HOME directory is defined in the OMVS segment. For details, see HOME directory requirements for started tasks.