Configuring and Installing Optional Components › Tasks for Separately Licensed Components › Configure the Multi-System Facility (MSF) › Set up Session Protocols › Setting up MSF to Use CAICCI › ADDRESS OPSCTL MSF DEFINE - Set Up MSF Connections Using CAICCI

ADDRESS OPSCTL MSF DEFINE - Set Up MSF Connections Using CAICCI

When using CAICCI, there are special rules for specifying the ADDRESS OPSCTL MSF DEFINE command for remote system definition. For the value of the APPLID keyword, you must specify the CAICCI system identifier (sysid) of the remote system.

For example, if the sysid of the remote system is CCI0B on a system that has an MSF ID of OPSS0B, your ADDRESS OPSCTL MSF DEFINE command would be:

ADDRESS OPSCTL "MSF DEFINE MSFID(OPSS0B) APPLID(CCI0B) CCI"

CCI0B

Identifies the sysid of CAICCI on system B.

The MSF checks to make sure that the value you specify is valid.

Note: In ADDRESS OPSCTL MSF DEFINE commands, the keyword CCI can only be used for remote systems.

The following examples illustrate several scenarios for defining an MSF connection.

Example 1: Definition of CCI as a Local System

In this example the CCI keyword is not used. The APPLID keyword is used to specify the local system ID to CAICCI.

ADDRESS OPSCTL "MSF DEFINE MSFID(OPSS0A) APPLID(CCI0A)"

Example 2: Using VTAM and CCI Simultaneously

• Local definition:

  ADDRESS OPSCTL "MSF DEFINE MSFID(OPSS0A) APPLID(OPSAPLID)"
  

• Remote definition to an APPC connection:

  ADDRESS OPSCTL "MSF DEFINE MSFID(OPSS0BVT) APPLID(OP2APLID) APPC"
  

• Remote definition to a CCI connection:

  ADDRESS OPSCTL "MSF DEFINE MSFID(OPSS0B) APPLID(CCI0B) CCI"
  

Example 3: Using CCI Only

• Local definition:

  ADDRESS OPSCTL "MSF DEFINE MSFID(OPSS0A) APPLID(CCI0A)"
  

• Remote definition:

  ADDRESS OPSCTL "MSF DEFINE MSFID(OPSS0B) APPLID(CCI0B) CCI"