×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
