____________________________________________________ OpenVMS AXP Version 1.5 Release Notes Order Number: AA-PV72A-TE May 1993 This document describes features, changes, and restrictions that apply to the OpenVMS AXP Version 1.5 operating system. Revision/Update Information: This is a new manual. Software Version: OpenVMS AXP Version 1.5 Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ May 1993 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. © Digital Equipment Corporation 1993. All Rights Reserved. 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: Alpha AXP, AXP, Bookreader, CDD/Repository, CI, DDCMP, DEC, DECchip, DECdtm, DEC Fortran, DECmcc, DECnet, DECram, DECspell, DECterm, DECthreads, DECwindows, DEQNA, Digital, Digital Press, HSC, KDM, LASTport, LAT, MSCP, OpenVMS, PDP-11, Q-bus, TURBOchannel, UETP, ULTRIX, VAX, VAX BASIC, VAX C, VAXcluster, VAX DOCUMENT, VAX MACRO, VAX PL/I, VAXserver, VAXstation, VMS, VMScluster, VT, XUI, the AXP logo, and the DIGITAL logo. The following are third-party trademarks: Adobe, Display PostScript, and PostScript are registered trademarks of Adobe Systems Incorporated. Microsoft, MS, and MS-DOS are registered trademarks of Microsoft Corporation. Motif, OSF, OSF/1, and OSF/Motif are registered trademarks of the Open Software Foundation, Inc. UNIX is a registered trademark of UNIX System Laboratories, Inc. X Window System is a common law trademark of MIT. All other trademarks and registered trademarks are the property of their respective holders. ZK6116 This document was prepared using VAX DOCUMENT, Version 2.1. _________________________________________________________________ Contents Preface................................................... xv 1 Overview of OpenVMS AXP Version 1.5 1.1 Differences Between OpenVMS AXP Version 1.5 and Version 1.0............................... 1-1 1.2 Unsupported Components and Functionality...... 1-2 1.3 How to Report Problems Found in OpenVMS AXP... 1-3 2 Running OpenVMS AXP 2.1 Release Notes Specific to OpenVMS AXP Version 1.5 .......................................... 2-1 2.2 AXP Environment............................... 2-2 2.3 Installation and Upgrade ..................... 2-2 2.3.1 InfoServer and Initial System Load (ISL) Support Available......................... 2-2 2.3.2 Installation Procedure - Spurious Message No Longer Appears......................... 2-3 2.3.3 Upgrade Procedure Requirement............. 2-3 2.3.4 Effect of Upgrade Procedure on Queue Database.................................. 2-3 2.3.5 DECram Version 1.1 Must Be Reinstalled After OpenVMS AXP Upgrade................. 2-4 2.3.6 Product Authorization Key Installation.... 2-4 2.4 Conversational Bootstrap - Problem Fixed...... 2-4 2.5 Compatibility with Translated Programs and Images........................................ 2-4 2.6 Privileged Architecture Library Code (PALcode) Version Checking Enabled...................... 2-5 2.7 Running OpenVMS AXP Using a DEC 3000 Series AXP Computer.................................. 2-6 2.7.1 Running DECwindows........................ 2-6 iii 2.7.2 DECwindows Support for OpenVMS AXP Version 1.0 ...................................... 2-7 2.7.3 Using DECW$TAILOR to Add or Remove DECwindows Files.......................... 2-7 2.7.4 DECwindows X11 Display Server and Driver.................................... 2-8 2.7.4.1 New Font Formats........................ 2-8 2.7.4.2 Font Compiler - Restrictions............ 2-8 2.7.4.3 Font Server Support..................... 2-9 2.7.4.4 Support Added for Scalable Outline Fonts................................... 2-10 2.7.4.5 DECwindows Transport.................... 2-12 2.7.4.6 Alternate Window System Console Provides 24-Line Console Window ................. 2-14 2.7.4.7 Known Problems.......................... 2-15 2.7.4.8 Problems Fixed ......................... 2-16 2.7.4.9 Error Recovery.......................... 2-17 2.7.4.10 Reporting Errors........................ 2-17 2.7.5 Multihead Configurations.................. 2-17 2.7.6 TURBOchannel PMAZB Adapter Support........ 2-18 2.8 Running OpenVMS AXP Using a DEC 3000 Model 300 Series AXP Computer........................... 2-20 2.9 Running OpenVMS AXP Using a DEC 3000 Model 400 AXP Computer.................................. 2-20 2.10 Running OpenVMS AXP Using a DEC 3000 Model 500 AXP Computer.................................. 2-20 2.11 Running OpenVMS AXP Using a DEC 4000 Series AXP Computer ................................. 2-20 2.12 Running OpenVMS AXP Using a DEC 7000 Model 600 AXP Computer.................................. 2-21 2.12.1 Local DIGITAL Storage Architecture (DSA) Disk and Tape Support .................... 2-21 2.12.2 SCSI Support ............................. 2-21 2.12.3 Booting from a SCSI Disk - Problem When XDELTA Is Included ....................... 2-22 2.13 PNDRIVER and Setting of SCSSYSTEMID System Parameter - Problem .......................... 2-23 2.14 SCSI Disk Class Driver (DKDRIVER) - Restriction .................................. 2-23 iv 3 General User-Level Release Notes 3.1 Release Notes Specific to OpenVMS AXP Version 1.5 .......................................... 3-1 3.2 DCL Commands and Utilities.................... 3-2 3.2.1 APPEND/PROTECTION and COPY/PROTECTION Commands - Problem Fixed ................. 3-2 3.2.2 EDIT Command ............................. 3-2 3.2.2.1 Change in Default Editor................ 3-2 3.2.2.2 Online Help Corrections................. 3-3 3.2.2.3 Problem Fixed .......................... 3-4 3.2.2.4 Translated TECO Editor Now Available ... 3-4 3.2.3 SET PROCESS/SUSPEND=KERNEL/ID= Command in a Cluster Environment - Incorrect Behavior.................................. 3-4 3.3 DECTPU and EVE Version 3.1 Notes.............. 3-4 3.4 Help Message Utility (MSGHLP) ................ 3-6 3.5 Mail Utility - Change in Default Editor....... 3-8 3.6 Sort/Merge Utility............................ 3-8 3.7 UETP Ethernet Test - Problem Fixed............ 3-9 4 System Management Release Notes 4.1 Release Notes Specific to OpenVMS AXP Version 1.5 .......................................... 4-1 4.2 Accounting Utility - Problem Fixed ........... 4-2 4.3 Modifications to Analyze/Disk_Structure Utility....................................... 4-3 4.4 Authorize Utility............................. 4-3 4.5 AUTOGEN Command Procedure..................... 4-4 4.5.1 Problem During System Startup............. 4-4 4.5.2 Support for Installed Resident Images..... 4-5 4.5.3 System Parameters......................... 4-6 4.5.3.1 AWSTIME and QUANTUM System Parameters... 4-6 4.5.3.2 DUMPSTYLE System Parameter - New Values ........................................ 4-6 4.5.3.3 MULTIPROCESSING System Parameter........ 4-7 4.5.3.4 PHYSICAL_MEMORY System Parameter........ 4-9 4.5.3.5 System Parameters and Performance Measurements ........................... 4-9 4.5.3.6 System Parameters That Have Been Removed ........................................ 4-9 4.6 Backup Utility ............................... 4-10 4.6.1 New BACKUP Qualifier - /EXACT_ORDER....... 4-11 v 4.6.2 Standalone BACKUP Change.................. 4-14 4.6.3 Restrictions ............................. 4-14 4.6.4 Backup Restriction Removed ............... 4-14 4.7 CONSCOPY.COM Command Procedure Not Available .............................................. 4-15 4.8 DECnet for OpenVMS AXP ....................... 4-15 4.8.1 Cluster Alias Support Available........... 4-15 4.8.2 Restrictions ............................. 4-15 4.9 Digital-Supplied Device Drivers - File Name Format Change ................................ 4-16 4.10 Distributed Transaction Manager Functionality Available..................................... 4-16 4.11 Error Log Report Formatter (ERF).............. 4-17 4.11.1 Features.................................. 4-17 4.11.2 Restrictions and Limitations.............. 4-17 4.12 Help Message Utility (MSGHLP) Restriction..... 4-17 4.13 Changes to the Install Utility................ 4-18 4.14 LAT Notes..................................... 4-19 4.15 License Management Facility (LMF)............. 4-19 4.16 Monitor Utility............................... 4-21 4.17 Mount Utility................................. 4-22 4.17.1 OpenVMS Support of ISO 9660 Standard - Problems and Restrictions................. 4-22 4.17.1.1 Volume Labels........................... 4-22 4.17.1.2 Volume Set Names........................ 4-23 4.17.1.3 Volume Set and Volume Set Name Duplication ............................ 4-23 4.17.1.4 InfoServer Served Volumes............... 4-23 4.17.1.5 UNDEFINED Record Format Errors.......... 4-24 4.17.1.6 PATHWORKS Access to ISO 9660 in a WAN/LAN Environment .................... 4-24 4.17.2 Restrictions.............................. 4-25 4.18 Password Generation........................... 4-25 4.19 Privileges, Protections, and Quotas........... 4-25 4.20 Security Auditing - Problem Fixed ............ 4-25 4.21 Symmetric Multiprocessing Support............. 4-25 4.21.1 Symmetric Multiprocessing Extension License................................... 4-27 4.21.2 Enabling Symmetric Multiprocessing on AXP Computers................................. 4-28 4.21.3 Restrictions.............................. 4-28 4.22 System Generation Utility - Unsupported Commands ..................................... 4-29 vi 4.23 System Management Utility..................... 4-29 4.23.1 I/O Configuration Support in SYSMAN....... 4-29 4.23.2 Change in Display for SYSMAN IO SHOW BUS Command for TURBOchannel Adapters......... 4-30 4.23.3 No Secondary Error Messages for PARAMETERS SET and PARAMETERS SHOW Commands - Problem................................... 4-30 4.23.4 Performing Clusterwide DISKQUOTA Commands - Restriction ............................ 4-31 4.23.5 Ownership of System Directories........... 4-33 4.24 Terminal Fallback Facility (TFF).............. 4-33 4.25 Virtual I/O Cache - New Feature .............. 4-35 4.26 VMSINSTAL Checks Process Quotas .............. 4-35 4.27 Watch Chip - Change in Time Range............. 4-36 4.28 XCDAC Adapter Storage-Only Support Available..................................... 4-37 4.29 X Terminal Support ........................... 4-37 5 Programming Release Notes 5.1 Release Notes Specific to OpenVMS AXP Version 1.5 .......................................... 5-1 5.2 Accessing Another Process's Context........... 5-2 5.2.1 Reading and Writing in the Address Space of Another Process........................ 5-3 5.2.1.1 EXE$READ_PROCESS and EXE$WRITE_PROCESS....................... 5-3 EXE$READ_PROCESS.................................... 5-4 EXE$WRITE_PROCESS................................... 5-7 5.2.2 Writing an Executive Image................ 5-12 5.2.2.1 INITIALIZATION_ROUTINE Macro............ 5-15 INITIALIZATION_ROUTINE.............................. 5-15 5.2.2.2 Linking an Executive Image.............. 5-17 5.2.2.3 Loading an Executive Image.............. 5-19 5.2.2.4 LDR$LOAD_IMAGE.......................... 5-20 vii LDR$LOAD_IMAGE...................................... 5-20 5.3 Calling Standard Change Between Native and Translated Images............................. 5-24 5.3.1 Changes to the Procedure Signature Information Block (PSIG) ................. 5-24 5.3.2 Versions of Compiled Languages............ 5-25 5.3.3 MACRO-64 Assembler Version 1.0 for OpenVMS AXP Systems............................... 5-26 5.4 Run-Time Support for DEC COBOL Programs - New Feature....................................... 5-27 5.5 OpenVMS Debugger ............................. 5-27 5.5.1 Enhancements.............................. 5-28 5.5.1.1 Language Support........................ 5-28 5.5.1.2 DECwindows Motif User Interface......... 5-28 5.5.1.3 RUN and RERUN Commands and the Kept Debugger................................ 5-30 5.5.1.4 Packed Math Operations.................. 5-30 5.5.2 Corrections to Known Problems............. 5-30 5.5.3 Known Problems and Restrictions........... 5-31 5.5.3.1 Debugging Critical Sections............. 5-31 5.5.3.2 CALL Command Problems and Restrictions............................ 5-32 5.5.3.3 EVALUE Command Limitation............... 5-32 5.5.3.4 EXAMINE Command Problems and Restrictions............................ 5-33 5.5.3.5 SET WATCH Command and Nonstatic Watchpoints............................. 5-33 5.5.3.6 SET WATCH/STATIC Command and Static Watchpoints............................. 5-34 5.5.3.7 SET BREAK/UNALIGNED_DATA Command and Related System Service Call ............ 5-34 5.5.3.8 Kept Debugger Restrictions and Problems................................ 5-34 5.5.3.9 DECwindows Motif Interface Restrictions and Problems............................ 5-36 5.5.3.10 Debugging Translated Images............. 5-38 5.5.3.11 Debugging Installed Resident Images..... 5-38 5.5.3.12 Debugging Inlined Routines.............. 5-38 5.5.3.13 Debugging Global Sections............... 5-39 5.5.3.14 Debugging Register Frame Procedures or Null Frame Procedures................... 5-39 5.5.3.15 Complex Variables in DEC Fortran Programs................................ 5-39 viii 5.5.3.16 Concealed Rooted-Directory Logical Names for Source Files........................ 5-39 5.5.3.17 DEPOSIT/TYPE Command with C Programs.... 5-40 5.5.3.18 SET IMAGE Command Limitation............ 5-40 5.5.3.19 SHOW BREAK and SHOW TRACE Command Limitations............................. 5-40 5.5.3.20 STEP/INTO Command and User Exception Handlers................................ 5-40 5.5.3.21 STEP/OVER Command Error with Recursive Calls................................... 5-40 5.5.3.22 STEP/OVER Command Error with One-Line Program Loops........................... 5-41 5.5.3.23 $WAKE Call Followed by $HIBER Call...... 5-41 5.5.3.24 DCL ANALYZE/PROCESS_DUMP Command and Zero Program Counter.................... 5-41 5.5.3.25 Changed Watchpoint Locations During System Service Calls.................... 5-41 5.5.3.26 STEP Command and Asynchronous System Trap Routines........................... 5-42 5.5.3.27 STEP Command into System Service Calls................................... 5-42 5.5.3.28 LCK$M_DEQALL Modifier in $DEQ System Service Call............................ 5-42 5.6 DECthreads - Restrictions .................... 5-42 5.7 DECwindows Motif for OpenVMS AXP Version 1.1........................................... 5-43 5.8 Executive Notes............................... 5-43 5.8.1 Executive Functions Not Included in OpenVMS AXP............................... 5-43 5.8.2 New Condition Code for Cross-Mode Page-Read Errors ......................... 5-43 5.8.3 Spinlock Changes.......................... 5-44 5.8.4 SYS.EXE Renamed to SYS$BASE_IMAGE.EXE..... 5-44 5.9 Exit Handler - Change in Behavior from Version 1.0........................................... 5-44 5.10 File System Notes............................. 5-44 5.10.1 Restrictions.............................. 5-45 5.10.2 File Definition Language ................. 5-45 5.10.3 National Character Set ................... 5-45 5.11 IEEE Floating-Point Standard.................. 5-45 5.12 Effects of a Failure During an I/O Write Operation..................................... 5-46 5.13 Linker Utility................................ 5-47 ix 5.13.1 Suggestion for Improving Application Code Performance .............................. 5-47 5.13.2 Restrictions ............................. 5-48 5.14 MACRO-32 Compiler for OpenVMS AXP ............ 5-49 5.14.1 New Function.............................. 5-49 5.14.2 Problems Corrected........................ 5-49 5.14.3 Restrictions and Known Problem............ 5-51 5.15 Programming Consideration for Manipulation of Absolute Queues .............................. 5-52 5.16 Run-Time Libraries............................ 5-53 5.16.1 Run-Time Libraries Not Included........... 5-53 5.16.2 Native DEC C Run-Time Library Notes....... 5-54 5.16.2.1 Incompatibilities Between Version 1.5 and OpenVMS AXP Version 1.0 ............ 5-54 5.16.2.2 New Features............................ 5-54 5.16.2.2.1 New Curses Implementation.............. 5-55 5.16.2.2.2 New Single-Character I/O Macro Support................................ 5-55 5.16.2.3 Restrictions in the DEC C RTL........... 5-56 5.16.2.3.1 DEC C RTL Called from User Mode........ 5-56 5.16.2.3.2 Modifying Constants Passed by Reference Can Cause an Access Violation ......... 5-56 5.16.2.3.3 Translated VAX C RTL Interoperability Restrictions........................... 5-57 5.16.2.4 DEC C RTL Images........................ 5-57 5.16.2.5 Incompatibilities Between DEC C RTL and VAX C RTL............................... 5-58 5.16.2.6 Obsolete Functionality.................. 5-60 5.16.2.7 Enhancements Not Found in the VAX C RTL..................................... 5-61 5.16.2.8 Performance Considerations.............. 5-62 5.16.2.9 Problems Corrected...................... 5-63 5.16.2.10 Known Problems.......................... 5-66 5.16.3 Compatibility Between the VAX and AXP Mathematics Libraries..................... 5-67 5.17 Security-Related Data Structures.............. 5-68 5.18 STARLET Data Structures and Definitions for C Programmers................................... 5-68 5.19 SUMSLP Utility (SUMSLP) - Problem Fixed....... 5-70 5.20 System Dump Analyzer Utility (SDA) Notes...... 5-70 5.20.1 SHOW MACHINE_CHECK Command Available...... 5-71 5.20.2 Problems Fixed............................ 5-71 5.20.3 Known Problems............................ 5-72 x 5.21 System Services Notes......................... 5-74 5.21.1 Low Four Bits of Chan Argument Are Checked - Change ................................. 5-74 5.21.2 Behavior of $CRMPSC and $MGBLSC System Services Differs on AXP and VAX Systems... 5-74 5.21.3 $DCLCMH System Service Behavior Differs on AXP and VAX Systems....................... 5-75 5.21.4 $FAO System Service....................... 5-76 5.21.5 $FORMAT_AUDIT Width Argument Does Not Work Consistently - Restriction ............... 5-76 5.21.6 $GETJPI System Service - New JPI$_DFMBC Item Code................................. 5-76 5.21.7 $SUSPND System Service in a Cluster Environment - Incorrect Behavior ......... 5-76 5.22 Traceback Handler Support..................... 5-77 5.23 Translated Image Environment (TIE) Notes...... 5-77 5.23.1 Interoperability.......................... 5-78 5.23.2 Running Translated Images................. 5-79 5.23.3 TIE Statistics and Feedback............... 5-79 5.23.4 TIE Restrictions.......................... 5-80 5.24 Translated Images and Other Related Files..... 5-83 5.25 Translated Run-Time Libraries................. 5-87 5.25.1 Accessing the D56 Form of the Run-Time Libraries................................. 5-89 5.25.2 Problem with Translated Image Environment............................... 5-89 5.25.3 Translated VAX BASIC Run-Time Library Notes..................................... 5-90 5.25.4 Translated VAX C Run-Time Library Notes... 5-91 5.25.4.1 Functional Restrictions................. 5-91 5.25.4.2 Interoperability Restrictions........... 5-91 5.25.5 Translated DEC Fortran Programs - Problem Fixed..................................... 5-93 6 Batch and Print Queuing System 6.1 Summary of Changes............................ 6-1 6.2 Upgrade and Installation Information.......... 6-2 6.2.1 Required Version for Mixed Architecture VMSclusters............................... 6-3 6.2.2 DECdtm Files Required for the Batch and Print Queuing System...................... 6-3 xi 6.2.3 Effect of Upgrade Procedure on Queue Database.................................. 6-4 6.3 System Management Changes..................... 6-5 6.3.1 New Queue Manager......................... 6-5 6.3.2 New Queue Database Files.................. 6-6 6.3.3 Specifying the Location of Queue Database Files..................................... 6-6 6.3.3.1 Master File............................. 6-8 6.3.3.2 Queue and Journal Files................. 6-9 6.3.4 Starting the Queue Manager and Creating the Queue Database........................ 6-10 6.3.4.1 VMScluster Environments With Multiple System Disks............................ 6-10 6.3.4.2 All Other Configurations................ 6-11 6.3.4.3 Customizing Queue Manager Failover...... 6-13 6.3.4.4 Automatic Queue Manager Restart......... 6-14 6.3.4.5 /NEW_VERSION Qualifier to START/QUEUE/MANAGER Command - Change in Behavior...................... 6-14 6.3.4.6 If the Queue Manager Is Already Started - Change in Behavior.................... 6-14 6.3.4.7 Obsolete Qualifiers to START/QUEUE/MANAGER Command............. 6-15 6.3.5 Stopping the Queue Manager................ 6-15 6.3.6 Stopping Queues on a Node................. 6-16 6.3.7 Autostart Feature......................... 6-16 6.3.7.1 Designating a Queue as an Autostart Queue................................... 6-17 6.3.7.2 Setting Up Autostart Queues for Automatic Failover...................... 6-18 6.3.7.3 Enabling Autostart on a Node............ 6-19 6.3.7.4 Starting Autostart Queues............... 6-20 6.3.7.5 Preventing Autostart Queues from Starting................................ 6-21 6.3.7.6 Disabling Autostart on a Node........... 6-21 6.3.8 Startup and Shutdown Procedures - Changes................................... 6-22 6.3.8.1 Startup Procedure Template.............. 6-22 6.3.8.2 SHUTDOWN.COM............................ 6-23 6.3.9 Deleting the DEFAULT Print Form - Change in Behavior............................... 6-24 6.3.10 Changing Print Forms and Characteristics - Change in Behavior........................ 6-24 xii 6.3.11 Generic Queue Restriction Lifted.......... 6-25 6.3.12 Generic Queues with Implicit Target Lists - Change in Behavior...................... 6-25 6.3.13 Job-Scheduling Priority - Change in Behavior.................................. 6-26 6.3.14 SHOW QUEUE and SHOW ENTRY - Change in Display................................... 6-27 6.3.15 System Parameters for Queuing - Change in Behavior.................................. 6-27 6.3.16 Banner Pages for Jobs Printed from MAIL - Change in Behavior........................ 6-28 6.3.17 PRINT/DELETE Command Requirement.......... 6-28 6.3.18 DEFINE/CHARACTERISTIC - Change in Behavior.................................. 6-29 6.3.19 Known Problems and Problems That Have Been Corrected................................. 6-30 6.3.19.1 STOP/QUEUE/RESET Command - Known Problem................................. 6-30 6.3.19.2 Chance of Queuing System Shutting Down During Node Shutdown - Known Problem.... 6-30 6.3.19.3 Queuing System Problem with CLUSTER_SHUTDOWN Option - Suggested Workaround.............................. 6-31 6.3.19.4 Corruption Detection for Queues - Known Problem................................. 6-31 6.3.19.5 Queuing Information in Accounting Records - Known Problem................. 6-32 6.3.19.6 SYNCHRONIZE Command - Problem Corrected............................... 6-32 6.4 User-Level Changes............................ 6-33 6.4.1 SHOW ENTRY Command........................ 6-33 6.4.1.1 Change in Display....................... 6-33 6.4.1.2 New Job-Name Parameter.................. 6-34 6.4.1.3 New Stalled Job State................... 6-34 6.4.2 SHOW QUEUE - Change in Display............ 6-35 6.4.3 User-Specified Job Retention.............. 6-35 6.4.3.1 Uses for User-Specified Job Retention... 6-36 6.4.3.2 Job Retention Command Syntax............ 6-36 6.4.3.3 How Job Retention Is Determined......... 6-37 6.4.3.4 Timed Retention......................... 6-38 6.4.4 SUBMIT Command - New /NOTE Qualifier...... 6-40 6.4.5 F$GETQUI Lexical Function - Changes....... 6-40 xiii 6.4.6 Invalid Qualifiers Removed from Queue Commands - Change in Behavior............. 6-46 6.4.7 DELETE/ENTRY Command - Problem Corrected................................. 6-46 6.5 Programming Changes........................... 6-46 6.5.1 $GETQUI System Service.................... 6-47 6.5.1.1 Changes and Enhancements................ 6-47 6.5.1.2 QUI$_QUEUE_STATUS Longword - Change in Behavior................................ 6-48 6.5.2 $SNDJBC Service........................... 6-49 6.5.2.1 Changes and Enhancements................ 6-49 6.5.2.2 Change in Behavior for SJC$_START_QUEUE_MANAGER Function Code.................................... 6-50 6.5.2.3 Extended Use of SJC$_SCSNODE_NAME Item Code.................................... 6-51 6.5.2.4 Obsolete Item Codes..................... 6-51 6.5.3 LIB$GETQUI Run-Time Library............... 6-51 7 DECTPU and EVE Release Notes 7.1 Release Notes Specific to OpenVMS AXP Version 1.5 .......................................... 7-1 7.2 DECTPU New Features........................... 7-1 7.2.1 EDIT Command and Multiple Input Files..... 7-2 7.2.2 Choosing Alternate Character Sets......... 7-2 7.2.3 Motif User Interface Support Added for DECTPU.................................... 7-4 7.3 EVE New Features.............................. 7-4 7.3.1 Motif User Interface Support Added for EVE....................................... 7-4 7.3.2 Selecting the Keypad in EVE............... 7-9 7.4 New DECTPU Built-Ins.......................... 7-9 7.4.1 DECwindows Motif for OpenVMS AXP Environment Built-In...................... 7-9 7.4.2 First Input Action Built-In............... 7-10 7.4.3 Input File Name Built-In.................. 7-11 7.4.4 Built-Ins to Lower and Raise a Widget..... 7-11 7.4.5 Motif Widget Context Help Built-In........ 7-12 7.4.6 Pop-Up Parent Widget Built-In............. 7-12 7.4.7 Screen Pixel Size Built-In................ 7-12 7.4.8 Top-Level Widget Built-In................. 7-13 7.4.9 UID Built-In.............................. 7-13 xiv 7.4.10 Widget Resource Types Built-In............ 7-13 7.4.11 Built-Ins for the X Resource Database..... 7-14 7.5 Modified DECTPU Built-Ins..................... 7-14 7.5.1 COMMAND_LINE.............................. 7-15 7.5.2 DECwindows Motif for OpenVMS AXP Environment............................... 7-15 7.5.3 DECwindows Motif for OpenVMS AXP Hierarchy................................. 7-15 7.5.4 Defining a WIDGET Class................... 7-15 7.5.5 GET_INFO (SYSTEM) Built-In Procedure...... 7-15 7.5.6 Global Select............................. 7-16 7.5.7 Icon Handling............................. 7-16 7.5.8 Menu Positioning.......................... 7-17 7.5.9 Sending Strings to Processes.............. 7-17 7.5.10 SCREEN Information........................ 7-18 7.5.11 Screen Update Behavior.................... 7-18 7.5.12 WIDGET Identification..................... 7-19 7.5.13 Writing Buffers........................... 7-19 7.6 Miscellaneous DECTPU Enhancements............. 7-20 7.6.1 Command File Input........................ 7-20 7.6.2 FAO, MESSAGE, and MESSAGE_TEXT Built-Ins................................. 7-20 7.6.3 ON and OFF States......................... 7-20 7.6.4 DCL Qualifier Changes..................... 7-22 7.6.5 Work File................................. 7-22 7.7 New EVE Commands.............................. 7-22 7.7.1 GET Command............................... 7-23 7.7.2 GET WILDCARDED FILES Command.............. 7-23 7.7.3 GLOBAL REPLACE Command.................... 7-23 7.7.4 SET FUNCTION KEYS MOTIF Command........... 7-23 7.7.5 SET SELECTION GRAB FOCUS Command.......... 7-23 7.7.6 SET SELECTION GRAB SELECTION Command...... 7-23 7.8 Miscellaneous EVE Enhancements................ 7-24 7.8.1 Commands Available Within System Buffers................................... 7-24 7.8.2 Edit Handlers............................. 7-24 7.8.3 Faster Command Parser..................... 7-24 7.8.4 FILL Permitted with DIGITAL Standard Runoff (DSR) and VAX DOCUMENT Tags........ 7-25 7.8.5 Menu Changes.............................. 7-25 7.8.6 Obsolete EVE Constants.................... 7-26 7.8.7 SPELL Command Available for DECwindows Motif for OpenVMS AXP..................... 7-27 xv 7.8.8 Title Bar Copyright....................... 7-27 7.9 DECTPU and EVE Restrictions................... 7-27 7.9.1 DECwindows Motif for OpenVMS AXP Applications That Execute READ_KEY and READ_CHAR Built-Ins....................... 7-28 7.9.2 SET (MAPPED_WHEN_MANAGED) Built-In........ 7-28 7.9.3 Small Display Monitors and DECwindows Motif for OpenVMS AXP Applications........ 7-29 7.10 DECTPU Problems That Have Been Fixed ......... 7-29 7.10.1 Aborting Compilation with Ctrl/C.......... 7-29 7.10.2 !AF FAO Directive Dropped from DECTPU Messaging................................. 7-30 7.10.3 CREATE_PROCESS and TMPMBX Privilege....... 7-30 7.10.4 Ctrl/C Key Definition..................... 7-30 7.10.5 Ctrl/C and Startup........................ 7-30 7.10.6 DEFINE_WIDGET_CLASS Built-In.............. 7-31 7.10.7 HELP_TEXT Built-In........................ 7-31 7.10.8 Improved DECwindows Motif for OpenVMS AXP Error Codes............................... 7-31 7.10.9 Journaling Performance Improvement........ 7-32 7.10.10 KEY_NAME and CTRL_MODIFIED................ 7-32 7.10.11 Logical Names and Journal File Conflict... 7-32 7.10.12 DECwindows Motif for OpenVMS AXP and Cursor Blink.............................. 7-33 7.10.13 DECwindows Motif for OpenVMS AXP Interface and TPU$TPU Callable Routine.............. 7-33 7.10.14 DECwindows Motif for OpenVMS AXP Resize... 7-33 7.10.15 Multiple-Line Text Strings in DECwindows Motif for OpenVMS AXP Applications........ 7-34 7.10.16 Partial Escape Sequence Errors............ 7-34 7.10.17 READ_KEY Built-In......................... 7-34 7.10.18 READ_KEY and READ_CHAR Prompts in DECwindows Motif for OpenVMS AXP Applications.............................. 7-34 7.10.19 READ_LINE Built-In for DECwindows Motif for OpenVMS AXP Applications.............. 7-35 7.10.20 READ_LINE Prompt String Limited to 255 Characters................................ 7-35 7.10.21 Reverse Searches from the Beginning of a Line...................................... 7-35 7.10.22 Screen Adjustments in DECwindows Motif for OpenVMS AXP Applications.................. 7-35 7.10.23 Select Range Cleanup...................... 7-35 xvi 7.10.24 SET (ICON_PIXMAP) Built-In................ 7-36 7.10.25 SET (TIMER) Built-In Problem Corrected.... 7-36 7.10.26 SET (WIDGET_CALLBACK) Built-In on Leaf Widgets................................... 7-36 7.10.27 Space Padding............................. 7-36 7.10.28 TRANSLATE and EDIT Screen Display Fixed... 7-37 7.10.29 TPU$PARSEINFO Succeeds with Private CLI... 7-37 7.10.30 UID Hierarchy Identifier.................. 7-37 7.11 EVE Problems That Have Been Fixed............. 7-37 7.11.1 BOX CUT Command Improved.................. 7-37 7.11.2 Box Operations in Overstrike Mode......... 7-38 7.11.3 Command File and SAVE ATTRIBUTES Command................................... 7-38 7.11.4 DCL or SHELL Subprocesses and the DECwindows Motif for OpenVMS AXP Environment............................... 7-38 7.11.5 DECspell Error Was Not Resetting State.... 7-38 7.11.6 DECwindows Motif for OpenVMS AXP EVE and Window Managers Other Than Motif.......... 7-38 7.11.7 Error Handling in GET [WILD] FILE[S]...... 7-39 7.11.8 EVE$BUILD................................. 7-39 7.11.9 EVE$INIT_POSTPROCEDURE Procedure.......... 7-39 7.11.10 EVE$TEARDOWN_WINDOWS and EVE$SETUP_WINDOWS Procedures................................ 7-39 7.11.11 EVE$TRIM_BUFFER Procedure................. 7-40 7.11.12 EVE and Concealed Logical Names........... 7-40 7.11.13 EVE Parser and User's Facility Name....... 7-40 7.11.14 EVE Repeat Operations..................... 7-40 7.11.15 FIND SELECTED with Box Select Active...... 7-42 7.11.16 FILL RANGE................................ 7-42 7.11.17 GET Command and Input File................ 7-42 7.11.18 Help On GET_INFO Built-In Improved........ 7-42 7.11.19 Help Messages Improved.................... 7-43 7.11.20 Improved SHOW BUFFERS Command............. 7-43 7.11.21 Improved Operations on White Space........ 7-43 7.11.22 Improved Window Buffering................. 7-44 7.11.23 Invoking EVE with Ambiguous Input File Specifications............................ 7-44 7.11.24 DECwindows Motif for OpenVMS AXP "Quick Cut" Operation Improved................... 7-44 7.11.25 Mouse Button MB1 and Range Removal........ 7-44 7.11.26 Mouse Drag................................ 7-44 7.11.27 Open Dialog Box Filter Corrected.......... 7-45 xvii 7.11.28 Open Dialog Box and Wildcard Active....... 7-45 7.11.29 OPEN SELECTED Command and Context Resetting................................. 7-45 7.11.30 OPEN SELECTED Command and Multiple File Selections................................ 7-45 7.11.31 OSF/Motif Style Guide Conformance......... 7-46 7.11.32 Primary Cut Mouse Operation............... 7-46 7.11.33 Prompt Replies Trimmed ................... 7-46 7.11.34 /RECOVER and Ctrl/C....................... 7-47 7.11.35 RECOVER BUFFER and Logical Names.......... 7-47 7.11.36 Resize Action Fixed....................... 7-47 7.11.37 SET SCROLLING Command..................... 7-48 7.11.38 SHOW BUFFERS and Buffer Deletion.......... 7-49 7.11.39 SHOW Command Improved..................... 7-49 7.11.40 SYSTEM Buffers are Marked Permanent....... 7-49 7.11.41 Wildcard Input File Specification......... 7-49 7.11.42 EVE Word Operations....................... 7-50 8 VMScluster Support for Version 1.5 8.1 Features ..................................... 8-2 8.2 Restrictions for VMScluster Systems........... 8-3 8.3 Configurations ............................... 8-4 8.4 Licensing VMScluster Software ................ 8-6 8.5 Installation and Operation.................... 8-7 8.6 Preparing the System Disk..................... 8-9 8.7 Preparing a Shared Environment ............... 8-9 8.8 OpenVMS AXP Satellite Booting ................ 8-10 9 Customer Log Desk (CLD) Problems Fixed in OpenVMS AXP Version 1.5 9.1 DEC 3000 Series AXP Computers................. 9-1 9.1.1 Disk Corruption........................... 9-1 9.1.2 PKCDRIVER................................. 9-2 9.2 DEC 7000 Model 600 AXP........................ 9-2 9.3 DECwindows for OpenVMS AXP.................... 9-2 9.3.1 DECwindows Display Server Problems........ 9-2 9.3.2 Internationalization Support Problem...... 9-3 9.3.3 Keyboard Selection Problem................ 9-3 9.4 Linker Utility................................ 9-3 9.5 Record Management Services (RMS) ............. 9-3 9.6 Mandatory Security Update Included............ 9-4 xviii 9.7 Sort/Merge Utility............................ 9-4 10 Documentation Release Notes 10.1 Documentation Changes for OpenVMS AXP Version 1.5........................................... 10-1 10.1.1 Extended Set Redefined.................... 10-1 10.1.2 New Standard + Optional Documentation Set....................................... 10-2 10.1.3 Three Flavors of Documentation Available................................. 10-2 10.2 OpenVMS AXP Documentation Set................. 10-2 10.3 A Comparison of System Management on OpenVMS AXP and OpenVMS VAX........................... 10-2 10.4 OpenVMS DCL Dictionary........................ 10-2 10.4.1 DISABLE AUTOSTART Command................. 10-3 10.4.2 ENABLE AUTOSTART Command.................. 10-3 10.4.3 F$EDIT Lexical Function................... 10-3 10.4.4 INITIALIZE Command........................ 10-4 10.4.5 OPEN Command.............................. 10-4 10.4.6 RUN (Process) Command..................... 10-4 10.4.7 SET Command............................... 10-5 10.4.8 SHOW Command.............................. 10-5 10.4.9 SHOW CLUSTER Command ..................... 10-6 10.4.10 STOP QUEUES/ON_NODE Command............... 10-6 10.5 OpenVMS Debugger Manual....................... 10-7 10.6 OpenVMS Delta/XDelta Debugger Manual.......... 10-7 10.7 Migrating to an OpenVMS AXP System: Porting VAX MACRO Code................................ 10-7 10.8 OpenVMS National Character Set Utility Manual .............................................. 10-8 10.9 Correction to OpenVMS Programming Documentation................................. 10-8 10.10 OpenVMS RTL Screen Management (SMG$) Manual... 10-9 SMG$GET_PASTEBOARD_ATTRIBUTES....................... 10-10 10.11 System Management Documentation............... 10-16 10.12 OpenVMS System Services Reference Manual...... 10-16 10.13 VMScluster Systems for OpenVMS................ 10-16 xix Index Figures 6-1 OpenVMS AXP Version 1.5 Queue Manager..... 6-5 6-2 Determining Job Retention................. 6-37 8-4 Sample Two-LAN Segment VMScluster Configuration ............................ 8-11 Tables 4-1 DUMPSTYLE System Parameter Values......... 4-6 4-2 MULTIPROCESSING Values on AXP and VAX Systems .................................. 4-8 4-3 Unsupported SYSGEN Commands............... 4-29 4-4 TFF Character Tables...................... 4-34 4-5 Minimum VMSINSTAL Installation Process Quotas.................................... 4-36 5-1 Debugger Language Support................. 5-28 5-2 Debugger Commands Disabled in the DECwindows Motif Interface................ 5-36 5-3 Run-Time Libraries Not Included........... 5-53 5-4 Changes in Printf() Behavior Required by the ANSI C Standard....................... 5-60 5-5 Interoperability Documentation............ 5-78 5-6 Run-Time Library Logical Names............ 5-89 6-1 Summary of Batch and Print Changes........ 6-1 6-2 New or Changed F$GETQUI Items............. 6-42 7-1 Character Set Values...................... 7-3 7-2 EVE Widget Resource Name Conversions...... 7-6 7-3 EVE Widget Callback Reason Conversions.... 7-8 7-4 GET_INFO Keywords......................... 7-16 7-5 Name Changes or Additions to EVE's Pulldown Menus............................ 7-25 10-1 SET Command Options....................... 10-5 10-2 SHOW Command Options...................... 10-5 xx _________________________________________________________________ Preface The OpenVMS AXP Version 1.5 Release Notes manual describes features and restrictions of the OpenVMS AXP Version 1.5 operating system. It also provides information about operating AXP computers and provides descriptions of features that are unique to AXP systems. Intended Audience This manual is intended for general users, system managers, developers, and programmers who use the operating system. It is especially useful for those who are about to install the operating system. Document Structure Chapter 1 provides an overview of this version of the operating system, including a summary of new or changed features in this version. Chapter 2 provides information about using AXP computers. Chapter 3 describes changes, new features, and restrictions that affect some commonly used procedures and utilities. Chapter 4 describes changes, new features, and restrictions that affect utilities used for system and performance management, system maintenance, and networking. Chapter 5 provides information about changes, new features, and restrictions that affect areas such as tools, utilities, run-time libraries, system services, and the file system. xv Chapter 6 describes functionality and changes related to the new batch and print queueing system. On OpenVMS AXP Version 1.5, the batch and print queueing system contains support for the features available in the VAX VMS Version 5.5 operating system. Chapter 7 contains information about DECTPU and EVE, including new features, changes, restrictions, and problems that have been fixed. Chapter 8 describes the cluster support that is present in Version 1.5, including dual-architecture configuration and satellite booting. Chapter 9 describes Customer Log Desk (CLD) problems that have been fixed in Version 1.5. Chapter 10 describes corrections to the OpenVMS AXP documentation set. Associated Information For a list of additional documents that are available in support of this version of OpenVMS AXP, refer to the CD-ROM booklet and the Overview of OpenVMS Documentation. The Alpha Architecture Reference Manual mentioned in this document is published by Digital Press under order number EY-L520E-DP. The VMS for Alpha Platforms Internals and Data Structures manual mentioned in this document is published by Digital Press under order number EY-L466E-P1. Conventions In this manual, every use of OpenVMS AXP means the OpenVMS AXP operating system, every use of OpenVMS VAX means the OpenVMS VAX operating system, and every use of OpenVMS means both the OpenVMS AXP operating system and the OpenVMS VAX operating system. The following conventions are also used in this manual: xvi V1.x A margin note beneath each heading indicates the OpenVMS AXP version in which the note was first published. All notes identified with the V1.0 margin note also apply to OpenVMS AXP Version 1.5. 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. GOLD x A sequence such as GOLD x indicates that you must first press and release the key defined GOLD, then press and release another key. GOLD key sequences can also have a slash (/), dash (-), or underscore (_) as a delimiter in EVE commands. In examples, a key name is shown enclosed in a box to indicate that you press a key on the keyboard. (In text, a key name is not enclosed in a box.) . . . 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. xvii 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 optional elements. You can choose one, none, or all of the options. (Brackets are not optional, however, in the syntax of a directory name in an OpenVMS file specification, or in the syntax of a substring specification in an assignment statement.) { } 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. Boldface text is also used to show user input in Bookreader versions of the manual. italic text Italic text emphasizes important information, indicates variables, and indicates complete titles of manuals. Italic text also represents information that can vary in system messages (for example, Internal error number), command lines (for example, /PRODUCER=name), and command parameters in text. UPPERCASE TEXT Uppercase text indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege. xviii - Hyphens in coding examples indicate that additional arguments to the request are provided on the line that follows. numbers All numbers in text are assumed to be decimal, unless otherwise noted. Nondecimal radixes-binary, octal, or hexadecimal-are explicitly indicated. mouse The term mouse refers to any pointing device, such as a mouse, a puck, or a stylus. MB1, MB2, MB3 MB1 indicates the left mouse button, MB2 indicates the middle mouse button, and MB3 indicates the right mouse button. (The buttons can be redefined by the user.) xix 1 _________________________________________________________________ Overview of OpenVMS AXP Version 1.5 This chapter provides a brief overview of the differences between OpenVMS AXP Version 1.5 and OpenVMS AXP Version 1.0. It also describes how to report problems found with the operating system. 1.1 Differences Between OpenVMS AXP Version 1.5 and Version 1.0 V1.5 OpenVMS AXP Version 1.0 is based on OpenVMS VAX Version 5.4-2 and contains most OpenVMS VAX features. However, OpenVMS VAX functionality was not complete in Version 1.0. OpenVMS AXP Version 1.5 is the second release of the AXP operating system software for Digital's 64-bit Alpha AXP architecture. In keeping with the OpenVMS AXP program plan, the goal of Version 1.5 is to deliver additional functionality so that OpenVMS AXP eventually achieves feature parity with OpenVMS VAX. Version 1.5 adds more of the VAX functionality to the OpenVMS AXP operating system. The following items are some of the many new or changed items for Version 1.5: o VMScluster support, including dual-architecture configuration and satellite booting - Chapter 8 o Symmetric multiprocessing support - Section 4.21 o New batch and print queueing system - Chapter 6 o DECdtm, the OpenVMS distributed transaction manager - Section 4.10 o InfoServer and Initial System Load (ISL) support - Section 2.3.1 o ISO 9660 support - Section 4.17.1 o X terminal support - Section 4.29 o Virtual I/O cache - Section 4.25 1-1 Overview of OpenVMS AXP Version 1.5 1.1 Differences Between OpenVMS AXP Version 1.5 and Version 1.0 o Calling standard change between native and translated images - Section 5.3 o Changes to system services - Section 5.21 o AUTOGEN and system parameter enhancements - Section 4.5 o DECnet changes - Section 4.8 o New condition code in the executive for cross-mode page- read errors - Section 5.8.2 o Changes to the MACRO-32 Compiler for OpenVMS AXP - Section 5.14 o Upgrade and installation considerations - Section 2.3 o XCDAC adapter storage-only support - Section 4.28 1.2 Unsupported Components and Functionality V1.5 The following components and related products are not supported on OpenVMS AXP Version 1.5: o DDCMP connections for DECnet communications o DECnet host-based routing (Version 1.5 supports cluster alias routing only) o Distributed Name Service (DNS) o OpenVMS Record Management Services (RMS) Journaling o User-written device drivers o OpenVMS Volume Shadowing When OpenVMS AXP Version 1.0 was released, a number of layered products from Digital Equipment Corporation and other vendors were not yet available. Your Digital representative can provide you with a current list of the Digital layered products that are available for AXP computers. If you copy existing startup procedures from one of your VAX computers to an AXP system disk, you must comment out the calls to the startup procedures of currently unavailable layered products. 1-2 Overview of OpenVMS AXP Version 1.5 1.3 How to Report Problems Found in OpenVMS AXP 1.3 How to Report Problems Found in OpenVMS AXP If you encounter a problem while using the operating system, review the Software Product Description (SPD) and Warranty Addendum for an explanation of the warranty. If you encounter a problem during the warranty period, either call Digital if your software contract or warranty agreement includes telephone support or follow alternate instructions provided by Digital for reporting problems. 1-3 2 _________________________________________________________________ Running OpenVMS AXP This chapter discusses aspects of the AXP operating system environment, including installation and upgrade capabilities, running DECwindows software, and using AXP computers. 2.1 Release Notes Specific to OpenVMS AXP Version 1.5 The release notes in this document are cumulative from OpenVMS AXP Version 1.0. In this chapter, the following sections contain release notes that pertain specifically to OpenVMS AXP Version 1.5: o The AXP environment - Section 2.2 o Installation and upgrade considerations - Section 2.3 o InfoServer and Initial System Load (ISL) support available - Section 2.3.1 o Effect of upgrade procedure on queue database - Section 2.3.4 o DECram Version 1.1 must be reinstalled after upgrading OpenVMS AXP - Section 2.3.5 o Conversational bootstrap problem fixed - Section 2.4 o Privileged Architecture Library code (PALcode) version checking enabled - Section 2.6 o Using DECW$TAILOR to add or remove DECwindows files - Section 2.7.3 o Display server changes - Section 2.7.4 o TURBOchannel PMAZB adapter support - Section 2.7.6 o Running OpenVMS AXP on a DEC 3000 Model 300 series AXP computer - Section 2.8 2-1 Running OpenVMS AXP 2.1 Release Notes Specific to OpenVMS AXP Version 1.5 o Problem when XDELTA is included when you boot from a SCSI disk - Section 2.12.3 o Problem with PNDRIVER and setting of SCSSYSTEMID system parameter - Section 2.13 2.2 AXP Environment V1.5 See the OpenVMS AXP Software Product Description (SPD 41.87.xx) for a description of the OpenVMS AXP operating system and supported hardware. Refer to the hardware manuals supplied with your AXP computer for detailed information about system hardware installation and operation. 2.3 Installation and Upgrade V1.5 OpenVMS AXP Version 1.5 provides installation and upgrade capabilities. For complete instructions on installing or upgrading the OpenVMS AXP operating system for Version 1.5, see the OpenVMS AXP Version 1.5 Upgrade and Installation Manual. That manual contains installation, upgrade, and operations information about AXP computers that run AXP operating system software. The following sections contain important information about the installation and upgrade procedures. 2.3.1 InfoServer and Initial System Load (ISL) Support Available V1.5 Version 1.5 provides Initial System Load (ISL) capabilities through the InfoServer. The InfoServer is a general-purpose disk storage server that allows you to use the distribution compact disc to install the operating system on remote client systems connected to the same LAN (local area network). See the OpenVMS AXP Version 1.5 Upgrade and Installation Manual for information about installing OpenVMS AXP using the InfoServer. Note, however, that you cannot perform an upgrade using the InfoServer. 2-2 Running OpenVMS AXP 2.3 Installation and Upgrade 2.3.2 Installation Procedure - Spurious Message No Longer Appears V1.5 During Phase 1 of the OpenVMS AXP Version 1.0 installation procedure, the following error message was displayed: . . . ... OPCOM AUDIT SERVER startup .... %STDRV-I-STARTUP, VMS Startup begun ... %DCL-W-IVVERB, unrecognized command .. \YOU\ The problem that caused the spurious message has been fixed. This message is not displayed on OpenVMS AXP Version 1.5. 2.3.3 Upgrade Procedure Requirement V1.5 During the upgrade procedure, you are prompted to specify the device on which the upgrade should be applied, as shown in the following example: * Device on which to install OpenVMS Alpha AXP (ddcu:): Although the prompt implies that you have a choice, you must specify the system disk. If you attempt to define a nonsystem disk for the installation, the following message is displayed: You may not perform an upgrade on a device other than the existing system disk. * Do you wish to re-specify the target (Y/N)? After you answer yes, you are prompted to enter the name of the system disk. 2.3.4 Effect of Upgrade Procedure on Queue Database V1.5 The OpenVMS AXP Version 1.5 upgrade procedure deletes your queue database. After completing the upgrade, you must perform the following steps to use your queuing system: 1. Start the queue manager, and create a queue database in the new format. For instructions, see Section 6.3.4. 2-3 Running OpenVMS AXP 2.3 Installation and Upgrade 2. Reinitialize any queues, and redefine any forms and characteristics you use with your queuing system. For instructions, see Chapter 13 of the OpenVMS System Manager's Manual. 3. Resubmit any outstanding jobs that were present in the queues before the upgrade. For more information about the batch and print queuing system, see Chapter 6. 2.3.5 DECram Version 1.1 Must Be Reinstalled After OpenVMS AXP Upgrade V1.5 You must reinstall the DECram Version 1.1 layered product after upgrading your OpenVMS AXP Version 1.0 system to Version 1.5. 2.3.6 Product Authorization Key Installation V1.5 If you registered OpenVMS AXP and DECnet for OpenVMS AXP Product Authorization Keys (PAKs) on Version 1.0, you need not install new license PAKs on Version 1.5. 2.4 Conversational Bootstrap - Problem Fixed V1.5 During a conversational bootstrap, you can instruct SYSBOOT to use an alternate system parameter file. However, in OpenVMS AXP Version 1.0, a known problem with the parameter handling code sometimes resulted in a boot failure. This problem is fixed in OpenVMS AXP Version 1.5. 2.5 Compatibility with Translated Programs and Images V1.5 Digital supports translation of programs from VAX VMS Version 4.0 through Version 5.4-3. Although the VAX Environment Software Translator (VEST) translates Version 5.5 images, OpenVMS AXP Version 1.5 might not provide the necessary run-time support because the translated libraries are based on Version 5.4-3. In this case, the translated VAX VMS Version 5.5 image may get an identification mismatch at run time. 2-4 Running OpenVMS AXP Privileged Architecture Library Code (PALcode) Version Checking Enabled 2.6 Privileged Architecture Library Code (PALcode) Version Checking Enabled V1.5 If your computer console does not have the specified minimum version of the Privileged Architecture Library code (PALcode), you may not be able to boot your system during the installation or upgrade procedure. Digital recommends, therefore, that you do the following before performing an installation or upgrade: 1. At the console prompt (>>>) on your running AXP system, enter the SHOW CONFIGURATION command (or SHOW PAL on DEC 7000 and DEC 10000 AXP series systems). The system display indicates which version of PALcode is running. 2. Refer to the cover letter that accompanied your kit for the absolute (required) minimum and recommended minimum versions of PALcode for your AXP computer. 3. Proceed as follows, depending on which version of PALcode your system is currently running: o If the PALcode is below the absolute (required) minimum, upgrade your console to the required minimum version (or higher) listed for your AXP computer in the cover letter that accompanied your kit. You can accomplish this task either by following directions contained in the hardware manuals that came with your computer or by contacting your Digital representative. _______________________ Caution _______________________ If you do not upgrade your console to the absolute (required) minimum PALcode, you receive a fatal error message similar to the following when you attempt to boot your system: APB-F-PALREV, PALcode revision 5.15 is below required minimum of 5.25 UNABLE TO CONTINUE ______________________________________________________ o If the PALcode is below the recommended minimum, you receive a warning message similar to the following: APB-W-PALREV, PALcode revision 5.25 is below recommended minimum of 5.39 2-5 Running OpenVMS AXP 2.6 Privileged Architecture Library Code (PALcode) Version Checking Enabled Although you are still able to boot your system, you should review the cover letter and check with your Digital representative to determine how you should upgrade your console to the recommended minimum version of the PALcode before installing or upgrading the operating system. 2.7 Running OpenVMS AXP Using a DEC 3000 Series AXP Computer V1.0 The following sections discuss features and configuration tasks that are common to the DEC 3000 series AXP computers. Refer to Section 2.8 for additional information that is specific to the DEC 3000 Model 300 series AXP computer. Refer to Section 2.9 for additional information that is specific to the DEC 3000 Model 400 AXP computer. Refer to Section 2.10 for additional information that is specific to the DEC 3000 Model 500 AXP computer. 2.7.1 Running DECwindows V1.0 Currently, the DEC 3000 series AXP workstations are the only AXP hardware platforms that are able to display graphics. Support for the DECwindows Motif for OpenVMS AXP layered product is provided by: o The DECwindows X11 display server, which is an optional part of the AXP kit. This optional part can be selected during the AXP installation procedure, when you are asked if you want to provide optional DECwindows workstation support. o The DECwindows Motif for OpenVMS AXP layered product, which provides programming and application support. This layered product must be installed separately. To run DECwindows Motif for OpenVMS AXP applications locally on the DEC 3000 series AXP computers, you must select the option for the DECwindows X11 display server during the AXP installation procedure and also install the DECwindows Motif for OpenVMS AXP layered product. See the DECwindows Motif for OpenVMS AXP Version 1.1 Installation Guide for information about installing the DECwindows Motif for OpenVMS AXP Version 1.1 layered product. 2-6 Running OpenVMS AXP 2.7 Running OpenVMS AXP Using a DEC 3000 Series AXP Computer 2.7.2 DECwindows Support for OpenVMS AXP Version 1.0 V1.0 Note the following about required and optional DECwindows save sets: o The required DECwindows save set included with the operating system supplies the base support you need to run the DECwindows Motif for OpenVMS AXP layered product, which you install separately. o The optional DECwindows workstation support save set that you can choose during the AXP installation is required if you want to run the windowing software on a DEC 3000 series AXP workstation (provided you also install the separate DECwindows Motif for OpenVMS AXP layered product). o The required DECwindows save set plus the optional DECwindows workstation support save set offered with the operating system does not constitute complete DECwindows support. You must install the separate DECwindows Motif for OpenVMS AXP layered product to obtain complete support. Note the following as well: o The DECwindows Motif for OpenVMS AXP layered product supports both the Motif and XUI environments. o If you want to customize aspects of the DECwindows environment, see the appendix in the DECwindows Motif for OpenVMS AXP Version 1.1 Installation Guide for instructions. 2.7.3 Using DECW$TAILOR to Add or Remove DECwindows Files V1.5 For OpenVMS AXP Version 1.5, you can use DECW$TAILOR to add or remove some or all DECwindows files from your system disk. See the OpenVMS AXP Version 1.5 Upgrade and Installation Manual for information about when and how you can use this feature. ________________________ Note ________________________ To add or remove files included with the separately installable DECwindows Motif for OpenVMS AXP layered product, refer to the VMS DECwindows Motif Installation Guide. With the exception of the required 2-7 Running OpenVMS AXP 2.7 Running OpenVMS AXP Using a DEC 3000 Series AXP Computer files, DECW$TAILOR adds or removes only the DECwindows support files that are supplied in the OpenVMS AXP kit. ______________________________________________________ 2.7.4 DECwindows X11 Display Server and Driver V1.5 The DECwindows X11 display server, including device drivers and fonts, can be selected for installation during the AXP installation procedure. The display server implementation is based upon the MIT X Window System Version 11 Release 5 (R5) display server. The following display server extensions are supported and have been tested: o Adobe-DPS-Extension - Display PostScript extension o DEC-XTRAP - X protocol trap extension o MIT-SUNDRY-NONSTANDARD - MIT miscellaneous extension o Multi-Buffering - Multibuffering extension o SHAPE - Nonrectangular windows extension o XIE - X imaging extension 2.7.4.1 New Font Formats V1.0 The display server supports the portable compiled format (PCF) that was introduced with the MIT R5 display server. PCF is a modified font format that includes bit/byte ordering and alignment information as part of the font data and allows for vendor-independent font support. All fonts currently provided with the DECwindows display server are available in PCF format. Applications do not have to be modified in order to use the PCF fonts. 2.7.4.2 Font Compiler - Restrictions V1.0 The DECwindows X11 display server includes a font compiler that enables programmers to convert an ASCII bitmap distribution format (BDF) into binary portable compiled format (PCF). The server uses a PCF file to display a font. Note that the DECwindows X11 display server for the OpenVMS VAX font compiler's MINBBOX and REPORT qualifiers are not supported in OpenVMS AXP Version 1.0. 2-8 Running OpenVMS AXP 2.7 Running OpenVMS AXP Using a DEC 3000 Series AXP Computer To invoke the font compiler, use the following format: FONT filespec [ /OUTPUT[=filename] ] The filename parameter specifies the PCF file to be converted. A file name is required. The default value of the optional file type is .DECW$BDF. The /OUTPUT qualifier specifies the file name and file type of the resulting PCF file. The default output file name is the file name of the BDF file being converted. The default output PCF file type is .PCF. Compiler output consists of a header file that contains font information, character metrics, amd the image of each character in the font. 2.7.4.3 Font Server Support V1.5 The R5 display server includes a font server renderer that supports the use of font servers to access fonts. This allows font files to be distributed on systems other than the system on which the display server is running. 2-9 Running OpenVMS AXP 2.7 Running OpenVMS AXP Using a DEC 3000 Series AXP Computer You can add font servers to the font path by defining the symbol DECW$FONT_SERVERS in the site-specific server setup file SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM. Depending on the transport type, use either of the following: o To add support for the TCP transport, specify TCP as the network connection type that will communicate with the font server. Replace node with the Internet node name. Specify the TCP/IP port number for port_number, as shown in the following example: $ DECW$FONT_SERVERS == "TCP/node::port_number" o To add support for the DECnet transport, specify DECNET as the network connection type that will communicate with the font server. Replace node with the DECnet node name. Specify the DECnet object name for network_object. $ DECW$FONT_SERVERS == "DECNET/node::network_object" Multiple font servers can be added by defining the symbol as a comma-separated list. The symbol is not case sensitive. 2.7.4.4 Support Added for Scalable Outline Fonts V1.5 The Version 1.5 DECwindows server supports scalable outline fonts. You can select an arbitrary size for any of these fonts, and they will be scaled as necessary; otherwise, they are treated as standard bitmapped fonts. The following scalable fonts are included: o Adobe-Courier-Bold-I-Normal-0-0-0-0-P-0-ISO8859-1 o Adobe-Courier-Bold-R-Normal-0-0-0-0-P-0-ISO8859-1 o Adobe-Courier-Medium-I-Normal-0-0-0-0-P-0-ISO8859-1 o Adobe-Courier-Medium-R-Normal-0-0-0-0-P-0-ISO8859-1 o Bitstream-Charter-Bold-I-Normal-0-0-0-0-P-0-ISO8859-1 o Bitstream-Charter-Bold-R-Normal-0-0-0-0-P-0-ISO8859-1 o Bitstream-Charter-Medium-I-Normal-0-0-0-0-P-0-ISO8859-1 o Bitstream-Charter-Medium-R-Normal-0-0-0-0-P-0-ISO8859-1 o Bitstream-Courier-Bold-I-Normal-0-0-0-0-M-0-ISO8859-1 o Bitstream-Courier-Bold-R-Normal-0-0-0-0-M-0-ISO8859-1 2-10 Running OpenVMS AXP 2.7 Running OpenVMS AXP Using a DEC 3000 Series AXP Computer o Bitstream-Courier-Medium-I-Normal-0-0-0-0-M-0-ISO8859-1 o Bitstream-Courier-Medium-R-Normal-0-0-0-0-M-0-ISO8859-1 o Bitstream-Courier-Medium-R-Normal-0-0-0-0-M-0-ISO8859-1 Font names that contain zeros in the size fields, such as those listed above, indicate scalable fonts. When selecting any of the fonts listed above, supply either the pixel size (the first zero in the size field) or the decipoint size (the second zero in the size field) to obtain the desired font size. 2-11 Running OpenVMS AXP 2.7 Running OpenVMS AXP Using a DEC 3000 Series AXP Computer For example, the following font specifications both select a 12-point Courier font: Size in pixels | Adobe-Courier-Medium-R-Normal--17-*-*-*-p-*-ISO8859-1 Adobe-Courier-Medium-R-Normal--*-120-*-*-p-*-ISO8859-1 | Size in decipoints The pixel size of a 12-point font at 100 dots per inch is 17 (120*100/720). If you specify values for both the pixel size and the decipoint size and those values are incompatible, no font is selected. If you omit both the pixel size and the decipoint size, a default size of 12- point is selected. The private display server setup file SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE contains information about how to customize a private display server command procedure for your environment. Rename the SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE to a command procedure file type (.COM). Edit the resulting SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM command procedure, and define the symbol DECW$MONITOR_DENSITY to be a value that represents the desired screen resolution. The symbol's value is rounded to either 75 or 100 dots per inch and is used to fill in the remaining fields in the font name. The default value is 100 dots per inch. For more information about specifying font names, see the VMS DECwindows Motif Guide to Application Programming. 2.7.4.5 DECwindows Transport V1.5 The DECwindows transport has been modified to correct disconnect problems. Under certain conditions, pending asynchronous system traps (ASTs) were sent after the transport cleanup process had begun. As a result, the AST attempted to access data that had already been deallocated, which in turn caused access violations or system failures. One solution, queuing the CLOSE_AND_DEALLOCATE_AST AST from the DECW$$TCPIP_CLOSE routine, was an incomplete one. The CLOSE_AND_DEALLOCATE_AST AST was queued to the current 2-12 Running OpenVMS AXP 2.7 Running OpenVMS AXP Using a DEC 3000 Series AXP Computer operation mode (executive), and this AST could be sent before pending user-mode ASTs. The Transport Function Table (XTFT) data structure has been modified, and a new common routine has been added. The XTFT data structure was increased by 1 longword to provide an additional routine entry, XTFT$A_DISCONNECT. The new common routine is DECW$XPORT_DISCONNECT. Digital recommends that you implement the following modifications if you have written your own DECwindows transport. These modifications are based on the sample transport implementation in the VMS DECwindows Transport Manual. ________________________ Note ________________________ You must recompile any user-written specific transport that uses the XTFT$C_LENGTH constant. ______________________________________________________ o Create a new routine to remove the cleanup instructions from the CLOSE_AND_DEALLOCATE_AST AST. Store this new routine address in the XTFT data structure at offset XTFT$ADISCONNECT. The XTFT is initialized in the DECW$TRANSPORT_INIT routine. This new routine takes the IXTCC parameter. o From DECW$$TCPIP_CLOSE, queue CLOSE_AND_DEALLOCATE_AST as a user-mode AST. o Inside CLOSE_AND_DEALLOCATE_AST, call the Common Transport routine DECW$XPORT_DISCONNECT, passing an IXTCC parameter. The DECW$XPORT_DISCONNECT routine calls the routine stored in XTFT[XTFT$A_DISCONNECT]. By dispatching the disconnect routine through the Common Transport layer, the process changes to executive mode as required to deallocate data structures. Restrictions The following restrictions apply to the DECwindows transport: o Although the VMS DECwindows Transport Manual does not state it, routines in customer-supplied DECwindows transports must execute in executive mode. 2-13 Running OpenVMS AXP 2.7 Running OpenVMS AXP Using a DEC 3000 Series AXP Computer If you are writing your own transport layer, the transport-specific routines must be executable in executive mode. This restriction applies to both AXP and VAX DECwindows transport routines. o DECwindows DECnet, TCP/IP, and local transport display server options are available. o Even though your application disables user-mode ASTs before calling XLIB, you may still receive user-mode ASTs in some circumstances. (This is a problem with XLIB.) 2.7.4.6 Alternate Window System Console Provides 24-Line Console Window V1.5 Normally, when you press the halt button and continue system operation, only six lines are displayed by the console at the top of the screen. This action minimizes console offscreen memory usage and allows maximum offscreen memory usage by the display server for pixmap and font glyph storage. This is a permanent restriction in the display server. When you turn on or reboot the system, the full console screen is displayed. However, in Version 1.5, an alternate window system console (also called a software console) is available. The software console provides a 24-line console window when the window system is running instead of the current 6-line window that is available through the firmware callbacks. Note that the software console destroys the display and does not use offscreen memory for its display area. As a result, when the software console window is removed, the server generates exposure events that redraw the display on the windows that were obscured by the console. The main benefit of exposure event generation is that approximately 153,600 bytes of offscreen memory are available to the server. However, the software console has the following limitations: 2-14 Running OpenVMS AXP 2.7 Running OpenVMS AXP Using a DEC 3000 Series AXP Computer o Windows with save unders (for example, Motif pulldown menus) are not correctly exposed when the console is removed. To work around this problem, either disable save unders or select the Refresh Window item in the Menus... option. o Input focus in the software console window might cause the Workspace menu to corrupt the display. o With the Motif window manager, new window creation can sometimes create the window over the software console window. (This does not happen with the XUI window manager.) Usually, you can correct these problems by pressing Ctrl/F2 twice to redraw the console area. To select the alternate window system console, set bit 8 (value 512) in the TTY_DEFPORT system parameter. Digital recommends that you use the System Management utility (SYSMAN) to modify system parameters. You can also set the TTY_DEFPORT system parameter during an interactive boot by using the command SET TTY_DEFPORT 512. 2.7.4.7 Known Problems V1.5 Oscillator selection on nonconsole monitors may be improperly initialized if the system is configured with multiple PMAGB-BA (HX) options and if the nonconsole monitors do not use the default oscillator. The VRT19-DA is one example of a monitor that does not use the default oscillator. The symptoms are a compressed screen with text shifted to the left and no flashing cursor on the lower left edge of the screen. Work around this problem by editing the SYS$MANAGER:SYSTARTUP_VMS.COM file and defining the following multivalued logicals: $ DEFINE/SYS/EXEC DECW$SERVER_MONITOR_RESET 0,1[,...] $ DEFINE/SYS/EXEC DECW$SERVER_MONITOR_SELECT 0,1[,...] Each value in the logical applies to a specific head (starting from screen 0). Specify a value for each head. Any value not provided is taken from the initial value. 2-15 Running OpenVMS AXP 2.7 Running OpenVMS AXP Using a DEC 3000 Series AXP Computer When set to a logical TRUE value, the RESET logical tells the X11 display server to unconditionally select the HX oscillator. A logical FALSE value for the RESET logical prevents the display server from altering the oscillator. A logical TRUE value for the SELECT logical selects the alternate oscillator (used by the VRT19-DA) and a logical FALSE value selects the standard oscillator (used by the VR320). This problem is caused by a firmware problem that Digital expects to fix in a future release. 2.7.4.8 Problems Fixed V1.5 The following problems found in OpenVMS AXP Version 1.0 have been fixed in this version: o When you halted the workstation and then continued system operation, the keyboard was sometimes not synchronized with the display server. For example, characters that you typed would not be entered correctly in the input focus window. o Occasionally, a vertical white bar showed up in the center of an icon. o When you positioned a window in the upper left corner of the screen and then slid the pointer up and down in the resize border area below the window menu button, you might have noticed flashing lines and bits that appeared and then immediately disappeared. This problem occurred only when the window was positioned in the upper left corner of the screen. o Occasionally the cursor remained visible after the screen saver had shut off the monitor display. o When you tried to create Calendar entries from the Day View dialog box and used the mouse to select a time slot, the text entry box was not always displayed completely. When you tried to type into the text entry box, the characters were not displayed. 2-16 Running OpenVMS AXP 2.7 Running OpenVMS AXP Using a DEC 3000 Series AXP Computer 2.7.4.9 Error Recovery V1.0 The display server contains a condition handler that intercepts problems (such as an access violation) that might otherwise cause the display server to stop. The condition handler tries to let the display server continue. When the condition handler intercepts a problem, it sends an implementation error to the client or disconnects the client or both. When the condition handler recovers from an error, the display server might lose resources, such as memory. Therefore, after a number (10) of these exceptions, the condition handler broadcasts a warning message to all users on the workstation indicating that the display server might be running in a degraded mode and suggesting that the display server be restarted. If you see messages like this, you should restart the display server at the next convenient opportunity. Enter the following command from a privileged account to restart the display server: $ @SYS$MANAGER:DECW$STARTUP RESTART 2.7.4.10 Reporting Errors V1.0 The file SYS$MANAGER:DECW$SERVER_0_ERROR.LOG contains display server startup and operational error information. Use the contents of this file when you submit problem reports concerning the display server. See Section 1.3 for information about reporting problems found with the DECwindows X11 display server. 2.7.5 Multihead Configurations V1.0 A multihead configuration consists of a single DEC 3000 series AXP workstation that supports multiple graphics options. A graphics option consists of a graphics controller and a graphics display interface (monitor). A DEC 3000 series AXP system will be automatically configured for multihead use if you rename the private display server setup file from a template file type (.TEMPLATE) to a command procedure file type (.COM). Rename this file after installing the DECwindows X11 display server and after logging on to your system. 2-17 Running OpenVMS AXP 2.7 Running OpenVMS AXP Using a DEC 3000 Series AXP Computer To rename the private display server setup file, enter the following command: $ RENAME SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE _To: SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM The display server loads the private display server setup command procedure on startup or restart. The private display server setup file always configures the console as the primary head (screen 0). Note that the firmware always selects the device with the lowest TURBOchannel slot address found in the system as the console device. After you have renamed the private display server setup file, use the following command to restart the display server: $ @SYS$STARTUP:DECW$STARTUP RESTART 2.7.6 TURBOchannel PMAZB Adapter Support V1.5 OpenVMS AXP Version 1.5 contains support for the PMAZB TURBOchannel adapter. The PMAZB adapter is software- compatible with the integrated Small Computer System Interface (SCSI) ports on the DEC 3000 series AXP systems. The DEC 3000 series AXP system consoles implement the SHOW CONFIGURATION console command, which displays information about the TURBOchannel options and the built-in adapters in the system. When a PMAZB adapter is installed in the TURBOchannel, the SHOW CONFIGURATION command displays the "PMAZB-AA" string, the TURBOchannel slot number, and the device status. The DEC 3000 series AXP consoles also implement the SHOW DEVICE command, which displays information about the devices in the system. Because the integrated SCSI adapter is built into every DEC 3000 series AXP system, the SHOW DEVICE console command can display the SCSI devices connected to the integrated SCSI ports. However, the SHOW DEVICE console command cannot display the SCSI devices connected to the PMAZB SCSI ports. 2-18 Running OpenVMS AXP 2.7 Running OpenVMS AXP Using a DEC 3000 Series AXP Computer To make the console display the devices connected to the PMAZB SCSI ports, enter the following command at the console prompt, where n is the TURBOchannel slot number in which the PMAZB adapter is installed: >>> test tcn cnfg This command displays the devices that are connected to each SCSI port of the PMAZB adapter. The device controller letters are either A or B, based on the PMAZB ports to which the devices are connected. Do not confuse these devices with any DKAxxx or DKBxxx devices displayed by the SHOW DEVICE command, which shows SCSI devices on the integrated SCSI ports only. See the OpenVMS AXP Version 1.5 Upgrade and Installation Manual for information about how to boot from a device connected to a PMAZB adapter. OpenVMS AXP does not distinguish between the PMAZB adapter and the integrated SCSI adapter. The operating system views them as identical adapters. Because OpenVMS AXP searches for I/O adapters in backplane slot number order, device controller letters are assigned that correspond to the backplane order of the TURBOchannel options, followed by the integrated adapters. This is different from console SCSI device naming, which always designates SCSI devices on the integrated SCSI ports as either "A" or "B" port devices. For example, on a DEC 3000 Model 500 AXP system with no TURBOchannel options installed, OpenVMS AXP names the integrated SCSI ports PKA0 and PKB0, and the devices connected to the ports inherit the controller letter from the port controller letter (A or B). In this case, the OpenVMS AXP SCSI device naming matches the console SCSI device naming. However, if a PMAZB adapter is installed in the TURBOchannel, OpenVMS AXP names the PMAZB SCSI ports PKA0 and PKB0 and names the integrated SCSI ports PKC0 and PKD0. The devices connected to the ports inherit the controller letter from the port controller letter (A, B, C, or D). 2-19 Running OpenVMS AXP 2.8 Running OpenVMS AXP Using a DEC 3000 Model 300 Series AXP Computer 2.8 Running OpenVMS AXP Using a DEC 3000 Model 300 Series AXP Computer V1.5 See the DEC 3000 AXP Model 300 Owner's Guide for information about using and maintaining the DEC 3000 Model 300 series AXP computer. Refer to the OpenVMS AXP Software Product Description (SPD 41.87.xx) for the DEC 3000 Model 300 series AXP system configurations that are supported by the operating system. 2.9 Running OpenVMS AXP Using a DEC 3000 Model 400 AXP Computer V1.0 See the DEC 3000 AXP Model 400 Owner's Guide for information about using and maintaining the DEC 3000 Model 400 AXP computer. Refer to the OpenVMS AXP Software Product Description (SPD 41.87.xx) for the DEC 3000 Model 400 AXP system configurations that are supported by the operating system. 2.10 Running OpenVMS AXP Using a DEC 3000 Model 500 AXP Computer V1.0 See the DEC 3000 AXP Model 500 Owner's Guide for information about using and maintaining the DEC 3000 Model 500 AXP computer. Refer to the OpenVMS AXP Software Product Description (SPD 41.87.xx) for the DEC 3000 Model 500 AXP system configurations that are supported by the operating system. 2.11 Running OpenVMS AXP Using a DEC 4000 Series AXP Computer V1.0 See the DEC 4000 AXP Owner's Guide for more information about using and maintaining the DEC 4000 series AXP computer. Refer to the OpenVMS AXP Software Product Description (SPD 41.87.xx) for the DEC 4000 series AXP system configurations that are supported by the operating system. Note that the ANALYZE/ERROR command does not format error log entries resulting from DSSI devices. This problem will be corrected in a future release of the operating system. 2-20 Running OpenVMS AXP 2.11 Running OpenVMS AXP Using a DEC 4000 Series AXP Computer The second console terminal port (OPA1:) is now automatically configured during system startup by the SYSMAN autoconfiguration utility. You no longer need to manually configure the port with the SYSMAN CONNECT command. The default baud rate for the port is determined by the console environment variable tta1_baud. To change the speed of the port, either reset the console environment variable or issue the following command: $ SET TERMINAL/PERMANENT/SPEED=xxxx OPA1: 2.12 Running OpenVMS AXP Using a DEC 7000 Model 600 AXP Computer V1.0 For information about using and maintaining the DEC 7000 Model 600 AXP computer, see the DEC 7000 AXP Model 600 Owner's Guide. Refer to the OpenVMS AXP Software Product Description (SPD 41.87.xx) for the DEC 7000 Model 600 AXP series system configurations that are supported by the operating system. 2.12.1 Local DIGITAL Storage Architecture (DSA) Disk and Tape Support V1.0 The operating system provides support for local DSA disk and tape devices on the DEC 7000 Model 600 AXP computer. Support is provided with the KDM70 on the XMI bus. However, you must obtain the latest KDM microcode, which supports the AXP 8-kilobyte page size, from your Digital representative. See the OpenVMS AXP Software Product Description (SPD 41.87.xx) for information about devices and peripherals that are supported by the operating system. 2.12.2 SCSI Support V1.0 The host ID is 7 for ports A and B of the KZMSA-AB SCSI controller. 2-21 Running OpenVMS AXP 2.12 Running OpenVMS AXP Using a DEC 7000 Model 600 AXP Computer 2.12.3 Booting from a SCSI Disk - Problem When XDELTA Is Included V1.5 A problem in Version 1.5 results in an error halt on the DEC 7000 Model 600 AXP SMP computer when the following conditions are met: o Your system boots from a SCSI disk. o You issue a boot command that instructs the system to include XDELTA at boot time and to stop at the EXEC_INIT breakpoints. The boot command would be similar to that shown in the following example. In the example, n is the root from which you boot, which is normally 0. The boot command qualifier value of 6 indicates that bits 1 and 2 should be set. >>> boot -flag n,6 dev This problem results in a kernel stack not valid error halt on a secondary CPU after you proceed from the second EXEC_ INIT breakpoint using ;P. To work around the problem, you must set also bit 17 in the boot flags, as shown in the following example: >>> boot -flag n,20007 dev In the example, the boot command qualifier value of 20007 indicates that bits 1, 2, and 17 will be set. Setting bit 17 avoids the kernel stack not valid error halt. It also causes a subset of the verbose boot messages to be displayed during the boot process. This problem only occurs when a system boots from a SCSI disk and the boot command instructs the system to include XDELTA and to stop at the EXEC_INIT breakpoints. If the boot command includes XDELTA but does not specify stopping at the EXEC_INIT breakpoints, the problem does not occur. The problem does not occur when a system boots from either a KDM70-based disk or from a CI based disk. 2-22 Running OpenVMS AXP 2.13 PNDRIVER and Setting of SCSSYSTEMID System Parameter - Problem 2.13 PNDRIVER and Setting of SCSSYSTEMID System Parameter - Problem V1.5 If you are booting a new system disk and the value of the SCSSYSTEMID system parameter is 0, PNDRIVER receives an access violation. As a result, the system hangs. To work around this problem, set the SCSSYSTEMID system parameter to a nonzero value. Digital expects to fix this problem with PNDRIVER in a future release of OpenVMS AXP. 2.14 SCSI Disk Class Driver (DKDRIVER) - Restriction V1.0 The SCSI disk class driver (DKDRIVER) does not support data check operations for OpenVMS AXP Version 1.0. The comparison operation invoked by the IO$M_DATACHECK modifier, the IO$_WRITECHECK function code, and other requests for data check support, always indicates success. Data check functionality will be included in a future release of the operating system. This restriction applies to all AXP hardware platforms. 2-23 3 _________________________________________________________________ General User-Level Release Notes This chapter contains information that is of interest to all users of the OpenVMS AXP operating system. It includes information about commonly used utilities, text processing utilities, and user-environment testing. 3.1 Release Notes Specific to OpenVMS AXP Version 1.5 The release notes in this document are cumulative from OpenVMS AXP Version 1.0. In this chapter, the following sections contain general user release notes that pertain specifically to OpenVMS AXP Version 1.5: o Problem with APPEND/PROTECTION and COPY/PROTECTION commands fixed - Section 3.2.1 o EDT editor becomes obsolete in next version of OpenVMS AXP - Section 3.2.2.1 o Online help corrections for the EDIT command - Section 3.2.2.2 o EDIT command problem fixed - Section 3.2.2.3 o Problem with SET PROCESS/SUSPEND=KERNEL/ID= command in a cluster environment - Section 3.2.3 o Sort/Merge utility changes - Section 3.6 o Translated TECO editor now available - Section 3.2.2.4 o UETP problem fixed - Section 3.7 In addition, also see Chapter 6 for general user-level information related to the new batch and print queueing system. 3-1 General User-Level Release Notes 3.2 DCL Commands and Utilities 3.2 DCL Commands and Utilities This section contains information about DCL commands and utilities. 3.2.1 APPEND/PROTECTION and COPY/PROTECTION Commands - Problem Fixed V1.5 In Version 1.0, when you used the APPEND/PROTECTION command or the COPY/PROTECTION command and specified an output file's ownership parameter as world (W) and the access parameter as delete (D), the protection attributes of world and delete were set correctly. However, the default protection for the ownership parameter group (G) was inadvertantly modified to allow access of read (R), write (W), execute (E), and delete (D). This problem has been fixed in OpenVMS AXP Version 1.5. 3.2.2 EDIT Command The following sections apply to the EDIT command. 3.2.2.1 Change in Default Editor V1.5 The default editor for the EDIT command has been changed to TPU from EDT. Therefore, when you enter the EDIT command, the Extensible Versatile Editor (EVE) is invoked rather than the EDT editor. ________________________ Note ________________________ The EDT editor is still included as part of the operating system. However, in the next version of OpenVMS AXP, the EDT editor and callable EDT will become obsolete. In the interest of upward compatibility, the EDT editor and callable EDT will be provided, but without support, with OpenVMS AXP. Digital urges EDT users to migrate to EVE at their earliest convenience. ______________________________________________________ This change was made to provide better system performance. TPU is a native image on AXP systems, whereas the EDT editor is a translated image. 3-2 General User-Level Release Notes 3.2 DCL Commands and Utilities The EDIT command now invokes TPU with the EVE section file. Please see Section 3.3 for DECTPU and EVE release notes. See the Guide to the DEC Text Processing Utility and the OpenVMS User's Manual for more information about DECTPU and EVE. Retaining the EDT Editor To continue using the EDT editor, define the following symbol interactively or in your login command procedure: $ EDIT :== EDIT/EDT This symbol overrides the default and causes the EDIT command to invoke the EDT editor instead of EVE. DCL Command Procedures and the EDIT Command Verify that the /EDT qualifier is present in any DCL command procedure that relies on EDT. Any procedure that uses the EDIT command without the /EDT qualifier will fail because this verb now invokes TPU with the TPU$SECTION section file. (By default, this section file is EVE.) EVE and the EDT Keypad In EVE, you can select an EDT-like keypad by defining the AXP logical name EVE$KEYPAD to be EDT. See Section 7.3.2 for details about how to do this at either the process level or system level. System managers can find an example of how to define EVE$KEYPAD at the system level in the file SYS$STARTUP:SYLOGICALS.TEMPLATE. 3.2.2.2 Online Help Corrections V1.5 On OpenVMS AXP Version 1.0, online help for the EDIT/EDT command assumed that EDT was the default editor. (TPU is the default editor on the OpenVMS AXP operating system.) As a result, the /EDT qualifier was omitted from the format line and from all of the examples. To correct this, the Version 1.5 online help has been revised by adding the /EDT qualifier in the format line and in all examples under EDIT/EDT help. 3-3 General User-Level Release Notes 3.2 DCL Commands and Utilities 3.2.2.3 Problem Fixed V1.5 In OpenVMS AXP Version 1.0, when you entered the EDIT command from the system console, the following error message was returned: %TPU-E-NONANSICRT, SYS$INPUT must be supported CRT You had to enter the SET TERMINAL/INQUIRE command in order to work around the problem. This problem is fixed in OpenVMS AXP Version 1.5. 3.2.2.4 Translated TECO Editor Now Available V1.5 The translated TECO editor is now included in the OpenVMS AXP operating system. Invoke the translated TECO editor with the EDIT/TECO command, as described in the OpenVMS DCL Dictionary, or with traditional access methods. For detailed information on the use of TECO, see the PDP-11 TECO User's Guide. 3.2.3 SET PROCESS/SUSPEND=KERNEL/ID= Command in a Cluster Environment - Incorrect Behavior V1.5 When you issue the SET PROCESS/SUSPEND=KERNEL/ID= command in a cluster environment, the KERNEL keyword is ignored if the target process and the current process reside on different cluster nodes. As a result, process suspension is handled as if you had specified the SUPERVISOR keyword (the default). This is caused by a problem with the $SUSPND system service, as discussed in Section 5.21.7. Digital expects to fix this problem in a future version of OpenVMS AXP. 3.3 DECTPU and EVE Version 3.1 Notes V1.0 On AXP systems, the default editor is EVE. See Section 3.2.2.1 for information about this change in default editors. For additional information about DECTPU and EVE new features, enhancements, restrictions, and problems that have been fixed, see Chapter 7. 3-4 General User-Level Release Notes 3.3 DECTPU and EVE Version 3.1 Notes DECwindows Motif for OpenVMS AXP Operations from EVE in a DECterm Emulator When EVE is used in a DECterm emulator, the mouse buttons are handled and processed by the underlying TPU code. This allows you to define the mouse buttons and bind TPU code to them. If you want to perform normal DECwindows Motif for OpenVMS AXP cut and paste operations from the DECterm emulator in which EVE is executing, you must turn off TPU's mouse support. The following command, when used from within EVE, allows normal DECwindows Motif for OpenVMS AXP cut and paste operations to occur: Command: tpu set (mouse,off) This command can be entered interactively or added to an EVE initialization file. 3-5 General User-Level Release Notes 3.3 DECTPU and EVE Version 3.1 Notes If you want to switch between TPU mouse support and DECwindows Motif for OpenVMS AXP cut and paste operations, add the following two procedures to a TPU command file: procedure eve_mouse_off; set (mouse,off); endprocedure; procedure eve_mouse_on; set (mouse,on); endprocedure; After the two commands have been compiled, you can then enter the command Command: Mouse off or Command: Mouse on to toggle between TPU and DECwindows Motif for OpenVMS AXP mouse support. See the OpenVMS User's Manual for more information on how to add new EVE commands and define the mouse buttons. 3.4 Help Message Utility (MSGHLP) V1.0 Help Message (MSGHLP) is a versatile new utility that allows you to quickly access online descriptions of system messages from the DCL prompt on a character-cell terminal (including DECterm windows). Help Message displays message descriptions from the latest VMS messages documentation (the most recent version of the OpenVMS System Messages and Recovery Procedures Reference Manual plus any subsequent Release Notes). In addition, the Help Message database can optionally include other source files, such as user-supplied messages documentation. Some Help Message features are summarized here. For full details about using Help Message and the HELP/MESSAGE command and qualifiers, refer to the OpenVMS System Messages: Companion Guide for Help Message Users. In addition, the OpenVMS System Manager's Manual provides information about how the system manager can customize the Help Message database. 3-6 General User-Level Release Notes 3.4 Help Message Utility (MSGHLP) Features of Help Message Help Message features include the following: o By default, Help Message provides information on the status of the last executed DCL command. o Because Help Message preserves the value of $STATUS, you can incorporate the HELP/MESSAGE command into a command procedure to obtain additional information about errors. o You can access message descriptions by specifying the message identifier or other words from the message text. o You can access a message description by specifying the message's decimal or hexadecimal status value. o You can restrict or select messages to be output by specifying one or more facility names. o By selecting the messages you want and directing them to a file, you can create and print your own customized messages documentation. o You can define local and system-wide search paths for the Help Message database to customize the contents of the database and even include descriptions of your own messages, if desired. o Users with write access to Digital-supplied database files (usually the system manager) can further customize the Help Message database by adding or deleting messages or adding comments to Digital messages. ________________________ Note ________________________ Currently, user-supplied comments or additions to Digital-supplied .MSGHLP$DATA files will not be preserved through the next upgrade. However, your own .MSGHLP$DATA files are not affected by future releases. Note that you can reuse .MSGHLP files to insert your own messages into future Digital-supplied database files. Depending on the content of future databases, you might also be able to reuse some .MSGHLP files to insert comments to existing messages. ______________________________________________________ 3-7 General User-Level Release Notes 3.5 Mail Utility - Change in Default Editor 3.5 Mail Utility - Change in Default Editor V1.0 The default editor for the Mail utility has been changed to TPU from EDT. Therefore, when you enter the EDIT command in the Mail utility, the Extensible Versatile Editor (EVE) is invoked rather than the EDT editor. For more information about this change, see Section 3.2.2.1. See the OpenVMS User's Manual for information about selecting an editor. 3.6 Sort/Merge Utility V1.5 The Sort/Merge utility (SORT/MERGE) runs as a native AXP image. For Version 1.5, common data dictionary support is included. CDD/Repository is available on OpenVMS AXP. All user-visible functions and interfaces of SORT/MERGE are identical to OpenVMS VAX SORT/MERGE, with the following exceptions: o Support for IEEE S and T floating-point datatypes is now available. Two new qualifiers, S_FLOATING and T_ FLOATING, have been added for the /KEY qualifier to specify these datatypes, as shown in the following example: SORT /KEY=(POS:1,S_FLOATING) INFILE.DAT OUTFILE.DAT The qualifier S_FLOATING specifies S_FLOATING format data in the key field. The qualifier T_FLOATING specifies T_FLOATING format data in the key field. The SIZE parameter is optional. However, if SIZE is specified, it must be 4 for S_FLOATING or 8 for T_ FLOATING data. o SORT does not trap IEEE NaNs or Denormals. Instead, they are collated as follows: -NaN < -Infinity +NaN > +Infinity -Denormal < 0 but greater than any other negative number +Denormal > 0 but less than any other positive number o During the course of SORT/MERGE development, the specification file format changed from the VAX VMS Version 3 format to the current format. If you still have specification files that need to be converted from VAX VMS Version 3.0 format to the current format, you 3-8 General User-Level Release Notes 3.6 Sort/Merge Utility must use the SRTTRN.EXE utility on VAX VMS Version 4.0 through Version 6.0. SRTTRN is not provided on OpenVMS AXP. This is a permanent restriction. o The behavior for reporting an invalid digit in a decimal string input differs between VAX systems and AXP systems. On VAX systems, you receive a reserved operand fault and a message that the value has been converted to a valid decimal string digit. On AXP systems, there is no indication of an invalid decimal digit or that a conversion has occurred. AXP systems do not have a decimal string hardware instruction to generate such a fault. The decimal string arithmetic is emulated in software. The data is converted with a decimal string zero inserted for the invalid character for comparison purposes. However, the data in the output file remains identical to that in the input file. o When SORT creates an output file containing fixed- length records whose record lengths vary from those of the input records, the following warning message is issued the first time a record with a different length is written: %SORT-W-VAR_FIX, records may be truncated or padded in output file: device:[user_directory]filename.ext Previously, SORT issued an "invalid record size" error message for every input record that was truncated or padded on output. 3.7 UETP Ethernet Test - Problem Fixed V1.5 In Version 1.0, when you selected all UETP phases (the default) or the device phase subset, the UETP Ethernet test (UETUNAS00) failed. This problem has been fixed in Version 1.5. Refer to the OpenVMS AXP Version 1.5 Upgrade and Installation Manual for details about using UETP tests. 3-9 4 _________________________________________________________________ System Management Release Notes This chapter contains information that applies to system maintenance and management, performance management, and networking. 4.1 Release Notes Specific to OpenVMS AXP Version 1.5 The release notes in this document are cumulative from OpenVMS AXP Version 1.0. In this chapter, the following sections contain system management release notes that pertain specifically to OpenVMS AXP Version 1.5: o Accounting utility problem fixed - Section 4.2 o Modifications to the Analyze/Disk_Structure utility - Section 4.3 o AUTOGEN support added for installed resident images - Section 4.5.2 o BACKUP enhancements and restrictions - Section 4.6 o DECnet changes - Section 4.8 o Distributed Transaction Manager functionality available - Section 4.10 o Change to the DUMPSTYLE system parameter - Section 4.5.3.2 o New value for MULTIPROCESSING system parameter - Section 4.5.3.3 o FRU support added to the Error Log Report Formatter - Section 4.11 o Changes to the Install utility - Section 4.13 o ISO 9660 support added - Section 4.17.1 o Monitor utility - Section 4.16 4-1 System Management Release Notes 4.1 Release Notes Specific to OpenVMS AXP Version 1.5 o Security auditing restriction removed - Section 4.20 o Symmetric multiprocessing support available - Section 4.21 o Changes, problems, and a restriction that affect SYSMAN - Section 4.23 o VMSINSTAL checks process quotas - Section 4.26 o XCDAC adapter storage-only support available - Section 4.28 o X terminal support - Section 4.29 o Virtual I/O cache - Section 4.25 For additional information about system management features and tasks, refer to A Comparison of System Management on OpenVMS AXP and OpenVMS VAX. The Comparison is intended for experienced system managers who need to learn quickly how specific management tasks differ or remain the same on AXP and VAX computers. In addition, see Chapter 6 for system management information related to the new batch and print queueing system and Chapter 8 for system management information related to VMSclusters. 4.2 Accounting Utility - Problem Fixed V1.5 After you enter the following command, the user process should be returned to the DCL prompt if the Accounting utility finds no records that match the request: $ ACCOUNTING/SUMMARY/SINCE= When there are records to fit the request, the information returned is correct. However, in OpenVMS AXP Version 1.0, the following spurious message was displayed if no records matched the request: %DEBUG-F-NOMSG, Message number 00020B54 This problem has been fixed in Version 1.5. The spurious message no longer appears. 4-2 System Management Release Notes 4.3 Modifications to Analyze/Disk_Structure Utility 4.3 Modifications to Analyze/Disk_Structure Utility V1.5 The following two qualifiers have been added to the Analyze /Disk_Structure utility: o /ATTRIBUTES The /ATTRIBUTES qualifier determines if the Analyze /Disk_Structure utility repairs files containing erroneous settings in the record attributes section of their associated File Attribute Blocks (FAB). The /ATTRIBUTES qualifier may be used with the /REPAIR qualifier. If attribute repair is enabled during the repair phase, erroneous bits are cleared from a file's record attributes. This action may not correctly set a file's record attributes because it is beyond the scope of this utility to determine their correct values. Digital recommends that system managers do not perform an attribute repair; instead they should notify the owners of the files about the inconsistencies and have the owners reset the files' attributes using the SET FILE/ATTRIBUTES=({record-attributes}) command. o /OUTPUT The /OUTPUT qualifier specifies the output file to which the disk structure errors are written. If you omit the /OUTPUT qualifier or the file specification, the output is directed to SYS$OUTPUT. If /NOOUTPUT is specified, no disk structure errors are displayed. If the /CONFIRM qualifier is specified, output is forced to SYS$OUTPUT regardless of the use of /OUTPUT or /NOOUTPUT. For more information about the Analyze/Disk_Structure Utility, see the OpenVMS System Management Utilities Reference Manual. 4.4 Authorize Utility V1.0 Authorize utility commands and parameters are identical on AXP and VAX systems. However, the default values for a number of AXP process limits and quotas are higher. See A Comparison of System Management on OpenVMS AXP and OpenVMS VAX for more information. 4-3 System Management Release Notes 4.4 Authorize Utility Digital reserves certain group user identification code (UIC) values on both AXP and VAX operating systems. When specifying a UIC with the /UIC qualifier, valid UIC values for the group number are 2 to 277 (octal) and 400 to 37776 (octal). Group 1 and groups 300 to 377 are reserved. 4.5 AUTOGEN Command Procedure V1.0 AUTOGEN automatically sizes system parameters after you install or upgrade the operating system and after you install optional layered products. Digital recommends that you run AUTOGEN on a weekly basis in order to adjust your system parameters according to your system's workload. See the OpenVMS AXP Version 1.5 Upgrade and Installation Manual for information about running AUTOGEN after installing the operating system. See A Comparison of System Management on OpenVMS AXP and OpenVMS VAX and the OpenVMS System Manager's Manual for additional information about using AUTOGEN. 4.5.1 Problem During System Startup V1.0 There have been instances where operational problems sometimes cause the operating system to enter a loop similar to the following: 1. During system startup, the startup procedure reports that DECwindows cannot be loaded because some system parameters necessary for DECwindows operation are set incorrectly. The system startup procedure asks if AUTOGEN should be run in order to correct the problem. 2. After you answer yes, the AUTOGEN procedure runs. 3. The system then automatically reboots. 4. The system again reports that the DECwindows-related system parameters are set incorrectly. If your system enters a loop as described above, consider the following possible problems: o In some instances, system parameter settings related to DECwindows have not taken effect because the automatic reboot used a different root than the previous boot. 4-4 System Management Release Notes 4.5 AUTOGEN Command Procedure o In some cases, the values in MODPARAMS.DAT force AUTOGEN to set system parameters related to DECwindows incorrectly. If the system startup procedure reports that system parameter settings related to DECwindows are incorrect after an automatic reboot, confirm that the boot is being done from the proper root. In addition, verify that the parameter settings in MODPARAMS.DAT do not conflict with DECwindows requirements. 4.5.2 Support for Installed Resident Images V1.5 AUTOGEN has been modified to update the GH_RSRVPGCNT and ITB_ENTRIES system parameters if feedback is specified or if these parameters are explicitly specified in MODPARAMS.DAT. When feedback is requested, the GH_RSRVPGCNT parameter is modified based on how many pages were allocated from the granularity hint code region after system startup has finished. AUTOGEN sets GH_RSRVPGCNT to the smaller value of either its current value or the number of pages (pages allocated after system startup) plus an additional 10% in order to leave slightly more room for expansion. After AUTOGEN calculates a new value for GH_RSRVPGCNT, it then modifies ITB_ENTRIES accordingly. The GH_RSRVPGCNT and ITB_ENTRIES parameters are updated by AUTOGEN unless any of the following conditions exist: o Feedback is not specified and the GH_RSRVPGCNT and ITB_ENTRIES parameters are not explicitly set in MODPARAMS.DAT. o Feedback is specified, but the SGN$V_RELEASE_PFNS flag is not set in the LOAD_SYS_IMAGES system parameter, which indicates that no PFNs are to be released from the granularity hint regions. Therefore, there is no need to modify these system parameters. o Feedback is specified, but the number of pages currently allocated in the granularity hint code region is less than the number of pages allocated at the end of system startup. If any of those conditions exist, AUTOGEN does not modify the GH_RSRVPGCNT and ITB_ENTRIES system parameters. 4-5 System Management Release Notes 4.5 AUTOGEN Command Procedure 4.5.3 System Parameters V1.0 Digital recommends that you use AUTOGEN to modify system parameters. You can also modify system parameters by using the System Management utility (SYSMAN) or by using the System Generation utility (SYSGEN). 4.5.3.1 AWSTIME and QUANTUM System Parameters V1.0 Some application configurations (for example, a large number of memory-intensive processes) may benefit if the values of the AWSTIME and QUANTUM system parameters are reduced. The value for both parameters should be identical and can be as low as 4. 4.5.3.2 DUMPSTYLE System Parameter - New Values V1.5 The DUMPSTYLE system parameter lets you control the amount and type of information that is generated when an OpenVMS AXP system fails. When an OpenVMS AXP system fails, the system first sends information to the operator's console terminal (if one exists) and then writes the memory contents either fully or selectively to the system dump file. (If there is no console terminal, you do not see the console data.) Both sets of information can be quite complex and very long. However, with the DUMPSTYLE system parameter, you can control how much information you receive, as shown in Table 4-1. Table_4-1_DUMPSTYLE_System_Parameter_Values________________ Value___Meaning____________________________________________ 0 Full dump with minimal console output 1 Selective dump with minimal console output 2 Full dump with full console output 3_______Selective_dump_with_full_console_output____________ The DUMPSTYLE system parameter for Version 1.5 introduces options for the amount of console output. Digital retained the values 0 and 1 for the shorter console output on AXP systems so that you do not have to change your DUMPSTYLE system parameter to get the default, shorter output. The new values of 2 and 3 let users select both the amount of 4-6 System Management Release Notes 4.5 AUTOGEN Command Procedure information that is written to the system dump file and the amount of information that is displayed as console output. The default value is 1. On an AXP system, the SHOW DUMPSTYLE command in the SYSGEN utility lists the default value for the DUMPSTYLE system parameter as 0. However, the AUTOGEN calculated value (effectively a default) is 1. 4.5.3.3 MULTIPROCESSING System Parameter V1.5 The MULTIPROCESSING system parameter, which controls loading of the system synchronization image, has a new value of 4. The new value guarantees that the streamlined image will be loaded in situations where the uniprocessor image would have been loaded by default. The Alpha AXP architecture allows the possibility of adding CPUs to the configuration set after a system boot. The new system parameter value of 4 lets system managers boot a single CPU symmetric multiprocessing (SMP) configuration and then add additional, previously unavailable CPUs (not allowed under VAX systems). The default value for the MULTIPROCESSING parameter will continue to be the same as for VAX systems; the new parameter value has been added to allow the new capability. The system parameter's values have equivalent functions on AXP and VAX systems. Table 4-2 summarizes the functions of the five MULTIPROCESSING values. 4-7 System Management Release Notes 4.5 AUTOGEN Command Procedure Table_4-2_MULTIPROCESSING_Values_on_AXP_and_VAX_Systems____ Value__Function____________________________________________ 0 Load uniprocessing synchronization image. 1 Load full-checking multiprocessing synchronization image if CPU type is capable of SMP and two or more CPUs are present on the system. 2 Always load full-checking version, regardless of system configuration or CPU availability. 3 Load streamlined multiprocessing synchronization image if CPU type is capable of SMP and two or more CPUs are present on the system. 4 Always load streamlined multiprocessing synchronization image, regardless of system _______configuration_or_CPU_availability.__________________ The new parameter value of 4 is comparable to the value of 2 for the full-checking system synchronization image. When the value is set to 4, even uniprocessor configurations load the multiprocessing system synchronization image, but in this case the streamlined one, rather than the full- checking one. When the full-checking multiprocessing synchronization image is loaded, OpenVMS performs software sanity checks on the node's CPUs; in addition, OpenVMS provides a history of spinlock acquisition information for each spin lock. This historical information is available in the event of a system failure. OpenVMS stores a program counter (PC) history in the spinlock (SPL) structures used to synchronize system activity. When the system fails, that information is accessible by using the System Dump Analyzer utility (SDA) SHOW SPINLOCK command. The information displayed includes the PCs of the last 16 acquisitions and releases of the spin locks. An SMP node running the full-checking image performs more slowly than a node running the streamlined image. It is easier to debug system failures on SMP nodes, though, when the full-checking image is enabled. The streamlined image is designed for faster performance, with the tradeoff being less extensive debug support following a system failure. 4-8 System Management Release Notes 4.5 AUTOGEN Command Procedure See Section 4.21 and A Comparison of System Management on OpenVMS AXP and OpenVMS VAX for more information about symmetric multiprocessing support in Version 1.5. 4.5.3.4 PHYSICAL_MEMORY System Parameter V1.0 On AXP systems, the PHYSICAL_MEMORY system parameter replaces the PHYSICALPAGES system parameter found on VAX systems. PHYSICAL_MEMORY is measured in megabytes. To reduce the amount of physical memory available for use, change the PHYSICAL_MEMORY parameter. The default value for the PHYSICAL_MEMORY parameter is the maximum value allowed. See the OpenVMS System Manager's Manual for information about how to calculate the proper system dump file size for your system. 4.5.3.5 System Parameters and Performance Measurements V1.0 The chapter on performance optimization tasks and Appendix A in A Comparison of System Management on OpenVMS AXP and OpenVMS VAX contain information about system-tuning tips that can be used to measure and enhance the performance of your AXP system. 4.5.3.6 System Parameters That Have Been Removed V1.0 The following system parameters are not present on AXP systems: IRPCOUNT IRPCOUNTV LRPCOUNT LRPCOUNTV LRPSIZE SRPCOUNT SRPCOUNTV These parameters were removed as part of the changes for adaptive pool management. Adaptive pool management offers simplified system management, improved performance, and reduced overall pool memory requirements. See A Comparison of System Management on OpenVMS AXP and OpenVMS VAX for more information about adaptive pool management. 4-9 System Management Release Notes 4.6 Backup Utility 4.6 Backup Utility V1.5 The Backup utility on AXP systems now supports hardware data compaction for SCSI tape drives that provide this capability. Use the BACKUP command qualifier /MEDIA_FORMAT=COMPACTION for these devices. 4-10 System Management Release Notes 4.6 Backup Utility 4.6.1 New BACKUP Qualifier - /EXACT_ORDER V1.5 For OpenVMS AXP Version 1.5, BACKUP has a new output qualifier, /EXACT_ORDER. Depending on the other qualifiers you specify on the command line, the /EXACT_ORDER qualifier lets you: o Specify the exact order of volume labels that you want to use in a BACKUP operation o Preserve the existing volume label on a tape o Prevent previous volumes of a multivolume save operation from being overwritten Note the following restrictions when you use the /EXACT_ ORDER output qualifier: o If you use the /EXACT_ORDER qualifier, you cannot specify a label longer than six characters on the command line. If you specify a label longer than six characters, BACKUP displays an error message similar to the following: %BACKUP-F-INVQUAVAL, value 'NET_CONTROL' invalid for /LABEL qualifier o You cannot use the /IGNORE=LABEL_PROCESSING qualifier with the /EXACT_ORDER qualifier. o You cannot use /REWIND as an output qualifier with the /EXACT_ORDER qualifier. The following example uses the /EXACT_ORDER qualifier to specify the exact order of labels for a BACKUP operation: $ BACKUP/IMAGE/RECORD/VERIFY/NOASSIST _From: DKA100: _To: MKB100:MAR11.SAV/LABEL=(TAPE1,TAPE2,TAPE3)/EXACT_ORDER In this example, BACKUP does the following: 1. Compares the volume label of the tape in MKB100: with the first label that you specified on the command line (TAPE1). If the labels match exactly, BACKUP begins the save operation. If the labels do not match, BACKUP displays the following messages: 4-11 System Management Release Notes 4.6 Backup Utility %BACKUP-W-MOUNTERR, volume 1 on MKB100: was not mounted because its label does not match the one requested %BACKUP-W-EXLABERR, volume label processing failed because volume TAPE4 is out of order, Volume label TAPE1 was expected specify option (QUIT, NEW tape, OVERWRITE tape, USE loaded tape) BACKUP> You can then quit the backup operation (QUIT), dismount the old tape and mount a new one (NEW), overwrite the label and the data on the tape (OVERWRITE), or write the data to the tape using the loaded tape's label (USE). 2. When the operation fills the first tape, it displays the following messages: %BACKUP-I-RESUME, resuming operation on volume 2 %BACKUP-I-READYWRITE, mount volume TAPE2 on MKB100: for writing Respond with YES when ready: 3. When you load the second tape and enter YES, BACKUP compares the label of the second tape with the second label you specified on the command line (TAPE2), just as it did in step 1. 4. Assuming the volume labels match, BACKUP continues processing until it completes the operation or runs out of volume labels. If you do not specify enough labels on the command line to complete the operation or if the tape loaded does not have an ANSI label, BACKUP prompts you to enter a label for the tape in the drive as follows: %BACKUP-W-MOUNTERR, volume 4 on MKB100: was not mounted because the label was not specified specify EXACT_ORDER label (up to 6 characters) BACKUP> BACKUP then compares the label on the tape with the label you specify, as described previously. The following example uses the /EXACT_ORDER qualifier to preserve the existing volume label on a tape: $ BACKUP/IMAGE/RECORD/VERIFY/NOASSIST _From: DKA100:[TEST] _To: MKB100:MAR11.SAV/EXACT_ORDER 4-12 System Management Release Notes 4.6 Backup Utility Because this example does not use the /LABEL qualifier, BACKUP uses the existing label on the tape. If the tape does not have an ANSI label and it is the first tape in the operation, BACKUP displays the following error message: %BACKUP-F-NOTANSI, tape is not valid ANSI format If the tape does not have an ANSI label and is not the first tape in the operation, BACKUP displays the following error message prompting you to specify a label: %BACKUP-W-MOUNTERR, volume 1 on MKB100: was not mounted because the label was not specified specify EXACT_ORDER label (up to 6 characters) BACKUP> ________________________ Note ________________________ BACKUP checks to make sure you specify a valid label. If the label is not valid (for example, longer than six characters), BACKUP displays the following error message (on your terminal or the operator terminal depending on whether you specified the /ASSIST qualifier): %BACKUP-F-INVQUAVAL, value 'NET_CONTROL' invalid for /LABEL qualifier ______________________________________________________ You can also use the /EXACT_ORDER qualifier in a multivolume save operation to prevent accidentally overwriting volumes you have already used. BACKUP keeps track of the volume labels you have already used. If you accidentally mount one of the previous volumes, BACKUP displays the following error message: %BACKUP-W-MOUNTERR, volume 1 on MKB100: was not mounted because its label does not match the one requested Volume with label TAPE1 was already used in this save operation specify option (QUIT or NEW tape) BACKUP> 4-13 System Management Release Notes 4.6 Backup Utility 4.6.2 Standalone BACKUP Change V1.5 When you boot standalone BACKUP for OpenVMS AXP Version 1.5, you are not always prompted to enter the time. You are prompted for the time only when the hardware clock does not clearly indicate it. For example, if another operating system were the last one run on the machine, standalone BACKUP might prompt you for the time. 4.6.3 Restrictions V1.5 The following restrictions apply to the Backup utility: o You cannot build a standalone backup kit on the following media types: - A magnetic tape The operating system does not support booting standalone from magnetic tape. - A disk smaller than 20 megabytes This is the minimum disk size needed to build an AXP standalone backup kit. o A BACKUP operation to mixed tape and disk save sets, as shown in the following command, is unsupported: $ BACKUP SYS$DISK:/IMAGE dka0:FOO,MKA0:/SAVE/REW o Because the Movefile operation is not available on AXP systems, you must not use online disk defragmenters (such as DEC File Optimizer for OpenVMS) that rely on the Movefile operation. Digital expects to remove this restriction in a future release. 4.6.4 Backup Restriction Removed V1.5 OpenVMS VAX Version 6.0 supports image backup operations of AXP system disks. You can back up or restore an AXP system disk from a VAX computer. 4-14 System Management Release Notes 4.7 CONSCOPY.COM Command Procedure Not Available 4.7 CONSCOPY.COM Command Procedure Not Available V1.0 VAX systems provide the CONSCOPY.COM command procedure, which system managers can use to create a backup copy of the original console volume disk. The VAX installation supplies the procedure in SYS$UPDATE. The CONSCOPY.COM procedure is not available for AXP systems. AXP consoles are contained in read-only memory, not on disk. 4.8 DECnet for OpenVMS AXP The following sections describe new support and restrictions that apply to DECnet for OpenVMS AXP. 4.8.1 Cluster Alias Support Available V1.5 DECnet cluster alias routing support is available in Version 1.5. Note, however, that the Product Authorization Key (PAK) name that enables DECnet for OpenVMS AXP cluster alias routing support (DVNETEXT) is different from the PAK name that enables OpenVMS VAX cluster alias routing support (DVNETRTG). The functions that are supported with the DVNETEXT (extended function) license differ from the VAX DVNETRTG license. DVNETEXT is supported only to enable Level 1 routing on AXP nodes acting as routers for a cluster alias. In a dual-architecture VMScluster environment, the router for the cluster alias can be either an AXP system or a VAX system. For additional information, see the chapter on networking management tasks in A Comparison of System Management on OpenVMS AXP and OpenVMS VAX. 4.8.2 Restrictions V1.5 The following restrictions apply to DECnet for OpenVMS AXP: o You must start the LAT software after you start DECnet. If you start DECnet after you start LAT, all existing LAT connections are terminated, and you might be unable to reconnect using LAT. This restriction only applies to Ethernet ports that will be running both LAT and DECnet (it does not apply to FDDI). 4-15 System Management Release Notes 4.8 DECnet for OpenVMS AXP o Level 1 routing is available but is supported only on DECnet for OpenVMS AXP nodes acting as routers for a cluster alias. Routing between multiple circuits is not supported. Level 2 routing is not supported on DECnet for OpenVMS AXP nodes. o Some line types are unsupported. OpenVMS AXP Version 1.5 nodes can connect to a DECnet network only via Ethernet lines or FDDI lines. DECnet communication over CI lines is not supported. There also is no support for DDCMP lines. Because DDCMP lines are unsupported, the DCL command SET TERMINAL /PROTOCOL=DDCMP /SWITCH=DECNET also is unsupported on AXP systems. 4.9 Digital-Supplied Device Drivers - File Name Format Change V1.0 Most device drivers supplied by Digital on AXP systems use the following format, where the facility-name is usually SYS: facility-name$xxDRIVER.EXE On VAX systems, no facility prefix is present or permitted for device drivers. They are simply named xxDRIVER.EXE. On AXP systems, non Digital device drivers still can be called xxDRIVER.EXE. ________________________ Note ________________________ User-written device drivers are not supported on OpenVMS AXP systems. ______________________________________________________ 4.10 Distributed Transaction Manager Functionality Available V1.5 The OpenVMS DECdtm Version 1.1 features are included in Version 1.5. Managing DECdtm services is the same as on VAX systems and is described in the OpenVMS System Manager's Manual. Programming DECdtm services is the same as on VAX systems and is described in the OpenVMS System Services Reference Manual. 4-16 System Management Release Notes 4.11 Error Log Report Formatter (ERF) 4.11 Error Log Report Formatter (ERF) The following sections describe features and restrictions that apply to ERF. 4.11.1 Features V1.5 The Error Log Report Formatter (ERF) supports AXP error logs. VAX error logs are not supported. ERF is a native port of the VAX version. Version 1.5 includes support for the FRU entry for the DEC 3000 Model 400 AXP computer. 4.11.2 Restrictions and Limitations V1.0 The following restrictions apply to ERF: o If, by mistake, a VAX error log is analyzed, the results would be unpredictable because VAX error logs are not supported. o The qualifier /SUMMARY is not supported. Its use results in the following error message: %ERF-I-LOADER, error loading image, SYS$SYSTEM:ERFSUMM.EXE o There is no Config Entry support for the DEC 7000 Model 600 AXP computer. 4.12 Help Message Utility (MSGHLP) Restriction V1.0 Features of the new Help Message utility are summarized in Section 3.4. Information about customizing the Help Message database is provided in the OpenVMS System Manager's Manual. ________________________ Note ________________________ Currently, user-supplied comments or additions to Digital-supplied .MSGHLP$DATA files will not be preserved through the next upgrade. However, your own .MSGHLP$DATA files are not affected by future releases. Note that you can reuse .MSGHLP files to insert your own messages into future Digital-supplied database files. Depending on the content of future databases, 4-17 System Management Release Notes 4.12 Help Message Utility (MSGHLP) Restriction you may also be able to reuse some .MSGHLP files to insert comments to existing messages. ______________________________________________________ 4.13 Changes to the Install Utility V1.5 In Version 1.0, you could use the Install utility to install shareable images resident. Version 1.5 lets you install main images resident. Note that these main images must be linked with the /SECTION_BINDING qualifier before they can be installed resident. An attempt to install an image /RESIDENT may fail if the code granularity hint region contains insufficient memory or if the image was linked incorrectly (that is, linked without the /SECTION_BINDING=CODE qualifier). If the attempt fails for either of these reasons, INSTALL now automatically attempts to install the image without the /RESIDENT qualifer but with all other specified options. 4-18 System Management Release Notes 4.13 Changes to the Install Utility When this occurs, the Install utility displays messages, as shown in the following example: $ INSTALL INSTALL> replace/resident sys$library:foo.exe %INSTALL-E-RESFAIL, failed to install image with /RESIDENT qualifier -INSTALL-E-NOGHREG, insufficient memory in the code granularity hint region %INSTALL-I-NONRES, installed image non-resident with other specified options $ INSTALL INSTALL> create/resident sys$library:foo2.exe %INSTALL-E-RESFAIL, failed to install image with /RESIDENT qualifier -INSTALL-E-NOGHREG, insufficient memory in the code granularity hint region %INSTALL-I-NONRES, installed image non-resident with other specified options 4.14 LAT Notes V1.0 OpenVMS AXP supports the LAT software when running on a suitably configured system. See the OpenVMS System Manager's Manual for more information about starting and using the LAT software. ________________________ Note ________________________ You must start the LAT software after you start DECnet. If you start DECnet after you start LAT, all existing LAT connections are terminated, and you might be unable to reconnect using LAT. This restriction applies only to Ethernet ports that will be running both LAT and DECnet (it does not apply to FDDI). ______________________________________________________ Always start LAT from the SYSTEM account because this account typically has appropriate privileges and quotas. 4.15 License Management Facility (LMF) V1.0 Availability Product Authorization Keys (PAKs) are available for OpenVMS AXP. An OpenVMS AXP PAK is identified by the keyword ALPHA in the PAK's option field. PAKs having the ALPHA option can be loaded and used only on AXP systems. However, they can safely reside in a license database (LDB) shared by both VAX and AXP systems. 4-19 System Management Release Notes 4.15 License Management Facility (LMF) Because the LMF for AXP systems is capable of handling all types of PAKs, including those for VAX, Digital recommends that you perform your LDB tasks using the AXP LMF. Availability PAKs for VAX systems (availability PAKs without the ALPHA option) will not load on AXP systems. Only those availability PAKs containing the ALPHA option will load on AXP systems. Other PAK types such as activity (also known as concurrent or n-user) and personal use (identified by the RESERVE_ UNITS option) work on both VAX and AXP systems. Avoid using the following LICENSE commands from a VAX system on a PAK containing the ALPHA option: o REGISTER o DELETE/STATUS o DISABLE o ENABLE o ISSUE o MOVE o COPY o LIST _______________________ Caution _______________________ By default, all AXP availability PAKs look disabled to a VAX system. Never use the DELETE/STATUS=DISABLED command from a VAX system on an LDB that contains AXP PAKs. If you do, all AXP PAKs will be deleted. ______________________________________________________ With the exception of the DELETE/STATUS=DISABLED command, if you inadvertently use one of the LICENSE commands listed above on an AXP PAK while using a VAX system, the PAK and the database will probably not be adversely affected. Repeat the command using LMF running on an AXP system, and the PAK should return to a valid state. 4-20 System Management Release Notes 4.15 License Management Facility (LMF) If you neglect to repeat the command using LMF on an AXP system, the AXP system will be mostly unaffected. At worst, an AXP PAK that you intended to disable will remain enabled. Only the AXP LMF can disable an AXP PAK. However, if you attempt to use any of the commands listed above on a PAK located in an LDB that is shared with a VAX system, the following serious problems may result: o Because AXP PAKs look disabled to a VAX system, they are normally ignored at load time by VAX systems. However, if one of the commands listed above is entered from a VAX system and the PAK information is not set to a valid state by an AXP system, there is a chance the VAX system will attempt to load the AXP PAK. Because the VAX system will be unable to load the PAK, the VAX LMF will report an error. o Even if a valid VAX PAK for the affected product is in the LDB, it too may not load. In this case, system users may be denied access to the product. If the PAK cannot be restored to a valid state because all AXP systems are inaccessible for any reason, use your VAX system to disable the AXP PAK. This prevents your VAX system from attempting to load the AXP PAK. In a future release of the VAX LMF, Digital expects to remove these command restrictions. See the OpenVMS License Management Utility Manual for more information about using LMF. 4.16 Monitor Utility V1.5 The Monitor utility (MONITOR) is nearly identical to that found on VAX systems. However, you should read A Comparison of System Management on OpenVMS AXP and OpenVMS VAX for information about the differences between MONITOR for AXP systems and MONITOR for VAX systems. One significant difference is that on AXP systems, the POOL class does not exist. Instead, adaptive pool management is used to enhance system performance and reduce overall pool memory requirements. See A Comparison of System Management on OpenVMS AXP and OpenVMS VAX for information about adaptive pool management. 4-21 System Management Release Notes 4.16 Monitor Utility Also refer to the OpenVMS System Manager's Manual for more information about the Monitor utility. The following Version 1.0 problems have been fixed in OpenVMS AXP Version 1.5: o When you entered an invalid command that caused a secondary error code from the command language interpreter (CLI), the Monitor utility sometimes displayed the invalid portion of the command incorrectly. For example, an invalid qualifier would not appear between the backslashes that follow an error message. You might also have seen random text in that location, as well as only one backslash. o Because the MSCP server is supported in OpenVMS AXP Version 1.5, the MONITOR MSCP_SERVER command now works properly. 4.17 Mount Utility V1.5 In this version of the operating system, the MOUNT command is supported for tape and disk volumes. The MOUNT/CLUSTER command is also supported. 4.17.1 OpenVMS Support of ISO 9660 Standard - Problems and Restrictions V1.5 This section lists and describes problems and restrictions that apply to OpenVMS support of the ISO 9660 standard. 4.17.1.1 Volume Labels V1.5 For ISO 9660 media, volume labels can contain from 1 to 32 characters. The first 12 characters are used to produce a unique volume identity. If the label is not unique within the first 12 characters, the volume will not mount, and the following error message is displayed: %SYSTEM-F-VOLALRMNT, another volume of the same label already mounted To resolve this problem, mount the volume specifying a different volume label, and use the /OVERRIDE=IDENTIFIER command qualifier. 4-22 System Management Release Notes 4.17 Mount Utility 4.17.1.2 Volume Set Names V1.5 An ISO 9660 volume set name can be from 1 to 128 characters in length. The first 12 characters are used to produce a unique volume set identity. If the volume set name is not unique within the first 12 characters, the volume will not mount and the following error message is displayed: %SYSTEM-F-VOLINSET, volume is already part of another volume set To resolve this problem, mount the volume specifying a new volume set name with the /BIND=volume-set-name command qualifier. 4.17.1.3 Volume Set and Volume Set Name Duplication V1.5 The first 12 characters of both the volume set and the volume set name are used to produce different OpenVMS distributed lock manager resource names, which are then used to coordinate volume and volume set associations. If both the volume name and the volume set name are the same (within the first 12 characters), an OpenVMS distributed lock manager deadlock error occurs, and the following error message is displayed: %SYSTEM-F-DEADLOCK, deadlock detected To resolve this problem, mount the volume specifying a different volume label, and use the /OVERRIDE=IDENTIFIER command qualifier. 4.17.1.4 InfoServer Served Volumes V1.5 The client software that makes InfoServer served volumes available recognizes only volumes whose media format is Files-11 ODS-2. To make ISO 9660 or High Sierra volumes visible to client software and accessible to client nodes, use the following command on the InfoServer for each ISO 9660 or High Sierra volume: INFOSERVER> create service BOOKREADER for DUA0: class ODS-2 4-23 System Management Release Notes 4.17 Mount Utility 4.17.1.5 UNDEFINED Record Format Errors V1.5 Many ISO 9660 CD-ROMs are mastered without a specified record format because the ISO 9660 media can be mastered from platforms that do not support the semantics of files containing predefined record formats. OpenVMS file system commands (such as TYPE and COPY), language run-time libraries, and applications that use RMS for record access may report RMS errors, utility errors, and language errors when accessing files whose record format is UNDEFINED or appears illegally specified. To avoid this problem, use the following command syntax at mount time to force all files of type UNDEFINED to the STREAM record format with a maximum record length of 512 bytes: MOUNT/MEDIA=CDROM/UNDEFINED=(STREAM:512)