5C4 ExplanationA call for a resource recovery services (RRS) service
was issued in an incorrect environment. Register 15 contains a hexadecimal
reason code. - Code
- Explanation
- xxxx000B
- RRS was unable to obtain a required storage area. The storage
area could be in CSA.
- xxxx0029
- RRS was unable to finish Internal Cold Start processing.
- 00010000
- For a call to the Delete_UR_Interest service, the parameters are
not in the primary address space.
- 00010001
- For a call to the Delete_UR_Interest service, the parameters are
not addressable.
- 00020000
- For a call to the Express_UR_Interest service, the parameters
are not in the primary address space.
- 00020001
- For a call to the Express_UR_Interest service, the parameters
are not addressable.
- 00030000
- For a call to the Begin_Restart service, the parameters are not
in the primary address space.
- 00030001
- For a call to the Begin_Restart service, the parameters are not
addressable.
- 00040000
- For a call to the End_Restart service, the parameters are not
in the primary address space.
- 00040001
- For a call to the End_Restart service, the parameters are not
addressable.
- 00050000
- For a call to the Retrieve_Log_Name service, the parameters are
not in the primary address space.
- 00050001
- For a call to the Retrieve_Log_Name service, the parameters are
not addressable.
- 00060000
- For a call to the Retrieve_UR_Interest service, the parameters
are not in the primary address space.
- 00060001
- For a call to the Retrieve_UR_Interest service, the parameters
are not addressable.
- 00070000
- For a call to the Process_Interest service, the parameters are
not in the primary address space.
- 00070001
- For a call to the Process_Interest service, the parameters are
not addressable.
- 00080000
- For a call to the Set_Log_Name service, the parameters are not
in the primary address space.
- 00080001
- For a call to the Set_Log_Name service, the parameters are not
addressable.
- 00090000
- For a call to the Post_Deferred_UR_Exit routine service, the parameters
are not in the primary address space.
- 00090001
- For a call to the Post_Deferred_UR_Exit routine service, the parameters
are not addressable.
- 000B0000
- For a call to the Retrieve_Interest_Data service, the parameters
are not in the primary address space.
- 000B0001
- For a call to the Retrieve_Interest_Data service, the parameters
are not addressable.
- 000C0000
- For a call to the Retrieve_UR_Data service, the parameters are
not in the primary address space.
- 000C0001
- For a call to the Retrieve_UR_Data service, the parameters are
not addressable.
- 000D0000
- For a call to the Retrieve_Side_Information service, the parameters
are not in the primary address space.
- 000D0001
- For a call to the Retrieve_Side_Information service, the parameters
are not addressable.
- 000E0000
- For a call to the Retrieve_Work_Identifier service, the parameters
are not in the primary address space.
- 000E0001
- For a call to the Retrieve_Work_Identifier service, the parameters
are not addressable.
- 000F0000
- For a call to the Change_Interest_Type service, the parameters
are not in the primary address space.
- 000F0001
- For a call to the Change_Interest_Type service, the parameters
are not addressable.
- 00100000
- For a call to the Set_Persistent_Interest_Data service, the parameters
are not in the primary address space.
- 00100001
- For a call to the Set_Persistent_Interest_Data service, the parameters
are not addressable.
- 00110000
- For a call to the Retain_Interest service, the parameters are
not in the primary address space.
- 00110001
- For a call to the Retain_Interest service, the parameters are
not addressable.
- 00120000
- For a call to the Set_Sync-point_Controls service, the parameters
are not in the primary address space.
- 00120001
- For a call to the Set_Sync-point_Controls service, the parameters
are not addressable.
- 00130000
- For a call to the Set_Side_Information service, the parameters
are not in the primary address space.
- 00130001
- For a call to the Set_Side_Information service, the parameters
are not addressable.
- 00140000
- For a call to the Set_Work_Identifier service, the parameters
are not in the primary address space.
- 00140001
- For a call to the Set_Work_Identifier service, the parameters
are not addressable.
- 00150000
- For a call to the Application_Backout_UR service, the parameters
are not in the primary address space.
- 00150001
- For a call to the Application_Backout_UR service, the parameters
are not addressable.
- 00150002
- For a call to the Application_Backout_UR service, the caller is
disabled.
- 00150003
- The program that called the Application_Backout_UR service is
holding one or more locks; no locks must be held.
- 00150004
- The program called the Application_Backout_UR service. The system
release does not support this service.
- 00150005
- The program that called the Application_Backout_UR service is
in an unsupported ASC mode; the mode must be primary.
- 00150006
- The program called the Application_Backout_UR service. The UR
is either:
- not in a valid state for the service call. The UR state must be in-reset or in-flight;
or,
- in local transaction mode. This service is only valid for a UR
in global transaction mode.
- 00150007
- The program called the Application_Backout_UR service. The service
encountered an unexpected error. RRS writes a logrec record and takes
a dump.
- 00150009
- The program that called the Application_Backout_UR service is
not in task mode, which is required.
- 00150010
- The program called the Application_Backout_UR service, but the
current UR (the UR being processed) encountered an unexpected error,
and RRS cannot continue to process the UR.
- 00150011
- The program called the Application_Backout_UR service, but the
service encountered an unexpected error from a context services service.
- 00160000
- For a call to the Application_Commit_UR service, the parameters
are not in the primary address space.
- 00160001
- For a call to the Application_Commit_UR service, the parameters
are not addressable.
- 00160002
- The program that called the Application_Commit_UR service is disabled;
the interrupt status must be enabled for I/O and external interrupts.
- 00160003
- The program that called the Application_Commit_UR service is holding
one or more locks; no locks must be held.
- 00160004
- The program called the Application_Commit_UR service. The system
release does not support this service.
- 00160005
- The program that called the Application_Commit_UR service is in
an unsupported ASC mode; the mode must be primary.
- 00160006
- The program called the Application_Commit_UR service. The UR is
either:
- not in a valid state for the service call. The UR state must be in-reset or in-flight;
or,
- in local transaction mode. This service is only valid for a UR
in global transaction mode.
- 00160007
- The program called the Application_Commit_UR service. The service
encountered an unexpected error. RRS writes a logrec record and takes
a dump.
- 00160008
- An application program called the Application_Commit_UR service
but a resource manager has already taken the server distributed sync-point
resource manager role (SDSRM), and only the SDSRM can initiate a syncpoint
operation.
- 00160009
- The program that called the Application_Commit_UR service is not
in task mode, which is required.
- 00160010
- The program called the Application_Commit_UR service, but the
current UR (the UR being processed) encountered an unexpected error,
and RRS cannot continue to process the UR.
- 00160011
- The program called the Application_Commit_UR service, but the
service encountered an unexpected error from a context services service.
- 00160012
- The program called the Application_Commit_UR service, but the
current UR (the UR being processed) is a child cascaded UR. Only the
top-level UR of a cascaded UR family can be committed.
- 00170000
- For a call to the Backout_UR service, the parameters are not in
the primary address space.
- 00170001
- For a call to the Backout_UR service, the parameters are not addressable.
- 00180000
- For a call to the Commit_UR service, the parameters are not in
the primary address space.
- 00180001
- For a call to the Commit_UR service, the parameters are not addressable.
- 001A0000
- For a call to the Backout_Agent_UR service, the parameters are
not in the primary address space.
- 001A0001
- For a call to the Backout_Agent_UR service, the parameters are
not addressable.
- 001B0000
- For a call to the Commit_Agent_UR service, the parameters are
not in the primary address space.
- 001B0001
- For a call to the Commit_Agent_UR service, the parameters are
not addressable.
- 001C0000
- For a call to the Forget_Agent_UR service, the parameters are
not in the primary address space.
- 001C0001
- For a call to the Forget_Agent_UR service, the parameters are
not addressable.
- 001D0000
- For a call to the Prepare_Agent_UR service, the parameters are
not in the primary address space.
- 001D0001
- For a call to the Prepare_Agent_UR service, the parameters are
not addressable.
- 001F0000
- For a call to the Create_Cascaded_UR service, the parameters passed
by the caller are not in the primary address space.
- 001F0001
- For a call to the Create_Cascaded_UR service, the parameters passed
by the caller are not addressable.
- 00200000
- For a call to the Set_Post_Sync_PET service, the parameters passed
by the caller are not in the primary address space.
- 00200001
- For a call to the Set_Post_Sync_PET service, the parameters passed
by the caller are not addressable.
- 00210000
- For a call to the Delete_Post_Sync_PET service, the parameters
passed by the caller are not in the primary address space.
- 00210001
- For a call to the Delete_Post_Sync_PET service, the parameters
passed by the caller are not addressable.
- 00220000
- For a call to the Delegate_Commit_Agent_UR service, the parameters
passed by the caller are not in the primary address space.
- 00220001
- For a call to the Delegate_Commit_Agent_UR service, the parameters
passed by the caller are not addressable.
- 00230000
- For a call to the Begin_Transaction service, the parameters passed
by the caller are not in the primary address space.
- 00230001
- For a call to the Begin_Transaction service, the parameters passed
by the caller are not addressable.
- 00240000
- For a call to the End_Transaction service, the parameters passed
by the caller are not in the primary address space.
- 00240001
- For a call to the End_Transaction service, the parameters passed
by the caller are not addressable.
- 00260000
- For a call to the Set_Environment service, the parameters passed
by the caller are not in the primary address space.
- 00260001
- For a call to the Set_Environment service, the parameters passed
by the caller are not addressable.
- 00270000
- For a call to the Retrieve_Environment service, the parameters
passed by the caller are not in the primary address space.
- 00270001
- For a call to the Retrieve_Environment service, the parameters
passed by the caller are not addressable.
- 01010005
- RRS WHEN CFS ARE DOWN
- 021F0001
- An RRS service was called, but the RRS service could not be processed
because the RRS address space was down.
- FFFF2222
- The SETRRS CANCEL command has cancelled RRS processing
System actionThe system rejects the service call. The system
abnormally ends the calling program.
Programmer responseFor most of the reason codes, check the
calling program for a probable coding error; correct the program and
rerun it.
For reason code X'xxxx000B', either enlarge
CSA or search problem reporting databases for a fix for the problem.
If no fix exists, contact the IBM® Support
Center and provide the dump.
For reason code
X'xxxx0029', save any dumps related to the problem and contact the IBM Support Center.
For reason
code X'00150004' or X'00160004', remove the calling
program from the system, and install it on a system that supports
RRS. Then rerun the program.
For reason code X'00150007' or X'00160007',
search problem reporting databases for a fix for the problem. If no
fix exists, obtain the related logrec record and dump, then contact IBM support.
For reason code X'00150010' or X'00160010',
check other diagnostic information to determine why RRS encountered
the error. To ensure resource consistency, you might need to intervene
manually.
For reason code X'00150011' or X'00160011',
check diagnostic information, such as the dump, from context services
to determine why the error occurred.
For reason code X'01010005',
check that coupling facilities are active.
For reason code X'FFFF2222',
no action is necessary.
For any other reason code, search problem
reporting databases for a fix for the problem. If no fix exists, save
any dump related to the problem and contact the IBM Support Center.
SourceResource recovery services (RRS)
|