To be more explicit,

You CAN test before hand to see if you can go to level 40 without
problems.

You CAN NOT test before hand to see if going from 40 to 50 will cause
any problems.

In the manual: 

"Most of the additional security measures that are enforced at security
level 50 do
not cause audit journal entries at lower security levels. Therefore, an
application
cannot be tested for all possible integrity error conditions prior to
changing to
security level 50.

The actions that cause errors at security level 50 are uncommon in
normal
application software. Most software that runs successfully at security
level 40 also
runs at security level 50.

If you are currently running at security level 40, you can change to
security level
50 without extra testing. Security level 50 cannot be tested in advance.
The
additional integrity protection that is enforced at security level 50
does not produce
error messages or journal entries at lower security levels."


HTH,


Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
  

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
> Sent: Wednesday, December 14, 2005 5:10 PM
> To: Midrange Systems Technical Discussion
> Subject: RE: Security level 50
> 
> Actually there is an easy way to check if your machine will 
> hurl.  There's 
> like a trial mode by turning on some authority notifications. 
>  They won't 
> halt anything but they will tell you what will stop working 
> if you do go 
> to level 40 or 50.  Run that way for a month or so should 
> cover about all 
> applications.
> 
> Rob Berendt


This thread ...

Follow-Ups:

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

This mailing list archive is Copyright 1997-2020 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].