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

[Bruce Vining <bvining@xxxxxxxxxx>]

The QIBM_QCA_CHG_COMMAND exit would seem to be a good fit for what you are
looking to do.  This exit is documented in the Program and CL Command
category of System APIs under Command Analyzer Change.  The exit program
will run in the job using the CLROUTQ command (including WRKOUTQ option 14)
and so you could retrieve the current user id for the job and log that
information.  You could also optionally replace the CLROUTQ command and so
stop the user from clearing the output queue (or just let the CLROUTQ
continue by setting the 3rd parameter to 0).



                                                                           
             "David A Parnin"                                              
             <daparnin@coopers                                             
             tandard.com>                                               To 
             Sent by:                  midrange-l@xxxxxxxxxxxx             
             midrange-l-bounce                                          cc 
             s@xxxxxxxxxxxx                                                
                                                                   Subject 
                                       Restrict CLROUTQ--A good use for an 
             05/10/2004 11:27          exit program?                       
             AM                                                            
                                                                           
                                                                           
             Please respond to                                             
             Midrange Systems                                              
                 Technical                                                 
                Discussion                                                 
                                                                           
                                                                           




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.