General CA MIM Statements and Commands › (MIM) CTCPATH Statement and Command-Define CTC Device

(MIM) CTCPATH Statement and Command-Define CTC Device

The CTCPATH statement and command lets you define the CTC device addresses connecting systems.

This statement has the following format:

CTCPATH FROMSYSTEM=sysid  ADDRESS=(devn1[,devn2]) TOSYSTEM=sysid

FROMSYSTEM

(Optional) Identifies the system from which you are creating a CTC path. Specify the system name, alias, or index number for this system in place of sysid.

Default: The local system.

ADDRESS

Indicates what logical device address the system identified on the FROMSYSTEM parameter should use to communicate with the system identified on the TOSYSTEM parameter.

You can specify two types of addresses: a primary address and a backup channel address. Specify the primary address in place of devn1. If you want to establish backup channels, then specify their addresses in place of devn2.

You can specify a maximum of 32 addresses for the ADDRESS parameter.

TOSYSTEM

(Optional) Identifies the system to which you are creating a CTC path. Specify the system name, alias, or index number for this system in place of sysid.

Usage Notes: CTCPATH

• Do not specify CTCPATH statements between IFSYS and ENDIF statements.
• To check your CTCPATH statements, issue the DISPLAY PATH command.
• You need to reformat your control files after specifying CTCPATH statements for the first time. You do not have to reformat the control files if you change the values for a CTCPATH statement, if you specify an additional CTCPATH statement, or if you delete a CTCPATH statement, as long as one remains.
• You must specify two CTCPATH statements for each pair of systems that you are connecting.

  Note: For more information on CTC connectivity, see the CA MIM Programming Guide.

• You can only specify the CTCPATH statement in the = INIT MIM file.
• Specify the same CTCPATH statements on all systems. The initialization member of each system contains the complete list of CTCPATH statements, even those members that define paths on other systems.
• If z/OS is running as a guest under z/VM and you want to connect systems to virtual CTC devices, define virtual addresses for each device through the CP DEFINE and COUPLE commands.
• Omitting the TOSYSTEM operand causes the destination system discovery when CA MIM completes the initial communication on the path.
• CA MIM’S CTC devices should be exluded from SMS ACS routines.
• Before starting CA MIM, attach the real CTC devices to the MIMGR virtual machine at the virtual addresses that are specified on the CTCPATH statements, or define and couple any virtual CTC devices that you are using.

  If you want to communicate with a z/OS or z/VM guest running on the same processor using virtual CTC devices, define virtual CTC devices by placing appropriate CP DEFINE and CP COUPLE commands in your PROFILE GCS on the MIMGR user ID.

Examples: CTCPATH Statement

• To connect systems SYS1 and SYS2 through the primary addresses 803 and 2C3, specify these statements in the initialization member:

  CTCPATH FROMSYSTEM=SYS1 ADDRESS=803 TOSYSTEM=SYS2
  CTCPATH FROMSYSTEM=SYS2 ADDRESS=2C3 TOSYSTEM=SYS1
  

• To connect systems SYSA and SYSB using a primary CTC connection and two backup or alternate CTC connections, define the following statements:

  CTCPATH FROMSYSTEM=SYSA ADDRESS=(90D0,80C1,9090) TOSYSTEM=SYSB
  CTCPATH FROMSYSTEM=SYSB ADDRESS=(70D1,A0C0,8091) TOSYSTEM=SYSA
  

  The first pair of CTC addresses, 90D0 and 70D1, connects SYSA and SYSB. This is the primary connection.

  The second pair of CTC addresses, 80C1 and A0C0, connects SYSA and SYSB. This is the first alternate connection.

  The third pair of CTC addresses, 9090 and 8091, connects SYSA and SYSB. This is the second alternate connection.

Note: The dynamic CTCPATH command requires compatibility level 12.0.