IBM Information Management System (IMS) - Group home

Is your IMS restart taking too long? Could it be hung?

By Michelle Carey posted Fri March 04, 2022 12:47 PM

  

When your IMS restart is taking a long time, have you wondered if restart is doing anything or whether it is hung?

To help answer those questions, IMS introduced an IMS restart log read progress message that helps you diagnose restart issues. It is shipped as part of APAR PH01551/PTF UI59302. 

This enhancement addresses RFE 17063. IMS is changing to issue the DFS5055I message that indicates that a log record read is either in progress or has completed. 

Here's how it works

  1. The IMS restart issues the first DFS5055I message when it starts reading the log.
  2. It re-issues the message every 30 seconds thereafter if restart lasts more than 30 seconds.
  3. It re-issues the message when restart has completed reading the log.


Here is an example of that DFS5055I message text:

DFS5055I RESTART LOG READ PASS 
n
 IS IN PROGRESS; LSN=
lsn


DFS5055I RESTART LOG READ PASS
n
 HAS COMPLETED;  LSN=
lsn
 

PASS
n
 is the restart log read pass number, which can be 1 for normal restart, or 1 or 2 for emergency restart. 
lsn
 is the log sequence number.


You can find more information about message DFS5055I in the IMS documentation or in APAR PH01551.

Now you have a better way to see what's really going on. Information is power!


Brought to you by IMS developer Sandy Stoob
0 comments
12 views