|
From: qsrvbas@xxxxxxxxxxxx Many of the *BEFORE and *AFTER actions (often _all_ of them) could be in a direct CL member executed as a script. If elements such as system auditing and database journaling are active, then every action and result would be automatically logged. Security for the administrative program object is almost trivial to set up. With a little effort, administrative complexities can be nearly eliminated while using nothing but the default (i.e., no extra charge) facilities of the system.
This is a huge point, Tom. One of the beauties of the integrated nature of the iSeries is that pretty much everything can be journaled. And this isn't just to some text file; it's to a secure object that can't be tampered with. AFAIK, you can't even log all your actions on Unix, much less in a secure, non-corruptible fashion. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.