VMS Version 5.4-2 Release Notes February 1991 This document describes software problems, corrections, restrictions, and documentation changes that pertain to Version 5.4-2 of the VMS operating system. Revision/Update Information: This is a new document. Software Version: VMS Version 5.4-2 digital equipment corporation maynard, massachusetts ________________________ February 1991 __________ The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. __________ © Digital Equipment Corporation 1991. All Rights Reserved. Printed in U.S.A. __________ The postpaid Reader's Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: CDA DEQNA MicroVAX VAX RMS DDIF Desktop-VMS PrintServer VAXserver 40 DEC DIGITAL Q-bus VAXstation DECdtm GIGI ReGIS VMS DECnet HSC ULTRIX VT DECUS LiveLink UNIBUS XUI DECwindows LN03 VAX DECwriter MASSBUS VAXcluster DIGITAL The following are third-party trademarks: Display PostScript is a trademark of Adobe Systems Incorporated. PostScript is a registered trademark of Adobe Systems Incorporated. ZK5700 __________________________________________________________________ Production Note This book was produced with the VAX DOCUMENT electronic publishing system, a software tool developed and sold by Digital. In this system, writers use an ASCII text editor to create source files containing text and English-like code; this code labels the structural elements of the document, such as chapters, paragraphs, and tables. The VAX DOCUMENT software, which runs on the VMS operating system, interprets the code to format the text, generate a table of contents and index, and paginate the entire document. Writers can print the document on the terminal or line printer, or they can use Digital- supported devices, such as the LN03 laser printer and PostScript printers (PrintServer 40 or LN03R ScriptPrinter), to produce a typeset-quality copy containing integrated graphics. _______________________________________________________ Contents _________________________________________________ PREFACE v _______________________________________________________ CHAPTER 1 GENERAL USER RELEASE NOTES 1-1 _________________________________________________ 1.1 CHARACTERS CHANGED FROM NONPRINTABLE TO PRINTABLE 1-1 _________________________________________________ 1.2 F$CONTEXT LEXICAL FUNCTION PROBLEM 1-2 _________________________________________________ 1.3 DUMP COMMAND ON KZQSA TAPE DRIVES 1-2 _________________________________________________ 1.4 IMAGE DATA VERIFICATION IN BATCH MODE-PROBLEM CORRECTED 1-2 _________________________________________________ 1.5 REMOTE IMAGE ACTIVATION OF FILES-PROBLEM CORRECTED 1-3 _________________________________________________ 1.6 VMS MAIL UTILITY RELEASE NOTES 1-3 1.6.1 Use Quotes in Address When Forwarding Mail to ULTRIX Users 1-3 1.6.2 Multiple Copies of a Message Delivered to the Same Recipient-Problem Corrected 1-4 v Contents _________________________________________________ 1.7 VAXSTATION 3100, MODEL 76 COMPUTER RELEASE NOTES 1-5 _________________________________________________ 1.8 WORKSTATIONS WITH DUAL-HEAD SUPPORT-RESTRICTIONS 1-5 _________________________________________________ 1.9 WRITE/SYMBOL COMMAND WITH NULL RECORDS-PROBLEM CORRECTED 1-6 _______________________________________________________ CHAPTER 2 SYSTEM MANAGER RELEASE NOTES 2-1 _________________________________________________ 2.1 ANALIMDMP-PROBLEM CORRECTED 2-1 _________________________________________________ 2.2 VAX 3100 MODEL 76 NOTES 2-2 2.2.1 System Crash 2-2 2.2.2 AUTOGEN LOCKDIRWT Parameter 2-2 2.2.3 Page and Swap File Sizes 2-2 _________________________________________________ 2.3 VAX 4000 MODEL 200 ETHERNET CHIP WORKAROUND 2-3 _________________________________________________ 2.4 AUTOMATIC ATTEMPT TO LOAD CONTINUATION VOLUME OF MAGNETIC TAPE 2-3 _________________________________________________ 2.5 SYSGEN CONFIGURATION PROBLEM 2-3 vi Contents _________________________________________________ 2.6 VAX 6000 MODEL 500 SERIES CONFIGURATION NOTE 2-4 _________________________________________________ 2.7 DECNET-VAX RELEASE NOTES 2-4 2.7.1 Circuit Selection on End Nodes with Multiple Equal-Cost Circuits-Problem Corrected 2-4 2.7.2 Incorrectly Negotiated Buffer Sizes-Problem Corrected 2-5 2.7.3 LAN Designated Router-Problem Corrected 2-5 2.7.4 Maintenance Operation Module (MOM)-Problem Corrected 2-6 2.7.5 Maximum Value of Executor MAXIMUM BROADCAST NONROUTERS Parameter Changed 2-6 2.7.6 NDDRIVER-Correction 2-6 2.7.7 Retransmission of Data after I/O Failure 2-7 2.7.8 SYS$CLUSTER_NODE Logical Name-Correction 2-7 2.7.9 TASK Object Characteristics Ignored-Problem Corrected 2-7 2.7.10 UNA Circuit Default Cost Changed 2-8 _________________________________________________ 2.8 DNS RELEASE NOTES 2-8 2.8.1 DNS RTL Routines DNS$PARSE_USERNAME_STRING and DNS$CVT_TO_USERNAME_STRING-Corrections 2-8 vii Contents _________________________________________________ 2.9 FAL MAXIMUM MESSAGE BUFFER SIZE EXTENDED 2-9 _________________________________________________ 2.10 HIERARCHICAL STORAGE CONTROLLER (HSC) REVISION LEVELS REQUIRED 2-9 _________________________________________________ 2.11 LADCP RELEASE NOTES 2-9 2.11.1 InfoServer Can Now Write to Services 2-10 2.11.2 New LADCP Command 2-10 _________________________________________________ 2.12 TERMINAL FALLBACK UTILITY RELEASE NOTES 2-10 2.12.1 TFU Problem in Error Message Display-Problem Corrected 2-11 2.12.2 TFU Now Supports P.S.I. Terminals 2-11 _________________________________________________ 2.13 TLZ04 TAPE DRIVER-PROBLEM CORRECTED 2-12 _________________________________________________ 2.14 VOLUME SHADOWING PHASE II RELEASE NOTES 2-12 2.14.1 Overview 2-12 2.14.2 AUTOGEN Operations-Volume Shadowing Adjustment Required 2-13 2.14.3 Batch and Print Jobs-Reentering after Conversion 2-14 2.14.4 Changing Physical Device Names 2-15 2.14.5 SHADBOOTFAIL Bugcheck Message 2-15 viii Contents 2.14.6 SHOW DEVICES Command 2-16 2.14.7 SHOW DEVICES Command-Addition to Display for Full Copy or Merge Operation 2-16 2.14.8 Specify a Virtual Unit Name to Obtain $GETDVI FREEBLOCK Information 2-18 2.14.9 SYSGEN Parameter VMSD3-Special Parameter to Control Failover 2-18 2.14.10 SYSGEN Parameter VIRTUALPAGECOUNT Adjustment 2-19 2.14.11 UAF Parameter Changes 2-20 _________________________________________________ 2.15 STANDALONE BACKUP CAUTION 2-21 _______________________________________________________ CHAPTER 3 PROGRAMMER RELEASE NOTES 3-1 _________________________________________________ 3.1 BASIC INKEY$ FUNCTION-CHANGE 3-1 _________________________________________________ 3.2 I/O PREFERRED PATH INTERFACE FOR DSA DEVICES-PROBLEM CORRECTED 3-1 _________________________________________________ 3.3 VMS RMS CONVERT/RECLAIM UTILITY-PROBLEM 3-2 ix Contents _______________________________________________________ CHAPTER 4 DOCUMENTATION RELEASE NOTES 4-1 _________________________________________________ 4.1 ADDITION TO DISPLAY POSTSCRIPT DOCUMENTATION 4-1 _________________________________________________ 4.2 VMS SYSTEM GENERATION UTILITY MANUAL 4-1 _________________________________________________ 4.3 VMS VERSION 5.4 UPGRADE AND INSTALLATION MANUAL 4-2 _______________________________________________________ INDEX _______________________________________________________ EXAMPLES 2-1 LADCP SHOW SERVICES Sample Display 2-11 2-2 SHOW DEVICES Display for Shadow Sets 2-17 2-3 SHOW DEVICES Display for Shadow Sets 2-18 _______________________________________________________ TABLES 2-1 Recommended UAF Parameters for the System Account 2-20 x _______________________________________________________ Preface Version 5.4-2 is an update to Version 5.4 of the VMS operating system. Version 5.4-2 includes the functions and corrections of VMS Versions 5.4-0A, 5.4-1, and 5.4-1A. These functions include VMS Volume Shadowing Phase II and optionally installable Local Area Transport (LAT) software. To apply the Version 5.4-2 update, you must be running at least VMS Version 5.4 on your system. This document describes software problems, corrections, restrictions, and documentation changes that pertain to VMS Version 5.4-2 (and Versions 5.4- 0A, 5.4-1, 5.4-1A, and 5.4-2). __________________________________________________________________ Intended Audience VMS Version 5.4-2 Release Notes is intended for all system users. Read the release notes before applying the Version 5.4-2 update. __________________________________________________________________ Document Structure This manual contains the following chapters: o Chapter 1 contains release notes intended for general users of the VMS operating system. o Chapter 2 contains release notes intended for system managers. o Chapter 3 contains release notes intended for application and system programmers. o Chapter 4 contains additions and corrections to the VMS Documentation Set. v Preface __________________________________________________________________ Conventions The following conventions are used in this manual: Ctrl/x A sequence such as Ctrl/x indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button. PF1 x A sequence such as PF1 x indicates that you must first press and release the key labeled PF1, then press and release another key or a pointing device button. A key name is shown enclosed to indicate that you press a key on the keyboard. . . . In examples, a horizontal ellipsis indicates one of the following possibilities: o Additional optional arguments in a statement have been omitted. o The preceding item or items can be repeated one or more times. o Additional parameters, values, or other information can be entered. vi Preface A vertical ellipsis indicates . the omission of items from a . code example or command format; . the items are omitted because they are not important to the topic being discussed. () In format descriptions, parentheses indicate that, if you choose more than one option, you must enclose the choices in parentheses. [] In format descriptions, brackets indicate that whatever is enclosed is optional; you can select none, one, or all of the choices. {} In format descriptions, braces surround a required choice of options; you must choose one of the options listed. boldface text Boldface text represents the introduction of a new term or the name of an argument, an attribute, or a reason. italic text Italic text represents information that can vary in system messages (for example, Internal error number). UPPERCASE TEXT Uppercase letters indicate that you must enter a command (for example, enter OPEN/READ). vii Preface Uppercase letters indicate the name of a routine, the name of a file, the name of a file protection code, or the abbreviation for a system privilege. - Hyphens in coding examples indicate that additional arguments to the request are provided on the line that follows. numbers Unless otherwise noted, all numbers in the text are assumed to be decimal. Nondecimal radixes-binary, octal, or hexadecimal-are explicitly indicated. viii _______________________________________________________ 1 General User Release Notes This chapter includes information about the VMS Version 5.4-2 operating system for the general user. __________________________________________________________________ 1.1 Characters Changed from Nonprintable to Printable The VMS print symbiont uses a nonprintable character table to decide the number of characters in the line. To support the internationalized printer environment, VMS Versions 5.4-1 and 5.4-2 change the following codes from nonprintable to printable: o A4 (decimal 164) o A6 (decimal 166) o AC (decimal 172) o AD (decimal 173) o AE (decimal 174) o AF (decimal 175) o B4 (decimal 180) o B8 (decimal 184) o BE (decimal 190) o D0 (decimal 208) o DE (decimal 222) o F0 (decimal 240) o FE (decimal 254) 1-1 General User Release Notes 1.1 Characters Changed from Nonprintable to Printable These codes are part of the DEC supplemental graphic set in the DEC Multinational Character Set (MCS) and were reserved for future standardization. For a description of MCS and a listing of its contents, see the Guide to Using VMS, Appendix A. __________________________________________________________________ 1.2 F$CONTEXT Lexical Function Problem The DCL lexical function F$CONTEXT can cause the deletion of a process unless you use the function in one of the following ways: o Specify CANCEL as the third parameter of F$CONTEXT. o Specify all parameters of F$CONTEXT. This problem will be addressed in a future release. __________________________________________________________________ 1.3 DUMP Command on KZQSA Tape Drives Simultaneous DUMP operations on two or more tape drives connected to a KZQSA controller is unsupported and can cause system hangs. __________________________________________________________________ 1.4 Image Data Verification in Batch Mode-Problem Corrected Prior to VMS Version 5.4-1, a login command procedure containing the DCL command SET NOVERIFY (specifying that image data records were not to be echoed, or verified) did not work properly when the job was running in batch mode. VMS did not propagate the setting to the command procedure submitted, causing the image data records to be echoed rather than suppressing the output as directed. VMS Versions 5.4-1 and 5.4-2 correct this problem. 1-2 General User Release Notes 1.5 Remote Image Activation of Files-Problem Corrected __________________________________________________________________ 1.5 Remote Image Activation of Files-Problem Corrected Prior to VMS Version 5.4-1, you could not activate a remote image if that image's specification was part of a search list that also included a specification for a local image. The following example illustrates this problem: $DEFINE FOO A.EXE, BAR::B.EXE $RUN FOO In this example, the definition of FOO includes the local image A.EXE and the remote image BAR::B.EXE. Prior to VMS Version 5.4-1, if A.EXE did not exist, the RUN command failed to execute BAR::B.EXE. VMS Versions 5.4-1 and 5.4-2 correct this problem. __________________________________________________________________ 1.6 VMS Mail Utility Release Notes The release notes in this section pertain to the VMS Mail Utility. ___________________________ 1.6.1 Use Quotes in Address When Forwarding Mail to ULTRIX Users The VMS Mail Utility requires addresses, including forwarding addresses, to be stored in uppercase letters. However, non-VMS mail systems, such as ULTRIX, may require addresses to contain lowercase characters. Prior to VMS Version 5.0, the VMS Mail Utility allowed addresses containing lowercase characters to be stored in a user profile and correctly passed them to the non-VMS mail systems. From VMS Version 5.0 through Version 5.4, the VMS Mail Utility converted all addresses to uppercase before storing them in a user profile. Beginning with VMS Version 5.4-1, the VMS Mail Utility again stores addresses containing lowercase addresses in a user 1-3 General User Release Notes 1.6 VMS Mail Utility Release Notes profile, provided you use one of the following methods to set a forwarding address: o If the initial part of the address, such as the node name, is in uppercase and the rest of the address is in lowercase, preserve the lowercase part of the address by enclosing it in three sets of double quotation marks, as in the following example: MAIL>SET FORWARD NODE::"""name""" o To preserve the entire address in lowercase, enclose the entire address in five sets of double quotation marks, as in the following example: MAIL>SET FORWARD """""node::name""""" Note that you cannot use the lowercase format for forwarding mail to VMS users. ___________________________ 1.6.2 Multiple Copies of a Message Delivered to the Same Recipient-Problem Corrected Prior to VMS Version 5.4-1, the VMS Mail Utility delivered multiple copies of a message to the same recipient when two conditions were present: 1 The sender used a distribution list with ULTRIX mail or some other mail agent that retries on errors. 2 A recipient could not receive mail for some unusual reason, for example, if the recipient had mail forwarded and exceeded disk quota. The VMS Mail Utility reported nondelivery to the recipient and to some other recipient for whom the delivery was successful. On retrying the delivery, the sending mail agent incorrectly delivered the message to someone who had already received it. 1-4 General User Release Notes 1.6 VMS Mail Utility Release Notes In VMS Versions 5.4-1 and 5.4-2, the Mail Utility correctly reports nondelivery to the sender. __________________________________________________________________ 1.7 VAXstation 3100, Model 76 Computer Release Notes The following release notes apply to the VAXstation 3100, Model 76 system: o Mouse performance-The mouse included with the VAXstation 3100, Model 76 system uses two "feet" (one for moving horizontally and one for moving vertically) instead of a ball. For optimal performance with this type of mouse, choose the Pointer... option from the Session Manager Customize menu. Then, set the mouse speed (Pointer Acceleration) in the Customize Pointer dialog box to Fast instead of Medium (which is the default setting required for a mouse with the ball design). Mouse performance, including improved diagonal movement, will be addressed in a future version of DECwindows software. Mouse performance on systems running VMS Workstation Software (VWS) is unaffected. o Upgrading with SPX graphics-Previously, when you upgraded your system to a VAXstation 3100 Model 76 with an SPX graphics option, the system sometimes failed to boot. This problem has been corrected. __________________________________________________________________ 1.8 Workstations with Dual-Head Support-Restrictions The following restrictions apply to workstations with dual-head support, such as VAXstation 3100 series systems. These workstations support two monitors. 1-5 General User Release Notes 1.8 Workstations with Dual-Head Support-Restrictions Setting the DPI If you use monitors with different dots-per-inch (dpi) settings, you may experience what appears to be window corruption but which is actually an overlapping of characters on the screen. For example, if you run an application on a workstation that has monitor 0 set to one dpi setting and monitor 1 set to a different dpi setting, the application will use fonts based on the dpi setting of monitor 0. When the application runs on monitor 1, you might perceive window corruption (overlapping characters). To avoid this problem, Digital recommends that you set your monitors to the same dpi setting using the DECW$PRIVATE_SERVER_SETUP.COM file. However, if you must maintain two monitors with different dpi settings, then you should run dpi/font-sensitive applications on monitor 0 only. Customizing Colors When customizing colors on a dual-head system that is configured with both a color monitor and a monochrome monitor, make sure you specify colors with sufficient contrast. If the color settings do not contrast enough, then applications customized for a color display might produce black-on-black or white-on-white output when run on the monochrome monitor. __________________________________________________________________ 1.9 WRITE/SYMBOL Command with Null Records-Problem Corrected In previous versions of VMS, if you used the DCL command WRITE/SYMBOL with a defined symbol that had a null value, VMS incorrectly issued an error message saying the symbol was undefined. VMS Version 5.4-1 and 5.4-2 correct this problem. 1-6 _______________________________________________________ 2 System Manager Release Notes This chapter includes information about the VMS Version 5.4-2 operating system for the system manager. __________________________________________________________________ 2.1 ANALIMDMP-Problem Corrected VMS Versions 5.4-1 and 5.4-2 correct a problem in the ANALIMDMP.EXE image that allowed authorized, nonprivileged users to obtain all privileges under very obscure circumstances. The ANALIMDMP.EXE image contained on the Version 5.4-1 and 5.4-2 kits also can be used on Version 5.4 systems. Following a Version 5.4-1 or 5.4-2 update, Digital recommends that you copy the image (SYS$SYSTEM:ANALIMDMP.EXE) to the common system directory (SYS$COMMON:[SYSEXE]) on any Version 5.4 systems or clusters that you manage. After you have copied this image to the common system directory, you should reinstall the image using the following commands on each node of a VAXcluster system: $SET PROC/PRIV=ALL $INSTALL REPLACE ANALIMDMP/OPEN/HEAD/SHARE/PRIV=(CMKRNL,CMEXEC) If you previously took the precaution of inserting any INSTALL commands (such as $ RUN SYS$SYSTEM:INSTALL ANALIMDMP/DELETE) in your system startup file (SYS$MANAGER:SYSTARTUP_V5.COM) to prevent the ANALIMDMP.EXE image from being installed, you should remove these commands following the update or after you have copied the new image to your Version 5.4 system. 2-1 System Manager Release Notes 2.2 VAX 3100 Model 76 Notes __________________________________________________________________ 2.2 VAX 3100 Model 76 Notes This section contains notes about the VAX 3100 Model 76 system. ___________________________ 2.2.1 System Crash Some VAX 3100 Model 76 systems may exhibit a rare system crash from a soft interrupt (due to a cache parity error). The crash generates a display on the stack that includes "SYSLOA+00D2C". This problem will be corrected in a future release. If you encounter, please submit an Software Problem Report (SPR). ___________________________ 2.2.2 AUTOGEN LOCKDIRWT Parameter Previously, the default AUTOGEN parameters set LOCKDIRWT to 1, which created potential performance problems on the VAX 3100 Model 76. This problem has been corrected; LOCKDIRWT is now set to 0. ___________________________ 2.2.3 Page and Swap File Sizes On a VAX 3100 Model 76, AUTOGEN makes some incorrect parameter calculations. Digital recommends that you edit SYS$SYSTEM:MODPARAMS.DAT and add the following lines: MAXPAGEFILE = 25000 MAXPROCESSCNT = 50 Changing these parameters results in a more realistic size for the page and swap files. 2-2 System Manager Release Notes 2.3 VAX 4000 Model 200 Ethernet Chip Workaround __________________________________________________________________ 2.3 VAX 4000 Model 200 Ethernet Chip Workaround VMS Version 5.4-2 contains a new EZDRIVER.EXE image that works around a problem with the Ethernet chip on VAX 4000 Model 200 series systems. Digital will correct the chip problem in a future hardware release. __________________________________________________________________ 2.4 Automatic Attempt to Load Continuation Volume of Magnetic Tape When you use MOUNT/AUTOMATIC to mount labeled tape volume sets on multiple drives, the magnetic tape ancillary control process (MTAACP) expects continuation volumes to be loaded on the proper drives and attempts to mount them without requesting operator assistance. Prior to VMS Version 5.4-1, the MTAACP required operator intervention to switch to the next continuation volume if only one magnetic tape drive was allocated to the volume set. This requirement reduced the effectiveness of the TA90 cartridge loaders, which can automatically switch volumes on a single drive. Starting with VMS Version 5.4-1, when you use the MOUNT/AUTOMATIC command to mount tapes on a single drive, the MTAACP attempts to load the continuation volume for 100 seconds before it requires operator assistance. __________________________________________________________________ 2.5 SYSGEN Configuration Problem The Autoconfigure facility of the System Generation Utility (SYSGEN) incorrectly configures a CIBCA device in the following circumstances: o When a DEBNA, DEBNI, TBK50, or TBK70 device is in the VAXBI slot directly preceeding the CIBCA. 2-3 System Manager Release Notes 2.5 SYSGEN Configuration Problem o When a DEBNA, DEBNI, TBK50, or TBK70 device is in the last slot on one VAXBI, and the CIBCA is in the first slot on the next-highest VAXBI. Note: This error will not occur if you boot the system from the CIBCA, because the boot device is not configured by SYSGEN when you boot from the CIBCA. The configuration error results in timeout errors on the PAA0 device when you boot standalone BACKUP or the VMS operating system. To avoid timeout errors, reconfigure the bus. This problem will be fixed in a future version of the VMS operating system. __________________________________________________________________ 2.6 VAX 6000 Model 500 Series Configuration Note On a VAX 6000 Model 500 series system, Digital recommends the primary CPU occupy the lowest numbered XMI slot. VAX 6000 Model 500 series systems are usually configured this way. If you ignore this restriction, the SHUTDOWN procedure might not complete normally and you will have to halt your system using the console. __________________________________________________________________ 2.7 DECnet-VAX Release Notes This section contains system manager release notes applicable to DECnet-VAX. ___________________________ 2.7.1 Circuit Selection on End Nodes with Multiple Equal-Cost Circuits-Problem Corrected End nodes can be configured with more than one circuit but can use only one circuit for data transmission. Prior to VMS Version 5.4-1, on end nodes with multiple equal-cost circuits, the DECnet software may have chosen an incorrect circuit for data transmission. VMS Versions 5.4-1 and 5.4-2 correct this problem. 2-4 System Manager Release Notes 2.7 DECnet-VAX Release Notes ___________________________ 2.7.2 Incorrectly Negotiated Buffer Sizes-Problem Corrected Prior to VMS Version 5.4-1, DECnet-VAX incorrectly negotiated buffer sizes, allowing use of a size greater than the line buffer size. Therefore, packets were discarded when either of two conditions occurred: 1 Incoming connections proposed buffer sizes greater than 576 on Ethernet circuits. 2 Route-through packets were received from devices using direct I/O techniques, such as the DMR11. VMS Versions 5.4-1 and 5.4-2 correct this problem. ___________________________ 2.7.3 LAN Designated Router-Problem Corrected Prior to VMS Version 5.4-1, a system configured as a DECnet-VAX router participating in a VAXcluster system could incorrectly declare itself the LAN designated router when quorum was lost. If the cluster lost quorum, the DECnet-VAX router lost adjacency with all other routers. The DECnet-VAX router then declared itself the designated router until the cluster regained quorum. VMS Versions 5.4-1 and 5.4-2 correct this problem by having NETDRIVER process all Broadcast Router Hello messages. During a VAXcluster state transition, the system running as a DECnet-VAX router does not lose adjacency with other routers on the LAN and, therefore, does not declare itself the LAN designated router. 2-5 System Manager Release Notes 2.7 DECnet-VAX Release Notes ___________________________ 2.7.4 Maintenance Operation Module (MOM)-Problem Corrected Prior to VMS Version 5.4-1, a problem with the Maintenance Operation Module (MOM) caused a VMS system to respond to a dump request on a multicast circuit without first checking its node database to ensure the requesting node was defined with a dump file parameter. If the dump file parameter was not defined and this VMS system was the first system to respond to the dump request, then the first segment of the crash dump was discarded and the remote system could not complete the crash dump or reboot. VMS Versions 5.4-1 and 5.4-2 correct this problem. ___________________________ 2.7.5 Maximum Value of Executor MAXIMUM BROADCAST NONROUTERS Parameter Changed Starting with VMS Version 5.4-1, the maximum value for the Executor parameter MAXIMUM BROADCAST NONROUTERS has been changed from 65,535 to 1023. If you have a value higher than 1023 already defined in the permanent database, then the DECnet-VAX software cannot start. Use the Network Control Program (NCP) command DEFINE EXECUTOR to set the MAXIMUM BROADCAST NONROUTERS parameter to a value of 1023 or less. ___________________________ 2.7.6 NDDRIVER-Correction Prior to VMS Version 5.4-1, certain DECnet-VAX maintenance operations that involved devices using direct I/O techniques resulted in system crashes in the NDDRIVER. VMS Versions 5.4-1 and 5.4-2 correct this problem. 2-6 System Manager Release Notes 2.7 DECnet-VAX Release Notes ___________________________ 2.7.7 Retransmission of Data after I/O Failure Prior to VMS Version 5.4-1, transient Ethernet problems that caused DECnet-VAX I/O failures caused the logging of a line synchronization loss error so that the circuit went down and was then reinitialized. Although DECnet logical links were preserved, the circuit took several seconds to recover, resulting in performance problems. Starting with VMS Version 5.4-1, when a nonfatal I/O error occurs on an Ethernet circuit, the data is requeued for transmission and the state of the circuit is not affected. ___________________________ 2.7.8 SYS$CLUSTER_NODE Logical Name-Correction In previous releases of VMS, DECnet-VAX did not deassign the SYS$CLUSTER_NODE logical name when the executor was set to the OFF state. Starting with VMS Version 5.4-1, DECnet-VAX deassigns the SYS$CLUSTER_ NODE logical name whenever the executor is set to the OFF state. The SYS$CLUSTER_NODE logical name is defined when you start the DECnet-VAX software, and the ALIAS NODE characteristic is defined for the executor node. ___________________________ 2.7.9 TASK Object Characteristics Ignored-Problem Corrected In VMS Versions 5.3-2 and 5.4, DECnet-VAX ignored all characteristics of the TASK object on outgoing connections. A symptom of this problem was that the cluster alias did not work properly for outgoing connections from the TASK object, even though the ALIAS OUTGOING characteristic was set to ENABLED. VMS Versions 5.4-1 and 5.4-2 correct this problem. 2-7 System Manager Release Notes 2.7 DECnet-VAX Release Notes ___________________________ 2.7.10 UNA Circuit Default Cost Changed VMS Versions 5.4-1 and 5.4-2 change the default cost of a UNA circuit from 3 to 4. This change makes the default costs of all Ethernet circuit types equal. __________________________________________________________________ 2.8 DNS Release Notes This section contains system manager release notes applicable to the VAX Distributed Name Service (DNS). ___________________________ 2.8.1 DNS RTL Routines DNS$PARSE_USERNAME_STRING and DNS$CVT_TO_USERNAME_STRING-Corrections In previous versions of VMS, a problem in the DNS Run- Time Library (RTL) routines caused generation of an incorrect opaque full name for client applications that used the DNS RTL routines DNS$PARSE_USERNAME_ STRING and DNS$CVT_TO_USERNAME_STRING. DNS client applications can use these routines to manipulate principals as access control entries of objects in the namespace or to manipulate members of a group object. The problem caused DNS$PARSE_USERNAME_STRING, when given the DECnet Phase IV format (node::user) to give an incorrect full name. The DNS server expects a correct opaque full name, so the DNS server rejected a DNS client application that used DNS$PARSE_USERNAME_ STRING. The problem also caused DNS$CVT_TO_USERNAME_ STRING to convert the incorrect opaque full name back to the DECnet Phase IV format (node::user). For objects showing this problem, use the DNS client application with the DNS$RTL image installed with VMS Versions 5.4-1 and 5.4-2 to add the attribute value again. 2-8 System Manager Release Notes 2.9 FAL Maximum Message Buffer Size Extended __________________________________________________________________ 2.9 FAL Maximum Message Buffer Size Extended VMS Versions 5.4-1 and 5.4-2 extend the file access listener (FAL) maximum message buffer size from 64 to 127 blocks. This extension allows FAL to handle files with 32767 byte records and makes the FAL maximum message buffer size consistent with the Record Management System (RMS) maximum buffer size of 127 blocks. You can improve performance of file copies if you use a network block count of 127. Use the DCL command SET RMS/NETWORK_BLOCK_COUNT to adjust the network block count parameter. __________________________________________________________________ 2.10 Hierarchical Storage Controller (HSC) Revision Levels Required Starting with VMS Version 5.4-1, the following Hierarchical Storage Controller (HSC) microcode revision levels are required for all HSC software: o V500 for HSC40 and HSC70 o V400 for HSC50 __________________________________________________________________ 2.11 LADCP Release Notes This section contains release notes pertaining to the Local Area Disk Control Program (LADCP). For information on LADCP, see the VMS LAD Control Program Manual, order number AA-PD1LA-TE. For help in using LADCP, you can access the online LADCP HELP facility by entering the following commands: $RUN SYS$SYSTEM:ESS$LADCP LADCP>HELP 2-9 System Manager Release Notes 2.11 LADCP Release Notes ___________________________ 2.11.1 InfoServer Can Now Write to Services Starting with VMS Version 5.4-1, InfoServer 100 can write to InfoServer 100 services that are write enabled. These services can be either entire devices or partitions that are named collections of logical blocks. When you mount a service as write enabled, InfoServer blocks all other connections to the service. ___________________________ 2.11.2 New LADCP Command VMS Versions 5.4-1 and 5.4-2 add the SHOW SERVICES command to the Local Area Disk Control Program (LADCP). The SHOW SERVICES command displays all services available on the network to which the client system can connect. The SHOW SERVICES command lists each service by its server node and displays information about each service, such as device type, rating, current connects, and whether or not the service allows write executions. Example 2-1 is an example of the information displayed by the SHOW SERVICES command: __________________________________________________________________ 2.12 Terminal Fallback Utility Release Notes This sections contains system manager release notes applicable to the Terminal Fallback Utility (TFU). 2-10 System Manager Release Notes 2.12 Terminal Fallback Utility Release Notes Example 2-1 LADCP SHOW SERVICES Sample Display _______________________________________________________ $ RUN SYS$SYSTEM:ESS$LADCP LADCP> SHOW SERVICES Interrogating network, please wait... Services offered by node ESS_08002BXXXXXX (LAD V3.0, Address: 08-00-2B-XX-XX-XX) Current Writes Service: Device: Rating: Connects: Allowed?: CDBIN03JUL01 RRD40 32371 2 No VMS054 RRD40 32371 0 No SCRATCH_DK RZ23 32380 0 Yes LADCP> _______________________________________________________ ___________________________ 2.12.1 TFU Problem in Error Message Display-Problem Corrected Prior to VMS Version 5.4-1, if the Terminal Fallback Utility (TFU) parsed a foreign command with an unrecognized qualifier, TFU displayed the text of the error message twice. VMS Versions 5.4-1 and 5.4- 2 correct this problem. TFU now displays the error message only once. ___________________________ 2.12.2 TFU Now Supports P.S.I. Terminals In previous versions of VMS, the Terminal Fallback Utility (TFU) did not support the P.S.I. terminal. Starting with VMS Version 5.4-1, TFU supports the P.S.I. terminal. The P.S.I. terminal can enable FALLBACK at the remote system from which the user dials in. For further information about using TFU, refer to the VMS Terminal Fallback Utility Manual. 2-11 System Manager Release Notes 2.13 TLZ04 Tape Driver-Problem Corrected __________________________________________________________________ 2.13 TLZ04 Tape Driver-Problem Corrected VMS Versions 5.4-1 and 5.4-2 correct a problem with the TLZ04 tape driver that is related to the PORT driver associated with the Q-bus-to-SCSI Adapter (QZA) and is found on systems using that adapter. Prior to VMS Version 5.4-1, mixed bus configurations such as the Small Computer System Interface (SCSI) and DIGITAL Storage Systems Interconnect (DSSI) sometimes saw multiple bus resets when a system crash occurred and attempted to reboot immediately after the crash. (A bus reset causes all of the devices on the bus to go off-line and into mount verification.) When the system disk was not a SCSI device and the bus was not reset, the PKI driver software assumed asynchronous operation until it was notified differently. When notification did not take place, the driver detected phase or bus errors and issued a bus reset. The driver then attempted to retry the failed operation and failed again. This scenario led to bus resets in loop mode. VMS Versions 5.4-1 and 5.4-2 correct the multiple bus reset problem. __________________________________________________________________ 2.14 Volume Shadowing Phase II Release Notes The release notes in this section pertain to VMS Volume Shadowing Phase II. ___________________________ 2.14.1 Overview VMS Volume Shadowing Phase I provides centralized shadowing on VMS systems that use HSC (Hierarchical Storage Controller) disks with identical DIGITAL Storage Architecture (DSA) disks. VMS Volume Shadowing Phase II is not limited to HSC-controlled disks; rather, it extends volume shadowing capabilities to the following: o All DSA disks, including those on local adapters 2-12 System Manager Release Notes 2.14 Volume Shadowing Phase II Release Notes o All DSSI (DIGITAL Small Systems Interconnect) RF- series disk drives on any VAX computer o Disks served by the mass storage control protocol (MSCP) and located anywhere in any supported VAXcluster configuration For more information, refer to the VMS Volume Shadowing SPD (27.29.07). For VMS Version 5.4-2, VMS Volume Shadowing Phase II is limited to 32 shadow sets in a VAXcluster system. The configuration rules for VMS Volume Shadowing Phase I are specified in the VMS Volume Shadowing SPD. ___________________________ 2.14.2 AUTOGEN Operations-Volume Shadowing Adjustment Required If you performed an AUTOGEN operation after you upgraded or installed the VMS operating system, and now you want to use Volume Shadowing Phase II for the first time, you must adjust the SYSGEN parameter NPAGEDYN before you run Volume Shadowing Phase II. For best results, perform an AUTOGEN operation on your system using the FEEDBACK parameter to modify the SYSGEN parameter NPAGEDYN. Match the setting of NPAGEDYN in MODPARAMS.DAT with that of your workload. Make the necessary adjustments as follows: 1 To make sure you have the necessary privileges, log in to the system manager's account. 2 Determine the current value for the SYSGEN parameter NPAGEDYN by entering the following command lines: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> USE CURRENT SYSGEN> SHOW NPAGEDYN 2-13 System Manager Release Notes 2.14 Volume Shadowing Phase II Release Notes 3 Edit the file SYS$SYSTEM:MODPARAMS.DAT and add the following entry, where nnnnn is the current SYSGEN value plus 36,000: MIN_NPAGEDYN = nnnnn 4 Perform an AUTOGEN operation on your system by entering the following command line: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT FEEDBACK For more information about AUTOGEN, see the Guide to Setting Up a VMS System. ___________________________ 2.14.3 Batch and Print Jobs-Reentering after Conversion After you convert a disk to a Volume Shadowing Phase II shadow set, batch and print jobs that were previously entered in the queuing system database (JBCSYSQUE.DAT) and whose job-related files reside on the device, will not execute as scheduled. Jobs in the pending, holding, timed release, and retained states before the conversion are candidates for this type of failure. This problem with execution occurs because the job entry in the queue database contains the physical device name of the disk where files associated with the job reside (command procedures and files to be printed). The device name that must now be referenced is the shadow-set virtual unit to which the disk volume was added. Before converting a disk to a Volume Shadowing Phase II shadow set, Digital recommends that you use the following DCL command to make a list of all batch and print jobs that refer to files on the disk: $ SHOW QUEUE/ALL/FULL/OUTPUT=listing-file 2-14 System Manager Release Notes 2.14 Volume Shadowing Phase II Release Notes Then, locate all jobs that refer to the device and do one of the following: o Run these jobs before performing the conversion. o Delete the jobs from the queue database and reenter them after the conversion is finished. ___________________________ 2.14.4 Changing Physical Device Names VMS Volume Shadowing Phase II records the physical member device names in an on-disk data structure. This information is used for various purposes by subsequent MOUNT commands. A side effect of storing this information is that, even though a shadow set is dismounted across the cluster, changing the names of the data disks through techniques such as swapping unit plugs can cause subsequent MOUNT commands to fail. Use one of the following supported methods for changing the physical device names when the shadow set is dissolved and then remount the set: o Change the virtual unit name when you recreate the shadow set. o Mount the disks using the /OVERRIDE=SHADOW qualifier before recreating the set. ___________________________ 2.14.5 SHADBOOTFAIL Bugcheck Message If you are using VMS Volume Shadowing Phase II and you get a SHADBOOTFAIL bugcheck message, you might not be able to access the dump if further analysis is required. Shadowing dump-file processing utilizes merge operations to perform a dump fixup. Because the set was never mounted on this node, a merge operation is not triggered. Refer to Appendix A in the VMS Volume Shadowing Manual for more information about why the shadow set failed to boot from the system disk shadow set. 2-15 System Manager Release Notes 2.14 Volume Shadowing Phase II Release Notes ___________________________ 2.14.6 SHOW DEVICES Command For systems using VMS Volume Shadowing Phase II, the SHOW DEVICES display does not list virtual units on nodes that have not mounted the shadow set. Shadow set virtual units are not served to the cluster through the mass storage control protocol (MSCP). Virtual units are created and maintained in a distributed fashion on each node in the cluster. Individual physical members, however, are MSCP served; with the SHOW DEVICES command, they are displayed on all nodes from which the physical members are accessible. ___________________________ 2.14.7 SHOW DEVICES Command-Addition to Display for Full Copy or Merge Operation If your VMS Volume Shadowing Phase II shadow set is undergoing a full copy or a merge operation, the display resulting from the DCL command SHOW DEVICES now includes the percentage of the disk that has been copied or merged. The SHOW DEVICES information is available on all nodes that have the shadow set mounted. Note: Issuing the SHOW DEVICES command on the node where the full copy or merge operation is taking place indicates the exact percentage of the disk that has been copied. However, when you issue the SHOW DEVICES command from some other node, the number indicating the percentage copied in the SHOW DEVICES output lags (by a small percentage) the actual percentage copied. In Example 2-2, the SHOW DEVICES command was issued when the $1$DIA0 device was undergoing a full copy operation. The example shows that $1$DIA0 is the target of a full copy operation and that the disk is 26% copied. Also, devices $1$DIA3 and $1$DIA4 are merge members of the shadow set represented by the virtual unit DSA0. The SHOW DEVICES output indicates 2-16 System Manager Release Notes 2.14 Volume Shadowing Phase II Release Notes that 11% of the disk devices on the virtual unit DSA0 are merged. Example 2-2 SHOW DEVICES Display for Shadow Sets _______________________________________________________ $ SHOW DEVICES Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt DSA0: Mounted 0 V54 292269 215 3 DSA2000: Mounted 0 X4AU 292971 1 1 $1$DIA0:(WHEN) ShadowCopying 0 (copy trgt DSA2000: 26% copied) $1$DIA3: (WHY) ShadowMergeMbr 0 (merging DSA0: 11% merged) $1$DIA4:(WHERE) ShadowMergeMbr 0 (merging DSA0: 11% merged) $1$DUA0:(WWWWWW) Online 0 $1$DUA1:(WWWWWW) Online 0 _______________________________________________________ Note that if a full copy and merge operation is occurring at the same time in the same shadow set, the number indicating the percentage merged remains static until the full copy completes. In Example 2-3, the SHOW DEVICES command was issued when the $1$DIA0 device was undergoing a full copy operation, and devices $1$DIA1 and $1$DIA2 were merge members. In this case, because the merge and full copy operations are performed in the same DSA2000 virtual unit, the merge operation is stalled until the full copy to the $1$DIA0 device is complete. Consecutive SHOW DEVICES displays will show that the percentage copied to the $1$DIA0 device continues to increment, while the merge members remain at 14% copied until the full copy operation completes. Then the merge operation proceeds again to completion. 2-17 System Manager Release Notes 2.14 Volume Shadowing Phase II Release Notes Example 2-3 SHOW DEVICES Display for Shadow Sets _______________________________________________________ $ SHOW DEVICES Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt DSA2000: Mounted 0 X4AU 292971 1 1 $1$DIA0: (WHEN) ShadowCopying 0 (copy trgt DSA2000: 82% copied) $1$DIA1: (WHO) ShadowMergeMbr 0 (merging DSA2000: 14% merged) $1$DIA2: (WHAT) ShadowMergeMbr 0 (merging DSA2000: 14% merged) $1$DUA3: (WWWWWW) Online 0 $1$DUB0:_(WWWWWW)__Online_________0_________ The SHOW DEVICES display does not indicate the percentage copied for VMS Volume Shadowing Phase I shadow sets. ___________________________ 2.14.8 Specify a Virtual Unit Name to Obtain $GETDVI FREEBLOCK Information If you use the $GETDVI system service to obtain FREEBLOCK count information for a shadow set, you should specify the virtual unit name on the $GETDVI service. If you specify the device name of one of the shadow set members, the $GETDVI service returns a value of zero. ___________________________ 2.14.9 SYSGEN Parameter VMSD3-Special Parameter to Control Failover With VMS Version 5.4, a special SYSGEN parameter, VMSD3, controls failover of shadowed volumes. The VMSD3 parameter specifies in hexadecimal the number of seconds (from 1 to 255) during which recovery of a repairable shadow set is attempted. If the high- order bit (%X80000000) is off, recovery of a failing member is attempted for 5 seconds before that member is removed from the shadow set. If the bit is on, 2-18 System Manager Release Notes 2.14 Volume Shadowing Phase II Release Notes the low-order byte is used dynamically to specify the number of seconds in which to attempt the recovery of a failing member. If zero is specified, it is ignored and the 5-second value is used. The following example shows how to set the failover attempt time to 10 seconds: $ MCR SYSGEN SYSGEN> USE CURRENT SYSGEN> SET VMSD3 %X8000000A SYSGEN> SHOW VMSD3 Parameter Name Current Default Min. Max. Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- VMSD3 -2147483638 0 0 1 D SYSGEN> WRITE CURRENT SYSGEN> EXIT $ ___________________________ 2.14.10 SYSGEN Parameter VIRTUALPAGECOUNT Adjustment In general, VMS volume shadowing can perform full copy and merge operations without any changes to SYSGEN parameter values. In some cases, however, it might be necessary to adjust the values of the SYSGEN parameters VIRTUALPAGECOUNT and WSMAX to ensure that the volume shadowing server process can develop sufficient virtual address space to do copy and merge operations. To determine whether the VIRTUALPAGECOUNT and WSMAX parameters need adjustment, compare the current values of these parameters (use the SYSGEN command SHOW to examine the parameter values) with the result of the following equation that uses the current value of the SYSGEN parameter SHADOW_MAX_COPY: (SHADOW_MAX_COPY*128)+100) 2-19 System Manager Release Notes 2.14 Volume Shadowing Phase II Release Notes For example, if a system has a SHADOW_MAX_COPY parameter of 42 (the default value of the SHADOW_ MAX_COPY parameter is 4), then the SYSGEN parameters VIRTUALPAGECOUNT and WSMAX should be no less than (42*128)+100, or 5476 pages. ___________________________ 2.14.11 UAF Parameter Changes For VMS Volume Shadowing Phase II, the user authorization file (UAF) parameter changes listed in Table 2-1 are recommended for your system account (these are the best minimum estimates for the shadow server): Table 2-1 Recommended UAF Parameters for the System ___________Account_____________________________________ BYTLM SHADOW_MAX_COPY * 3KB BIOLM SHADOW_MAX_COPY + 10 DIOLM SHADOW_MAX_COPY + 10 ASTLM SHADOW_MAX_COPY * 2 + 20 TQELM SHADOW_MAX_COPY * 2 + 10 WSQUO SHADOW_MAX_COPY * 128 + 100 WSDEF SHADOW_MAX_COPY * 128/2 + 100 ENQLM SHADOW_MAX_COPY * 2 PGFLQUO___SHADOW_MAX_COPY_*_130_+_500__________________ 2-20 System Manager Release Notes 2.15 Standalone BACKUP Caution __________________________________________________________________ 2.15 Standalone BACKUP Caution VMS Version 5.4-1 and 5.4-2 do not build Standalone BACKUP correctly on the following small media: o RX01 o RX02 o RX33 o RX50 o TU58 Do not attempt to use VMS Version 5.4-2 to build Standalone BACKUP on any of these media. Digital recommends that you use VMS Version 5.4 or earlier. Digital expects to correct this problem in a future release of the VMS operating system. 2-21 _______________________________________________________ 3 Programmer Release Notes This chapter includes information about VMS Version 5.4-2 for application and system programmers. __________________________________________________________________ 3.1 BASIC INKEY$ Function-Change In previous versions of VMS, the first VAX BASIC INKEY$ function left the application keypad in application mode until the end of the program. Starting with VMS Version 5.4-1, after the program executes the INKEY$ function, the application keypad stays in numeric mode if it was in numeric mode before the program started. This change also affects BASIC INPUT, INPUT LINE, and LINPUT statements that a program executes after the INKEY$ function. Starting with VMS Version 5.4-1, when the program executes an INPUT, INPUT LINE, or LINPUT statement after an INKEY$ function, the application keypad stays in numeric mode if it was in numeric mode before the program started. __________________________________________________________________ 3.2 I/O Preferred Path Interface for DSA Devices-Problem Corrected The VMS Version 5.4 preferred path interface does not allow you to specify the local node as the preferred path. VMS Versions 5.4-1 and 5.4-2 correct this problem. Starting with VMS Version 5.4-1, if you specify the local node as the preferred path, the disk class driver clears any preferred path information for the disk, allowing default path selection. For disks that have dual paths between VMS systems, specifying the 3-1 Programmer Release Notes 3.2 I/O Preferred Path Interface for DSA Devices-Problem Corrected local node as the preferred path causes the disk class driver to try to locate the disk on a local controller before trying Mass Storage Control Protocol (MSCP) server paths. __________________________________________________________________ 3.3 VMS RMS CONVERT/RECLAIM Utility-Problem A problem exists with the VMS RMS CONVERT/RECLAIM Utility. During reclamation of a VMS RMS prolog 3 indexed file containing multiple keys, the CONVERT /RECLAIM Utility incorrectly handles records deleted under the rules of the RAB$V_FDL record-processing option. These records are created under application control (using RAB$L_ROP = RAB$V_FDL) or during normal RMS record operations where process resources are at a minimum. For information on the RAB$V_FDL record- processing option, see the VMS Record Management Services Manual. Failure of the CONVERT/RECLAIM Utility to correctly handle records that are deleted under these rules of the RAB$V_FDL record-processing option may cause normal RMS indexed file record processing operations to fail in situations where they normally would not. Possible errors returned are RMS$_RNF, RMS$_DUP, or internal RMS processing errors that may provoke an RMS non-fatal BUGCHECK. To avoid this problem caused by the VMS RMS CONVERT /RECLAIM Utility, perform one of the following actions: o Use the VMS RMS CONVERT Utility instead of the VMS RMS CONVERT/RECLAIM Utility. o Prior to using the VMS RMS CONVERT/RECLAIM Utility, access every record along all secondary keys. 3-2 _______________________________________________________ 4 Documentation Release Notes This chapter describes changes to specific manuals in the VMS documentation set. __________________________________________________________________ 4.1 Addition to Display PostScript Documentation Actual colors are colors that the Display PostScript (DPS) server allocates as a result of either of two actions: o Passing a non-zero actual parameter to the CREATE CONTEXT routine or to the setXgcdrawablecolor PostScript operator o Using the setXrgbactual PostScript operator DPS always allocates actual colors as shared. However, if you create a colormap with the AllocAll flag, all entries in the colormap are allocated as nonshareable. Therefore, you cannot use actual colors in DPS with a colormap that you created with the AllocAll flag. __________________________________________________________________ 4.2 VMS System Generation Utility Manual The CONNECT/ADAPTER=adapter-spec command on page SGN- 10 of the VMS System Generation Utility Manual defines adapter specification as: "...the name of the Unibus or mass bus adapter to which the device is attached. The value can be expressed as an integer or as one of the names listed by the SYSGEN command SHOW/ADAPTER." Substitute the following definition for adapter specification: 4-1 Documentation Release Notes 4.2 VMS System Generation Utility Manual "The adapter specification is the nexus number assigned to the device. You can find the nexus number by executing the SYSGEN SHOW/ADAPTER or SHOW/BUS commands." VMS does not support the use of named equivalents for nexus numbers such as UB0 on all machines. __________________________________________________________________ 4.3 VMS Version 5.4 Upgrade and Installation Manual Page D-4 of the VMS Version 5.4 Upgrade and Installation Manual incorrectly states that CDD/Plus [TM] V4.2 is the minimum version required for VMS Version 5.4. VMS Version 5.4 requires CDD/Plus V4.2A or later. If you must run CDD/Plus, do not install VMS Version 5.4 until you are running CDD/Plus V4.2A. ________________ [TM] CDD/Plus is a trademark of Digital Equipment Corporation. 4-2