Re: Question about opening and closing files

In most case, opening and closing file on transaction by transaction
bases will not cause any performance issue on interactive job, meaning
user will not notice much of a different. However, you might experience
noticeable performance issue when running in batch mode where million of
transactions are being processed. Under this case scenario, I would add
some codes in the *inzsr routine of the trigger program to first
determine if the job is a batch or interactive job. If it is a batch
job, open the file and leave it open. If it is interactive job, open
and close the file while actually performing I/O.


"James Lampert" <jamesl@xxxxxxxxxxxxxxxxx> wrote in message
news:<mailman.9425.1220917610.2545.rpg400-l@xxxxxxxxxxxx>...

How much overhead would you say is involved in making files *USROPN,

and

keeping them open only while actually performing I/O on them, as

opposed

to doing things the usual way?

We're thinking of doing this in a trigger program, in order to cut

back

on the number of file locks.

--
James H. H. Lampert
Touchtone Corporation