|
Scotto, 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. Regards, Carel Teijgeler *********** REPLY SEPARATOR *********** 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.
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
