Re: Variable Length Input File

In article <db00b$45915999$d066072d$11570@xxxxxxxx>,
CG <Carl.Gehr.ButNoSPAMStuff@xxxxxxxxx> wrote:
docdwarf@xxxxxxxxx wrote:
In article <nf0to21l7sn57s6qjkocj493emf0bgfiv4@xxxxxxx>,
Clark F Morris <cfmpublic@xxxxxxxxxxxxxxx> wrote:
On Sun, 24 Dec 2006 01:13:42 +0000 (UTC), docdwarf@xxxxxxxxx () wrote:

In article <lairo250619raljqhu1d545id7c5rbsan0@xxxxxxx>,
Clark F Morris <cfmpublic@xxxxxxxxxxxxxxx> wrote:

[snip]

For FB code the
maximum size 01 level expected for the FD and RECORD 0 in addition to
BLOCK 0 and the actual record length will be determined at run time.
Unfortunately this only works for INPUT.

[snip]

//TESTA DD DSN=USERID1.TESTA,
// DISP=(,CATLG,CATLG),
// UNIT=SYSDA,
// SPACE=(TRK,(1,1),RLSE),
// DCB=(RECFM=FB,LRECL=30,BLKSIZE=27990)

[snip]

... ... the job ABENDs with IEF450I WSXSKEL0 STEP020 - ABEND=S000 U4038
REASON=00000001 and the following messages in the SYSOUT:

[snip]

Would you be so kind as to point out what you see as being the errors I've
made in attempting to implement your suggestion?

Just to get something to you quickly, in case Clark is otherwise occupied...

Just how did you expect to get VARIABLE length records when you
explicitly created the file as FIXED length?

I didn't expect to get VB records; as per Mr Morris' assertion above, the
solution is for FB.

Dealing with a VB dataset with different-length records has not presented,
at least to me, very much of a problem... the difficulty is, I believe, in
dealing with a fixed length dataset which has different-length records. I
had been taught, e'er-so-long ago, that a compiled COBOL module does not
readily enjoy having to deal with a fixed-length dataset which contains
record-lengths differing from those specified before the compile... and so
far all examples I've been able to come up with appear to demonstrate this
behavior.

DD

.

Relevant Pages