TCP/IP only connection
Figure 9 shows a JES2 with two images. In Image 1, the controller and tracker are in the same address space. Image 2 contains a tracker. The spool is not shared. Two Data Stores are required, one for Image 1 and one for Image 2. All connections are TCP/IP links.
Key:
- FCC
- Data Store Communication task
- FL
- Fetch Job Log Task
- ID
- Task for Data Store-to-controller TCP/IP communication
- IP
- Task for tracker-to-controller TCP/IP communication
Table 11 shows the initialization statements you can use to create the configuration in Figure 9.
Controller member | Tracker member |
C1
OPCOPTS RCLEANUP(YES) FLOPTS TCPDEST(********.'9.12.134.1', '9.12.134.9') ROUTOPTS TCPIP(TRK1:'9.12.134.9') |
T1
TRROPTS HOSTCON(TCP) TCPHOSTNAME('9.12.134.1') |
Data Store members | |
D1
DSTOPTS HOSTCON(TCP) CTLHOSTNAME('9.12.134.1') |
D2
DSTOPTS HOSTCON(TCP) CTLHOSTNAME('9.12.134.1') |
Note:
In this example, the name of the tracker destination
is TRK1. The destination name is defined also in the destination field
of the workstation. The TCP/IP address of image 1 is 9.12.134.1 and
the TCP/IP address of image 2 is 9.12.134.9.