RE: A WRKOUTQ with fewer options

Alternatively: Consider just restricting the commands that change or delete
out queues? Then if they do those options they will be stopped by the OS.
Many auditors (the ones that can spell IBM i without being spotted the "I"
anyway) are asking for those commands to be restricted since one could send
confidential output to places unknown somewhat easily with that authority.

--
Jim Oberholtzer
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
dlclark@xxxxxxxxxxxxxxxx
Sent: Tuesday, October 22, 2019 10:32 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: A WRKOUTQ with fewer options

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 10/22/2019
11:28:26 AM:

I'd like to give some support people access to WRKOUTQ, but without
some of the options in the "Work with All Output Queues" screen.
This is the screen displayed if you do a WRKOUTQ and hit enter.
These operators do not have command line access. We'd like them to be
able to hold and release queues, but not reconfigure them with options
like 2=Change, 4=Delete, or 8=Description. I'm trying to avoid
recoding all the screen logic in my own program just to remove some of
these options. Is there a trick I might use to disallow some of these
options but allow others?

To the best of my knowledge, the easiest way is to code your own UIM
panel to front-end the WRKOUTQ command. That of course presumes that
you don't have to learn all about UIM in the first place. ;-) There
is a UIM application on the wiki to give you a head start doing this.


Sincerely,

Dave Clark