ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

CA DELIVER U0878 ABEND

book

Article ID: 226362

calendar_today

Updated On:

Products

View

Issue/Introduction

On one of our sysplexs, we are receiving the following abend in our CA Deliver started task (RMOSTC) on several lpars. 

RMOSTC01  CA Deliver 14.0.02 is initialized                                     
RMOCPT13  CA Deliver daily cycle BEGINNING                                      
RMOSEP30  ********************************************                          
RMOSEP30  *                                          *                          
RMOSEP30  *   CA-DELIVER       (EXPRESS /JOB22908)   *                          
RMOSEP30  *   PRODUCT HAS ABENDED WITH CODE U0878    *                          
RMOSEP30  *   ***     RESTART PRODUCT ASAP     ***   *                          
RMOSEP30  *                                          *                          
RMOSEP30  ********************************************                          
IEF450I EXPRESS DELIVER EXPRESS - ABEND=S000 U0878 REASON=00000000              
IEF404I EXPRESS - ENDED - TIME=08.01.58                                         

Cause

Insufficient REGION specification for RMOSTC

Environment

Release : 14.0

Component : CA Deliver

Resolution

- SE reviewed the code to see where the U0878 is being issued from, and what this abend actually means, and replied as follows:

"The only place I can find us issuing a U0878 is in RMOSDIM and it is because of a GETMAIN failure (no storage available)".

- We observed that your RMOSTC JCL has :   //DELIVER EXEC PGM=RMOSTC,REGION=128M,TIME=1440

- We also observed that your CHECKPOINT file is allocated at the maximum 200Cyls, which raises the following questions...

a. Did you recently increase the size of the checkpoint file to 200 cyls?

b. When you did increase it, did you also increase the REGION=nnnn setting in the RMOSTC's at the same time?

 

** Received following feedback from customer **

Increasing the REGION size for our RMOSTC's fixed the problem.