DFS3733A FPE AREA OFFLINE RECOVERY TERMINATED ABNORMALLY FOR AREA=areaname (DD=ddname) REASON CODE=nn
Explanation
The offline database recovery for a DEDB failed.
The following nn values indicate the reason for
the failure:
- Code (dec)
- Meaning
- 00
- The area authorization module, DBFDBAU0, was not found in the IMS resident library.
- 04
- A DBRC call and FUNC=INIT failed.
- 08
- The area authorization failed.
- 12
- No data set1 DD statement specified in the JCL. If DBRC is used
and the Area is registered, the ddname specified in data set1 DD statement
must match the names registered in the ADS list of the target Area.
If DBRC is used, but the Area is not registered, or if DBRC is not used, the ddname specified in the data set1 DD statement must match the areaname.
- 16
- The area status conflicted with the requested recovery mode. The
area status does not match the requested recovery mode. For DEDB recovery,
the area must be in one of the following status:
- If in full recovery, the area must be in the recovery-needed status.
- If in track recovery, the area must be in the recovery-not-needed status and the data set must be available.
- 20
- Unable to open the ACB for the target data set.
- 24
- Unable to read the second control interval for the target data set.
- 28
- DBRC was not initialized for this region and was unable to authorize the area. If the system does not have DBRC, this message is issued.
- 36
- Unable to get the control interval size for the target data set. For DEDB track recovery, SHOWCB is issued to get the length of the CI for a later reading of the second CI, but it failed.
- 40
- Unable to change the VSAM control block (RPL). For DEDB track recovery, MODCB Is issued to set the relative byte address of the second control interval for reading, but it failed.
- 44
- An invalid data set name was issued. For a DEDB, the dsname specified in the data set1 DD statement of the Database Recovery utility must match the names registered in the ADS list of the target area.
- 48
- The RDJFCB macro failed. Check the IEC131I message.
- 52
- No ADS record is found in the DBRC RECON data set.
System action
The program terminates. For reason code 32, the system sets the data set unavailable status in the ADS list of the DBRC area record. The area status is set to the recovery-needed status if the data set is the last one in the area.
Programmer response
Respond based on the return code nn as
follows:
- Code (dec)
- Meaning
- 00
- Check if DBFDBAU0 exists in SDFSRESL.
- 04
- See the DBRC message related to this message and check it.
- 08
- Check the message related to the area authorization.
- 12
- First check to see if DBRC is used or not. (This can be done by
checking the DBRC positional parameter in the EXEC parameter or the
IMSCTRL DBRC parameter in the IMS system definition macro.)
If DBRC is used and the Area is registered, specify one of the ddnames of the ADS list in the data set1 DD statement. If DBRC is used, but the Area is not registered, or if DBRC is not used, specify the areaname in the data set1 DD statement then resubmit the job.
- 16
- Specify the correct recovery mode according to the area status in DBRC RECON data set and resubmit the job.
- 20
- Check the other message related to this message.
- 24
- Check other messages related to this message.
- 28
- Check if the system has DBRC.
- 32
- Recover the data set and the area if the area is in recovery-needed status.
- 36
- Rerun the job.
- 40
- Rerun the job.
- 44
- Specify the correct dsname in the data set1 DD statement and resubmit the job.
- 48
- Follow the operator response described in the IEC131I message.
- 52
- Print the DBRC RECON data set and check the ADS list of the named area. If there is not any ddname in the ADS list, register at least one ddname in the DBRC RECON data set using an INIT.ADS command. After the registration, recover the named area by a Database Recovery utility and rerun the job.