RE: Retrieve screen history in ACS...

I get the impression that the OP wants something which will export the files into just a particular program. IDK if it's Power Point or whatever.
This way he can put it into some printable documentation. Sort of like a run book.

As it is, ACS will create .history files which can be displayed from another ACS session. But apparently associating .history files with ACS would be unacceptable because a "live" runbook, with links to other programs, web, etc would not suffice. It must be printable.
At first I wondered if this was archaic thinking. Then I realized my quarterly runbooks are rather extensive so I figured I shouldn't try to remove the speck out of his eye.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Robert Rogerson
Sent: Monday, January 28, 2019 7:11 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Retrieve screen history in ACS...

Thanks Paul and Vern.  I'll look into this....

Rob

On 1/28/2019 6:41 PM, Vernon Hamberg wrote:

Hi Paul

I was thinking als about STRCPYSCN - the archive things is basically
just that - it captures what has just processed - now the archive does
have that history file, and it is a PKZIP archive - and one of the
files in the archive has the characters of each screen captured -
something else makes them look like images in the viewer.

So a person COULD open up the history file and get all the screens as
text - just as STRCPYSCN lets you do.

Cheers
Vern

On 1/28/2019 5:26 PM, Paul Roy wrote:

what about using STRCPYSCN command...
I remember an audit function recording screen image for some
"sensitives"
transactions..

Paul




From:   Robert Rogerson <rogersonra@xxxxxxxxx>
To:     Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Date:   29/01/2019 00:17
Subject:        Re: Retrieve screen history in ACS...
Sent by:        "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>



@Paul, this is for documentation purposes.  As an aside, we do use
journals extensively and have a nightly extract set up which retains
the daily transactions and stores the data in "extract files" which
can easily be queried at a later time.  We have found this invaluable
for resolving both software and user issues.

@John, thanks for the idea of a third party tool but at this point
we're just trying to understand what ACS has to offer out of the box.

@Jack Silly Putty is so passé.  I can get better resolution taking a
picture with my Nokia Flip Phone

Thanks to all who responded.

Rob

On 1/28/2019 5:41 PM, Musselman, Paul wrote:

Rob (the other Rob)--

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

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com