Re: Lvl 20 to 40

At 10:33 PM 8/21/97, Matthias wrote:
>To change security levels from 20 to 40 I assume it is safer to take it
>in steps, first to 30, then to 40.
>Would anyone have any hints or tips about going from 20 to 30? Are
>there any traps to avoid?
>The security reference is a bit vague on the subject.
>Thanks,
>Matthias

I agree with making the change in steps. We are at 30 and will probably
stay there. The reasons have to do with MI restrictions at 40.

We have Hawkeye Pathfinder (cross-reference tool) that uses fast MI
routines at 30 and slower CL (or even API) stuff at 40. Performance makes a
huge difference here.

We also use a wonderful little utility called FNDMBR, which will not work
at all at 40, again because of the MI routines.

In out case, we don't really NEED level 40, so we will, as I said, probably
stay at 30.

By the way, you can turn on certain kinds of security auditing that will
tell you the impact of moving to the higher level, without having actually
to do it.

Also, you might want to look at the manual 'Tips and Tools for Securing
Your AS/400'. It has great information for all kinds of situations. It goes
along with a Security Toolkit and various security PTFs. The toolkit is
free. I'll follow up later with the details for ordering.

Cheers
Vernon Hamberg
System Software Programmer
Old Republic National Title Insurance Company
400 Second Avenue South
Minneapolis, MN 55401
(612) 371-1111 x480
+---
| 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 MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---