IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Need information on SB37 Space issue in Jcl


IBM Mainframe Forums -> JCL & VSAM
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
sivasaras

New User


Joined: 29 Sep 2007
Posts: 93
Location: chenna/i-

PostPosted: Mon Jan 16, 2012 7:20 pm
Reply with quote

Hi,

My application job which is running daily got abended with SB37 issue while writing the records to the report file.

This is the file which abended

DSN=MT.MTCH01.MT00535.ERROR.REPORT(+1),
DISP=(NEW,CATLG,CATLG),
DCB=(RECFM=FB,LRECL=133,BLKSIZE=27930),
SPACE=(CYL,(10,2),RLSE)


Now I am going to increase the cylinders from CYL(10,2) to CYL(200,200) so that it wont abend once again.

Daily I am receiving 2,000,000 records and while writing some of the records which are rejected then I got SB37 issue.

Kindly guide me whether I can go ahead with this increase of space.

Thanks
Siva
Back to top
View user's profile Send private message
Bill Woodger

Moderator Emeritus


Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix

PostPosted: Mon Jan 16, 2012 7:31 pm
Reply with quote

You need a reasonably estimate of how many items should be on the report. Size it accordingly, allowing for business growth. Someone, like Production Control, should monitor for extents used.

The problem with making it huge is, if there is a program error or unusual event which causes a lot of erroneous rejections, the first thing you know about it is when the user sees it, rather than when it has blown the "reasonable" size of the report file.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA

PostPosted: Mon Jan 16, 2012 7:40 pm
Reply with quote

Your current allocation allows, at most, 252000 records (40 cylinders of space times 15 tracks per cylinder times 2 blocks per track times 210 records per block -- the limit may be less if the volume is nearly full) whereas the space you're proposing allows for over 20 MILLION records. Both are completely ridiculous -- if you are getting 2 million records a day, size the error file to allow for every record to be an error; don't allocate a small proportion for the file, and don't allocate 10 times the space it needs. And don't rely on secondary extents -- size the file correctly with the primary space allocation.
Back to top
View user's profile Send private message
sivasaras

New User


Joined: 29 Sep 2007
Posts: 93
Location: chenna/i-

PostPosted: Mon Jan 16, 2012 8:33 pm
Reply with quote

Hi,

Thanks for the reply

i will increase the primary allocation and now the space=(CYL,(100,25),RLSE)

This is ok

Thanks
Siva
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> JCL & VSAM

 


Similar Topics
Topic Forum Replies
No new posts Replace each space in cobol string wi... COBOL Programming 2
No new posts SFTP Issue - destination file record ... All Other Mainframe Topics 2
No new posts Capturing Job Execution Information All Other Mainframe Topics 3
No new posts Issue after ISPF copy to Linklist Lib... TSO/ISPF 1
No new posts Facing ABM3 issue! CICS 3
Search our Forums:

Back to Top