View previous topic :: View next topic
|
Author |
Message |
atulxp
New User
Joined: 27 Nov 2005 Posts: 15 Location: Phoenix
|
|
|
|
I have a file having 210000000 in a file & I have to prepare two output files using conditions as in following sort card.
SORT FIELDS=(1,13,CH,A,14,14,CH,A,129,10,CH,A)
SUM FIELDS=NONE,XSUM
My Job is abending due to SORT CAPACITY EXCEEDED.
I have tried following options as well
OPTION MOSIZE=MAX,HIPRMAX=OPTIMAL,DSPSIZE=MAX
Is there any otherway to get result without problem.
Thanks in advance |
|
Back to top |
|
|
William Thompson
Global Moderator
Joined: 18 Nov 2006 Posts: 3156 Location: Tucson AZ
|
|
|
|
Please post your JCL and all of the sort's output messages.
Without complete information, help will be very slow in coming. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Until you post the material Bill requested, all i can offer is to first split the file into something your capacity can handle, run the split pieces individually thru the sort, then merge them back into the final file you need.
In addition to the number of records, what is your lrecl?
Regardless of which sort product you are using, there is always a capacity ceiling - splitting the file may be your route.
Good luck - we're here |
|
Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
|
|
|
|
I have usually found that this is caused by the SORTWKnn needing to have a much larger DASD allocation than they already have. Either by increasing the space allocated or by increasing the number of SORTWKnn DD statements.
You may have to code these yourself if you are using dynamic sortwork allocation. |
|
Back to top |
|
|
atulxp
New User
Joined: 27 Nov 2005 Posts: 15 Location: Phoenix
|
|
|
|
Thanks problem got resolved, actually i was using less sort work files |
|
Back to top |
|
|
|