|
The thing about the audit journals is that it will even tell you things that work fine now, but will fail when you go to level 40 or 50. However, I am not so sure that you'll get the same results in going to level 30 from level 20. If you're going to make the jump to level 30, you might want to check the journals for level 40 or 50 errors and just jump to one of those levels. You should be ok unless you're using some obscure package that hasn't been updated to stop using those leaks. If so, the journal entries will point it out to you. You could just try starting the journalling and see what happens. At best it will let you know certain objects the person would not have had access to and you can start adding authorization lists, etc., before you jump to plus 20. At worst, it won't tell you squat and you'll just have to clean up the journal and receivers. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin kirkg@xxxxxxxxxxxxx Sent by: midrange-l-bounces@xxxxxxxxxxxx 09/04/2003 03:43 PM Please respond to Midrange Systems Technical Discussion To: midrange-l@xxxxxxxxxxxx cc: Fax to: Subject: Going to level 30 Security It been a long since I've needed to do this... I thought I remembered there was a way to use the audit journals to test what will happen when you move from security level 20 to 30 or higher. I've been able to find a tip that says basically going 20 to 30 is by setting up test profiles. I've also found a tip of going from 30 to 40 that does use the audit journal using the *PGMFAIL option. Is there a better way to get from 20 to 30 other than by trial and error? _____________________ Kirk Goins CCNA Systems Engineer, Manage Inc. IBM Certified iSeries Solutions Expert IBM Certified iSeries e-Business Infrastructure IBM Certified Designing IBM e-business Solutions Office 503-353-1721 x106 Cell 503-577-9519 kirkg@xxxxxxxxxxxxx www.manageinc.com _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.