Re: COBOL400-L Digest, Vol 4, Issue 125

It is my understanding that the block contains clause is irrelevant in the 
iSeries world.  it was retained as a convenience to minimize unneeded 
modifications when converting COBOL code from the mainframe world.  It matters 
not whether you leave the clause in or keep them the iSeries will block the 
files as it will.  I remove such statements because I like clean compiles but 
that is not necessary.

-----Original Message-----
From: cobol400-l-bounces+jarnold=fedmedinc.com@xxxxxxxxxxxx on behalf of 
cobol400-l-request@xxxxxxxxxxxx
Sent: Wed 11/29/2006 1:00 PM
To: cobol400-l@xxxxxxxxxxxx
Subject: COBOL400-L Digest, Vol 4, Issue 125
 
Send COBOL400-L mailing list submissions to
        cobol400-l@xxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.midrange.com/mailman/listinfo/cobol400-l
or, via email, send a message with subject or body 'help' to
        cobol400-l-request@xxxxxxxxxxxx

You can reach the person managing the list at
        cobol400-l-owner@xxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of COBOL400-L digest..."


Today's Topics:

   1. Re:  question on BLK vs. NOBLK compiler option...
      (Michael Rosinger)
   2. Re:  question on BLK vs. NOBLK compiler option... (Jon Paris)
   3. Re:  question on BLK vs. NOBLK compiler option...
      (Michael Rosinger)


----------------------------------------------------------------------

message: 1
date: Tue, 28 Nov 2006 15:55:03 -0500
from: "Michael Rosinger" <mrosinger@xxxxxxxxx>
subject: Re: [COBOL400-L] question on BLK vs. NOBLK compiler option...

Jon,

I appreciate your response. Let me rephrase my issue/question. Perhaps the 
compiler option BLK/NOBLK has nothing to do with what I am wanting to know.

We READ and WRITE quite a few sequential files (not indexed or relative) in 
many of our COBOL programs. Virtually all of the FD's for those files have 
the BLOCK CONTAINS clause specified. Many of these sequential files have 
variable length records.

My question is what is the best combination to use in the iSeries world?

1) Remove the BLOCK CONTAINS altogether and let the compiler block and 
de-block as it sees fit? Does it do a good job?

2) Retain BLOCK CONTAINS and use what was originally specified in the VSE 
world?

3) Retain BLOCK CONTAINS and but specify a new value that is more correct 
for the iSeries world? Is there a rule of thumb for this?