Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
 
meaning of BLOCK CONTAINS 0 RECORDS

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> COBOL Programming
View previous topic :: :: View next topic  
Author Message
raviprasath_kp
Warnings : 1

New User


Joined: 20 Feb 2005
Posts: 65
Location: chennai

PostPosted: Tue Aug 21, 2007 8:39 pm    Post subject: meaning of BLOCK CONTAINS 0 RECORDS
Reply with quote

any one can suggest me why we are using
BLOCK CONTAINS 0 RECORDS
Back to top
View user's profile Send private message

dbzTHEdinosauer

Global Moderator


Joined: 20 Oct 2006
Posts: 6970
Location: porcelain throne

PostPosted: Tue Aug 21, 2007 8:45 pm    Post subject:
Reply with quote

on new versions (the old, also), the system can calculate the optimum blocksize for a DASD device better than the programmer. It is considered a 'Best Practice'.
Back to top
View user's profile Send private message
dr_te_z

New User


Joined: 08 Jun 2007
Posts: 71
Location: Zoetermeer, the Netherlands

PostPosted: Wed Aug 22, 2007 11:09 am    Post subject:
Reply with quote

Yep, it's called "SDB" (system determined blocksize). You code your application like you described, do not hard-code blocksizes in your JCL and the O.S. will determine the optimum blocksize for you, taking into account the DADS device on which the dataset is placed.

I worked in a componay once which had a mix of 3380 en 3390 disks. Works very cool.

1 catch: when you concatinate input datasets, you have to make sure they all have the same blocksize (so be sure there placed on the same type of DASD).
Back to top
View user's profile Send private message
Anuj Dhawan

Senior Member


Joined: 22 Apr 2006
Posts: 6258
Location: Mumbai, India

PostPosted: Wed Aug 22, 2007 11:34 am    Post subject:
Reply with quote

Hi,

Bit more:

When running under MVS, BLOCK CONTAINS 0 can be specified for QSAM files; the block size is determined at object time from the DD parameters or the data set label.

The BLOCK CONTAINS clause is an optional clause in a file description entry. The BLOCK CONTAINS clause specifies the size of the physical records. The characters in the BLOCK CONTAINS clause reflect the number of bytes in the record. (For example, if you have a block with 10 DBCS* characters, the BLOCK CONTAINS clause should say BLOCK CONTAINS 20 CHARACTERS.

*Double-Byte Character Set

Hope this helps.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> COBOL Programming All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Inefficient BUILD - VB records paddin... Daniel Prosser SYNCSORT 6 Thu Dec 14, 2017 3:52 pm
No new posts ISSUE IN copying Sequential file reco... thesumitk JCL & VSAM 2 Wed Dec 13, 2017 3:07 pm
No new posts Merging 2 records at multiple rows wi... Bijesh DFSORT/ICETOOL 2 Wed Dec 06, 2017 1:50 am
No new posts Increment number for every group of r... srajendran2 DFSORT/ICETOOL 7 Thu Nov 09, 2017 10:31 pm
No new posts Matching and unmatched records!! Vignesh Sid SYNCSORT 3 Thu Nov 09, 2017 11:22 am

Facebook
Back to Top
 
Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us