Re: Variable Length Input File

In article <4vdr12F1botahU1@xxxxxxxxxxxxxxxxxx>,
Pete Dashwood <dashwood@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I have a question, please, Doc.

[snip]

If the JCL specifies a block size of 27990 (nicely divisible by 30, 933
times), and the COBOL program is specifying a block/record size of 32767,
wouldn't this be likely to cause an IO error when the dataset is opened?

I thought there would be some kind of error as well, Mr Dashwood, hence my
testing... but both of our thinkings appear to be contrary to Mr Morris'
assertion that '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.'

I posted code which I believed was in accordance with this - it is a new
technique for me and I'm not quite sure I got it right - and, likewise,
posted the results (an ABEND). If there's something else I should be
doing then, by all means, post the code - both COBOL and JCL - and I'll be
more than happy to compile it and show the results.

DD
.

Relevant Pages

  • Re: Variable Length Input File
    ... Pete Dashwood wrote: ... times), and the COBOL program is specifying a block/record size of 32767, ... I posted code which I believed was in accordance with this - it is a new ...
    (comp.lang.cobol)
  • Re: read by which index?
    ... Pete Dashwood wrote: ... system subroutine describes the dataname as a PRimary or ALternate or ... that someone posted code that showed how a COBOL program could access the ... But as for Mr Hoberg... ...
    (comp.lang.cobol)
  • Re: Variable Length Input File
    ... Pete Dashwood wrote: ... times), and the COBOL program is specifying a block/record size of 32767, ... FD was made the same as the LRECL size... ... TESTA doesn't always have the same LRECL. ...
    (comp.lang.cobol)