Database Status list

The Database Status list names the DL/I, DEDB, and MSDB databases whose control blocks were not initialized or were in a stopped state when IMS failed. The names of DL/I databases you need to recover are also shown.

After the next IMS cold start, and before running application programs, see this list to stop the listed DL/I databases and recover them with the IMS provided utilities.

The following figure shows an example of the Database Status list. Table 1 lists the status codes and the required actions. Be sure to perform the recommended operations completely to ensure data integrity.

Figure 1. Database Status list

IMS DEDB FAST RECOVERY V2R2       --- DATA BASE STATUS LIST                             TIME  15:03:00   DATE   9/05/2021    P -   1 
 
  DBD NAME  REASON1 REASON2   ERROR DD NAME                                                                                       
 
  DBDATA1   NOTINIT
  DBDATA2   NOTINIT
  DBDATA3           STOPPED
  DBFSAMD1  NOTINIT
  DBFSAMD2  NOTINIT
  DBFSAMD3  NOTINIT
  DEDBJN01  NOTINIT
  DEDB0002  NOTINIT
  DH41M502  NOTINIT
  DH41TS01          BKONEED
            IOTEEQE           DH41TS01
  DI21PART  NOTINIT
  DX41M502  NOTINIT
  HDAM0001  IOTEEQE RCVNEED   HDAMDD01 HDAMDD11
  HDAM0002  IOTEEQE RCVNEED   HDAMDD02
  HDAM0003  NOTINIT
  MSDBLM03  NOTINIT
  MSDBLM04  NOTINIT 
 
END OF REPORT

Report field descriptions

DBD NAME: The database name (DBD name, HALDB master name, or HALDB partition name).
REASON1: The database status code that does not require any special action. See the following table.
REASON2: The database status code that requires special action. See the following table.
ERROR DD NAME: The ddname of the data set that needs recovery.

The following table lists the status codes and the required actions.

Table 1. Status codes in the Database Status list
Status code		Database status	Required actions before the IMS cold start	Required actions after the IMS cold start
REASON1	REASON2	Database status	Required actions before the IMS cold start	Required actions after the IMS cold start
NOTINIT (see note)		The database control block was not initialized.	None.	Check that it is not used.
	STOPPED (see note)	The database was in a stopped state.	None.	Stop with the /STOP command.
	BKONEED	An update log did not reach a sync point.	Batch backout.	None.
IOTEEQE IOEEEQE	RCVNEED RCVNEED	The database contains the I/O toleration, write-error, user-specified, or PERM-specified EEQE and needs recovery before cold start because it is not protected by DBRC.	DB recovery.	None.
IOTEEQE IOEEEQE		The database contains the I/O toleration, write-error, user-specified, or PERM-specified EEQE. DBRC continues to protect the database by EEQE.	None.	DB recovery.
NORCVDB	RCVNEED	The database is defined as recovery not required, and the SLDS found in the log data set after the recovery start checkpoint was used by IMS DEDB Fast Recovery.	None.	Re-create the database if necessary.
IDTEEQE	NOT-DEL	In-doubt EEQE information remains undeleted. Or, the EEQE was not deleted because DBRC=N was specified.	None.	Delete all in-doubt EEQE information created by IMS in this DL/I database with the DBRC CHANGE.DBDS command. Make sure that the target DL/I database is deallocated from all IMS subsystems.
IDTEEQE	SYNC	IMS DEDB Fast Recovery processed the in-doubt EEQE of the database, and other IMS subsystems must be notified of the in-doubt EEQE.	If other active data-sharing IMS subsystems exist, deallocate the database from another IMS by using the /STOP command.	Restart the database in all IMS subsystems by using the /START command.
Note: The status codes NOTINIT and STOPPED apply to all databases. The other codes apply only to DL/I databases.