× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. July 2001

RE: OUTQ Security

  • Subject: RE: OUTQ Security
  • From: "Weatherly, Howard" <hweatherly@xxxxxxxxxxxx>
  • Date: Fri, 27 Jul 2001 08:16:21 -0400
Why not create a separate outq for this application and just give the 6 or so users authority to that outq thru an authorization list ?
 
Check out the CRTOUTQ command, I suspect this will accomplish what you want with little pain to anyone, the current users will not even notice and the users in the group for the new outq will get what they need.
-----Original Message-----
From: KirkG@PacInfoSys.com [mailto:KirkG@PacInfoSys.com]
Sent: Thursday, July 26, 2001 19:27
To: midrange-l@midrange.com
Subject: OUTQ Security


I have a client that somewhere in the past has given the majority of the users *SPLCTL authority so they can control there own outqs/writers etc. Now they have a new app that they want to secure the output to only 6 or so users. From what I can read *SPLCTL trumps most if not all security placed on the outq.

The 1st step appears to remove *SPLCTL and to change *PUBLIC to *EXCLUDE but then what is the best way to allow users to control selected outqs?

Grant each user specific authority to the outq, AuthorityList?  ??

---------------------------------
Kirk Goins
IBM Certified AS/400 Technical Solutions
DataMirror High Availability Certified
Pacific Information Systems - An IBM Premier Business Partner
503-674-2985             kirkg@pacinfosys.com
"WE KNOW TECHNOLOGY"
---------------------------------

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.