To participate in cross platform scheduling, all machines must have CAICCI installed, active, and connected to the machines involved.
For non z/OS communications, CAICCI connections are defined in the following files:
The format of the REMOTE control cards are:
REMOTE = ip address cciname blocksize [STARTUP] [PORT=nnnn] [RETRY=x]
Specifies the numerical TCP/IP address of the node or the hostname that can be resolved into a TCP/IP address. You can specify an IP address in either IPV4 format (dotted decimal notation: "ddd.ddd.ddd.ddd") or IPV6 format ("xx:xx:xx:xx:xx:xx:xx:xx") in release r12 and later. A TCP/IP PING command on this value is successful.
Specifies the name that CAICCI uses for this node. This value can be the same as the hostname, but it does not have to be. The name must match the CAICCI name that is defined at the remote node. For z/OS, the SYSID parameter in the ENFPARMS defines the CAICCI name.
(Optional) Indicates that the connection is attempted as soon as CAICCI starts. Recommended.
Specifies the TCP/IP port number (nnnn) to use. The default on z/OS with CAICCI 2.1 is 1721 and can be changed on the PROTOCOL(TCPSSLGW…) statement. (The default port for non z/OS machines is 1721.).
Specifies the time (x) to wait to reconnect if the connection attempt fails or is broken.
CAICCI must be recycled to pick up changes to the ccirmtd file. The ccirmtd file also contains the LOCAL statement, which identifies this computer in a CAICCI network.
Example: a LOCAL statement:
LOCAL = BARNA03SRVR BARNA03XPS 32768 startup ALIAS=BARNA03W
An ALIAS keyword is required when the CAICCI name field, the second field on the LOCAL statement, is longer than eight characters. Most of the CAICCI applications on the mainframe can only support eight character CAICCI sysids (including cross platform scheduling). The ALIAS setting is the eight character name that z/OS CAICCI applications know the local computer.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|