Date:         Tue, 14 Feb 2006 16:53:21 -0800
Reply-To:     CICS List <CICS-L@LISTSERV.UGA.EDU>
Sender:       CICS List <CICS-L@LISTSERV.UGA.EDU>
From:         "Smith, Cheryl" <csmith@CO.SANTA-BARBARA.CA.US>
Subject:      CICS delayed shutdown
Content-Type: multipart/alternative;

This morning after testing a printer, we saw the following problem:


 


05.00.09 STC06497  +DFHTM1710I CICSTLAW Control returned from PLT
programs.                                          

05.00.09 STC06497  +DFHTM1781 CICSTLAW CICS shutdown cannot complete
because some non-system user tasks have not     

terminated.


05.02.09 STC06497  +DFHCESD  CICSTLAW THERE ARE NOW 0002 TASKS STILL IN
THE SYSTEM.                                  

05.02.11 STC06497  +DFHCESD  CICSTLAW THERE ARE NOW 0001 TASKS STILL IN
THE SYSTEM.                                  

05.02.13 STC06497  +DFHTM1782I CICSTLAW All non-system tasks have been
successfully terminated.                      

05.02.13 STC06497  +DFHZC2305I CICSTLAW Termination of VTAM sessions
beginning                                       

05.06.14 STC06497 @DFHZC2350A CICSTLAW


05:06:14 CICSTLAW CICS Terminal Control shutdown threshold(4 minutes)
exceeded. Sessions still active: C42SXBA ((1)  

Module name: DFHZSHU)


06.26.04 STC06497  +DFHRM0204 CICSTLAW There are no indoubt,
commit-failed or backout-failed UOWs.                   

06.26.05 STC06497  ACFAE048 ACF2/CICS Termination Started


 


The problem is that even after recognizing that C42SXBA had exceeded its
threshold for shutting                      

down, the system waited an additional 80 minutes before actually
shutting down.  Part of this was                    

addressed by adding a TCSACTN=FORCE and another part was addressed by
fixing the printer in                          

question.


 


But what really puzzles me, a complete CICS neophyte, is what is causing
CICS to shutdown at all,                    

after the 80 minutes elapses.  We had the same timing (shutdown occurred
apparently spontaneously 80   

minutes after the threshold of 4 minutes had been exceeded)and situation
occur several months          

previous.  I have searched for "80" or a multiple of 80 through all the
parameters I can find in       

CICS and fail to see what actually trips the long delayed shutdown.  

 

Any suggestions?                  


[text/html]