Re: Cobol I/O Modules and Blocking

[Terry Grider <tgrider@xxxxxxxxxxxx>]

Sclind2@aol.com wrote:

> In a message dated 98-07-08 01:41:12 EDT, you write:
>
> << We have a system where the vendor has coded all file i/o into dynamically
> called
>  modules.  These modules have all possible file access methods available
> (sequential,
>  random, input, output, i/o).  The problem comes when these module are used to
> process
>  a file sequentially and it would be a great benefit to block the file, but
> because the
>  system sees the other processing methods defined in the module, it disables 
>any
> blocking
>  paramaters we try to use.  Short of rewriting these modules, (there are
> hundreds of them)
>  does anyone know a way to enable blocking using these modules? >>
>
> If you're willing to change the CL program that call the COBOL program (or add
> one), I believe:
>
> OVRDBF FILE(FILEX) SEQONLY(*YES XXXX)
>
> forces sequential access even when random I/O was found by the compiler.
>
> Scott Lindstrom
> Zenith Electronics
>

  Thanks for the reply Scott, but unfortunately, I have tried this idea already.
For whatever reason the system will not use the value supplied on the SEQONLY
parameter.

Thanks again,
Terry Grider

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---