× 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: QSECURITY Level 40
  • From: Rob Berendt <rob@xxxxxxxxx>
  • Date: Wed, 14 Jun 2000 14:43:13 -0500

Well Bryan, did you find entries in your journal?





srprog3@co.collin.tx.us on 06/14/2000 02:27:32 PM
Please respond to RPG400-L@midrange.com@Internet
To:     RPG400-L@midrange.com@Internet
cc:      
Fax to: 
Subject:        Re: QSECURITY Level 40



Ted Barry wrote:

> Is there a URL out there that shows step by step the requirements for
> changing from QSECURITY 30 to 40?  Pros/Cons?  Anyone who's gone
> through this?  Is it worth it?

I don't know about a URL but you can go to the AS/400 Security Refernce book
(SC41-5302) and look at chapter 2 "Using System Security (QSecurity) System
Values which details changing to level 40.  This book is available online at the
as400 site if you don't have it in your shop.  IBM also has a security advisor
wizard at http://www.as400.ibm.com/tstudio/secure1 that will give you security
change suggestions based on your system configuration

>
>
> I know this has been kicked around before on this list, but I'm thinking
> about turning it on this weekend.  Is there enough time to get ready
> (two/three days)?

Not a good idea.  You should change the QAUDLVL system values to journal 
*AUTFAIL
and *PGMFAIL errors.  Then monitor your journals for a while (we did it for 30
days) to see if there are objects that would cause hard failures under security
level 40.

Hope this helps
Bryan


srprog3.vcf


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.