To check the values of your system parameters, enter the following command at the DCL prompt to invoke SYSGEN:

$ RUN SYS$SYSTEM:SYSGEN SYSGEN>

At the SYSGEN> prompt, enter the SHOW command to display the value of each system parameter. Make sure that the values displayed equal or exceed the value of each parameter listed in Table 2-6 or Table 2-7. The following command displays the value for the VIRTUALPAGECNT system parameter:

SYSGEN> SHOW VIRTUALPAGECNT Parameter Name Current Default Min. Max. Unit Dynamic -------------- ------- ------- ------ ------ ---- ------- VIRTUALPAGECNT 270144 9216 512 1200000 Pages

This example shows that the current value for VIRTUALPAGECNT is 270144.

After you finish checking the parameters with the SHOW command, enter the EXIT command at the SYSGEN> prompt to return to DCL level.

2.6.2 Calculating the Values for GBLPAGES and GBLSECTIONS

To install and run ACMS, you must set the correct values for the GBLPAGES and GBLSECTIONS system parameters.

The values for GBLPAGES and GBLSECTIONS in Table 2-6 and Table 2-7 (excluding the value of n) indicate the number of unused pages or sections you must have available on your system for the installation to process successfully. To calculate whether your system has a sufficient number of unused global pages and global sections, perform the following steps:

1. Show the current free global pages and global sections using the following DCL commands:

   $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") 3420 $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") 72

2. Determine if the number of unused pages (3420 in the example) is equal to or greater than the number specified in Table 2-6 or Table 2-7. If the number of unused pages is less than the number listed in the table, increase the allocation value for GBLPAGES.
3. Determine if the number of unused global sections (72 in the example) is equal to or greater than the number specified in Table 2-6 or Table 2-7. If the value is less than the number required, increase the allocation value of the GBLSECTIONS parameter.

Section 2.6.3 describes the procedures for increasing these values as well as those of other system parameters. Refer to the OpenVMS documentation on system management and operations for more information.

2.6.3 Changing System Parameter Values with AUTOGEN

Use the AUTOGEN command procedure to change system parameters. To change system parameters with AUTOGEN, you must edit the following file:

SYS$SYSTEM:MODPARAMS.DAT

For example, to change the setting for the GBLPAGES system parameter, add this line to the file:

GBLPAGES = 100000

Now, run the AUTOGEN procedure to recalculate your system parameters. Enter the following command at the DCL prompt:

$ @SYS$UPDATE:AUTOGEN GETDATA REBOOT

AUTOGEN performs an automatic system shutdown and reboots when it has finished. Rebooting your system makes the new parameter values active. For more information about using AUTOGEN, see the instructions on modifying system parameters in the OpenVMS documentation on system management and operations.

2.6.4 Setting the CLISYMTBL Dynamic System Parameter

If the CLISYMTBL system parameter value for your system is less than 500, change the setting by entering the following series of commands:

$ RUN SYS$SYSTEM:SYSGEN SYSGEN> USE ACTIVE SYSGEN> SET CLISYMTBL 500 SYSGEN> WRITE ACTIVE SYSGEN> EXIT

CLISYMTBL is a dynamic parameter, which means that you do not have to reboot the system to make the change take effect. The new value for CLISYMTBL becomes effective when you enter the SYSGEN command WRITE ACTIVE.

If you do nothing further, the new value for CLISYMTBL remains in effect until the next time you reboot the system, at which time the old value for CLISYMTBL is restored.

If you want to make the new CLISYMTBL value permanent, enter the following SYSGEN command:

SYSGEN> WRITE CURRENT

The WRITE CURRENT command writes the new value for CLISYMTBL into the SYSGEN database on disk, so that it is available when the system is rebooted.

To exit from SYSGEN, enter the following command:

SYSGEN> EXIT

The account you use to install ACMS must have sufficient quotas to enable you to perform the installation. Table 2-8 summarizes the process quotas required to perform the installation.

Table 2-8 Process Account Quotas

Account Quota	Required Value
ASTLM	24
BIOLM	18
BYTLM	32,768
DIOLM	18
ENQLM	2,000
FILLM	200
PRCLM	10
PGFLQUO	12,800

User account quotas are stored in the file SYSUAF.DAT. Use the OpenVMS Authorize Utility (AUTHORIZE) to verify and change user account quotas. First set your directory to SYS$SYSTEM and then run AUTHORIZE:

$ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF>

At the AUTHORIZE prompt (UAF>), enter the SHOW command with an account name to check a particular account. For example:

UAF> SHOW SYSTEM

To change a quota, enter the MODIFY command at the UAF> prompt. MODIFY has the following format:

MODIFY account-name/quota-name=nnnn

The following example changes the FILLM quota for the SYSTEM account and then exits from the Authorize Utility:

UAF> MODIFY SYSTEM/FILLM=200 UAF> EXIT

After you exit from the utility, the OpenVMS system displays messages indicating whether or not changes were made. Once the changes have been made, you must log out and log in again for the new quotas to take effect.

For more information on modifying account quotas, see the description of the Authorize Utility in the OpenVMS documentation on system management and operations.

2.8 Time Required for Installation

Table 2-9 lists the approximate time required for installing each ACMS kit.

Table 2-9 Timetable for Installing ACMS

Kit	Installation Time1	IVP Time
Development	7 minutes	2 minutes
Run-time	4 minutes	2 minutes
Remote-access	2 minutes	1 minute

The ACMS installation checks for the presence of the OpenVMS user account ACMS$IVP. If this account does not exist, you are asked for information needed to create it. The ACMS$IVP account is used to run the ACMS Installation Verification Procedure.

Among the information requested for this account is a unique user identification code (UIC) in the form [ggggg,nnnnnn], where ggggg is an octal user group number in the range 1--37776, and nnnnnn is an octal user number in the range 1--177776. Additionally, the group number cannot be a system group number.

Enter the following commands to list the UICs currently in use on your system:

$ MCR AUTHORIZE UAF> LIST * /BRIEF

The result of these commands is that all UICs in use on your system are listed in the file SYSUAF.LIS, in your default directory. You can then examine this listing to determine a unique UIC for the ACMS$IVP account.

On your system, a certain range of group numbers has been reserved for system users. To determine this range, execute the following commands:

$ MAXSYS = F$GETSYI("MAXSYSGROUP") $ SHOW SYMBOL MAXSYS

The value you supply for the octal group number in the ACMS$IVP UIC must be greater than the octal value of the symbol MAXSYS. The following example shows that the maximum system group number is octal 10; therefore, you must specify a group number for the ACMS$IVP UIC that is in the range 11--37776:

$ MAXSYS = F$GETSYI("MAXSYSGROUP") $ SHOW SYMBOL MAXSYS MAXSYS = 8 Hex = 00000008 Octal = 00000000010

This chapter describes how to install the ACMS software. Section 3.2 contains a step-by-step description of the installation procedure.

3.1 Installation Log

A log of your installation is kept in the following file:

SYS$COMMON:[SYSUPD]ACMS043_INSTALLATION.LOG

In particular, if the ACMS installation fails because prerequisites were not met, this log contains a list of those prerequisites. You can use it as a check list of items to address before you reinstall ACMS.

In addition, after the installation is completed, a list of the files created by the installation is stored in the following file:

SYS$COMMON:[SYSEXE]ACMS043_FILES.DAT

3.2 Installation Procedure

ACMS provides online release notes. The prompt to display or print the release notes before the installation appears in the installation procedure, if you invoke VMSINSTAL with the OPTIONS N parameter. For information on accessing the release notes after the installation, refer to Section 3.4.

The ACMS installation process is divided into five phases:

• The first phase consists of invoking VMSINSTAL and supplying information such as which kit to install, where the kit resides, and other installation options. Section 3.2.1 explains the first phase.
• The second phase consists of a series of questions, checks, and informational messages related to ACMS. This phase ensures that the installation environment is sufficient to support the actual installation work that occurs in the third phase. The second phase ends when you are shown a summary of what happens in the third phase and are asked whether you want to continue. Chapter 2 has information to help you answer the questions asked in the second phase; if you have not read Chapter 2 in preparation for this installation, do so now. Section 3.2.2 takes you step by step through the second phase of the installation.
• The third phase is the actual installation work. This usually includes restoring kit savesets, providing files to system directories, creating the ACMS$IVP user account, updating the LSE and Oracle Trace environments, updating DCL tables and help libraries, and other steps as enumerated at the end of the second phase. No user interaction is required during this phase. Section 3.2.3 explains the messages that you might see during this phase.
• The fourth phase is the ACMS postinstallation procedure. This procedure, which executes automatically after the ACMS software is installed, performs the minimum system management operations that are necessary to allow ACMS to be used on the system. Section 3.2.4 guides you through the postinstallation phase.
• The fifth phase is the ACMS Installation Verification Procedure (IVP). This procedure performs a series of exercises to ensure that ACMS is properly installed and usable on your system. Section 3.2.5 discusses the execution of the IVP.

To abort the installation procedure at any time, press [Ctrl/Y]. When you press [Ctrl/Y], the installation procedure deletes all files it has created up to that point and exits. You can then start the installation again.

3.2.1 Invoking VMSINSTAL (First Phase)

To start the installation, log in to the SYSTEM account, and set default to the SYS$UPDATE directory:

Username: SYSTEM Password: $ SET DEFAULT SYS$UPDATE

Next, invoke VMSINSTAL. Use the following syntax to invoke VMSINSTAL:

@VMSINSTAL product-name device-name [OPTIONS option-1[,...]]

product-name

The installation name for the component. Enter one of the following:

• ACMSDEVA_043 --- if you are installing the Alpha development kit.
• ACMSRTOA_043 --- if you are installing the Alpha run-time kit.
• ACMSREMA_043 --- if you are installing the Alpha remote-access kit.
• ACMSDEVV_043 --- if you are installing the VAX development kit.
• ACMSRTOV_043 --- if you are installing the VAX run-time kit.
• ACMSREMV_043 --- if you are installing the VAX remote-access kit.

device-name

The name of the device on which you plan to mount the media. For example, MTA0: is the device name for a tape drive.

OPTIONS

An optional parameter indicating that one or more VMSINSTAL options are being supplied. This parameter is followed by a space, and then the requested options. If multiple options are requested, separate them with commas (,); do not include spaces in the options list.

The following are VMSINSTAL options that you can use for the ACMS installation:

• N---The release notes option causes VMSINSTAL to prompt you to display or print the ACMS release notes during the installation. (Release notes are always copied to SYS$HELP during an installation, whether or not this option is specified.)
• AWD---The alternate working device option allows you specify an alternate disk device on which to create the temporary working directory used by VMSINSTAL during a product installation. This option allows you to perform an installation with fewer free blocks on the system disk than are otherwise required.
  Specify the AWD option using the following format:

  AWD=device

  Note Use the AWD option only if you have previously installed ACMS and you do not have sufficient space on your system disk to perform a normal installation. If you have not previously installed ACMS, you must have the disk space listed in Table 2-2 or Table 2-3 available to accommodate the ACMS software.

  
  See Section 2.4.2 for more information on using the AWD option.

VMSINSTAL has several other options; for information, see the OpenVMS documentation on software installation.

On Alpha, the following command invokes VMSINSTAL and installs ACMS from the MTA0: tape drive. This example uses the N option for printing or displaying release notes, and the AWD option to use disk DISK1 as an alternate working device:

$ @SYS$UPDATE:VMSINSTAL ACMSDEVA_043 MTA0: OPTIONS N,AWD=DISK1 OpenVMS AXP Software Product Installation Procedure V6.2 It is 7-OCT-1999 at 11:00. Enter a question mark (?) at any time for help.

If you do not supply either the product name or the device name, VMSINSTAL prompts you for this information later on in the installation procedure.

1. System backup VMSINSTAL asks the following question to ensure that your system disk is properly backed up:

   * Are you satisfied with the backup of your system disk [YES]?

   
   Always back up your system disk before performing an installation. If you are satisfied with the backup of your system disk, press [Return]. Otherwise, answer NO to stop the installation. After you back up your system disk, you can restart the installation.

2. Mounting the media VMSINSTAL instructs you to mount the ACMS Version 4.3 distribution media on the device you specified when you invoked VMSINSTAL. When you have mounted the media, answer YES to the question, "Are you ready?":

   Please mount the first volume of the set on MTA0:. * Are you ready? Y

   
   If you entered the wrong device name when you invoked VMSINSTAL and need to restart the installation, answer NO in response to the question. To abort the installation for any other reason, press [Ctrl/Y].
   VMSINSTAL then reads the media and begins the installation of ACMS. A message similar to the following appears:

   %MOUNT-I-MOUNTED, ACMSDEVA_043 MOUNTED ON _$200$MTA0: The following products will be processed: ACMSDEVA_ V4.3 Beginning installation of ACMSDEVA_ V4.3 at 11:01 %VMSINSTAL-I-RESTORE, Restoring product saveset A...

3. Release notes If you specified OPTIONS N when you invoked VMSINSTAL, you are now given several options for reviewing the release notes.

   Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]:

   
   If you select option 1, VMSINSTAL displays the release notes immediately. You can terminate the display at any time by pressing [Ctrl/C]. Because the release notes are lengthy, it is recommended that you choose option 2 to print the release notes rather than reviewing them on line.
   If you select option 2, VMSINSTAL prompts you for the name of the print queue that you want to use:

   * Queue name [SYS$PRINT]:

   
   You can enter a queue name or just press [Return] to send the file to the default output print queue SYS$PRINT.
   If you select option 3, VMSINSTAL displays the release notes immediately and then prompts you for a queue name for the printed version.
   If you select option 4, VMSINSTAL does not display or print the release notes. Use the DCL command TYPE or PRINT to view the release notes in the following file:

   SYS$HELP:ACMS043.RELEASE_NOTES

   
   The release notes are copied to the SYS$HELP directory under all circumstances, regardless of your choice from the menu.

   Note The release notes for each version of ACMS are uniquely named so that release notes from multiple versions can be maintained. To facilitate comparison of various versions of ACMS, Compaq recommends not deleting release notes for previous versions of ACMS.

4. Continuing the installation The installation procedure now asks if you want to continue the installation. To continue, answer YES. Otherwise, press [Return] to stop the installation:

   * Do you want to continue the installation [N]?: Y %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.

   
   After you read the release notes, you can restart the installation without being questioned about the release notes by removing OPTIONS N from the VMSINSTAL command. For example:

   $ @SYS$UPDATE:VMSINSTAL ACMSDEVA_043 MTA0: