Yes Rob, that's pretty much what I'm looking for. I realize there are
many different ways to get a list of screens that a user traverses
through to complete a task but these usually require some sort of manual
intervention. This leaves the potential for missed screens.
What I liked about screen history was that it automatically captured the
screens. But from what we've seen there is no way to export the screens
as images which can be imported by another application.
Hopefully the RFE [1]here will get enough votes and be excepted.
Thanks to all who contributed to this discussion.
Rob
On 1/29/2019 7:05 AM, Rob Berendt wrote:
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 [2]<midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Robert Rogerson
Sent: Monday, January 28, 2019 7:11 PM
To: Midrange Systems Technical Discussion [3]<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 [4]<rogersonra@xxxxxxxxx>
To: Midrange Systems Technical Discussion
[5]<midrange-l@xxxxxxxxxxxxxxxxxx>
Date: 29/01/2019 00:17
Subject: Re: Retrieve screen history in ACS...
Sent by: "MIDRANGE-L" [6]<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
[7]PaulMmn@xxxxxxxxxxxxx
-----Original Message-----
From: MIDRANGE-L [8]<midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf
Of
Robert Rogerson
Sent: Monday, January 28, 2019 2:47 PM
To: Midrange Systems Technical Discussion
[9]<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: [10]MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: [11]
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: [12]MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at [13]
https://archive.midrange.com/midrange-l.
Please contact [14]support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: [15]
https://amazon.midrange.com
References
Visible links
1.
https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=123233
2. mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx
3. mailto:midrange-l@xxxxxxxxxxxxxxxxxx
4. mailto:rogersonra@xxxxxxxxx
5. mailto:midrange-l@xxxxxxxxxxxxxxxxxx
6. mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx
7. mailto:PaulMmn@xxxxxxxxxxxxx
8. mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx
9. mailto:midrange-l@xxxxxxxxxxxxxxxxxx
10. mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx
11.
https://lists.midrange.com/mailman/listinfo/midrange-l
12. mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
13.
https://archive.midrange.com/midrange-l
14. mailto:support@xxxxxxxxxxxx
15.
https://amazon.midrange.com/
midrange.com
