We are doing a disaster recovery test. One of the cv's is spitting out many messages waiting on condense. Not sure why the condense has not finished. DC203004 V18 J1JRNL Being Condensed - Waiting for Finish DC203004 V18 J1JRNL Being Condensed - Waiting for Finish DC203004 V18 J1JRNL Being Condensed - Waiting for Finish etc etc
The DC203004 message comes out because IDMS is trying to rollback the transaction but it detects that the specified journal file is being condensed. There are 3 slightly different scenarios within the code but they all end up issuing the DC203004 and then issue a #SETIME for 10 seconds. Upon expiration of the of the 10 second interval the code will again check the journal's header and if still in condense it will repeat the process with no limitation on the loop's iterations. Running the RESTART option on the archive journal specified in the message should clear the problem.