  Reloading (test) system (network) environment? 
 The Question is:
 
How can I automate the configuration of NET$CONFIGURE and UCX$CONFIG.
We have two different applications running on two different Alpa-servers.
Regulary we want to test changes made in the applications so we have a third
server we can use as a "test-server" and restore a full-backup on that
server. We have automate the most
 of the configuration but because we want to have the server in the same
network we have to change also the Decnet-adress and IP-adress etc. with
Net$configure and Ucx$config. Is there a way to automate this without typing
the every field each time.
 
 
 The Answer is:
 
  The OpenVMS Wizard generally finds it valuable to have a clean OpenVMS
  environment, and the ability to use a PCSI kit or (less desirably) a
  VMSINSTAL kit or (least desirable) a DCL script to load the application
  onto the target system environment.
 
  The OpenVMS Wizard would recommend two "template" system disks (and
  image copies for restoration) with the appropriate application startup
  "hooks" in place, and restore the application-specific information to
  an alternate disk.
 
  Alternatively, use the same system disk copy, but use two (or more)
  system roots.  (Each root on the test system would have its own DECnet
  and IP address, its own associated network database, and its own
  associated system parameter database.  The console BOOT command would
  then select the particular system environment needed.
 
  NET$CONFIG, UCX$CONFIG, and TCPIP$CONFIG do accept parameters...
 
