|
<Buck>
What do you do to log error information for later analysis?
</Buck>
First of all: All files have to be journaled.
All database stuff has to be transaction safe (commit)
All Batch jobs are restart safe.
Some details depend on project (I'm working as a dreelancer).
- sending diagnostics to joblog via QMHSNDPM. (log4rpg would be better,
as it is external configurable)
- in one project, we've had a logfile of our own, for problem detection
and automatic restarts.
Up to now I didn't see much benefit for dump.
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.