SNA only connection
Figure 7 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 VTAM® links.
Key:
- FCC
- Data Store Communication task
- FL
- Fetch Job Log Task
- FN
- Data Store SNA handler task
- NCF
- Network Communication function
Table 9 shows the initialization statements you can use to create the configuration in Figure 7.
Controller member | Tracker member |
C1
OPCOPTS RCLEANUP(YES) NCFTASK(YES) NCFAPPL(LU00C1T) FLOPTS CTLLUNAM(LU00C1D) SNADEST(********.LU000D1, LU000T1.LU000D2) ROUTOPTS SNA(LU000T1) |
T1
OPCOPTS NCFTASK(YES) NCFAPPL (LU000T1) TRROPTS HOSTCON(SNA) SNAHOST(LU00C1T) |
Data Store members | |
D1
DSTOPTS DSTLUNAM(LU000D1) CTLLUNAM(LU00C1D) |
D2
DSTOPTS HOSTCON(SNA) DSTLUNAM(LU000D2) CTLLUNAM(LU00C1D) |
Note:
In this example, the LU names for the communication
partners are the following:
- LU00C1D
- Controller C1, when communicating with a Data Store.
- LU000D1
- Data Store D1.
- LU000D2
- Data Store D2.
- LU00C1T
- Controller C1, when communicating with tracker T1.
- LU000T1
- Tracker T1.