Activating server support for the Dynamic Workload Console

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

SERVOPTS SUBSYS (OPCX)
         USERMAP (USERS)
         PROTOCOL (TCP)
         PORTNUMBER (425)
         CODEPAGE (IBM-037)
INIT     CALENDAR (DEFAULT)

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 servers (srv1, srv2, ...) on 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 a SYSTCPD DD card is required pointing to a TCP/IP data set containing the TCPIPJOBNAME parameter.

You always have to define OMVS segments for Tivoli Workload Scheduler for z/OS server started tasks.