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

Customize the INIT and SERVOPTS initialization parameters to set up the correct server environment. For example:

SERVOPTS SUBSYS (OPCX)
         PROTOCOL (E2E)
         TPLGYPRM(TPLGY)

For more information, see Tivoli® Workload Scheduler for z/OS: Customization and Tuning.

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 Tivoli Workload Scheduler for z/OS 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 always have to define OMVS segments for server started tasks.