ACQSTATUS

ACQSTATUS specifies the acquire status of the resource. For a connection, this means whether it should have a session established (bound) or ended (unbound). For a node, it means whether the z/OS Communications Server ACB for the node should be opened or closed. The acquire status can be set to ACQUIRED (a status of ACQUIRING indicates that the acquisition has not yet been completed), or to RELEASED .

Setting RELEASED does not end any existing conversations that are using the resource; the acquire status is RELEASING until the existing conversations end. However, for connections, a conversation that is unowned and in a pending state (see STATE ) is ended immediately if the acquire state is set to RELEASED ; this means that connections being used by a failed application can be recovered.

ACQUIRING and RELEASING are shown as BEING ACQUIRED and BEING RELEASED by CEMT.

Network and other problems can cause connections to become stuck in a RELEASING or ACQUIRING state, in which case the operator might need to intervene using VTAM operator commands.

Note: VTAM is now the z/OS Communications Server.

If a FEPI connection remains in a RELEASING state for longer than expected, try the following:

Note the node and target associated with the connection; use CEMT INQUIRE FETARGET to find the z/OS Communications Server application name that the target represents.
Issue the following VTAM command to find out the state of network session associated with the connection:
```
D NET,E,ID=nodename
```
Note the session status. See z/OS Communications Server: IP and SNA Codes for an explanation of the status. If no session exists and a subsequent INQUIRE of the connection status using CEMT shows the state still as BEING RELEASED, there has been a system failure; you should collect diagnostic information.
If the session is in session takedown processing, you can use the VTAM command
```
D NET,SESSION
```
to find out what signals are needed to complete processing.
If you can resolve the problem using commands on the back-end system, attempt to do so.
If there is no other way to resolve the session status, you can use the VTAM command
```
V NET,TERM
```
to end the network procedure in progress. FEPI will then be able to complete processing.

If an ACQUIRING state has persisted for too long, and you cannot determine why the session has not been established, follow the same procedure described previously. If no session is active for the connection, FEPI is currently waiting for the retry interval to expire. The system log should contain VTAM messages explaining why the session cannot be established. The LACQCODE option of CEMT INQUIRE FECONNECTION gives the reason code z/OS Communications Server provided for the last session failure.

Also be sure to check that the node on which the connection depends is properly acquired; if not, resolve whatever problem is indicated by the LACQCODE option for the node.

Note that, under normal circumstances, after a FEPI FREE RELEASE command has been issued the session does not remain in RELEASED state, because FEPI automatically tries to reacquire the session. However, if a FEPI SET CONNECTION ACQSTATUS(RELEASED) command is issued before the FREE RELEASE, the session remains in RELEASED state.