Re: [MI400] permanent spaces

["srichter " <srichter@xxxxxxxxxxxxxxxxxx>]

---------- Original Message ----------------------------------
From: "Leif Svalgaard" <leif@leif.org>
Reply-To: mi400@midrange.com
Date: Sat, 20 Oct 2001 20:33:59 -0500

>I didn't have time to do all combinations,
>but a system-state program creating a permanent
>space with CRTSP does in fact NOT create a journal
>entry. This is news to me. I'm running (as always) at level 50.
>Aren't you? :-)
>

I never use the CRTS or CRTINX instructions. Always the api's. Are they in the 
MI manual? So I dont even have the instruction template specs.

I dont think the sysp to the object having authority to it has anything to do 
with this. The idea is that you want the audit journal to show all crt, dlt and 
moves of objects on the system.  It is possible to compromise a system by 
creating an object with the same name as a production object and placing the 
new obj ahead of the prod obj in the libl of a job. With auditing on, you can 
at least see a record of this devious activity. If the object is a space or 
index and CRTS or CRTINX is used to create the obj, than there is no audit 
journal record that the object was created.

Again best guessing, security auditing is at the OS400 level, not the VLIC 
level. So CRTS and CRTINX run below OS400 and above VLIC and its use will not 
be audited.

-Steve