Question & Answer
Question
Why is my CICS region hanging instead of terminating after I receive an error indicating that "CICS will be terminated"? My CICS region experienced the following error:
DFHLG0734 severe error (code X'3337') has occurred while accessing the CICS system log. CICS will be terminated.
The message indicates CICS will terminate, but the region never shuts down. CICS becomes unresponsive. Following is the last message in the CICS log:
BPXP018I THREAD 1D53880000000000, IN PROCESS 17172044, ENDED WITHOUT BEING UNDUBBED WITH COMPLETION CODE 0033E000
I am running Xpediter from Compuware.
Answer
Compuware provided fix XDRN115 to resolve this problem.
When reviewing a dump at the time of the hang, enter VERBX DFHPDxxx 'TR=1' (where xxx is your release level of CICS like 690 for CICS TS 5.2) and you should see the following exception trace entry for the CICS main terminal control task- TCP:
*EXC* - DSSR_ILLEGAL_ENVIRONMENT_2 - FUNCTION(WAIT_MVS) RESOURCE_TYPE(CCVSAMWT)
ECB_ADDRESS(627844C0) PURGEABLE(NO) WLM_WAIT_TYPE(IO) RESOURCE_NAME(ASYNRESP)
Next you can look at the stack for this TCP task by entering VERBX DFHPDxxx 'KE=1' and you will find DFHERM is calling the Task Related User Exits or TRUEs for 'CICS termination'. Here are the module names in TCP's stack:
NAME
DO_TERM
DFHERM
DFHEIQDS
DFHFCFS
CLOSE_FILE
DISABLE_FILE
CATALOG_FCTE
CATALOG_WRITE
DFHCCCC
WRITE
FILE_GET
VSAM
Compuware exit program CXIETASK is doing a systems programming interface (SPI) SET FILE Close command against file DBUGPRF . But, there is a restriction that says CICS services cannot be used during this type of termination. So, this causes the region to hang. You can read more about the restrictions in topic entitled Limitations of task-related user exits during CICS shutdown in the CICS.
Product Synonym
CICS/TS CICSTS CICS TS CICS Transaction Server
Was this topic helpful?
Document Information
Modified date:
12 January 2016
UID
dwa1243301