search cancel

Fastunload : SYSTEM COMPLETION CODE=878 REASON CODE=00000010 in PFU step

book

Article ID: 254390

calendar_today

Updated On:

Products

Fast Unload for DB2 for z/OS

Issue/Introduction

Unload jobs are generating these messages and abending:

06.00.24 JOB77771  WER999A GE8REP34,STEP0020,        -  UNSUCCESSFUL SORT 878 S REASON=00000010 ..........               
06.00.24 JOB77771  IDI0055E Fault Analyzer processing excluded because 8 meg of 31 bit storage is not currently available
06.00.24 JOB77771  IDI0135E Recovery fault recording terminating. Severe private storage shortage.                       
06.00.26 JOB77771  IEA995I SYMPTOM DUMP OUTPUT  494                                                                      
   494             SYSTEM COMPLETION CODE=878  REASON CODE=00000010  

The suggestion is to change the region parm to 0M as suggested in article "S878 abend in sort executing Fast Unload with ORDER BY syntax."

Is there anything that can be done system-wide to make this perform as it did before we applied the maintenance so we don't have to change the JCL for hundreds of jobs immediately? 

       

                                           

Environment

Release : 20.0

Component : Fast Unload for Db2 for Z/OS

Resolution

One workaround is to add a second line to the hlq.CDBAPARM(PFU) member as below:

SYSADM SETUP
ZIIP NO                   <---------------------


When the Fast Unload job is executed the message below will be seen:

PFU0002I - PROCESSING OF CA PARMLIB MEMBER "PFU" - BEGINNING                    
SYSADM SETUP                                                         
ZIIP NO


Note that this is just a circumvention until the JCL's are changed to provide a REGION specification within the jobcard.

The change to the PFU member will impact all users of PFU on that installation including any users operating on other subsystems that are using the same product libraries too. 

In the job sysout the following message may also be seen: 

PUT0911I - Overriding small region

This means that Fastunload(PFU) has identified that the region size was too small to run the utility. PFUhas changed the region size (REGION=nM) to one of the following minimum values based on the storage area:
6M for storage below the line
100M for storage above the line

(These values may change in the future, check the online error code documentation page above)

However , the S878 abend indicates that this was still not enough. 

Also likely to be true is there is no REGION parm on the jobcard or the step anywhere.

See also: : S878 abend in sort executing Fast Unload with ORDER BY syntax.

The bottom line is that there was no REGION= specification on either the JOBCARD or STEP.  When a REGION= 
was specified with an allowed allocation for the environment this corrected the S878 abend.

See also: Specify a JOB Statement

"Fast Unload cannot run when the region size is too small. If the specified region size is below the following minimum values, the value is changed to the minimum based on the storage area:
6M for storage below the line
100M for storage above the line"

"We recommend specifying REGION=0M to let the utility use as much storage as required. Verify with your systems programmer that user exits at your site are not restricting memory allocation for REGION=0M requests."

 

Additional Information

PUT0911I - Overriding small region

S878 abend in sort executing Fast Unload with ORDER BY syntax.

Specify a JOB Statement

ZIIP NO