|
As I see your point, this is where it gets really sticky - to begin with, the first part of the web app is only doing reads, no updates and does not see the records, to make matters even more complex, we have green screen apps still in use that are using journaling/commitment control to do the maintenance on the same file, so I am not going to be able to change the frcratio due to those other programs (some will go away, some will stay) All the srp programs are under the same activation group.... Would it be a good idea to change my files to user controlled?? closing and opening them with each new web request?? Even though LR should do "most" of this "housekeeping" I was "watching" one of the jobs for the live web site, now this is something very strange I noticed, doing a 5 and then a 14 to watch the files, I see the same file opened multiple times, for the same job, not with overrides - hmm It does "seem" like the files are being left open even with LR being set on. I may just make them user controlled, and see what that does. -----Original Message----- From: web400-admin@midrange.com [mailto:web400-admin@midrange.com]On Behalf Of Nathan M. Andelin Sent: Tuesday, March 05, 2002 2:47 PM To: web400@midrange.com Subject: Re: [WEB400] strange behavior with web site programs/files Mark, I'd recommend using the CHGPF command to set the FRCRATIO value to 1. Although you say you're setting LR *ON before returning, it appears that something is preventing the file from being closed, and the records forced to disk. Subsequent requests from the browser may be handled by an entirely different server JOB. If the records are not forced to disk, the other JOB wont see them. Maybe something to do with the activation group(s) your CGI programs run under? Nathan M. Andelin
As an Amazon Associate we earn from qualifying purchases.
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.