Utilities and Other Interfaces › CTC Path Validation Utility › Install the Utility

Install the Utility

The utility needs to be activated on both systems owning the end-point CTC devices in question.

The device addresses are passed on through the z/OS START command used to activate the utility. If the two addresses provided represent the same CTC connection, then the utility exchanges system information and displays the result of the exchange. If the two device addresses fail to communicate, then other error messages may be issued, and the CTC validation I/O from the utility remains pending on each device until the utility is canceled through operator command.

The general syntax for the checking 3-digit CTC devices is:

START PROCCTC,ddd

The general syntax for the checking 4-digit CTC devices is:

START PROCCTC,/dddd

Example:

Assume you were told device 810 on SYSA was connected to SYSB device 910. To verify this connection, perform the following steps:

1. Customize the PROCTC JCL PROC, rename it to CTCTEST, and copy it to an appropriate PROCLIB.
2. On SYSA, issue command START CTCTEST,810.
3. On SYSB, issue command START CTCTEST,910.
4. Monitor message traffic on SYSA and SYSB. If the utility ends normally on each system, then the two devices were able to communicate to one another across the complex. This typically occurs a few seconds after the START commands are issued on each system.
5. If the utility runs successfully, then you could define this particular channel-to-channel connection to CA MIM using CTCPATH statements placed in the MIMINIT parmlib member:

   CTCPATH  FROMSYS=SYSA  ADDR=810  TOSYS=SYSB
   CTCPATH  FROMSYS=SYSB  ADDR=910  TOSYS=SYSA
   

6. If the utility determines the devices are unable to communicate cross-system, then contact your local system programmer or OEM Service Engineer for hardware connectivity assistance. In this case, you need to terminate the utility on each system by using the z/OS CANCEL command.