Document revision date: 19 July 1999

The OpenVMS Version 7.2 release introduced a problem where users were unable to mount multiple CD-ROMs privately. This problem also caused XQPERR bugchecks.

This problem has been corrected for OpenVMS Alpha Version 7.2-1. However, a mount verification problem now exists. For a description of the mount verification problem and its workaround, see Section 3.10.

3.12 Multipath Devices: Volume Rebuilds During Mount Operation

When doing a Mount operation on a Fibre Channel or SCSI device, a volume rebuild is sometimes performed even though the volume has previously been dismounted without any apparent error. For example:

$ dismount $1$DGA32762: $ $ mount/cluster $1$DGA32762: MYVOL %MOUNT-I-MOUNTED, DGA1016 mounted on _$1$DGA32762: (FIBRE2) %MOUNT-I-REBUILD, volume was improperly dismounted; rebuild in progress

Workaround

A user with privileges can work around this problem by issuing an I/O to the device immediately before dismounting it. For example:

$ CREATE $1$DGA32762:[0,0]A.TMP $ DELETE $1$DGA32762:[0,0]A.TMP;0

This problem will be addressed in a future release.

3.13 Multipath Failover Fails Infrequently on HSZ70/HSZ80 Controllers

Under heavy load, a host-initiated manual or automatic path switch from one controller to another may fail on an HSZ70 or HSZ80 controller. Testing has shown this to occur infrequently. The problem will be fixed in a future release.

This problem does not occur on the HSG80 controller.

3.14 Multipath SCSI and FC Shadow Sets: Adjustments to System Parameters

The use of default settings for certain system parameters may lead to the occasional removal of shadow set members that are configured for multipath support. The shadow set members where this has been observed are using Volume Shadowing for OpenVMS.

Therefore, when configuring multipath shadow sets using Volume Shadowing for OpenVMS, follow the recommendations in Table 3-2 for setting these system parameters.

Table 3-2 System Parameter Settings for Multipath Shadow Sets

System Parameter	Recommended Setting
MSCP_CMD_TMO	60 as a minimum. The value of 60 has been appropriate for most configurations. Some configurations may require a higher setting.
SHADOW_MBR_TMO	3 x MSCP_CMD_TMO
SHADOW_SYS_TMO	3 x MSCP_CMD_TMO
MVTIMEOUT	At least 2 x SHADOW_MBR_TMO

The following example shows the use of the recommended settings:

MSCP_CMD_TMO 60 SHADOW_MBR_TMO 180 SHADOW_SYS_TMO 180 MVTIMEOUT 1200

3.15 Multiple Tape Density Updates

This section provides information on the use of multiple tape density for OpenVMS Alpha Version 7.2-1.

3.15.1 Guidelines for Multiple Tape Density Use

The following guidelines pertain to the use of multiple tape density:

• Compaq strongly advises that you be consistent in your use of the /DENSITY qualifier across all command lines. For example, if /DENSITY=TK88 is specified on the INIT command, then it should also be specified on all subsequent command lines, such as MOUNT and BACKUP.
• Beginning in OpenVMS Alpha Version 7.2-1, more stringent checks have been implemented to prevent unsupported densities from being sent to the tape drive. Consequently, densities that may have been previously allowed (but ignored) might now return a fatal error. For example, $INIT/DENSITY=1600 to a locally attached TZ89 tape drive results in the error "IVDENS, invalid density."
  This change in behavior also has implications for served tapes in mixed version OpenVMS clusters. If a client node is running OpenVMS Alpha Version 7.2-1 and the server node is not, then the /DENS=1600 qualifier (mentioned above) generates the IVDENS error when issued on the client, but does not generate that error when issued on the server. Similar logic applies when the server is running OpenVMS Alpha Version 7.2-1 and the client is not; in that case, more stringent density checks are made for commands issued on the server, and less stringent checks for commands issued on the client.
• The SHOW DEVICE/FULL and SHOW MAGTAPE commands are intended to display the current working density of the device. In most cases the display is accurate; however, in some cases it is impossible for the software to determine the current density until after a write request has been completed for the drive. In such cases, the density display is updated only after some time delay.
• The TLZ09 and other DAT drives have cartridge-dependent densities. Regardless of the density specified on the command line (for example, DDS1, DDS2), the drive will operate at the density that is appropriate for the current cartridge in use.
• Beginning in OpenVMS Alpha Version 7.2-1, the presence of both the /DENSITY=DEFAULT and /MEDIA=[NO]COMPACTION qualifiers on the same command line will be rejected as an illegal combination. This is because DEFAULT density already implies a compaction status, and should not be superceded by the /MEDIA qualifier. Use of these two qualifiers on the same command line is still supported as long as you avoid using the keyword DEFAULT. For example, /DENSITY=TK89/MEDIA=COMPACTION is a legal combination.
• Use of the new tape density qualifiers (for example, TK89, DDS1, 8200) is not supported on any OpenVMS VAX system.

The following documentation updates have been made to reflect multiple tape density changes.

• OpenVMS DCL Dictionary
  The following commands and lexical function have been updated:
  • INITIALIZE command
    The keywords following the note in the table listing density values are valid on Alpha systems only.
  • SET MAGTAPE/DENSITY command
    The keywords following the note in the table listing density values are valid on Alpha systems only.
  • F$GETDVI lexical function
    The following item codes have been added to F$GETDVI:

    Item	Return Type	Information Returned
    MT3_DENSITY	String	Current density of the device (tapes only)
    MT3_SUPPORTED	String	TRUE or FALSE to indicate whether the device supports densities defined in the MT3DEF (for Alpha tapes only)

• OpenVMS System Services Reference Manual
  The following item codes have been added to $GETDVI:
  • DVI$_MT3_SUPPORTED
    When you specify DVI$_MT3_SUPPORTED, $GETDVI returns the density of the device. Valid for tapes only. This code is an unsigned longword integer.
  • DVI$_MT3_DENSITY
    When you specify DVI$_MT3_DENSITY, the return value of 1 indicates that the device supports tape density codes defined by MT3DEF. Valid for tapes only. This code is an unsigned longword integer.

For systems with the PowerStorm 4D10T (ELSA) graphics card, support for graphics is not part of the OpenVMS Version 7.2-1 installation. You can install the graphics support from the [ELSA] directory located on the OpenVMS Alpha Version 7.2-1 Operating System CD-ROM. Use the following commands to install the ELSA kit:

1. Use commands similar to the following to start the ELSA_INSTALL.COM command procedure and copy the the ELSA support files to the appropriate directories on the system disk.
   For example, if OpenVMS is installed from a CD in DKA400:, log in to a privileged account after OpenVMS has booted and enter the following commands:

   $ MOUNT/OVERRIDE=ID DKA400: $ @DKA400:[ELSA.KIT]ELSA_INSTALL $ DISMOUNT DKA400:

2. Next, load the graphics drivers and start DECwindows. Either reboot the system or execute the following commands:

   $ MCR SYSMAN IO AUTOCONFIGURE $ @SYS$MANAGER:DECW$STARTUP

   
   If you are running DECW$STARTUP.COM from a graphics console, log off the graphics console. Once you log off from the console, a DECwindows login box is displayed. Then you can log in to a DECwindows session.

This section describes changes and updates to the OpenVMS Alpha Version 7.2-1 documentation.

3.17.1 DCL Commands and Lexical Functions

The following table describes updates to the DCL command and lexical function documentation for OpenVMS Alpha Version 7.2-1.

DCL Command/Lexical	Documentation Update
ANALYZE	The /DISK qualifier is valid for Files-11 On-Disk Structure Level 5 disks.
COPY	The /CONCATENATE qualifier is valid for Files-11 On-Disk Structure Level 5 disks.
DUMP	The /DIRECTORY qualifier is valid for Files-11 On-Disk Structure Level 5 disks.
F$GETDVI	The item code, PREFERRED_CPU, has been added to this command. The tables listing values returned by the DEVTYPE item are incomplete. For a more complete list, refer to the $DCDEF module in STARLET.
F$GETSYI	The item code, PAGE_SIZE, has been added to this command.
INITIALIZE	The documentation for the /CLUSTER_SIZE qualifier has been updated. The /ERASE qualifier is valid for Files-11 On-Disk Structure Level 5 disks.
SET FILE	The /BACKUP qualifier is valid for Files-11 On-Disk Structure Level 5 disks.
SET PREFERRED_PATH	This command was inadvertently documented as SET PATH_PREFERRED in the OpenVMS Version 7.2 New Features Manual.
SET PRINTER	The qualifier, /POLLED, has been added to this command.

3.17.2 I/O User's Reference Manual

Section 3.4.12 in the OpenVMS I/O User's Reference Manual states that the data security erase function is applicable only for certain listed tape drives.

This statement is incorrect and has been removed, as this function applies to newer tape drives as well.

3.17.3 Migrating an Application from OpenVMS VAX to OpenVMS Alpha

Migrating an Application from OpenVMS VAX to OpenVMS Alpha has been archived for OpenVMS Alpha Version 7.2-1. This manual will be updated and reproduced for a future release.

3.17.4 System Services

The following table describes updated system services documentation for OpenVMS Alpha Version 7.2-1.

System Service	Documentation Update
$CREATE_USER_PROFILE	The error messages have been updated for this service.
$CREMBX	The maximum value you can specify for the maxmsg argument is 65535.
$GETDVI	The item code, DVI$_PREFERRED_CPU, has been added to this service.
$GETSYI	Six new item codes have been added to this service. They are: SYI$_CPUCONF, SYI$_IO_PREFER_CPUS, SYI$_CPU_FAILOVER, SYI$_POTENTIAL_CPU_MASK, SYI$_POTENTIALCPU_CNT, and SYI$_AUTOSTART.
$MOUNT	The documentation has been modified to state that you must have read or control access to mount a volume on a device.
$PERSONA_RESERVE	As of this release, this service requires the IMPERSONATE privilege.

The OpenVMS Registry server manages the OpenVMS Registry database. Before you can use the OpenVMS Registry, you must configure the OpenVMS Registry server. For information about configuring the OpenVMS Registry server, see Section 4.1.

For the latest information about the OpenVMS Registry, see the OpenVMS Connectivity Developer Guide. This document is available as part of the COM for OpenVMS kit and from the OpenVMS website (http://www.compaq.com/openvms/) in the OpenVMS documentation area. (Click the Documentation link on the main OpenVMS page.)

The OpenVMS Registry server is installed as part of the OpenVMS Version 7.2-1 system installation.

Before you can use the OpenVMS Registry, you must configure the OpenVMS Registry server and populate the OpenVMS Registry database. For more information about configuring the OpenVMS Registry server, see Section 4.1. For more information about populating the OpenVMS Registry database, see the Running DCOM$SETUP section in the COM for OpenVMS Utilities for Application Development and Deployment chapter of the OpenVMS Connectivity Developer Guide.

The first time you start the OpenVMS Registry server using the startup process described in Section 4.2, the OpenVMS system creates the OpenVMS Registry database.

You can access the OpenVMS Registry in several ways. Depending on how you want to access the OpenVMS Registry, you must install the following products:

• If you want to access the OpenVMS Registry using the COM APIs, you must install COM for OpenVMS. For more information, see the OpenVMS Connectivity Developer Guide.
• If you want to access the OpenVMS Registry using the Windows NT application RegEdt32, you must first install, configure, and start Advanced Server for OpenVMS. For more information, see the Advanced Server for OpenVMS documentation available on the documentation CD-ROM.

You can also access the OpenVMS Registry using the OpenVMS Registry server management utility or the OpenVMS Registry system services, which are installed as part of the OpenVMS Registry in OpenVMS Version 7.2-1.

4.1 Configuring the OpenVMS Registry: the REG$CONFIG Configuration Utility

The OpenVMS Registry Configuration utility (REG$CONFIG) provides information about the OpenVMS Registry server status and the OpenVMS Registry database location, and allows you to change OpenVMS Registry logical names and paths.

Enter the following command to start the OpenVMS Registry Configuration utility:

$ @SYS$MANAGER:REG$CONFIG

The system displays the following menu:

--------------------------------------------------------- OpenVMS Registry Configuration Utility ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1 - Configure OpenVMS Registry logical names and directory paths 2 - Display OpenVMS Registry logical names and directory paths 3 - Check the state of the OpenVMS Registry server 4 - Start the OpenVMS Registry server on this node H - Help about this utility [E] - Exit Please enter your choice : ---------------------------------------------------------

To select an option, enter the option number. The options are as follows:

• 1 - Configure OpenVMS Registry logical names and directory paths
  Allows you to configure the OpenVMS Registry server startup value and specify the location of the OpenVMS Registry database.
  For this procedure, see Section 4.1.1.
• 2 - Display OpenVMS Registry logical names and directory paths
  Displays the current values of the OpenVMS Registry server logical (startup value) for this node and the OpenVMS Registry database location.
• 3 - Check the state of the OpenVMS Registry server
  Displays the current state of the OpenVMS Registry server. The system displays one of the following:

  The OpenVMS Registry server is started in the cluster. The OpenVMS Registry server is started on this node. The OpenVMS Registry server is not started.

• 4 - Start the OpenVMS Registry server on this node
  Starts the OpenVMS Registry server on the current node. The system displays the following message:

  The OpenVMS Registry server has successfully started.

• H - Help about this utility
  Display online help for OpenVMS Registry Configuration utility options.
• [E] - Exit
  Exit the OpenVMS Registry Configuration utility.

The system displays the following questions:

1. The system prompts you to enter standalone or cluster information. The system displays the following message:

   Is this system now a node in a cluster or will this system become part of a cluster? (Y/N/Q):

2. The system displays the current information about the REG$TO_BE_STARTED logical, then prompts you to change the value.

   - REG$TO_BE_STARTED - [current value of REG$TO_BE_STARTED] NOTE: Setting this logical to TRUE starts the OpenVMS Registry server automatically when the system boots. Setting this logical to FALSE prevents the OpenVMS Registry server from starting when the system boots and prevents other products from starting the OpenVMS Registry server. If the OpenVMS Registry Server is not started at boot time, but other products that require an OpenVMS Registry server are able to start the OpenVMS Registry server, you do not need to assign a value to this logical. Do you want to change this value? (Y/N/Q) [Y]:

   
   If you choose Y, the system prompts you for the new value.

   Enter the new value (TRUE/FALSE/NOVAL/Q):

   
   Enter one of these values based on the action you want taken:

   Action	Value
   Start the OpenVMS Registry server on reboot. Allow other products to start the server.	TRUE
   Do not start the OpenVMS Registry server on reboot. Do not allow other products to start the server.	FALSE
   Do not start the OpenVMS Registry server on reboot. Allow other products to start the server. (Deassigns the logical name.)	NOVAL
   Quit this procedure and return to the OpenVMS Registry Configuration utility menu.	Q

   In which logical name table do you want the logical defined? (SYSTEM/SYSCLUSTER/CLUSTER/Q) :

   
   Enter one of these values based on the action you want taken:

   Action	Value
   Add the REG$TO_BE_STARTED logical to the LNM$SYSTEM logical name table. This table contains names that are shared by all processes in the system.	SYSTEM
   Add the REG$TO_BE_STARTED logical to the LNM$SYSCLUSTER logical name table. This table contains names that are shared by all processes in an OpenVMS Cluster.	SYSCLUSTER
   Add the REG$TO_BE_STARTED logical to the LNM$CLUSTER logical name table. This table is the parent table for all clusterwide logical name tables.	CLUSTER
   Quit this procedure and return to the OpenVMS Registry Configuration utility menu.	Q

   
   After you enter the new or updated value, the system confirms the change and displays the line you must add to your SYLOGICALS.COM file.

   The logical REG$TO_BE_STARTED has been temporarily defined. Before you reboot the system, you must edit your SYLOGICALS.COM to include the line: DEFINE/TABLE=table-name REG$TO_BE_STARTED value Press [Enter] to continue.

3. The system displays the current information about the SYS$REGISTRY logical, then prompts you to change the value.

   - SYS$REGISTRY logical - current value of SYS$REGISTRY Note: When the OpenVMS Registry server is started, the system creates an OpenVMS Registry database at this location. If an OpenVMS Registry database already exists on your system, you must redefine the SYS$REGISTRY logical to point to the existing OpenVMS Registry database location. Do you wish to change this value? (Y/N/Q) [Y]:

   
   If you choose Y, the system prompts you for the new value.

   Enter the new value for SYS$REGISTRY ("yourvalue"/NOVAL/Q):

   
   Enter one of these values based on the action you want taken:

   Action	Value
   Define a new or changed location for the OpenVMS Registry database.	A valid directory specification, such as DKA0:[SYS$REGISTRY].
   Deassign the logical name.	NOVAL
   Quit this procedure and return to the OpenVMS Registry Configuration utility menu.	Q

4. The system displays your updated value and prompts you to confirm the value.

   You have entered: value Is this correct? (Y/N/Q) [Y]:

5. The system prompts you to enter a logical table name in which to store the new or updated logical.

   In which logical name table do you want the logical defined? (SYSTEM/SYSCLUSTER/CLUSTER/Q):

   
   Enter one of these values based on the action you want taken:

   Action	Value
   Add the SYS$REGISTRY logical to the LNM$SYSTEM logical name table. This table contains names that are shared by all processes in the system.	SYSTEM
   Add the SYS$REGISTRY logical to the LNM$SYSCLUSTER logical name table. This table contains names that are shared by all processes in an OpenVMS Cluster.	SYSCLUSTER
   Add the SYS$REGISTRY logical to the LNM$CLUSTER logical name table. This table is the parent table for all clusterwide logical name tables.	CLUSTER
   Quit this procedure and return to the OpenVMS Registry Configuration utility menu.	Q

   
   After you enter the new or updated value, the system confirms the change and displays the line you must add to your SYLOGICALS.COM file.

   The logical SYS$REGISTRY has been temporarily defined. Before you reboot the system, you must edit your SYLOGICALS.COM file to include the line: DEFINE/TABLE=table-name SYS$REGISTRY dir-spec Press [Enter] to continue.

6. The system displays information about the location of the OpenVMS Registry database.

   - SYS$REGISTRY directory - [directory status]

   
   If the directory does not exist, the system prompts you to create the directory.

   ---

   Previous

   Next

   Contents

   Index

   	privacy and legal statement
   6614PRO_002.HTML