Smart/RESTART SRSR005E RRS CALL SRRCMIT has failed with hexadecimal RC 0000012C.

Products

• Smart Restart

Issue/Introduction

Several Smart/RESTART jobs failed with the following messages:

SRSR005E - THE RRS CALL SRRCMIT HAS FAILED WITH HEXADECIMAL RETURN CODE IS    
0000012C
SRS086E - COMMIT CALL TO RESOURCE MANAGER HAS FAILED DURING CHECKPOINT. CANNOT
PROCEED                

The Smart/RESTART jobs were restarted and completed successfully with no modifications.

Resolution

Per the Smart/RESTART error message:

SRSR005E - THE RRS CALL SRRCMIT HAS FAILED WITH HEXADECIMAL RETURN CODE IS
0000012C                                                                  
 
The application issues a COMMIT request, Smart/RESTART passes this COMMIT to RRS
using a z/OS RRS service named ATRCMIT.  ATRCMIT fails with return code 12C (hex).

See the following IBM manual for description of this return code:
Resource recovery services (RRS) Return Codes

IBM documents x'12C' return code as follows:

Hexadecimal Return Code: 12C
Decimal Return Code:  300
Code: RR_BACKED_OUT

Meaning: Environmental error. The commit failed. The resource managers backed out the changes, 
returning the resources to the values they had before the UR was processed.

Action: Same as the action for return code 65 (101).

One action for return code 65 (in that same manual) is: "Abnormally end the application because the resource manager 
will not allow any further changes to the resource until the situation is resolved."

After getting return code 12C from SRRCMIT, Smart/RESTART follows the IBM recommendation and terminates the job step abnormally:

+SRS086E - COMMIT CALL TO RESOURCE MANAGER HAS FAILED DURING CHECKPOINT. CANNOT
+PROCEED                                                                       
+SRSA67E - AN UNSUCCESSFUL CHECKPOINT OCCURRED. ABENDING IMMEDIATELY           

As the job restart was successful, this indicates by the time that you had re-submitted the failed job step, a problem 
that was causing the z/OS Resource Manager to fail (that COMMIT request) was resolved.

Contact your system programmers to examine RRS log around the time of the failed job step.

Typically, there is a participating resource manager in RRS, like MQ for example, that falls behind of another 
Resource Manager (like Db2) and this causes for z/OS RRS to halt a current unit of work.