Ron,

Been awhile (years) but last time I looked your JSF needed to be fixed and
max length (going out on a limb)
was 80 characters.  One common hose up was keeping the file as numbered and
confusing the poor job
processor.  Anyhow, fixed length record, maxchar=(ummm 80?) as of a few
years ago.

jt

> -----Original Message-----
> From: Ron Wallace [SMTP:[log in to unmask]]
> Sent: Tuesday, January 26, 1999 10:51 AM
> To:   [log in to unmask]
> Subject:      COBOL accept on variable length files.
>
> In COBOL
>
> I ran across an accept statement problem with variable length files.
> Notice the "Y" on "NOREPORTY" on line 90.
>
> When the stream file was variable length the ACCEPT command picked up two
> lines in the standard list.
>
> When the same program was run from a fixed length file the ACCEPT command
> worked as it should.
>      79   :
>      80   :SETVAR COBRUNTIME,"M IDCA   W"
>      81   :FILE LAGAG001=JA0005XH
>      82   :FILE BRULE001=JA0005XI
>      83   :FILE RULEREPT=JA0005XG
>      84   :FILE RULESORT=JA0005XJ
>      85   :FILE RULETBL=RULETBL5.VCDATA.AIH
>      86   :FILE JVRPT;DEV=901,5,1
>      87   :RUN BRULE04C.VCCBPRG.AMISYS9T
>      88
>      89   VER. 2.00 RKW 990120
>      90   REPORT NOPRINTY
>      91    UPDATE Y OR N IS Y
>      92
>
> The JCL was:
>
> !RUN BRULE04C.VCCBPRG.AMISYS9T
> NOPRINT
> Y
> Y
>
>
> The characters accepted in the job stream was smaller than the buffer in
> working storage.
>
> Anyone know the specific rules about variable length STREAM files and the
> COBOL ACCEPT statement?  Does the buffer size have to match the characters
> input?
>
> Ron (just curious) Wallace
> 559-446-6888