|
Tony, To avoid the problem of possible lock during update, may I suggest that each request, batch or interactive, submit an entry to a data queue with any relevant information you may want to collect. You can then off hours process the data queue for analytical purposes. With this method you may be able to "black box" the logging into any/all programs that allow a request. We do this type of thing extensively and always (Ok, almost always ... don't nit pick) have a requester interface program that front ends the submit program which calls the execution program that returns and does the presentation program. Slipping in a logging program under this design would not rock the boat. HTH, James W. Kilgore email@James-W-Kilgore.com Tony.Minehan@hr-m.b-m.defence.gov.au wrote: > G'Day people, > > We have a large amount of programs that our end-users use to produce > hardcopy or screen-based reports. The higher-ups have suggested that we may > like to know how many times each of these programs are run. Each of the > programs has an option to print the report or view it on the screen. If the > report is printed a batch job is submitted. No problem getting stats on > these as job accounting is active. The problem is how many times are the > programs run with the report being generated interactively. My suggestion > is to have each program increment a data area and use the data areas for > the reporting that management requires. Any other suggestions?? > > Tony > +--- | 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 +---
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.