VMS Software / Documentation / VSI Console Management for OpenVMS Installation Guide

VSI Console Management for OpenVMS Installation Guide

Software Version:
V3.1

Preface

1. About VSI

VMS Software, Inc. (VSI) is an independent software company licensed by Hewlett Packard Enterprise to develop and support the OpenVMS operating system.

2. Intended Audience

This guide is for system managers who are installing VSI Console Management for OpenVMS and for system administrators who are looking for an overview of these products. It contains information about the installation and use of the product. This document should be read in its entirety before beginning the installation. It is intended to be used in conjunction with the Readme and the Release Notes files.

3. Document Structure

This manual is organized as follows:

4. VSI Encourages Your Comments

You may send comments or suggestions regarding this manual or any VSI document by sending electronic mail to the following Internet address: . Users who have VSI OpenVMS support contracts through VSI can contact for help with this product.

5. OpenVMS Documentation

The full VSI OpenVMS documentation set can be found on the VMS Software Documentation webpage at https://docs.vmssoftware.com.

6. VSI Encourages Your Comments

You may send comments or suggestions regarding this manual or any VSI document by sending electronic mail to the following Internet address: . Users who have VSI OpenVMS support contracts through VSI can contact for help with this product.

Chapter 1. Introduction

VSI Console Management for OpenVMS lets you monitor and manage console activity of multiple systems, network devices, and storage controllers without having to be present at those consoles. You can manage or monitor activity locally or remotely and perform management tasks with single or multiple points of control. Management can be from either a workstation, or a character cell terminal.

Use the Console Manager to monitor and manage any device that sends and receives data via an RS232 link in ASCII format, has an EIA console port, and supports flow control (XON/XOFF) and I/O buffering. Devices that have a network console port accessible via TELNET or SSH protocols can also be monitored and managed. This device can be running any operating system.

This section contains the following topics:

1.2. Installation Kit

The installation package is available for download from the VSI Service Portal located at https://sp.vmssoftware.com. The package consists of a zip file that contains the installation kit that is installed using the VMSINSTAL utility. You must have OpenVMS UNZIP available on your system in order to extract the installation kit from the zip file.

Chapter 2. Install the Console Manager

This chapter describes how to install Console Manager on x86-64 system running the OpenVMS operating system.

Keep this guide with your distribution kit. You will need it to install maintenance updates or to reinstall Console Manager for any other reason.

This section contains the following topics:

2.1. Prepare for the Installation

This section discusses the preparations and requirements necessary for installing Console Manager.

2.1.1. Hardware and Software Requirements

Before installing the product, make sure your OpenVMS server meets the following minimum requirements:

  • VSI OpenVMS x86-64 V9.2-2

  • VSI TCP/IP Services for OpenVMS x86-64 Version V6.0

  • VSI DECWindows Motif for x86-64 V1.8

  • A minimum of 100,000 blocks of free disk space

2.1.2. Installation Procedure Requirements

This section describes the requirements for installing the application (privileges, system parameters, and disk space).

Standard procedures for checking and setting various parameters are described in Standard System Maintenance Procedures later in this chapter.

2.1.2.1. Privileges

A successful installation requires you to be logged in to the SYSTEM account for permission to access the Console Manager configuration database.

2.1.2.2. Disk Space

Console Manager requires approximately 1000 blocks of disk space on the system disk, and 100,000 blocks of disk space in your target installation area.

In addition, the installation procedure requires 75,000 blocks of free disk space to decompress the installation package. Console Manager can be installed either on a system disk (SYS$SYSDEVICE) or any other disk accessible via a physical path. VSI does not recommend installing Console Manager on a disk that is MSCP served by another OpenVMS system.

If you want to install the background bitmaps, you must have an additional 45,000 blocks of disk space in your target installation area.

Disk space refers to the space required for the product base files and does not take into account the requirements for log and archive data collected by Console Manager.

To check for available disk space on your system disk, enter the command: 

$ SHOW DEVICE SYS$SYSDEVICE

2.1.2.3. System Disk Backup

At the beginning of the installation, the installation process asks if you have backed up your system disk. VSI recommends that you back up the system disk before installing any software. Use the backup procedures that are established at your site.

2.2. Read the Release Notes

Included with the Console Manager software are the Readme and Release Notes. VSI recommends that you read the Readme and the Release Notes before you install the software.

If you encounter any errors or failures during installation, see the section Recover from Errors.

2.3. Prior Versions of VSI Console Management for OpenVMS

Before installing components of VSI Console Management for OpenVMS, you should stop any prior version running on your system. After starting the installation, if there are active processes, the installation procedure displays them and asks if you would like to continue. Answering YES lets you continue the installation procedure, while NO stops the installation.

2.4. Upgrade and Migration Considerations

2.4.1. Upgrade Considerations

In order to upgrade from an older version, Console Manager must have been started since the last system boot, or the Console Manager logical names must be defined. To define the logical names, run the command 

$ @sys$startup:console$manager$startup.com logicals

If the Console Manager logical names are not defined, the installation will exit.

When upgrading from previous versions of Console Manager, the installation procedure, in order to provide IPv6 support, shuts down VSI NSM Integration and CAM. It uninstalls the previous version of CAM, if detected.

2.4.2. Migration Considerations

You can migrate an existing Console Manager configuration from an existing VAX, Alpha, or Itanium system. You will use the Export/Import function of the Console Manager configuration editor to migrate the basic configuration, but you should be aware of the following:

  • Custom action routines written in a high-level language. Make sure that there is a compiler available for that language on OpenVMS x86-64.

  • Logical names and DCL symbols that need to be defined on the new system.

  • If you have created SYS$MANAGER:CONSOLE$PRIVATE_SETUP.COM, be sure to examine it and make any modifications necessary for it to work correctly in your migrated environment.

  • Physical device names hard-coded into DCL procedures and DCL-based action routines as those device names may not exist on the x86-64 system.

  • If you utilize any of the Console Manager DECWindows-based graphical user interfaces or action routines, you will need an Xwindows compatible display station in your migrated environment.

  • Third-party software that may not be available on OpenVMS x86-64.

2.5. How You Install Console Manager

The installation consists of a number of steps designed to check your system, install Console Manager, and then initialize Console Manager. You must complete the following tasks in the following order:

  1. Decompress the zip file

  2. Run the installation procedure

  3. Check your system backup

  4. Check for a Product Authorization Key

  5. Start Console Manager after the installation

  6. Run the Installation Verification Procedure

  7. Purge previous version files

  8. Specify Users Privileges

  9. Install Background Bitmap Files (optional)

  10. Select if the IVP runs Graphical Tests

  11. Select a Product Directory Location

For a sample installation, see the Sample Installation Log.

  1. Extract the installation kit from the installation package zip file. You must have OpenVMS UNZIP present on the system and you must have the UNZIP foreign command defined:

    $ unzip x86vms-consolemgr-v0301

    Make note of the directory path where the installation kit was extracted to; you will need it for the next step.

  2. Using the SYSTEM account, run the installation procedure on the OpenVMS system by typing the following command: 

    $ @sys$update:vmsinstal VCM031 <directory-path-for-the-installation-kit>

  3. You should always back up your system disk before installing any new software. If you need to restore your former system settings, you want the most current information saved. To ensure you have a good backup, the installation asks if you are satisfied with your backup. Select one of the following responses:

    YES

    If you are satisfied with the backup of your system disk, press Return to accept the default YES.

    NO

    Type NO and press Return to stop the installation. Back up your system disk, and then restart the installation.

  4. The installation procedure prompts for the presence of a valid Product Authorization Key (PAK). Select one of the following responses:

    YES

    The installation verifies if a PAK has been registered and loaded. If a PAK is found the installation will continue. If a PAK is not found the installation will continue, however, the Installation Verification Procedure will not be run.

    NO

    The installation continues; however, the Installation Verification procedure will not be run.

  5. During the installation process you can choose to start or not start Console Manager after the installation completes.

    Note

    If you choose not to start the application after installing it, but you run the Installation Verification Procedure (IVP), the IVP starts Console Manager before it can run.

    If this is the first time you are installing the application on your system, you are asked if you want the software to start right after the installation. Select one of the following responses:

    YES

    The application is started after the installation.

    NO

    The application is not started after the installation.

  6. After the installation, and if a valid PAK has been registered and loaded, the Installation Verification Procedure (IVP) checks to ensure that the installation was successful. It starts the application and performs function tests. VSI recommends that you run the IVP, so the installation gives you the opportunity by asking if you want to run it after completing the installation. Select one of the following responses:

    YES

    The IVP runs after the installation completes.

    NO

    The IVP does not run after the installation completes.

    Note

    If you choose not to run the IVP during the installation, you can run it at any time after the installation completes by entering the following command: 

    $ @SYS$TEST:CONSOLE$MANAGER$IVP.COM

  7. You can purge files from previous versions of the product that are superseded by this installation. VSI recommends that you purge your old files; however, if you need to keep files from a previous version you can choose to not purge your files. The installation asks if you want to purge files replaced by this installation. Select one of the following responses:

    YES

    The files related to earlier versions of the product are purged after the installation completes.

    NO

    The files related to earlier versions of the product are left on the system after the installation completes.

  8. To edit the Console Manager database from an account other than SYSTEM, there must be an entry in the database for the user who needs to perform the edit. The installation prompts you to enter the usernames for users who are granted full Console Manager privileges: 

    * Username of user to add (<RETURN> to end):

  9. You can choose to install background bitmaps. However, the installation requires an additional 45,000 blocks of disk space to provide these background bitmap files. The installation displays the following prompt: 

    * Do you wish to install the background bitmap files [NO]?

  10. If you chose to run the IVP, the installation asks if you want to run graphical tests. The graphical tests display the configuration editor followed by the C3 interface on a workstation of your choice. The installation displays the following prompt: 

    * Do you wish to execute the graphical tests [NO]?

  11. Console Manager files go into the [CONSOLE] directory. The installation procedure asks you for the device where the product directory should be located. The default answer is SYS$SYSDEVICE; however, if you are installing Console Manager in an OpenVMS cluster, you should specify a disk that is shared among all nodes in the cluster. This way, all nodes in the OpenVMS cluster have access to the [CONSOLE] product directory. 

    * Enter the full pathname for Console Manager [SYS$SYSDEVICE:[CONSOLE]]: 
Selected pathname: [SYS$SYSDEVICE:[CONSOLE]] 
Is that correct [Y]?

2.6. Post-Installation Considerations

During the post installation, you will see different messages if you install Console Manager over a previous installation. If this is a new installation, you will see the following: 

%VCM031_I-POST, Starting Console Manager post installation tasks 
No previous Database file exists on the system. Please ignore 
any "Cannot open input file: CONSOLE$DATA:CONSOLE_CFG.DAT" 
messages, this is normal. 
%VCM031_I-CREATENEWDB, Creating system default 
database file…

If you install Console Manager over a previous installation, these messages appear: 

The database format may be changed. The existing database file will be 
purged to one version, the remaining database file will be exported as 
CONSOLE$TEMPLATES:CONSOLE$PRE_V31UPGRADE.PORT, then renamed as 
CONSOLE$DATA:CONSOLE_CFG.PRE_V31UPGRADE. The export file will be 
re-imported to create a new database with the required format. 
Finally, an import of the default CM database entries will be made. 
%VCM031_I-PURGEDB, Purging database... 
%VCM031_I-EXPORTDB, Exporting database... 
%VCM031_I-RENAMEDB, Renaming database to CONSOLE$DATA:CONSOLE 
CFG.PRE_V31UPGRADE...

2.7. Complete the Console Manager Installation

Some post-installation requirements are necessary to enable your system to run the Console Manager software.

The following are items to consider after Console Manager is installed:

  • Close the Installation DECterm

  • Make the Site-Specific Customizations

  • Post-Installation Tasks

  • OpenVMS Cluster Considerations

  • Configure the Automatic Startup Procedure

  • Run the IVP

2.7.1. Close the Installation DECterm

You must close the installation DECterm window after you complete the installation. If this DECterm is not closed, it may lock out other DECterm windows.

2.7.2. Make the Site-Specific Customizations

Console Manager provides a private template file that you can modify to:

  • Change the device/directory where console data is logged.

  • Change the device/directory where console data is archived.

  • Change the default login commands for logging in to serviced systems from the C3 interface.

To modify the template file, copy the file SYS$STARTUP:CONSOLE$PRIVATE_SETUP.TEMPLATE to SYS$STARTUP:CONSOLE$PRIVATE_SETUP.COM and edit the .COM file to reflect your site requirements.

Note

VSI recommends that you put your log and archive directories on separate disks.

2.7.3. Post-Installation Tasks

After completing the Console Manager installation, you might need to perform the following post-installation tasks:

  • Ensure that accounts running the C3 interface have the following quotas: 

    BYTLM=100000+
PGFLQUOTA=40000+
PRCLM=30+
  • Adjust your Console Manager host for running Console Manager. Console Manager requires 300 free global sections and 12,000 free global pages. To set these parameters, add the following lines to SYS$SYSTEM:MODPARAMS.DAT
    ADD_GBLSECTIONS=300 
ADD_GBLPAGES=12000

  • Increase the size of the alternate type-ahead buffer and the XOFF threshold for the alternate type-ahead buffer to accommodate high-data rates from the consoles managed by Console Manager when LAT and Direct connections are used. To set these parameters, add the following lines to SYS$SYSTEM:MODPARAMS.DAT: 

    TTY_ALTPAHD=2000 
TTY_ALTALARM=640

    Note

    You can increase the above two parameters; however, you must maintain the 3 to 1 ratio between them.

  • After you add the lines above to SYS$SYSTEM:MODPARAMS.DAT, execute the AUTOGEN procedure and reboot the system so that they take effect. To do this, type the following command: 

    @SYS$UPDATE:AUTOGEN GETDATA REBOOT.

2.7.4. OpenVMS Cluster Considerations

If you want to run the application on more than one member of a cluster simultaneously, you must copy the file SYS$STARTUP:CONSOLE$PRIVATE_SETUP.TEMPLATE to the specific startup directory, and change the name of the file to CONSOLE$PRIVATE_SETUP.COM. For example: 

$ COPY SYS$STARTUP:CONSOLE$PRIVATE_SETUP.TEMPLATE 
SYS$SPECIFIC:[SYS$STARTUP]CONSOLE$PRIVATE_SETUP.COM

After you copy the file, then for each machine running the application in the cluster, edit the file so that the logical names defined point to your required data and temp directories.

Important

You must make sure that the CONSOLE$DATA and CONSOLE$TMP logical names point to different locations on each machine running Console Manager in the cluster.

If you intend to run the application on more than one node in an OpenVMS cluster, then only one cluster-wide instance of the configuration editor can modify the configuration database. This is the case even if two different instances of the database are being edited. The first privileged user to run the configuration editor in the cluster will be the one who can modify the configuration database.

Note

When running in a cluster and cluster quorum is lost, access to the consoles of the managed systems is lost until quorum is regained.

2.7.5. Configure the Automatic Startup Procedure

Console Manager software contains a startup procedure that defines pointers to example directories. The startup procedure is named CONSOLE$MANAGER$STARTUP.COM and is placed in the SYS$STARTUP directory. Edit the SYSTARTUP_VMS.COM file to run SYS$STARTUP:CONSOLE$MANAGER$STARTUP.COM to define Console Manager logical names.

For more revisions that you might want to make to your startup file, see the VSI Console Management for OpenVMS Administration guide.

If you are using the VSI Common Services Integration software as well, add the following item to your system startup file: 

@SYS$STARTUP:CAPOLY$STARTUP

CAPOLY$STARTUP checks for the presence of each component, and, if installed, will start it.

2.7.6. Run the IVP

The IVP verifies that the component was installed correctly. If you did not choose to auto-run the IVP during the installation procedure, you can manually run it with the following command: 

$ @SYS$TEST:CONSOLE$MANAGER$IVP

The IVP verifies your installation as follows: 

Starting IVP for Console Management 
 =========================================== 
 Checking Files... 
 Startup Files... 
 Binary files...
 Action Routines... 
 Default database Creation... 
 Required UID Files...
 Console Management IVP completed.
 
 Graphical Interface Tests 
------------------------------

To perform these tests you need to be on a workstation 
platform or to have set your display environment correctly. 
The main window of the database editor should appear on your workstation. 
Perform the following:

1. Pull down the "File" menu and select "Verify". 
A message should appear in Status: Database Verification Successful 
2. Pull down the "File" menu and select "Quit" 
The main window of the C3 graphical user interface should appear 
3. Pull down the "File" menu and select "Exit". 

VSI Console Management 
C3 Version –V3.1-yymm 
IVP Completed.

You can run the IVP at any time if you want to verify that the Console Manager software is properly installed.

2.8. Disk Space Required After Installation

To run Console Manager, a minimum of 90,000 blocks of free disk space is required. Disk space refers to space required for the product base files and does not take into account the requirements for log and archive data collected by Console Manager.

2.9. Recover from Errors

This section provides information to help you deal with failures or errors that might occur during installation or use of the application.

2.9.1. Failures During Product Installation

If the installation procedure detects any problems during the installation, it notifies you and asks if you want to continue the installation. In some instances, you can enter YES to continue. To stop the installation process and correct the situation, enter NO or press Return. Then correct the problem and restart the installation.

If errors occur during the installation itself or when the Installation Verification Procedure (IVP) is running, the installation procedure displays failure messages. If the installation fails, you see the following message: 

%VMSINSTAL-E-INSFAIL, The installation of CONSOLE-UNI-0000-yymmdd-V3.1 has failed.

If the IVP fails, you see these messages: 

The VCM031 Installation Verification Procedure failed. 
%VMSINSTAL-E-IVPFAIL, The IVP for VCM031 has failed.

Errors can occur during the installation if any of the following conditions exist:

  • The operating system version is incorrect.

  • A prerequisite software version is incorrect.

  • System parameter values for successful installation are insufficient.

  • The OpenVMS help library is currently in use.

For descriptions of the error messages generated by these conditions, see HP's OpenVMS documentation on system messages, recovery procedures, and OpenVMS software installation. If you are notified that any of these conditions exist, you should take the appropriate action as described in the message.

For information on installation requirements, see the section Prepare for the Installation.

2.10. Uninstall Console Manager

Uninstallation scripts enable you to remove the application from your system. The following script uninstalls VSI Console Management for OpenVMS:

Main De-Installing Script: CONSOLE$MANAGER$DEINSTALL.COM

2.11. Reinstall Console Manager

To reinstall Console Manager, follow the steps described in Installing Console Manager, earlier in this chapter. When you reinstall the product, the installation procedure does not overwrite the existing configuration database.

Note

For more information on creating a new template database, see the VSI Console Management for OpenVMS Administration Guide.

After reinstalling the application, execute the following commands: 

@sys$startup:console$manager$shutdown 
@sys$startup:console$manager$startup

2.12. Sample Installation Log

 $ @SYS$UPDATE:VMSINSTAL VCM031 SYS$MANAGER:
    OpenVMS  Software Product Installation Procedure V9.2-2

It is 11-JUN-2024 at 13:37.
Enter a question mark (?) at any time for help.
* Are you satisfied with the backup of your system disk [YES]? 
The following products will be processed:
  VCM V3.1
    Beginning installation of VCM V3.1 at 13:37

    **********************************************************************
%VMSINSTAL-I-VALSIGN, Performing product kit validation of signed kits ...
Success
%VMSINSTAL-I-VALPASSED, validation of SYS$SYSROOT:[SYSMGR]VCM031.A_VNC succeeded
Success
%VMSINSTAL-I-VALPASSED, validation of SYS$SYSROOT:[SYSMGR]VCM031.B_VNC succeeded
Success
%VMSINSTAL-I-VALPASSED, validation of SYS$SYSROOT:[SYSMGR]VCM031.C_VNC succeeded
Success
%VMSINSTAL-I-VALPASSED, validation of SYS$SYSROOT:[SYSMGR]VCM031.G_VNC succeeded
Success
%VMSINSTAL-I-VALPASSED, validation of SYS$SYSROOT:[SYSMGR]VCM031.Y_VNC succeeded
%VMSINSTAL-I-RESTORE, Restoring product save set A ...
%VMSINSTAL-I-RESTORE, Restoring product save set Y ...

  Copyright (c) 2024 VSI. All rights reserved.

        Product:      VMS-CONSOLEMGR
        Producer:     VSI
        Version:      
        Release Date: 

* Does this product have an authorization key registered and loaded? YES
* Do you want to run the IVP after the installation (Product Startup Required)  [YES]? 
  The product will be started and the IVP will run automatically at the end of this install.[0m
 
* Do you want to purge files replaced by this installation [YES]? 

   This product needs a TCP/IP network stack installed and
   started on this node.  You can use VSI TCP/IP Services
   for OpenVMS x86_64.

   The TCP/IP stack TCP/IP Services is up and running...

%VCM-I-CHECKFORDB, Checking for existing database file...

  In order to edit the Console Management database from an account other than
  "SYSTEM" there must be an entry in the database for the user wishing to
  perform the edit.

  Please enter the usernames for those users who will be granted full
  Console Management privileges, terminate your input with a <RETURN>

* Username of user to add (<RETURN> to end): JSMITH
* Username of user to add (<RETURN> to end): 
* Do you wish to install the background bitmap files [NO]? YES

  It is possible to execute a graphical portion of the IVP, this will
  display the configuration editor, followed by the C3 on a workstation
  of your choice.

  NOTE: When the IVP displays the graphical components of
        Console Management on your screen, in order for the IVP and
        this installation to complete, you should exit from the
        components which appear using the "Exit" option on the
        "File" menu for each interface.

* Do you wish to execute the graphical tests [NO]? 
* Enter the full pathname for Console Manager [SYS$SYSDEVICE:[CONSOLE]]: 
   Selected pathname: [1mSYS$SYSDEVICE:[CONSOLE][0m

* Is that correct [Y]? 

%VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[CONSOLE].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[CONSOLE.DATA].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[CONSOLE.EXAMPLES].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[CONSOLE.TEMPLATES].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[CONSOLE.LOG].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[CONSOLE.TEMP].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[CONSOLE.IMAGES].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[CONSOLE.ARCHIVE].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[CONSOLE.ACTIONS].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[CONSOLE.ACTIONS.USER].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[CONSOLE.ACTIONS.SYSTEM].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[CONSOLE.ICONS].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[CONSOLE.ICONS.SYSTEM].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[CONSOLE.ICONS.USER].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[CONSOLE.APP-DEFAULTS].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[CONSOLE.CREDENTIALS].

   All questions regarding this installation have been asked.[0m
   The installation will run for approximately 2 to 5 minutes

   Providing files...
%VMSINSTAL-I-RESTORE, Restoring product save set B ...
%VCM-I-DEVICEICONS, Providing device icons...
%VCM-I-GROUPICONS, Providing group icons...
%VMSINSTAL-I-RESTORE, Restoring product save set C ...
%VCM-I-BACKGROUNDBITMAPS, Providing background bitmaps...
%VMSINSTAL-I-RESTORE, Restoring product save set G ...
%VCM-I-UPDATEDCL, Updating DCL tables...
%VCM-I-UPDATEHELP, Updating System Help library...

   Providing Startup, Shutdown, Installation Verification
   and Deinstallation procedures ...

%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...
%VCM-I-POST, Starting Console Management post installation tasks

  No previous Database file exists on the system. Please ignore
  any "Cannot open input file: CONSOLE$DATA:CONSOLE_CFG.DAT"
  messages, this is normal.

%VCM-I-CREATENEWDB, Creating system default database file...
%VCM-I-ADDINGUSERS, Adding users to database file...

 Starting Console Management Version
 ====================================

 Defining Console Management logical names...
 De-installing Console Management images...
 Installing Console Management images...
 Starting Console Management processes...
 Clearing out Temporary Directory 
 Starting Console Manager Processes. 
 Console Management startup complete
  Copyright 2024 VMS Software, Inc.

  Starting IVP for Console Management
  ==========================================

  Checking files
      Startup files...
      Binary files...
      Action routines...
      Default database creation...
      Required UID files...
* Do you wish to run the graphical tests ? [N]: 
  Console Management IVP completed.
    Installation of VCM V3.1 completed at 13:38

    Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY
    Creating installation data file: VMI$ROOT:[SYSUPD]VCM031.VMI_DATA
    VMSINSTAL procedure done at 13:38

Appendix A. Standard System Maintenance Procedures

This section contains the following topics:

A.1. Check and Set Process Account Quotas

User account quotas are stored in the file SYSUAF.DAT. Use the OpenVMS Authorize Utility (AUTHORIZE) to verify and change user account quotas.

To check and set process account quotas:

  1. Set your directory to SYS$SYSTEM, and then run AUTHORIZE, as shown in the following example: 

    $ SET DEFAULT SYS$SYSTEM 
$ RUN AUTHORIZE
 UAF>

  2. At the UAF> prompt, enter the SHOW command with an account name. For example: 

    UAF> SHOW SMITH

  3. To change a quota, enter the MODIFY command.

    The following example changes the FILLM quota for the SMITH account and then exits from the utility: 

    UAF> MODIFY SMITH /FILLM=50 
UAF> EXIT

After you exit from the utility, the system displays messages indicating whether or not changes were made. After 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 HP's OpenVMS documentation.

A.2. Check System Parameter Values

To check the values of your system parameters:

  1. Enter the following command at the DCL prompt to invoke the System Generation Utility (SYSGEN): 

    $ RUN SYS$SYSTEM:SYSGEN 
SYSGEN>

  2. At the SYSGEN> prompt, enter the SHOW command to display the value of a system parameter.

    The following example displays the value for the WSMAX system parameter: 

    SYSGEN> SHOW WSMAX

    Enter the EXIT command at the SYSGEN> prompt to return to DCL level.

A.2.1. Calculate the Values for Global Pages or Pagelets and Global Sections

During the installation, the installation procedure creates a new copy of the DCL command tables that includes the CONSOLE command. For the installation procedure to complete this process successfully, your system must have available enough unused global sections and global pages or pagelets.

Note

If you do not ensure that your system has the necessary global pages or pagelets and global section SYSGEN parameters for the installation, the DCL tables can be unavailable until rebooted.

  • To determine the number of global pages and global sections that the DCL tables at your site require, enter the following commands: 

    $ INSTALL 
INSTALL> LIST SYS$LIBRARY:DCLTABLES.EXE/GLOBAL 
The output generated is similar to the following: 
DCLTABLES;219 Open Hdr Shar Lnkbl System Global Sections 
DCLTABLES_001 (06000000) PRM SYS Pagcnt/Refcnt=484/21296

    In this example, the DCL command table uses 1 global section, as indicated by the single entry DCLTABLES_001. It also uses 484 global pages, indicated by the Pagcnt. Therefore, to replace your DCL command table to include the ADVISE command, this system needs a minimum of 1 unused global section and 484 unused global pages.

  • To calculate the number of unused global sections, enter the following command: 

    INSTALL> LIST/GLOBAL/SUMMARY 
Summary of Local Memory Global Sections 
299 Global Sections Used, 32316/12684 Global Pages Used/Unused

    In this example, there are 299 used global sections and 12684 unused global pages. Because this system requires 484 global pages to replace its DCL command table and 12684 are available, the GBLPAGES parameter does not need to be increased.

  • To check the current value of GBLSECTIONS, enter the following sequence of commands: 

    $ RUN SYS$SYSTEM:SYSGEN
SYSGEN> USE CURRENT 
SYSGEN> SHOW GBLSECTIONS

    These commands produce output similar to the following: 

    Parameter Name    Current    Default    Minimum    Maximum    Unit    Dynamic
--------------    -------    -------    -------    -------    ----    ---------
GBLSECTIONS       500        128        20         4095       Sections

  • To make the calculation for this system, subtract the number of used GBLSECTIONS from the number of current GBLSECTIONS. 

    For example: 500 - 299 = 201 unused sections

Because this system required only one global section to replace its DCL command table and there are 201 unused global sections, the value of the SYSGEN parameter GBLSECTIONS would not need to be altered.

If you need to change the number of global pages, pagelets, or sections, invoke AUTOGEN after entering the new parameter values in SYS$SYSTEM:MODPARAMS.DAT.

A.2.2. Change System Parameter Values with AUTOGEN

Use the AUTOGEN command procedure to change system parameters. AUTOGEN automatically adjusts values for parameters that are associated with the values you reset manually.

To change system parameters with AUTOGEN:

  1. Edit the following file: 

    SYS$SYSTEM:MODPARAMS.DAT

  2. Change a parameter value listed in this file, delete the current value associated with that parameter and enter the new value.

  3. To add a new parameter, add a line to the file that includes both the name of the parameter and its value. For example: 

    WSMAX = 8096

  4. To modify incremental parameters such as free global pages or pagelets and global sections, use ADD_parameter. The following example increases the global page setting by 2000: 

    ADD_GBLPAGES = 2000

    Note

    When you set the page file quota, do not use a value that exceeds the amount of page file space available on the system.

  5. After you make all your changes, exit from the editor and execute the AUTOGEN procedure to recalculate your system parameters.

    The following command recalculates your system parameters and reboots the system: 

    $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT

When you specify REBOOT, AUTOGEN performs an automatic system shutdown, and then reboots the system. Any users logged on to the system are immediately disconnected during the shutdown. The automatic reboot puts the new parameter values into effect.

The AUTOGEN utility automatically adjusts some of the SYSGEN parameters based on the consumption of resources since the last reboot. If you do not want to take advantage of this automatic adjustment, include the NOFEEDBACK qualifier on the AUTOGEN command line.

For more information about using AUTOGEN, refer to HP's OpenVMS System Management Utilities Reference manual.

A.3. Set Dynamic Parameter Values

Use the System Generation Utility (SYSGEN) to set dynamic parameter values. Dynamic parameters changed with the SYSGEN WRITE ACTIVE command become active immediately without any need to reboot your system. Rebooting returns the dynamic parameter values to their previous settings.

After you change the dynamic parameter values, complete the installation before rebooting the system. After you finish with the installation, you can reset the dynamic parameters to their previous values or let them be reset automatically when you next reboot your system.

If the dynamic parameter values on your system are less than the values listed in Installation Procedure Requirements, use the following series of commands to change the values. This example changes the CLISYMTBL value to 250: 

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