Re: Cobol I/O Modules and Blocking

     I ran across a possible cause for this last night. Are you by any 
     chance using a trigger program on the file you are trying to process 
     sequentially? As I understand it, the trigger program _may_ be forcing 
     all I/O to be processed a record at a time. This is to allow the 
     trigger to fire on each record that is processed. Could this be the 
     answer to your problem?
     
     Eric A DeLong
     ericadelong@pmsc.com


______________________________ Reply Separator _________________________________
Subject: Cobol I/O Modules and Blocking 
Author:  <MIDRANGE-L@midrange.com > at INTERNET
Date:    7/7/98 9:39 AM


Hi all,
  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?
     
TIA
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 
+---
     


+---
| 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
+---