Retrieve information about a system connection.
INQUIRE CONNECTION >>-INQUIRE CONNECTION(data-value)-------------------------------> .-----------------------------. V | >----+-------------------------+-+----------------------------->< +-ACCESSMETHOD(cvda)------+ +-ACQSTATUS(cvda)---------+ +-AUTOCONNECT(cvda)-------+ +-CONNSTATUS(cvda)--------+ +-CONNTYPE(cvda)----------+ +-CQP(cvda)---------------+ +-EXITTRACING(cvda)-------+ +-GRNAME(data-area)-------+ +-LINKSYSTEM(data-area)---+ +-MEMBERNAME(data-area)---+ +-NETNAME(data-area)------+ +-NQNAME(data-area)-------+ +-PENDSTATUS(cvda)--------+ +-PROTOCOL(cvda)----------+ +-RECEIVECOUNT(data-area)-+ +-RECOVSTATUS(cvda)-------+ +-REMOTENAME(data-area)---+ +-REMOTESYSNET(data-area)-+ +-REMOTESYSTEM(data-area)-+ +-SENDCOUNT(data-area)----+ +-SERVSTATUS(cvda)--------+ +-XLNSTATUS(cvda)---------+ '-ZCPTRACING(cvda)--------'
Conditions: END, ILLOGIC, NOTAUTH, SYSIDERR
For more information about the use of CVDAs, see CICS-value data areas (CVDAs).
The INQUIRE CONNECTION command retrieves information about a connection from your local CICS region to another CICS region or another system. A CONNECTION definition is sometimes known as a "system entry".
There are two main types of system connection:
A special form of MRO connection, used by the external CICS interface (EXCI), can exist between a CICS region and a non-CICS client program running in MVS, for example an MVS batch or TSO program. An EXCI connection connects the client program to a CICS region running in the same MVS image or within the same MVS/ESA sysplex.
In addition to links to other systems or devices, some connection definitions refer to remote connections. A remote connection is a link to another system or device that is actually owned by another CICS system. The owning system is called the terminal-owning region (TOR). Note that different connections may have different TORs. TOR here refers to the owning system for a particular connection.
The way that the local system is connected to the TOR makes a difference to the way in which the REMOTESYSTEM and REMOTESYSNET options of the remote CONNECTION definition are specified.
If the TOR is directly connected to the local system, the REMOTESYSTEM option usually names the CONNECTION definition for the link. (It can name an indirect connection, but that is an unusual setup). In this case, the netname of the TOR is specified in the link CONNECTION definition. The REMOTESYSNET option of the remote CONNECTION definition may or may not specify the netname of the TOR.
If a remote connection is on a system that is not directly linked to the TOR, the REMOTESYSTEM option can name one of two types of connection, as follows:
Note, however, that for remote connection definitions:
An application-owning region (AOR) has direct links to an intermediate system, CONNECTION(INTS) NETNAME(SYSI) to CONNECTION(AOR) NETNAME(AOR1); and also to terminal-owning regions (TORs), CONNECTION(TORB) NETNAME(TOR2) to CONNECTION(AOR) NETNAME(AOR1).
The AOR, APPLID=AOR1, has remote connection definitions, CONNECTION(CON1) NETNAME(NETCON1) REMOTESYSTEM(INDC) REMOTESYSNET() and links by indirect link to CONNECTION(INDC) NETNAME(TOR1) INDSYS(INTS); and then links by direct links to the intermediate system, CONNECTION(INTS) NETNAME(SYSI) to CONNECTION(AOR) NETNAME(AOR1). The AOR also has remote terminal definition, TERMINAL(TER1) NETNAME(NETTER1) REMOTESYSTEM(TORB) REMOTESYSNET() that has direct links to the TORs, CONNECTION(TORB) NETNAME(TOR2) to CONNECTION(AOR) NETNAME(AOR1).
The intermediate system has direct links to the TORs, CONNECTION(TORA) NETNAME(TOR1) to CONNECTION(INTS) NETNAME(SYSI).
The TORs have local connection definitions, CONNECTION(CON1) NETNAME(NETCON1), and local terminal definition, TERMINAL(TER1) NETNAME(NETTER1).
The following diagram illustrates a graphical representation of the example above.
Intermediate Terminal-owning Application-owning region (AOR) system regions (TORs) *---------------------------------* *-------------* *-------------------* | APPLID=AOR1 | | APPLID=SYSI | | APPLID=TOR1 | | | | | | | |Remote | | | | | |connection | | | | | |definitions Indirect link | | | | Local connection definitions |*------------* *------------* | | | | *-----------* ||CONNECTION | |CONNECTION | | | | | |CONNECTION | || (CON1) |*>| (INDC) | | | | | | (CON1) | ||NETNAME || |NETNAME | | | | | |NETNAME | || (NETCON1)|| | (TOR1) | | | | | | (NETCON1)*-------> ||REMOTESYSTEM|| |INDSYS | | | | | | | || (INDC) ** | (INTS) *-* | | | | | | ||REMOTESYSNET| | | | | | | | *-----------* || () | *------------* | | | Direct | |links | |*------------* | | | *-----------* *-----------* | | | | | |CONNECTION | |CONNECTION | | | *------------* | | | (TORA) | | (INTS) | | | | | | |NETNAME | |NETNAME | | | | | | | (TOR1) <-> (SYSI) | | | | | | *-----------* *-----------* | | | | | | | | | | Direct | |links | | | |*------------* | *-----------* *----------* | | *-----------* ||CONNECTION | | |CONNECTION | |CONNECTION| | | |CONNECTION | || (CON2) | *->| (INTS) | | (AOR) | | | | (CON2) | ||NETNAME | | |NETNAME | |NETNAME | | | |NETNAME | || (NETCON2)| | | (SYSI) <-> (AOR1) | | | | (NETCON2)*-------> ||REMOTESYSTEM| | | | | | | | | | || (INTS) *----* | | | | | | | | ||REMOTESYSNET| *-----------* *----------* | | *-----------* || (TOR1) | | *-------------* *-------------------* |*------------* | *-------------------* | | | APPLID=TOR2 | | | Direct links | | | *-----------* *----------* | | |CONNECTION | |CONNECTION| | | Remote terminal *->| (TORB) | | (AOR) | | | definition | |NETNAME | |NETNAME | | |*-------------* | | (TOR2) <-----------------> (AOR1) | | ||TERMINAL | | *-----------* *----------* | || (TER1) | | | | | ||NETNAME | | | | | || (NETTER1) | | | | Local terminal definition ||REMOTESYSTEM | | | | *------------* || (TORB) *---* | | |TERMINAL | ||REMOTESYSNET | | | | (TER1) | || () | | | |NETNAME | |*-------------* | | | (NETTER1) *--------> | | | *------------* *---------------------------------* *-------------------*
You can also browse through all of the CONNECTION definitions installed in your system by using the browse options (START, NEXT, and END) on INQUIRE CONNECTION commands. See Browsing resource definitions for general information about browsing, including syntax, exception conditions, and examples.
The criteria for ACQUIRED for MRO links are:
The RELEASED status can be caused by any one of a number of general conditions:
In the case of a CICS-to-CICS MRO connection, the RELEASED status may also be because:
In the case of an APPC ISC connection, the RELEASED status may also be because:
See the CICS® External Interfaces Guide for more information about EXCI connections.
For an ISC connection, the NETNAME corresponds to the VTAM APPLID of the remote system.
For a CICS-to-CICS MRO connection, the NETNAME is the name the remote system uses to log on to DFHIRP (from the APPLID option in its system initialization table (SIT)).
For a SPECIFIC EXCI connection, NETNAME is the name of the client program which is passed on the EXCI INITIALIZE_USER command; for a GENERIC EXCI connection, NETNAME is always blanks.
For an indirect connection, NETNAME corresponds to the APPLID (as specified in the SIT APPLID option) of the terminal-owning region.
NQNAME, which is supported for problem determination purposes only, is returned for both autoinstalled and RDO-defined resources if it has been supplied by VTAM. However, it is not catalogued for RDO-defined resources and is therefore not available on a restart until that resource logs on again.
If the resource is non-VTAM, NQNAME is blank. If the resource is a VTAM resource but has not yet received an NQNAME, CICS returns the known netname.
There is resynchronization work outstanding for the connection but the partner system has performed an initial start, preventing completion of the resynchronization process. (If the partner system is a CICS version earlier than CICS Transaction Server, a cold start performed on the partner system has the same effect.) You can use the SET CONNECTION NOTPENDING command to unilaterally commit or back out the units of work associated with the connection, according to their associated transaction definitions. You can also investigate the units of work individually and force them to commit or back out, in which case you must also complete the recovery activity by using a SET CONNECTION NOTPENDING command to clear the PENDING condition.
If this is an APPC connection, no new syncpoint work (that is, work involving synclevel 2 protocols) can be transmitted across it until a SET CONNECTION NOTPENDING command has been issued. This restriction does not apply to MRO connections.
If you are not concerned by the loss of synchronization caused by the initial (or cold) start of the partner, you can cause the SET CONNECTION NOTPENDING command to be issued automatically by specifying XLNACTION(FORCE) on the CONNECTION definition.
For further information about pending units of work, see the CICS Intercommunication Guide.
If there is recovery outstanding, then on completion of exchange lognames, either resynchronization takes place or, in the case of a cold exchange, the PENDING condition is created.
Otherwise this field is blank.