[Digital logo]
[HR]

OpenVMS Version 7.1 Release Notes

Previous | Contents

If you upgrade your OpenVMS Alpha Version 7.0 system to OpenVMS Alpha Version 7.1 when Spiralog is installed, and later remove Spiralog or install any version of Spiralog, this action will cause a failure in the Backup utility, the batch and print queuing system, and DECdtm services.

If you accidentally upgrade your OpenVMS Alpha system to Version 7.1 while Spiralog is installed, you must deinstall Spiralog, reinstall OpenVMS Alpha Version 7.1 using the PRESERVE option, install Spiralog Version 1.2, and reboot your system in order to recover.

Considerations When Choosing a File System

With OpenVMS Alpha you can choose to use the standard Files--11 file system or the new Spiralog file system for each disk in your configuration. By default, the Files--11 file system is used for all disks.

Before deciding to use Spiralog for any of your disks, carefully consider the following tradeoffs:

If you decide to use Spiralog, your system environment must meet the prerequisites outlined in the Spiralog Version 1.n Software Product Description (SPD).

1.5 AlphaServer 4100 (Alpha Only)

This section contains release notes pertaining to the AlphaServer 4100.

1.5.1 Problems and Restrictions

The following note describes how to resolve an error that occurs on the AlphaServer 4100.

1.5.1.1 Field Replaceable Units (FRU) Table Error

V7.1

After you boot the OpenVMS Alpha operating system on an AlphaServer 4100, the following message might display on the screen: 

*****Config packet buffer allocation failure: Continuing without writing Errorlog

This message indicates that the size of the FRU table exceeds the size of the buffer allocated by the default value of the SYSGEN parameter ERLBUFFERPAGES. It is a warning message only and indicates that the FRU table was not written in the error log on this reboot.

If your system displays this message, Digital recommends that you change the value of the ERLBUFFERPAGES parameter from 4 (the default) to 6. The following example shows how to use the SYSGEN utility to accomplish this task: 

$ MCR SYSGEN 
SYSGEN> USE CURRENT 
SYSGEN> SET ERLBUFFERPAGES 6 
SYSGEN> WRITE CURRENT 
SYSGEN> EXIT

If this warning appears again after you reboot the system, increase the value of the ERLBUFFERPAGES parameter in increments of 2 (not exceeding the maximum of 32) until the warning message no longer displays. The value of ERLBUFFERPAGES that resolves the problem varies depending on the configuration of the system.

1.6 DEC 7000 (Alpha Only)

This section contains release notes pertaining to DEC 7000 systems.

1.6.1 Changes and Enhancements

The following note describes a change in the behavior of DEC 7000 systems.

1.6.1.1 Ctrl/P Behavior Change During Boot

V7.1

Starting with OpenVMS Alpha Version 7.1, the remote halt command, issued by typing Ctrl/P at the system console, does not work during boot until the following copyright banner appears. 

$!  Copyright (c) 1996 Digital Equipment Corporation.  All rights reserved.

In previous versions of OpenVMS, typing Ctrl/P at the system console always returned the system to the console prompt at any time during the boot.

1.7 Qvision Graphics Board (Alpha Only)

See Section 2.10.1.1 for a behavior change that affects users with the Qvision graphics board on their workstation or server.

1.8 RF73 and Other RFnn DSSI Disk Devices

Release notes in this section pertain to the RF31T, RF31T+, RF35, RF35+, RF73, and RF74 DSSI disk devices.

1.8.1 Problems and Restrictions

This section describes a problem found in certain RF31T, RF31T+, RF35, RF35+, RF73, and RF74 DSSI disk devices.

1.8.1.1 RF73 and Other RFnn DSSI Disk Devices and Controller Memory Errors

V6.2

A problem exists with the microcode for earlier versions of RF31T, RF31T+, RF35, RF35+, RF73, and RF74 DSSI disk devices that can cause data loss. The problem can occur when reading data from one of these devices if the device has had a controller memory error (also known as an error detection and correction (EDC) error). The error could have been induced by a virtual circuit closure or faulty hardware.

Digital advises customers with any of these devices to check their microcode revision levels. If the microcode revision levels are lower than the numbers shown in Table 1-1, Digital recommends that you update the microcode. The microcode for all models, except the RF31T, RF31T+, and RF35+, is provided on the latest OpenVMS binary distribution CD--ROM.

The RF_VERS utility, a utility program that displays the microcode revision level of the DSSI disk devices, is also provided on the CD--ROM. Instructions for using the utility program and for updating the microcode are provided in this section.

Note

If you have an RF31T, RF31T+, or RF35+ disk drive with a version of microcode that is not supported (see Table 1-1), and if you have a support contract, contact your Digital support representative. Otherwise, contact your authorized reseller.

The earliest supportable revision levels of the DSSI disk microcode are shown in Table 1-1.

Table 1-1 Supported Microcode Revision Levels
Device Type Minimum Level with Supported Microcode
RF31T T387E
RF31T+ T387E
RF35 T392D
RF35+ T392D
RF36 V427P
RF73 T392D
RF74 V427P

To display the microcode version level of your DSSI disk devices, perform the following steps:

  1. Log in to the SYSTEM account or another account that has the CMKRNL, DIAGNOSE, and SYSPRV privileges.
  2. Issue the following commands: 
     $ SET PROCESS /PRIVILEGE=(DIAGNOSE,CMKRNL,SYSPRV) 
 $ SHOW DEVICE FYA0:

    On VAX systems, if the SHOW DEVICE command produces an error, issue the following commands: 
     $ RUN SYS$SYSTEM:SYSGEN 
         SYSGEN>  CONN FYA0/NOADAP 
         SYSGEN>  ^Z

    On Alpha systems, if the SHOW DEVICE command produces an error, issue the following commands: 
     $ RUN SYS$SYSTEM:SYSMAN 
         SYSMAN> IO CONNECT FYA0: /NOADAP 
         SYSGEN>  ^Z
  3. On VAX and Alpha systems, issue the following command: 
     $ RUN SYS$ETC:RF_VERS.EXE

The following is an example of the display produced by the RF_VERS utility: 

 Program Name:   RF_VERS 
 Revision Level: V1.2s 
 
 NOTICE: This program does not currently support the RF72 or any 
         HSDxx controllers. See next version for support. 
 
 DSSI disks currently on this system as seen by RF_VERS 
 
 Device         Node        Status       Hardware    Firmware  
 Name           Name                     Type        Version   
 
 _$22$DIA7:     R4JL2I      mounted      RF73        T387A     
 _$22$DIA6:     R4I0BG      mounted      RF73        T387A     
 _$22$DIA8:     R4XLWE      mounted      RF73        T387A     
 _$22$DIA2:     R4FCZK      mounted      RF73        T387A     
 _$22$DIA3:     R4CKCG      mounted      RF73        T387A     
 _$22$DIA4:     R4ZKUE      mounted      RF73        T387A     
 _$22$DIA9:     R4GYYI      mounted      RF73        T387A     
 _$22$DIA1:     R4XRYI      mounted      RF73        T387A

To update the microcode in your device, use the appropriate command for your device and platform from Table 1-2.

Caution

Back up the disk before updating the microcode.

Table 1-2 Commands for Updating Microcode in Certain DSSI Disk Devices
Device Type Platform Command
RF35 Alpha $RUN SYS$ETC:RF35_T392F_DEC_ALPHA.EXE
RF35 VAX $RUN SYS$ETC:RF35_T392F_DEC.EXE
RF36 Alpha $RUN SYS$ETC:RF36_V427P_DEC_ALPHA.EXE
RF36 VAX $RUN SYS$ETC:RF36_V427P_DEC.EXE
RF73 Alpha $RUN SYS$ETC:RF73_T392F_DEC_ALPHA.EXE
RF73 VAX $RUN SYS$ETC:RF73_T392F_DEC.EXE
RF74 Alpha $RUN SYS$ETC:RF74_V427P_DEC_ALPHA.EXE
RF74 VAX $RUN SYS$ETC:RF74_V427P_DEC.EXE

Caution

Do not delete SCSI_INFO.EXE, RF_VERS.EXE, or any of the files listed in Table 1-2. If these files are deleted, VMSKITBLD.COM (on VAX) will not be able to find them. Similarly, on Alpha systems, the PRODUCT INSTALL commands in AXPVMS$PCSI_INSTALL and AXPVMS$PCSI_INSTALL_MIN will fail.

Chapter 2
OpenVMS Layered Products Release Notes

This chapter contains installation and support information about OpenVMS layered products. Notes about using compilers, linkers, and run-time library routines are included in Chapter 5.

2.1 Layered Product Support

Information about layered product support is available in the Software Public Rollout Reports for OpenVMS, available on the World Wide Web. The Software Public Rollout Reports for OpenVMS list the availability of Digital's software products shipping on the Software Products Library kits (CD--ROM consolidations) for OpenVMS Alpha and OpenVMS VAX.

For OpenVMS Version 7.1, three new reports show currently shipping and previously released Digital layered software products for the following operating system versions:

The reports contain the product name and version, the operating system version required to support the product, and the volume ship date for the product. The information in these tables is continually evolving and is subject to change. The reports are intended for public distribution and are updated monthly. The information is not provided in these release notes because of the changing nature of the information.

These reports are available from the OpenVMS home page on the World Wide Web in the OpenVMS Products section. Use the following URL to access the OpenVMS Software Public Rollout Reports for OpenVMS: 

http://www.openvms.digital.com/openvms/os/swroll.html

If you do not have Internet access, you can find the operating system support information on any of the quarterly Software Products Libraries, in the following directory: 

     [README]SW_COMPAT_MATRIX.PS (.TXT)

The Software Public Rollout Reports are also available from your Digital support representative.

2.2 DEC BASIC

This section contains release notes pertaining to DEC BASIC.

2.2.1 Problems and Restrictions

The following note describes a build restriction for DEC BASIC.

2.2.1.1 BASIC$STARLET.TLB Build Restriction (Alpha Only)

V7.0

The introduction of 64-bit support for system services prevents the proper construction and use of BASIC$STARLET.TLB on OpenVMS Alpha systems.

If you do not need any of the system definitions from STARLET, take the default for the following question when installing DEC BASIC: 

Do you want to install the OpenVMS AXP system definitions (10 min.) [NO]?

If you do need system definitions from STARLET, there are two possible workarounds: