My advice would be to change the Signoff command. You can put a RTVJOBA command in there and retrieve the user who is trying to signoff. You can compare that with the users you want to monitor. As for printing the joblog, all you have to do is DSPJOBLOG OUTPUT(*PRINT). Let me know if you need anything else.

Shane Duncan

-----Original Message-----
From: security400-bounces@xxxxxxxxxxxx [mailto:security400-bounces@xxxxxxxxxxxx] On Behalf Of Yogesh Pathak
Sent: Monday, October 31, 2011 5:44 AM
To: security400@xxxxxxxxxxxx
Subject: [Security400] Printing Job Log

Dear All,

I am struggling with an issue on our iSeries.

I want to print the JobLog for two particular user IDs when they signoff
from the system.

If I change the Signoff command, the system will print the job Log of all
Users, which will add a considerable overhead on Disk Space and clearing the
spool files. I am therefore not keen on implementing this.

Is there any way to make sure Job Log of a particular user is printed when
he signs off? These two User ID are authorized to make Production Releases,
and they should be logged on only at the time of performing a Production
release. I want to make sure all their Job Logs are available for audit, and
hence this request.

Thanks and Regards

Yogesh Pathak


"You have a right to expect all that is good and high from yourself - indeed
you must demand it from yourself - but as far as others are concerned, you
must be tolerant."

- Parthasarathi Rajagopalachari

This is the Security Administration on the AS400 / iSeries (Security400) mailing list
To post a message email: Security400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: Security400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by 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].