SYSVIEW z/OSMF job abends with EC6 REASON CODE=0000FD1D

Products

• SYSVIEW Performance Management

Issue/Introduction

Submitted job IZUD01UZ and it abended with

14.12.29 JOB20633  IEA995I SYMPTOM DUMP OUTPUT  292                                                                       
   292             SYSTEM COMPLETION CODE=EC6  REASON CODE=0000FD1D                                                       
   292              TIME=14.12.29  SEQ=00075  CPU=0000  ASID=0037                                                         
   292              PSW AT TIME OF ERROR  070C4000   922F2566  ILC 0  INTC 00                                             
   292                NO ACTIVE MODULE FOUND - PRIMARY NOT EQUAL TO HOME                                                  
   292                NAME=UNKNOWN                                                                                        
   292                DATA AT PSW  122F2560 - 1F001F11  05EF010E  EBECD300                                                

      :
      :
14.12.29 JOB20633  BPXP013I THREAD 12A5200000000000, IN PROCESS 50331859, WAS  293  
   293             TERMINATED BY SIGNAL SIGXCPU, DUE TO CPU TIME OUT.               
14.12.29 JOB20633  IEF450I LOWJA03S GIMUNZIP - ABEND=SEC6 U0000 REASON=0000FD1D  294
   294                     TIME=14.12.29                                            
14.12.29 JOB20633  -GIMUNZIP          *SEC6   409K  18317  1.309227  0.088622    3.5

 

Environment

Release : 17.0

Cause

The job exceeded the allowed CPU time.

Resolution

EC6 abends always involves OMVS in some manner.

The 0000FD1D reason code indicates that the job ran out of CPU time.

The OMVS message after the abend shows

BPXP013I THREAD 12A5200000000000, IN PROCESS 50331859, WAS  293  
   293             TERMINATED BY SIGNAL SIGXCPU, DUE TO CPU TIME OUT.  

The SIGXCPU is coming from OMVS and again, indicates  that the CPU time limit has been exceeded.

The JOB card shows  TIME=(1,10), which allows for 1 minute 10 seconds of CPU time.  

Changing the JOB card to contain TIME=1440 resolved the problem.

Additional Information

If changing the jobcard does not correct the problem, additional items to check would include

1) Does the Job card include the CLASS?  If not, check to ensure it is running in the correct class as that may be problematic depending on system configuration.

2) Check with your sysprog for potential causes.  One possibility would be to check the setting for MAXCPUTIME in the BPXPRMxx PARMLIB member or ACID settings. Note that these are not settings to be changed lightly.

3) Potentially helpful documentation:

IBM JCL reference for the TIME parameter

IBM doc for BPXP013I message

 

If the problem persists, please contact Sysview support.