FEPI INQUIRE CONNECTION

Function

FEPI INQUIRE CONNECTION returns information about a FEPI connection. A connection is identified by specifying its target and node.

Syntax

Read syntax diagramSkip visual syntax diagramFEPI INQUIRE CONNECTION
 
>>-FEPI INQUIRE CONNECTION--NODE(data-value)-------------------->
 
>--TARGET(data-value)--+-------------------+-------------------->
                       '-ACQNUM(data-area)-'
 
>--+-----------------+--+--------------------+------------------>
   '-ACQSTATUS(cvda)-'  '-CONVNUM(data-area)-'
 
>--+-------------------+--+------------------------+------------>
   '-INSTLSTATUS(cvda)-'  '-LASTACQCODE(data-area)-'
 
>--+-----------------+--+------------------+--+-------------+--->
   '-POOL(data-area)-'  '-SERVSTATUS(cvda)-'  '-STATE(cvda)-'
 
>--+---------------------+--+------------------------+---------><
   '-USERDATA(data-area)-'  '-WAITCONVNUM(data-area)-'
 

The following commands allow you to browse all FEPI connections. Read the information about browsing earlier in this book before using the browsing commands.

FEPI Browse CONNECTION

FEPI INQUIRE CONNECTION START
FEPI INQUIRE CONNECTION NEXTNODE|NEXTTARGET
NODE(8-character data-area)
TARGET(8-character data-area)
[The options are as for FEPI INQUIRE CONNECTION]
FEPI INQUIRE CONNECTION END

Conditions: INVREQ, NOTAUTH

The next connection for which information is returned depends on whether NEXTNODE or NEXTTARGET is specified. If NEXTNODE is specified, the information returned is for:

If NEXTTARGET is specified, the information returned is for:

Options

ACQNUM(fullword binary data-area)
returns the number of times that the connection has been acquired.
ACQSTATUS(cvda)
returns the acquire state; that is, whether a session on the connection is bound or not. The relevant CVDA values are:
ACQUIRED
The session is bound.
ACQUIRING
A state of ACQUIRED has been requested but binding a session has not yet been completed.
RELEASED
No session is bound.
RELEASING
A state of RELEASED has been requested but unbinding the session has not yet been completed.
If ACQUIRING or RELEASING persist, the operator might need to intervene using VTAM® commands to recover the connection.
CONVNUM(fullword binary data-area)
returns the number of conversations that have used the connection.
INSTLSTATUS(cvda)
returns the install state of the connection. The relevant CVDA values are:
INSTALLED
The connection is in a pool defined by INSTALL and is available for use.
NOTINSTALLED
The connection is in a pool, or involves a node or target that is being discarded but is still in use.
LASTACQCODE(fullword binary data-area)
returns the result of the last acquire request for the connection; that is, the sense code from the last VTAM REQSESS, zero indicating success.
Note:
CLSDST(PASS)--X'32020000'--can be returned in this field. This is the unbind flow received by CICS® during CLSDST(PASS) processing.

For details of VTAM sense codes, see the VTAM Messages and Codes manual, or SNA Formats manual.

NODE(8-character data-value/8-character data-area)
is the node identifying the connection.
POOL(8-character data-area)
returns the name of the pool that defines the connection.
SERVSTATUS(cvda)
returns the service state of the connection. The relevant CVDA values are:
INSERVICE
The connection is in service and can be used in a conversation.
OUTSERVICE
The connection is out of service and cannot be used for any new conversation, but a conversation using the connection is unaffected. The service state is GOINGOUT until any such conversation ends.
GOINGOUT
A state of OUTSERVICE has been requested but the connection is still being used by some conversation.
STATE(cvda)
returns the state of the conversation using the connection. The relevant CVDA values are:
NOCONV
No conversation is active on the connection.
PENDSTSN
An STSN-handling task has been scheduled.
STSN
An STSN-handling task owns the conversation.
PENDBEGIN
A begin-session handling task has been scheduled.
BEGINSESSION
A begin-session handling task owns the conversation.
APPLICATION
A normal application task owns the conversation.
PENDDATA
FEPI is waiting for inbound data, following a FEPI START command.
PENDSTART
Inbound data having arrived, a task specified by FEPI START has been scheduled.
PENDFREE
An end-session handling task has been scheduled, following a FEPI FREE command.
FREE
An end-session handling task owns the conversation, following a FEPI FREE command.
PENDRELEASE
An end-session handling task has been scheduled, following an unbind request.
RELEASE
An end-session handling task owns the conversation, following an unbind request.
PENDUNSOL
An unsolicited-data handling task has been scheduled.
UNSOLDATA
An unsolicited-data handling task owns the conversation.
PENDPASS
The conversation is unowned, following a FEPI FREE PASS command.
The ‘pending’ states indicate that the conversation is unowned, pending the event or task indicated; the state ceases to be pending when a task issues a FEPI ALLOCATE PASSCONVID command. If a ‘pending’ state persists, it is likely that the application has failed in some way; you should consider resetting the connection by issuing FEPI SET CONNECTION RELEASED.
TARGET(8-character data-value/8-character data-area)
is the target identifying the connection.
USERDATA(64-character data-area)
returns the user data for the connection. If no user data has been set, nulls are returned.
WAITCONVNUM(fullword binary data-area)
returns the number of conversations that are waiting to start using the connection. Note that, if a conversation could use any one of several connections, it is counted as waiting on each one.

Conditions

Condition RESP2 Meaning
ILLOGIC 1 For START: browse of this resource type is already in progress.
For NEXT or INQUIRE: END was not issued.
END 2 For NEXT: all resource definitions have been retrieved.
INVREQ 116 TARGET name unknown.
INVREQ 117 NODE name unknown.
INVREQ 118 Connection unknown (TARGET and NODE names known, but not in a common pool).
[[ Contents Previous Page | Next Page Index ]]