DC001003 STALLED WAITING FOR ICEECB when Archive Journal condense phase was long

Products

• IDMS
• IDMS - Database

Issue/Introduction

The following messages are observed when an ARCHIVE JOURNAL condense took longer than usual.  What does this mean and what is ICEECB? 

23.58.31 STC00722 +IDMS DC203004 Vnnn Tnnnnnnn SYSJRN08 Being Condensed - Waiting for Finish 
23.58.40 STC00722 +IDMS DC203004 Vnnn Tnnnnnnn SYSJRN08 Being Condensed - Waiting for Finish 
23.58.50 STC00722 +IDMS DC203004 Vnnn Tnnnnnnn SYSJRN08 Being Condensed - Waiting for Finish 
23.59.00 STC00722 +IDMS DC001003 Vnnn Tnnnnnnn TASK:BATCBULK PROG:<pgmname> STALLED WAITING FOR ICEECB AT 2FF83C9C 
23.59.00 STC00722 +IDMS DC201006 Vnnn T1 ABRT D002 nnnnnnn 100 BATCBULK xxxxxxx xxxxxxxxx xxxxxx nnnnnnnn 
23.59.13 STC00722 +IDMS DC203004 Vnnn Tnnnnnnn SYSJRN08 Being Condensed - Waiting for Finish 
23.59.22 STC00722 +IDMS DC203004 Vnnn Tnnnnnnn SYSJRN08 Being Condensed - Waiting for Finish 
00.01.12 STC00722 +IDMS DC203005 Vnnn Tnnnnnnn Program-ID <pgmname> Transaction-ID nnnnnnnnnn has been Rolled Out! 

Environment

Release: All supported releases.

Cause

A task needed access to the CV journal in question for automatic recovery of a transaction.

The CV journal was in the middle of the condense phase of ARCHIVE JOURNAL so the online transaction had to wait until it completed.

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 in this case, INACTIVE INTERVAL was also set to 10 seconds, so one of those 10 second intervals, the stall interval (INACTIVE INTERVAL) popped before the ICEECB timer popped.

Resolution

Again this is rare, but because IDMS internally waits for 10 seconds for rechecking the journal, the suggestion is to set INACTIVE INTERVAL to 11 seconds.