Why does DBCBUPDT Abend with S0C1?

Document ID : KB000013480
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

When running the DBCBUPDT job (as per the HOLD Action for PTF RO90201), the UPDATE step Abends with
a S0C1 and generates the following messages:

 

 JOB35144  DB00101I - STARTED JOB-JHHDBUPD NUMBER-15261 CXX=DMSCXX   MUFNAME=DMSMUF
 JOB35144  DB00101I - STARTED JOB-JHHDBUPD NUMBER-15261 CXX=DMSCXX
 JOB35144  ICE046A 0 JHHDBUPD.UPDATE   SORT CAPACITY EXCEEDED - RECORD COUNT 8976298
 JOB35144  DB02405I - PXX START JHHDBUPD 15261 13(062) ADD##-650-    D-1 DBUTLTY RETIX
 JOB35144  DB02406I - PXX END - SORT IN LOAD/RETIX HAD AN ERROR
 JOB35144  DB10089I - DBUTLTY ABEND HANDLER DRIVEN - NO ACTION REQUIRED
 JOB35144  IEA995I SYMPTOM DUMP OUTPUT  135
           SYSTEM COMPLETION CODE=0C1  REASON CODE=00000001




 

 

Question:

Why does DBCBUPDT Abend with S0C1?

 

 

 

Environment:
z/OS DATACOM/AD - Files Data Base
Answer:

To resolve the DFSORT error, which is the cause of the Abend, increase the 'SORT=999999' parameter
value in the DBCBUPDT PROC, and then re-run the job.

 

Example: 

// PARM='|RETIX DBID=&DBID,OPTIMIZE=YES,SORT=99999999'

 

 

 

Additional Information: