Desktop productivity for business analysts and programmers

SEC6 Abend in Mainframe job whil sorting huge SAS dataset

Reply
New Contributor
Posts: 3

SEC6 Abend in Mainframe job whil sorting huge SAS dataset

SEC6 Abend in Mainframe job whil sorting huge SAS dataset

The address space has used a maximum of 1884K below the line and 26888K ab

$HASP375 COGVVWUS ESTIMATE EXCEEDED BY           1,250,000  LINES         

Have around 50 temporary datasets in the program.

Esteemed Advisor
Posts: 6,698

Re: SEC6 Abend in Mainframe job whil sorting huge SAS dataset

This:

http://support.sas.com/kb/17/550.html

could be helpful.

---------------------------------------------------------------------------------------------
Maxims of Maximally Efficient SAS Programmers
New Contributor
Posts: 3

Re: SEC6 Abend in Mainframe job whil sorting huge SAS dataset

This is occuring for me in Mainframe SAS below are system codes i get.

SYSTEM COMPLETION CODE=EC6  REASON CODE=0000FD1D

01.19.52 JOB27249  BPXP013I THREAD 1709580000000000, IN PROCESS  50332167, WAS  193 

   193             TERMINATED BY SIGNAL SIGXCPU, DUE TO CPU TIME OUT.         

Esteemed Advisor
Posts: 6,698

Re: SEC6 Abend in Mainframe job whil sorting huge SAS dataset

Looks like you simply run out of time

IBM Abend EC6 reason code 0000FD1D MQ channel initiator job fails - United States

See

IBM Knowledge Center

I found the first link by googling "SYSTEM COMPLETION CODE=EC6  REASON CODE=0000FD1D"

---------------------------------------------------------------------------------------------
Maxims of Maximally Efficient SAS Programmers
Valued Guide
Posts: 3,206

Re: SEC6 Abend in Mainframe job whil sorting huge SAS dataset

Normally there is 322 abend code when there is a timeout on the exec time parameters (SMF MVS managed). The EC6 is coming from a different one Unix service within mainframe.   
IBM Knowledge Center z/OS MVS System codes.    The FD1D is telling there was somebody giving a signal to the task and make a dump. That may be an reaction to some other problem like looping or suspect to be looping.
The 193 CPU time out is telling there is timelimit being passed. That must be one in the open segment setting. (search those words)

33650 - An error occurs when you use SAS/CONNECT® through a spawner to download data from the z/OS e...

42735 - Support for the RACF profile BPX.DEFAULT.USER is dropped in z/OS 2.1

http://support.sas.com/documentation/installcenter/en/ikfdtnmvscg/66194/PDF/default/config.pdf

---->-- ja karman --<-----
Ask a Question
Discussion stats
  • 4 replies
  • 1688 views
  • 0 likes
  • 3 in conversation