× 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.


  • Subject: Re: Level 40 security from level 30
  • From: "Bruce Odum" <bodum@xxxxxxxxxxxx>
  • Date: Mon, 15 Dec 1997 18:11:09 -0500

This is a brand new system we are in the process of setting up.  I dont
think we have changed QSYS or QUSRSYS.  This system will be connected to the
internet also so is it wise to make this change?
I will look at creating a permanet pool of virtule devices and the
pre-authorize method but I will have to fig that one out. I have never tried
that.

>Just a guess, but at the same time that you went from Level 30 to Level 40,
>did you also change the default public authority for library QSYS or
QUSRSYS
>to *USE?  The symptoms you describe (not authorised to device) remind me of
>what happens when folks do not have *CHANGE authority for devices and
>message queues.  One way around this is to create a permanent pool of
>virtual devices and pre-authorize users to those devices.
>
>If that's not it, send a copy of the error message and I can dig a little
>into this communications security FAQ folder I've been constructing.
>
>

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


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.