James wrote:
"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."
If your trigger program is doing enough work to be causing record locks,
then there is entirely too much logic in the trigger. I would suggest you
externalize the logic. When I have a trigger to write, if it does more
than update fields in the existing record, I move the logic out.
Usually my trigger program gets the needed information from the before or
after image and outputs it to a dataq. I then have a dataq server running
to handle the heavy logic. This approach keeps your database access quick
because the trigger program should run extremely quickly to just write a
dataq entry.
My two cents.
Brian May
Project Lead
Management Information Systems
Garan, Incorporated
Starkville, Mississippi
Young i Professionals
http://www.youngiprofessionals.com/
midrange.com
