HP OpenVMS Systems Documentation

This appendix provides a list of files provided by the DECwindows base and workstation support components included on the OpenVMS VAX distribution kit.

E.1 Table of Components

Table E-1 contains the name of the DECwindows display server and fonts components, the directory where the component can be found, a brief description of what the component does, and one of the following component classifications:

• BASE --- Indicates that the component is part of all installations. BASE Component Class files are located in savesets B and C.
• WS --- Indicates that the component is part of the workstation support. WS Component Class files are located in saveset D.
• FONT --- Indicates the component is part of the fonts component. FONT Component Class files are located in savesets E (75 DPI fonts) and C (100 DPI fonts).

This appendix lists files installed either over or under existing files during an upgrade.

F.1 Where Files Are Installed

During an upgrade, the procedure replaces certain files that exist on your system with new versions of those files from the OpenVMS VAX distribution kit. For some system files, the upgrade procedure does not replace your existing system files, which might contain customizations for your site. Instead, the procedure retains your existing file and installs the new file from the kit at a version number higher or at a version number lower than your existing file.

You can use the DCL command DIFFERENCES to compare the contents of your existing files and the contents of the new files provided by OpenVMS VAX Version 7.3. Enter the command using the following syntax:

The /OUTPUT qualifier causes the DIFFERENCES command to write the list of differences to the output file you specify. This output file has the default file type .DIF. For more information about using the DIFFERENCES command, refer to the OpenVMS DCL Dictionary.

New files that the procedure installs at a version number higher than your existing files are referred to as new_over files. You must use these files at least until you complete the upgrade. After you have upgraded your system, you can add your customizations to these files.

New files installed at a version number lower than the existing files are referred to as new_under files. This allows you to continue to use your existing files during and after the upgrade.

If you purge a new_over file, you are left with the new version of the file provided by the distribution kit, and any customizations you made to the existing file are lost. If you purge a new_under file, you are left with the file that existed before the upgrade.

In addition to the new_over and new_under files, there are certain files that are intended to contain your site-specific modifications. During an upgrade, the old versions of these files are retained if they were present before the upgrade. The new version of the file is installed only if no old version is present on your system. With the exception of TFF$STARTUP.COM, there is a corresponding .TEMPLATE file for each of the site-specfic files. The new version of the .TEMPLATE file replaces the old version.

F.1.1 NEW_OVER Files

During an upgrade, the following new files are installed over (that is, at a version number higher than) the existing files:

[SYSEXE]SHUTDOWN.COM
[SYSEXE]STARTUP.COM
[SYSHLP]HELPLIB.HLB
[SYSLIB]ADARTL.EXE
[SYSLIB]BASRTL.EXE
[SYSLIB]BASRTL2.EXE
[SYSLIB]BLAS1RTL.EXE
[SYSLIB]COBRTL.EXE
[SYSLIB]DBLRTL.EXE
[SYSLIB]DCLTABLES.EXE
[SYSLIB]ENCRYPSHR.EXE
[SYSLIB]FORRTL.EXE
[SYSLIB]FORRTL2.EXE
[SYSLIB]IMAGELIB.OLB
[SYSLIB]LBRSHR.EXE
[SYSLIB]LIBRTL.EXE
[SYSLIB]LIBRTL2.EXE
[SYSLIB]MTHRTL.EXE
[SYSLIB]PASRTL.EXE
[SYSLIB]PLIRTL.EXE
[SYSLIB]PPLRTL.EXE
[SYSLIB]RPGRTL.EXE
[SYSLIB]SCNRTL.EXE
[SYSLIB]STARLET.OLB
[SYSLIB]UVMTHRTL.EXE
[SYSLIB]VAXCRTL.EXE
[SYSLIB]VAXCRTLG.EXE
[SYSLIB]VBLAS1RTL.EXE
[SYSLIB]VMSRTL.EXE
[SYSLIB]VMTHRTL.EXE
[SYSMGR]DBLSTRTUP.COM
[SYSMGR]WELCOME.TEMPLATE

During an upgrade, the following new files are installed under (that is, at a version number lower than) the existing files:

[SYS$LDR]VMS$SYSTEM_IMAGES.DATA
[SYS$STARTUP]ESS$LAST_STARTUP.DAT
[SYS$STARTUP]VMS$LAYERED.DAT
[SYSEXE]VMS$IMAGE_VERSION.DAT
[SYSLIB]CDA$ACCESS.EXE
[SYSLIB]CDDSHR.EXE
[SYSLIB]DECW$DWTLIBSHR.EXE
[SYSLIB]DECW$PRINTWGTSHR.EXE
[SYSLIB]DECW$XLIBSHR.EXE
[SYSLIB]EPC$FACILITY.TLB
[SYSLIB]EPC$SHR.EXE
[SYSLIB]UISSHR.EXE
[SYSMSG]EPC$MSG.EXE
[SYSLIB]XDPS$DPSBINDINGSSHR.EXE
[SYSLIB]XDPS$DPSCLIENTSHR.EXE
[SYSLIB]XDPS$DPSLIBSHR.EXE
[SYSLIB]XNL$SHR.EXE
[SYSMGR]AMDS$DRIVER_ACCESS.TEMPLATE
[SYSMGR]AMDS$LOGICALS.TEMPLATE

The following files are intended to contain site-specific modifications. Note that, with the exception of TFF$STARTUP.COM, there is a corresponding .TEMPLATE file for each of these files. The new version of the .TEMPLATE file replaces the old version.

[SYS$STARTUP]ICC$SYSTARTUP.COM
[SYSEXE]SYSUAF.DAT
[SYSMGR]AGEN$NEW_NODE_DEFAULTS.DAT
[SYSMGR]AGEN$NEW_SATELLITE_DEFAULTS.DAT
[SYSMGR]LAT$SYSTARTUP.COM
[SYSMGR]LOGIN.COM
[SYSMGR]SYCONFIG.COM
[SYSMGR]SYLOGICALS.COM
[SYSMGR]SYLOGIN.COM
[SYSMGR]SYPAGSWPFILES.COM
[SYSMGR]SYSECURITY.COM
[SYSMGR]SYSHUTDWN.COM
[SYSMGR]SYSTARTUP_VMS.COM
[SYSMGR]TFF$STARTUP.COM

During the OpenVMS installation or upgrade procedure, the OpenVMS Management Station server software is automatically installed on your OpenVMS system disk.

If you accepted the default options the PC client files will be located in SYS$COMMON:[TNT.CLIENT]. If these files are deleted from your system you can either tailor (see Chapter 10) them back on, or download them from the following location:

http://www.openvms.compaq.com/openvms/products/argus/index.html#ordering

If the TNT$* server files have been deleted from SYS$SYSTEM, you can recover the server files by reinstalling the OpenVMS operating system.

After you have ensured that OpenVMS Management Station software is installed on your system, follow the procedures described in this appendix.

G.1 Preparing Your OpenVMS System

You must prepare your OpenVMS system to run the server software so that your system can properly interact with the PC running the client software. The procedures include the following:

• Set up within a mixed-architecture cluster environment (if applicable).
• Start the server on other nodes.
• Update the printer and storage database.
• Edit the system files.
• Allow OpenVMS Management Station to control the printer and storage environment.
• Keep your printer environment up to date.
• Check if running third-party TCP/IP stacks.
• Recover from a failure.
• Determine and report problems.

The OpenVMS Management Station server creates several configuration files:

• TNT$UADB.DAT
• TNT$ACS.DAT
• TNT$JOURNAL.TNT$TRANSACTION_JOURNAL
• TNT$MONITOR.DAT
• TNT$MONITOR.TNT$MONITOR_JOURNAL
• TNT$EMERGENCY_MOUNT.COM

In a common-environment cluster with one common system disk, you use a common copy of each of these files located in the SYS$COMMON:[SYSEXE] directory on the common system disk, or on a disk that is mounted by all cluster nodes. No further action is required.

However, to prepare a common user environment for an OpenVMS Cluster system that includes more than one common VAX system disk or more than one common Alpha system disk, you must coordinate the files on those disks.

The following rules apply:

• Disks holding common resources must be mounted early in the system startup procedure, such as in the SYLOGICALS.COM procedure.
• You must ensure that the disks are mounted with each cluster reboot.

Follow these steps to coordinate files:

1. Decide where to locate the files. In a cluster with multiple system disks, system management is much easier if the common system files are located on a single disk that is not a system disk.
2. Copy TNT$UADB.DAT, TNT$ACS.DAT, TNT$MONITOR.DAT, TNT$MONITOR.TNT$MONITOR_JOURNAL, TNT$EMERGENCY_MOUNT.COM, and TNT$JOURNAL.TNT$TRANSACTION_JOURNAL to a location other than the system disk.
3. Edit the file SYS$COMMON:[SYSMGR]SYLOGICALS.COM on each system disk and define logical names that specify the location of the cluster common files.

   Example
   
   If the files will be located on $1$DJA16, define logical names as follows:

   $ DEFINE/SYSTEM/EXEC TNT$ACS - _$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$ACS.DAT

   
   TNT$EMERGENCY_MOUNT.COM will be created in SYS$SYSTEM or in the directory pointed to by the TNT$ACS logical, if the logical exists.

   $ DEFINE/SYSTEM/EXEC TNT$UADB - _$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$UADB.DAT $ DEFINE/SYSTEM/EXEC TNT$JOURNAL - _$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$JOURNAL.TNT$TRANSACTION_JOURNAL $ DEFINE/SYSTEM/EXEC TNT$MONITOR - _$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$MONITOR.DAT $ DEFINE/SYSTEM/EXEC TNT$MONITORJOURNAL - _$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$MONITOR.TNT$MONITOR_JOURNAL

4. To ensure that the system disks are mounted correctly with each reboot, follow these steps:
   1. Copy the SYS$EXAMPLES:CLU_MOUNT_DISK.COM file to the [VMS$COMMON.SYSMGR] directory, and edit it for your configuration.
   2. Edit SYLOGICALS.COM and include commands to mount, with the appropriate volume label, the system disk containing the shared files.

      Example
      
      If the system disk is $1$DJA16, include the following command:

   $ @SYS$SYSDEVICE:[VMS$COMMON.SYSMGR]CLU_MOUNT_DISK.COM - _$ $1$DJA16: volume-label

If you plan to run OpenVMS Management Station on more than one node in an OpenVMS Cluster without a reboot, you need to start the software on those nodes.

Use SYSMAN to start the server as follows:

$ @SYS$STARTUP:TNT$STARTUP.COM

Or, you can log into each node that shares the SYS$COMMON: directory and enter the following command:

$ @SYS$STARTUP:TNT$STARTUP.COM

If you are performing an upgrade or a reinstallation and OpenVMS Management Station is already running on the node, add the RESTART parameter to the startup command, as follows:

$ @SYS$STARTUP:TNT$STARTUP.COM RESTART