Is this to be a one-time exercise to document the procedure, or a means of tracking down who did what to whom?
From the course of this thread, I'm assuming that a nice log(4 00 *seclvl) logclpgm(*YES) joblog is not sufficient...
What we've been doing is journaling our files. This is required for our backup process (MIMIX - to copy data from our production to our backup system), but as a 2ndary benefit, we capture the transactions for key files and tuck them away for error analysis. Then, when a user asks, "Who changed this order?!" we can look at the journal receivers and say, "You did-- on the 14th of December at 10:33 in the morning." This goes a long way towards determining if we have a software or a user malfunction. (:
Paul E Musselman
PaulMmn@xxxxxxxxxxxxx
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Robert Rogerson
Sent: Monday, January 28, 2019 2:47 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Retrieve screen history in ACS...
What we trying to accomplish is a document which shows the steps/screens
a user took in order to accomplish a task. So yes, we do want images
(in one form or another). What I've found from you and Vern is that it
is possible although manual steps are required.
This may be acceptable but a fully automatic solution would be even better.
Rob
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: Retrieve screen history in ACS..., (continued)
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.