IRO7302E RPCR phase status, RC=return code, RSN=reason code, ERROR: error

Explanation

This message indicates that an error was detected in the Recovery Point Create command processing during the phase listed. The phase status, return code, reason code and error are displayed in the message. For more information on the return and reason codes, see the IMS System Programming API Reference. Valid values for status are:
WARNING
RPCR encountered a warning condition. Some RPCR processes were successful while others may have failed. This is specified when RC=4.
FAILED
RPCR encountered an error which has prevented RPCR from completing successfully. This is specified when RC=8.
ERROR
RPCR encountered a severe error which has prevented RPCR from completing successfully. This is specified when RC=10.
TRACE
RPCR encountered an error situation and has created trace entries in the TRACE report which can be used to diagnose the problem. This is specified when RC=14.
When the return code is 04, 08 or 10, the reason for the error will be shown in the error field. The following table shows the reason code and the associated error value. When the return code is 14, then an error was encountered and internal trace entries were created to assist in determining the cause for the error. In this case, additional messages will also be issued indicating the error that occurred.

The following are valid values for error:

Table 1. Valid values for error

Reason code

Error

Description

00000032

INVALID TOKEN FOR FUNCTION

Invalid token passed to RPCR. Contact IBM® Software Support.

00000033

TOKEN NOT FOR SAME TCB

Invalid token passed to RPCR. Contact IBM Software Support.

00000034

UNABLE TO JOIN XCF GROUP

An attempt to join the XCF group for TOSI has failed. Ensure that the correct XCF group is specified in the RECONID record.

00000064

TARGET SYSTEM NOT AVAILABLE

An attempt to issue an IMS command against one or more target IMS systems has failed. Ensure that the IMS system is still active.

00000065

UNABLE TO OBTAIN RECON INFO

RPCR was unable to access the RECON data sets to obtain RECON information. Review the joblog for additional messages indicating the specific error.

00000066

UNABLE TO GET ONLINE DB STATUS

RPCR was unable to access the RECON data sets to obtain database information. Review the joblog for additional messages indicating the specific error.

00000067

UNABLE TO SWITCH LOG

RPCR was unable to complete the /SWI OLDS command processing. Review the joblog and the IMS messages for additional messages indicating the specific error.

00000068

UNABLE TO DBR A DB

RPCR was unable to DBR one or more databases. Review the joblog and the IMS messages for additional messages indicating the specific error.

00000069

UNABLE TO DBD A DB

RPCR was unable to DBD one or more databases. Review the joblog and the IMS messages for additional messages indicating the specific error.

0000006A

UNABLE TO START DB

RPCR was unable to start one or more databases. Review the joblog and the IMS messages for additional messages indicating the specific error.

0000006B

OPTIONS CONFLICT WITH DB TYPE

The RPCR options specified conflict with database type. Contact IBM software support.

0000006C

GETMAIN REQUEST FAILED

Unable to acquire storage. Ensure that the region size for the Extended Functions job is adequate.

0000006D

NAME TOKEN SERVICES FAILED

An error was encountered using MVS name token services. Contact IBM Software Support.

0000006E

UNABLE TO LOAD PROGRAM

RPCR was unable to load a required program. Ensure that Extended Functions has been correctly installed and all required load modules are include in the JOBLIB or STEPLIB.

0000006F

DYNAMIC ALLOCATION FAILED

Dynamic allocation failed for one or more database data sets. Review the joblog for details on the specific data set. This normally indicates that some job or user outside of IMS has the data set in use.

00000070

UNABLE TO LOCATE SUBTASK SVCS

Unable to locate subtask services. Contact IBM Software Support.

00000071

SVCS NOT AVAILABLE FOR SUBTASK

Subtask services are not available. Contact IBM Software Support.

00000072

ERROR STARTING SERVICE SUBTASK

Unable to start the subtask services. Contact IBM Software Support.

00000073

IMS ENVIRONMENTAL ERROR

RPCR encountered an error within the IMS environment. Contact IBM Software Support.

00000074

NOT APF AUTHORIZED

The RPCR program is not running in an APF authorized environment. Ensure that the load libraries in the JOBLIB or STEPLIB are APF authorized.

00000075

MISSING IMS DD

The specific RPCR options specified require the IMS DD to be specified. Add the appropriate IMS DD concatenation.

00000076

INCORRECT DSNAME FOR RECON

The data set name associated with the RECON being accessed does not match the data set name passed to RPCR. Ensure that the same RECON data sets are accessed by the IMS Database Recovery Facility Extended Functions job and the online IMS system.

00000077

DB IN USE FOR TIMEOUT DURATION

One or more databases were in use for the timeout duration and RPCR failed. If PARTIAL(Y) was specified, some databases may have succeeded. If PARTIAL(N) was specified, then RPCR failed.

00000078

DB NOT PROCESSED, PARTIAL(N)

One or more databases were in use for the timeout duration and PARTIAL(N) was specified. All other databases in the list have been skipped.

00000096

DB IS NOT REGISTERED

One or more databases passed to RPCR were not registered to DBRC. Ensure all databases are registered.

000000C8

DB TYPE IS UNSUPPORTED

The database type is either unsupported by RPCR or cannot be determined.

000000C9

UNABLE TO LOCATE DBD

RPCR could not locate the DBD in the IMS DD concatenation. Ensure the correct blocks are located in the IMS DD concatenation.

000000CA

UNABLE TO LOCATE PART INFO

RPCR could not locate information for a HALDB partition. Ensure the correct blocks are located in the IMS DD concatenation.

000000CB

DUPLICATE DBD/PART IN DBLIST

A duplicate database or partition was passed to RPCR in the DBLIST. Contact IBM.

000000CC

ALLOCATED AFTER DBR

RPCR has determined that one or more databases processed was allocated after it was DBR'd. The RPCR process must fail because it cannot ensure that a correct recovery point was created.

000000CD

CMDTYPE(DBD) NOT VALID FOR DB

This is an internal error. Contact IBM Software Support.

000000CE

DB TYPE NOT PROVIDED

This is an internal error. Contact IBM Software Support.

000000CF

DB DSLIST NOT PROVIDED

This is an internal error. Contact IBM Software Support.

000000D0

DB IS CURRENTLY BEING USED

One or more databases were in use for the timeout duration and failed RPCR.

System action

If the status is WARNING, then RPCR processing may have worked for some databases and failed for others. Otherwise, RPCR processing terminates.

System programmer response

Review the RPTRPCR report and other messages in the joblog to determine the outcome of RPCR.

Module

IROPRPCI, IROPRPCP