Why not indeed

2010/7/29 Frank M. Ramaekers <framaek...@ailife.com>

> That brings up another question, can AUTOLOG1 have a password of
> AUTOONLY?
>
>
> Frank M. Ramaekers Jr.
>
>
>
> -----Original Message-----
> From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
> Behalf Of Alan Altmark
> Sent: Thursday, July 29, 2010 7:34 AM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: AUTOLOG2?
>
> On Thursday, 07/29/2010 at 08:11 EDT, "Frank M. Ramaekers"
> <framaek...@ailife.com> wrote:
> > Why is there an AUTOLOG2?  My system came defined with one, but the
> 191(A) disk
> > is empty.   (Back in my old VM/ESA days there was not AUTOLOG2
> although
> there
> > was an AUTOLOG1.)
>
> It is used by RACF (and maybe other ESMs - I don't know).  AUTOLOG1
> brings
> up RACF.  RACF brings up AUTOLOG2.
>
> This pre-dates the ability to configure the autolog user ID in SYSTEM
> CONFIG.  Using a more modern view, installing an ESM would cause you to
> change SYSTEM CONFIG to contain
>  SYSTEM_USERIDS STARTUP RACFVM AUTOLOG
> and RACFVM would bring up AUTOLOG1.
>
> But there is no way to configure RACF to bring up AUTOLOG1, so that
> would
> have to be addressed.  I've never gotten a complaint about the
> AUTOLOG1/2
> issue, so I haven't worried about it.
>
> There is still an outstanding requirement that IBM provide some sort of
> data in the default user directory that will more easily allow you to
> identify IBM-generated user IDs and their purpose.
>
> Alan Altmark
> z/VM Development
> IBM Endicott
>
> _____________________________________________________
> This message contains information which is privileged and confidential and
> is solely for the use of the
> intended recipient. If you are not the intended recipient, be aware that
> any review, disclosure,
> copying, distribution, or use of the contents of this message is strictly
> prohibited. If you have
> received this in error, please destroy it immediately and notify us at
> privacy...@ailife.com.
>



-- 
Kris Buelens,
IBM Belgium, VM customer support

Reply via email to