DFHXQ0304I STOP command is waiting for connections to be closed. Number of active connections = connections.

Explanation

A queue server STOP command has been issued (either via an MVS STOP command or via an MVS MODIFY command with the text STOP) but there are still active connections to the server, so the STOP command has not yet taken effect.

System action

The server rejects any further attempts to establish new connections, but continues processing requests for existing connections. Each time a connection is terminated, this message is repeated for as long as there are more active connections.

User response

Further information about the connections which are still active can be obtained using the command DISPLAY CONNECTIONS.

If the server needs to be shut down without waiting for connections to be closed, issue the queue server CANCEL command. Note that this immediately terminates any active connections, causing any further requests for that server to be given a SYSIDERR indication. (The MVS CANCEL command can also be used, but should preferably be avoided because it prevents the server from producing its normal closedown statistics and reports).

Note that if a CICS region is abnormally terminated while server connect or disconnect processing is in progress, or is terminated without going through end of task processing (for example using the FORCE command) there is a slight chance that the server will not be notified that the connection has been terminated. In this case the server is not able to be closed down with the server STOP command, but only with the server CANCEL command.

Module

DFHXQOP

Destination

Console and SYSPRINT