Basic server configuration example
This section gives an example of a basic server configuration of Tivoli Workload Scheduler for z/OS. Tivoli Workload Scheduler for z/OS connects distributed agents to the server via TCP/IP. The controller transmits work to the fault-tolerant workstations via TCP/IP, and the same connection is used to pass event information back. The server is connected to the first level domain managers in the distributed network. TCP/IP is also used to connect the Dynamic Workload Console to the server through the connector. The server connects to the remote interfaces, either Programming Interfaces or remote ISPF interface users, using APPC. The following example shows a simple configuration using mixed protocols and minimal parameter customization.
Table 3 shows the initialization statements you can use to create the configuration in Figure 1, using the TCP/IP link for the user application-server communication.
EQQSERP
SERVOPTS SUBSYS(OPCA) USERMAP(USERS) PROTOCOL(E2E,TCP) TPLGYPRM(TPLGY) INIT CALENDAR(DEFAULT) |
TPLGY
TOPOLOGY TPLGYMEM(TPLGYDOM) BINDIR('/usr/lpp/TWS8.3.0') WRKDIR('/var/TWS/OPCA') USRMEM(TPLGYUSR) CODEPAGE(IBM-280) |
TPLGYUSR
USRREC USRCPU(FTW1) USRNAM('tws83') USRPSW('tws83') |
TPLGYDOM
DOMREC DOMAIN(DOM0) DOMMNGR(FTW1) DOMPARENT(MASTERDM) CPUREC CPUNAME(FTW1) CPUOS(WNT) CPUNODE('xxx.xx.xxx.x') CPUDOMAIN(DOM0) CPUTYPE(FTA) CPUTCPIP(31111) CPUFULLSTAT(ON) CPUAUTOLNK(ON) CPULIMIT(SYSTEM) FIREWALL(NO) CPUTZ('EUT') |
Note:
For USERS members,
see the SERVOPTS USERMAP parameter, and for the TPLGY members, see
the TOPOLOGY statement in Tivoli® Workload Scheduler for z/OS®: Customization and Tuning. |