If possible, post the entire DFSORT output. There are many elements in the various messages that will help understanding the issue. I am interesting in the parms being passed to sort, the rec in/out info and a few other pieces
The Cobol code not so much Any changes to the program recently like LRECL or increase in records being processed? Also, if you did not know this, you can email the dfsort team directly for assistance. [email protected] Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Vernooij, Kees (ITOPT1) - KLM > Sent: Monday, October 02, 2017 6:47 AM > To: [email protected] > Subject: Re: Sort Question > > Apparently your sortwk's are that small, that many more are needed. > > Post your sortparameter, displayable with this job: > //LISTDEF EXEC PGM=ICETOOL > //TOOLMSG DD SYSOUT=* > //DFSMSG DD SYSOUT=* > //SHOWDEF DD SYSOUT=* > //TOOLIN DD * > DEFAULTS LIST(SHOWDEF) > /* > > Post the full DFSORT output and the JCL of the step with the error. > > This info must give a clue. > > Kees. > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] > > On Behalf Of Pfister, Nathan > > Sent: 02 October, 2017 15:40 > > To: [email protected] > > Subject: Sort Question > > > > List; > > > > I have a question dealing with a DFSORT job which I am hoping to get > > some guidance on. > > > > We have a COBOL program which inconsistently gets a SORT CAPACITY > > EXCEEDED error. They've changed their cards several times with > > several different options to try and get this to work. Depending on > > the month sometimes it works and sometimes it doesn't, with their > > typical OPTION > > DYNSPC=1024,DYNALLOC=(SYSDA,59) > > > > The latest run, we added FILSZ=E60000000 > > > > In every run it seems to exceed the sort capacity. > > +ICE046A 5 PRSPM175.J05 SORT CAPACITY EXCEEDED - RECORD COUNT > > 58081219 > > > > And the following error as well. Not sure > > > > ICE278I 1 59 WORK DATA SETS WERE INSUFFICIENT TO COMPLETE THIS SORT SO > > 44 ADDITIONAL WERE USED > > > > The funny thing is, this has worked with a DYNALLOC of 24...there is > > nothing else in the system at the time this was running, and plenty of > > DASD. Obviously I am overlooking some key piece of information. > > > > Here's the COBOL for the Sort, which doesn't mean too much to me as I > > am not a COBOL programmer, so I am sure I am missing parts of the sort > > call, but this is what I was given... > > > > SD S1-SORT-FILE > > RECORDING MODE IS F > > DATA RECORDS ARE S10-SORT-REC > > RECORD CONTAINS 49 CHARACTERS. > > 01 S10-SORT-REC. > > 05 S20-SORT-KEY. > > 10 S20-KEY-LOCATION PIC X(2). > > 10 S20-KEY-MCO PIC X(2). > > 10 S20-KEY-PCO PIC X(2). > > 10 S20-KEY-TREATY PIC X(4). > > 10 S20-KEY-AS-LINE1 PIC 9(3). > > 10 S20-KEY-AS-LINE REDEFINES S20-KEY-AS-LINE1 > > PIC 9(2)V9(1). > > 05 S20-BREAK-KEY-R1 REDEFINES S20-SORT-KEY. > > 10 S20-TREATY-BREAK PIC X(10). > > 10 FILLER PIC X(3). > > 05 S20-BREAK-KEY-R2 REDEFINES S20-SORT-KEY. > > 10 S20-PCO-BREAK PIC X(6). > > 10 FILLER PIC X(7). > > 05 S20-BREAK-KEY-R3 REDEFINES S20-SORT-KEY. > > 10 S20-MCO-BREAK PIC X(4). > > 10 FILLER PIC X(9). > > 05 S30-SORT-BODY. > > 10 S30-LINE-TYPE PIC 9(1). > > 10 S30-MONTHLY-WRITTEN PIC S9(7)V9(2) COMP-3. > > 10 S30-TO-DATE-WRITTEN PIC S9(7)V9(2) COMP-3. > > 10 S30-NEW-MONTH PIC S9(7)V9(2) COMP-3. > > 10 S30-THIS-MONTH-EARNED PIC S9(7)V9(2) COMP-3. > > 10 S30-INFORCE-TO-DATE PIC S9(7)V9(2) COMP-3. > > 10 S30-LA-COMMISSION PIC S9(7)V9(2) COMP-3. > > 10 S30-TOT-COMMISSION PIC S9(7)V9(2) COMP-3. > > EJECT > > > > SORT S1-SORT-FILE > > ASCENDING KEY > > S20-SORT-KEY > > > > If anyone could point me in the right direction on this, I would > > appreciate it! > > > > Nathan Pfister > > Systems Programmer > > Donegal Insurance Group > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
