IBM Support

CWXN stuck in the initial socket receive for 30 seconds

Question & Answer


Question

I have encountered a problem with a TCPIPS service that is getting backed up, due to what appears to be long running CICS CWXN transactions.

My TCPIPS service definition is defined with a 'socket close' as 10 seconds, but CWXN is timing out at a default of 30 seconds. The CWXN transaction does not have a DTIMOUT value assigned.

What configuration setting would force transaction CWXN to timeout sooner than 30 seconds?

Answer

The CWXN tasks all appear to be in their initial socket receives. This receive waits for the DTIMOUT value or 30 seconds if a DTIMOUT value is not set. The tasks all have a timeout time 30s after their suspend time.

The correct action to reduce the time these tasks wait is to code a DTIMOUT value for transaction CWXN.

Sharon Yang
IBM CICS Level2 response

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

Product Synonym

CICSTG CICS TG;CICS/TS CICSTS CICS TS CICS Transaction Server

Document Information

Modified date:
18 September 2018

UID

dwa1448469

Page Feedback