Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

DFSORT abend - Call from SAS

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> DFSORT/ICETOOL
View previous topic :: :: View next topic  
Author Message
vasanthz

Global Moderator


Joined: 28 Aug 2007
Posts: 1491
Location: Chennai

PostPosted: Fri Apr 15, 2011 5:35 pm    Post subject: DFSORT abend - Call from SAS
Reply with quote

Hi,

We have a SAS sort step and SAS calls host sort(DFSORT) to perform sorting, during this step the job is failing with the below abend, the unusal thing is, this job runs fine once restarted without any changes made to the job.

Code:
SASLOG:
.ERROR: Sort did not complete successfully. See messages on the Job Console Log
.ERROR: Host sort cannot be used.                                               
.NOTE: The SAS System stopped processing this step because of errors.           
.NOTE: SAS set option OBS=0 and will continue to check statements. This may caus
.NOTE: There were 1978265 observations read from the data set WORK02.SMFXCQ00. 
.WARNING: The data set WORK01.SMFXCQ00 may be incomplete.  When this step was st
.         variables.                                                           
.ERROR: Expecting page 1650, got page -1 instead.               
.ERROR: Page validation error while reading WORK01.SMFXCQ00.DATA.
.ERROR: Expecting page 1, got page -1 instead.                   
.ERROR: Page validation error while reading WORK01.SMFXCQ00.DATA.
.ERROR: Expecting page 1, got page -1 instead.                   
.ERROR: Page validation error while reading WORK01.SMFXCQ00.DATA.
.ERROR: Expecting page 1, got page -1 instead.                   
.ERROR: Page validation error while reading WORK01.SMFXCQ00.DATA.


Code:
SYSOUT:
.ICE185A 0 AN S878  ABEND WAS ISSUED BY DFSORT, ANOTHER PROGRAM OR AN EXIT (PHASE S 3)


Could you please let me know the reason for this failure.
There was link which has a description of similar abend https://www-304.ibm.com/support/docview.wss?uid=swg1PK66166

but in our job it runs fine once restarted after abend, without any changes.
Back to top
View user's profile Send private message

expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Fri Apr 15, 2011 6:08 pm    Post subject:
Reply with quote

I have only experienced one problem with DFSORT under SAS, which with some fast and good help from Frank and Dave was quickly resolved.

Are you using predefined SORTWK DD statements.

If you are, then I suggest that you do not, but use
Code:
//DFSPARM DD *
  OPTION DYNALLOC=(,32)


The thing that took me ages to find was that SAS always invokes its own SORT routine before deciding that DFSORT should really be doing this, but then limits the number of SORTWK's that it will use. Limit of 6 or whatever your site options are set to.

To overcome this I changed the SORT OPTION - see below - to bypass the SAS intervention and go directly to DFSORT instead.
Code:
OPTIONS SORTPGM=SORT


I don't know if this is related to your problem but from the benefit of experience I'm happy to share with you.
Back to top
View user's profile Send private message
Frank Yaeger

DFSORT Moderator


Joined: 15 Feb 2005
Posts: 7130
Location: San Jose, CA

PostPosted: Fri Apr 15, 2011 9:39 pm    Post subject:
Reply with quote

Vasanth,

S878 is a storage abend. Here's a link to the Explanation:

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/iea2h7a0/2.513?ACTION=MATCHES&REQUEST=878&TYPE=FUZZY&SHELF=&DT=20090604035642&CASE=&searchTopic=TOPIC&searchText=TEXT&searchIndex=INDEX&rank=RANK&ScrollTOP=FIRSTHIT#FIRSTHIT

The link you gave is for a problem with DB2, not SAS, so it's probably not relevant.

It's impossible to tell what the actual problem is without much more information (such as the complete JES log). It may have been a temporary system storage shortage of some kind that disappeared by the time you reran the job.

Expat's suggestions may work.

If not, you'd need to open a problem with IBM so the relevant doc could be collected and analyzed.
Back to top
View user's profile Send private message
vasanthz

Global Moderator


Joined: 28 Aug 2007
Posts: 1491
Location: Chennai

PostPosted: Mon Apr 18, 2011 12:23 pm    Post subject:
Reply with quote

Quote:

I don't know if this is related to your problem but from the benefit of experience I'm happy to share with you.

thanks icon_biggrin.gif

Quote:
It may have been a temporary system storage shortage of some kind that disappeared by the time you reran the job.

This abend happens like 3 times a week. So I guess its not a one off issue.


The JCL is generated by several SAS macros(30 or more), its a product by CA which generates the JCL and I think macros are overused to the point where we dont get to see actual SAS data and proc statements or JCL statements.

I would check if the SORTWK DD is hardcoded in the generated JCL and remove them and add the DFSPARM and check out if it helps.

Thanks Expat and Frank for your thoughts.
Back to top
View user's profile Send private message
PeterHolland

Global Moderator


Joined: 27 Oct 2009
Posts: 2433
Location: Netherlands, Amstelveen

PostPosted: Mon Apr 18, 2011 12:41 pm    Post subject:
Reply with quote

http://support.sas.com/kb/7/816.html
Back to top
View user's profile Send private message
vasanthz

Global Moderator


Joined: 28 Aug 2007
Posts: 1491
Location: Chennai

PostPosted: Mon Apr 18, 2011 1:18 pm    Post subject:
Reply with quote

Thanks Peter that looks like a relevant link to the problem.

The link suggests,
Quote:
1. Submit your data set in interactive. Does it run without error?
2. Run PROC SORT, which sorts the entire data set.


the dataset being worked is temp work dataset, i would try to create a perm dataset and check the solution.

Thanks,
Back to top
View user's profile Send private message
vasanthz

Global Moderator


Joined: 28 Aug 2007
Posts: 1491
Location: Chennai

PostPosted: Thu Apr 21, 2011 2:11 pm    Post subject:
Reply with quote

Hi,

There was a message on the JES log
Code:
+Requested MEMSIZE=75497472 exceeded available REGION=60792832


and also Frank mentioned that this was a storage issue, so changed REGION=0M and there had been no failures so far for the past 4 days(touchwood). icon_biggrin.gif

Quote:
the unusal thing is, this job runs fine once restarted without any changes made to the job.

The JCL has several steps, & the JCL had REGION=48M earlier on job card. When the job was running and came to the SORT step it failed, maybe the region was insufficient.
When we restarted from "failed step" it ran successfully, maybe the region was sufficient now since it was restarted from failed step.

Thanks Expat, Peter & Frank.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> DFSORT/ICETOOL All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Need help in REXX CALL program Raje1002 CLIST & REXX 5 Wed Apr 19, 2017 11:18 pm
No new posts Need help in triggering a PL1 module ... Varungv99 IMS DB/DC 0 Fri Apr 07, 2017 10:01 am
No new posts DFSORT - Overriding default option TU... Steve Ironmonger DFSORT/ICETOOL 3 Tue Apr 04, 2017 3:54 pm
No new posts IMS region inactive - User abend code... gthmrj IMS DB/DC 5 Tue Mar 07, 2017 12:29 pm
No new posts DFSORT MUL FIELDS tspr52 DFSORT/ICETOOL 16 Fri Mar 03, 2017 11:53 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us