|
Does someone know of a way to correct this behavior or of anothermethod of giving users (on-call programmers, actually) a way to respond
problems which would require *ALLOBJ authority without actually givingthem *ALLOBJ on their user profile?
-----Original Message-----
From: security400-bounces@xxxxxxxxxxxx
[mailto:security400-bounces@xxxxxxxxxxxx] On Behalf Of Steve McKay
Sent: Thursday, May 01, 2008 8:58 AM
To: security400@xxxxxxxxxxxx
Subject: [Security400] Wayne Evans' LOGCMD
I have a copy of Wayne Evans' LOGCMD program/command. This
allows specified non-admin users to gain *ALLOBJ authority
and records the commands they enter to QAUDJRN by acquiring a
user profile handle, turning on *CMD auditing on the user
profile, and processing the entered commands as messages from
the external message queue. This works well if the user
stays on the QCMD screen that is initially displayed. If the
user enters some command that has it's own command line
(WRKACTJOB, for instance), any commands entered on that
command line do not get recorded in QAUDJRN.
Does someone know of a way to correct this behavior or of
another method of giving users (on-call programmers,
actually) a way to respond to problems which would require
*ALLOBJ authority without actually giving them *ALLOBJ on
their user profile?
TIA,
Steve
_______________________________________________
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,
visit: http://lists.midrange.com/mailman/listinfo/security400
or email: Security400-request@xxxxxxxxxxxx Before posting,
please take a moment to review the archives at
http://archive.midrange.com/security400.
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.