baije01

Tech Tip: CA IDMS Stalled Waiting for ICEECB

Discussion created by baije01 Employee on May 9, 2017

Question:

WE had the following messages and a task Stall abend when an Archive Journal condense took longer than usual.  What does this mean and what is ICEECB? 

23.58.31 STC00722 +IDMS DC203004 V101 T59344367 SYSJRN08 Being Condensed - Waiting for Finish
23.58.40 STC00722 +IDMS DC203004 V101 T59344367 SYSJRN08 Being Condensed - Waiting for Finish
23.58.50 STC00722 +IDMS DC203004 V101 T59344367 SYSJRN08 Being Condensed - Waiting for Finish
23.59.00 STC00722 +IDMS DC001003 V101 T59344367 TASK:BATCBULK PROG:GNABC894 STALLED WAITING FOR ICEECB AT 2FF83C9C
23.59.00 STC00722 +IDMS DC201006 V101 T1 ABRT D002 59344367 100 BATCBULK GNAJ822 GNABC894 GNAJOB 8C4F4A3F
23.59.13 STC00722 +IDMS DC203004 V101 T59344367 SYSJRN08 Being Condensed - Waiting for Finish
23.59.22 STC00722 +IDMS DC203004 V101 T59344367 SYSJRN08 Being Condensed - Waiting for Finish
00.01.12 STC00722 +IDMS DC203005 V101 T59344367 Program-ID GNABC894 Transaction-ID 3334158907 has been Rolled Out!

Answer:

In this case a task needed access to the Disk Journal in question for automatic recovery of the transaction.

The Disk Journal in question was in the middle of the Condense phase of ARCHIVE JOURNAL so the online transaction has to wait until it completes.

CV will put out the DC203004 message and then put the task into a WAIT for 10 seconds (using #SETIME TYPE=WAIT so the wait is for ICEECB) and when the timer pops it will check the Journal to see if the recovery can now proceed.

This is a rare occurrence but client had INACTIVE INTERVAL set to 10 seconds as well, so one of those 10 second intervals, the Stall interval (INACTIVE INTERVAL) popped before the ICEECB timer popped.

Again this is rare but because we have a set interval of 10 seconds for rechecking the journal, we suggested they set INACTIVE INTERVAL to 11 seconds. 

Outcomes