OpenVMS VAX Version 7.1 Upgrade and Installation Manual

With the release of OpenVMS VAX Version 6.2, phase I Volume Shadowing is no longer available. Refer to the Volume Shadowing for OpenVMS manual for instructions about moving from phase I to phase II.

B.5.3 Types of Licenses

Two types of Volume Shadowing licenses are valid for OpenVMS VAX Version 7.1:

• Capacity license---If you are using this type of license, you must have one license for each node in a cluster that is accessing shadowed data.
• Per-disk license---If you are using this type of license, you must have one license for every disk contained in the shadow set.
  For information about OpenVMS VAX Version 7.1 changes to per-disk licensing for Volume Shadowing, refer to Section 1.2.1.

See the Volume Shadowing for OpenVMS manual for more information about these two licenses.

B.6 Other System Integrated Product Licenses

After you install OpenVMS VAX Version 7.1, you must register licenses for any system integrated product. If you upgraded to OpenVMS VAX Version 7.1, you do not need to reregister licenses for system integrated products.

You must boot from the [SYSF] root during phases 2, 3, and 4 of the upgrade procedure. Different VAX computers require that you use different booting procedures. This appendix describes how to boot the various VAX computers from [SYSF].

Go to the section that describes your VAX computer and follow the instructions for booting from [SYSF]. If you need more information about booting, refer to the upgrade and installation supplement for your VAX computer.

C.1.1 MicroVAX and VAXstation Computers

The information in this section applies to the following VAX computers:

• VAXstation II, VAXstation II/GPX, and MicroVAX II
• VAXstation 2000 and MicroVAX 2000
• VAXstation 3100 and MicroVAX 3100 series
• VAXstation 3200 and 3500
• VAXstation 3520 and 3540
• VAXstation 4000
• VAXft 110, 310, 410, 610, and 612
• MicroVAX 3300, 3400, 3500, 3600, 3800, and 3900

To boot from [SYSF], enter the BOOT command in the following format and press the Return key:

>>> B/F0000000 device-name

Substitute the device name of the system disk for device-name.

C.1.2 VAX 8530, 8550, 8810 (8700), 8820-N (8800) Computers

To boot from [SYSF], use the following procedure:

1. Press Ctrl/P. Enter the following command at the console-mode prompt (>>>) and press the Return key:

   >>> HALT
   

2. Enter the BOOT command at the console-mode prompt (>>>) in the following format:

   >>> B dddn /R5:F0000000
   

   
   Substitute BCI, BDA, or UDA for ddd. Substitute the unit number of the drive holding the system disk for n.

To boot from [SYSF], use the following procedure:

1. Enter the following command at the PS-OS-0> prompt and press Return:

   PS-OS-0> HALT/CPU=ALL
   

2. Enter the BOOT command at the PS-CIO-0> prompt in the following format:

   PS-CIO-0> B dddn /R5=F0000000
   

   
   Substitute BCI or BDA for ddd. Substitute the unit number of the drive holding the system disk for n.

To boot from [SYSF], create a command procedure named SYFBOO.CMD before the upgrade is started.

To create SYFBOO.CMD, use the following procedure:

Note

This procedure assumes that you have installed and booted the OpenVMS VAX operating system and are logged in to the SYSTEM account.

1. Log in to the SYSTEM account.
2. Make sure that the console media is in the console drive.
3. To connect the console drive to the system, enter the following commands and press the Return key after each one:

   $ RUN SYS$SYSTEM:SYSGEN
   SYSGEN> CONNECT CONSOLE
   SYSGEN> EXIT
   

4. Use the Exchange utility to copy the appropriate boot command procedure from the console media to your current directory on the system disk. If the system disk is on an HSC drive and you have created DEFBOO.CMD, enter the following command and press Return:

   $ EXCHANGE COPY CSA1:DEFBOO.CMD *
   

   
   On the VAX--11/750 computer, if the system disk is on a local drive, copy the boot command procedure that matches the drive that holds the system disk. For example, suppose the system disk is on an RP06 drive and has a controller designation of A and a unit number of one. Enter the following command and press the Return key:

   $ EXCHANGE COPY CSA1:DA1BOO.CMD *   
   

5. Edit the boot command procedure. Change the line that deposits a value in register 5 (R5). This line contains the comment !software boot flags. The value is a hexadecimal number with eight digits. For example:

   D/G R5 0    !software boot flags
   

   Change the left-most digit of the value to reflect the name of the root directory from which you want to boot. For example, to boot from the [SYSF] root directory, change the line as follows:

   D/G/L R5 F0000000     !designated root is SYSF
   

6. Rename the boot command procedure to SYFBOO.CMD. For example, if the boot command procedure is DEFBOO.CMD, enter the following command and press the Return key:

   $ RENAME DEFBOO.CMD SYFBOO.CMD
   

7. Use the Exchange utility to copy SYFBOO.CMD back to the console media. Enter the following command and press Return:

   $ EXCHANGE COPY SYFBOO.CMD CSA1:SYFBOO.CMD
   

8. When the copy operation completes, enter the following command and press Return:

   $ DISMOUNT CSA1
   

9. To secure the console media from unauthorized access, you must enter the following command and press Return:

   $ MOUNT/FOREIGN/SYSTEM/NOWRITE/NOASSIST CSA1
   

To boot from [SYSF], use the following procedure:

1. Make sure the console media is in the console drive. On the VAX--11/750 computers, make sure the keylock switch is set to LOCAL. Set the BOOT DEVICE switch to position A.
   On the VAX 8200 computer, set the upper keylock switch to ENABLE and the lower keylock switch to HALT.
2. Press Ctrl/P.
3. On the VAX--11/750 computer, enter the following command and press the Return key:

   >>> B/800 DDA0
   

   
   On the VAX 8200 computer, enter the following command at the console-mode prompt (>>>) and press Return:

   >>> B/R5:800 CSA1
   

4. At the BOOT58> prompt, enter the following command:

   BOOT58> @SYFBOO.CMD
   

To boot from [SYSF], create a command procedure named SYFBOO.CMD (for VAX--11/730, 11/780, and 11/785 computers) or SYFBOO.COM (for VAX 8600 and 8650 computers) before the upgrade is started.

To create SYFBOO.CMD or SYFBOO.COM, use the following procedure:

Note

This procedure assumes that you have installed and booted the OpenVMS VAX operating system and are logged in to the SYSTEM account.

1. Log in to the SYSTEM account.
2. Make sure that the console media is in the console drive. On the VAX 8600 computer, make sure the TERMINAL CONTROL switch is set to LOCAL.
3. To connect the console drive, enter the following commands and press the Return key after each one:

   $ RUN SYS$SYSTEM:SYSGEN
   SYSGEN> CONNECT CONSOLE
   SYSGEN> EXIT
   

4. Use the Exchange utility to copy DEFBOO.CMD (for VAX--11/730, 11/780, and 11/785 computers) or DEFBOO.COM (for VAX 8600 and 8650 computers) from the console media to your current directory on the system disk. On the VAX--11/780, 11/785, and 8600 computers, enter a command similar to the following and press Return:

   $ EXCHANGE COPY CSA1:DEFBOO.CMD *
   

   
   On the VAX--11/730 computer, enter the following command and press the Return key:

   $ EXCHANGE COPY CSA2:DEFBOO.CMD *
   

5. Edit DEFBOO.CMD or DEFBOO.COM. Change the line that deposits a value in register 5 (R5). On the VAX--11/730, 11/780, and 11/785 computers, this line contains the comment !software boot flags. On the VAX 8600, this line contains the comment !Use R5 for optional boot control flags [SYSB.]. The value is a hexadecimal number with eight bits. For example:

   DEPOSIT R5 10000000     !software boot flags 
   

   
   Change the left-most digit of the value to reflect the name of the root directory from which you want to boot. For example, to boot from [SYSF], change the line as follows:

   DEPOSIT R5 F0000000     !software boot flags 
   

6. Rename DEFBOO.CMD to SYFBOO.CMD (or DEFBOO.COM to SYFBOO.COM), as follows:

   $ RENAME DEFBOO.CMD SYFBOO.CMD
   

7. Use the Exchange utility to copy SYFBOO.CMD or SYFBOO.COM to the console media. On the VAX--11/780, 11/785, and 8600 computers, enter a command similar to the following:

   $ EXCHANGE COPY SYFBOO.CMD CSA1:SYFBOO.CMD
   

   
   On the VAX--11/730 computer, enter the following command and press the Return key:

   $ EXCHANGE COPY SYFBOO.CMD CSA2:SYFBOO.CMD
   

8. When you are finished, enter a command similar to the following and press Return:

   $ DISMOUNT CSA1
   

9. To secure the console media from unauthorized access, you must enter a command similar to the following and press Return:

   $ MOUNT/FOREIGN/SYSTEM/NOWRITE/NOASSIST CSA1
   

To boot from [SYSF] during an upgrade, use the following procedure:

1. Make sure the console media is in the console drive. On the VAX--11/730, 11/780, and 11/785 computers, make sure the keylock switch is set to LOCAL. On the VAX 8600, make sure the TERMINAL CONTROL switch is set to LOCAL.
2. Press Ctrl/P. On the VAX--11/780, 11/785, and 8600 computers, enter the HALT command at the console-mode prompt (>>>) and press the Return key:

   >>> HALT
   

3. Use SYFBOO.CMD to boot from [SYSF]. Enter the following command and press Return:

   >>> B SYF
   

To boot from [SYSF], use the following procedure:

1. If you have a CIBCA-A adapter and are booting over the CI, insert the console tape cartridge in the console drive.
2. Press Ctrl/P to put the system in console mode.
3. Enter the BOOT command in the following format:

   >>> BOOT /R5:F0000000  /XMI:a  /BI:b  [/R3:c]  [/NODE:d]  DUu
   

   
   where:
   • a is the XMI node number of the system disk.
   • b is the VAXBI node number of the system disk.
   • c pertains to volume shadowing. This qualifier is not required unless you are using volume shadowing. For more information, see the Volume Shadowing for OpenVMS manual.
   • d is the HSC node number of the node being accessed. The /NODE qualifier is not necessary if you are booting from a local disk. The HSC node number is in hexadecimal. You can deposit a maximum of two HSC node numbers (if two HSCs are available).
   • u is the unit number of the drive holding the system disk.
   
   For example, suppose you want to boot from [SYSF] on an HSC disk with a unit number of one and your system has the following configuration:
   • The disk is connected to the VAXBI at node 2.
   • The VAXBI you are using is connected to the XMI at node 3.
   • The disk is available to two HSCs, node numbers 0E and 02.
   
   Enter the following command and press the Return key:

   >>> BOOT/R5:F0000000/XMI:3/BI:2/NODE:0E02 DU1
   

   C.1.7 VAX 9000 Series

   The upgrade procedure automatically updates DEFBOO.CMD to boot from [SYSF]. If you want to boot a VAX 9000 computer manually from [SYSF] however, you must set up DEFBOO.CMD to boot from the system disk and perform the following procedure:
   1. Press Ctrl/P to obtain the console prompt.
   2. Enter the following BOOT commands:

      >>> I/K
      >>> BOOT/NOSTART
      >>> DEPOSIT R5 F0000000
      >>> CONTINUE
      

   3. If you set up DEFBOO.CMD properly, the system will boot from the SYSF directory on the system disk and continue with the upgrade procedure.
      If the system does not boot, enter the SHOW CONFIGURATION console command and verify that DEFBOO.CMD contains the correct information for your configuration. For more information, see the OpenVMS VAX Upgrade and Installation Supplement: VAX 9000 Series.

   ---

   Appendix D
   OpenVMS VAX Save Set Subclasses

   This appendix lists the file subclasses contained in the following save sets:

   • VMS070.C---Library save set
   • VMS070.D---Optional save set
   • VMS070.E---Help Message save set
   • VMS070.F---OpenVMS Management Station save set

   D.1 Save Set C Subclasses

   The following files are contained in the Library save set:

   • Network support
     • Incoming Remote File Access files
     • Incoming Remote Terminal files
     • Network Test files
     • Remote Task Loading
   • Programming Support
     • Debugger utility (DEBUG)
     • Image Dump utility (ANALYZE/PROCESS_DUMP)
     • RMS Analyze and FDL Editor utilities (ANALYZE/RMS, ANALYZE/FDL)
     • Message utility (MESSAGE)
     • Object and Shareable Image libraries
     • MACRO libraries
     • MACRO assembler
     • SDL intermediary form of STARLET.MLB
     • Fortran required files
     • VAX C object libraries
     • X/Open transport interface libraries
     • OpenVMS RMS journaling files
   • System programming Support
     • Files-11 ODS--1, ISO 9660, High Sierra ACPs
     • Monitor utility
     • Delta/XDelta debugger
     • System Dump Analyzer utility (ANALYZE/SYSTEM, ANALYZE/CRASH)
     • System Symbol Table file (SYS.STB)
     • Miscellaneous symbol table files
   • Secure User's Environment
     • File Access Control List utilities
     • Print and Batch Queue utilities
     • Input Queue Symbiont (Card Reader)
     • Accounting Log Report Generator utility
     • DECdtm
   • Utilities
     • Mail utility
     • DUMP utility
     • RUNOFF utility
     • Phone utility
     • OpenVMS Help library
     • Foreign Terminal Support
     • LAT-11 terminal server (via Ethernet)
     • Standalone backup
     • Error Log Report Generator utility (ANALYZE/ERROR)
     • DECTPU
     • Terminal Fallback Facility
     • National Character Set utility (NCS)
     • C language internationalization utilities
   • TECO editor
   • EDT documentation
   • OpenVMS workstation support
   • Workstation device support

   D.2 Save Set D Subclasses

   The following files are contained in the Optional save set:

   • Miscellaneous files
   • System map
   • LPA-11 support
   • BLISS required files
   • UETP (the User Environment Test Package)
   • Example files

   D.3 Save Set E Subclasses

   The following files are contained in the Help Message save set:

   • Help Message database

   D.4 Save Set F Subclasses

   The following files are contained in the OpenVMS Management Station save set:

   • OpenVMS Management Station software PC files

   ---

   Appendix E
   DECwindows Display Server and Fonts Components

   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.
   • WS---Indicates that the component is part of the workstation support.
   • FONT---Indicates the component is part of the fonts component.

   Table E-1 DECwindows Display Server and Fonts Components

   File	Purpose	Component Class
   	Files in DECW$KEYMAP Directory
   DECW$KEYMAP		BASE
   	Files in SYS$LOADABLE_IMAGES Directory
   GAADRIVER.EXE	VAXstation II/GPX driver	WS
   GABDRIVER.EXE	VAXstation 2000/GPX driver	WS
   GBBDRIVER.EXE	VAXstation 35x0 driver	WS
   GCADRIVER.EXE	VAXstation II monochrome device driver	WS
   GCBDRIVER.EXE	VAXstation 2000 monochrome device driver	WS
   GEBDRIVER.EXE	Scanproc graphics device driver	WS
   GECDRIVER.EXE	Spxg/gt graphics device driver	WS
   GFBDRIVER.EXE	Low-cost graphics device driver	WS
   IEDRIVER.EXE	Input extension driver	WS
   IKDRIVER.EXE	Keyboard decoder driver	WS
   IMDRIVER.EXE	Mouse decoder driver	WS
   INDRIVER.EXE	Common input function driver	WS
   WSDRIVER.EXE	Set display driver	BASE
   	Files in SYS$SYSTEM Directory
   DECW$FONTCOMPILER.EXE	Font compiler image	FONT
   DECW$MKFONTDIR.EXE	Font utility to generate list of fonts and paths	FONT
   DECW$SERVER_MAIN.EXE	Server main image	WS
   DECW$SETSHODIS.EXE	SHOW DISPLAY command image	BASE
   	Files in DECW$FONT Directory
   See VMS DECwindows Xlib Programming Volume	DECwindows fonts	WS
   	Files in DECW$EXAMPLES Directory
   DECW$FONT_ALIAS_CHARTER.DAT	Example alias file for Charter fonts	FONT
   DECW$FONT_ALIAS_CHARTER_100DPI.DAT	Example alias file for 100 dpi Charter fonts	FONT
   DECW$FONT_ALIAS_FILENAMES.DAT	Brief alias name list for shipped fonts	FONT
   DECW$FONT_ALIAS_KANJI.DAT	Example alias file for Kanjifonts	FONT
   DECW$FONT_ALIAS_LUCIDA.DAT	Example alias file for Lucida fonts	FONT
   DECW$FONT_ALIAS_LUCIDA_100DPI.DAT	Example alias file for 100 dpi Lucida fonts	FONT
   	Files in SYS$LIBRARY Directory
   DECW$DRIVER.MLB	Driver macro library	WS
   DECW$FONTCOMPILER.CLD	CLD for font compile commands	FONT
   DECW$SERVER_DDX_GA.EXE	Server color device support shareable image	WS
   DECW$SERVER_DDX_GB.EXE	Server color device support shareable image	WS
   DECW$SERVER_DDX_GC.EXE	Server monochrome device support shareable image	WS
   DECW$SERVER_DDX_GE.EXE	Server scanproc device-dependent shareable image	WS
   DECW$SERVER_DDX_GF.EXE	Server low-cost graphics device-dependent shareable image	WS
   DECW$SERVER_DIX.EXE	Server device independent support	WS
   DECW$SERVER_XINPUT_IE.EXE	Input extension for handling nonstandard input devices	WS
   DECW$SESSIONSHRP.EXE	Support routines for DECwindows Session Manager	BASE
   DECW$SVEXT_ADOBE_DPS_EXTENSION.EXE	Display PostScript server extension image	WS
   DECW$SVEXT_D2DX_EXTENSIONS.EXE	DECwindows 2D extensions	WS
   DECW$SVEXT_DEC_XTRAP.EXE	Input and event recording and playback extension	WS
   DECW$SVEXT_MULTI_BUFFERING.EXE	DECwindows multi-buffering extension	WS
   DECW$SVEXT_X3D_PEX.EXE	Phigs Extension to X (PEX) for 3D	WS
   DECW$SVEXT_X3D_PEX_GB.EXE	PEX for 35x0 systems	WS
   DECW$SVEXT_X3D_PEX_GB_UCODE.EXE	PEX microcode for 35x0 systems	WS
   DECW$SVEXT_X3D_PEX_GE.EXE	PEX for scanproc systems	WS
   DECW$SVEXT_X3D_PEX_STP.EXE	PEX for scanproc systems with geometry processor	WS
   DECW$SVEXT_X3D_PEX_STP_UCODE.EXE	PEX microcode for scanproc systems with geometry processor	WS
   DECW$SVEXT_X3D_PEX_VCFB.EXE	PEX color frame buffer (software PEX)	WS
   DECW$SVEXT_XIE.EXE	DECwindows imaging extension	WS
   DECW$SVEXT_XINPUTEXTENSION.EXE	DECwindows input extension	WS
   DECW$TRANSPORT_COMMON.EXE	Common transport shareable image	BASE
   DECW$TRANSPORT_DECNET.EXE	DECnet transport image	BASE
   DECW$TRANSPORT_LOCAL.EXE	Local transport image	BASE
   DECW$TRANSPORT_TCPIP.EXE	TCP/IP transport image	BASE
   DECW$XPORTCOM.H	Common transport definitions	BASE
   DECW$XPORTCOM.MAR	Common transport definitions	BASE
   DECW$XPORTCOM.R32	Common transport definitions	BASE
   DECW$XPORTDEF.H	Transport definitions	BASE
   DECW$XPORTDEF.MAR	Transport definitions	BASE
   DECW$XPORTDEF.R32	Transport definitions	BASE
   DECW$XPORTMAC.R32	Transport BLISS macros	BASE
   DECW$XPORTMSG.R32	Transport message symbols	BASE
   XDPS$MASTERDPSVM.DAT	Display PostScript support file	WS
   	Files in SYS$MANAGER Directory
   DECW$DEVICE.COM	Device detection and configuration	BASE
   DECW$DEVICE_GE.COM	Scanproc device detection and configuration	WS
   DECW$DEVICE_GF.COM	Low-cost graphics device detection and configuration	WS
   DECW$DEVICE_GG.COM	Scanproc turbo device detection and configuration	WS
   DECW$RGB.DAT	Definitions of the color names used by the XStoreNamedColor and XAllocNamedColor requests	WS
   DECW$STARTSERVER.COM	Server initialization and startup	WS
   	Files in SYS$MESSAGE Directory
   DECW$TRANSPORTMSG.EXE	Transport message image	BASE
   	Files in SYS$UPDATE Directory
   DECW$MKFONTDIR.COM	Command file to invoke DECW$MKFONTDIR.EXE font utility	FONT

   ---

   Appendix F
   NEW_OVER and NEW_UNDER Files

   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.1. Enter the command using the following syntax:

   DIFFERENCES/OUTPUT=filespec existing_filename new_filename 
   

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

   ---

   Previous | Next | Contents | [Home] | [Comments] | [Ordering info] | [Help]

   ---

   
   

     6487P012.HTM
     OSSG Documentation
      9-DEC-1996 10:54:19.13
   

   Copyright © Digital Equipment Corporation 1996. All Rights Reserved.

   Legal