Fiddling with the system ID is a NOGO when having many VM systems: the system ID is the often checked by various execs. And, yes, some execs use IDENTIFY, other programmers uses CP Q USERID, so SYSTEM NETID and SYSTEM CONFIG must set the same system ID. What we did was storing a file on AUTOLOG1 while taking the disaster backups. When the file is found, AUTOLOG1 would prompt the operator to tell if it was an IPL after a disater or not.
2008/7/10 John Franciscovich <[EMAIL PROTECTED]>: > > >And a corollary to that question... > > > >I know the system config can have a "say" command. > >But is there also a "stop" or "exit" or "abort"? > >i.e. is there a way to say whoa, this system config does not belong on > >this CPU - I'm not where I wanted to be! - disable wait me? > > Marcy, > > There is no "stop", "exit", or "abort", but if you use different > system identifiers (which are defined by CPU) > you can use a combination of record qualifiers and > IMBED statements (to make the record qualifiers less tedious) to cause > only the relevant statements to be processed for each system. > > For example, with system identifiers DTEST and DREAL: > > DTEST: IMBED DISTEST CONFIG > DREAL: IMBED DISREAL CONFIG > > DISTEST CONFIG and DISREAL CONFIG are separate config files with > statements that are unique to one system or the other. > > If this applies to only a few statements, you can just put them all in > the same config file and use a record qualifier on each statement > that is unique to one system or the other. > > John Franciscovich > z/VM Development -- Kris Buelens, IBM Belgium, VM customer support
