Identifying remote systems

In addition to having a SYSIDNT for itself, a CICS® system requires a SYSIDNT for every other system with which it can communicate. SYSIDNT names are used to relate session definitions to system definitions; to identify the systems on which remote resources, such as files, reside; and to refer to specific systems in application programs.

SYSIDNT names are private to the CICS system in which they are defined; they are not known by other systems. In particular, the SYSIDNT defined for a remote CICS system is independent of the SYSIDNT by which the remote system knows itself; you need not make them the same.

The mapping between the local (private) SYSIDNT assigned to a remote system and the APPLID by which the remote system is known globally in the network (its netname), is made when you define the intercommunication link. For example, for an MRO or ISC over SNA connection, on the CONNECTION definition you specify the following attributes:
CONNECTION(sysidnt)
The local name for the remote system
NETNAME(applid)
The applid of the remote system
For an IPIC connection, on the IPCONN definition you specify the following attributes:
IPCONN(sysidnt)
The local name for the remote system
APPLID(applid)
The APPLID of the remote system

Each SYSIDNT name defined to a CICS system must be unique.



dfht12c.html | Timestamp icon Last updated: Sunday, 4 June 2017