As an addendum: I do soemthing similar with my LINUX guests. They all have a common PROFILE EXEC which reads config files to determine what VDISKS to setup for the userid and what IPL command to use. It also look s for userid specific EXECs to do any special setup that guest might need.
Brian Nielsen On Thu, 25 Jan 2007 09:00:13 -0600, Brian Nielsen <[EMAIL PROTECTED] > wrote: >After retrieving the system name, which others have shown how to do, use >it as the filename of a file containing the linux guests that should be >brought up on that system. Benefits over coding them directly in the >autolog PROFILE are that you only touch the code once (thus reducing the >likelyhood of a syntax error terminating the exec), and the PROFILE >becomes common code across all systems. > >Brian Nielsen > > >On Thu, 25 Jan 2007 08:34:04 -0600, Mary Anne Link ><[EMAIL PROTECTED]> wrote: > >>Does anyone have an autolog profile exec that contains some logic to >autolog >>different servers based on what system you are on? We are trying to get >to a >>point where we can quickly copy the res pack to other systems, and, based >on >>the system config fn specified on salipl, ipl a copy of that res pack t o >>bring up different systems. >> >>Ideally what I'm looking for is a command that will retrieve the system >name >>(which I can't seem to find) and then I can start different linux guest s >>based on that system name. >> >>Also, aside from system config, the tcpip files (which use system name) , >the >>autologs, and having to keep all users in the user direct, can anyone >think >>of any snags in my plan? >> >>Thanks, >>Mary Anne (A VM newbie) >>======================== ========================= =======================
