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

RE: Setting up user security on development machine

As some said, CHGLIB CRTAUT(...) where CRTAUT is currently set to *SYSVAL. 
 Which is set by WRKSYSVAL QCRTAUT.
You can:

- CHGSYSVAL QCRTAUT *EXCLUDE.  But a user wouldn't even be allowed to sign 
on to an automatically created display without being granted access.  If 
that's ok with you, so be it.

- CHGLIB CRTAUT(*EXCLUDE) and then only new objects created in that 
library will have *public *EXCLUDE.

- One that I like is to create a new authorization list.  Change *public 
to *exclude in the authorization list and then CHGLIB CRTAUT(NewAutl). 
That assigns the new authorization list to any new objects created in that 
library.  Then it's easier to change object security, locked or not.


Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
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.