Overview

OCF communication can also be established using the BSA X‑System Router Beta 02. As a separate standalone started task, the X‑System Router enables two LPARS (operating systems) to be connected via OCF. It can also be used to connect two parallel sysplexes, or to connect a parallel sysplex to an external system.

Advantages of using Beta 02

The advantage of using the X-System Router for OCF communication are as follows:

• This started task does not require a database or a Beta product library.
• In the event of VTAM problems, it can be restarted to rebuild the OCF (for example Beta 93) that is active as the master.
• Beta 02 can be used as an OCF node in a multi-CPU XCF connection without influencing the functions of the product started task environment (parallel sysplex) to provide a communication link to an external system.

Installation procedure

The X-System Router is implemented by installing Beta 02 as a started task. It is installed according to the same rules as for all other Beta started tasks. Do the following:

1. Create the JCL for the Beta 02 started task.
2. Create member B02SSIxx for the initialization of the subsystem ID (see "SSI parameters").
3. Define the subsystem ID.
4. Run BST01ARI.
5. Customize LST member B02LSTxx with the required OCF parameters (see "LST parameters for OCF" and "Parameters for OCF via TCP/IP".

Note

X-System-Router Beta 02 can also be used as a standalone started task for the BSA TCP/IP server. An example of how to activate the server as a separate, standalone, Beta 02 started task can be found under the name BETA02 in the BSA.SAMPLIB. For more information, see "BSA TCP/IP server as a standalone STC (Beta 02)".

Examples

Two examples are given on the following pages. The first example shows how the X-System Router can be used with a slave system, the second shows it without a slave system.

OCF in Beta 02 can also be used to connect an XCF sysplex to an external system (see "Example: Communication between sysplex and non-sysplex").