Preparing a Base Group for a Remote System

If you are creating a CSLT for distribution to another system, HPINSTAL allows you to include your own installation-specific system files on the CSLT. You can specify these files in a base group. The base group must be a valid configuration group created using SYSGEN.

You only need to create a base group if creating a CSLT for a remote system because if you are updating the system you are on, any system files you have added will remain there. The only way to add system files to a remote system would be to put them on the CSLT.




	NOTE: The procedure for preparing a base group is not required in all cases. Unless you are certain that you need to add your own system files to the CSLT, use the default configuration group specified by pressing [RETURN] at the prompt requesting the base group. Then HPINSTAL creates a default configuration group based on the current configuration group (of the system you are working on).

To create the base group:

Determine which group to use as a source for the base group. You'll probably want to choose the default factory configuration group corresponding to the model number of the target system. (For example, if the target system is a 995, start with confg995.)
Determine a name for the group to use as the base group on the remote system.
NOTE: The remote system base group can never be used as a Release 4.0 configuration.
Use the Release 5.5 version of SYSGEN to create the base group for HPINSTAL to use:
1. Set up file equations to point to the Release 5.5 SYSGCAT and CATALOG:
  :FILE SYSGCAT.PUB.SYS=SYSGCAT.INSTALL.SYS :FILE CATALOG.PUB.SYS=CATALOG.INSTALL.SYS
2. Run the Release 5.5 SYSGEN to create the base group:
  :RUN SYSGEN.INSTALL.SYS

The following example shows using SYSGEN to create a base group. It uses CONFG995 as the source for the configuration group for the remote system, which is an HP 3000 Model 995. The base group for the remote system is called CUSTCONF. Note that CUSTCONF does not have to exist prior to running SYSGEN. The base group should be named a group name of your choosing that does not conflict with the names of the default configuration groups.

:RUN SYSGEN.INSTALL.SYS
SYSGEN version D.01.01: catalog version D.01.00 TUE, MAR 22,
1994, 1:32 PM
Copyright 1987 Hewlett-Packard Co. All Rights Reserved.
 
WARNING
no NMCONFIG file in this configuration.
 
WARNING
NMCONFIG.PUB.SYS is now the NMCONFIG file
 
First level command
   io log (lo)    misc (mi)    spu (sp)     sysfile (sy)
   basegroup (ba) keep (ke)    permyes (pe) show (sh)   tape (ta)
   clear (cl)(c)  exit (ex)(e) help (he)(h) oclose (oc)  redo
sysgen> BASEGROUP CONFG935
sysgen> sysfile
 
SYSFILE configurator commands
   aauto (aa)    aboot (ab)   acmsl (ac)   asprog (as)
   cmsl (cm)     dauto (da)   dboot (db)   dcmsl (dc)
   dsprog (ds)   lcmsl (lc)   rauto (ra)   rboot (rb)
   rcat (rc)     rcmsl (rcm)  rdcc (rd)    ripl (ri)
   rnmlib (rn)   rsprog (rs)  show (sh)
   clear (cl)(c) exit (ex)(e) help (he)(h) hold (ho)
 
sysfile> ASPROG sys_program_name sys_filename
At this point, you can use the ASPROG command to specify the
names of the system files to add to the CSLT. Use the DSPROG
command to delete files from the group.
...
sysfile> HOLD
sysgen> KEEP CUSTCONF
Be sure to keep the changes in a group name of your choosing.
 
configuration files successfully saved
sysgen> EXIT
END OF PROGRAM

Preparing a Base Group for a Remote System

Technical documentation

» Table of Contents

» Glossary

» Index