RE: Saving a session's history

Is there a way to have the inquiry message answered automatically, either by 
the system or some other application, so that the end user is not aware that 
the screen copy is taking place?

Norman Boyd

>>> qsrvbas@xxxxxxxxxxxx 04/29/04 03:49PM >>>
Carel:

STRCPYSCN is actually a cool solution to the original problem. A secondary 
session is only required if the copy-screen output is being sent to another 
display. If the output goes to a file, it can all be contained within the one 
session.

I put together an applications problem logging tool that worked in this way and 
made it available to users via their <Attn> menues. When a user wanted to log 
an issue and have application support look it over, they'd take the "Start 
logging" menu option and answer 'Y' (or 'G' or whatever that required character 
was) when asked if screen copying was okay.

Then they'd go through the sequence that had problems or needed clarification. 
When done, they'd take the "End logging" menu option.

The logging tool created a new member to store the session in. It added an 
index entry to track user, member name, application, etc., whatever info was 
useful, and sent a message to application support saying "Hey, check this 
[member] out."

App support could take a complementary menu options to replay the session 
including page-forward/page-backward, print the session, remove old sessions, 
etc. Printing was partly through an LF that translated DSPF field attributes 
and created a form suitable for other documentation. The printing aspect was 
used as part of creating user guides, sample test scripts, etc.

STRCPYSCN can be a major plus if used creatively.

Tom Liotta

midrange-l-request@xxxxxxxxxxxx wrote:

>   1. Re: Saving a session's history (Carel Teijgeler)
>
>I do not think STRCPYSCN will do, as such jobs are started from another 
>session and the inlogging user have to answer whether or not that proces may 
>be run (IIRC).
>
>Changing the job with a startup programme may be countered by them, if they 
>know the system well an ddo a simple CHGJOB, too.
>
>Auditing may be the only solution.
>
>On 29-4-04 at 10:02 sgallaher@xxxxxxx wrote:
>
>>Is there a 400 equivalent to the old S/36 HISTORY command?
>>
>>I'm looking for a way to keep track of everything someone did while 
>>they're signed on with their *SECOFR account (commands, STRSQL sessions, 
>>etc).  The most detailed thing I can think of is writing some CL to issue 
>>the STRCPYSCN command when they log in.


-- 
Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone  253-872-7788 x313
Fax    253-872-7904
http://www.powertech.com 


__________________________________________________________________
Introducing the New Netscape Internet Service. 
Only $9.95 a month -- Sign up today at http://isp.netscape.com/register 

Netscape. Just the Net You Need. 

New! Netscape Toolbar for Internet Explorer
Search from anywhere on the Web and block those annoying pop-ups.
Download now at http://channels.netscape.com/ns/search/install.jsp 
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
or email: MIDRANGE-L-request@xxxxxxxxxxxx 
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.