On each operating system running Beta product address spaces, there must be at least one address space (the "OCF node") for OCF functions, enabling the Beta products to communicate with each other across the OCF network. At present, OCF node functions always run in the started task of a product or enhancement facility.
Note: Each OCF node can be a member of only one OCF network.
As in the examples, the product subsystems are best connected as master and slave (master-slave connection). Depending on the features of the Beta product concerned, a master-to-master connection can be set up, but only for online usage (TSO or Beta VDF).
Each Beta product may have slightly different requirements. For detailed examples of OCF environments for a specific product, please see the Installation and System Guide of the product concerned.
To support the VTAM connection between the two z/OS systems, some definitions must be made in the SYS1.VTAMLST and in the BETA.PARMLIB datasets of the OCF node subsystems. Once in place, these definitions need not be changed again unless changes are made to the LU6.2 connection, or additional Beta product subsystems are added to the OCF Network.