DEDB Area Status list

For all DEDB areas that were open when IMS failed, the DEDB Area Status list describes the status of the areas after IMS DEDB Fast Recovery execution. The list provides the names of the available area data sets, the status of the area at the time when IMS failed, and the user actions required for each DEDB area.

The following figure shows an example of the DEDB Area Status list.

Figure 1. DEDB Area Status list 
IMS DEDB FAST RECOVERY V2R2       --- DEDB AREA STATUS LIST                             TIME  15:03:00   DATE   9/05/2021    P -   1

AREA NAME OPT  STATUS               AVAILABLE DATA SET AND CF STRUCTURE                                                 

*DB21AR0                            DB21AR01
*DB21AR1                            DB21AR11
 DB22AR2  V    RCVNEED  (NONRCV)   (DB22AR21) (DB22AR22) (DB22AR23)
 DB23AR1  VO                        DB23AR11
 DB23AR2       SYNC     (IOTEEQE)   DB23AR21   DB23AR22  (DB23AR23)
               IOERR
 DB24AR1       SYNC     (IDTEEQE)   DB24AR11
 DB24AR2       SYNC     (IOTEEQE)   DB24AR21   DB24AR22   DB24AR23
 DB24AR3  VO   RCVNEED  (CFCONER)   STR1= RDODDB24AR3STR1  STR2=
                                   (DB24AR31)
 DB30AR0  VOL  RCVNEED  (CFCONER)   STR1=(V$$$RDODMAS_512 )
                                   (DB30AR01)
 DB30AR1  VOL  RCVNEED  (CFNOTDF)   STR1=(V$$$RDODMAS_512 )
                                   (DB30AR11) (DB30AR12)
 DB30AR2  VOL  RCVNEED  (CFALCER)   STR1=(V$$$RDODMAS_2048)
                                   (DB30AR21)
 DB30AR3  VOL  RCVNEED  (CFCONLS)   STR1=(V$$$RDODMAS_2048)
                                   (DB30AR31) (DB30AR32) (DB30AR33)
 DB30AR4  VOL  RCVNEED  (CFREDER)   STR1=(V$$$RDODMAS_2048)
                                   (DB30AR41)

END OF REPORT

Report field descriptions

The names of all DEDB areas that were open when IMS failed are shown in the AREA NAME column. In the case of the user-recoverable DEDB, an asterisk (*) is shown as the first character in the AREA NAME column.

The OPT column shows the following VSO options (VSO and PRELOAD) and the PREOPEN option for the area used by IMS:

V
The area was a VSO area when IMS failed.
O
The area was preopened when IMS failed.
L
The area was preloaded when IMS failed. L always appears with both V and O, because the preloaded area must be a preopened VSO area.

Areas not listed were not open when IMS failed. Areas not open but in a stopped state are listed with a status code of STOPPED, NOPENED.

The data set status is shown only when the area requires user action to ensure database integrity. The status codes of IOERR, REORG, CREATE, HSSP, DELETE, SCAN, SYNC, and INT.STOP are shown only for the areas defined as the DEDB block-level data-sharing area. The status FORCE OPEN, SYNC (IOTEEQE), and SYNC (IDTEEQE) might be shown for a non-block-level data-sharing area.

If DBRC needs recovery, and you run IMS DEDB Fast Recovery with DBRC=N, you use this list to recover the DBRC RECON data set.

Table 1 shows the user action required for each status.

The data set name associated with each area is listed under AVAILABLE DATA SET AND CF STRUCTURE. Data sets whose names are in parentheses are not available.

If the failed IMS uses block-level data-sharing VSO areas, the structure name related to each area is listed under AVAILABLE DATA SET AND CF STRUCTURE. If an area is not in RETRY status and structure names related to the area are not in parentheses, the structure is disconnected normally. That means, if there are any other connectors, the structure remains. If there are no other connectors, the structure is deleted from CF when IMS DEDB Fast Recovery is disconnected. If an area is in RETRY status, and the structure names related to the area are not in parentheses, the failed-persistent connection of the failed IMS is maintained, and the structure remains.

If a structure name is in parentheses, the cause might be one of the following reasons:

  • The area is VUNloaded.

    If an area is not in RCVNEED status and all the structure names related to the area are in parentheses, the area is VUNloaded. There is no structure related to the area.

  • The structure is deleted because of connection loss.

    If an area is not in RCVNEED or RETRY status and one of the two structure names is in parentheses, a connection is lost for the structure. The structure that lost connection to an IMS is disconnected normally and deleted by another IMS that maintains connection with the structure or by IMS DEDB Fast Recovery. The other structure is recovered successfully and disconnected normally.

    If an area is in RETRY status and one of the two structure names related to the area is in parentheses, the connection for the structure is lost. The structure that lost the connection to an IMS is disconnected normally and deleted by another IMS that maintains connection with the structure or by IMS DEDB Fast Recovery. For the other structure, the failed-persistent connection of the failed IMS is maintained, and the structure remains.

  • The area is unavailable, and the related structures cannot be used.

    If an area is in RCVNEED status and all structure names related to the area are in parentheses, the structures related to the area are disconnected normally.

    Note: Normal disconnection of a structure means that the failed persistent connection at IMS failure is removed.
Table 1. Status codes in the DEDB Area Status list
Status code Status of area or area data set Actions required before the IMS cold start Actions required after the IMS cold start
STOPPED,
NOPENED 		The area was in stopped state. None. Stop the area with the /STOP command.
RCVNEED
RCVNEED (CFreason)		 The area needs recovery. CFreason indicates the cause of the access error of CF structure during the recovery of block-level data-sharing VSO areas. For the CFreason, see the note to this table. DB recovery (can be executed after the IMS cold start if the status is registered to DBRC). None.
RCVNEED (NONRCV) The area needs recovery. The area is a nonrecoverable DEDB area, and any CI updates for the area are compromised by the failure of IMS. If possible, IMS DEDB Fast Recovery registers the area to DBRC as recovery needed. DB has to be restored from an image copy, a repro, or some other source, because the area has no DB change logs in OLDS/SLDS. (This action can be taken after the IMS cold start if the status is registered to DBRC). None.
IOERR There was an error in one of the data sets in this area during the IMS DEDB Fast Recovery processing. Other IMS subsystems must be notified of it. If other active data-sharing IMS subsystems exist, deallocate the area from another IMS by using the /STOP command. Restart the area in all IMS subsystems (except for areas shown as INT.STOP(AREA)) by using the /START command.

For the areas shown as IOERR, INT.STOP(ADS) or CREATE, re-create unavailable area data sets by using the Area Data Set Create utility.

INT.STOP(AREA) The area is now in stopped state, and other IMS subsystems must be notified.
INT.STOP(ADS) Several area data sets in the area are now in stopped state, and other IMS subsystems must be notified.
CREATE The Area Data Set Create utility was being processed for the area.
REORG The Direct Reorganization utility was being processed for the area.
HSSP An application program using the HSSP function was being processed for the area.
SCAN The Scan utility was being processed for the area.
DELETE The Delete utility was being processed for the area. Other IMS subsystems must be notified or the status must be reset.
SYNC(AREA) Other IMS subsystems were being notified of the area status.
SYNC(ADS) Other IMS subsystems were being notified of the area data set status in the area. They must be notified again.
SYNC(IOTEEQE)
SYNC(IDTEEQE)
SYNC(WRTEEQE)		 IMS DEDB Fast Recovery processed the I/O toleration EEQE(IOTEEQE), the in-doubt EEQE(IDTEEQE), or the write error EEQE(WRTEEQE) of the area. Other IMS subsystems must be notified of the EEQE.
FORCE OPEN The area containing the I/O toleration EEQE was forced to open. N/A N/A
IOTEEQE NOT DELETE
IDTEEQE NOT DELETE
WRTEEQE NOT DELETE		 I/O toleration EEQE information remains undeleted. In-doubt EEQE information remains undeleted. Or, the EEQE was not deleted because DBRC=N was specified. None. Delete all EEQE information created by IMS in this area with the DBRC CHANGE.DBDS command. Make sure that the target area is deallocated from all IMS subsystems.
RETRY (CFreason) The block-level data-sharing VSO area needs another trial of IMS DEDB Fast Recovery. CFreason identifies the cause of the connectivity error of the CF structure. For CFreason, see the note to this table. Remove the cause of the problem and execute IMS DEDB Fast Recovery for the area again. N/A
CF DISCON FAILED An error was detected during disconnection from the block-level data-sharing VSO area. The recovery process for the area has been completed. N/A N/A
Notes:
  • CFreason shows one of the following reasons:
    CFCONER
    Connection error
    CFNOTDF
    No definition
    CFALCER
    No structure
    CFCONLS
    Connection loss
    CFREDER
    Read error
    CFDELER
    Entry deletion error
    CFCASER
    Casting out error

    An error message is shown for each error. See the explanation of the message.

  • If there is no other connector for a block-level data-sharing VSO area and the recovery is completed successfully by IMS DEDB Fast Recovery, the structures related to the area are deleted from CF. If IMS DEDB Fast Recovery runs for the area again, IMS DEDB Fast Recovery recognizes that a structure that should exist does not actually exist. Although the CFRET=Y execution generates RETRY (CFALCER) as a status code, you do not have to run IMS DEDB Fast Recovery again. The CFRET=N execution generates RCVNEED (CFALCER) as a status code. Be careful with the second or later execution.