IBM Support

AXMSC0036 when CICS tries to contact Temporary Storage Queue Server

Question & Answer


Question

Why do I get message AXMSC0036 from one of my CICS Transaction Server for z/OS (CICS TS) regions every few seconds when it tries to contact the Temporary Storage Queue (TSQ) server? Other CICS regions can continue to communicate with the TSQ server without a problem.

  AXMSC0036 Connection to server xxxx was rejected by the server.

Answer

Look for the following message in the log for the TSQ Server log:

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

where nn is the number of CICS regions still connected to the server. If you find the message, then the STOP command was entered against the TSQ Server. The STOP command terminates the server, waiting for any active connections to terminate first, and preventing any new connections.

Any CICS region that is still communicating with the TSQ Server will continue to be able to do so and will not allow the TSQ Server to complete its termination.

Once a CICS region is cycled, it will be unable to reconnect with the TSQ Server until all CICS regions have been cycled and have broken contact with the server, allowing the termination to complete.

Another option is to use the following command:

CANCEL RESTART=YES

This terminates all existing connections and shuts down the server. A new instance of the server job is then started again immediately. See Shared TS queue server commands for more information.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Component":"Temporary Storage","Version":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Product Synonym

CICS/TS CICSTS CICS TS CICS Transaction Server

Document Information

Modified date:
13 January 2017

UID

dwa1334350