Laser-Scan Ltd

LSL LAMPS Software Installation Guide

Issue 2.0 - 03-Aug-1990
Copyright (C) $$year Laser-Scan Ltd
Science Park, Milton Road, Cambridge, England CB4 4FY  tel: (0223) 420414

Document "LSL LAMPS Software Installation Guide"

Document Issue 1.0      Paul Hardy              18-Mar-1987
Document Issue 1.4      Paul Hardy              04-Aug-1988
Document Issue 2.0      Paul Hardy              03-Aug-1990

LSL LAMPS INSTALLATION GUIDE

INTRODUCTION

Laser-Scan LAMPS is a combination of hardware and software components which together allow use of modern high performance minicomputers and workstations (DEC VAX series) for digital cartography, automated map production, and GIS (Geographical Information System) queries.

This guide is intended to be of use to personnel carrying out an initial LAMPS installation on a new customer system. Note that this will usually be LSL staff with knowledge of LAMPS software, and hence this manual makes considerable assumptions about prerequisite knowledge. In particular, the installer is expected to be familiar with the "LAMPS Software Environment Guide". It is also assumed that the installer is already familiar with general use of a DEC VAX series computer and of the VMS operating system, with some background in VMS system management.

LSL software is divided into packages, and the main ones involved in a basic LAMPS system will be:
LSLSYSTEM LSL software support package
MAPPING Mapping kernel support package
IMP IFF Map Processing package
LITES2 Cartographic editor package
PLOTTING Map plotting package

Other optional facilities might include:
VTRAK Vector automatic digitising
METROPOLIS Land Information System
HORIZON Environmental GIS
STRUCTURE Topological vector structuring
POLYGONS Polygon formation and manipulation
MATRIX Matrix (raster) data manipulation
DTMCREATE Terrain model creation
TVES Terrain Visualisation and exploitation

This manual has a section describing prerequisites for installation, and then a section describing in some detail how to carry out an installation.

Appendix A covers points to consider if installing LAMPS on a VAXcluster or LAVc, where several nodes share a common filestore.

Note that an automated procedure called LSLINSTALL.COM is available to carry out the majority of the steps involved in a LAMPS installation. An example of use of LSLINSTALL on a standalone VAXstation 3100 is supplied as Appendix B to this document.

INSTALLATION PREREQUISITES

To start installation of LAMPS software on an existing VAX or MicroVAX which already has a functioning VMS operating system, the installer needs access to certain resources. The installation procedure in section 3 guides the installer in ensuring the availability of these resources, but they are listed here as an overview.

PREREQUISITE USERNAMES

All LAMPS users must be in the same UIC group, both to allow file sharing and for process synchronisation using shared global sections and common event flags. The UIC group is normally 100, but can be changed if 100 is already in use. The following usernames are always needed. See the automated LSLINSTALL procedure below for details.
[100,2] LSLSOFT is the owner of all LAMPS programs.
[100,100] LSLUSER is a template LAMPS user with ordinary resource quotas
[100,101] LSLBIG is a template user with enlarged quotas for eg DTMCREATE

The following usernames are created as needed.

[100,1] VTRAK is the captive VTRAK user.
[100,3] LSLENG is the owner of all LSL hardware diagnostics.
[100,5] METROPOLIS is the captive METROPOLIS user.
[100,6] HORIZON is the captive HORIZON user.

PREREQUISITE DIRECTORIES

Five root level directories will be created, owned by [LSLSOFT] with corresponding rooted logical names vis:
LSL$PUBLIC_ROOT: -> [LSLPUBLIC...] ! LSL published software (read-only)
LSL$SITE_ROOT: -> [LSLSITE...] ! LSL site-specific software
LSL$USER_ROOT: -> [LSLUSER...] ! LSL users home directories
LSL$DATA_ROOT: -> [LSLDATA...] ! LSL data directories
LSL$LOCAL_ROOT: -> [LSLLOCAL...] ! LSL workspace directories

Conventionally, [LSLPUBLIC], [LSLSITE] and [LSLUSER] which contain mainly static data are often held on the system disk, while [LSLDATA] which contains volatile data files is often on a different disk to equalise disk accesses. [LSLLOCAL] contains temporary workspace files and care should be taken on a VAXcluster satellite that this logical name is redirected to point to a disk which is local to that node. Other than this, the environment is uniform across a cluster.

The LSLINSTALL installation procedure will automatically create these directories and their requisite subdirectories, and set up logical names and search lists to allow LAMPS software to access directories without knowing their exact location.

PREREQUISITE RESOURCES

The basic LAMPS software packages need no elevated quotas or privileges beyond what is normally found on most VAXes. It is however important for efficient operation of LITES2, that per-process working sets are not overly constrained. LSL recommend a working set per process (WSQUOTA) of at least 1000 pages, with 2000 pages preferred if large or complex maps are being edited. This can be reduced slightly if there will be multiple simultaneous users of LITES2 on one node, and the image is installed shared. WSEXTENT should be set (eg 3 times) larger than WSQUOTA to allow working set expansion on lightly loaded systems. The SYSGEN parameter WSMAX must be larger than the largest WSEXTENT in the UAF (limited of course by physical memory size).

Note that some LAMPS packages require extended virtual address space to allow them to handle matrix or structured data. These include the terrain matrix manipulation packages MATRIX, DTMCREATE, and TVES, and also the STRUCTURE and POLYGONS packages. All these packages require that the SYSGEN parameter VIRTUALPAGECNT be set to at least 36000 pages (18MB), and corresponding value of PGFLQUOTA be set for each user in the UAF. Working sets should therefore be correspondingly bigger (eg 3000 pages WSQUOTA).

The VTRAK package has considerably larger requirements for virtual and physical address space in which to hold its large raster datasets. Refer to the VTRAK documentation for more information.

The METROPOLIS and HORIZON packages use relational databases and raster backdrop datasets, and hence also have requirements for enhanced resources. Refer to their documentation for more information.

INSTALLATION PROCEDURE

A command procedure LSLINSTALL.COM is provided as part of the basic LSL system support package LSLSYSTEM to carry out the main steps in LAMPS software installation. The procedure has built in help. As however it is part of the software it is intended to install, some degree of manual bootstrapping is of course required.

The suggested procedure for installation is as follows, in four parts, three as the system manager, and one as the LSLSOFT user.

FIRST PHASE INSTALLATION

This phase is reading of the LSLINSTALL procedure from the LSL distribution media (usually TK50 or =" magtape). In the following examples, this is assumed to be a TK50 tape to be read from device MUA0:. If you are using other media, use the appropriate device name (eg MTA1:) and appropriate media load instructions.

SECOND PHASE INSTALLATION

The next phase involves invoking the LSLINSTALL procedure, which carries out the following stages:
PREPARE - give introduction, and check resources.
USERNAMES - create standard usernames.
ROOTS - create root directories and set up rooted logical names.
LOAD - load and install software issue BACKUP savesets.
DIRECTORIES - create standard site-dependent directories.
FILES - copy standard startup files to destinations.
SEARCHLISTS - setup search lists LSL$EXE:, LSL$COM: etc.
OPTIONS - set up environment for optional software.
TUNE - recommend sensible SYSGEN VMS tuning parameters.

THIRD PHASE INSTALLATION

This phase requires manual intervention to adapt the supplied template startup procedures to suit the site requirements, and to carry out VMS system tuning.

FOURTH PHASE INSTALLATION

This phase requires no special privileges, and consists largely of tailoring the LAMPS environment to customer requirements, and verification of correct installation. Installation of LAMPS is then complete.
APPENDIX
On a Local Area VAXcluster (LAVC), there are multiple VAX, MicroVAX, and VAXstation processors sharing a common filestore. Hence the LAMPS environment needs consideration in such matters as which files are common and which are CPU specific.

The following hints have been found useful, and are based on an example LAVC of a MicroVAX boot node (MVA), a VAXstation 3100 (V3A), and a diskless VAXstation 2000 (VSA).

APPENDIX

        Welcome to VAX/VMS V5.3    

Username: SYSTEM
Password: 
        Welcome to VAX/VMS version V5.3 on node LSLV3O
    Last interactive login on Friday, 13-JUL-1990 09:32
    Last non-interactive login on Friday, 13-JUL-1990 09:32

$!
$! first find the name of our magtape drive
$!
$ SHOW DEVICE M 

Device                  Device           Error    Volume         Free  Trans Mnt
 Name                   Status           Count     Label        Blocks Count Cnt
MKA500:                 Online               0

Device                  Device           Error    Volume         Free  Trans Mnt
 Name                   Status           Count     Label        Blocks Count Cnt
MBA1:                   Online               0
$!
$! now get the LSLINSTALL procedure off the issue tape
$!
$ MOUNT MKA500:/FOREIGN/NOASSIST 
%MOUNT-I-WRITELOCK, volume is write locked
%MOUNT-I-MOUNTED, LSLSYS mounted on _MKA500:
$!
$ BACKUP/LOG MKA500:/REWIND/SELECT=LSLINSTALL.COM SYS$MANAGER: 
%BACKUP-S-CREATED, created SYS$SYSROOT:[SYSMGR]LSLINSTALL.COM;1
$!
$ DISMOUNT MKA500:/NOUNLOAD 
$!
$! now invoke it to carry out the installation
$!
$ @LSLINSTALL 
 
LSL LAMPS software installation procedure V2.0 Try HELP for assistance.
 
LSLINSTALL> HELP 

Commands available are:

HELP            - type this message.
INSTALL         - do complete installation (P,U,R,L,D,F,S,O,T)
PREPARE         - give introduction, and check resources.
USERNAMES       - create standard usernames.
ROOTS           - create root directories and set up rooted logical names.
LOAD            - load and install software issue BACKUP savesets.
DIRECTORIES     - create standard site_dependent directories.
FILES           - copy standard startup files to destinations.
SEARCHLISTS     - setup search lists LSL$EXE:, LSL$COM: etc.
OPTIONS         - set up environment for optional software.
TUNE            - recommend sensible SYSGEN VMS tuning parameters.

Suggested sequence which is done by INSTALL command is:
        PREPARE, USERNAMES, ROOTS, LOAD, DIRECTORIES, FILES, SEARCHLISTS,
        OPTIONS, TUNE

LSLINSTALL> INSTALL 
 
--------------------------------------------------------------
PREPARE - give introduction, and check resources
--------------------------------------------------------------
 
This procedure is used for the installation of LSL LAMPS (Laser-Scan Automated
Map Processing) Mapping and GIS software packages. It is documented in the 
"LAMPS Installation Guide" which is part of the package documentation for the
LSL MAPPING package. 

To run this procedure, you must be logged on as user SYSTEM, as it carries out
the primary system management functions associated with installation of 
LAMPS software, vis:

        - Set up standard usernames for a LAMPS system
        - Load a distribution tape containing the LSL software
        - Create standard site_dependent directories and files
        - Evaluate changes in SYSGEN parameters needed.

The procedure is general enough to cope with installation on most standalone
and turnkey LAMPS systems. It should be noted however, that on complex
pre-existing sites, it may be necessary for the system manager to edit this
procedure to avoid conflicts with assumptions made by previously installed
software packages.

OK to proceed [Y] ?  
 
--------------------------------------------------------------
USERNAMES - Setting up standard LSL usernames.
--------------------------------------------------------------
 
The procedure will create the following standard usernames:
[100,2]   = [LSLSOFT]   ! owner of LSL software
[100,100] = [LSLUSER]   ! template LSL user
[100,101] = [LSLBIG]    ! template large quota user
 
Proceed with this stage [Y] ?  
 
Creating user [LSLSOFT]
 
%UAF-I-RDBADDMSGU, identifier LSL value: [000100,177777] added to rights data 
 base
%UAF-I-ADDMSG, user record successfully added
%UAF-I-RDBADDMSGU, identifier LSLSOFT value: [000100,000002] added to rights 
 data base
%UAF-I-MDFYMSG, user record(s) updated
%UAF-I-MDFYMSG, user record(s) updated
%UAF-I-MDFYMSG, user record(s) updated
%UAF-I-MDFYMSG, user record(s) updated
%UAF-I-DONEMSG, system authorization file modified
%UAF-I-NAFNOMODS, no modifications made to network proxy data base
%UAF-I-RDBDONEMSG, rights data base modified
 
Press RETURN to continue  
 
Creating user [LSLUSER]
 
%UAF-I-COPMSG, user record copied
%UAF-I-RDBADDMSGU, identifier LSLUSER value: [000100,000100] added to rights 
 data base
%UAF-I-MDFYMSG, user record(s) updated
%UAF-I-MDFYMSG, user record(s) updated
%UAF-I-DONEMSG, system authorization file modified
%UAF-I-NAFNOMODS, no modifications made to network proxy data base
%UAF-I-RDBDONEMSG, rights data base modified
 
Press RETURN to continue  
 
Creating user [LSLBIG]
 
%UAF-I-COPMSG, user record copied
%UAF-I-RDBADDMSGU, identifier LSLBIG value: [000100,000101] added to rights 
 data base
%UAF-I-MDFYMSG, user record(s) updated
%UAF-I-MDFYMSG, user record(s) updated
%UAF-I-MDFYMSG, user record(s) updated
%UAF-I-DONEMSG, system authorization file modified
%UAF-I-NAFNOMODS, no modifications made to network proxy data base
%UAF-I-RDBDONEMSG, rights data base modified
 
Press RETURN to continue  
 
       Owner         Username           UIC       Account  Privs Pri Directory

LSL Software         LSLSOFT         [100,2]      LSL      Group   4 LSL$SITE_
ROOT:[LSLSOFT]
LSL LAMPS user       LSLUSER         [100,100]    LSL      Group   4 LSL$USER_
ROOT:[LSLUSER]
LSL LAMPS big user   LSLBIG          [100,101]    LSL      Group   4 LSL$USER
_ROOT:[LSLUSER]
%UAF-I-NOMODS, no modifications made to system authorization file
%UAF-I-NAFNOMODS, no modifications made to network proxy data base
%UAF-I-RDBNOMODS, no modifications made to rights data base
 
Press RETURN to continue  
 
--------------------------------------------------------------
ROOTS - Setting up root level directory trees.
--------------------------------------------------------------
 
The procedure will create the following root level directories:
 
LSL$PUBLIC_ROOT: -> [LSLPUBLIC...]      ! LSL published software (read-only)
LSL$SITE_ROOT: ->   [LSLSITE...]        ! LSL site-specific software 
LSL$USER_ROOT: ->   [LSLUSER...]        ! LSL users home directories
LSL$DATA_ROOT: ->   [LSLDATA...]        ! LSL data directories
LSL$LOCAL_ROOT: ->  [LSLLOCAL...]       ! LSL workspace directories
 
Proceed with this stage [Y] ?  
 
Disk devices available are:

Device                  Device           Error    Volume         Free  Trans Mnt
 Name                   Status           Count     Label        Blocks Count Cnt
DKA300:                 Online               0
DKA100:                 Mounted              0  SYS_DISK       1157787   131   1
DUA2:                   Online               0
 
Firstly select a disk for the LSL standard software files.
This will have the following directories:
LSL$PUBLIC_ROOT: -> [LSLPUBLIC...]      ! LSL published software (read-only)
 
What device for public tree [default is DKA100:] ?  
   "LSL$PUBLIC_ROOT" = "DKA100:[LSLPUBLIC.]" (LNM$SYSTEM_TABLE)
 
Now select a disk for the LSL site-specific files.
This will have the following directories:
LSL$SITE_ROOT: ->   [LSLSITE...]        ! site-specific software 
 
What device for site tree [default is DKA100:] ?  
   "LSL$SITE_ROOT" = "DKA100:[LSLSITE.]" (LNM$SYSTEM_TABLE)
 
Now select a disk for the LSL users home directories.
This will have the following directories:
LSL$USER_ROOT: -> [LSLUSER...]  ! LSL users home directories
 
What device for user tree [default is DKA100:] ?  
   "LSL$USER_ROOT" = "DKA100:[LSLUSER.]" (LNM$SYSTEM_TABLE)
 
Now select a disk for the LSL data directories.
This will have the following directories:
LSL$DATA_ROOT: -> [LSLDATA...]  ! LSL data directories
 
What device for data tree [default is DKA100:] ?  
   "LSL$DATA_ROOT" = "DKA100:[LSLDATA.]" (LNM$SYSTEM_TABLE)
 
Now select a disk for the LSL local workspace directories.
This will have the following directories:
LSL$LOCAL_ROOT: -> [LSLLOCAL...]        ! LSL workspace directories
 
What device for local tree [default is DKA100:] ?  
   "LSL$LOCAL_ROOT" = "DKA100:[LSLLOCAL.]" (LNM$SYSTEM_TABLE)
 
Now creating site-specific definitions file LSDEFNS_ROOTS
 
$! LSDEFNS_ROOTS.COM - define LSL root logical names.
$!
$! This file was generated by LSLINSTALL.COM, but can now be edited
$!
$       DEFINE/SYSTEM/TRANS=(CONCEALED,TERMINAL) LSL$PUBLIC_ROOT -
                DKA100:[LSLPUBLIC.]
$       DEFINE/SYSTEM/TRANS=(CONCEALED,TERMINAL) LSL$SITE_ROOT  -
                DKA100:[LSLSITE.]
$       DEFINE/SYSTEM/TRANS=(CONCEALED,TERMINAL) LSL$DATA_ROOT  -
                DKA100:[LSLDATA.]
$       DEFINE/SYSTEM/TRANS=(CONCEALED,TERMINAL) LSL$USER_ROOT  -
                DKA100:[LSLUSER.]
$       DEFINE/SYSTEM/TRANS=(CONCEALED,TERMINAL) LSL$LOCAL_ROOT -
                DKA100:[LSLLOCAL.]
$!
$       EXIT

Press RETURN to continue  
 
--------------------------------------------------------------
LOAD - Load savesets from distribution medium
--------------------------------------------------------------
 
Proceed with this stage [Y] ?  
 
 
The following magtape devices are available on this CPU ()
 
Device MKA500: is a TK50 drive (Cartridge tape)
 
Where should issue savesets be read from [default is MKA500:] ?  
Tape device MKA500: will now be mounted
Hit RETURN when ready 
%MOUNT-I-WRITELOCK, volume is write locked
%MOUNT-I-MOUNTED, LSLSYS mounted on _MKA500:
 
Laser-Scan strongly recommend that the whole of any installation kit is applied.
Do you want to select only part of this kit [default N] ?  
 
Now select any special options for the loading:
  /VERIFY will carry out an extra BACKUP verification pass for each saveset.
  /LIST will produce a BACKUP listing for each saveset and file loaded.
  /LOG will produce a BACKUP log line for each file loaded.
The defaults are usually adequate for a normal installation.
 
/VERIFY [default N] ?  
/LIST [default N] ?  
/LOG [default N] ?  
 
Starting load now - this may take several minutes.
Load complete
 
Now setting protections on all files on LSL$PUBLIC_ROOT:
 
Press RETURN to continue  
 
--------------------------------------------------------------
DIRECTORIES - Set up standard site_dependent directories
--------------------------------------------------------------
 
Proceed with this stage [Y] ?  y
%CREATE-I-CREATED, LSL$SITE_ROOT:[LSL.COM] created
%CREATE-I-CREATED, LSL$SITE_ROOT:[LSL.EXE] created
%CREATE-I-CREATED, LSL$SITE_ROOT:[LSL.LIB] created
%CREATE-I-CREATED, LSL$SITE_ROOT:[LSL.HELP] created
%CREATE-I-CREATED, LSL$SITE_ROOT:[LSL.LOOKUP] created
%CREATE-I-CREATED, LSL$SITE_ROOT:[LSL.FRT] created
%CREATE-I-CREATED, LSL$SITE_ROOT:[LSL.UIL] created
%CREATE-I-CREATED, LSL$SITE_ROOT:[LSL.UID] created
%CREATE-I-CREATED, LSL$SITE_ROOT:[LSL.CDL] created
%CREATE-I-CREATED, LSL$SITE_ROOT:[LSL.FPP] created
%CREATE-I-CREATED, LSL$SITE_ROOT:[LSL.MGMT] created
%CREATE-I-CREATED, LSL$SITE_ROOT:[LSLSOFT] created
%CREATE-I-CREATED, LSL$SITE_ROOT:[LITES2.CMD] created
%CREATE-I-CREATED, LSL$USER_ROOT:[LSLUSER] created
%CREATE-I-CREATED, LSL$DATA_ROOT:[LSL.IFF] created
%CREATE-I-CREATED, LSL$DATA_ROOT:[LSL.DTI] created
%CREATE-I-CREATED, LSL$LOCAL_ROOT:[LITES2.WORK] created
%CREATE-I-CREATED, LSL$LOCAL_ROOT:[LITES2.JNL] created
%SET-I-MODIFIED, LSL$LOCAL_ROOT:[LITES2.JNL] modified
 
Press RETURN to continue  
 
 
--------------------------------------------------------------
FILES - Copy the startup files to SYS$MANAGER:
--------------------------------------------------------------
 
This will copy the template LS*.com startup files from the newly
loaded public tree, and also any package-specific startup files.
 
Proceed with this stage [Y] ?  
 
Copying the following startup template files to SYS$COMMON:[SYSMGR]:
        LSDEFNS.COM
        LSDEFNS_DEVICES.COM
        LSDEFNS_LOCAL.COM
        LSDEFNS_SEARCHLISTS.COM
        LSDISKS.COM
        LSDISKS_DISMOUNT.COM
        LSDISKS_LOGICALS.COM
        LSDISKS_MOUNT.COM
        LSIMAGES.COM
        LSLOGIN.COM
        LSPORTS.COM
        LSPRINTERS.COM
        LSPROCESSES.COM
        LSQUEUES.COM
        LSSTARTUP.COM
        LSSYSTARTUP.COM
        LSTERMS.COM
 
 
Copying the following package-specific startup files to SYS$COMMON:[SYSMGR]:
No package-specific startup procedures found
 
Press RETURN to continue  
 
Creating the login definitions files for LSLUSER and LSLSOFT
 
Creating login.com for [LSLSOFT]
Creating login.com for [LSLUSER]
 
Press RETURN to continue  

Now you need to specify the Laser-Scan short name for your site, which will be
used for software licensing purposes.

It will usually be an acronym of the name of the organisation, eg LSLCAM. If
you do not know the name that LSL have given your site, either deduce it from
the following list of available licences, or telephone the Customer Services
department at LSL Cambridge.

If you are not able to specify a valid name, then give a value of "UNKNOWN",
and edit the correct value later into the file which will now be created called
SYS$MANAGER:LSDEFNS_SITE.COM. If you do this, then you will not be able to run
full LAMPS software until the correct name and/or licence files are supplied.

Press RETURN to continue  
 
Licences are available for the following customers:
        LSLCAM
 
What is your customer name [default is LSLCAM] ?  
 
Now creating site-specific definitions file LSDEFNS_SITE
 
$! LSDEFNS_SITE.COM - define LSL site-specific logical names.
$!
$! This file was generated by LSLINSTALL.COM, but can now be edited
$!
$! Firstly a customer name, to be used for software licences
$!
$       DEFINE/SYSTEM   LSL$CUSTOMER_NAME               LSLCAM
$!
$       EXIT
 
Press RETURN to continue  
 
--------------------------------------------------------------
SEARCHLISTS - Set up search lists for LSL$EXE etc
--------------------------------------------------------------
 
Proceed with this stage [Y] ?  

LSL$SEARCHLISTS_GENERATE.COM (V2.0) - generate file of searchlist definitions

Creating LSDEFNS_SEARCHLISTS.COM in SYS$COMMON:[SYSMGR]

$! LSDEFNS_SEARCHLISTS.COM - define LSL searchlists.
$!
$! WARNING - This file is automatically generated by a command procedure
$! Do not edit it. Instead go @LSL$COM:LSLSEARCHLISTS_GENERATE.COM.
$!
$!
$! Set up search list for public tree .COM directories
$!
$       Define/System   LSL$COM -
                LSL$SITE_ROOT:[LSL.COM],-
                LSL$COM_PUBLIC
$!
$       Define/System   LSL$COM_PUBLIC  -
                LSL$PUBLIC_ROOT:[$XGIS_BYPS.COM],-
                LSL$PUBLIC_ROOT:[IMP.COM],-
                LSL$PUBLIC_ROOT:[LITES2.COM],-
                LSL$PUBLIC_ROOT:[LSLSYSTEM.COM],-
                LSL$PUBLIC_ROOT:[MAPPING.COM],-
                LSL$PUBLIC_ROOT:[MAPSTATION.COM],-
                LSL$PUBLIC_ROOT:[MATRIX.COM],-
                LSL$PUBLIC_ROOT:[METROPOLIS.COM],-
                LSL$PUBLIC_ROOT:[POSTPROCESS.COM],-
                LSL$PUBLIC_ROOT:[SCANCONVERT.COM],-
                LSL$PUBLIC_ROOT:[VTRAK.COM],-
                LSL$PUBLIC_ROOT:[XGIS.COM]
$!
$! Set up search list for public tree .EXE directories
$!
$       Define/System   LSL$EXE -
                LSL$SITE_ROOT:[LSL.EXE],-
                LSL$EXE_PUBLIC
$!
$       Define/System   LSL$EXE_PUBLIC  -
                LSL$PUBLIC_ROOT:[$XGIS_BYPS.EXE],-
                LSL$PUBLIC_ROOT:[IMP.EXE],-
                LSL$PUBLIC_ROOT:[LITES2.EXE],-
                LSL$PUBLIC_ROOT:[LSLSYSTEM.EXE],-
                LSL$PUBLIC_ROOT:[MAPPING.EXE],-
                LSL$PUBLIC_ROOT:[MATRIX.EXE],-
                LSL$PUBLIC_ROOT:[METROPOLIS.EXE],-
                LSL$PUBLIC_ROOT:[POSTPROCESS.EXE],-
                LSL$PUBLIC_ROOT:[SCANCONVERT.EXE],-
                LSL$PUBLIC_ROOT:[VTRAK.EXE],-
                LSL$PUBLIC_ROOT:[XGIS.EXE]
$!
$! Set up search list for public tree .LIB directories
$!
$       Define/System   LSL$LIBRARY     -
                LSL$SITE_ROOT:[LSL.LIB],-
                LSL$LIBRARY_PUBLIC
$!
$       Define/System   LSL$LIBRARY_PUBLIC      -
                LSL$PUBLIC_ROOT:[LSLSYSTEM.LIB],-
                LSL$PUBLIC_ROOT:[MAPPING.LIB],-
                LSL$PUBLIC_ROOT:[MATRIX.LIB]
$!
$! Set up search list for public tree .HELP directories
$!
$       Define/System   LSL$HELP        -
                LSL$SITE_ROOT:[LSL.HELP],-
                LSL$HELP_PUBLIC
$!
$       Define/System   LSL$HELP_PUBLIC -
                LSL$PUBLIC_ROOT:[IMP.HELP],-
                LSL$PUBLIC_ROOT:[LITES2.HELP],-
                LSL$PUBLIC_ROOT:[LSLSYSTEM.HELP],-
                LSL$PUBLIC_ROOT:[MAPPING.HELP],-
                LSL$PUBLIC_ROOT:[MATRIX.HELP],-
                LSL$PUBLIC_ROOT:[VTRAK.HELP]
$!
$! Set up search list for public tree .LOOKUP directories
$!
$       Define/System   LSL$LOOKUP      -
                LSL$SITE_ROOT:[LSL.LOOKUP],-
                LSL$LOOKUP_PUBLIC
$!
$       Define/System   LSL$LOOKUP_PUBLIC       -
                LSL$PUBLIC_ROOT:[IMP.LOOKUP],-
                LSL$PUBLIC_ROOT:[LSLSYSTEM.LOOKUP],-
                LSL$PUBLIC_ROOT:[MATRIX.LOOKUP]
$!
$! Set up search list for public tree .UIL directories
$!
$       Define/System   LSL$UIL -
                LSL$SITE_ROOT:[LSL.UIL],-
                LSL$UIL_PUBLIC
$!
$       Define/System   LSL$UIL_PUBLIC  -
                LSL$PUBLIC_ROOT:[$XGIS_BYPS.UIL],-
                LSL$PUBLIC_ROOT:[LITES2.UIL],-
                LSL$PUBLIC_ROOT:[METROPOLIS.UIL],-
                LSL$PUBLIC_ROOT:[XGIS.UIL]
$!
$! Set up search list for public tree .UID directories
$!
$       Define/System   LSL$UID -
                LSL$SITE_ROOT:[LSL.UID],-
                LSL$UID_PUBLIC
$!
$       Define/System   LSL$UID_PUBLIC  -
                LSL$PUBLIC_ROOT:[SCANCONVERT.UID],-
                LSL$PUBLIC_ROOT:[VTRAK.UID]
$!
$! Set up search list for public tree .CDL directories
$!
$       Define/System   LSL$CDL -
                LSL$SITE_ROOT:[LSL.CDL],-
                LSL$CDL_PUBLIC
$!
$       Define/System   LSL$CDL_PUBLIC  -
                LSL$PUBLIC_ROOT:[MAPSTATION.CDL],-
                LSL$PUBLIC_ROOT:[SCANCONVERT.CDL],-
                LSL$PUBLIC_ROOT:[VTRAK.CDL]
$!
$! Set up search list for public tree .CMD directories
$!
$       Define/System   LSL$LITES2CMD   -
                LSL$SITE_ROOT:[LITES2.CMD],-
                LSL$LITES2CMD_PUBLIC
$!
$       Define/System   LSL$LITES2CMD_PUBLIC    -
                LSL$PUBLIC_ROOT:[$XGIS_BYPS.CMD],-
                LSL$PUBLIC_ROOT:[METROPOLIS.CMD],-
                LSL$PUBLIC_ROOT:[XGIS.CMD]
$!
$       EXIT
 
Press RETURN to continue  
 
--------------------------------------------------------------
OPTIONS - set up environment for optional software
--------------------------------------------------------------
 
Proceed with this stage [Y] ?  y
 
The procedure will create the following captive usernames:
[100,1]   = [VTRAK]     ! VTRAK captive user
 
Creating user [VTRAK]
 
%UAF-I-COPMSG, user record copied
%UAF-I-RDBADDMSGU, identifier VTRAK value: [000100,000001] added to rights 
 data base
%UAF-I-MDFYMSG, user record(s) updated
%UAF-I-MDFYMSG, user record(s) updated
%UAF-I-MDFYMSG, user record(s) updated
       Owner         Username           UIC       Account  Privs Pri Directory

LSL VTRAK user       VTRAK           [100,1]      LSL      Group   4 LSL$USER_
ROOT:[VTRAK]
%UAF-I-DONEMSG, system authorization file modified
%UAF-I-NAFNOMODS, no modifications made to network proxy data base
%UAF-I-RDBDONEMSG, rights data base modified
 
Press RETURN to continue  

The LAMPS environment contains an optional privileged user called [OPER],
which is supplied with a template captive command procedure for carrying 
out useful VMS operator functions such as disk archiving, queue management,
system shutdown, etc.

This functionality is particularly useful for small LAMPS turnkey systems,
which are not run as general-purpose timesharing systems, and hence do not 
have full-time system management and systems operations personnel.

Larger systems with many layered products installed will usually already 
have operator accounts, and so will not want to include the LSL offering.

Do you want to create a privileged operator [OPER] user [Y] ?  y
 
Creating user [OPER]
 
%UAF-I-COPMSG, user record copied
%UAF-I-RDBADDMSGU, identifier OPER value: [000001,000377] added to rights data 
 base
%UAF-I-MDFYMSG, user record(s) updated
%UAF-I-MDFYMSG, user record(s) updated
%UAF-I-MDFYMSG, user record(s) updated
%UAF-I-MDFYMSG, user record(s) updated
%UAF-I-MDFYMSG, user record(s) updated
%UAF-I-MDFYMSG, user record(s) updated
%UAF-I-MDFYMSG, user record(s) updated
       Owner         Username           UIC       Account  Privs Pri Directory

SYSTEM OPERATOR      OPER              [1,377]    OPERATOR All     4 SYS$SYSDEV
ICE:[OPER]
%UAF-I-DONEMSG, system authorization file modified
%UAF-I-NAFNOMODS, no modifications made to network proxy data base
%UAF-I-RDBDONEMSG, rights data base modified
 
 
Press RETURN to continue  
 
No package-specific installation procedures found
 
Press RETURN to continue  
 
--------------------------------------------------------------
TUNE - Evaluate SYSGEN parameters.
--------------------------------------------------------------
 
Proceed with this stage [Y] ?  
 
Current value of VIRTUALPAGECNT is 24384
   LSL recommend at least 300000
   You should edit MODPARAMS.DAT and insert the line:
   MIN_VIRTUALPAGECNT=300000    ! Increase for LSL LAMPS
 
Current value of WSMAX is 4100
   LSL recommend at least 16384
   You should edit MODPARAMS.DAT and insert the line:
   MIN_WSMAX=16384      ! Increase for LSL LAMPS
 
Press RETURN to continue  

WARNING - Your current SYSGEN parameters are probably low.

You should note the values which were recommended above and which have been
stored for you in the file SYS$SYSTEM:LSLINSTALL_MODPARAMS.DAT. Consider
whether they are indeed suitable for your hardware and software configuration.
When satisfied, edit the values into the MODPARAMS.DAT file in SYS$SYSTEM:,
then run the DEC-supplied AUTOGEN procedure, then reboot the system. 

Look up AUTOGEN in the VMS System Management manuals if you are not familiar
with changing SYSGEN parameters using AUTOGEN and the MODPARAMS.DAT file. 

You should do this as soon as this LSLINSTALL procedure finishes, before
logging off as SYSTEM.

Press RETURN to continue  
 

The LSLINSTALL stage of LSL LAMPS software installation is now complete.

If the TUNE stage above suggested changes to MODPARAMS.DAT, do that now.

LSLINSTALL terminating sucessfully
$
$!
$! Now try it out !!!
$!
$ @LSSTARTUP 
Entering LSSTARTUP.COM - Laser-Scan startup procedure
LSDISKS_LOGICALS.COM - Defining LSL disk logical names
LSDEFNS.COM - Defining LSL logical names
%DCL-I-SUPERSEDE, previous value of LSL$PUBLIC_ROOT has been superseded
%DCL-I-SUPERSEDE, previous value of LSL$SITE_ROOT has been superseded
%DCL-I-SUPERSEDE, previous value of LSL$DATA_ROOT has been superseded
%DCL-I-SUPERSEDE, previous value of LSL$USER_ROOT has been superseded
%DCL-I-SUPERSEDE, previous value of LSL$LOCAL_ROOT has been superseded
%DCL-I-SUPERSEDE, previous value of LSL$COM has been superseded
%DCL-I-SUPERSEDE, previous value of LSL$COM_PUBLIC has been superseded
%DCL-I-SUPERSEDE, previous value of LSL$EXE has been superseded
%DCL-I-SUPERSEDE, previous value of LSL$EXE_PUBLIC has been superseded
%DCL-I-SUPERSEDE, previous value of LSL$LIBRARY has been superseded
%DCL-I-SUPERSEDE, previous value of LSL$LIBRARY_PUBLIC has been superseded
%DCL-I-SUPERSEDE, previous value of LSL$HELP has been superseded
%DCL-I-SUPERSEDE, previous value of LSL$HELP_PUBLIC has been superseded
%DCL-I-SUPERSEDE, previous value of LSL$LOOKUP has been superseded
%DCL-I-SUPERSEDE, previous value of LSL$LOOKUP_PUBLIC has been superseded
%DCL-I-SUPERSEDE, previous value of LSL$UIL has been superseded
%DCL-I-SUPERSEDE, previous value of LSL$UIL_PUBLIC has been superseded
%DCL-I-SUPERSEDE, previous value of LSL$UID has been superseded
%DCL-I-SUPERSEDE, previous value of LSL$UID_PUBLIC has been superseded
%DCL-I-SUPERSEDE, previous value of LSL$CDL has been superseded
%DCL-I-SUPERSEDE, previous value of LSL$CDL_PUBLIC has been superseded
%DCL-I-SUPERSEDE, previous value of LSL$LITES2CMD has been superseded
%DCL-I-SUPERSEDE, previous value of LSL$LITES2CMD_PUBLIC has been superseded
LSTERMS.COM - Setting up serial lines
LSPORTS.COM - Setting up terminal server ports
LSIMAGES.COM - Installing images
LSQUEUES.COM - starting queues
LSPRINTERS.COM - setting up printers
Finished LSSTARTUP.COM
$ 
$!
$! seems OK, would carry on now with editing template files etc.
$!
$ LOGOFF 
  SYSTEM       logged out at 13-JUL-1990 10:32:48.54