DFS030I DBRC VERUOR REQUEST FAILED, RC=yy
or
DBRC REQUEST FAILED, REASON=xx, RC=yy
or
DBRC SIGNOFF REQUEST FAILED xx, RC=yy
or
DBRC SAVUOR REQUEST FAILED, RC=yy
or
DBRC UPDUOR REQUEST FAILED, RC=yy
Explanation
The first form of the message is issued by modules DFSDBAU0, DFSDDUI0, DFSDLOC0, and DBFPICT0. The second form of the message is issued by module DFSPCCC0. The SAVUOR, UPDUOR and VERUOR versions of the message are issued by either DFSRBOI0, DFSDBDR0 or DFSST500.
The particular DBRC request with or without the reason code xx failed with a return code of yy.
To determine the cause of the failure indicated by the return code yy, see the DBRC request return codes information in IMS Version 15.3 Messages and Codes, Volume 4: IMS Component Codes.
The following reason codes indicate the xx value.
- Code (hex)
- Meaning
- 01
- A synchronization process or emergency restart backout process attempted to notify DBRC of a database backout failure. DBRC indicated that the database was not registered. If the database is not registered, neither process notifies DBRC, and the condition does not occur.
- 02
- A synchronization process or an emergency restart backout process attempted to notify DBRC of a database backout failure. DBRC indicated that the subsystem was not authorized to use the database. Because no changes to the database could have been made unless it was authorized, this condition should not have occurred.
- 03
- A database authorization call was made to DBRC. A return code X'0C', which indicated that the subsystem was not signed on to DBRC, was received upon return. This condition should not have occurred unless there was an error in the IMS subsystem initialization or in the DBRC.
- 05
- A sign-off call was made to DBRC while IMS was terminating. The return code indicated that either there was no subsystem entry found, that an internal error was encountered during the unauthorization process, that the subsystem entry was found but terminated abnormally, or that the recovery processing had been started.
- 06
- DBRC was called to unauthorize a database during DL/I close processing. The return code set by DBRC indicated that the database was not registered in the RECON data set. Because the unauthorization call is only issued if the database is registered to DBRC, an internal error has occurred.
- 07
- DBRC was called to unauthorize a database during DL/I close processing. The return code set by DBRC indicated that the subsystem was not registered in the RECON data set. Because the subsystem was registered when authorization for the database was obtained, an internal error has occurred.
- 08
- DBRC was called to unauthorize the database during DL/I close
processing. The return code from DBRC indicated that the subsystem
did not have authorization for the database. Because authorization
for the database was obtained before the database was opened, this
condition should not occur.
Abend 3275 is issued if DBRC returns this code and the system is not being emergency restarted. During emergency restart, this condition might exist if the /DBRECOVERY command is run for the HALDB master before the /ERESTART command is run.
- 09
- DBRC was called to unauthorize a database during DL/I close processing. The return code set by DBRC indicated that an internal DBRC error occurred during or subsequent to the authorization process, or that the unauthorization process was unable to produce a new authorization state for the database. See the message issued by DBRC before the abend for further explanation.
- 0A
- The database open call to DBRC was issued during DL/I open processing. The return code from DBRC indicated that the database being processed was not registered to DBRC. This situation might not occur, because DBRC is not called during open processing unless authorization for the database was previously obtained from DBRC.
- 0B
- The return code set by DBRC when the database open call was processed indicated that the subsystem was not registered to DBRC. This situation should not occur, because DBRC is called during DL/I open processing only if the subsystem previously obtained authorization for the database, at which time it must be registered to DBRC.
- 0C
- The database open call to DBRC was issued during DL/I open processing. The return code from DBRC indicated that the subsystem did not have authorization for the database. This situation should not occur because the open call to DBRC is issued only if authorization was obtained for the database before DL/I open processing was started.
- 0D
- The database open call to DBRC was issued during DL/I open processing. The return code from DBRC indicated that an internal DBRC error was detected.
- 0E
- The DBRC call to reverify the data sets failed.
- 0F
- DBRC received an end HSSP Image Copy call during image copy termination. The DBRC return code indicates that the image copy record specified was not found. The begin HSSP Image Copy call should create that image copy record.
- 10
- DBRC received an end HSSP Image Copy call during image copy termination. The DBRC return code indicates that the database/area was not registered in the RECON data set. HSSP Image Copy can only process a registered database/area.
- 20
- DBRC received an end HSSP Image Copy call during image copy termination. The DBRC return code indicates that the end HSSP Image Copy call was already made for this image copy processing. Abend 3275 is issued if DBRC returns this code and the system is not being emergency restarted.
- 30
- DBRC received an end HSSP Image Copy call during Image Copy termination. The DBRC return code indicates that an internal DBRC error occurred.
- 40
- DBRC received an end HSSP Image Copy call during image copy termination. The DBRC return code indicates that an invalid parameter was found.
- 53
- DBRC was called to create a REORG record for the database. The return code from DBRC indicates there was a problem processing the request. For additional information about return codes from the RELOAD Utility, and to determine the cause of the failure, see the DBRC request return codes information in IMS Version 15.3 Messages and Codes, Volume 4: IMS Component Codes.
- 54
- DBRC was called to create a REORG record for the database. The return code, X'04', indicated that the database was not registered.
- 55
- DBRC was called to create a REORG record for the database. The return code, X'08', indicated there was an I/O error reading the RECON data set or a DD statement was not included for a data set being reorganized.
- 56
- An invalid partition reorganization number was passed on the notify reorganization call to DBRC.
System action
IMS terminates abnormally with abend 3275.
Programmer response
Check the return code and take appropriate action.