TCP/IP connected

Figure 4 shows two Tivoli Workload Scheduler for z/OS address spaces with a TCP/IP connection on a z/OS system.

You represent this system to the scheduler by defining a computer workstation with a destination field that specifies the destination name of the tracker. The controller transmits JCL, release commands, WTO messages, and cleanup requests across the TCP/IP link. The tracker receives data across the TCP/IP link and performs the following actions:

• Submits JCL for batch jobs to the JES internal reader
• Writes the JCL for started tasks into the EQQSTC data set and issues START procname z/OS commands
• Issues JES release commands for jobs in HOLD status
• Submits the cleanup job.

The event-tracking routines create event records to describe activities that occur on the system. These records are added to the tracker event writer queue in ECSA. The tracker processes the queue, transmits the records to the controller across the TCP/IP link, and writes the events into the event data set. The IP task in the controller receives the event records, and the current plan is updated.

Figure 4. A z/OS system with a TCP/IP connection

Table 6 shows the initialization statements you can use to create the configuration in Figure 4.

OPCOPTS  OPCHOST(YES)
         ERDRTASK(0)

ROUTOPTS TCPIP(DEST1:'1.111.111.111'/4444)

TCPOPTS  TCPIPJOBNAME('TCPIP')
         HOSTNAME('9.12.134.1')
         TRKPORTNUMBER(8888)

OPCOPTS OPCHOST(NO)
        ERDRTASK(0)
        EWTRTASK(YES)
TRROPTS HOSTCON(TCP)
        TCPHOSTNAME('9.12.134.1')
        TCPPORTNUMBER(8888)
TCPOPTS TCPIPJOBNAME('TCPIP')
        HOSTNAME('1.111.111.111')
        TRKPORTNUMBER(4444) 

EWTROPTS EWSEQNO(01)