Re: Restrict CLROUTQ--A good use for an exit program?

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Dave, the simplest way is to turn on auditing for the command. Use

CHGOBJAUD OBJ(CLROUTQ) OBJTYPE(*CMD) OBJAUD(*USRPRF)

You might want to do the same with the CHGOBJAUD command!  ;-)

And be sure to know which users have *AUDIT special authority - they can 
change auditing even if they do not have authority to an object, according 
to the help text.

Then you need to have a journal called QAUDJRN. And set system value 
QAUDCTL. The easiest way is to GO SECTOOLS and use option 10. For this 
purpose, all you need is object auditing (*OBJAUD).

HTH
Vern

At 11:27 AM 5/10/2004, you wrote:
> Good morning all,
>
> We have a situation where someone appears to be clearing an outq for a
> printer used by many people.  There's no real need for any user to be using
> the CLROUTQ command or choosing option 14 from WRKOUTQ.  What we would like
> to do is to log the user-id of people trying to do this and give an error
> message to any non-MIS people.
>
> My boss initially suggested creating a modified CLROUTQ command that was
> higher in the library list than the system command.  Over the weekend I
> started wondering if an exit program could do the job.  I've never
> attempted an exit program before but wouldn't mind learning.  I've seen
> examples for FTP and Telnet in the archives but can they be added for any
> command?
>
> I would appreciate any advice.  Thanks.
>
> Dave Parnin
> Nishikawa Standard Company
> Topeka, IN  46571
> daparnin@xxxxxxxxxxxxxxxxxx
>
>
> _______________________________________________
> 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.