I have a sort step with region=9182k in production and this is abending with space abend, then I changed to Region=0M but it is still abending with same space issues. Could anyone please let me how do I avoid this space issues.
Joined: 22 Apr 2006 Posts: 6248 Location: Mumbai, India
Quote:
RECFM=VB ; LRECL= 1039; BLKSIZE= 32760
Is your input file on TAPE?
As gylbharat also indicated, you're not getting space-abend - but then why do you say so in your first post?
Quote:
I changed to Region=0M
This is not the correct solution for such problems. Depending upon the CLASS in which the Job is executing value on REGION parameter might/might-not be honoured.
Suggest you get in touch with the SyncSort representative at your shop.
Joined: 06 Jun 2008 Posts: 8700 Location: Dubuque, Iowa, USA
Quote:
this is abending with space abend, then I changed to Region=0M but it is still abending with same space issues.
This is like telling a mechanic your car won't go into reverse, so the mechanic changes the radiator fluid. There is NO relationship between a "space abend" and the REGION= parameter in a job. Further, you need to be aware that a "space abend" may be an SB37, SD37, SE37 (among others) abend and these require different solutions depending upon which is occurring -- and why.
Typically, UNIT=CART refers to some form of tape (3480 cartridge, 3490 cartridge, 3590, etc) -- in which case using a SPACE parameter is completely and totally useless since tape cartridges do not have nor do they use SPACE (a parameter that applies ONLY to disk drives).
Further, you need to tell us how many records are in your input file and what is their average record length. Have you run a historgram on your input file?
Joined: 22 Apr 2006 Posts: 6248 Location: Mumbai, India
It looks like te OP is not posting what actually is happening. WER046A is termed as "space abend" while neither posted-SYSOUT not the JESMSGLG talka about S%37. I'm not sure if it's a "true-thread".