Question

  Asked: Apr 17 2008   2:29 PM GMT
  Asked by: Mrkellam1


Outq Management


OUTQ management, OUTQ security, WRKOUTQ

I have a system with more that 100 outqs on it. When a user types "wrkoutq" they get a list of all the outqs.
Is there a way to not only restrict what outqs are accessible by what users, but control what outqs are visible by user groups.
most users only need to see their 2 or 3 outq they use.
Even if it's not an OS400 security config, maybe a third party utility.
I want to be able to control this.
Any suggestions would be appreciated.
Thanks.

Subscribe to Alerts! Get questions and answers delivered to your Inbox.


E-mail me updates on this question



   SUBSCRIBE

hidden modal window

Answer Wiki (Improve, edit or add to this answer)


 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0



Unfortunately WRKOUTQ doesn't appear to check authorities concerning the *OUTQ prior to displaying the list. Authority checking does come into play if the user tries to work/display/etc an *OUTQ, but you want to stop the *OUTQs from showing up initially.

I don't keep track of 3rd party offerings very well and so I can't help you there, hopefully someone else will be able to. If you don't find one that meets your need I could certainly provide one though for a reasonable cost :-)

If you would like to build your own solution, the List Objects API could be used to get a listing of all *OUTQs on the system. From there you could subset the list based on a file, keyed by the current user name, containing the list of *OUTQs to not show. Alternatively you could have a file of what the user is supposed to see and have your program read and display those entries. In either case your program could then call the appropriate CL command or API to implement the various functions of WRKOUTQ.

Bruce Vining
http://www.brucevining.com/
Providing integrated solutions for the System i user community

Another suggestion is to create the output queues in different libraries and then using library lists perfrom the wrkoutq *libl/*all for that user. This is a non programmable way around this but it will mean a lot of management in setting up specific library list groups for each group of user

Bruce B. lovemyi
  • AddThis Social Bookmark Button

Browse more Questions and Answers on AS/400.

Looking for relevant AS/400 Whitepapers? Visit the Search400.com Research Library.


Discuss This Answer


You must be logged-in to discuss a question. Log-in/Register