On Friday, 08/01/2008 at 10:01 EDT, Rob van der Heij <[EMAIL PROTECTED]> wrote:
> I am thinking it would be a neat idea to put the XAUTOLOG as CP > commands in the directory entry. > > :soapbox. > It may be too late, but &deity should done RACF startup the other way > around: change CP to start a new AUTOLOGx at IPL that will bring up > RACFVM, and have RACFVM start AUTOLOG1 as the customer had it > before... > :esoapbox. Been there. Thought that. The correct way to do this is to identify ALL of the required ESM servers in SYSTEM CONFIG. When all ESMs have signalled "Ready" to CP, then CP starts AUTOLOG1. In the event of a timeout, CP issues a message skips starting AUTOLOG1. And while I'm halucinating, I would have a command that adds and deletes users from an autolog list. The list is in the warm start area. No requirement for AUTOLOG1 unless you want it. Oh, and the autologs would be paced to ensure that the system is not brought to its knees during IPL. And I want a pony. Alan Altmark z/VM Development IBM Endicott
