Document revision date: 19 July 1999

The following list is offered to help new users with some common concerns and questions regarding the License Management Facility (LMF).

• If you do not have a valid OpenVMS VAX license that is registered and activated, the system displays a warning message as part of system startup and restricts system use to the operator's console, OPA0.
• If a checksum error is displayed when you register a license, check all the fields of data that you entered, including the checksum itself.
• After your PAKs are registered, they are activated (loaded) automatically as part of each system startup.
• If an OpenVMS VAX availability license is registered with insufficient license units for the specified VAX computer, the system displays a warning message at system startup but allows normal system use at the console level only.
• If an OpenVMS VAX activity license is registered with insufficient license units to meet your user requirements, the system displays the following message when the user (process) attempts to log in:

  %LICENSE-F-EXCEEDED, licensed product has exceeded current license limits

  
  A user can always log in to the operator's console, OPA0, however.

• The default LICENSE database is located in the file SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB. You can move the database, although Compaq does not recommend doing so. If you move the database, you must either define the logical name LMF$LICENSE at the system level to point to the new database or use the /DATABASE=filespec qualifier with all LICENSE commands. To redirect LMF to another database location on a more permanent basis, add the following line to the command procedure SYS$MANAGER:SYLOGICALS.COM:

  $ DEFINE/SYSTEM LMF$LICENSE device:[directory]LMF$LICENSE.LDB

  
  If you specify a device other than SYS$SYSDEVICE, you must also mount the specified disk from the SYLOGICALS.COM command procedure.

• Each VAX VMS and OpenVMS VAX Base license is restricted to a single node for permanent PAKs. You must assign a System Communications Services (SCS) name to the license when you register with the VMSLICENSE.COM command procedure, or you must enter a LICENSE MODIFY/INCLUDE=node-name command after you register the license. Although you can successfully activate an unassigned OpenVMS VAX license on a standalone system, you cannot activate one in a VAXcluster environment.

  Note The SCS node name is not necessarily the DECnet node name. SCSNODE is a system parameter; it can be a maximum of 6 alphabetic characters.

The following paragraphs describe Volume Shadowing for OpenVMS licenses.

B.4.1 When to Register

After you install OpenVMS VAX Version 7.2, you must register your Volume Shadowing for OpenVMS license before you can use the volume shadowing software. If you upgraded to OpenVMS VAX Version 7.2, you do not need to reregister this license.

B.4.2 Volume Shadowing Software Phase I and Phase II

In the past, volume shadowing has offered two modes of operation: phase I and phase II. The original implementation of volume shadowing, phase I, was HSC controller-based. The newer implementation, phase II, is host-based and provides performance superior to phase I.

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.4.3 Types of Licenses

Two types of volume shadowing licenses are valid for OpenVMS VAX Version 7.2:

• 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.2 changes to per-disk licensing for volume shadowing, see Section 1.1.2.

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

B.5 Other System Integrated Product Licenses

After you install OpenVMS VAX Version 7.2, you must register licenses for any system integrated product. If you upgraded to OpenVMS VAX Version 7.2, 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 Return:

>>> 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 Return:

   >>> 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:

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 Return 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 Return:

   $ 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 Return:

   $ 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 Return:

   >>> 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:

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 Return 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 Return:

   $ 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 Return:

   >>> 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, refer to 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 Return:

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

C.1.7 VAX 9000 Series

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 boo

   Previous

   Next

   Contents

   Index

   	privacy and legal statement
   6521PRO_015.HTML