View previous topic :: View next topic
|
Author |
Message |
balubhat
New User
Joined: 04 Oct 2005 Posts: 19 Location: Singapore
|
|
|
|
Hii
How to get rid of the abends like SB37, SD37, SE37 permanently.
Means instead of keep increasing the primary and secondary allocation in SPACE parameter, is there any other parameter which will solve these end of space abends permanently.
Please let me know.
Thanks
Bala |
|
Back to top |
|
|
Kumar Saraboji
New User
Joined: 15 Sep 2009 Posts: 8 Location: India
|
|
|
|
Hi Bala,
I guess you can avoid these ABENDs by going for SMS datasets (but this still this has site based limitiations). But not sure, please wait for experts solution.
Thanks,
Kumar |
|
Back to top |
|
|
Terry Heinze
JCL Moderator
Joined: 14 Jul 2008 Posts: 1249 Location: Richfield, MN, USA
|
|
|
|
Nothing will guarantee that all x37 abends will disappear, but as far as the B37 goes, see the unit-count subparameter of the UNIT parameter of the DD statement in the JCL manual. Other vendors also sell software to reduce x37 abends. As usual, the MVS System Codes manual has the details on what causes these abends. Have you looked them up? |
|
Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
|
|
|
|
Kumar Saraboji wrote: |
I guess you can avoid these ABENDs by going for SMS datasets (but this still this has site based limitiations). But not sure, please wait for experts solution. |
Not quite sure how the dataset being SMS managed will help here. The problem is that the dataset has run out of available space to continue writing to.
This can be caused by a variety of reasons. Volume of data, insufficient space available on the volume(s), the volume(s) being badly fragmented and causing each logical extent being fragmented in up to 5 physical extents, or just poor space allocation by the JCL monkey.
This needs to be investigated to find the real cause, and then a longer term fix can be applied. |
|
Back to top |
|
|
gcicchet
Senior Member
Joined: 28 Jul 2006 Posts: 1702 Location: Australia
|
|
|
|
Hi,
and let's not forget a looping program can quickly use up all the available space.
Gerry |
|
Back to top |
|
|
balubhat
New User
Joined: 04 Oct 2005 Posts: 19 Location: Singapore
|
|
|
|
Thanks for the reply.
The scenario is like program is writing into a file and suddenly the allocated space for the file is over. The I increased the Primary and Secondary allocation in SPACE parameter to some large figure like SPACE=(BLK,(9000,9000),RLSE) but still I got the abend.
the I am thinking of some alternative to get rid of this error.
And this file is going to be a big file and it has be in single file only. |
|
Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
|
|
|
|
RECFM & LRECL of the file
Estimated number of records in the file |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
Quote: |
I am thinking of some alternative to get rid of this error. |
Try thinking of a perpetual motion device -- equally as likely. You cannot possibly get rid of all possible causes for space abends, so there is absolutely no alternative that will get rid of them forever. If you know how many records are expected in the file, you can calculate how big the file must be and set the SPACE parameters based on that -- but if there are more records than you're expecting, or growth over time, you can still run out of space. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Everything is relative. . . 9000 blocks is not a very large number, typically.
Usually, large files are allocated in CYL rather than BLK or even TRK. . .
As others have asked - what are the recfm, lrecl, and number of records? |
|
Back to top |
|
|
devd
New User
Joined: 19 Mar 2009 Posts: 11 Location: Chennai
|
|
|
|
Hi,
I feel space abends can be get rid of by any permanent fix.Some or other time you might get it as it's quite dependant on the size of of file written onto here.
In recent past i was also facing SB37 a lot many times for a particular job. I had analysed and found that it had prob with SORT component while loading into the table.I just added specific number SORTWK DD names for the job with space parm as SPACE=(CYL,(X,Y),RLSE) .
Am just telling this to inform you that you might also be having similar issue .So just check it out |
|
Back to top |
|
|
|