1 AUTOGEN
 This procedure is a collection of 4 subprocedures which attempt to
 configure a VMS system for a site's hardware environment and its
 typical user needs.  The format of the procedure command is:

	@SYS$UPDATE:AUTOGEN  [subproc]

 where the subproc parameter selects the subprocedure to be invoked.

 Typical procedure is to do an AUTOGEN CONFIG followed by GENPAR.
 The PARAMS.DAT file may then be editted to specify explicit values
 for system parameters (lines with <name>=<value>).  Then AUTOGEN
 is invoked (with or without REBOOT or SHUTDOWN) to update the
 system parameters and files.

2 Subprocedures

 <none>     Updates the current system parameters and files and
            creates a parameter file named SYS$SYSTEM:AUTOGEN.PAR
            using the results of a previous AUTOGEN GENPAR operation.

 CONFIG     Used to determine the current hardware configuration.
            Writes a new SYS$SYSTEM:CONFIG.DAT file.

 SAVE       Used in an upgrade to propogate a previously running
            systems requirements into the new system.

 GENPAR     Used to normalize values coming from an upgrade and
            a new installation and produce a user editable
            requirements file. Creates a new SYS$SYSTEM:PARAMS.DAT
            file.

 SHUTDOWN or
 REBOOT     Used to process a user requirements file into sysgen
            parameters, installed image list, and paging, swapping
            and dump files then either reboot or shutdown the system.
1 BOOTUPD
 This procedure updates the bootstrap image on the console device.
 The VMS bootstrap file VMB.EXE on the console storage device will
 be replaced from the copy stored in SYS$SYSTEM:.  It is assumed
 that the current default device is the system device.  The format
 of the command is:

	@SYS$UPDATE:BOOTUPD

 Note that the console storage device CSA1: is used directly.
1 DYBOOTUPD
 This procedure updates the bootstrap image on a console floppy.
 The VMS bootstrap file VMB.EXE on the console floppy will be
 replaced from the copy stored in SYS$SYSTEM:.  It is assumed
 that the current default device is the system device.  The format
 of the command is:

	@SYS$UPDATE:DYBOOTUPD

 Note that the console floppy must be placed in DYA0:.
1 CONSCOPY
 Save or Restore a console medium.

 This program saves or restores a console medium.  It uses the
 compatibility mode utility FLX to copy and re-format files between
 a user medium (Files-11 format) and a console medium (RT-11 format).
 The command format is:

	@SYS$UPDATE:CONSCOPY  kit  func  f11dev  cnsdev  [boot]

2 Parameters
kit
  VMS kit type: 780 or 750 or 730.
func
  Function: SAVE or RESTORE.
f11dev
  Files-11 device and directory.
cnsdev
  Console device drive in the format "ddcu:".
boot
  File to be written on the bootblock of the console medium (optional).
  The defaults are:
       780 - CONSOL.SYS
       750 - BOOT58.EXE
       730 - BOOT.EXE
1 DIRCLENUP
 This command cleans up dangling directory entries on a Release 2 system.
 The format of the command is:

	@SYS$UPDATE:DIRCLENUP  device

 where the parameter is the name of the device that is to be cleaned up.
 If this parameter is not specified, then the user is prompted for the
 information.
1 LINEPAGE
 This procedure will patch the number of print lines per printer page
 used by certain compatibility mode utilities in their listing formats.
 The format of the command is:

	@SYS$UPDATE:LINEPAGE  [lines]  [data_file]

 The lines parameter gives the number of lines on a printer page (this
 is 66 in the United States by default).  The data_file parameter gives
 the file specification of the data file with the fix information.  The
 default for this is SYS$UPDATE:LINEPAGE.DAT.
2 Data_file
 The format of the data file is as follows:

	*CRF
	25:110/63
	25:422/63

 The "*" must be in column 1, the file name contains no device
 directory, file type, or version. SYS$SYSTEM:.EXE is assumed.
 the numbers in the patch lines MUST all be OCTAL.  The first
 two numbers are the virtual block number and byte within that
 block, the 3rd value is that which appears in the standard
 image when a 66 line-per-page printer is used.  In the case of
 CRF above, that value is 63 octal (51 decimal).  The patch files
 may be concatenated as they are in LINEPAGE.DAT.
1 SETDEFBOO
 Command file to set default boot command file.  The format of the
 command is:

	@SYS$UPDATE:SETDEFBOO  [cpu_type]

 The optional parameter determines the CPU type from the table:
	1 - 11/780
	2 - 11/750
	3 - 11/730
1 STABACKIT
 This command procedure builds a standalone BACKUP kit on floppies,
 TU58 cartridges, or a disk. The format of the command is:

	@SYS$UPDATE:STABACKIT  tgt_dev  [tgt_dire]  [source]

 The SETPRV privilege is required to use this command procedure and
 you must also have write access to SYS$UPDATE:.
2 Parameters
tgt_dev
  Target device, assumed online with no media mounted.
tgt_dire
  Optional target directory, defaults to [SYSEXE].
source
  Optional source device and directory, defaults to SYS$SYSTEM:.
1 SWAPFILES
 Modify the sizes of the page, swap, and dump files.

	@SYS$UPDATE:SWAPFILES

1 VMSINSTAL
 Install new software on VAX/VMS Version 3.0.
 This command procedure installs software onto a VAX/VMS system.

	$ SET DEFAULT SYS$UPDATE:
	$ @VMSINSTAL  [product]  [keyword]

 The distribution kit is expected to contain a saveset, which will be
 restored onto the system disk in the directory [SYSUPD.saveset_name].
 Once the files are restored, a command procedure (saveset_name.COM)
 will be invoked to perform the product-specific installation.

 The privilege SETPRV is required.
2 Parameters
product
  The name of the product being installed (which
  is used by this procedure as the name of the saveset to
  restore).  If this parameter is defaulted, the volume label
  on the installation kit is used as the name of the saveset.
  defaulted, VMSINSTAL will prompt for it.
keyword
  Keyword DETAILOR or RETAILOR.  DETAILOR should be specified
  before an update or installation is performed on an RL02
  system disk.  RETAILOR should be specified after an update
  or installation has completed on an RL02 system disk.
1 VMSKITBLD
 Build or Copy VAX/VMS binary distribution  kit for Release 3.
 This command file allows the invoker to create a system disk or copy a
 system disk.  The transfer can occur between any of the disk types sup-
 ported in Release 3.  For small disks (e.g. RL02) the saveset select
 feature allows distribution over several volumes.

 This command file will also create a bootblock on the target disk.  This
 This is done by WRITEBOOT, and requires LOG_IO privilege.

 There are  eight parameters which  control the kit build procedure.  Some
 or all of these parameters may be specified as input.

 $ SET DEFAULT SYS$UPDATE
 $ @VMSKITBLD filespec mask source target select midnite copy options

2 Parameters
filespec
  The file name of the data file to use for the procedure.
	Default = SYS$UPDATE:VMSKITBLD.DAT
mask
  The mask to use for determining whether to transfer each
  individual file.
source:[source_topsys]
  This specifies the source disk from which the kit will be built,
  and the associated top level system directory if any.
  If SOURCE_TOPSYS is defaulted, then the source device is checked
  to see if it has a SYS0 topsys.  If it does, then SYS0 is the
  the default, if not then NONE is the default.
target:label[target_topsys]
  The target disk, its associated top level system directory,
  and the target disk label to which the kit will be built.
  If TARGET_TOPSYS is defaulted, then it is assumed to be SYS0.
  An explicit "NONE" is required to produce a "flat" system.
select
  Savesets to be output.  One of: REQ, LIB, OPT, ALL, or EDTCAI.
  By default ALL files are transferred to the output device
midnite
  This parameter is set to one of either R,E, or D depending
  on whether a MidNite system is being built or not.
	R - Required file set only.
	E - Set for an execution only system.
	D - Set for a full development system.
copy
  This parameter specifies whether to BUILD, ADD, or COPY..
  BUILD - Initializes a new volume or volume set and creates all
          the necessary directories from scratch.
  ADD   - This is the new feature that puts a new system in a new
          set of directories on an existing volume which presumably
          contains other systems on it.  The TARGET_TOPSYS should
          be a new top level system directory.
  COPY  - Copies the kit files to an already existing set of
          system directories.  It will not create the directories.
options
  This parameter is a comma separated list of options:
  NOPROMPT - Indicates that the user should not be prompted with
             "device ready" questions.  Command procedures which
             invoke VMSKITBLD with known device status set this switch.
2 Data_file
 This command procedure uses as input a data file (specified in P1 or
 defaulted to [SYSUPD]VMSKITBLD.DAT on the system disk).  The data file
 is read as input commands to be executed by the procedure.  The format
 of each record in the data file is as follows:

    1) If the record begins with a "$" (dollar sign), then the record is
       submitted directly as a DCL command line.
    2) The remainder of the records have the following fields defined:
       NOTE: The fields can be in any order.

	NAME,OP=op,SET=set,COND=mask,MID=flags,CAT=tailorgroup

3 NAME
 The name of the file to be copied.  Must include the extension
 but not the version.
3 OPERATION
 The action to be performed on the file.
 If null, then build/copy the file normally, otherwise one of:
4 BUILD
 Transfer the file during build only.
4 SET
 Set the default directory to NAME for the succeeding transfers.
4 CREATE
 Create a directory entry called NAME (build only).
 The "SYNONYM="  field specifies an alternate directory name
 to be entered as a synonym to NAME.
4 ENTER
 Make a directory entry for file NAME (build only).
4 COPY
 Transfer the file during copy only.
4 CONTIG
 Make the destination file contiguous.
4 RENAME_B
 Rename a file just copied to the target disk.  In a rename
 operation, the data record also contains the field
 DEST=new_file_name.  Only used for BUILD and ADD operations.
4 RENAME_C
 Same as RENAME_B except used for COPY operations.
4 SYSGEN
 Create the sysgen files (build only).  If NAME is null, then
 use the default SYSGEN file sizes depending on the target
 disk type.  If NAME is not null, create the SYSGEN file specified
 in NAME, and use the FILESIZE= field of the record to specify
 the file size.
4 WRITEBOOT
 Write a bootblock on the target device.
3 SAVESET
 Chooses a subset of files to copy to the target device.
 This parameter is used for building Release 3 distribution kits.

	REQ - required saveset
	LIB - library saveset
	OPT - optional saveset
	EDTCAI - edtcai saveset
	ALL - all savesets
3 CONDITIONAL 
 The value to be ANDed to determine whether or not to copy/build
 this file:

	1,2,4  -  UETP
	8  -  HELP files
	16  -  F4P, FORTRAN
	32  -  BASIC +2
	64  -  DECnet
	128 -  BLISS32 and .L32 files
	256 -  coding examples
	512,1024  -  VMS development only, not for REL 3 kits
	2048 - files needed to build VMS distribution kits

 All others undefined.
3 CATEGORY
 The tailoring group(s) to which this file belongs.  This field is
 used by [SYSBLDCOM]TAILORBLD.COM to create the tailoring group files.
1 VMSTAILOR
 Tailor a VMS software configuration
 This command procedure tailors VMS software configurations
 on tape or disk media.

 This facility is restricted to VAX-11/730 dual RL02
 configurations for VAX/VMS Version 3.0.

1 VMSUPDATE
 This procedure is used to perform a VMS update or install optional
 software.  The installation media are mounted (as requested) in the
 console device.  The procedure is invoke by:

	SET UIC [1,4]
	SET DEFAULT SYS$UPDATE
	@VMSUPDATE

1 DYVMSUPD
 This procedure is used to perform a VMS update or install optional
 software.  The installation media are mounted (as requested) in the
 RX02 drive DYA1:.  The procedure is invoke by:

	SET UIC [1,4]
	SET DEFAULT SYS$UPDATE
	@DYVMSUPD

