In example 2, four address spaces are shown conversing with each other in an OCF network. Two of the address spaces, B93A and B92A, are on system ZOSA. The other two, B93P and B92B, are on system ZOSB. In addition to carrying out Beta product application functions, subsystems B93A and B93P also serve as OCF nodes in transferring requests to the other machine via the LU6.2 protocol boundary. Because they are being used as OCF nodes, both subsystems (B93A and B93P) must remain active for the entire period of communication.
Subsystem B92A on system ZOSA can communicate with subsystem B92B in system ZOSB and vice versa simply by specifying the subsystem ID B92B in the transfer request. The request is then automatically routed from subsystem B92A via B93A and B93P to the target subsystem B92B.
Online user A on system ZOSA can access subsystem B93P (master) on ZOSB simply by specifying the subsystem (B93A, slave) in the online application. The online user only needs to know the system and location name, and the subsystem ID. OCF takes care of the rest. The same applies to online user B. User B has direct access to subsystem B93P (master).
In this example, the following OCF parameters are necessary in the BETA.PARMLIB members:
+------------------------------------------------------------------------+
| ... |
|OCF_APPLID = OCFPMS00 |
|OCF_CONVERSE = OCFPMS01,4,5,10,32768 |
|OCF_LOCAL_SYSTEM = B93A,BETA93 |
|OCF_LOCAL_SYSTEM = B92A,BETA92 |
+------------------------------------------------------------------------+
+------------------------------------------------------------------------+
| ... |
|OCF_APPLID = OCFPMS01 |
|OCF_CONVERSE = OCFPMS00,4,5,10,32768 |
|OCF_LOCAL_SYSTEM = B93P,BETA93 |
|OCF_LOCAL_SYSTEM = B92B,BETA92 |
+------------------------------------------------------------------------+
For the BETA.PARMLIB members in use by Beta 92 on ZOSA and Beta 92 on ZOSB, no additional OCF parameters are required. This is because the subsystems B92A and B92B have already been specified in the OCF_LOCAL_SYSTEM parameters above as being accessible in this OCF network.
It would also be possible to connect subsystems B92A and B93P directly across the LU6.2 boundary, in addition to the connection between the subsystems B93A and B93P. As a consequence, it would be necessary to maintain additional VTAM and OCF definitions and additional hardware to support the additional conversations. Since the OCF nodes on each z/OS machine know which subsystems are locally active, only one OCF and VTAM connection is required between two z/OS hosts running Beta products. The hardware and software resources required are then put to use more efficiently.