Page 1 of 1

Space abends ( SB37,SD37,SE37 )

PostPosted: Tue Apr 13, 2010 7:39 pm
by uday123
Hi,

Can anyone pls list out what are the ways to handle space abends ( SB37,SD37,SE37 ) ?
I know that if we increase number of cylinders , then we can avoid them , or give secondary allocation.
But even if we try with above said , if it gives space abend , then how do we handle it? Any alternate way
of handling large datasets. Pls advise. Thnx


Regards
Uday

Re: Space abends

PostPosted: Tue Apr 13, 2010 8:47 pm
by Robert Sample
Work with your site storage management group. They can provide assistance in minimizing or even totally eliminating space abends.

Re: Space abends

PostPosted: Thu Apr 15, 2010 3:12 am
by Bill Dennis
You need to look at the reason code on your abends, ex. E37-08. Different abend reasons have different solutions.
If the volume is out of space, increasing the allocation does no good! Understand why the abend happened and you will be on your way to fixing it.

Re: Space abends

PostPosted: Thu Apr 15, 2010 12:36 pm
by uday123
Thank you.. Based upon the reason code , can u pls list out the common way of handling space abends..
Like will u split a large dataset or something like tat ?

Regards
Uday

Re: Space abends

PostPosted: Thu Apr 15, 2010 4:22 pm
by expat
Uday,

Why not take a look at the MVS system codes manual and see for yourself. That way you will learn how to find and use manuals, and how to resolve problems on your own.

Re: Space abends

PostPosted: Thu Apr 15, 2010 5:27 pm
by Robert Sample
You are asking for something that cannot exist. Each site has different products installed and those products help dictate how the site handles space abends. For example, some sites install vendor products that specifically deal with space abends -- other sites do not. Furthermore, there are multiple reasons for space abends and the response depends upon the precise problem -- the file may not be able to get an extent on the pack because the pack is full, or there are no more candidate volumes in the storage spool, or there are no candidate volumes in the storage pool with free space equal to the primary space allocation of the data set, or the data set may have hit 16 extents, or the data set may have used 65,535 tracks on the pack, or the VTOC is full, or the data set allocation is too small for the number of records being put in the file, or .... There are too many possible problem reasons to be able to come up with a list of answers.

Re: Space abends

PostPosted: Sun Apr 18, 2010 9:04 pm
by Anuj Dhawan
oh Robert I've a feeling that you've scared the OP! Go slow please...:)

Have a good one, :)