XCF only connection
Figure 8 shows a JES2 MAS (shared spool) with two images. In Image 1, the controller and a tracker are in the same address space and connected via XCF. Image 2 contains another tracker. You need only one Data Store, which is installed in Image 2. The controller will request the Job Log from the Data Store using the FL subtask.
Key:
- FL
- Fetch Job Log task
- FCC
- Data Store Communication task
- MAJOR
- Controller/tracker main task
Table 10 shows the initialization statements you can use to create the configuration in Figure 8.
Controller member | Tracker member |
C1
OPCOPTS RCLEANUP(YES) NCFTASK(NO) ROUTOPTS XCF(XCFMEMT1) XCFOPTS GROUP(XCFGRUCT) MEMBER(XCFMEMCT) FLOPTS DSTGROUP(XCFGRUCD) CTLMEM(XCFMEMCD) XCFDEST(********.XCFMEMD1, XCFMEMT1.XCFMEMD1) |
T1
OPCOPTS NCFTASK(NO) TRROPTS HOSTCON(XCF) XCFOPTS GROUP(XCFGRUCT) MEMBER(XCFMEMT1) |
Data Store member | |
D1
DSTOPTS HOSTCON(XCF) DSTGROUP(XCFGRUCD) DSTMEM(XCFMEMD1) |
|
Note:
In this example, the XCF groups for the
communication partners are the following:
- XCFGRUCD
- The XCF group for the communication between controller and Data
Store. The members in the group are:
- XCFMEMCD
- The controller.
- XCFMEMD1
- The Data Store.
- XCFGRUCT
- The XCF group for the communication between controller and tracker.
The members in the group are:
- XCFMEMCT
- The controller.
- XCFMEMT1
- The tracker.