ISC/MRO connections - CONNECT

The ISC/MRO connections (CONNECT) views display information about ISC over SNA connections, MRO connections and the local system entry.

For the local system entry, the only applicable fields are the applid and signature fields, but the Cancel, Purge and Force actions apply to allow AIDs to be cleared from the local system.

Supplied views

To access from the main menu, click:

CICS operations views > Connection operations views > ISC/MRO connections

Table 1. Views in the supplied ISC/MRO connections (CONNECT) view set
View Notes
ISC/MRO connections

EYUSTARTCONNECT.ACQUIRE

 Acquire a connection (APPC only).
ISC/MRO connections

EYUSTARTCONNECT.BACKOUT

 Back out any units of work that are in-doubt because of a failure of the connection.
ISC/MRO connections

EYUSTARTCONNECT.CANCEL

 Cancel automatic initiation descriptor (AID) queuing for a connection.
ISC/MRO connections

EYUSTARTCONNECT.COMMIT

 Commit any units of work that are in-doubt because of a failure of the connection.
ISC/MRO connections

EYUSTARTCONNECT.DETAIL1

 Displays detailed information about session information and allocate requests for a selected ISC/MRO connection.
ISC/MRO connections

EYUSTARTCONNECT.DETAIL2

 Displays detailed information about Automatic Initiator Descriptors (AIDs) and bids for a selected ISC/MRO connection.
ISC/MRO connections

EYUSTARTCONNECT.DETAIL3

 Displays detailed information about function ships for a selected ISC/MRO connection.
ISC/MRO connections

EYUSTARTCONNECT.DETAIL4

 Detailed information about the resource signature.
ISC/MRO connections

EYUSTARTCONNECT.DETAILED

 Displays detailed information about a selected ISC/MRO connection.
ISC/MRO connections

EYUSTARTCONNECT.DISCARD

 Discard a connection from the CICS system where it is installed. The connection must be out of service before it can be discarded.
ISC/MRO connections

EYUSTARTCONNECT.ENDAFFINITY

 Specifies, where CICS is a member of a VTAM generic resource group, that VTAM is to end an affinity owned by CICS. This is valid only for APPC and LU6.1 connections. The connection must be out of service and, for APPC, in NORECOVDATA state.
  • There is no facility in VTAM for inquiring on affinities, so CICS has no certain knowledge that an affinity exists for a given connection. Whenever there is a possibility that an affinity has been created that must be ended explicitly, CICS issues message DFHZC0177. This message gives the NETNAME and NETID of the suspect connection.
  • If a request to end an affinity is rejected by VTAM because no such affinity exists, CICS issues message DFHZC0181.
ISC/MRO connections

EYUSTARTCONNECT.FORCE

 Force transactions associated with a connection to be immediately purged (VTAM only).
ISC/MRO connections

EYUSTARTCONNECT.INSERVICE

 Place the system in service; that is, available for use.
  • For an MRO connection, all sessions are placed in service and the following occurs:
    • If both the issuing system and the remote system have IRC open, and the remote system has INSERVICE connection definition for the issuing system, the connection is made ACQUIRED.
    • Otherwise, the status of the connection is set INSERVICE so that the connection is acquired when the above conditions are met.
    • The status of the underlying sessions for a connection is always the same as that for the connection itself.
  • For an EXCI connection, all receive sessions (or 'pipes') are placed in service and available for use by the client program.
  • For an ISC APPC connection, the LU Services Manager sessions are placed in service, thereby enabling the connection subsequently to be acquired.
  • For an ISC LU6.1 connection, all sessions are placed in service.
ISC/MRO connections

EYUSTARTCONNECT.NORECOVDATA

Force all in-doubt units of work (according to the transaction definitions), target any resyncs that were outstanding for the connection, and erase the logname previously received from the partner system. The state of the connection is reset.

Attention:You should use NORECOVDATA only in exceptional circumstances. It erases recovery information and may compromise data integrity for units of work that have updated resources on remote systems.

Examples of circumstances in which you might need to use it are:
  • You need to discard a connection, or issue an ENDAFFINITY, and it is not possible for the quiesce protocols with the partner system to be completed. (Neither action is possible for an APPC connection if recovery data is outstanding.)
  • In operational or logic error results in a logname mismatch for the connection. The connection state must be reset to allow the exchange lognames process to complete.
ISC/MRO connections

EYUSTARTCONNECT.NOTPENDING

Force all in-doubt units of work (according to the transaction definition) that were created by the connection before the initial (or cold) start of the partner. Also forget any resyncs (waitforget UOW-links) that are outstanding for the connection, and created before the initial (or cold) start of the partner.

The PENDING condition indicates the existence of recovery information (either shunted UOWs or decisions remembered for the partner) on a connection that has experienced a lognames mismatch with its partner. For a CICS Transaction Server for z/OS partner, a lognames mismatch indicates that the partner has performed an initial start. For a pre-CICS Transaction Server for z/OS partner, a lognames mismatch indicates that the partner has performed a cold start. In either case, the recovery protocol has been corrupted by a loss of log data at the partner.

It is not possible to set a connection to NOTPENDING state (forcing in-doubt and erasing NOFORGET UOWs) until this system has made contact with the partner and received a new logname from it.

Decisions for a whole connection can be forgotten, but that does not affect the memory of a decision for any other connection involved in the UOW.

ISC/MRO connections

EYUSTARTCONNECT.OUTSERVICE

Place the connection out of service; that is, not available for use.

For a connection, all sessions are placed out of service (immediately if PURGE is specified, or when tasks have terminated if it is not) and the following occurs:
  • If an APPC connection is currently ACQUIRED and you specify OUTSERVICE, the command fails. You must RELEASE the connection before setting OUTSERVICE.
  • If any other connection is currently ACQUIRED, the sessions are broken (quiesced). The connection cannot be used until it is once again placed INSERVICE.
  • If the connection is currently RELEASED, the status of the connection is set to OUTSERVICE and it cannot be used until it is in service again.
  • The status of the underlying sessions for a connection is always the same as that for the connection itself.
  • For an EXCI connection, all receive sessions (or 'pipes') are placed out of service and are not available for use by the client program.
  • For an ISC APPC system, this option is valid only if the connection is RELEASED. The LU Services Manager sessions are placed out of service, and the connection cannot be acquired until it is placed INSERVICE again.
  • For an ISC LU6.1 connection, all sessions are released and placed out of service: immediately if PURGE or FORCEPURGE is specified; or when tasks have terminated if neither PURGE nor FORCEPURGE is specified. If the response to an INQUIRE CONNECTION command shows OUTSERVICE, it does not imply that the connection has been explicitly set as SET OUTSERVICE; in particular circumstances, you cannot reinstall this connection.
ISC/MRO connections

EYUSTARTCONNECT.PURGE

 Purge abnormally the transactions associated with a connection (VTAM only). CICS terminates the transactions associated with this connection only if system and data integrity can be maintained. Note: A transaction is not purged if its definition specifies SPURGE=NO.
ISC/MRO connections

EYUSTARTCONNECT.RELEASE

 Release a connection (APPC only).
ISC/MRO connections

EYUSTARTCONNECT.RESYNC

 Retry any UOWs shunted because of the failure of this connection (that is, exchange lognames resynchronization for this connection is to be attempted). This process should normally be started automatically when a connection is acquired or when a UOW is unshunted.
ISC/MRO connections

EYUSTARTCONNECT.SET

 Display the Set view in order to change the attributes of a selected ISC/MRO connection.
ISC/MRO connections

EYUSTARTCONNECT.TABULAR

 Displays tabular information about ISC and MRO connections.

Actions

Table 2. Actions available for CONNECT views
Action Description
ACQUIRE Acquire a connection (APPC only).
BACKOUT Back out any units of work that are in-doubt because of a failure of the connection.
CANCEL Cancel automatic initiation descriptor (AID) queuing for a connection.
COMMIT Commit any units of work that are in-doubt because of a failure of the connection.
DISCARD Discard a connection from the CICS system where it is installed. The connection must be out of service before it can be discarded.
ENDAFFINITY Specifies, where CICS is a member of a VTAM generic resource group, that VTAM is to end an affinity owned by CICS. This is valid only for APPC and LU6.1 connections. The connection must be out of service and, for APPC, in NORECOVDATA state.
  • There is no facility in VTAM for inquiring on affinities, so CICS has no certain knowledge that an affinity exists for a given connection. Whenever there is a possibility that an affinity has been created that must be ended explicitly, CICS issues message DFHZC0177. This message gives the NETNAME and NETID of the suspect connection.
  • If a request to end an affinity is rejected by VTAM because no such affinity exists, CICS issues message DFHZC0181.
FORCE Force transactions associated with a connection to be immediately purged (VTAM only).
FORCECANCEL Cancel all automatic initiation descriptors (AIDs), including system AIDs, queuing for the specified connection. This can lead to unpredictable results and should be used only in exceptional circumstances.

Note: This does not remove transient data AIDs with an associated triggered task. These AIDs can be removed by purging the associated task.
FORCEPURGE

Immediately abnormally terminate all transactions running on sessions on the connected system. This can lead to unpredictable results and should be used only in exceptional circumstances. In some extreme cases (for example, if an error occurs during backout processing), CICS might terminate abnormally.

For in-doubt and shunted UOWs, FORCEPURGE has no effect. To force shunted UOWs, you must use the COMMIT, BACKOUT, or FORCE commands on the connection following a FORCEPURGE. This can lead to unpredictable results and should be used only in exceptional circumstances.
INSERVICE Place the system in service; that is, available for use.
  • For an MRO connection, all sessions are placed in service and the following occurs:
    • If both the issuing system and the remote system have IRC open, and the remote system has INSERVICE connection definition for the issuing system, the connection is made ACQUIRED.
    • Otherwise, the status of the connection is set INSERVICE so that the connection is acquired when the above conditions are met.
    • The status of the underlying sessions for a connection is always the same as that for the connection itself.
  • For an EXCI connection, all receive sessions (or 'pipes') are placed in service and available for use by the client program.
  • For an ISC APPC connection, the LU Services Manager sessions are placed in service, thereby enabling the connection subsequently to be acquired.
  • For an ISC LU6.1 connection, all sessions are placed in service.
KILL Terminate the task. System and data integrity is not guaranteed. The KILL option extends the PURGE and FORCEPURGE options. It should be used only after an attempt has been made to PURGE or FORCEPURGE a task. The KILL option does not guarantee integrity of any kind but in some situations it allows the user to free up a stalled region enabling the region to continue processing. In some cases, for example, if a task is killed during back out processing, CICS terminates abnormally.
NORECOVDATA

Force all in-doubt units of work (according to the transaction definitions), target any resyncs that were outstanding for the connection, and erase the logname previously received from the partner system. The state of the connection is reset.

Attention:You should use NORECOVDATA only in exceptional circumstances. It erases recovery information and may compromise data integrity for units of work that have updated resources on remote systems.

Examples of circumstances in which you might need to use it are:
  • You need to discard a connection, or issue an ENDAFFINITY, and it is not possible for the quiesce protocols with the partner system to be completed. (Neither action is possible for an APPC connection if recovery data is outstanding.)
  • In operational or logic error results in a logname mismatch for the connection. The connection state must be reset to allow the exchange lognames process to complete.
NOTPENDING

Force all in-doubt units of work (according to the transaction definition) that were created by the connection before the initial (or cold) start of the partner. Also forget any resyncs (waitforget UOW-links) that are outstanding for the connection, and created before the initial (or cold) start of the partner.

The PENDING condition indicates the existence of recovery information (either shunted UOWs or decisions remembered for the partner) on a connection that has experienced a lognames mismatch with its partner. For a CICS Transaction Server for z/OS partner, a lognames mismatch indicates that the partner has performed an initial start. For a pre-CICS Transaction Server for z/OS partner, a lognames mismatch indicates that the partner has performed a cold start. In either case, the recovery protocol has been corrupted by a loss of log data at the partner.

It is not possible to set a connection to NOTPENDING state (forcing in-doubt and erasing NOFORGET UOWs) until this system has made contact with the partner and received a new logname from it.

Decisions for a whole connection can be forgotten, but that does not affect the memory of a decision for any other connection involved in the UOW.

OUTSERVICE

Place the connection out of service; that is, not available for use.

For a connection, all sessions are placed out of service (immediately if PURGE is specified, or when tasks have terminated if it is not) and the following occurs:
  • If an APPC connection is currently ACQUIRED and you specify OUTSERVICE, the command fails. You must RELEASE the connection before setting OUTSERVICE.
  • If any other connection is currently ACQUIRED, the sessions are broken (quiesced). The connection cannot be used until it is once again placed INSERVICE.
  • If the connection is currently RELEASED, the status of the connection is set to OUTSERVICE and it cannot be used until it is in service again.
  • The status of the underlying sessions for a connection is always the same as that for the connection itself.
  • For an EXCI connection, all receive sessions (or 'pipes') are placed out of service and are not available for use by the client program.
  • For an ISC APPC system, this option is valid only if the connection is RELEASED. The LU Services Manager sessions are placed out of service, and the connection cannot be acquired until it is placed INSERVICE again.
  • For an ISC LU6.1 connection, all sessions are released and placed out of service: immediately if PURGE or FORCEPURGE is specified; or when tasks have terminated if neither PURGE nor FORCEPURGE is specified. If the response to an INQUIRE CONNECTION command shows OUTSERVICE, it does not imply that the connection has been explicitly set as SET OUTSERVICE; in particular circumstances, you cannot reinstall this connection.
PURGE Purge abnormally the transactions associated with a connection (VTAM only). CICS terminates the transactions associated with this connection only if system and data integrity can be maintained. Note: A transaction is not purged if its definition specifies SPURGE=NO.
RELEASE Release a connection (APPC only).
RESYNC Retry any UOWs shunted because of the failure of this connection (that is, exchange lognames resynchronization for this connection is to be attempted). This process should normally be started automatically when a connection is acquired or when a UOW is unshunted.
SET Display the Set view in order to change the attributes of a selected ISC/MRO connection.

Fields

Table 3. Fields in CONNECT views
Field Attribute name Description
Access method ACCESSMETHOD The access method in use for this connection (VTAM, IRC, INDIRECT, XCF, XM, NETBIOS, TCPIP or NOTAPPLIC).
Peak automatic initiator descriptors (AIDs) AIDHWM The peak number of automatic initiator descriptors (AIDs) in the AID chain.
Number of automatic initiator descriptors (AIDs) AIDS The current number of automatic initiator descriptors (AIDs) in the AID chain.

This is obsolete from CICS TS Version 5 Release 5.
Number of automatic initiator descriptors (AIDs) AIDSF The current number of automatic initiator descriptors (AIDs) in the AID chain.
Total number of allocate requests ALLOCATES The total number of allocate requests against this system.
Allocate queue limit (QUEUELIMIT) ALLOCQLIMIT The value of the QUEUELIMIT parameter as specified on the CONNECTION definition. If this value is reached, then allocate queue requests are rejected. If the CONNECTION is defined with a QUEUELIMIT of NO, N/A will be displayed.
Number of ATIs satisfied by primary sessions ATISBPRI The number of ATI requests satisfied by primary (contention loser) sessions.
Number of ATIs satisfied by secondary sessions ATISBSEC The number of ATI requests satisfied by secondary (contention winner) sessions.
Autoconnect option AUTOSTATUS Indicates whether sessions with this connection are to be bound when CICS is initialized or whenever communication with VTAM is started:
  • ALLCONN - Associated sessions are bound.
  • AUTOCONN - Associated sessions are bound.
  • NONAUTOCONN - Associated sessions are not bound.
  • NOTAPPLIC - The connection is the local system entry.
BAS resource definition version BASDEFINEVER The BAS version number of this definition.
Total number of bids sent BIDSSENT The total number of bids that were sent.
Last modification agent CHANGEAGENT The change agent identifier that made the last modification.
  • CSDAPI - The resource was last changed by a CEDA transaction, by the programmable interface to DFHEDAP or by an EXEC CICS CSD command.
  • CSDBATCH - The resource was last changed by a DFHCSDUP job.
  • DREPAPI - The resource was last changed by a CICSPlex SM BAS API command.
  • DREPBATCH - The resource was last changed by a CICSPlex SM utility.
  • AUTOINSTALL - The resource was last autoinstalled.
  • CREATESPI - The resource was last changed by an EXEC CICS CREATE command.
  • DYNAMIC - The resource was installed dynamically.
  • NOTAPPLIC - This is not applicable for this resource.
  • OVERRIDE - Resource was last changed by resource overrides.
  • N_A - Resource was created or last updated prior to CICS TS Version 4 Release 1 and support for resource signatures.
Last modification agent release CHANGEAGREL If the connection was installed using a CICSPlex SM SYSLINK definition, this is the CICS release level of the CICS system where the connection is installed. For connections not installed using SYSLINK this is the CICS release level of the agent that made the last modification to the connection definition.
Last modification time CHANGETIME If the connection was installed using a CICSPlex SM SYSLINK definition, this is the local date and time of the installation. For connections not installed using SYSLINK this is the local date and time when the connection definition was last changed.
Last modification user ID CHANGEUSRID If the connection was installed using a CICSPlex SM SYSLINK definition, this is the user ID that requested the installation. For connections not installed using SYSLINK this is the user ID that made the last modification to the connection definition.
Number of bids currently in progress CONCURBIDS The number of bids currently in progress.
Local connection create time CONNCREATIME The local time when the connection was created
Local connection delete time CONNDELETIME The local time when the connection was deleted
Connection status CONNSTATUS For connections using either the APPC or MRO protocol, the status of the connection as one of the following:
  • ACQUIRED - The connection is acquired.
  • AVAILABLE - The connection is acquired, but there are currently no bound sessions.
  • FREEING - The connection is being released.
  • NOTAPPLIC - The connection is not a CICS-to-CICS MRO or APPC connection.
  • OBTAINING - The connection is being acquired.
  • RELEASED - The connection is released.
Input Values: ACQUIRED, RELEASED
External CICS interface type CONNTYPE Indicates whether this connection is:
  • SPECIFIC - For communication from a non-CICS client program to the CICS system, and is an MRO link with one or more sessions dedicated to a single user in a client program.
  • GENERIC - For communication from a non-CICS client program to the CICS system, and is an MRO link with a number of sessions to be shared by multiple external CICS interface users.
  • NOTAPPLIC - Not an external CICS interface connection.
Source of the resource definition DEFINESOURCE The source of the definition, depending on which agent made the last change.
Creation time DEFINETIME If the connection was installed using a CICSPlex SM SYSLINK definition, this is the local date and time of the installation. For connections not installed using SYSLINK this is the local date and time when the connection definition record was created on DFHCSD or EYUDREP.
Number of DL/I function ships DLIFUNCSHIP The number of DL/I requests for function shipping.
Number of Distributed Program Link function ships DPLFUNCSHIP The number of Distributed Program Link (DPL) requests that have been function shipped across this connection.
Interval Control FS start requests with channels ESTICCHNL Number of Interval Control FS start requests with channels
Number of bytes received on START channel requests ESTICCHNRCVD The number of bytes received on START channel requests
Number of bytes sent on START channel requests ESTICCHNSENT The number of bytes sent on START channel requests
Program Control FS LINK requests with channels ESTPCCHNL Number of program control FS LINK requests with channels
Bytes received on LINK channel requests ESTPCCHNRCVD Number of bytes received on LINK channel requests
Bytes sent on LINK channel requests ESTPCCHNSENT Number of bytes sent on LINK channel requests
Number of terminal sharing channel requests ESTTCCHNL The number of terminal sharing channel requests.
Bytes received on terminal sharing channel requests ESTTCCHNRCVD Number of bytes received on terminal sharing channel requests
Bytes sent on terminal sharing channel requests ESTTCCHNSENT Number of bytes sent on terminal sharing channel requests
Exit Tracing status EXITTRACING Controls the terminal exit program's tracing activity for the sessions associated with this connection. A value of NOTAPPLIC means this connection is either not an LU6.1 or APPC connection, or it is a remote connection.

Input Values: EXITTRACE, NOEXITTRACE

Allocates rejected because QUEUELIMIT reached EXIT_REJALLC The total number of allocates rejected due to the QUEUELIMIT value being reached.
Number of allocate requests with other failure FAILEDOTHERS The number of allocate requests that failed due to a session not being currently available for use.
Number of allocate requests with link failure FAILINKALLOC The number of allocate requests that failed due to the connection being released, out of service, or with a closed mode group.
Number of File Control function ships FCFUNCSHIP The number of file control requests for function shipping.
GMT connection create time GMTCREATIME The time when the connection was created in Greenwich Mean Time (GMT) format
GMT connection delete time GMTDELETIME The time when the connection was deleted in Greenwich Mean Time (GMT) format
APPC generic resource GRNAME For an APPC connection to a generic resource when this system is also a generic resource, this field contains the 8-character generic resource name of the connected LU. Otherwise, the field is blank.
Number of Interval Control function ships ICFUNCSHIP The number of interval control requests for function shipping.
Installation agent INSTALLAGENT The install agent identifier that made the installation.
  • CSDAPI - The resource was installed by a CEDA transaction, by the programmable interface to DFHEDAP or by an EXEC CICS CSD command.
  • CREATESPI - The resource was installed by an EXEC CICS CREATE command.
  • AUTOINSTALL - The resource was autoinstalled.
  • DYNAMIC - The resource was installed dynamically.
  • GRPLIST - The resource was installed by GRPLIST INSTALL.
Installation time INSTALLTIME The local date and time when the definition was installed.
Installation user ID INSTALLUSRID The user ID that installed the resource definition.
Name of real link towards TOR LINKSYSTEM The 4-character name of the connection that is the real link towards the TOR for a remote or indirect system entry, if it is available. It is not set if some connection definitions in the chain from the remote or indirect entry to the link system are missing.
Maximum number of concurrent bids MAXBIDS The maximum number of bids in progress at any one time.
Peak number of primary sessions in use MAXPRIMARIES The maximum number of primary (contention loser) sessions in use at any one time.
Number of allocates purged when MAXQTIME exceeded MAXQTALLCPRG The number of allocates purged because the queue processing time would have exceeded the maximum queue time value.
Maximum queue time MAXQTIME The maximum amount of time, in seconds, provided to process an allocate queue once the QUEUELIMIT value for the connection has been reached. If an allocate queue would take longer than this to process, the queue is purged.
Number of allocates purged due to MAXQTIME value MAXQTPURGCNT The number of times an allocate queue has been purged because its processing time would have exceeded the maximum queue time value.
Peak number of secondaries in use at one time MAXSECOND The maximum number of secondary (contention winner) sessions in use at any one time.
Member name of connected LU MEMBERNAME For an APPC connection to a generic resource when this system is also a generic resource, this field contains the 8-character member name (applid) of the connected LU. Otherwise, the field is blank.
Connection ID NAME The name of the installed connection.
Net name NETNAME The name by which the remote system is known to the network.
Number of AIDs waiting for a session NONSPECAIDS The current number of automatic initiator descriptors (AIDs) that are waiting for a session to become available.
Network qualified name NQNAME The network qualified name if one was sent by VTAM at logon time.
Peak number of outstanding allocate requests OUTSALLOC The maximum number of allocate requests that were queued for this system.
Pending status PENDSTATUS For connections using the APPC and MRO protocol, indicates whether there are any units of work that require resynchronization after a session failure (PENDING or NOTPENDING).
Number of primaries currently in use PRICURRUSED The number of primary (contention loser) sessions currently in use
Connection protocol PROTOCOL For connections with an access method of VTAM, indicates which SNA protocol is in use, either LU61 or APPC. A value of EXCI means this connection uses the External CICS Interface. A value of NOTAPPLIC means this connection is not a VTAM connection.
Number of queued allocate requests QUEDALLOCATE The current number of queued allocate requests against this system.
Number of defined receive sessions RECEIVECOUNT For MRO connections, the number of receive sessions defined in the SESSIONS definition.
Recovery status RECOVSTATUS Indicates whether there is recovery information outstanding for the connection:
  • NORECOVDATA - The connection was quiesced and neither side of the connection has recovery information outstanding. Data integrity will be maintained for a cold start of the local CICS system.
  • RECOVDATA - The local CICS system has either in-doubt logical units of work or outstanding resynchronizations on the connection. Resynchronization will take place the next time the connection becomes active. Data integrity will not be maintained for a cold start of the local CICS system.
  • NRS - The connection is active and has completed the exchange of lognames. There may be logical units of work in-flight or in resynchronization.
Connection name in remote system REMOTENAME The name by which this connection is known in a remote system.
Net name of the owning TOR REMOTESYSNET The system ID of the owning TOR
Remote connection name REMOTESYSTEM The name of the remotely connected system
Number of secondaries currently in use SECCURRUSED The number of secondary (contention winner) sessions currently in use.
Number of defined send sessions SENDCOUNT For MRO connections, the number of send sessions defined in the SESSIONS definition.
Service status SERVSTATUS Indicates whether the system can receive and send data as follows:
  • INSERVICE - The connection is in service; the system can send and receive data.
  • OUTSERVICE - The connection is not in service; the system can not send or receive data.
  • GOINGOUT - An OUTSERVICE request was issued for the connection, but can not be processed until all current work is complete.
  • NOTAPPLIC - This is not applicable for this resource.
Number of Transient Data function ships TDFUNCSHIP The number of transient data requests for function shipping.
Number of terminal sharing requests TERMSHAREREQ The number of transaction routing commands.
Number of Temporary Storage function ships TSFUNCSHIP The number of temporary storage requests for function shipping.
Connection type TYPE The connection type. Values are: LU61, LU62, INDIRECT, MRO, NETBIOS, TCPIP or NOTAPPLIC
Exchange lognames (XLN) status XLNSTATUS The status of the exchange lognames (XLN) process. A value of NOTAPPLIC means that the link is released, the link is MRO, LU6.1, or single-session APPC, or the link does not support synchronization level 2 conversations.
Number of allocates purged by XZIQUE exit XZIQALLCPRG The number of allocates purged as a result of the XZIQUE exit requesting that queues be purged.
Number of queue purges requested by XZIQUE exit XZIQPRGCNT The number of allocate queue purges requested by the XZIQUE exit.
Number of allocates rejected by XZIQUE exit XZIQREJS The number of allocates rejected by the XZIQUE exit.
ZCP tracing ZCPTRACING Indicates the status of the ZCP trace facility. A value of NOTAPPLIC means this connection is not LU6.1 or APPC.

Input Values: ZPTRACE, NOZPTRACE