____________________________________________________ OpenVMS Alpha Version 1.0 Release Notes Order Number: AA-PQYRA-TE October 1992 This document describes software features, changes, and restrictions, and changes to documentation for Version 1.0 of the OpenVMS Alpha AXP operating system. Revision/Update Information: This is a new manual Software Version: OpenVMS Alpha AXP Version 1.0 Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ October 1992 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 1992. 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: AXP, DEC, DECchip, DECdtm, DECmcc, DECnet, DECspell, DECTPU, DECwindows, DEQNA, Digital, DSSI, FDDI, HSC, KDM, LASTport, LAT, OpenVMS, Q-bus, TURBOchannel, ULTRIX, VAX, VAX RMS, VAXcluster, VAX DOCUMENT, VAXserver, VAXstation, VMS, VMScluster, VT, XMI, XUI, the AXP logo, and the DIGITAL logo. The following are third-party trademarks: Display PostScript is a registered trademark of Adobe Systems Incorporated. MS, Microsoft, and MS-DOS are registered trademarks of Microsoft Corporation. OSF, OSF/Motif, and Motif are registered trademarks of the Open Software Foundation, Inc. PostScript is a registered trademark of Adobe Systems Incorporated. UNIX is a registered trademark of UNIX System Laboratories, Inc. X Window System is a common law trademark of MIT. ZK5852 This document was prepared using VAX DOCUMENT, Version 2.1. _________________________________________________________________ Contents Preface................................................... xi 1 Introduction 1.1 An Overview of OpenVMS Alpha AXP................. 1-1 1.1.1 Differences Between OpenVMS VAX Version 5.5 and OpenVMS Alpha AXP.............................. 1-2 1.1.2 Unsupported OpenVMS Components and Functionality.................................. 1-2 1.2 How to Report Problems Found in OpenVMS Alpha AXP ................................................. 1-3 2 Running OpenVMS Alpha AXP 2.1 OpenVMS Alpha AXP Environment.................... 2-1 2.2 OpenVMS Alpha AXP Installation................... 2-2 2.2.1 Upgrade Procedure Requirement ................. 2-2 2.2.2 VMSINSTAL Runs Only from Compact Disc Drives .. 2-2 2.3 PALcode Version Checking Enabled................. 2-3 2.4 Running OpenVMS Alpha AXP Using a DEC 3000 AXP Series Computer.................................. 2-3 2.4.1 Running DECwindows ............................ 2-3 2.4.2 DECwindows X11 Display Server and Driver ...... 2-4 2.4.2.1 New Font Formats............................ 2-4 2.4.2.2 Font Compiler - Restrictions................ 2-5 2.4.2.3 DECwindows Transport - Restrictions......... 2-5 2.4.2.4 Display Server - Restriction................ 2-6 2.4.2.5 Known Problem............................... 2-6 2.4.2.6 Error Recovery.............................. 2-6 2.4.2.7 Reporting Errors............................ 2-6 2.4.3 Multi-head Configuration ...................... 2-7 2.5 Running OpenVMS Alpha AXP Using a DEC 3000 AXP Model 400 Computer............................... 2-7 iii 2.6 Running OpenVMS Alpha AXP Using a DEC 3000 AXP Model 500 Computer............................... 2-8 2.7 Running OpenVMS Alpha AXP Using a DEC 4000 AXP Computer ........................................ 2-8 2.7.1 Restrictions .................................. 2-8 2.7.2 Small Computer Systems Interface Port Driver - Restriction ................................... 2-8 2.8 Running OpenVMS Alpha AXP Using a DEC 7000 AXP Series Computer.................................. 2-9 2.8.1 Local Digital Storage Architecture (DSA) Disk and Tape Support .............................. 2-9 2.8.2 Local DSA Device Naming - Differs from OpenVMS VAX Implementation............................. 2-9 2.8.3 Small Computer Systems Interface Support ..... 2-12 2.9 Small Computer Systems Interface - DKDRIVER Restriction ..................................... 2-12 2.10 TZK10 Drive - Restriction........................ 2-12 3 General Release Notes 3.1 DCL Commands and Utilities....................... 3-1 3.1.1 APPEND/PROTECTION and COPY/PROTECTION Commands - Incorrect Behavior........................... 3-1 3.1.2 EDIT Command - Change in Default Editor ....... 3-2 3.1.2.1 Retaining the EDT Editor.................... 3-2 3.1.2.2 DCL Command Procedures and the EDIT Command..................................... 3-2 3.1.2.3 EVE and the EDT Keypad...................... 3-3 3.2 DECTPU and EVE Version 3.1 Notes................. 3-3 3.2.1 DECwindows Motif for OpenVMS AXP Operations from EVE in a DECterm Emulator................. 3-3 3.3 Help Message Utility (MSGHLP) ................... 3-4 3.4 Mail Utility - Change in Default Editor.......... 3-5 3.5 Sort/Merge Utility............................... 3-6 3.6 UETP Restrictions................................ 3-7 iv 4 System Management Release Notes 4.1 Accounting Utility - Spurious Message............ 4-2 4.2 Authorize Utility................................ 4-2 4.3 AUTOGEN Command Procedure........................ 4-3 4.3.1 AUTOGEN - Problem During System Startup ....... 4-3 4.3.2 System Parameters ............................. 4-4 4.3.2.1 Changes to System Parameters ............... 4-4 4.3.2.2 AWSTIME and QUANTUM System Parameters....... 4-6 4.3.2.3 PHYSICAL_MEMORY System Parameter............ 4-6 4.3.2.4 System Parameters and Performance Measurements ............................... 4-6 4.3.2.5 System Parameters That Have Been Removed ... 4-7 4.4 Backup Utility - Restrictions.................... 4-7 4.5 CONSCOPY.COM Procedure Not Available ............ 4-8 4.6 DECnet for OpenVMS Alpha AXP - Restrictions ..... 4-8 4.7 Digital-Supplied Device Drivers - File Name Format Change ................................... 4-9 4.8 Error Log Report Formatter (ERF)................. 4-9 4.8.1 Restrictions and Limitations .................. 4-9 4.9 Help Message Utility (MSGHLP) Restriction........ 4-10 4.10 LAT Notes........................................ 4-10 4.11 License Management Facility (LMF)................ 4-11 4.12 Monitor Utility.................................. 4-13 4.12.1 Restrictions ................................. 4-13 4.13 Mount Utility.................................... 4-14 4.13.1 Restrictions .................................. 4-14 4.14 Operator Communication Manager (OPCOM)........... 4-14 4.15 Password Generation.............................. 4-14 4.16 Privileges, Protections, and Quotas.............. 4-15 4.17 System Generation Utility - Unsupported Commands ................................................. 4-15 4.18 System Management Utility........................ 4-15 4.18.1 I/O Configuration Support in SYSMAN ........... 4-15 4.19 Terminal Fallback Facility (TFF)................. 4-16 4.20 VMScluster Systems Unsupported on OpenVMS Alpha AXP ............................................. 4-17 4.20.1 Lack of Support for VMSclusters Impacts Maintenance ................................... 4-17 4.21 Watch Chip - Change in Time Range................ 4-19 v 5 Programming Release Notes 5.1 OpenVMS Debugger Notes........................... 5-2 5.1.1 Language Support .............................. 5-2 5.1.2 Known Problems and Restrictions ............... 5-2 5.1.2.1 Debugging Translated Images................. 5-2 5.1.2.2 Debugging Installed Resident Images......... 5-2 5.1.2.3 Debugging Inlined Routines.................. 5-3 5.1.2.4 Debugging Global Sections................... 5-3 5.1.2.5 Debugging Register Frame Procedures or No Frame Procedures............................ 5-3 5.1.2.6 Compilation with /DEBUG Qualifier........... 5-3 5.1.2.7 Complex Variables in FORTRAN Programs....... 5-3 5.1.2.8 Concealed Rooted-Directory Logical Names for Source Files................................ 5-4 5.1.2.9 Ctrl/C Interruption......................... 5-4 5.1.2.10 HALT Instructions........................... 5-4 5.1.2.11 CALL Command Problems and Restrictions...... 5-4 5.1.2.12 DEPOSIT/TYPE Command with C Programs........ 5-5 5.1.2.13 DEPOSIT and EXAMINE Commands with Floating-Point Values....................... 5-5 5.1.2.14 EXAMINE Command Problems and Restrictions... 5-5 5.1.2.15 SET IMAGE Command Limitation................ 5-6 5.1.2.16 SET WATCH Command Caution................... 5-6 5.1.2.17 SHOW BREAK and SHOW TRACE Command Limitations................................. 5-7 5.1.2.18 STEP/INTO Command and User Exception Handlers.................................... 5-7 5.1.2.19 STEP/OVER Command Error With Recursive Calls....................................... 5-7 5.1.2.20 STEP/OVER Command Error With One-Line Program Loops............................... 5-7 5.1.2.21 $WAKE Call Followed by $HIBER Call.......... 5-8 5.1.2.22 DCL ANALYZE/PROCESS_DUMP Command and Zero Program Counter............................. 5-8 5.1.2.23 Changed Watchpoint Locations During System Service Calls............................... 5-8 5.1.2.24 STEP Command and Asynchronous System Trap (AST) Routines.............................. 5-8 5.1.2.25 STEP Command into System Service Calls...... 5-8 5.1.2.26 LCK$M_DEQALL Modifier in $DEQ System Service Call........................................ 5-9 5.1.2.27 SHOW CALLS Command Can Display System Call Frames...................................... 5-9 vi 5.2 DECthreads....................................... 5-9 5.2.1 Restrictions ................................. 5-9 5.3 DECwindows Motif for OpenVMS AXP Version 1.1..... 5-10 5.4 Executive Notes.................................. 5-10 5.4.1 Spinlock Changes .............................. 5-10 5.4.2 SYS.EXE Renamed to SYS$BASE_IMAGE.EXE ......... 5-10 5.4.3 Executive Functions Not Included in OpenVMS Alpha AXP...................................... 5-10 5.5 File System Notes................................ 5-10 5.5.1 File Definition Language ..................... 5-11 5.5.2 National Character Set ....................... 5-11 5.6 IEEE Floating Point Standard..................... 5-11 5.7 Linker Utility - Restriction..................... 5-12 5.8 MACRO-32 Compiler for OpenVMS Alpha AXP - Restrictions and Known Problems ................. 5-12 5.9 Run-Time Libraries............................... 5-14 5.9.1 Compatibility Between the OpenVMS VAX and OpenVMS Alpha AXP Mathematics Libraries........ 5-14 5.10 STARLET Data Structures and Definitions For C Programmers...................................... 5-15 5.11 SUMSLP Utility (SUMSLP).......................... 5-17 5.12 System Dump Analyzer Utility Notes............... 5-17 5.12.1 SHOW MACHINE_CHECK Command Available .......... 5-17 5.12.2 Restrictions and Known Problems ............... 5-18 5.12.2.1 ANALYZE/CRASH_DUMP and ANALYZE/SYSTEM....... 5-19 5.12.2.2 General Register Symbols.................... 5-19 5.12.2.3 RMS Commands................................ 5-20 5.12.2.4 SHOW CRASH Display is Incorrect............. 5-20 5.13 System Services Notes............................ 5-20 5.13.1 Low Four Bits of Chan Argument Are Checked - Change ........................................ 5-20 5.13.2 $DCLCMH System Service Behavior Differs on OpenVMS Alpha AXP and OpenVMS VAX Systems...... 5-21 5.13.3 $FORMAT_AUDIT Width Argument Does Not Work Consistently - Restriction .................... 5-22 5.14 Traceback Handler Support........................ 5-22 5.15 Translated Image Environment (TIE) Notes......... 5-23 5.15.1 Interoperability .............................. 5-23 5.15.2 Running Translated Images ..................... 5-24 5.15.3 TIE Statistics and Feedback ................... 5-25 5.15.4 TIE Restrictions .............................. 5-25 5.16 Translated Images and Other Related Files........ 5-29 5.17 Translated Run-Time Libraries.................... 5-33 vii 5.17.1 Accessing the D56 Form of the Run-Time Libraries...................................... 5-34 5.17.2 Problem with Translated Image Environment ..... 5-35 5.17.3 Translated VAX BASIC Run-Time Library Notes ... 5-35 5.17.3.1 Functional Restrictions..................... 5-35 5.17.4 Translated VAX C Run-Time Library Notes ....... 5-36 5.17.4.1 Functional Restrictions..................... 5-36 5.17.4.2 Interoperability Restrictions............... 5-37 5.17.5 Translated VAX FORTRAN Programs - Restriction.................................... 5-38 6 Documentation Release Notes 6.1 OpenVMS Alpha AXP Documentation Set.............. 6-1 6.2 OpenVMS DCL Dictionary........................... 6-1 6.3 OpenVMS Linker Utility Manual.................... 6-2 6.4 VMS National Character Set Utility Manual ....... 6-2 6.5 Correction to OpenVMS Programming Documentation.. 6-2 6.6 OpenVMS System Management Utilities Reference Manual........................................... 6-3 6.7 OpenVMS Alpha Guide to System Security........... 6-4 A New OpenVMS System Messages B DECTPU and EVE Release Notes B.1 DECTPU New Features.............................. B-1 B.1.1 EDIT Command and Multiple Input Files ......... B-1 B.1.2 Choosing Alternate Character Sets ............. B-2 B.1.3 Motif User Interface Support Added for DECTPU......................................... B-3 B.2 EVE New Features................................. B-3 B.2.1 Motif User Interface Support Added for EVE .... B-4 B.2.2 Selecting the Keypad in EVE ................... B-7 B.3 New DECTPU Built-ins............................. B-7 B.3.1 DECwindows Motif for OpenVMS AXP Environment Built-in....................................... B-7 B.3.2 First Input Action Built-in ................... B-8 B.3.3 Input File Name Built-in ...................... B-9 B.3.4 Built-ins to Lower and Raise a Widget ......... B-9 B.3.5 Motif Widget Context Help Built-in ............ B-10 B.3.6 Popup Parent Widget Built-in .................. B-10 B.3.7 Screen Pixel Size Built-in .................... B-10 viii B.3.8 Top Level Widget Built-in ..................... B-11 B.3.9 UID Built-in .................................. B-11 B.3.10 Widget Resource Types Built-in ................ B-11 B.3.11 Built-ins for the X Resource Database ......... B-12 B.4 Modified DECTPU Built-ins........................ B-12 B.4.1 COMMAND_LINE .................................. B-13 B.4.2 DECwindows Motif for OpenVMS AXP Environment .. B-13 B.4.3 DECwindows Motif for OpenVMS AXP Hierarchy .... B-13 B.4.4 Defining a WIDGET Class ....................... B-13 B.4.5 GET_INFO (SYSTEM) Built-in Procedure .......... B-13 B.4.6 Global Select ................................. B-14 B.4.7 Icon Handling ................................. B-14 B.4.8 Menu Positioning .............................. B-15 B.4.9 Sending Strings to Processes .................. B-15 B.4.10 SCREEN Information ............................ B-15 B.4.11 Screen Update Behavior ........................ B-16 B.4.12 WIDGET Identification ......................... B-17 B.4.13 Writing Buffers ............................... B-17 B.5 Miscellaneous DECTPU Enhancements................ B-18 B.5.1 Command File Input ............................ B-18 B.5.2 FAO, MESSAGE and MESSAGE_TEXT Built-ins ....... B-18 B.5.3 ON and OFF States ............................. B-18 B.5.4 OpenVMS Alpha AXP DCL Qualifier Changes ....... B-20 B.5.5 Work File ..................................... B-20 B.6 New EVE Commands................................. B-20 B.6.1 GET Command ................................... B-21 B.6.2 GET WILDCARDED FILES Command .................. B-21 B.6.3 GLOBAL REPLACE Command ........................ B-21 B.6.4 SET FUNCTION KEYS MOTIF Command ............... B-21 B.6.5 SET SELECTION GRAB FOCUS Command .............. B-21 B.6.6 SET SELECTION GRAB SELECTION Command .......... B-21 B.7 Miscellaneous EVE Enhancements................... B-22 B.7.1 Commands Available Within System Buffers ...... B-22 B.7.2 Edit Handlers ................................. B-22 B.7.3 Faster Command Parser ......................... B-22 B.7.4 FILL Permitted with DIGITAL Standard Runoff (DSR) and VAX Document Tags.................... B-23 B.7.5 Menu Changes .................................. B-23 B.7.6 Obsolete EVE Constants ........................ B-24 B.7.7 SPELL Command Available for DECwindows Motif for OpenVMS AXP................................ B-25 B.7.8 Title Bar Copyright ........................... B-25 B.8 DECTPU and EVE Restrictions...................... B-25 ix B.8.1 DECwindows Motif for OpenVMS AXP Applications that Execute READ_KEY and READ_CHAR Built-ins...................................... B-26 B.8.2 SET (MAPPED_WHEN_MANAGED) Built-in ............ B-26 B.8.3 Small Display Monitors and DECwindows Motif for OpenVMS AXP Applications....................... B-27 B.9 DECTPU Problems That Have Been Fixed ............ B-27 B.9.1 Aborting Compilation with Ctrl/C .............. B-27 B.9.2 !AF FAO Directive Dropped from DECTPU Messaging...................................... B-28 B.9.3 Ctrl/C Key Definition ......................... B-28 B.9.4 Ctrl/C and Startup ............................ B-28 B.9.5 DEFINE_WIDGET_CLASS Built-in .................. B-28 B.9.6 HELP_TEXT Built-in ............................ B-29 B.9.7 Improved DECwindows Motif for OpenVMS AXP Error Codes.......................................... B-29 B.9.8 Journaling Performance Improvement ............ B-30 B.9.9 KEY_NAME and CTRL_MODIFIED .................... B-30 B.9.10 Logical Names and Journal File Conflict ....... B-30 B.9.11 DECwindows Motif for OpenVMS AXP and Cursor Blink.......................................... B-31 B.9.12 DECwindows Motif for OpenVMS AXP Interface and TPU$TPU Callable Routine....................... B-31 B.9.13 DECwindows Motif for OpenVMS AXP Resize ....... B-31 B.9.14 Multiple-line Text Strings in DECwindows Motif for OpenVMS AXP Applications................... B-32 B.9.15 Partial Escape Sequence Errors ................ B-32 B.9.16 READ_KEY Built-in ............................. B-32 B.9.17 READ_KEY and READ_CHAR Prompts in DECwindows Motif for OpenVMS AXP Applications............. B-32 B.9.18 READ_LINE Built-in for DECwindows Motif for OpenVMS AXP Applications....................... B-33 B.9.19 READ_LINE Prompt String Limited to 255 Characters..................................... B-33 B.9.20 Reverse Searches From the Beginning of a Line........................................... B-33 B.9.21 Screen Adjustments in DECwindows Motif for OpenVMS AXP Applications....................... B-33 B.9.22 SET (ICON_PIXMAP) Built-in .................... B-34 B.9.23 SET (TIMER) Built-in Problem Corrected ........ B-34 B.9.24 SET (WIDGET_CALLBACK) Built-in on Leaf Widgets........................................ B-34 B.9.25 Space Padding ................................. B-34 x B.9.26 TRANSLATE and EDIT Screen Display Fixed ....... B-35 B.9.27 UID Hierarchy Identifier ...................... B-35 B.10 EVE Problems That Have Been Fixed................ B-35 B.10.1 BOX CUT Command Improved ...................... B-35 B.10.2 Box Operations in Overstrike Mode ............. B-35 B.10.3 Command File and SAVE ATTRIBUTES Command ...... B-35 B.10.4 DCL or SHELL Subprocesses and the DECwindows Motif for OpenVMS AXP Environment.............. B-36 B.10.5 DECspell Error Was Not Resetting State ........ B-36 B.10.6 DECwindows Motif for OpenVMS AXP EVE and Window Managers Other than Motif...................... B-36 B.10.7 Error Handling in GET [WILD] FILE[S] .......... B-36 B.10.8 EVE$BUILD ..................................... B-36 B.10.9 EVE$TEARDOWN_WINDOWS and EVE$SETUP_WINDOWS Procedures..................................... B-37 B.10.10 EVE and Concealed Logical Names ............... B-37 B.10.11 EVE Parser and User's Facility Name ........... B-37 B.10.12 EVE Repeat Operations ......................... B-38 B.10.13 FIND SELECTED with Box Select Active .......... B-39 B.10.14 FILL RANGE .................................... B-39 B.10.15 GET Command and Input File .................... B-40 B.10.16 Help On GET_INFO Built-in Improved ............ B-40 B.10.17 Help Messages Improved ........................ B-40 B.10.18 Improved SHOW BUFFERS Command ................. B-40 B.10.19 Improved Operations on White Space ............ B-40 B.10.20 Improved Window Buffering ..................... B-41 B.10.21 Invoking EVE with Ambiguous Input File Specifications................................. B-41 B.10.22 DECwindows Motif for OpenVMS AXP "Quick Cut" Operation Improved............................. B-41 B.10.23 Mouse Button MB1 and Range Removal ............ B-41 B.10.24 Mouse Drag .................................... B-42 B.10.25 Open Dialog Box Filter Corrected .............. B-42 B.10.26 Open Dialog Box and Wildcard Active ........... B-42 B.10.27 OPEN SELECTED Command and Context Resetting ... B-42 B.10.28 OPEN SELECTED Command and Multiple File Selections..................................... B-42 B.10.29 OSF/Motif Style Guide Conformance ............. B-43 B.10.30 Primary Cut Mouse Operation ................... B-43 B.10.31 Prompt Replies Trimmed ....................... B-44 B.10.32 /RECOVER and Ctrl/C ........................... B-44 B.10.33 RECOVER BUFFER and Logical Names .............. B-44 B.10.34 Resize Action Fixed ........................... B-44 xi B.10.35 SET SCROLLING command ......................... B-45 B.10.36 SHOW BUFFERS and Buffer Deletion .............. B-46 B.10.37 SHOW Command Improved ......................... B-46 B.10.38 SYSTEM Buffers are Marked Permanent ........... B-46 B.10.39 Wildcard Input File Specification ............. B-46 B.10.40 EVE Word Operations ........................... B-47 Index Tables 2-1 Device Naming ................................. 2-10 4-1 TFF Character Tables .......................... 4-17 5-1 Run-Time Libraries Not Included ............... 5-14 5-2 Interoperability Documentation ................ 5-24 5-3 Run-Time Library Logical Names ................ 5-35 B-1 Character Set Values .......................... B-3 B-2 EVE Widget Resource Name Conversions .......... B-4 B-3 EVE Widget Callback Reason Conversions ........ B-6 B-4 GET_INFO Keywords ............................. B-14 B-5 Name Changes or Additions to EVE's Pulldown Menus.......................................... B-23 xii _________________________________________________________________ Preface The OpenVMS Alpha Version 1.0 Release Notes manual describes features and restrictions of the OpenVMS Alpha AXP operating system. It also provides information about operating OpenVMS Alpha AXP computers and provides descriptions of features that are unique to OpenVMS Alpha AXP systems. Intended Audience This manual is intended for general users, system managers, developers, and programmers who use the OpenVMS Alpha AXP operating system. It is especially useful for those who are about to install the OpenVMS Alpha AXP operating system. Document Structure Chapter 1 provides an overview of OpenVMS Alpha AXP. Chapter 2 provides information about using OpenVMS Alpha AXP on OpenVMS Alpha AXP computers. Chapter 3 describes changes, new features, and restrictions that affect some commonly used OpenVMS Alpha AXP utilities, text processing utilities, and other aspects of the user environment. 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. xi Chapter 6 describes corrections to the OpenVMS Alpha AXP documentation set. Appendix A contains new or changed system messages for many OpenVMS Alpha AXP facilities, as part of the new Help Message utility (MSGHLP). Appendix B contains information about DECTPU and EVE, including new features, changes, restrictions, and problems that have been fixed. Associated Information For a list of additional documents that are available in support of this version of OpenVMS Alpha AXP, readers should refer to the CD booklet and the Overview of OpenVMS Documentation. Readers should also refer to the OpenVMS Alpha Version 1.0 Release Notes Addendum, which is part of the Cover Letter for OpenVMS AXP Version 1.0. Conventions In this manual, every use of OpenVMS Alpha AXP means the OpenVMS Alpha AXP operating system. Every use of OpenVMS VAX means the OpenVMS VAX operating system. The following conventions are also used in this manual: Ctrl/x A sequence such as Ctrl/x (or 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. 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.) xii . . . 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. A vertical ellipsis indicates the omission . of items from a code example or command . format; the items are omitted because . they are not important to the topic being discussed. ( ) In format descriptions, parentheses indicate that, if you choose more than one option, you must enclose the choices in parentheses. [ ] In format descriptions, brackets indicate that whatever is enclosed within the brackets is optional; you can select none, one, or all of the choices. (Brackets are not, however, optional in the syntax of a directory name in a 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 online versions of the book. italic text Italic text represents information that can vary in system messages (for example, Internal error number). xiii UPPERCASE TEXT Uppercase text indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege. - Hyphens in coding examples indicate that additional arguments to the request are provided on the line that follows. numbers Unless otherwise noted, all numbers in the text are assumed to be decimal. Nondecimal radixes-binary, octal, or hexadecimal-are explicitly indicated. mouse The term mouse is used to refer 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.) xiv 1 _________________________________________________________________ Introduction This chapter provides a brief overview of OpenVMS Alpha AXP, including a discussion of the differences between OpenVMS Alpha AXP and OpenVMS VAX Version 5.5. It also describes how to report problems found with the operating system. 1.1 An Overview of OpenVMS Alpha AXP OpenVMS Alpha AXP Version 1.0 is the first release of the OpenVMS operating environment for Digital's 64-bit architecture. This release contains many of the OpenVMS VAX operating system features. A series of releases will phase in the complete OpenVMS Alpha AXP environment. The OpenVMS Alpha AXP Version 1.0 operating system is a port of OpenVMS VAX Version 5.4-2 features but includes selected features of releases after Version 5.4-2 of OpenVMS VAX. Refer to the following chapters for detailed descriptions of OpenVMS Alpha AXP restrictions and changes: - Chapter 3 describes the features, restrictions, and changes that affect areas of the user environment, such as DCL commands and utilities, DECTPU and EVE, the Sort /Merge utility, and UETP. - Chapter 4 describes the features, restrictions, and changes that apply to items used for system management and maintenance, performance management, and networking. - Chapter 5 describes features, restrictions, and changes that apply to items of particular interest to programmers, such as the OpenVMS Debugger, DECthreads, the file system, run-time libraries, the System Dump Analyzer (SDA), system services, the Translated Image 1-1 Introduction 1.1 An Overview of OpenVMS Alpha AXP Environment (TIE), and translated executables, images, and related files. Problems with any OpenVMS Alpha AXP features should be reported to Digital, using the method described in Section 1.2. 1.1.1 Differences Between OpenVMS VAX Version 5.5 and OpenVMS Alpha AXP For a discussion of the differences between OpenVMS VAX and OpenVMS Alpha AXP, see A Comparison of System Management on OpenVMS Alpha and OpenVMS VAX. That manual describes differences that affect system setup, maintenance, security, performance optimization, and network management. Appendix A of that manual describes architectural differences between OpenVMS VAX and OpenVMS Alpha AXP and their effect on performance characteristics. 1.1.2 Unsupported OpenVMS Components and Functionality The following OpenVMS components and related products are not supported on OpenVMS Alpha AXP Version 1.0: o Symmetric multiprocessing (SMP) o VMSclusters o DECdtm, a component of OpenVMS on VAX o DEC InfoServer, which includes the Local Area Disk Control Program (LAD CP) and the LAST/port network transport control program o OpenVMS Volume Shadowing o RMS Journaling o VAX Distributed Name Service (DNS) o The TECO editor o Level 1 and level 2 host-based DECnet routing o DIGITAL Data Communications Message Protocol (DDCMP) connections for DECnet communications o Multiple disk volume sets 1-2 Introduction 1.1 An Overview of OpenVMS Alpha AXP o With the OpenVMS Alpha AXP Version 1.0 release, a number of layered products from Digital Equipment Corporation and other vendors are not available yet. Your Digital representative can provide you with a current list of the Digital layered products that are available for OpenVMS Alpha AXP computers. If you copy existing startup procedures from one of your OpenVMS VAX computers to an OpenVMS Alpha AXP system disk, you must comment out the calls to the startup procedures of currently unavailable layered products. 1.2 How to Report Problems Found in OpenVMS Alpha AXP If you encounter a problem while using the OpenVMS Alpha AXP 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 Alpha AXP This chapter describes the following aspects of running the OpenVMS Alpha AXP operating system: o The OpenVMS Alpha AXP environment o Running DECwindows o Information about running OpenVMS Alpha AXP on the DEC 3000 AXP Model 400 computer o Information about running OpenVMS Alpha AXP on the DEC 3000 AXP Model 500 computer o Information about running OpenVMS Alpha AXP on the DEC 4000 AXP computer o Information about running OpenVMS Alpha AXP on the DEC 7000 AXP Model 600 series computer 2.1 OpenVMS Alpha AXP Environment OpenVMS Alpha AXP can run on the DEC 3000 AXP Model 400, DEC 3000 AXP Model 500, DEC 4000 AXP, and DEC 7000 AXP Model 600 series computers. You should refer to the hardware manuals supplied with your OpenVMS Alpha AXP computer for detailed information about system hardware installation and operation. The DEC 3000 AXP Model 400 and DEC 3000 AXP Model 500 computers provide graphics and audio capabilities on a workstation or server platform. The DEC 4000 AXP computer is a high-performance superserver for multiple users, on a system that provides high capacity storage. 2-1 Running OpenVMS Alpha AXP 2.1 OpenVMS Alpha AXP Environment The DEC 7000 AXP Model 600 series computer is a high performance departmental system supporting multiple XMI buses, large numbers of DSA and SCSI disks, and large memory configurations. See the OpenVMS Alpha AXP Software Product Description (SPD 41.87.xx) for a description of the OpenVMS Alpha AXP operating system and supported hardware. 2.2 OpenVMS Alpha AXP Installation OpenVMS Alpha AXP Version 1.0 provides installation and upgrade capabilities. For complete instructions on installing or upgrading the OpenVMS Alpha AXP operating system, see the OpenVMS Alpha Version 1.0 Upgrade and Installation Manual. That manual contains installation, upgrade, and operations information about Alpha AXP computers that run OpenVMS Alpha AXP operating system software. 2.2.1 Upgrade Procedure Requirement During the upgrade procedure you will be 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 (ddcu:): Although the prompt implies that you have a choice, you must specify the system disk. 2.2.2 VMSINSTAL Runs Only from Compact Disc Drives For Version 1.0 of the OpenVMS Alpha AXP operating system, VMSINSTAL runs from compact disc drives only. No other devices are supported in this release, including CSA0: and CSA1: devices (console block storage devices that do not exist on Alpha AXP systems). 2-2 Running OpenVMS Alpha AXP 2.3 PALcode Version Checking Enabled 2.3 PALcode Version Checking Enabled Minimum PALcode version checking is enabled on OpenVMS Alpha AXP Version 1.0. See your Digital representative for the minimum version of PALcode that is appropriate for your system. If the minimum PALcode version is not present on your system, the booting procedure will abort after displaying a message similar to the following: APB-F-PALREV, PAL code revision 4.33 is below minimum revision level of 4.58 unable to continue. 2.4 Running OpenVMS Alpha AXP Using a DEC 3000 AXP Series Computer The following sections discuss configuration tasks and functionality that are common to the OpenVMS Alpha AXP DEC 3000 AXP Model 400 and Model 500 computers. Refer to Section 2.5 for additional information that is specific to the DEC 3000 AXP Model 400 computer. Refer to Section 2.6 for additional information that is specific to the DEC 3000 AXP Model 500 computer. 2.4.1 Running DECwindows Currently, the DEC 3000 AXP Model 400 and DEC 3000 AXP Model 500 workstations are the only OpenVMS Alpha AXP hardware platforms that are able to display graphics. Support for DECwindows Motif for OpenVMS Alpha AXP is provided by: o The DECwindows X11 display server, which is an optional part of the OpenVMS Alpha AXP Version 1.0 kit. This optional part can be selected during the OpenVMS Alpha AXP Version 1.0 installation procedure, when you are asked if you want to provide optional DECwindows workstation support. o The DECwindows Motif for OpenVMS Alpha AXP layered product, which provides programming and application support. This layered product must be installed separately. 2-3 Running OpenVMS Alpha AXP 2.4 Running OpenVMS Alpha AXP Using a DEC 3000 AXP Series Computer To run DECwindows Motif for OpenVMS Alpha AXP applications locally on the DEC 3000 AXP series computers, you must select the option for the DECwindows X11 display server during the OpenVMS Alpha AXP installation procedure and also install the DECwindows Motif for OpenVMS Alpha AXP layered product. See the DECwindows Motif for OpenVMS AXP Version 1.1 Installation Guide for information about installing the DECwindows Motif for OpenVMS Alpha AXP Version 1.1 layered product. 2.4.2 DECwindows X11 Display Server and Driver The DECwindows X11 display server, including device drivers and fonts, can be selected for installation during the OpenVMS Alpha 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 initially tested: o D2DX - Digital 2D Extension o MITMisc - Miscellaneous MIT Extensions o Shape - Nonrectangular Windows Extension o SME - Server Management Extension o XIE - X Imaging Extension o XTrap - X Protocol Trap Extension 2.4.2.1 New Font Formats 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 OpenVMS DECwindows display server will be available in PCF format. Applications do not have to be modified in order to use the PCF fonts. 2-4 Running OpenVMS Alpha AXP 2.4 Running OpenVMS Alpha AXP Using a DEC 3000 AXP Series Computer 2.4.2.2 Font Compiler - Restrictions 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 OpenVMS VAX font compiler's MINBBOX and REPORT qualifiers are not supported in OpenVMS Alpha AXP Version 1.0. 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.4.2.3 DECwindows Transport - Restrictions The following restrictions apply to DECwindows transport: o Although the VMS DECwindows Transport Manual does not state it, routines in customer-supplied DECwindows transports must execute in executive (exec) mode. If you are writing your own transport layer, the transport-specific routines must be executable in exec mode. This restriction applies to both OpenVMS Alpha AXP and OpenVMS VAX DECwindows transport routines. o DECwindows DECnet and local transport display server options are available. DECwindows TCP/IP network transport is not available; UCX support and testing is pending. 2-5 Running OpenVMS Alpha AXP 2.4 Running OpenVMS Alpha AXP Using a DEC 3000 AXP Series Computer 2.4.2.4 Display Server - Restriction When you press the halt button and continue system operation, only 6 lines will be 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. When you power-on or reboot the system, the full console screen will be displayed. This is a permanent restriction in the display server. 2.4.2.5 Known Problem Occasionally the mouse remains visible after the screen saver has shut off the monitor display. 2.4.2.6 Error Recovery 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.4.2.7 Reporting Errors 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.2 for information about reporting problems found with the DECwindows X11 display server. 2-6 Running OpenVMS Alpha AXP 2.4 Running OpenVMS Alpha AXP Using a DEC 3000 AXP Series Computer 2.4.3 Multi-head Configuration A multi-head configuration consists of a single DEC 3000 AXP series workstation that supports multiple graphics options. A graphics option consists of a graphics controller and a graphics display interface (monitor). A DEC 3000 AXP series system will be automatically configured for multi-head 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. 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 will always select 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.5 Running OpenVMS Alpha AXP Using a DEC 3000 AXP Model 400 Computer See the DEC 3000 AXP Model 400 Owner's Guide for information about using and maintaining the DEC 3000 AXP Model 400 computer. Refer to the OpenVMS Alpha AXP Software Product Description (SPD 41.87.xx) for the DEC 3000 AXP Model 400 system configurations that are supported on OpenVMS Alpha AXP. 2-7 Running OpenVMS Alpha AXP 2.6 Running OpenVMS Alpha AXP Using a DEC 3000 AXP Model 500 Computer 2.6 Running OpenVMS Alpha AXP Using a DEC 3000 AXP Model 500 Computer See the DEC 3000 AXP Model 500 Owner's Guide for information about using and maintaining the DEC 3000 AXP Model 500 computer. Refer to the OpenVMS Alpha AXP Software Product Description (SPD 41.87.xx) for the DEC 3000 AXP Model 500 system configurations that are supported in OpenVMS Alpha AXP. 2.7 Running OpenVMS Alpha AXP Using a DEC 4000 AXP Computer See the DEC 4000 AXP Owner's Guide for more information about using and maintaining the DEC 4000 AXP computer. Refer to the OpenVMS Alpha AXP Software Product Description (SPD 41.87.xx) for the DEC 4000 AXP system configurations that are supported in OpenVMS Alpha AXP. 2.7.1 Restrictions The following restrictions and limitations apply to DEC 4000 AXP support: o Dual-porting of DSSI disks is not supported. o The ANALYZE/ERROR command will not format error log entries resulting from DSSI devices. This problem will be corrected in a future release of OpenVMS Alpha AXP. o The following command may be used to configure the secondary console terminal port on DEC 4000 AXP systems: $ RUN SYS$SYSTEM:SYSMAN SYSMAN> IO CONNECT OPA1:/NOADAPTER/DRIVER=OPERATOR For convenience, this command can be added to the site- specific startup command procedure. 2.7.2 Small Computer Systems Interface Port Driver - Restriction The small computer systems interface (SCSI) port driver for the DEC 4000 AXP computer does not support bus disconnects or several types of error recovery. Because of this, a DEC 4000 AXP system will not perform overlapping disk seeks. Also, any unexpected SCSI bus condition will produce an INCONSTATE bugcheck. 2-8 Running OpenVMS Alpha AXP 2.7 Running OpenVMS Alpha AXP Using a DEC 4000 AXP Computer System hangs when accessing BACKUP save sets stored on disks also have been observed; such hangs are configuration-dependent. Some actions that alter the total length of the SCSI bus may eliminate further occurrences of the hangs. These limitations result from attempts to change the device driver development methodology for OpenVMS Alpha AXP. The limitations will be lifted in a release following OpenVMS Alpha AXP Version 1.0. Digital regrets the inconvenience caused by these limitations. 2.8 Running OpenVMS Alpha AXP Using a DEC 7000 AXP Series Computer For information about using and maintaining the DEC 7000 AXP Model 600 series computer, see the DEC 7000 AXP Model 600 Owner's Guide. Refer to the OpenVMS Alpha AXP Software Product Description (SPD 41.87.xx) for the DEC 7000 AXP Model 600 series system configurations that are supported in OpenVMS Alpha AXP. 2.8.1 Local Digital Storage Architecture (DSA) Disk and Tape Support OpenVMS Alpha AXP provides support for local DSA disk and tape devices on the DEC 7000 AXP Model 600 series computer. Support is provided with the KDM70 on the XMI bus. However, you must obtain the latest KDM microcode, which supports the OpenVMS Alpha AXP 8 kilobyte (KB) page size, from your Digital representative. See the OpenVMS Alpha AXP Software Product Description (SPD 41.87.xx) for information about devices and peripherals that are supported on OpenVMS Alpha AXP Version 1.0. 2.8.2 Local DSA Device Naming - Differs from OpenVMS VAX Implementation On OpenVMS Alpha AXP, all local DSA devices use a controller letter of "A", regardless of the physical controller the device resides on. All local DSA disk devices are named DUAn or DJAn, where n is the unique disk unit number. All local DSA tape devices are named MUAn, where n is the unique tape unit number. 2-9 Running OpenVMS Alpha AXP 2.8 Running OpenVMS Alpha AXP Using a DEC 7000 AXP Series Computer The OpenVMS Alpha AXP local device naming scheme represents a change from OpenVMS VAX, where local DSA devices inherit the controller letter from the physical controller on which the device resides. Table 2-1 contrasts the new OpenVMS Alpha AXP local DSA device naming scheme with the OpenVMS VAX and DEC 7000 AXP Model 600 series console local DSA device naming schemes. Note that the DEC 7000 AXP Model 600 series console uses the OpenVMS VAX local DSA device naming scheme when referring to local DSA devices. As a result, you must specify the OpenVMS VAX local DSA device names when you use the DEC 7000 AXP Model 600 series console commands BOOT and SHOW DEVICE. Table_2-1_Device_Naming____________________________________ OpenVMS VAX and DEC 7000 AXP Model 600 OpenVMS Alpha Controller Where the Series Console Local AXP Local Disk_Resides__________Device_Naming_________Device_Naming__ PUA0 DUA0 DUA0 PUB0 DUB14 DUA14 PUC0__________________DUC115________________DUA115_________ As shown in Table 2-1, OpenVMS VAX names disk unit 14 on controller PUB0 as DUB14, while OpenVMS Alpha AXP names this unit DUA14. On OpenVMS Alpha AXP, use of a single controller letter requires that the unit number for each local DSA device be unique. Controller letters are used in device naming for hardware that artificially restricts unit number ranges. For example, SCSI controllers currently can only have disk unit numbers from 0 to 7 which almost precludes sufficient uniqueness for any large system requiring many disks. By contrast, modern DSA disks have a unit number range of 0 to 4000. In addition, the allocation class can be used to further differentiate device names. As a result, the OpenVMS Alpha AXP operating system does not add uniqueness to the device name via the controller letter. 2-10 Running OpenVMS Alpha AXP 2.8 Running OpenVMS Alpha AXP Using a DEC 7000 AXP Series Computer The following benefits result from the local DSA device naming change: o Device naming is more uniform. Local DSA device naming is now identical to the scheme used for local DSSI devices and remote DSA devices. o System management is simplified. Since all DSA devices now have unique unit numbers, an operator can unambiguously locate a device from among a system's disks using only the device's unit number. The operator need not be concerned whether a device with unit number 0 might be DUA0 or DUB0. o Dual-pathing of a device between two OpenVMS Alpha AXP systems with local controllers (unsupported in OpenVMS Alpha AXP Version 1.0) will be easier as a result of this device naming change. Dual-pathing is possible only if the device is named identically throughout the cluster. On OpenVMS VAX, the device name inherits the controller letter from the controller the device resides on. You have to take great care to place the device on identically named controllers on each OpenVMS VAX system so that the resulting device names are identical. With the OpenVMS Alpha AXP local DSA naming scheme, device names are insensitive to the controller the device resides on, and always use a controller letter of "A". In a future release of OpenVMS Alpha AXP, dual- pathing can be configured without regard to which local controller the dual-pathed device resides on. The local DSA device naming change on OpenVMS Alpha AXP may require that you make some changes. If local DSA devices are not already unique by unit number, then you may need to reconfigure DSA devices when moving from OpenVMS VAX to OpenVMS Alpha AXP. Local DSA physical device names that are hardcoded in command files or applications may also be affected by this change. 2-11 Running OpenVMS Alpha AXP 2.8 Running OpenVMS Alpha AXP Using a DEC 7000 AXP Series Computer 2.8.3 Small Computer Systems Interface Support The host ID is 7 for ports A and B of the KZMSA-AB SCSI controller. 2.9 Small Computer Systems Interface - DKDRIVER Restriction The small computer systems interface (SCSI) disk class driver (DKDRIVER) does not support data check operations for OpenVMS Alpha 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, will always indicate success. Data check functionality will be included in a future release of OpenVMS Alpha AXP. This restriction applies to all OpenVMS Alpha AXP hardware platforms. 2.10 TZK10 Drive - Restriction Attempts to write before the end of data when using a TZK10 drive (a quarter inch cartridge (QIC) standard drive) result in a write append error. This is a restriction in the QIC standard. The QIC standard allows drives to write at the end of data (append) or write the entire tape from beginning of tape (BOT), but does not allow data to be written before the end of data. This restriction applies to all OpenVMS Alpha AXP hardware platforms that support the TZK10 drive. 2-12 3 _________________________________________________________________ General Release Notes This chapter contains information that is of interest to all users of the OpenVMS Alpha AXP operating system. It includes information about commonly used utilities, text processing utilities, and user-environment testing. This chapter describes changes that affect the following areas of OpenVMS Alpha AXP: o DCL commands and utilities o DECTPU and EVE Version 3.1 o the Help Message utility (MSGHLP) o the Mail utility o the Sort/Merge utility o UETP device test support 3.1 DCL Commands and Utilities This section contains information about DCL commands and utilities. 3.1.1 APPEND/PROTECTION and COPY/PROTECTION Commands - Incorrect Behavior When you use the APPEND/PROTECTION command or the COPY /PROTECTION command and specify an output file's ownership parameter as world (W) and the access parameter as delete (D), the protection attributes of world and delete are set correctly. However, the default protection for the ownership parameter group (G) is inadvertantly modified to allow access of read (R), write (W), execute (E), and delete (D). We expect to fix this problem in a future release of OpenVMS Alpha AXP. 3-1 General Release Notes 3.1 DCL Commands and Utilities 3.1.2 EDIT Command - Change in Default Editor 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 OpenVMS Alpha AXP operating system. ______________________________________________________ This change was made to provide better system performance. TPU is a native image on OpenVMS Alpha AXP, whereas the EDT editor is a translated image. The EDIT command now invokes TPU with the EVE section file. Please see Section 3.2 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. 3.1.2.1 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. 3.1.2.2 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.) 3-2 General Release Notes 3.1 DCL Commands and Utilities 3.1.2.3 EVE and the EDT Keypad In EVE, you can select an EDT-like keypad by defining the OpenVMS Alpha AXP logical name EVE$KEYPAD to be EDT. See Section B.2.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 DECTPU and EVE Version 3.1 Notes On OpenVMS Alpha AXP, the default editor is EVE. See Section 3.1.2 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 Appendix B. 3.2.1 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 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. 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; 3-3 General Release Notes 3.2 DECTPU and EVE Version 3.1 Notes 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.3 Help Message Utility (MSGHLP) 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 VMS 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. See Appendix A for documentation of MSGHLP error messages and other new messages for this release. Features of Help Message Some Help Message features include: 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. 3-4 General Release Notes 3.3 Help Message Utility (MSGHLP) 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.4 Mail Utility - Change in Default Editor 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.1.2. See the OpenVMS User's Manual for information about selecting an editor. 3-5 General Release Notes 3.5 Sort/Merge Utility 3.5 Sort/Merge Utility The Sort/Merge utility (SORT/MERGE) runs as a native OpenVMS Alpha AXP image. All user-visible functions and interfaces of SORT/MERGE are identical to OpenVMS VAX SORT /MERGE, with the following exceptions: o There is no Common Data Dictionary (CDD) support, since CDD is not yet available on OpenVMS Alpha AXP. o During the course of SORT/MERGE development, the specification file format changed from the version 3 format to the current format. However, the current version of SORT/MERGE is incompatible with the specification files that are used on both OpenVMS VAX and OpenVMS Alpha AXP because the specification files are in the version 3 format. OpenVMS VAX provides a translation utility that converts the specification files from the version 3 format to the current format. OpenVMS Alpha AXP provides no such translation utility. To use SORT/MERGE on OpenVMS Alpha AXP, first you must convert the specification files on an OpenVMS VAX system by using the translation utility. Then move the translated files to the OpenVMS Alpha AXP system. This is a permanent restriction. o The behavior for reporting an invalid digit in a decimal string input differs between OpenVMS VAX and OpenVMS Alpha AXP. On OpenVMS VAX, you receive a reserved operand fault and a message that the value has been converted to a valid decimal string digit. On OpenVMS Alpha AXP, there is no indication of an invalid decimal digit or that a conversion has occurred. OpenVMS Alpha AXP does 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. 3-6 General Release Notes 3.6 UETP Restrictions 3.6 UETP Restrictions UETP's device, DECnet, and load phases are supported for OpenVMS Alpha AXP Version 1.0. However, the UETP Ethernet device test in the device phase fails with a bad parameter error if it is run when DECnet is running. If you want to run the Ethernet device test, do not start DECnet or LAT. Although the UETP cluster phase is supported in OpenVMS Alpha AXP Version 1.0, Digital discourages its use since VMSclusters are not supported. If the cluster phase is selected on a system that is not configured as a cluster member, the following message will be displayed: ** NOTE ** This system is not a member of a Cluster. The CLUSTER phase will not be run. ** **** ** Refer to the OpenVMS Alpha Version 1.0 Upgrade and Installation Manual for details about using UETP. 3-7 4 _________________________________________________________________ System Management Release Notes This chapter contains information that applies to system maintenance and management, performance management, and networking. This chapter describes the following topics: o Accounting utility o Authorize utility o AUTOGEN o Backup utility o CONSCOPY.COM command procedure not available o DECnet o Digital-supplied device drivers o Error Log Report Formatter (ERF) o Help Message utility o LAT o License Management Facility (LMF) o Monitor utility o Mount utility o OPCOM o Password generation o System Generation utility (SYSGEN) o System Management utility (SYSMAN) o Terminal Fallback facility (TFF) o VMScluster systems unsupported o Watch chip 4-1 System Management Release Notes For additional information about system management features and tasks, refer to A Comparison of System Management on OpenVMS Alpha and OpenVMS VAX. This manual compares OpenVMS system management on OpenVMS Alpha AXP and OpenVMS VAX computers. It is intended for experienced system managers who need to learn quickly how specific management tasks differ or remain the same on OpenVMS Alpha AXP and OpenVMS VAX computers. 4.1 Accounting Utility - Spurious Message 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 Alpha AXP Version 1.0, the following spurious message is displayed if no records match the request: %DEBUG-F-NOMSG, Message number 00020B54 This message can be safely ignored. No functionality is negatively affected. 4.2 Authorize Utility Authorize utility commands and parameters are identical on OpenVMS Alpha AXP and OpenVMS VAX. However, the default values for a number of OpenVMS Alpha AXP process limits and quotas are higher. See A Comparison of System Management on OpenVMS Alpha and OpenVMS VAX for more information. Digital reserves certain group user identification code (UIC) values on both OpenVMS Alpha AXP and OpenVMS VAX. 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-2 System Management Release Notes 4.3 AUTOGEN Command Procedure 4.3 AUTOGEN Command Procedure Use AUTOGEN to size system parameters after installing the operating system and after installing layered products. Digital also 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 Alpha Version 1.0 Upgrade and Installation Manual for information about running AUTOGEN after installing the OpenVMS Alpha AXP operating system. See A Comparison of System Management on OpenVMS Alpha and OpenVMS VAX and the OpenVMS System Manager's Manual for additional information about using AUTOGEN. 4.3.1 AUTOGEN - Problem During System Startup There have been instances where operational problems sometimes cause the OpenVMS Alpha AXP 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, you should 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. o In some cases, the values in MODPARAMS.DAT force AUTOGEN to set system parameters related to DECwindows incorrectly. 4-3 System Management Release Notes 4.3 AUTOGEN Command Procedure 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.3.2 System Parameters 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). See Section 6.6 for information about system parameters that were inadvertently omitted from Appendix K in the OpenVMS System Management Utilities Reference Manual. 4.3.2.1 Changes to System Parameters The Performance Optimization Tasks chapter of A Comparison of System Management on OpenVMS Alpha and OpenVMS VAX discusses system parameters on OpenVMS Alpha AXP Version 1.0. Section 5.1 and Section 5.2 of the document compare OpenVMS system parameters on OpenVMS Alpha AXP Version 1.0 and OpenVMS VAX Version 5.n. After the document was printed, some system parameter values were altered to better suit optimal performance on OpenVMS Alpha AXP systems: o PFCDEFAULT system parameter The default page-fault cluster size; specifies the maximum number of pagelets (pages, internally) that will be read from sections not specifying a cluster factor. Also applies to page-file pages. On OpenVMS VAX, the PFCDEFAULT maximum value is 127 512-byte pages. On OpenVMS Alpha AXP, the PFCDEFAULT maximum value is 2032 512-byte pagelets (127 8192-byte Alpha AXP pages). o WSINC system parameter The working set increment; sets the size in pagelets (pages, internally) to increase the working set size to compensate for a high page-fault rate. On OpenVMS VAX, the WSINC default value is 150 512-byte pages. 4-4 System Management Release Notes 4.3 AUTOGEN Command Procedure On OpenVMS Alpha AXP, the WSINC default value is 2400 512-byte pagelets (150 8192-byte Alpha AXP pages). The WSINC system parameter is dynamic, which means that you can alter its value without having to reboot the system. You might want to experiment with larger WSINC values. A large WSINC value might have a positive effect on the performance of memory-intensive applications. Also consider experimenting with the WSEXTENT process quota for processes that use memory-intensive applications. As noted in the System Setup Tasks chapter of A Comparison of System Management on OpenVMS Alpha and OpenVMS VAX, the default value for the WSEXTENT process quota was increased from VAX to Alpha AXP. On OpenVMS VAX, the WSEXTENT default value is 512 512- byte pages. On OpenVMS Alpha AXP, the WSEXTENT default value is 16384 512-byte pagelets (1024 8192-byte pages). Even higher WSEXTENT process quota values might be appropriate on Alpha AXP computers with large amounts of memory, such as 256MB. In general, you want to avoid situations where the WSEXTENT process quota or the WSINC system parameter is limiting the required (and available) working set memory. o PFRATH system parameter The page-fault rate's high threshold; sets the upper page-fault rate threshold for incrementing automatic working set size. On OpenVMS VAX, the PFRATH default value is 120 page faults every 10 seconds. On OpenVMS Alpha AXP, the PFRATH default value is reduced to 8 page faults every 10 seconds. The reduction was made on OpenVMS Alpha AXP because of the larger page size. See A Comparison of System Management on OpenVMS Alpha and OpenVMS VAX for information about the relative sizes on a VAX page (512 bytes), an Alpha AXP pagelet (also 512 bytes), and an Alpha AXP page (8192 bytes on the initial set of Alpha AXP computers). o MPW_WRTCLUSTER system parameter 4-5 System Management Release Notes 4.3 AUTOGEN Command Procedure The number of pages written per I/O from the modified page list; specifies the number of pages to attempt to write from the modified page list as a single contiguous I/O transfer to disk. On OpenVMS VAX, the MPW_WRTCLUSTER default value and maximum value is 120 512-byte pages; its minimum value is 16 512-byte pages. On OpenVMS Alpha AXP, the MPW_WRTCLUSTER default value is 64 8192-byte pages; its maximum value is 512 8192- byte pages; and its minimum value is 16 8192-byte pages. 4.3.2.2 AWSTIME and QUANTUM System Parameters 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.3.2.3 PHYSICAL_MEMORY System Parameter On OpenVMS Alpha AXP, the PHYSICAL_MEMORY system parameter replaces the PHYSICALPAGES system parameter found on OpenVMS VAX. 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: Part II for information about how to calculate the proper system dump file size for your system. 4.3.2.4 System Parameters and Performance Measurements The chapter on performance optimization tasks and Appendix A in A Comparison of System Management on OpenVMS Alpha and OpenVMS VAX contain information about system tuning tips that can be used to measure and enhance the performance of your OpenVMS Alpha AXP system. 4-6 System Management Release Notes 4.3 AUTOGEN Command Procedure 4.3.2.5 System Parameters That Have Been Removed The following system parameters are not present on OpenVMS Alpha AXP systems: IRPCOUNT IRPCOUNTV LRPCOUNT LRPCOUNTV LRPSIZE SRPCOUNT SRPCOUNTV These parameters were removed as part of the changes for automated pool management. Automated pool management offers simplified system management, improved performance, and reduced overall pool memory requirements. See A Comparison of System Management on OpenVMS Alpha and OpenVMS VAX for more information about automated pool management. 4.4 Backup Utility - Restrictions The following restrictions apply to the Backup utility on OpenVMS Alpha AXP: o You cannot specify data compaction for SCSI tape drives. The Backup utility on OpenVMS Alpha AXP does not support data compaction for SCSI tape drives. The BACKUP command qualifier /MEDIA_FORMAT=COMPACTION is ignored for these devices. Digital expects to remove this restriction in a future release of OpenVMS Alpha AXP. o You cannot build a standalone backup kit on the following media types: - A magnetic tape OpenVMS Alpha AXP does not support booting standalone from magnetic tape. - A disk smaller than 20Mb This is the minimum disk size needed to build an OpenVMS Alpha AXP standalone backup kit. o You cannot back up or restore an OpenVMS Alpha AXP system disk from an OpenVMS VAX computer. 4-7 System Management Release Notes 4.4 Backup Utility - Restrictions OpenVMS Alpha AXP system disks use a specialized version of the boot block. The current version of the Backup utility on OpenVMS VAX does not recognize this boot block. Digital expects to remove this restriction in a future release of OpenVMS VAX. 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 4.5 CONSCOPY.COM Procedure Not Available OpenVMS VAX provides the CONSCOPY.COM command procedure, which system managers can use to create a backup copy of the original console volume. The OpenVMS VAX installation supplies the procedure in SYS$UPDATE. The CONSCOPY.COM procedure is not available at this time for OpenVMS Alpha AXP computers. 4.6 DECnet for OpenVMS Alpha AXP - Restrictions The following restrictions apply to DECnet for OpenVMS Alpha AXP Version 1.0: o You must start DECnet before you start LAT. If you start DECnet after you start LAT, all existing LAT connections are terminated, and you might be unable to reconnect using LAT. o There is no routing support. o Some line types are unsupported. OpenVMS Alpha AXP Version 1.0 nodes can connect to a local area network (LAN) only via Ethernet lines or FDDI lines. DECnet communication over Computer Interconnect (CI) lines is not supported. There also is no support for DIGITAL Data Communications Message Protocol (DDCMP) lines. Because DDCMP lines are unsupported, the DCL command SET TERMINAL /PROTOCOL=DDCMP /SWITCH=DECNET also is unsupported on OpenVMS Alpha AXP systems. 4-8 System Management Release Notes 4.6 DECnet for OpenVMS Alpha AXP - Restrictions o The DECnet cluster alias feature is unavailable, due to the lack of VMScluster support. For additional information, see the chapter on networking management tasks in A Comparison of System Management on OpenVMS Alpha and OpenVMS VAX. 4.7 Digital-Supplied Device Drivers - File Name Format Change All device drivers supplied by Digital on OpenVMS Alpha AXP use the following format: facility-name$xxDRIVER.EXE The device drivers included on the OpenVMS Alpha AXP kit use SYS for the facility-name. On OpenVMS VAX, no facility prefix is present or permitted for device drivers. They are simply named xxDRIVER.EXE. On OpenVMS Alpha AXP, non-Digital device drivers still can be called xxDRIVER.EXE. 4.8 Error Log Report Formatter (ERF) The Error Log Report Formatter (ERF) supports OpenVMS Alpha AXP error logs. OpenVMS VAX error logs are not supported. ERF is a native port of the OpenVMS VAX version. 4.8.1 Restrictions and Limitations The following restrictions apply to ERF in this version of OpenVMS Alpha AXP: o If, by mistake, an OpenVMS VAX error log is analyzed, the results would be unpredictable since OpenVMS 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 AXP Model 600 computer. o There is no FRU entry for the DEC 3000 AXP Model 400 computer. 4-9 System Management Release Notes 4.9 Help Message Utility (MSGHLP) Restriction 4.9 Help Message Utility (MSGHLP) Restriction Features of the new Help Message utility are summarized in Section 3.3. Information about customizing the Help Message database is provided in 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, you might also be able to reuse some .MSGHLP files to insert comments to existing messages. ______________________________________________________ 4.10 LAT Notes OpenVMS Alpha AXP supports the LAT software when running on a suitably configured system. See the OpenVMS System Manager's Manual: Part II for more information about starting and using the LAT software. ________________________ Note ________________________ You must start DECnet before you start LAT. If you start DECnet after you start LAT, all existing LAT connections are terminated and in some cases you are unable to reconnect using LAT. Reestablish the connection from VXT, using the CONNECT command. ______________________________________________________ Always start LAT from the SYSTEM account, since this account typically has appropriate privileges and quotas. 4-10 System Management Release Notes 4.11 License Management Facility (LMF) 4.11 License Management Facility (LMF) Availability Product Authorization Keys (PAKs) are available for OpenVMS Alpha AXP. An OpenVMS Alpha 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 OpenVMS Alpha AXP systems. However, they can safely reside in a license database (LDB) shared by both OpenVMS VAX and OpenVMS Alpha AXP systems. Since LMF for OpenVMS Alpha AXP is capable of handling all types of PAKs, including those for OpenVMS VAX, Digital recommends that you perform your LDB tasks using the OpenVMS Alpha AXP LMF. Availability PAKs for OpenVMS VAX (availability PAKs without the ALPHA option) will not load on OpenVMS Alpha AXP systems. Only those availability PAKs containing the ALPHA option will load on OpenVMS Alpha 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 OpenVMS VAX and OpenVMS Alpha AXP systems. Avoid using the following LICENSE commands from an OpenVMS 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 OpenVMS Alpha AXP availability PAKs look disabled to an OpenVMS VAX system. Never use the DELETE/STATUS=DISABLED command from an OpenVMS VAX 4-11 System Management Release Notes 4.11 License Management Facility (LMF) system on an LDB that contains OpenVMS Alpha AXP PAKs. If you do, all OpenVMS Alpha 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 OpenVMS Alpha AXP PAK while using an OpenVMS VAX system, the PAK and the database will probably not be adversely affected. Repeat the command using LMF running on an OpenVMS Alpha AXP system, and the PAK should return to a valid state. If you neglect to repeat the command using LMF on an OpenVMS Alpha AXP system, the OpenVMS Alpha AXP system will be mostly unaffected. At worst, an OpenVMS Alpha AXP PAK that you intended to disable will remain enabled. Only OpenVMS Alpha AXP LMF can disable an OpenVMS Alpha 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 an OpenVMS VAX system, the following serious problems may result: o Since OpenVMS Alpha AXP PAKs look disabled to an OpenVMS VAX system, they are normally ignored at load time by OpenVMS VAX systems. However, if one of the commands listed above is entered from an OpenVMS VAX system and the PAK information is not set to a valid state by an OpenVMS Alpha AXP system, there is a chance the OpenVMS VAX system will attempt to load the OpenVMS Alpha AXP PAK. Since the OpenVMS VAX system will be unable to load the PAK, the OpenVMS VAX LMF will report an error. o Even if a valid OpenVMS VAX PAK for the affected product is in the LDB, it too may not load. In this case, system users might be denied access to the product. If the PAK cannot be restored to a valid state because all OpenVMS Alpha AXP systems are inaccessible for any reason, use your OpenVMS VAX system to disable the OpenVMS Alpha AXP PAK. This prevents your VAX system from attempting to load the OpenVMS Alpha AXP PAK. In a future release of OpenVMS VAX LMF, Digital expects to remove these command restrictions. 4-12 System Management Release Notes 4.11 License Management Facility (LMF) See the VMS License Management Utility Manual for more information about using LMF. 4.12 Monitor Utility The Monitor utility (MONITOR) for OpenVMS Alpha AXP Version 1.0 is nearly identical to that found on OpenVMS VAX. However, you should read A Comparison of System Management on OpenVMS Alpha and OpenVMS VAX for information about the differences between MONITOR for OpenVMS Alpha AXP and MONITOR for OpenVMS VAX. Some significant differences are: o On OpenVMS Alpha AXP, the POOL class does not exist. Automated pool management is used to enhance system performance and reduce overall pool memory requirements. See A Comparison of System Management on OpenVMS Alpha and OpenVMS VAX for information about automated pool management. o Although VMSclusters and DECdtm are unsupported in OpenVMS Alpha AXP, the MONITOR commands MONITOR CLUSTER, MONITOR SCS, and MONITOR TRANSACTION are included. Refer to A Comparison of System Management on OpenVMS Alpha and OpenVMS VAX for more information about specific MONITOR commands. Also refer to OpenVMS System Manager's Manual: Part II for more information about the Monitor utility. 4.12.1 Restrictions The following restrictions apply to the Monitor utility in this version of OpenVMS Alpha AXP: o When you enter an invalid command that causes a secondary error code from the command language interpreter (CLI), the Monitor utility might display the invalid portion of the command incorrectly. For example, when you enter the MONITOR/FOO command (where FOO is an invalid qualifier), the Monitor utility should display the following error message: %MONITOR-E-ERRPARSE, error parsing command -CLI-W-IVQUAL, unrecognized qualifier - check validity, spelling, and placement \FOO\ 4-13 System Management Release Notes 4.12 Monitor Utility However, on OpenVMS Alpha AXP Version 1.0, the invalid qualifier FOO does not appear between the backslashes that follow the error message. You might also see random text in that location, as well as only one backslash. The Monitor utility might display a message similar to the following: %MONITOR-E-ERRPARSE, error parsing command -CLI-W-IVQUAL, unrecognized qualifier - check validity, spelling, and placement \\ We expect to fix this problem in a future release of OpenVMS Alpha AXP. o The MONITOR MSCP command is available with OpenVMS Alpha AXP Version 1.0, but it displays zeros because the MSCP server is unsupported at this time. 4.13 Mount Utility In this version of OpenVMS Alpha AXP, the MOUNT command is supported for tape and disk volumes. 4.13.1 Restrictions The MOUNT command is not supported for shadowed volumes or for volume sets. The MOUNT/CLUSTER command is also unsupported. 4.14 Operator Communication Manager (OPCOM) OPCOM starts automatically from STARTUP. All major functionality is present in OpenVMS Alpha AXP Version 1.0, with the exception of cluster operations. See the OpenVMS System Manager's Manual for more information about OPCOM. 4.15 Password Generation On OpenVMS Alpha AXP, the password generation algorithm allows for future use of non-English password generation databases. Because of this, the password generation logic does not return information necessary to perform English word hyphenation. As a result, the SET PASSWORD command cannot display a hyphenated word list, as it does on OpenVMS VAX. This is a permanent change in behavior on OpenVMS Alpha AXP. 4-14 System Management Release Notes 4.16 Privileges, Protections, and Quotas 4.16 Privileges, Protections, and Quotas The default values for a number of OpenVMS Alpha AXP process limits and quotas are higher than those on OpenVMS VAX. Refer to the chapter on system setup tasks in A Comparison of System Management on OpenVMS Alpha and OpenVMS VAX for more information about default values for process limits and quotas. 4.17 System Generation Utility - Unsupported Commands All I/O subsystem configuration commands have been removed from the System Generation (SYSGEN) utility. The System Management (SYSMAN) utility's I/O configuration commands are used for all I/O subsystem tuning and device driver loading. Refer to the OpenVMS System Management Utilities Reference Manual for more information about SYSMAN I/O subsystem configuration commands. On OpenVMS Alpha AXP, the following commands are no longer supported in SYSGEN: AUTOCONFIGURE CONFIGURE CONNECT LOAD MSCP RELOAD SHARE SHOW/ADAPTER SHOW/CONFIGURATION SHOW/DEVICE SHOW/DRIVER SHOW/UNIBUS 4.18 System Management Utility The following section describes the I/O configuration support that has been added to the System Management utility (SYSMAN). These functions are provided by SYSGEN on OpenVMS VAX systems. 4.18.1 I/O Configuration Support in SYSMAN On OpenVMS Alpha AXP, the SYSMAN utility is used to connect devices, load I/O device drivers, and display configuration information useful for debugging device drivers. All SYSMAN commands that control and display the I/O configuration of an OpenVMS Alpha AXP system must be introduced with the prefix IO. For example, to autoconfigure a system, enter the following commands: $ RUN SYS$SYSTEM:SYSMAN SYSMAN> IO AUTOCONFIGURE 4-15 System Management Release Notes 4.18 System Management Utility For a discussion of the differences between I/O subsystem configuration commands in OpenVMS Alpha AXP SYSMAN and OpenVMS VAX SYSGEN, see the chapter on system setup tasks in A Comparison of System Management on OpenVMS Alpha and OpenVMS VAX. The OpenVMS System Management Utilities Reference Manual describes the SYSMAN I/O commands. 4.19 Terminal Fallback Facility (TFF) The Terminal Fallback facility (TFF) includes a fallback driver (SYS$FBDRIVER.EXE), a shareable image (TFFSHR.EXE), a terminal fallback utility (TFU.EXE), and a fallback table library (TFF$MASTER.DAT). o To start TFF, invoke the TFF startup command procedure located in SYS$MANAGER, as follows: $ @SYS$MANAGER:TFF$SYSTARTUP.COM o To enable fallback or to change fallback characteristics, invoke the terminal fallback utility (TFU), as follows: $ RUN SYS$SYSTEM:TFU TFU> o To enable default fallback to the terminal, issue the following DCL command: $ SET TERMINAL/FALLBACK OpenVMS Alpha AXP TFF differs from OpenVMS VAX TFF in the following areas: o On OpenVMS Alpha AXP, the TFF fallback driver is named SYS$FBDRIVER.EXE. On OpenVMS VAX, the TFF fallback driver is named FBDRIVER.EXE. o On OpenVMS Alpha AXP, TFF is capable of handling 16- bit character fallback. The OpenVMS Alpha AXP fallback table library (TFF$MASTER.DAT) contains two more 16-bit character tables than the OpenVMS VAX library. Table 4-1 describes these additional tables. 4-16 System Management Release Notes 4.19 Terminal Fallback Facility (TFF) Table_4-1_TFF_Character_Tables_____________________________ Table_Name_______Base___Description________________________ HANYU_TELEX CNS CNS 11643 for MITAC TELEX-CODE terminal HANGUL_DS________KS_____KS_for_DOOSAN_200_terminal_________ These two tables are mainly used by the Asian region. Also, the table format was changed due to the support of 16-bit character fallback. o On OpenVMS Alpha AXP, the TFU command SHOW STATISTICS does not display the size of the fallback driver (SYS$FBDRIVER.EXE). RT terminals are not supported by TFF. Please refer to the VMS Terminal Fallback Utility Manual for more information about the Terminal Fallback facility. ________________________ Note ________________________ TFFSHR has been removed from IMAGELIB, since it is not a documented, user-callable interface. The image is still available in SYS$LIBRARY:. ______________________________________________________ 4.20 VMScluster Systems Unsupported on OpenVMS Alpha AXP OpenVMS Alpha AXP computing systems do not support VMScluster capabilities at this time. 4.20.1 Lack of Support for VMSclusters Impacts Maintenance The lack of support for VMSclusters in OpenVMS Alpha AXP Version 1.0 affects a number of OpenVMS maintenance commands and features: o MOUNT/CLUSTER command You cannot mount a volume for clusterwide access. o DECnet cluster alias This feature is unsupported. See the chapter on network management tasks in A Comparison of System Management on OpenVMS Alpha and OpenVMS VAX for more information. 4-17 System Management Release Notes 4.20 VMScluster Systems Unsupported on OpenVMS Alpha AXP o CLUSTER_CONFIG.COM procedure is unsupported. ________________________ Note ________________________ Standalone systems that use DSSI disks might need the CLU_MOUNT_DISK.COM procedure that is supplied with the OpenVMS Alpha AXP kit. The procedure is not only for VMScluster environments. ______________________________________________________ Although VMSclusters are unsupported on OpenVMS Alpha AXP Version 1.0, a number of cluster-related commands are available. The actions performed or the information returned by the commands in the following list correctly reports on an OpenVMS Alpha AXP node as if it were a standalone system: o SYSMAN utility commands that control clusterwide commands or display cluster information: - SET ENVIRONMENT/CLUSTER command - CONFIGURATION SET CLUSTER_AUTHORIZATION command - CONFIGURATION SHOW CLUSTER_AUTHORIZATION command - SHOW/CLUSTER command o MONITOR CLUSTER command o SET CLUSTER command ________________________ Note ________________________ You can use the MONITOR SCS and SHOW CLUSTER commands for: - Standalone DEC 4000 AXP computers running OpenVMS Alpha AXP software and using DSSI buses - Standalone DEC 7000 AXP computers running OpenVMS Alpha AXP software and using KDM ports. ______________________________________________________ 4-18 System Management Release Notes 4.21 Watch Chip - Change in Time Range 4.21 Watch Chip - Change in Time Range OpenVMS AXP systems maintain their system time during power failures and system downtime with a watch chip (BBW). This chip replaces the time-of-day register (TODR) used on OpenVMS VAX systems. The BBW chip only allows a range of one century, placing a greater constraint on the dates that can be accepted by the $SETIME service and SET TIME DCL commands. What used to be a wider date range on OpenVMS VAX systems is now limited to the century between 1957 and 2056. In addition, a set of sanity checks has been added to the system boot routines to validate the format of the BBW and the values put into it by previous system boots. These checks will recognize out-of-bounds values. When the time is known to be earlier than the last time modification or greater than 5 years in the future, you will be prompted to enter the time at the console prompt. Such situations may occur when an Alpha AXP computer, after running another operating system such as OSF, is rebooted using the OpenVMS Alpha AXP operating system. 4-19 5 _________________________________________________________________ Programming Release Notes This chapter contains information of particular interest to programmers, such as tools, utilities, system services, and the file system. This chapter describes the following features: o The OpenVMS Debugger o DECthreads o The executive o The file system o IEEE floating point standard o The linker o MACRO-32 Compiler for OpenVMS Alpha AXP o Run-Time Libraries o STARLET Data Structures and Definitions For C Programmers o The SUMSLP utility o System Dump Analyzer (SDA) utility o System services o The traceback handler o Translated Image Environment (TIE) o Translated executables, images, and related files 5-1 Programming Release Notes 5.1 OpenVMS Debugger Notes 5.1 OpenVMS Debugger Notes The following sections describe the requirements, known problems, and restrictions present in this version of the OpenVMS Debugger. The Delta/XDelta utility (DELTA/XDELTA) is also available for debugging. See the OpenVMS Delta/XDelta Debugger Manual for details on using the Delta/XDelta utility. 5.1.1 Language Support In this release, the debugger provides full support for the DEC C and FORTRAN languages. Partial support is provided for DEC Ada. All other languages are untested and unsupported. If you use an unsupported language, you can test debugger response to your language by entering a SET LANGUAGE language-keyword command. See the OpenVMS Debugger Manual for more information about the SET LANGUAGE command. 5.1.2 Known Problems and Restrictions This section describes known problems and restrictions that affect the debugger in OpenVMS Alpha AXP Version 1.0. For complete information on debugger functionality, see the OpenVMS Debugger Manual for OpenVMS Alpha AXP Version 1.0. 5.1.2.1 Debugging Translated Images The debugger does not support attempts to debug translated images. If you must debug a translated image, use the Delta /XDelta Debugger. For more information on the Delta/XDelta Debugger, see the OpenVMS Delta/XDelta Debugger Manual. Using the OpenVMS Debugger in a process where any translated shareable image (for example, EDTSHR) is active is not supported. 5.1.2.2 Debugging Installed Resident Images The debugger does not support attempts to debug installed resident images. 5-2 Programming Release Notes 5.1 OpenVMS Debugger Notes 5.1.2.3 Debugging Inlined Routines The debugger does not support attempts to debug inlined routines. If you attempt to debug an inlined routine, the debugger issues a message stating that it cannot access the routine, as shown in the following example: %DEBUG-E-ACCESSR, no read access to address 00000000 To work around this problem, compile your program with the /NOOPTIMIZE qualifier. 5.1.2.4 Debugging Global Sections The debugger does not support setting watchpoints on variables whose addresses are in global sections. If you attempt to set a watchpoint on a location in a global section, the debugger issues a message rejecting the watchpoint, as shown in the following example: %DEBUG-E-BADWATCH, cannot watch protect address 'address-value' 5.1.2.5 Debugging Register Frame Procedures or No Frame Procedures The debugger does not fully support attempts to debug Register Frame Procedures or No Frame Procedures. If you issue the STEP/OVER or STEP/RETURN commands for these procedures, unexpected results might occur. For more information on Register Frame Procedures and No Frame Procedures, see the OpenVMS Calling Standard. 5.1.2.6 Compilation with /DEBUG Qualifier If your module is not compiled with the /DEBUG qualifier, the debugger will be unable to symbolize your module. 5.1.2.7 Complex Variables in FORTRAN Programs The debugger cannot evaluate expressions that contain complex variables. (Currently, FORTRAN is the only supported language that contains complex variables.) To work around this problem, examine the complex variable and then evaluate the expression using the real and imaginary parts of the expression obtained from the EXAMINE command. 5-3 Programming Release Notes 5.1 OpenVMS Debugger Notes 5.1.2.8 Concealed Rooted-Directory Logical Names for Source Files If you use a rooted-directory logical name to specify the location of a source file when compiling a program with the /DEBUG qualifier, make sure that the rooted- directory logical name is concealed. You must include the /TRANSLATION_ATTRIB=CONCEALED qualifier in your logical name definition, as follows: DEFINE /TRANSLATION_ATTRIB=CONCEALED root_dir_log_name disk:[dir.] If the rooted-directory logical name is not concealed, and you move the source file to another directory after compilation, you will be unable to use the debugger SET SOURCE command to specify the new location of the source file. 5.1.2.9 Ctrl/C Interruption On this version of the debugger, you cannot interrupt program execution with Ctrl/C when execution of the program is in system space. 5.1.2.10 HALT Instructions The debugger cannot step past a HALT instruction. To work around this problem, issue a GO command to execute the HALT. 5.1.2.11 CALL Command Problems and Restrictions The following CALL command problems and restrictions appear in this release: o When you issue a CALL command before another outstanding CALL command has completed (that is, before the "value returned" message appears), the debugger hangs. To work around this restriction, continue execution of the program with the STEP or GO commands until the previous CALL command completes. o When you issue a CALL command from an exception break, all breakpoints, tracepoints, and watchpoints in the called routine are triggered. o You cannot debug routines that are activated before the routine activated by a CALL command. For example, suppose your program is stopped in routine MAIN, and you set a breakpoint in routine SORT. You issue the debugger 5-4 Programming Release Notes 5.1 OpenVMS Debugger Notes CALL SORT command. While debugging routine SORT, you cannot debug routine MAIN. You must first return from the call to routine SORT. 5.1.2.12 DEPOSIT/TYPE Command with C Programs When debugging a C program, you cannot use the DEPOSIT/TYPE command if the type specified is a mixed or lowercase name. For example, suppose the program has a function like the following: xyzzy_type foo () { xyzzy_type z; z = get_z (); return (z); } If you try to enter the following command, the debugger issues a message that it cannot find the type "xyzzy_type": DBG> DEPOSIT/TYPE=(xyzzy_type) z="whatever" 5.1.2.13 DEPOSIT and EXAMINE Commands with Floating-Point Values If you attempt to examine or deposit to a D_FLOAT or G_ FLOAT floating-point value that is located in a register, your operation produces an incorrect result. To work around this problem, compile your program with the /FLOAT=IEEE qualifier, which creates an S_FLOAT variable. When you issue the EXAMINE or DEPOSIT command, append the /T_FLOAT qualifier. (If an S_FLOAT variable is stored in a register, the Alpha architecture converts the variable to T_FLOAT.) 5.1.2.14 EXAMINE Command Problems and Restrictions The following EXAMINE command problems and restrictions appear in this release: o The first longword of a routine cannot be examined. o When you place a breakpoint at a particular instruction, you cannot examine that instruction. o When program execution is suspended in system space, the command EXAMINE PC displays an incorrect value for the high order longword of the PC. 5-5 Programming Release Notes 5.1 OpenVMS Debugger Notes o When you issue an EXAMINE/PS command, the debugger returns a syntax error. To work around this problem, reenter the command as EXAMINE PS. o When you issue an EXAMINE/SOURCE command for a routine, the debugger displays incorrect instructions. To work around this problem, enter the following commands: - SHOW SYMBOL/ADDRESS routine-name to determine the correct code address for the routine - EXAMINE/SOURCE code-address-value to display the correct instructions o When the symbol to which an offset is applied is a routine, the debugger does not compute symbol offsets correctly. For example, if CALCULATE is a routine name, then locations of the form "CALCULATE + n" have an incorrect value computed for n. o When you issue the command EXAMINE LABEL[n] or EXAMINE LABEL(n), where LABEL is a label for a code location and n is an integer, an access violation error results. (Note that this problem does not occur when the label marks the start of data storage, as in a MACRO program.) 5.1.2.15 SET IMAGE Command Limitation For some large programs with many program sections (usually caused by many FORTRAN routines with many COMMON blocks), the debugger might receive an internal error while processing a SET IMAGE command. In such cases, the image cannot be debugged. 5.1.2.16 SET WATCH Command Caution On OpenVMS Alpha AXP Version 1.0 systems, all watchpoints set by the debugger are non-static watchpoints. That is, no matter where the watched value is stored, the debugger traces every instruction and checks the value of each watched variable after each instruction. The default for non-static watchpoints is /OVER. For more information on non-static watchpoints and the SET WATCH/INTO and SET WATCH /OVER commands, see the OpenVMS Debugger Manual. 5-6 Programming Release Notes 5.1 OpenVMS Debugger Notes 5.1.2.17 SHOW BREAK and SHOW TRACE Command Limitations SHOW BREAK and SHOW TRACE do not display individual instructions when the break or trace is on a particular class of instruction (such as SET BREAK/CALL or SET BREAK /RETURN). 5.1.2.18 STEP/INTO Command and User Exception Handlers When execution is stopped at an exception break, STEP/INTO does not transfer control to a user exception handler. To work around this problem, set a breakpoint on the handler. 5.1.2.19 STEP/OVER Command Error With Recursive Calls When you issue a STEP/OVER command at a recursive call to the routine that is currently executing, a SYSTEM-F-OPCDEC error or an internal debugger error results. To work around this problem, either issue the STEP/OVER command at the initial call to the recursive routine or issue the STEP /INTO command at each recursive call of the routine. 5.1.2.20 STEP/OVER Command Error With One-Line Program Loops When you issue the STEP/OVER command at a program loop that is coded on a single source line, and that source line also contains a routine call, the debugger steps into the called routine instead of stepping to the next source line. In the following example, if you issue the STEP/OVER command when execution is stopped at the FOR loop, the debugger steps into SQUARE instead of stepping to the J assignment statement: For (i=0;i<10;i++) SQUARE(i); J=6; To work around this problem, either set a temporary breakpoint on the line following the FOR loop (in the previous example, J=6) or move the routine call to a separate line, as follows: For (i=0;i<10;i++) SQUARE(i); 5-7 Programming Release Notes 5.1 OpenVMS Debugger Notes 5.1.2.21 $WAKE Call Followed by $HIBER Call If a program, running under the two-process or multiprocess debugger, issues a $WAKE call followed by a $HIBER call, the user application hibernates. 5.1.2.22 DCL ANALYZE/PROCESS_DUMP Command and Zero Program Counter If you attempt to invoke the debugger with the DCL ANALYZE /PROCESS_DUMP command, and the dump file you are analyzing describes an image that received an access violation with the program counter at zero, the debugger cannot complete startup. A register dump occurs, and you return to the DCL prompt. 5.1.2.23 Changed Watchpoint Locations During System Service Calls If a watched location changes during a system service routine, you will be notified that the watchpoint occurred. However, the stack will show one or more debugger frames on top of the frame or frames for your program. To work around this problem, enter one or more STEP/RETURN commands to return to your program. 5.1.2.24 STEP Command and Asynchronous System Trap (AST) Routines If you set a breakpoint in an AST routine, and an AST fires during the execution of a STEP command, the STEP command will (incorrectly) complete when the breakpoint in the AST routine triggers. When the AST routine completes, and control returns to the point where the AST fired, the debugger receives an access violation. If you continue execution from this access violation, the AST routine is re-executed and the access violation occurs again. To work around this problem, use breakpoints (but not the STEP command) to control the execution of your program when you set breakpoints in AST routines. 5.1.2.25 STEP Command into System Service Calls If you attempt to single-step into a system service call, an access violation results. 5-8 Programming Release Notes 5.1 OpenVMS Debugger Notes 5.1.2.26 LCK$M_DEQALL Modifier in $DEQ System Service Call When an application includes the LCK$M_DEQALL modifier in a $DEQ system service call, this modifier breaks communication links between the portion of the debugger in the user process (the kernel) and the debugger main process. The result is that the user's process stays in hibernate (HIB) state. To work around this problem, debug these application programs using the limited one-process mode, rather than the default or the multiprocess mode. To set up one-process mode, issue the following command: $ DEFINE DBG$PROCESS NONE 5.1.2.27 SHOW CALLS Command Can Display System Call Frames After you issue a SHOW CALLS command, the output may include system call frames in addition to the user call frames associated with your program. System call frames appear in the following circumstances: - When an exception occurs - When an asynchronous system trap occurs - When a watchpoint occurs in system space The display of system call frames does not indicate a problem. In a future release of OpenVMS Alpha AXP, display of these frames will be suppressed, so that behavior on OpenVMS Alpha AXP parallels the behavior on OpenVMS VAX. 5.2 DECthreads DECthreads, including the DECthreads Library routines, is executable in OpenVMS Alpha AXP. The Guide to DECthreads provides additional detailed information. 5.2.1 Restrictions The DECthreads routines cma_thread_exit_error, cma_thread_ exit_normal, and pthread_exit should terminate the calling thread only. However, these routines erroneously cause the process to terminate when they are called in the initial thread. This problem will be corrected in a future version of OpenVMS Alpha AXP. 5-9 Programming Release Notes 5.3 DECwindows Motif for OpenVMS AXP Version 1.1 5.3 DECwindows Motif for OpenVMS AXP Version 1.1 See the DECwindows Motif for OpenVMS AXP Version 1.1 Installation Guide for information about the DECwindows Motif for OpenVMS AXP layered product. 5.4 Executive Notes The following sections provide information about the executive for OpenVMS Alpha AXP Version 1.0. 5.4.1 Spinlock Changes The rank values for all current static spinlocks have been spread out to allow for future additions. All known references to the JIB dynamic spinlock have been replaced with interlocked code sequences, allowing the spinlock itself to be eliminated. 5.4.2 SYS.EXE Renamed to SYS$BASE_IMAGE.EXE The loadable executive image SYS.EXE has been renamed SYS$BASE_IMAGE.EXE. By renaming the loadable executive image SYS.EXE to SYS$BASE_IMAGE.EXE, the name conforms to our naming standards which state that SYS$ should prefix the image name. 5.4.3 Executive Functions Not Included in OpenVMS Alpha AXP Support for PDP-11 compatibility mode will not be included in this release or in future releases of OpenVMS Alpha AXP. In addition, symmetric multiprocessing (SMP) support is not available in OpenVMS Alpha AXP Version 1.0. 5.5 File System Notes All basic disk file system support is present in OpenVMS Alpha AXP Version 1.0. ODS-1 format disks will not be supported on OpenVMS Alpha AXP, and multi-volume file sets will not be supported on OpenVMS Alpha AXP Version 1.0. 5-10 Programming Release Notes 5.5 File System Notes 5.5.1 File Definition Language The File Definition Language (FDL) facility is included in this version of OpenVMS Alpha AXP. FDL provides FDLSHR.EXE and CREATEFDL.EXE, the latter invoked with CREATE/FDL. In addition, OpenVMS Alpha AXP includes the Edit/FDL (EDIT /FDL) utility. You can use EDIT/FDL to create new files, but you might not be able to edit existing files. 5.5.2 National Character Set The National Character Set (NCS) runs as a native OpenVMS Alpha AXP image. All user-visible functions and interfaces of NCS are identical to OpenVMS VAX NCS. An NCS library created on OpenVMS VAX is supported on OpenVMS Alpha AXP. 5.6 IEEE Floating Point Standard For OpenVMS Alpha AXP Version 1.0, a subset of the IEEE Standard for Binary Floating-Point Arithmetic (number 754- 1985) as defined by the OpenVMS Alpha AXP architecture is available. However, the complete IEEE implementation, which requires additional software support as described in the Alpha Architecture Reference Manual, is not yet available in OpenVMS Alpha AXP. The Alpha Architecture Reference Manual (order number EY-L520E-DP) can be ordered through Digital Press. The following restrictions apply to features defined by the IEEE floating point standard: o No support for optional IEEE software trap enable /disable modes o Supports infinity arithmetic only by trapping when an infinity operand is encountered and when an infinity is to be created from infinity operands by overflow or division by zero o Supports NaNs only by trapping when a NaN operand is encountered and when a NaN is to be created o No provision for IEEE exception trap behavior; the hardware traps on a superset of the IEEE-required conditions 5-11 Programming Release Notes 5.7 Linker Utility - Restriction 5.7 Linker Utility - Restriction The OpenVMS Alpha AXP Version 1.0 linker cannot overlay program sections that are referenced by symbol definitions with shareable image program sections of the same name. Symbol definition records which contain the index of an overlaid program section are generated by the C compiler when the relaxed ref-def extern model is used (the default). Shareable image program sections are created when you link a shareable image and use the PSECT keyword in your SYMBOL_VECTOR option. If the linker detects this condition it will issue the following error: %LINK-E-SHRSYMFND, shareable image psect was pointed to by a symbol definition %LINK-E-NOIMGFIL, image file not created The link will continue, but no image will be created. To work around this restriction, change the symbol vector keyword to DATA, or recompile your C program with the qualifer /EXTERN=COMMON. 5.8 MACRO-32 Compiler for OpenVMS Alpha AXP - Restrictions and Known Problems The MACRO-32 Compiler for OpenVMS Alpha AXP Version 1.0 has one restriction. It does not yet have the support to make its symbols visible to the OpenVMS Debugger. To debug MACRO code, you must specify the addresses of locations you want to examine or modify. This support is planned for a future release. The following problems are known to exist in the compiler. All of these conditions are extremely uncommon coding practices; it is very unlikely that you will encounter any of them. These problems include: o The compiler generates incorrect code for FFC and FFS instructions when the field lengths are greater than 63. This should not cause a problem for ported code, since these instructions cause a RESERVED OPERAND condition on OpenVMS VAX when a field length is greater than 32, and the compiler generates code that works correctly on OpenVMS Alpha AXP for bit lengths up to 63. However, lengths greater than 63 do not work correctly on OpenVMS Alpha AXP and do not cause a direct fault. 5-12 Programming Release Notes Compiler for OpenVMS Alpha AXP - Restrictions and Known Problems o If a global routine has the same name as a psect in the same module, and the object module is then inserted into an object library, the routine name will not be included in the library's global entry list for that module. The routine will be found by the linker if the module is included specifically, but it will not be found by a library search for the routine name. o A call to an equated symbol does not work. For example, the following sequence will not compile correctly: routine2 = routine1 ; routine1 is the name of a legally declared routine calls #0,routine2 You must call routines by their declared names. o REMQxx instructions whose target is 4(AP) or 8(AP) will not get correct results. You must move the target to another register or memory location before executing the REMQxx instruction. o The instruction MOVAx #LABEL, xx does not work correctly. On OpenVMS VAX, this instruction pushes the value of the label into the code stream and then moves the address of that location in the code stream to the requested destination. On OpenVMS Alpha AXP, the compiler does the equivalent operation correctly for numeric literals. However, if a label is specified, it moves the value of the label to the requested destination instead of moving the address of a location which contains the value of the label. o Repeat counts do not work correctly for values specified as equations. For example, the following code does not compile correctly: .BYTE [10] You must change the code as follows for correct compilation: Z= .BYTE Z[10] See the manual Migrating to an OpenVMS Alpha System: Porting VAX MACRO Code for a complete description of the compiler. 5-13 Programming Release Notes 5.9 Run-Time Libraries 5.9 Run-Time Libraries The run-time libraries listed in Table 5-1 are not included in this version of OpenVMS Alpha AXP: Table_5-1_Run-Time_Libraries_Not_Included__________________ ADARTL No ADA in OpenVMS Alpha AXP Version 1.0 DBGSSISHR DEBUG item, not required in OpenVMS Alpha AXP DNS$RTL No DNS in OpenVMS Alpha AXP Version 1.0 DNS$SHARE No DNS in OpenVMS Alpha AXP Version 1.0 DTI$SHARE No DECdtm in OpenVMS Alpha AXP Version 1.0 VBLAS1RTL No support for OpenVMS VAX vector programs VMTHRTL No support for OpenVMS VAX vector ______________________programs_____________________________ Most run-time libraries that were available in OpenVMS VAX Version 5.4 are available in this version of OpenVMS Alpha AXP. The OpenVMS VAX Version 5.4 libraries that are not available are either not being ported to OpenVMS Alpha AXP or are planned for a later release of OpenVMS Alpha AXP. For example, the vector math libraries VBLAS1RTL and VMTHRTL are not available in OpenVMS Alpha AXP because there is no support on OpenVMS Alpha AXP for programs that use the OpenVMS VAX vector instructions. 5.9.1 Compatibility Between the OpenVMS VAX and OpenVMS Alpha AXP Mathematics Libraries Mathematical applications using the standard OpenVMS call interface to the OpenVMS Run-Time Mathematics (MTH$) Library need not change their calls to MTH$ routines when migrating to an OpenVMS Alpha AXP system. Jacket routines are provided that map MTH$ routines to their math$ counterparts in the Digital Portable Mathematics Library (DPML) for OpenVMS Alpha AXP. However, there is no support 5-14 Programming Release Notes 5.9 Run-Time Libraries in the DPML for calls made to JSB entry points and vector routines. Please note that DPML routines are different from those in the OpenVMS Run-Time Mathematics (MTH$) Library. You should expect to see small differences in the precision of the mathematical results. If one of your goals is to maintain compatibility with future libraries and to create portable mathematical applications, Digital recommends that you use the DPML routines available through the high-level language of your choice (for example, FORTRAN and C) rather than using the call interface. Significantly higher performance and accuracy are also available to you with DPML routines. See the DPML, Digital Portable Mathematics Library manual for more information about DPML. 5.10 STARLET Data Structures and Definitions For C Programmers OpenVMS Alpha AXP Version 1.0 includes a new file, SYS$STARLET_C.TLB, that contains all the .H files that provide STARLET functionality equivalent to STARLETSD.TLB. The file SYS$STARLET_C.TLB, together with DECC$RTLDEF.TLB now shipping with the DEC C Compiler, replaces VAXCDEF.TLB that previously shipped with the VAX C compiler. DECC$RTLDEF.TLB contains all the .H files that support the compiler and RTL, such as STDIO.H. The following differences may require source changes: o RMS structures Previously, the RMS structures FAB, NAM, RAB, XABALL, and so forth, were defined in the appropriate .H files as "struct RAB {...", for example. The .H files to be supplied in OpenVMS Alpha AXP Version 1.0 will define them as "struct rabdef {...". To compensate for this difference, lines of the form "#define RAB rabdef" have been added. However, there is one situation where a source change will be required because of this change. If you have a private structure that contains a pointer to one of these structures, and your private structure is defined (but not used) before the RMS structure has been defined, you will receive compile-time errors similar to the following: 5-15 Programming Release Notes 5.10 STARLET Data Structures and Definitions For C Programmers %CC-E-PASNOTMEM, In this statement, "rab$b_rac" is not a member of "rab". This error can be avoided by reordering your source file so that the RMS structure is defined before the private structure. Typically this will involve moving around "#include" statements. o LIB (privileged interface) structures Historically, three structures from LIB (NFBDEF.H, FATDEF.H, and FCHDEF.H) have been made available as .H files. These files are shipped as .H files in OpenVMS Alpha AXP Version 1.0 (not in the new SYS$STARLET_ C.TLB). In a future release, another .TLB containing all LIB structures and definitions will be shipped. Once it is available, these files will become part of that .TLB, and will not be shipped separately as .H files. When that happens, it is very likely that source changes will be required, as no attempt will be made to preserve any existing anomalies in these files. The structures and definitions from LIB are for privileged interfaces only and are therefore subject to change. o Use of "variant_struct" and "variant_union" In the new .H files, "variant_struct" and "variant_ union" are always used, whereas previously some structures used "struct" and "union". Therefore, the intermediate structure names cannot be specified when referencing fields within data structures. For example, the following statement: AlignFaultItem.PC[0] = DataPtr->afr$r_pc_data_overlay.afr$q_fault_pc[0]; becomes: AlignFaultItem.PC[0] = DataPtr->afr$q_fault_pc[0]; o Member alignment Each of the .H files in SYS$STARLET_C.TLB saves and restores the state of "#pragma member_alignment". o Conventions The .H files in SYS$STARLET_C.TLB adhere to some conventions that were only partly followed in VAXCDEF.TLB. All constants (#defines) have uppercase names. All identifiers (routines, structure members, and so forth) have lowercase names. Where there is a 5-16 Programming Release Notes 5.10 STARLET Data Structures and Definitions For C Programmers difference from VAXCDEF.TLB, the old symbol name is also included for compatibility, but users are encouraged to follow the new conventions. o Use of librarian to access the .H files During installation of OpenVMS Alpha AXP Version 1.0, the contents of SYS$STARLET_C.TLB are not extracted into the separate .H files. The DEC C compiler will access these files from within SYS$STARLET_C.TLB, regardless of the format of the #include statement. If you want to inspect an individual .H file, the Librarian utility can be used, as in the following example: $ LIBRARY /EXTRACT=AFRDEF /OUTPUT=AFRDEF.H SYS$LIBRARY:SYS$STARLET_C.TLB o Additional .H files included in SYS$STARLET_C.TLB In addition to the .H files derived from STARLET sources, SYS$STARLET_C.TLB includes .H files that provide support for DECthreads, such as CMA.H. 5.11 SUMSLP Utility (SUMSLP) The SUMSLP utility (SUMSLP), a batch-oriented editor that allows you to update source files, does not work in OpenVMS Alpha AXP Version 1.0. SUMSLP should not be used for any purpose. We expect to fix this problem in a future release of OpenVMS Alpha AXP. 5.12 System Dump Analyzer Utility Notes The following sections describe enhancements and restrictions that apply to the System Dump Analyzer (SDA) utility. 5.12.1 SHOW MACHINE_CHECK Command Available The SDA SHOW MACHINE_CHECK display works for the DEC 4000 AXP and DEC 7000 AXP Model 600 platforms only. Users should note that the SHOW MACHINE_CHECK command will display available information even if the cause of the system crash was something other than a machine check. The data is guaranteed to be accurate only if the bugcheck code for the crash is a machine check. 5-17 Programming Release Notes 5.12 System Dump Analyzer Utility Notes The following display applies to a DEC 7000 AXP Model 600 machine check: Processor specific information: ------------------------------- Exception address: 00000000 00030122 Exception Summary: 00000000 00000000 Pal base address: 00000000 00008000 Exception Mask: 00000000 00000000 HW Interrupt Request: 00000000 00000342 HW Interrupt Ena: 00000001 FFFFDCE0 MM_CSR 00000000 00005120 ICCSR: 00000003 F81F0000 D-cache address: 00000007 FFFFFFFF D-cache status: 00000000 000002E0 BIU status: 00000000 00000041 BIU address [7..0]: 00000003 F8400000 BIU control: 00000008 50006447 Fill Address: 00000000 00006120 Single-bit syndrome: 00000000 00000000 Processor mchck VA: 00000000 00006190 A-box control: 00000000 0000040E B-cache TAG: 0000609A 30482000 System specific information: ---------------------------- Garbage bus info: 00300009 000000B0 Device type: 00008001 LCNR: 00000001 Memory error: 00000000 LBER: 00001081 Bus error synd 0,1: 0000000C 0000000C Bus error cmd: 00000020 00420000 Bus error synd 2,3: 0000000C 0000000C LEP mode: 00010010 LEP lock address: 00091B86 5.12.2 Restrictions and Known Problems The following problems and restrictions apply to SDA: o If you supply an invalid file specification after the SDA READ command, SDA will print an error message and exit to DCL. This will be fixed in a future release of OpenVMS Alpha AXP. o The SDA commands EXAMINE/SYSTEM/NOSUPPRESS, EXAMINE /P0/NOSUPPRESS, and EXAMINE/P1/NOSUPPRESS are not parsed correctly on OpenVMS Alpha AXP Version 1.0. Specifically, the /NOSUPPRESS qualifer is not parsed correctly and SDA returns an error. This will be fixed in a future release of OpenVMS Alpha AXP. o The following command does not work if the specified includes some informational bits in the upper part of the lock id longword: SDA> SHOW LOCK 5-18 Programming Release Notes 5.12 System Dump Analyzer Utility Notes SDA does not remove these informational bits before trying to match the lock. As a result, it never finds the correct lock. To work around this problem, enter only the lower part of the lock id in the command. Examine LCK$GL_MAXID to determine the maximum size of the lock id. This will be fixed in a future release of OpenVMS Alpha AXP. o The following command does not always find the lock that you specify: SDA> SHOW LOCK/NAME="" This command works correctly the first time you enter it. SDA displays information about the lock that you specify. However, when you repeat the command, SDA returns to the SDA prompt without displaying any lock information. This problem occurs because the first SHOW LOCK command does not reset the lock index. When you enter the second SHOW LOCK command, SDA starts searching at the location in the lock database where the first SHOW LOCK command ended, rather than starting at the beginning of the lock database. To work around this problem, enter a SHOW LOCK command without specifying any parameters. Enter the SHOW LOCK/NAME command immediately after the first lock is displayed. This problem will be fixed in a future release of OpenVMS Alpha AXP. 5.12.2.1 ANALYZE/CRASH_DUMP and ANALYZE/SYSTEM The ANALYZE/CRASH_DUMP and ANALYZE/SYSTEM commands do not return errors to DCL correctly. As a result, the Help Message utility is unable to provide a description of the error messages that are displayed when SDA exits. 5.12.2.2 General Register Symbols The general register symbols R30 and R31 are not valid in this version of SDA; they will be added in a future release. As a workaround, substitute the EXAMINE SP command for the EXAMINE R30 command. 5-19 Programming Release Notes 5.12 System Dump Analyzer Utility Notes 5.12.2.3 RMS Commands The following series of commands does not work in this version of SDA: SDA> SET RMS=(xxx,yyy) SDA> SHOW PROCESS/RMS This command sequence will be operational in a future release of SDA. As a workaround, use the following command instead: SDA> SHOW PROCESS/RMS=(xxx,yyy) 5.12.2.4 SHOW CRASH Display is Incorrect The ASTSR/ASTEN field in the SHOW CRASH display incorrectly appears as follows: ASTEN/ASTSR: XXXXXXXX ASTSR and ASTEN should be reversed. This field should appear as follows: ASTSR/ASTEN: XXXXXXXX The reversed order is incorrect because the longword contains the data in that order. As a workaround for OpenVMS Alpha AXP Version 1.0, examine the SHOW PROCESS /REGISTERS display, where this data appears in the correct order. 5.13 System Services Notes The following sections describe changes and a restriction that apply to system services in OpenVMS Alpha AXP Version 1.0. 5.13.1 Low Four Bits of Chan Argument Are Checked - Change The chan argument is used in a number of system services to pass a channel number. Historically, OpenVMS has always regarded the chan argument as a 16 bit unsigned number but has never used the low four bits of the argument. Thus, it is possible that some user programs might use the low four bits of the argument as temporary storage unrelated to the channel number. 5-20 Programming Release Notes 5.13 System Services Notes Now, the low four bits of the chan argument are checked. If any bit is nonzero, a status code of SS$_IVCHAN is returned to the caller of the service. Modify your source code to properly store user information in a location other than the chan argument. 5.13.2 $DCLCMH System Service Behavior Differs on OpenVMS Alpha AXP and OpenVMS VAX Systems The Declare Change Mode or Compatibility Mode Handler service specifies the address of a routine to receive control when a Change Mode to User or Change Mode to Supervisor instruction trap occurs, or when a compatibility mode fault occurs on OpenVMS VAX. You declare the change mode handler from the access mode at which the request is to be handled; then when the process executing in user mode issues a Change Mode to Supervisor instruction, the change mode handler receives control and executes in supervisor mode. On OpenVMS Alpha AXP, the change mode dispatcher calls the change mode handler as a normal procedure (that is, with a standard procedure call). The change mode handler must exit by performing a standard procedure return to the change mode dispatcher. Argument usage (for example, the change mode code) passed between the routine that issued the change mode instruction and the change mode handler is coordinated strictly by agreement between the two procedures, rather than in accord with the calling standard. The following MACRO code example shows a subroutine, calling Change Mode to User, written for OpenVMS Alpha AXP users porting from OpenVMS VAX: CHG_MD: .CALL_ENTRY CHMU RET This subroutine should be called from any program that requires a Change Mode to User instruction to be invoked. On OpenVMS VAX, the top longword of the stack contains the zero-extended change mode code. The change mode handler must exit by removing the change mode code from the stack and issuing an REI instruction. 5-21 Programming Release Notes 5.13 System Services Notes 5.13.3 $FORMAT_AUDIT Width Argument Does Not Work Consistently - Restriction The width argument to the $FORMAT_AUDIT system service does not work consistently. In most cases, if you specify both the width argument and the full format style (NSA$C_FORMAT_ STYLE_FULL), $FORMAT_AUDIT ignores the width argument. The minimum width is 80 columns; lower values do not limit the width to less than 80. If you specify a width greater than 80 columns, most lines are not joined to use the full width. In general, you should avoid using the width argument. 5.14 Traceback Handler Support Traceback handler support is present in OpenVMS Alpha AXP Version 1.0. The following items describe the available support: o Symbolic traceback is supported, including traceback for images installed /RESIDENT. The symbolic information that is reported includes the image name in which the invocation PC lies, the module name, the routine name, and the line number. Two PC values are also provided: - Relative (to the routine base address) - Absolute If the traceback handler must resort to nonsymbolic information (because there is no symbolic information in the image), then the relative PC is relative to the image base address. o The traceback handler supports the (nonsymbolic) display of translated VAX call frames. o Exception frame reporting has been implemented. 5-22 Programming Release Notes 5.15 Translated Image Environment (TIE) Notes 5.15 Translated Image Environment (TIE) Notes Image translation is one means of migrating all or part of an OpenVMS VAX application to OpenVMS Alpha AXP. The VAX Environment Software Translator (VEST) creates a translated image by converting an OpenVMS VAX executable or shareable image into a functionally equivalent OpenVMS Alpha AXP image. VEST is a component of the optional layered product DECmigrate for OpenVMS AXP. When a translated image runs on OpenVMS Alpha AXP, the Translated Image Environment (TIE) provides the OpenVMS VAX environment required for the image to execute properly. The TIE consists of the shareable images TIE$SHARE and TIE$EMULAT_TV, which performs VAX complex instructions. For information on the role of image translation in a migration strategy, see the manuals Migrating to an OpenVMS Alpha System: Planning for Migration and DECmigrate for OpenVMS AXP Version 1.0 Translating Images. Digital supports translation of programs from OpenVMS VAX Version 4.0 through Version 5.4-3. Although VEST translates Version 5.5 images, OpenVMS Alpha AXP Version 1.0 might not provide the necessary run-time support because the translated libraries are based on Version 5.4-3. In this case, the translated OpenVMS VAX Version 5.5 image may get an ident mismatch at run time. The following sections discuss these topics: o Interoperability between native and translated images o Running translated images o TIE statistics and feedback o TIE restrictions 5.15.1 Interoperability The TIE works together with other components of OpenVMS Alpha AXP to enable native and translated images to interoperate, that is, to call one another. If you are developing applications or run-time libraries that rely on interoperability, you need to follow certain procedures when compiling, linking, or translating. See the first restriction described in Section 5.15.4. Table 5-2 provides pointers to documentation that describes the procedures. 5-23 Programming Release Notes 5.15 Translated Image Environment (TIE) Notes Table_5-2_Interoperability_Documentation___________________ For_information_about______See_____________________________ Ensuring interoperability Migrating to an OpenVMS between native and Alpha System: Recompiling and translated images Relinking Applications DECmigrate for OpenVMS AXP Version 1.0 Translating Images Coordinating native DECmigrate for OpenVMS AXP and translated run-time Version 1.0 Translating Images libraries__________________________________________________ 5.15.2 Running Translated Images Use the DCL RUN command to run a translated image. For example: $ RUN FOO_TV.EXE Note that the translated image will not run correctly unless OpenVMS Alpha AXP includes the appropriate translated shareable images and run-time libraries. When you translate an image, VEST requires the image information files (IIFs-file type .IIF) corresponding to whichever images and libraries that the input image refers to. These .IIFs enable VEST to create a translated image that correctly refers to the translated versions of the shareable images and libraries. An image information file used at image translation must exactly correspond to the version of the translated shareable image or run-time library available on OpenVMS Alpha AXP. OpenVMS Alpha AXP includes a set of translated run-time libraries and a matching set of image information files, which are listed in Section 5.16. Check these lists to determine if they include the libraries or shareable images referred to by images you want to translate and run. If OpenVMS Alpha AXP does not include the required shared images or libraries, refer to the manual DECmigrate for OpenVMS AXP Version 1.0 Translating Images. This manual describes how to create and use image information files. Defining logical names for libraries 5-24 Programming Release Notes 5.15 Translated Image Environment (TIE) Notes Note that when a translated library has been replaced by a native version of the library, you need to define accordingly any logical names that point to it-that is, you need to redefine image_TV to image. 5.15.3 TIE Statistics and Feedback In addition to the TIE's run-time support function, TIE statistics and feedback can help to improve translated image performance: o The TIE can display statistics about the run-time execution of translated images. These statistics describe the image's use of TIE resources and the interactions between images. o The TIE can record information about VAX entry points discovered while interpreting VAX code. When you retranslate the image, VEST uses the information to find and translate more VAX code. The manual DECmigrate for OpenVMS AXP Version 1.0 Translating Images describes these features in detail and explains how to define the logical names that enable and disable their use. 5.15.4 TIE Restrictions The following restrictions apply to the TIE: Interoperability restrictions o A native routine that either calls or is called by a translated image must be compiled with the /TIE qualifier and linked with the /NONATIVE_ONLY qualifier. Checking for interoperability between native and translated images occurs at run-time. If the /TIE and /NONATIVE_ONLY qualifiers were not used to compile and link the native routine, an error will occur at run-time when the the native routine and a translated image attempt to interoperate. If such an error occurs, recompile and relink the native routine appropriately. This restriction is permanent. 5-25 Programming Release Notes 5.15 Translated Image Environment (TIE) Notes o An access violation can occur at run time if a native routine that was not compiled with the /TIE qualifier makes an indirect call to a translated routine. The indirect call is made through a variable that contains the translated routine's address. When this happens, there is no autojacketing code in place to assist the native to translated call. The native code attempts to use the routine address as a native procedure descriptor. The code address of a native procedure is at offset PDSC$L_ENTRY, whose value is 8, from the base of the procedure descriptor. Because the translated routine address is treated as a procedure descriptor, the value at offset 8 from that address is used as the code to call. This usually results in an access violation. If you suspect you are encountering this problem, use a debugger to check the following: o Check that R27 points into a translated image. o Check that bits <31:2> of 8(R27) equal bits <31:2> of the ACCVIO address. (All bits are not used because OpenVMS Alpha AXP instructions are longword aligned.) o Check that R26 points into a native image. o Check that -4(R26) is a JSR R26,(26) instruction. If all these checks prove to be true, recompile the native routine with the /TIE qualifier to enable autojacketing at run time. Condition and exception handler restrictions o A restriction on the type of condition handler that can be established exists for both native and translated images. A native routine cannot establish a translated condition handler, nor can a translated routine establish a native condition handler. If a native or translated image violates this restriction, the run-time results are unpredictable. This restriction is permanent. o Translated images with exception handlers that depend on receiving the correct program status longword (PSL) might not function properly. When exceptions are reported, the AXP program status (PS) is reported in the signal array instead since there is no VAX PSL. 5-26 Programming Release Notes 5.15 Translated Image Environment (TIE) Notes This restriction is permanent. o Translated images with exception handlers that depend on modifying the PSL in the signal array will not function properly. The modified PSL will not be propagated back to the faulting code. This restriction is permanent. Floating point restrictions o In some cases, floating point instructions operating on the same data generate a trap on an AXP system but not on a VAX system. Specifically, VAX floating point instructions on OpenVMS Alpha AXP generate traps for the "dirty zeros" that VAX hardware can handle correctly. "Dirty zeros" are floating point values that are alternate encodings for zero. To retain compatibility with translated code that performs operations using dirty zeros, the TIE includes a condition handler that corrects the dirty zeros and retries the floating point operation. However, the handler succeeds only if the qualifier /PRESERVE=FLOAT_EXCEPTIONS was used when the image was translated. Images that were not translated with /PRESERVE=FLOAT_ EXCEPTIONS and that perform an operation on a dirty zero incur an HPARITH exception with a summary status that has bit 1 set. If your translated application incurs one of these exceptions, retranslate with /PRESERVE=FLOAT_ EXCEPTIONS VAX dirty zeros commonly result from not initializing floating data to 0. In this case, changes to source code may be necessary to port to OpenVMS Alpha AXP an application that uses dirty zeros. This restriction is permanent. o Alpha D53 floating point (D_floating point as a 53-bit fraction instead of a 56-bit fraction) is VAX D_floating converted to G_floating representation. This conversion leads to the following problem. Consider the following VAX instruction sequence: MOVD (SP),R2 MOVD R2,-(SP) 5-27 Programming Release Notes 5.15 Translated Image Environment (TIE) Notes VEST translates these OpenVMS VAX instructions into OpenVMS Alpha AXP code like the following: LDD F2,0(R14) ! Pickup D float CVTDG F2,F2 ! Convert to Canonical G Form with rounding CVTGD F2,F17 ! Convert back to D Form for storing STD F17,-8(R14) ! Store the result At run-time, the VEST-generated code uses rounding to obtain the most accurate G_floating value when converting the D56 floating point to G canonical form. In some cases, the conversion to G canonical form may round up the D_floating value to create an exponent that cannot be represented in D_floating. When this happens, the CVTGD operation incurs an HPARITH trap with floating overflow as the summary reason. If a translated image incurs this problem at run time, it needs to be retranslated with the VEST qualifier /FLOAT=D56_FLOAT to execute properly. This restriction is permanent. Translated VAX C program restrictions o If a program uses the VAXCRTL routine brk() to release dynamic memory (that is, a lower break address is requested than the current break address) the next attempt by TIE to use a complex instruction routine may result in a fatal memory access violation. This may happen because the complex instruction routines are in a separate image, TIE$EMULAT_TV.EXE, which is dynamically activated via LIB$FIND_IMAGE_SYMBOL on the first use of one of the routines. Depending on when this occurs and the address passed to the brk() call that releases memory, the memory into which TIE$EMULAT_TV.EXE was loaded may also be released. To avoid this problem, never use brk() to release memory or be sure to execute a complex VAX instruction prior to getting the break address that is later used to release memory. Using brk() to allocate memory is fine. This restriction is permanent. 5-28 Programming Release Notes 5.15 Translated Image Environment (TIE) Notes o A translated VAX C program that uses vfork() and any executive function may hang at run-time. If the child process of the VAX C program aborts erroneously, it may hang waiting for a mailbox I/O to be completed. One workaround is to prevent the child process from aborting. This problem will be fixed in a future release of DECmigrate for OpenVMS AXP. 5.16 Translated Images and Other Related Files This section lists the translated images, image information files, and other related files that are provided with OpenVMS Alpha AXP. OpenVMS Alpha AXP contains no translated message images. All translated message images have been made native. OpenVMS Alpha AXP contains the following translated images in SYS$LIBRARY: BASRTL2_D53_TV.EXE BASRTL2_D56_TV.EXE BASRTL_D56_TV.EXE BLAS1RTL_D53_TV.EXE BLAS1RTL_D56_TV.EXE COBRTL_D56_TV.EXE DBLRTL_D56_TV.EXE EDTSHR_TV.EXE FORRTL2_TV.EXE FORRTL_D56_TV.EXE LIBRTL2_D56_TV.EXE LIBRTL_D56_TV.EXE MTHRTL_D53_TV.EXE MTHRTL_D56_TV.EXE PASRTL_D56_TV.EXE PLIRTL_D56_TV.EXE RPGRTL_TV.EXE SCNRTL_TV.EXE TIE$EMULAT_TV.EXE UVMTHRTL_D53_TV.EXE UVMTHRTL_D56_TV.EXE VAXCRTLG_D56_TV.EXE VAXCRTL_D56_TV.EXE 5-29 Programming Release Notes 5.16 Translated Images and Other Related Files VMSRTL_TV.EXE OpenVMS Alpha AXP provides the following translated images in SYS$SYSTEM: ALPHA_MACRO_TV.EXE DBLMSGMGR_TV.EXE EDF_TV.EXE EDT_TV.EXE MONITOR_TV.EXE OpenVMS Alpha AXP contains the following translated images in IMAGELIB: BASRTL2_D53_TV.EXE BASRTL_D56_TV.EXE BLAS1RTL_D53_TV.EXE COBRTL_D56_TV.EXE DBLRTL_D56_TV.EXE EDTSHR_TV.EXE FORRTL2_TV.EXE FORRTL_D56_TV.EXE LIBRTL2_D56_TV.EXE LIBRTL_D56_TV.EXE PASRTL_D56_TV.EXE PLIRTL_D56_TV.EXE RPGRTL_TV.EXE SCNRTL_TV.EXE Note that most of the translated RTLs are provided in D56 format rather than D53 format; some are provided in both formats. Where both formats are provided, the default format is D53. See Section 5.17 for more information about the translated run-time libraries. OpenVMS Alpha AXP contains the following image information files in SYS$LIBRARY: ACLEDTSHR.IIF BASRTL2.IIF BASRTL.IIF BLAS1RTL.IIF COBRTL.IIF CONVSHR.IIF CRFSHR.IIF DBLRTL.IIF DCXSHR.IIF 5-30 Programming Release Notes 5.16 Translated Images and Other Related Files DISMNTSHR.IIF DTKSHR.IIF EDTSHR.IIF ENCRYPSHR.IIF EPC$SHR.IIF FDLSHR.IIF FORRTL.IIF FORRTL2.IIF INIT$SHR.IIF LBRSHR.IIF LIBRTL.IIF LIBRTL2.IIF MAILSHR.IIF MOUNTSHR.IIF MTHRTL.IIF NCSSHR.IIF P1_SPACE.IIF PASRTL.IIF PLIRTL.IIF PPLRTL.IIF PTD$SERVICES_SHR.IIF RPGRTL.IIF S0_SPACE.IIF SCNRTL.IIF SCRSHR.IIF SECURESHR.IIF SMBSRVSHR.IIF SMGSHR.IIF SORTSHR.IIF SPISHR.IIF TPUSHR.IIF UVMTHRTL.IIF VAXCRTL.IIF VAXCRTLG.IIF VMSRTL.IIF The following system logicals are defined in order to facilitate the translated environment: ACLEDTSHR_TV = ACLEDTSHR CDDSHR_TV = CDDSHR CONVSHR_TV = CONVSHR CRFSHR_TV = CRFSHR DCXSHR_TV = DCXSHR 5-31 Programming Release Notes 5.16 Translated Images and Other Related Files DISMNTSHR_TV = DISMNTSHR DTKSHR_TV = DTKSHR ENCRYPSHR_TV = ENCRYPSHR EPC$SHR_TV = EPC_SHR FDLSHR_TV = FDLSHR INIT$SHR_TV = INIT$SHR LBRSHR_TV = LBRSHR MAILSHR_TV = MAILSHR MOUNTSHR_TV = MOUNTSHR NCSSHR_TV = NCSSHR PPLRTL_TV = PPLRTL PTD$SERVICES_SHR_TV = PTD$SERVICES_SHR SCRSHR_TV = SCRSHR SECURESHR_TV = SECURESHR_JACKET SMBSRVSHR_TV = SMBSRVSHR SMGSHR_TV = SMGSHR SORTSHR_TV = SORTSHR SPISHR_TV = SPISHR TPUSHR_TV = TPUSHR BASRTL_TV = BASRTL_D56_TV BASRTL2_TV = BASRTL2_D53_TV BLAS1RTL_TV = BLAS1RTL_D53_TV COBRTL_TV = COBRTL_D56_TV DBLRTL_TV = DBLRTL_D56_TV FORRTL_TV = FORRTL_D56_TV LIBRTL_TV = LIBRTL_D56_TV LIBRTL2_TV = LIBRTL2_D56_TV MTHRTL_TV = MTHRTL_D53_TV PASRTL_TV = PASRTL_D56_TV PLIRTL_TV = PLIRTL_D56_TV VAXCRTL_TV = VAXCRTL_D56_TV VAXCRTLG_TV = VAXCRTLG_D56_TV ALPHA_MACRO = ALPHA_MACRO_TV DBLMSGMGR = DBLMSGMGR_TV EDTSHR = EDTSHR_TV VMSRTL = VMSRTL_TV DBLRTLMSG = DBL$MSG PASMSG = PAS$MSG PLIMSG = PLI$MSG RPGMSG = RPG$MSG 5-32 Programming Release Notes 5.16 Translated Images and Other Related Files SCNMSG = SCN$MSG VAXCMSG = DECC$MSG 5.17 Translated Run-Time Libraries As part of the OpenVMS Alpha AXP kit, Digital provides a set of translated run-time libraries. Some of the routines in the OpenVMS VAX run-time libraries use the VAX D_floating data type for double-precision arithmetic. In the translated versions of these libraries, the OpenVMS Alpha AXP D56 D_floating data type is used by default (where the OpenVMS VAX run-time library used D_floating). This provides the full precision of the 56-bit mantissa in VAX D_floating, yielding consistency of results, at a cost in execution time performance. For a handful of performance-critical math-related libraries, Digital also supplies versions of the translated run-time libraries that use the OpenVMS Alpha AXP D53 D_ floating data type for double precision operations. For these libraries, the D53 forms are the default. The D53 forms provide better performance, by sacrificing the low- order three bits of precision in the mantissa. The following translated libraries are provided in D56 form only: o BASRTL o COBRTL o DBLRTL o FORRTL o LIBRTL o LIBRTL2 o PASRTL o PLIRTL o VAXCRTL o VAXCRTLG 5-33 Programming Release Notes 5.17 Translated Run-Time Libraries The following translated libraries are provided in both D56 and D53 (the default) form: o BASRTL2 o BLAS1RTL o MTHRTL o UVMTHRTL If you need to use the D56 form of one of these libraries in order to get more consistent results (at a cost of execution time performance), see Section 5.17.1 for instructions. 5.17.1 Accessing the D56 Form of the Run-Time Libraries The following actions happen by default when you use the run-time libraries: o For BASRTL2, translated BASIC images that use MAT functions on double precision data invoke BASIC run-time library routines that use the D53 data type. o For BLAS1RTL, translated images that invoke BLAS$ functions with double-precision floating-point arguments get routines that use the D53 data type. o For MTHRTL, translated images that invoke MTH$ double- precision floating-point functions get routines that use the D53 data type. o For all others, the OpenVMS Alpha AXP D56 floating point data type is used by default. Some users might need the full precision of D56 floating point. However, using the D56 routines imposes a very significant performance penalty. To access the D56 routines, redefine the run-time library's logical name to the D56 form, as shown in Table 5-3. The logical name can be defined on a per-process or system-wide basis, as appropriate for your site. 5-34 Programming Release Notes 5.17 Translated Run-Time Libraries Table_5-3_Run-Time_Library_Logical_Names___________________ Library_______Logical_Name_____D56_Name____________________ BASRTL2 BASRTL2_TV BASRTL2_D56_TV BLAS1RTL BLAS1RTL_TV BLAS1RTL_D56_TV MTHRTL________MTHRTL_TV________MTHRTL_D56_TV_______________ 5.17.2 Problem with Translated Image Environment Translated callers to CRF$FREE_VM and CRF$GET_VM will not work properly. The translated callers are expecting VAX JSB semantics, but instead, OpenVMS Alpha AXP JSB semantics are present in the native code (naturally). To work around this problem, the translated callers need to use CALL instead of JSB. 5.17.3 Translated VAX BASIC Run-Time Library Notes This section describes the limitations and known problems with the OpenVMS Alpha AXP translated VAX BASIC run-time library (VAX BASIC RTL). 5.17.3.1 Functional Restrictions The translated VAX BASIC RTL is a translated version of the OpenVMS VAX Version 5.4 VAX BASIC RTL. All problems and restrictions present in the OpenVMS VAX Version 5.4 release of the VAX BASIC RTL exist unchanged in the translated VAX BASIC RTL. These include: o Integer errors do not raise the appropriate exceptions. For example, a divide by zero error will not raise a BASIC error handler but will cause the translated program to abort. To avoid these problems, you should explicitly test for integer operand error conditions. o Array descriptors for H Float data items will not work. For example, passing an H float array by descriptor (the default) will not pass the array properly to a function or subprogram. You should pass H Float arrays by reference to avoid this problem. o WHEN block exception processing may not work the same as on OpenVMS VAX. 5-35 Programming Release Notes 5.17 Translated Run-Time Libraries The program should be translated using the /OPTIMIZE=NOSCHEDULE qualifier. Programs containing WHEN blocks will handle errors but may dump on exit. o Explicit calls to LIB$SIGNAL are not handled by a BASIC exception handler in a user program. o The ON...GOSUB statement does not work properly. The control expression is corrupted. Any attempt to access the control variable after the ON...GOSUB statement has completed will cause the program to abort. o Taking the identity of large odd dimension matrices can result in memory management violations. 5.17.4 Translated VAX C Run-Time Library Notes This section describes the limitations and known problems with the OpenVMS Alpha AXP translated VAX C Run-Time Library (VAX C RTL). 5.17.4.1 Functional Restrictions The following items are known restrictions in the functionality of the translated VAX C RTL: o The translated VAX C RTL is a translated version of the OpenVMS VAX Version 5.4 VAX C RTL. All problems and restrictions present in that release of the VAX C RTL exist unchanged in the translated VAX C RTL. o The fmod( ) function does not produce correct results for D_FLOAT. o D_FLOAT programs that use the SIGFPE signal may not catch all floating point exceptions. Translating the program using /FLOAT=D56_FLOAT will fix most SIGFPE problems. o The sbrk( ) function returns an address that does not match the value returned from SYS$EXPREG. o D_FLOAT programs that use the HUGE_VAL constant or call the math functions (which may return HUGE_VAL) may fail unless they are translated with /FLOAT=D56_FLOAT. 5-36 Programming Release Notes 5.17 Translated Run-Time Libraries o Under some circumstances, some math functions (either D_FLOAT or G_FLOAT) may generate a High Performance Arithmetic Trap exception instead of setting errno to ERANGE or EDOM. 5.17.4.2 Interoperability Restrictions The following restrictions apply when the translated VAX C RTL interoperates with the native DEC C RTL: o The longjmp function cannot be used to transfer control from: - a native routine to a translated routine - a translated routine to a native routine o Memory allocated by malloc, calloc, and so forth must be freed in the same context. That is, if a translated routine allocates memory, the free call must occur in a translated routine. Allocating memory in a translated routine and freeing it in a native routine will result in corruption of the heap. Likewise allocating memory in a native routine and freeing that memory in a translated routine will also corrupt the heap. o Signal handlers established by the signal (and related) functions in translated routines will not be invoked when the signal is raised. Only native signal handlers can be used to catch UNIX-style signals. o The signals SIGEMT, SIGTRAP, SIGIOT and SIGFPE cannot be caught if those signals are raised by a translated image. o The exec function can only be used to invoke similar images. That is, an exec function invoked in a native image cannot execute a translated image. Likewise, an exec function invoked in a translated image cannot execute a native image. o An access violation will occur if vfork is executed in a native image to establish the context for a later system call, and the system call is then invoked in a translated image. 5-37 Programming Release Notes 5.17 Translated Run-Time Libraries o File pointers and file descriptors cannot be shared between native and translated images. An access violation or file corruption is likely to occur if a file is opened in a translated image and a native image attempts to read or write using that file pointer. The same results will occur if a file is opened in a native image and a translated image attempts to read or write using that file pointer. Programs that perform any of these restricted actions may receive access violations or other exceptions. No testing is performed to detect and prevent restricted operations from being performed. 5.17.5 Translated VAX FORTRAN Programs - Restriction Parallel processing errors are not available on OpenVMS Alpha AXP. Errors generated during execution of translated VAX FORTRAN programs performing parallel processing operations will generate the following error: %NONAME-F-NOSMG 5-38 6 _________________________________________________________________ Documentation Release Notes This chapter contains corrections to published documentation. 6.1 OpenVMS Alpha AXP Documentation Set Parts of the OpenVMS Alpha AXP Documentation Set refer to the ALARM_JOURNAL ACE as the ALARM ACE. The ALARM ACE and the ALARM_JOURNAL ACE are synonymous. 6.2 OpenVMS DCL Dictionary The description of the following DCL commands contains incorrect information pertaining to displays of memory management data. The DCL Help for these commands, however, is correct. SHOW SYSTEM The explanation to Example 1, "Physical memory occupied" should read: Physical memory occupied-The number of CPU-specific pages in physical memory that the process is currently occupying. On OpenVMS Alpha AXP systems, this column is labelled "Pages"; on an OpenVMS VAX system, it is labelled "Ph. Mem". SHOW PROCESS The explanation to Example 2 should note that the values under "Peak working set size" and "Peak virtual size" are rendered in 512-byte pages on OpenVMS VAX and pagelets on OpenVMS Alpha AXP. The explanation to Example 4 should note that the value under "Paging file quota" is rendered in pages on OpenVMS VAX and 512-byte pagelets on OpenVMS Alpha AXP. 6-1 Documentation Release Notes 6.2 OpenVMS DCL Dictionary The explanation to Example 6 should read: Note that the "Virtual memory" heading appears on OpenVMS VAX and the "Virtual pages" heading appears on OpenVMS Alpha AXP; both indicate the virtual memory used as a number of CPU-specific pages. The value displayed for "Working set" is also a number of CPU-specific pages. The explanation to Example 7 should note that the "Blocks LEQU 32" field in the OpenVMS VAX display appears as "Blocks LEQU 64" on OpenVMS Alpha AXP systems. 6.3 OpenVMS Linker Utility Manual In the description of the /NATIVE_ONLY qualifier in the OpenVMS Linker Utility Manual, the default value of the qualifier is listed incorrectly as /NATIVE_ONLY. The default value for this qualifier is /NONATIVE_ONLY. 6.4 VMS National Character Set Utility Manual The command NCS/CREATE/LIBRARY=filename.ext defaults to directory SYS$LIBRARY. A device and directory specification is required to create the library elsewhere, as shown in the following example: NCS/CREATE/LIBRARY=device:[directory]filename.ext The VMS National Character Set Utility Manual shows this by example but does not explicitly indicate the default. This information was omitted from the existing documentation. 6.5 Correction to OpenVMS Programming Documentation Appendix A of the OpenVMS VAX Version 5.4 manual Introduction to VMS System Routines (currently Appendix B of the OpenVMS Alpha AXP manual OpenVMS Programming Concepts Manual) describes the OpenVMS usage type user- arg as being an "unsigned longword denoting a user-defined argument." This description is correct. Descriptions of certain OpenVMS system services and Run-Time Library (RTL) routines in OpenVMS programming documentation classify the OpenVMS usage type user-arg as being "unspecified". This is incorrect. The user argument 6-2 Documentation Release Notes 6.5 Correction to OpenVMS Programming Documentation parameter to such routines must be specified as a longword containing a nonfloating-point value. A program that uses the user argument parameter of any of the following routines to pass floating-point data will not run correctly on an OpenVMS Alpha AXP system, either as a native OpenVMS Alpha AXP image or as a translated VAX image: o LIB$CREATE_USER_VM_ZONE o LIB$DECODE_FAULT o LIB$DELETE_FILE o LIB$INSERT_TREE o LIB$LOOKUP_TREE o LIB$RENAME_FILE o LIB$SHOW_TIMER o LIB$SHOW_VM o LIB$SHOW_VM_ZONE o LIB$SPAWN o LIB$STAT_TIMER o LIB$STAT_VM o LIB$TRAVERSE_TREE o SMG$PUT_PASTEBOARD o SYS$PUTMSG The current editions of the appropriate OpenVMS programming manuals contain the correct descriptions of user argument parameters to these routines. 6.6 OpenVMS System Management Utilities Reference Manual The following system parameter was inadvertently omitted from Appendix K in the OpenVMS System Management Utilities Reference Manual: 6-3 Documentation Release Notes 6.6 OpenVMS System Management Utilities Reference Manual CRDENABL CRDENABL enables or disables detection and logging of memory-corrected read data (ECC) errors. This parameter should normally be on (1). 6.7 OpenVMS Alpha Guide to System Security The OpenVMS Alpha Guide to System Security incorrectly refers to the default audit log file as SECURITY.AUDIT$JOURNAL. In fact, the default audit log file is called SECURITY_AUDIT.AUDIT$JOURNAL. 6-4 A _________________________________________________________________ New OpenVMS System Messages The Help Message database for this release includes new or changed messages for the following OpenVMS facilities: o AMAC, MACRO-32 Compiler for OpenVMS Alpha o EDT, EDT Editor o IMGACT, Image Activator o INIT, INITIALIZE Command o LINK, Linker Utility o MAIL, Mail Utility o MSGHLP, Help Message Utility o RMS, VMS Record Management Services o SDA, System Dump Analyzer o SYSTEM, System Services o TIE, Translated Image Environment This appendix alphabetically lists and describes all messages that have been added or changed for this release and that are not included in the OpenVMS System Messages: Companion Guide for Help Message Users. For your convenience, messages from the VMS Version 5.5-2 Release Notes have also been merged into this appendix. You can access online descriptions of these and all other VMS system messages by using the new online Help Message utility. A-1 New OpenVMS System Messages ABSPSECT, statement not supported in absolute program section Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: A declaration that was not a symbol definition was included in an absolute program section. User Action: Move any declarations that are not symbol definitions to other program sections (psects). ACTION, unknown action code encountered Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: This message indicates a problem with the compiler, not with your code. User Action: Call Digital Services and file a Software Performance Report (SPR). ACTIONLEN, length of action block not as expected Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: This message indicates a problem with the compiler, not with your code. User Action: Call Digital Services and file a Software Performance Report (SPR). ALIASINUSE, universal alias name 'alias-name' is already in use Facility: LINK, Linker Utility Explanation: The specified alias name has already been associated with another symbol. User Action: Edit the option file to assign a unique alias to the symbol, and relink. ALIGN, data alignment trap Facility: SYSTEM, System Services Explanation: An alignment fault occurred in user code, and alignment fault reporting is enabled. User Action: None. This is an informational message. The program will run as if there were no alignment fault. A-2 New OpenVMS System Messages ALPHASHRNOTBAS, Alpha shareable images cannot contain based clusters Facility: LINK, Linker Utility Explanation: OpenVMS Alpha systems do not support basing clusters at a specific virtual address in shareable images. User Action: Remove the base address from all CLUSTER options used to build the OpenVMS Alpha shareable image. ALTRETADDR, alternate return address on stack in routine 'routine-descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: An instruction within a JSB routine tried to modify a return address on the stack to change the flow of control. This is not allowed on OpenVMS Alpha systems. User Action: To change the flow of control, rewrite the code that modifies the return address on the stack to return a status value to its caller. The status value can either cause the caller to branch to a given location or can contain the address of a special .JSB_ENTRY routine that the caller should invoke. APTEMPUSE, AP used as temporary register is converted to R12 in routine 'routine-descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: Because the routine modified AP, the compiler changed any use of AP in the routine to R12. User Action: None. This is an informational message. ARGLISHOME, argument list must be homed in caller Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The reference to AP caused the arguments to be homed. User Action: Inspect your code. No action is required if the following conditions are met: o The number of arguments is six or fewer, or the compiler found an explicit reference to the number of arguments o The argument list was homed in the last .CALL_ENTRY routine A-3 New OpenVMS System Messages If there are more than six arguments and no explicit reference to the number, specify the number in the argument max_args=n to the .CALL_ENTRY directive. If the argument list was not homed in the last .CALL_ENTRY routine, specify the argument home_arg=TRUE to the .CALL_ENTRY directive. ASSERTERR, assertion error, PC='xxxxxxxx', PS='xxxxxxxx' Facility: SYSTEM, System Services Explanation: An assertion that should have been true was false at execution time. User Action: Examine the PC location displayed in the message; check the program listing to verify that operands or variables are specified correctly. BADLABTYP, label type not recognized, type='decimal-number' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: This message indicates a problem with the compiler, not with your code. User Action: Call Digital Services and file a Software Performance Report (SPR). BAD_LINK, image, linked /NATIVE_ONLY, cannot call a translated routine Facility: IMGACT, Image Activator Explanation: An attempt by a native routine to call a translated routine failed because the image containing the native routine was not linked with the default linker qualifier, /NONATIVE_ONLY. An accompanying message identifies the native and translated images. User Action: Use the default linker qualifier, /NONATIVE_ ONLY, when linking an image that could call translated OpenVMS VAX images. BADLPINDEX, conditional linkage index ('decimal-number') is greater than that specified in end-of-module record ('decimal-number') in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: More linkage pairs were found in the named module than were specified in the end-of-module record for that module. This can indicate a problem with the A-4 New OpenVMS System Messages OpenVMS Alpha object language produced by the compiler that originally produced the module. User Action: Recompile the specified module, and relink. If the problem persists, use the ANALYZE/OBJECT utility for OpenVMS Alpha systems to collect additional information. If the compiler was provided by Digital Equipment Corporation, submit a Software Performance Report (SPR). BADPAGE, PFN 'page' marked BAD in memory descriptors; continuing anyway Facility: SDA, System Dump Analyzer Explanation: SDA accessed a bad page. User Action: None. SDA continues the operation and attempts to read the data. BADSTATUS, translation of symbol $STATUS has invalid format: 'text' Facility: MSGHLP, Help Message Utility Explanation: The DCL symbol $STATUS contains something other than a hexadecimal number in the form: "%Xnnnnnnnn". User Action: Retry the operation that created the error. BADSTRUCT, invalid value on /STRUCTURE qualifier Facility: INIT, INITIALIZE Command Explanation: An invalid value was specified on a /STRUCTURE qualifier. On OpenVMS Alpha systems, the only legal value for the /STRUCTURE qualifier is 2. On OpenVMS VAX systems, the only legal values are 1 and 2. User Action: Correct the command by specifying a legal value for the /STRUCTURE qualifier. BADVECTOR, insufficient/invalid device vector information information supplied Facility: SYSMAN, Cluster System Management Utility Explanation: The interrupt vector address specified for the device is incorrect. User Action: If you use the /NUM_VEC=vector-count qualifier, you must also specify the /VECTOR=vector-address qualifier. A-5 New OpenVMS System Messages Retry the command, being sure to enter the correct vector address for the device. The values must be longword aligned. To specify the vector address in octal or hexadecimal, precede the address with %O or %X, respectively. BASENOTALLW, basing shareable image cluster, file 'filename' not allowed for Alpha images, base ignored Facility: LINK, Linker Utility Explanation: The linker detected an attempt to base a shareable image cluster within an image. Basing shareable image clusters is not allowed on OpenVMS Alpha systems. User Action: Remove the base from the CLUSTER= clause, and relink the image. BINDFAIL, failed to bind reference at 'address' between sections at locations 'address' and 'address' in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: The /SECTION_BINDING qualifer is specified and a relative address reference crosses an image section boundary. The first address specified is the location of the address reference. The second and third addresses specified are the starting addresses of the image sections. This condition can occur if data exists in a code section. User Action: If the referenced image sections are intended to be installed resident, or if all the code section address references are intended to be optimized, the relative address dependency between image sections must be removed. BINDFAILS, binding failed, psect 'psect-name' spanned image section located at 'address' Facility: LINK, Linker Utility Explanation: The /SECTION_BINDING qualifer is specified and a program section extends across the end of one image section to the beginning of another. This causes a relative reference made within the program section to cross this boundary. User Action: Use clusters to create more, smaller image sections, one of which can completely contain the program section. A-6 New OpenVMS System Messages BOGUSCOL, invalid or inaccessible collate table Facility: RMS, VMS Record Management Services Explanation: One of the following conditions caused this error during a $CREATE operation for a key defined with a collated key type: o The format or size of the collate table is invalid. o The collating sequence for the collate table has not been specified or is inaccessible. User Action: Verify that any collated key definition in the FDL or the XABKEY is defined correctly and that the collating sequence has been specified and is accessible. The status value (STV) field of the FAB could contain a key of reference. BRANCHBET, branch between routines from routine 'routine- descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: A branch occurred from this routine to another routine. User Action: By default, the compiler saves and restores the contents of R2 through R11 if those registers are modified. If a register is modified in one routine, it is saved and restored by default in all routines with which the modifying routine shares code. Therefore, a routine can save and restore a register even though it does not directly modify that register. Examine your code for any registers between R2 and R12 whose contents you do not want saved and restored. If you find such registers, specify them with the output or scratch arguments to the appropriate entry point directive (.CALL_ ENTRY, .JSB_ENTRY, or .JSB32_ENTRY). BRINTOCAL, branch into CALL_ENTRY routine from JSB_ENTRY 'routine-descriptor' with non-scratch registers Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: A branch occurred into a CALL_ENTRY routine from a JSB_ENTRY routine with non-scratch registers. The A-7 New OpenVMS System Messages contents of these registers cannot be saved and restored in such a branch. User Action: If the contents of the registers do not have to be saved and restored, no change is necessary. If they do have to be restored and if the .JSB_ENTRY routine is trying to execute a RET on behalf of its caller, change the common code in the .CALL_ENTRY to a second .JSB_ENTRY that can be invoked from both routines. BUGCHECK, compiler bugcheck, please report problem to maintainers Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: This message indicates a problem with the compiler, not with your code. User Action: Call Digital Services and file a Software Performance Report (SPR). BUGTEXT, 'descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: This message indicates a problem with the compiler, not with your code. User Action: Call Digital Services and file a Software Performance Report (SPR). BYTALSTK, byte aligned stack in routine 'routine-descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected a byte-aligned stack in the routine. The compiler octaword-aligns the stack on calls. However, references to the byte-aligned stack within the routine can cause alignment faults. User Action: Inspect your code to determine if byte alignment of the stack is necessary. If not, change the alignment in your source code by padding the data elements or structures or by promoting the data structures from bytes to octawords. A-8 New OpenVMS System Messages CANTPARCAS, cannot parse CASE instruction Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The CASE instruction was not followed by an offset table, but instead depended on the program section (psect) placement by the linker to complete the instruction. User Action: Complete the instruction in the module, or build a table of addresses in a data program section, and replace the CASE instruction with code to select a destination address from the table and branch. CANTRESFP, cannot resolve FP reference in routine 'routine- descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The FP reference cannot be resolved because its offset is not a compile-time constant. User Action: Change the offset to a compile-time constant. CANTRESSTK, cannot resolve stack reference in routine 'routine- descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The SP reference cannot be resolved because its offset is not a compile-time constant. User Action: Change the offset to a compile-time constant. CBINDISABLE, section binding of CODE has been disabled Facility: LINK, Linker Utility Explanation: The /SECTION_BINDING=CODE qualifier was specified and the linker found dependencies between different image sections. The image is not eligible for code section binding. User Action: If the image is intended to be eligible for code section binding, the dependency between image sections must be removed by performing one or both of the following actions: o Modify the source code to eliminate the reference; then recompile and relink. o Use the CLUSTER=, COLLECT=, and PSECT_ATTR= linker options to put the references in the same image section. A-9 New OpenVMS System Messages CHECKUSE, check instruction use of BUGx Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: BUGx pertains to the VAX architecture. User Action: Use the EVAX-BUGCHK builtin instead. CHKRELADR, external relative addressing mode should be checked Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected the use of a label as an offset for an external address. User Action: Examine the instruction to determine if the referenced label is a code or data label. For example, MOVAB FOO+2 could be storing a code offset that will later be branched to. This should be changed. The only code addresses that can legally be stored for subsequent invocations by means of CALLS, JSB, or JMP instructions are routine entry point labels. CLOSEOUT, error closing 'filespec' as output Facility: EDT, EDT Editor Explanation: A VMS RMS error occurred while closing the specified output file. This message is accompanied by another RMS message indicating the reason for the error. For example, this message is accompanied by the RMS error ENT and the SYSTEM error NOPRIV if you attempted to exit from a file that does not have OWNER:DELETE privileges and a version limit exists for that file or for the directory in which the file is located. The RMS error ENT occurs on an attempt to delete the .TMP file. The ENT error indicates that the version exceeds the version limit for the file or directory. User Action: Follow the recovery procedure for the specified RMS message. For example, to correct the condition that produces the RMS error ENT, follow these steps: 1. Use the following command to recover your file: EDIT/RECOVER filename.filetype A-10 New OpenVMS System Messages The journal (.JOU) file called by the EDIT/RECOVER command might not contain the last few edits that you made to the file. Update the file as necessary. 2. Press Ctrl/Z to obtain the EDT asterisk command prompt. 3. At the asterisk prompt, write your file to a new file with a different file name and then exit from the EDT editor. For example: * WRITE NEWFILE.TXT * EXIT The new file contains the edits that you made prior to the error. To avoid this problem in the future, purge your files or use the SET FILE/VERSION command to raise the version limit for the files or for the directory. CODGENWARN, code generation warning Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The code generator detected a problem. This message indicates an internal compiler error in all cases except one. If you use an IPR number not supported by OpenVMS Alpha systems in an MTPR/MFPR instruction, this warning message is issued. User Action: Check to make sure that any IPR numbers in your code are supported on OpenVMS Alpha systems. If all are supported, the message indicates an internal compiler error. Call Digital Services and file a Software Performance Report (SPR). CONDCAFT, condition code C expected after JSB in routine 'routine-descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected an attempt to communicate by means of condition code C. The compiler does not permit implicit communication by means of condition codes. User Action: Revise the code to return a status value or a flag parameter instead. A-11 New OpenVMS System Messages CONDCIN, condition code C expected as input to routine 'routine-descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected an attempt to communicate by means of condition code C. The compiler does not permit implicit communication by means of condition codes. User Action: Revise the code to return a status value or a flag parameter instead. CONDNAFT, condition code N expected after JSB in routine 'routine-descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected an attempt to communicate by means of condition code N. The compiler does not permit implicit communication by means of condition codes. User Action: Revise the code to return a status value or a flag parameter instead. CONDNIN, condition code N expected as input to routine 'routine-descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected an attempt to communicate by means of condition code N. The compiler does not permit implicit communication by means of condition codes. User Action: Revise the code to return a status value or a flag parameter instead. CONDVAFT, condition code V expected after JSB in routine 'routine-descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected an attempt to communicate by means of condition code V. The compiler does not permit implicit communication by means of condition codes. User Action: Revise the code to return a status value or a flag parameter instead. A-12 New OpenVMS System Messages CONDVIN, condition code V expected as input to routine 'routine-descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected an attempt to communicate by means of condition code V. The compiler does not permit implicit communication by means of condition codes. User Action: Revise the code to return a status value or a flag parameter instead. CONDZAFT, condition code Z expected after JSB in routine 'routine-descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected an attempt to communicate by means of condition code Z. The compiler does not permit implicit communication by means of condition codes. User Action: Revise the code to return a status value or a flag parameter instead. CONDZIN, condition code Z expected as input to routine 'routine-descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected an attempt to communicate by means of condition code Z. The compiler does not permit implicit communication by means of condition codes. User Action: Revise the code to return a status value or a flag parameter instead. CONFOPTION, conflicting options: 'option' and 'option', Facility: LINK, Linker Utility Explanation: The specified options conflict. For example, a base address was specified for an OpenVMS VAX image being linked with the /BPAGE qualifier, or a symbol vector was specified for an OpenVMS Alpha executable or system image. No image is produced. User Action: Resolve the conflict and relink. A-13 New OpenVMS System Messages CONPSCATT, NOMOD attribute conflicts with 'attribute'; set to NO'attribute' in psect 'psect-name', module 'module-name', file 'filename' Facility: LINK, Linker Utility Explanation: Both the NOMOD attribute and the specified attribute were present for the specified OpenVMS Alpha program section (psect). The specified attribute was negated for that program section. User Action: None required. The NOMOD attribute of the program section can be specified only by the language processor that compiled the module. To reset the program section attribute that has been negated, use the PSECT_ATTR= option, setting the MOD attribute at the same time. CONTLINE, continuation line capacity exceeded Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: This message indicates a problem with the compiler, not with your code. User Action: Call Digital Services and file a Software Performance Report (SPR). COROUTCALL, co-routine call in routine 'routine-descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: An SP or FP reference in which the offset is not a compile-time constant was found in this routine. User Action: Rewrite the routine that initiates the coroutine linkage so that it passes an explicit callback routine address to the other routine. The coroutine initiator should then invoke the other routine with a JSB instruction. CTRLC_ACK, Ctrl/C received; cleaning up, please wait Facility: SDA, System Dump Analyzer Explanation: A Ctrl/C was entered during an uninterruptable operation. The Ctrl/C will be accepted when the operation completes. User Action: None. A-14 New OpenVMS System Messages DATINCODE, data in code stream Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: Data was found in the code stream. This condition is not allowed on OpenVMS Alpha systems. User Action: For implicit JSB parameters, pass the parameter value in a register. If any values are larger than a longword, put them in another program section (psect) and explicitly pass its address. For data contiguous with code in the code stream, rewrite the code so that the data is in a data program section. DBINDISABLE, section binding of DATA has been disabled, Facility: LINK, Linker Utility Explanation: The /SECTION_BINDING=DATA qualifier was specified and the linker found dependencies between data references in different image sections. The image is not eligible for data section binding. User Action: If the image is intended to be eligible for data section binding, the dependency between image sections must be removed by performing one or both of the following actions: o Modify the source code to eliminate the reference; then recompile and relink. o Use the CLUSTER=, COLLECT=, and PSECT_ATTR= linker options to put the references in the same image section. DECDIV, decimal divide by zero, PC='xxxxxxxx', PS='xxxxxxxx' Facility: SYSTEM, System Services Explanation: An arithmetic exception occurred as the result of an attempt to divide a decimal number by the value zero. User Action: Examine the PC location displayed in the message; check the program listing to verify that operands or variables are specified correctly. A-15 New OpenVMS System Messages DECINV, decimal invalid operand, PC='xxxxxxxx', PS='xxxxxxxx' Facility: SYSTEM, System Services Explanation: An arithmetic exception occurred as the result of performing an operation on a decimal operand that contained an invalid digit or sign. User Action: Examine the PC location displayed in the message; check the program listing to verify that operands or variables are specified correctly. DEVEXISTS, device unit already exists Facility: SYSTEM, System Services Explanation: The device you are attempting to connect is already connected to the system. User Action: Check the specified device name or enter the SYSMAN command IO SHOW DEVICE to display the devices connected to the system, their device drivers, and their I/O databases. DIRMASK, .MASK directive is not supported Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected use of the .MASK directive, which is used with .TRANSFER on OpenVMS VAX systems. Transfer vectors are not supported on OpenVMS Alpha systems. User Action: Remove the transfer vector from the code. In its place, specify a Linker options file that includes the SYMBOL_VECTOR statement when you link the object file. DIROPDEF, opcodes generated with .OPDEF not supported Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected operation codes generated with .OPDEF. Dynamic generation of code is not supported on OpenVMS Alpha systems. User Action: Replace .OPDEF with a macro. DIRREF, .REFxx directive is not supported Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected use of .REFxx, which is not supported on OpenVMS Alpha systems. User Action: Replace .REFxx with a macro. A-16 New OpenVMS System Messages DIRTRANS, .TRANSFER directive is not supported Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: A .TRANSFER directive was found. Transfer vectors are not supported on OpenVMS Alpha systems. User Action: Remove the transfer vector from the code. In its place, specify a Linker options file that includes the SYMBOL_VECTOR statement when you link the object file. DME, dynamic memory exhausted Facility: RMS, VMS Record Management Services Explanation: VMS RMS was unable to allocate additional process memory for the given request (usually an RMS $OPEN or $CONNECT system service call). Such requests can require a large number of buffers, large buffer sizes, or a combination of both. User Action: Increase the amount of available process memory or decrease the size or number of requested buffers. For process permanent files (such as DCL OPEN, DCL command procedures using "@filename", SYS$INPUT, SYS$OUTPUT, SYS$ERROR, and batch log files), the size of available memory is governed by the SYSGEN parameter PIOPAGES. The number of buffers and their sizes is governed by the DCL command SET RMS. Only 63 process permanent files can be opened at once; any attempt to open more such files produces this message. For image files, process memory is governed by the UAF parameter PGFLQUOTA and the SYSGEN parameter VIRTUALPAGECNT. The size and number of buffers is controlled by the application and/or the DCL command SET RMS. Image buffer space can also be controlled with the linker option of IOSEGMENT, which can determine the amount of fixed RMS memory allocated and the process region in which it is allocated. See the OpenVMS Linker Utility Manual for further information. A-17 New OpenVMS System Messages DRVEXISTS, device driver already loaded; not superceded Facility: SYSTEM, System Services Explanation: The driver you are attempting to load is already loaded on the system. User Action: Check the specified driver name or enter the SYSMAN command IO SHOW DEVICE to display the device drivers loaded into the system. DRVNOTVALID, device driver failed DPT consistency checks Facility: SYSTEM, System Services Explanation: The driver is not linked correctly. User Action: Follow the documented linking procedures for OpenVMS Alpha device drivers. DRV_NOUNLOAD, device driver is not unloadable Facility: SYSTEM, System Services Explanation: The specified device driver cannot be unloaded. User Action: If you want to reload this device driver, reboot the system. EMPTYNEST, nested command procedures are not supported Facility: SDA, System Dump Analyzer Explanation: A nested SDA command procedure was detected. User Action: Rewrite the command procedure so that it is not nested. EXCPC2NATIVE, Translated Exception PC 'pc-id' replaced with Native PC 'pc-id' by condition handler 'handler'. Facility: TIE, Translated Image Environment Explanation: An exception occurred in translated code and a user-written exception handler replaced the translated PC in the signal array with a native PC. A translated PC can only be replaced by another translated PC. User Action: Modify the exception handler in the original program and retranslate. A-18 New OpenVMS System Messages EXCPC2VAX, Native Exception PC 'pc-id' replaced with VAX PC 'pc-id' by condition handler 'handler'. Facility: TIE, Translated Image Environment Explanation: An exception occurred in translated code and a user-written exception handler replaced the native PC in the signal array with a translated PC. A native PC can only be replaced by another native PC. User Action: Modify the exception handler in the original program and retranslate. EXPSTACKC, expression was not completed, depth='decimal-number' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: This message indicates a problem with the compiler, not with your code. User Action: Call Digital Services and file a Software Performance Report (SPR). EXPSTACKO, expression stack overflow, depth='decimal-number' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: This message indicates a problem with the compiler, not with your code. User Action: Call Digital Services and file a Software Performance Report (SPR). EXPSTACKU, expression stack underflow Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: This message indicates a problem with the compiler, not with your code. User Action: Call Digital Services and file a Software Performance Report (SPR). FIEINALI, Field in aligned structure not naturally aligned. Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: An unaligned field was detected in an aligned data structure. User Action: Align the field on a natural boundary, that is, a byte on a byte boundary, a word on a word boundary, a longword on a longword boundary, and so forth. A-19 New OpenVMS System Messages FILEOPEN, Message redirection file is already open. Facility: TIE, Translated Image Environment Explanation: The TIE has encountered an internal error. User Action: Submit a Software Performance Report (SPR) describing the error message. FIXUPERR, error when 'calling-image' referenced 'shareable- image' Facility: IMGACT, Image Activator Explanation: This message is displayed as a secondary error message to the BAD_LINK message or the SYMVECMIS message. This message identifies the conflicting calling image and shareable image that caused the error. In the case of a SYMVECMIS error, there was an inconsistency between a shareable image that was activated at runtime and information used to create an image that calls it. For a BAD_LINK error, a native image that was linked /NATIVE_ONLY attempted to call a translated routine. User Action: For a SYMVECMIS error, link the calling image against the correct version of the shareable image, or, for a translated image, use the correct .IIF file if the image is built using the VEST utility. For a BAD_LINK error, link the native image with the default linker qualifier, /NONATIVE_ONLY, so that this image can call translated code. FLTINE, floating inexact result, PC='xxxxxxxx', PS='xxxxxxxx' Facility: SYSTEM, System Services Explanation: The IEEE floating point Inexact trap was enabled, and a floating point operation produced an inexact result. User Action: Examine the PC location displayed in the message; check the program listing to verify that operands or variables are specified correctly. A-20 New OpenVMS System Messages FLTINV, floating invalid operation, PC='xxxxxxxx', PS='xxxxxxxx' Facility: SYSTEM, System Services Explanation: An arithmetic exception occurred as the result of operating on a non-finite floating point number or attempting an invalid operation such as 0/0 or SQRT(-1). User Action: Examine the PC location displayed in the message; check the program listing to verify that operands or variables are specified correctly. FMTERR, error formatting or displaying text Facility: MSGHLP, Help Message Utility Explanation: Help Message cannot properly display the requested information for the reason stated in an accompanying message. User Action: Take action based on the accompanying message. FPNOTFOUND, could not read FP from process state Facility: SDA, System Dump Analyzer Explanation: SDA cannot execute the SHOW CALL command because it cannot read the current frame pointer (FP). User Action: Execute the SHOW CALL command again using the /NEXT_FP qualifier. FRMPTRMOD, frame pointer modified Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: A write to FP was detected. User Action: Remove any stack frame references. GENTRAP, software trap, code='xxxxxxxx', PC='xxxxxxxx', PS='xxxxxxxx' Facility: SYSTEM, System Services Explanation: An exception occurred as the result of executing a GENTRAP PALcode instruction. User Action: Examine the PC location displayed in the message; check the program listing to verify that operands or variables are specified correctly. A-21 New OpenVMS System Messages GETJPI, Sys$getjpi returned an error code. Facility: TIE, Translated Image Environment Explanation: The TIE has encountered an internal error. User Action: Submit a Software Performance Report (SPR) describing the error message. GLOBENTRY, global entry point 'descriptor' must be declared Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected a global entry point with no entry declaration. User Action: Use the most suitable compiler entry point directive, either .CALL_ENTRY, .JSB_ENTRY, or .JSB32_ENTRY. GLOBLABMUS, global labels must be declared in code psects Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected a global label with no entry declaration. User Action: Use the most suitable compiler entry point directive, either .CALL_ENTRY, .JSB_ENTRY, or .JSB32_ENTRY. HIFENTRIES, There were 'number' HIF entries appended to 'filename'. Facility: TIE, Translated Image Environment Explanation: While interpreting VAX code in a translated image, the TIE discovered VAX entry points that were not detected when the image was translated. When the program finished executing, the TIE created the .HIF file specified and then recorded the VAX entry points it detected while interpreting code. User Action: To improve the performance of the translated image, retranslate the original image with the .HIF file specified in the message. VEST uses the .HIF file entries to find and translate code it did not detect in a previous translation. You can disable all the .HIF entry messages either at translation or at runtime. When translating an image, use the /NOFEEDBACK qualifier in the VEST command line. At runtime, you can define the logical name TIE$FEEDBACK_ DIRECTORY to point to a null device (nl:, for example). A-22 New OpenVMS System Messages HIFENTRIESWRITTEN, 'filename' created. There were 'number' entries written to it. Facility: TIE, Translated Image Environment Explanation: While interpreting VAX code in a translated image, the TIE discovered VAX entry points that were not detected when the image was translated. When the program finished executing, the TIE recorded those VAX entry points in the existing .HIF file that is identified in the message. User Action: To improve the performance of the translated image, retranslate the original image with the .HIF file specified in the message. VEST uses the .HIF file entries to find and translate code it did not detect in a previous translation. You can disable all the .HIF entry messages either at translation or at runtime. When translating an image, use the /NOFEEDBACK qualifier in the VEST command line. At runtime, you can define the logical name TIE$FEEDBACK_ DIRECTORY to point to a null device (nl:, for example). HIFENTRY, There was one HIF entry appended to 'filename'. Facility: TIE, Translated Image Environment Explanation: While interpreting VAX code in a translated image, the TIE discovered a single VAX entry point that was not detected when the image was translated. When the program finished executing, the TIE created the .HIF file specified and then recorded the VAX entry point it detected while interpreting code. User Action: To improve the performance of the translated image, retranslate the original image with the .HIF file specified in the message. VEST uses the .HIF file entries to find and translate code it did not detect in a previous translation. You can disable all the .HIF entry messages either at translation or at runtime. When translating an image, use the /NOFEEDBACK qualifier in the VEST command line. At runtime, you can define the logical name TIE$FEEDBACK_ DIRECTORY to point to a null device (nl:, for example). A-23 New OpenVMS System Messages HIFENTRYWRITTEN, 'filename' created. There was one entry written to it. Facility: TIE, Translated Image Environment Explanation: While interpreting VAX code in a translated image, the TIE discovered a single VAX entry point that was not detected when the image was translated. When the program finished executing, the TIE recorded the VAX entry point in the existing .HIF file that is identified in the message. User Action: To improve the performance of the translated image, retranslate the original image with the .HIF file specified in the message. VEST uses the .HIF file entries to find and translate code it did not detect in a previous translation. You can disable all the .HIF entry messages either at translation or at runtime. When translating an image, use the /NOFEEDBACK qualifier in the VEST command line. At runtime, you can define the logical name TIE$FEEDBACK_ DIRECTORY to point to a null device (nl:, for example). HINTRTN, compiler hint: Auto-preserved registers: xx in routine 'routine-descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected registers that are saved and restored by default. User Action: Inspect the code to confirm that you do want the contents of the registers saved and restored. If you do not, then specify those registers with the argument scratch= in the entry declaration. HPARITH, high performance arithmetic trap, Imask='xxxxxxxx', Fmask='xxxxxxxx', summary='xx', PC='xxxxxxxx', PS='xxxxxxxx' Facility: SYSTEM, System Services Explanation: The image performed an arithmetic or conversion operation that resulted in an arithmetic trap. When an arithmetic exception condition is detected, several instructions can be in various stages of execution. These instructions are allowed to complete before the arithmetic trap can be initiated. Some of these instructions can themselves cause further arithmetic traps. Thus it is possible for several arithmetic traps to be reported simultaneously. A-24 New OpenVMS System Messages The Imask parameter records all integer registers that were targets of the instructions that set the bits in the exception summary. Bit 0 corresponds to R0, bit 1 corresponds to R1, and so on. The Fmask parameter records all floating point registers that were targets of the instructions that set the bits in the exception summary. Bit 0 corresponds to F0, bit 1 corresponds to F1, and so on. The exception summary parameter records the various types of arithmetic traps that can occur together: _____________________________________________________________ Bit_Set__Meaning_____________________________________________ Bit 0 Software Completion All the other arithmetic exception bits were set by floating-operate instructions with the /S software completion trap modifier set. Bit 1 Invalid Operation An attempt was made to perform a floating arithmetic, conversion, or comparison operation, and one or more of the operand values was illegal. Bit 2 Division by Zero An attempt was made to perform a floating divide operation with a divisor of zero. Bit 3 Overflow A floating arithmetic or conversion operation overflowed the destination exponent. Bit 4 Underflow A floating arithmetic or conversion operation underflowed the destination exponent. Bit 5 Inexact Result A floating arithmetic or conversion operation gave a result that differed from the mathematically exact result. A-25 New OpenVMS System Messages _____________________________________________________________ Bit_Set__Meaning_____________________________________________ Bit 6 Integer Overflow An integer arithmetic operation or a conversion operation from floating to integer overflowed ____________the_destination_precision._______________________ The PC parameter is the virtual address of the next instruction. This is defined as the virtual address of the first instruction not executed after the trap condition was recognized. User Action: Check the program listing to verify that the operands or variables are specified correctly. HWRPB_NF, could not find HWRPB in dump file; cannot analyze crash dump Facility: SDA, System Dump Analyzer Explanation: SDA could not find the hardware restart parameter block (HWRPB) during initialization. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. IAMCNFUSD, Value out of range. Please submit an SPR. Facility: TIE, Translated Image Environment Explanation: The TIE has encountered an internal error. User Action: Submit a Software Performance Report (SPR) describing the error message. IGCNOTDONE, VAX IGC didn't achieve a granular boundary for AST at 'address', detected at 'address'. Facility: TIE, Translated Image Environment Explanation: The TIE granularity controller was unable to preserve instruction granularity for an AST at the location specified in the message. This message can only occur if the image was translated using the qualifier /PRESERVE=INSTRUCTION_ATOMICITY. User Action: Submit a Software Performance Report (SPR) for VEST that describes the error message and includes the VEST- generated machine code at the basic block surrounding the address given. A-26 New OpenVMS System Messages ILLABSADR, illegal absolute addressing mode Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: An absolute address was detected. Absolute addresses are not allowed on OpenVMS Alpha systems. User Action: Replace the absolute address with a valid relative address. ILLDBGETIR, cannot do fixup for ETIR record ('record-type') in debug/traceback context Facility: LINK, Linker Utility Explanation: Illegal fixup information was discovered in a debug or traceback context in an object file. Examples include fixups for quadword addresses, linkage pairs, and code addresses. User Action: Collect as much information as possible about the object module and submit a Software Performance Report (SPR) for the compiler that generated the module. ILLFSTCHR, illegal field type character 'character' encountered at line 'line-number' Facility: MSGHLP, Help Message Utility Explanation: The specified line in a .MSGHLP file does not contain a 1, 2, 3, 4, or 5 prefix. User Action: Update the specified line in the .MSGHLP file to contain the correct numerical prefix: 1-Message 2-Facility 3-Explanation 4-User Action 5-Comment ILLPCOFF, illegal PC offset addressing mode Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: An address with a PC offset was detected. Such addressing is not allowed on OpenVMS Alpha systems. User Action: Revise the code to eliminate the PC offset in the address. A-27 New OpenVMS System Messages ILLRELADR, illegal relative addressing mode Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: A branch to a destination that is the offset from a label (for example, BLSS FOO+2) is not allowed. User Action: Place a label at the destination and branch to that label. ILLRETEXC, illegal RET in EXCEPTION_ENTRY routine 'routine- descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The EXCEPTION_ENTRY routine contains a RET instruction which is not valid on OpenVMS Alpha systems. User Action: Replace the RET instruction with an REI instruction. ILLRSBCAL, illegal RSB in CALL_ENTRY routine 'routine- descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The code path to which the CALL_ENTRY routine branched contains an RSB instruction. Such a CALL routine will fail at run time. User Action: Replace the RSB instruction with a RET instruction. ILLRSBEXC, illegal RSB in EXCEPTION_ENTRY routine 'routine- descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The EXCEPTION_ENTRY routine contains an RSB instruction that is not valid on OpenVMS Alpha systems. User Action: Replace the RSB instruction with an REI instruction. ILLRSDM, operation not allowed on resource domain Facility: SYSTEM, System Services Explanation: The process failed on an attempt at one of the following operations: o Reading a lock value block in a resource domain not accessed for read. A-28 New OpenVMS System Messages o Writing a lock value block in a resource domain not accessed for write. o Queuing a lock in a resource domain not accessed for lock. o Queuing a lock in a resource domain owned by a more privileged access mode. User Action: Determine what operation is failing. Use SHOW SECURITY to verify the access allowed to the specified resource domain. ILLSTATINI, illegal static initialization Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: An invalid static initialization was detected. The compiler restricts operations to opr where opr represents all MACRO operators and where constant can be an expression that equates to a compile time constant. This restriction applies to external symbols and operands that are labels in other program sections (psects). User Action: Revise the code to contain no more than two external symbols. Static initialization directives using any operations are supported on literals, symbols with constant values, and labels in the same program section (psect). IMAGENF, 'filename' not found; check current process or EXEC list Facility: SDA, System Dump Analyzer Explanation: The image file specified in a READ command cannot be found. User Action: Check the READ command to ensure that the image name is entered correctly, and check the image lists to ensure that the image exists. A-29 New OpenVMS System Messages INSFILLM, open file limit is too low to complete link - increase FILLM, Facility: LINK, Linker Utility Explanation: The value of the FILLM process quota parameter is too low. The linker cannot open enough files to complete the link. User Action: Use the OpenVMS Authorize utility to increase the FILLM quota in the User Authorization File. Relink after you log out and log in again to reset the FILLM quota. If appropriate, consider using object libraries instead of object modules to reduce the number of files the linker keeps open simultaneously. INSFREEREG, insufficient free registers Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: There were not enough unused Alpha registers available to implement needed condition codes. The code continues to compile, using R31 as the condition code register. User Action: Reduce the use of Alpha registers. To ensure that this problem does not occur, use only VAX registers. INSNOTSUP, instruction not supported Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected an instruction that is not supported on OpenVMS Alpha systems. User Action: Investigate whether you can substitute a builtin function. INTERLOCK, callable MSGHLP routines are not reentrant Facility: MSGHLP, Help Message Utility Explanation: A program called a MSGHLP routine while another code thread in the same program was also calling a MSGHLP routine. User Action: Retry the operation. A-30 New OpenVMS System Messages INVALID_HWRPB, VBN for HWRPB in header is invalid; searching dump file Facility: SDA, System Dump Analyzer Explanation: SDA could not find the hardware restart parameter block (HWRPB) in the dump header, and is searching the dump file. User Action: None. INVBRNCOD, Invalid branch code - Address: 'address' Code: 'code'. Facility: TIE, Translated Image Environment Explanation: The TIE has encountered an internal error. User Action: Submit a Software Performance Report (SPR) describing the error message. INVIMAGEINDEX, Invalid image index - Address: 'address' Index: 'index'. Facility: TIE, Translated Image Environment Explanation: The TIE has encountered an internal error. User Action: Submit a Software Performance Report (SPR) describing the error message. INVREMQHI, Invalid remqhi operation. Facility: TIE, Translated Image Environment Explanation: The TIE has encountered an internal error. User Action: Submit a Software Performance Report (SPR) describing the error message. INVSPECIAL, Invalid TIE processing value 'value'. Please submit an SPR. Facility: TIE, Translated Image Environment Explanation: The TIE has encountered an internal error. User Action: Submit a Software Performance Report (SPR) describing the error message. A-31 New OpenVMS System Messages INVSS, System service at 'address' is not available under OpenVMS Alpha. Facility: TIE, Translated Image Environment Explanation: A translated program has attempted to use a system service not supported on OpenVMS Alpha systems that is supported on OpenVMS VAX systems. User Action: Either rewrite the original OpenVMS VAX program to eliminate the reference to the unsupported system service or ensure that the unsupported code does not execute at runtime. Then retranslate the image. INVSTACK, invalid/inaccessible 'stack-pointer' stack pointer = 'address' Facility: SDA, System Dump Analyzer Explanation: The SHOW STACK command cannot access the stack pointer. User Action: None. IOADDRESS, the 'data-structure' is located at address 'address' Facility: SYSMAN, Cluster System Management Utility Explanation: This informational message reports the address of the specified data structure. User Action: None. IONOTEXIST, no 'data-structure' exists for this device Facility: SYSMAN, Cluster System Management Utility Explanation: The connection of the device or driver failed. User Action: Check the accompanying messages for more detailed information and respond accordingly. IOPREFIX, the current prefix list is 'list' Facility: SYSMAN, Cluster System Management Utility Explanation: The specified prefix list is currently in effect. User Action: None. This is an informational message. A-32 New OpenVMS System Messages JSBHOME, argument list use in JSB_ENTRY 'routine-descriptor' required homed argument list in caller Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected a use of AP in the JSB_ ENTRY routine. For this usage to work, the argument list in the caller must be homed. User Action: Ensure that the argument list in the caller is homed. Do this by specifying the argument home_args=TRUE to the entry point directive of the caller. If there are more than six arguments in the argument list in the caller and the number is not explicitly referenced, you must also specify the number with the argument max_args=n to the entry point directive. JSBMODEXC, JSB routine 'routine-descriptor' modifies exception handler address Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The JSB routine modified the exception handler address, (0(FP)). On OpenVMS Alpha systems, the exception handler can be modified only within the .CALL_ENTRY routine that uses it. User Action: Move the declaration to the .CALL_ENTRY routine. JSBRCHHOM, argument list use reachable from JSB_ENTRY 'routine- descriptor' required homed argument list in caller Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The argument list usage in the routine is reachable from a JSB_ENTRY routine. Therefore, the argument list in the .CALL_ENTRY routine must be homed. User Action: Ensure that the argument list in the CALL_ENTRY routine is homed. Do this by specifying the argument home_ args=TRUE to the entry point directive of the caller. If there are more than six arguments in the argument list in the caller and the number is not explicitly referenced, you must also specify the number with the argument max_args=n to the entry point directive. A-33 New OpenVMS System Messages KNOWN, Duplicate image detected in list of images: 'image' Facility: TIE, Translated Image Environment Explanation: The TIE has encountered an internal error. User Action: Submit a Software Performance Report (SPR) describing the error message. LABSTACKO, label stack overflow, depth='decimal-number', label='label-descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: This message indicates a problem with the compiler, not with your code. User Action: Call Digital Services and file a Software Performance Report (SPR). LANGUAGE, language-specific routine returned bad status Facility: MSGHLP, Help Message Utility Explanation: A local, language-specific routine from SYS$SHARE:MSGHLP$language.EXE returned a bad status value. This message can occur only when a localized version of Help Message has been installed (for example, on a Japanese OpenVMS system). An accompanying message gives more details. User Action: Take action based on the accompanying message. LPNOTMAPPED, attempt to write to conditional linkage at unmapped address ('address'.) in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: The linker attempted to resolve a conditional linkage pair at an address that was not mapped in the virtual memory of the image. User Action: Collect as much information as possible about the link and submit a Software Performance Report (SPR). MAXARGEXC, MAX_ARGS exceeded in routine 'routine-descriptor', using higher value Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: This message is displayed for either of the following reasons: o An argument reference for a homed argument list was found that exceeded the count specified in max_args A-34 New OpenVMS System Messages o The argument home_args=TRUE was specified without the argument max_args User Action: If an argument reference for a homed argument list was found that exceeded the count specified in max_ args, increase the count. If the argument home_args=TRUE was specified without the argument max_args, specify the argument max_args. MAXARGUSE, MAX_ARGS value used for homed argument list is 'decimal-number' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The max_args clause in the .CALL_ENTRY directive of a procedure, whose arguments require homing, was not specified. The compiler assumed the highest argument referenced and homed the argument list. User Action: Check the code to determine if the number of arguments is less than or equal to the number reported by this message. If it is, no action is necessary. If the number of arguments is greater, specify the number with the max_args clause to the .CALL_ENTRY directive. MDFERR, error accessing HELP/MESSAGE database file 'filespec' Facility: MSGHLP, Help Message Utility Explanation: Help Message cannot access the named .MSGHLP$DATA file for the reason specified in an accompanying message. User Action: Take action based on the accompanying message. Some possibilities to investigate are: o Do you have write access for the named .MSGHLP$DATA file? o Is the named .MSGHLP$DATA file included in the default search path defined by logical name MSGHLP$LIBRARY or in a search path specified by the /LIBRARY qualifier? o If you used the /LIBRARY qualifier to specify the .MSGHLP$DATA file, did you make a typing error? A-35 New OpenVMS System Messages MDFIERR, error accessing database update file 'filespec' Facility: MSGHLP, Help Message Utility Explanation: Help Message cannot access the named .MSGHLP file for the reason specified in an accompanying message. User Action: Take action based on the accompanying message. For example, check to see whether you incorrectly typed the .MSGHLP file specification. MEMORYALC, unable to allocate dynamic memory Facility: MSGHLP, Help Message Utility Explanation: Help Message cannot allocate dynamic memory. See the error returns section of the LIB$GET_VM routine in the VMS Run-Time Library Routines Volume for possible reasons for the error. User Action: Refer to the VMS Run-Time Library Routines Volume for more information. MEMREFNOT, memory reference not naturally aligned in routine 'routine-descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected a memory reference that is not naturally aligned (that is, a byte on a byte boundary, a word on a word boundary, a longword on a longword boundary, and so forth). User Action: If performance is a concern, correct the alignment by padding the memory reference or by promoting it to a larger unit. MISTRAN, missing nickname translation record at line 'line- number' Facility: MSGHLP, Help Message Utility Explanation: The .MSGHLP file contains a line with a 9 prefix (designating a nickname) that is not immediately followed by a line with a 0 prefix (designating a nickname translation). User Action: Specify the missing nickname translation on a line with a 0 prefix immediately following the specified "9" line, or delete the untranslated nickname line from the .MSGHLP file. A-36 New OpenVMS System Messages MULTLKSEC, routines which share code must use the same linkage psect Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected a routine that shares code with another routine but does not use the same linkage section. User Action: Put the routines that share code in the same linkage section. MUSTBEJSB, branch target must be declared JSB_ENTRY Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected a routine, which is a branch target, without a JSB entry directive. User Action: Declare the JSB entry point with either the .JSB_ENTRY or JSB32_ENTRY directive. NOCALLTRANS, code at 'address' cannot call translated code Facility: SYSTEM, System Services Explanation: The autojacketing routine EXE$NATIVE_TO_ TRANSLATED aborted the user program. The native routine containing the specified address does not have a procedure signature block associated with it. User Action: Compile the native routine using the /TIE qualifier. The debugger can identify the native routine by the address cited in the message. To enable the native routine to call a translated routine, use the /NONATIVE_ONLY default for the LINK command when linking the image that contains the native routine. NOCONTEXT, VAX context not found during exception processing. Please submit an SPR. Facility: TIE, Translated Image Environment Explanation: The TIE has encountered an internal error. User Action: Submit a Software Performance Report (SPR) describing the error message. A-37 New OpenVMS System Messages NOENTRYDECL, no entry declaration could be found for a code psect Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected a code psect with no entry declarations. User Action: Add the appropriate entry declarations. NOEXITHANDLER, Unable to initialize exit handler. Facility: TIE, Translated Image Environment Explanation: The TIE has encountered an internal error. User Action: Submit a Software Performance Report (SPR) describing the error message. NOEXTEND, previous $EXTEND operation failed - further $EXTENDs prohibited Facility: RMS, VMS Record Management Services Explanation: An $EXTEND operation failed because the NOEXTEND bit is set in the prolog of a relative file. This bit was set for data integrity purposes when a previous $EXTEND operation failed. The records in this relative file can still be read. User Action: In the relative file for which this error was reported, the records must be read and written to appropriate cells in a new relative file. The CONVERT utility can be used for this purpose only if there are no empty or deleted cells in the old file. NOFILECLOSED, Unable to close file 'filename'. Facility: TIE, Translated Image Environment Explanation: The TIE was unable to close an .HIF file for a reason stated in an accompanying message. User Action: Refer to the accompanying message. NOFILECONNECTED, Unable to connect to file 'filename'. Facility: TIE, Translated Image Environment Explanation: The TIE was unable to connect to an .HIF file for the reason stated in an accompanying message. User Action: Refer to the accompanying message. A-38 New OpenVMS System Messages NOFILEOPENED, Unable to open file 'filename'. Facility: TIE, Translated Image Environment Explanation: The TIE was unable to open an .HIF file for the reason stated in an accompanying message. User Action: Refer to the accompanying message. NOFILEWRIT, Unable to write to file 'filename'. Facility: TIE, Translated Image Environment Explanation: The TIE was unable to write to an .HIF file for the reason stated in an accompanying message. User Action: Refer to the accompanying message. NOHIFSTORE, Unable to allocate HIF store. Facility: TIE, Translated Image Environment Explanation: The TIE was unable to allocate memory to store .HIF file information because insufficient virtual memory was available. User Action: Investigate the reasons for the shortage of virtual memory and correct the problem if possible. NOINSHIFENT, Unable to insert HIF entry - Address: 'filename' Code: 'code'. Facility: TIE, Translated Image Environment Explanation: The TIE has encountered an internal error. User Action: Submit a Software Performance Report (SPR) describing the error message. NOLINKSTB, linker-generated symbol table file is illegal input module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: A linker-generated symbol table file was detected. Such a file is not legal input for building an OpenVMS Alpha image. User Action: Relink against the shareable image corresponding to the symbol table instead of the symbol table file itself. A-39 New OpenVMS System Messages NOMODATTIGN, psect attribute NOMOD is not user settable Facility: LINK, Linker Utility Explanation: The NOMOD attribute of a program section cannot be specified by the user. A compiler sets the NOMOD attribute on the basis of the contents of the program section. User Action: Remove the NOMOD attribute from the PSECT_ATTR= option specification. NOMPSCALL, psect 'psect-name' is marked NOMOD but has zero allocation in module 'module-name', file 'filename' Facility: LINK, Linker Utility Explanation: The specified program section was marked NOMOD by the linker, but no virtual memory is allocated for it; the object module is corrupt. NOMOD program sections must have virtual memory allocated. The NOMOD attribute of the program section is removed. User Action: File a Software Performance Report (SPR) against the compiler that produced the object module. NOMSGFND, unable to locate message translation for status 'status-code' Facility: MSGHLP, Help Message Utility Explanation: Help Message cannot translate the value passed in $STATUS or /STATUS into an OpenVMS system message. User Action: If you specified the /STATUS qualifier, check your input for an error. NOMTCHFND, no matching message description found at line 'line- number' Facility: MSGHLP, Help Message Utility Explanation: A request was made to delete a message that does not exist in the specified or implied .MSGHLP$DATA file. The message includes the line number where the unfound message is specified in the .MSGHLP file. User Action: If you attempted to delete the same message twice, this message does not flag a problem. To check whether the message exists in the database, enter the HELP /MESSAGE command and specify the message identifier (or other message text) in the search string. A-40 New OpenVMS System Messages __________________________ Note __________________________ The default database you access to output a message description can include multiple .MSGHLP$DATA files, whereas a delete operation accesses only one .MSGHLP$DATA file. When a search path is specified directly or by default, a delete operation is performed only on the first .MSGHLP$DATA file in the search path. __________________________________________________________ If the message is in the database and you are certain the correct .MSGHLP$DATA file is being accessed to delete the message, but with no success, check to see that the message text and facility name in the .MSGHLP file exactly match the same fields in the message display. NOOPTSYMV, symbol 'symbol-name' was defined by option and cannot be used in SYMBOL_VECTOR statement Facility: LINK, Linker Utility Explanation: A symbol defined by the SYMBOL= option cannot be included as a symbol vector entry using the SYMBOL_ VECTOR= option. User Action: Specify the symbol by using some means other than the SYMBOL option (for example, change the source and recompile), or remove the corresponding symbol vector entry. NOPAGESIZE, could not get page size from SYS$GETSYI Facility: SDA, System Dump Analyzer Explanation: When attempting to analyze a running system, SDA could not obtain the page size. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. NOPSCOVR, psect 'psect-name' in module 'module-name' will not be overlaid with psect in shareable image 'image-name' Facility: LINK, Linker Utility Explanation: The linker found symbol definitions in a program section that it is attempting to overlay. User Action: Ensure that program sections intended to be overlaid do not contain symbol definitions. A-41 New OpenVMS System Messages NOSUCHFAC, unknown facility name; use /FACILITY=? for complete list Facility: MSGHLP, Help Message Utility Explanation: The requested facility name does not appear in the specified messages database. By default, the database is SYS$COMMON:[SYSHLP]MSGHLP$LIBRARY.MSGHLP$DATA or a search path defined by logical name MSGHLP$LIBRARY. You can specify an alternate database by using /LIBRARY to specify a particular .MSGHLP$DATA file or another search path. User Action: If you typed in a facility name, check to see that you entered a valid facility and that there are no typing errors. If you enter more than one word in the facility name, be sure you enclose the string in double quotes and mimic the capitalization that is used in the database. Use the /FACILITY=? qualifier to output a list of all facility names in the database. NOSUCHVOL, no such volume Facility: SYSTEM, System Services Explanation: The specified volume does not exist. User Action: Verify the specified volume name and correct it if necessary. NOSYMVECT, symbol vector address for SYS$BASE_IMAGE.EXE not accessible Facility: SDA, System Dump Analyzer Explanation: On initialization, SDA could not access the symbol vector for SYS$BASE_IMAGE.EXE. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. NOTALPHAEOM, VAX end-of-module record found in Alpha object file 'filename' Facility: LINK, Linker Utility Explanation: An OpenVMS VAX end-of-module record was found in the specified OpenVMS Alpha object file. This is a language processor error. User Action: Submit a Software Performance Report (SPR) for the language processor. A-42 New OpenVMS System Messages NOTFLAGOPT, not a legal FLAG option Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected an illegal option to the FLAG qualifier to the MACRO/MIGRATION command. User Action: Revise the code to include only legal FLAG options. NOTFOUND, message not found in HELP/MESSAGE database Facility: MSGHLP, Help Message Utility Explanation: Help Message cannot find documentation for this message in a .MSGHLP$DATA file or search path specified by the /LIBRARY qualifier or in the default database, which is either SYS$COMMON:[SYSHLP]MSGHLP$LIBRARY.MSGHLP$DATA or a search path of .MSGHLP$DATA files defined by logical name MSGHLP$LIBRARY. User Action: Perform the following checks: o If you include a search string, check for typing errors and ensure that the string contains at least one word of three or more characters (shorter words are ignored in the search). o If you paste a message into the search string, check to see if you failed to delete any operation-specific value that was inserted into a variable field in the message. o Check to see if any installed .MSGHLP$DATA files that you require are missing from the search path defined by logical name MSGHLP$LIBRARY, or from a search path that you want to specify using the /LIBRARY qualifier. o Try to determine if the undocumented message was issued by a source other than OpenVMS Engineering. If so, report the missing message to the appropriate party. If you perform these checks and the search still fails, file a Software Performance Report (SPR) listing the missing message and the facility that produced it. A-43 New OpenVMS System Messages NOTINIMAGE, address 'address' not within a system or user image Facility: SDA, System Dump Analyzer Explanation: The address specified in a MAP command cannot be found within a system image or an installed image. User Action: Check the MAP command to ensure that the address has been entered correctly. NOTNATIVE, image is not an OpenVMS Alpha image Facility: IMGACT, Image Activator Explanation: The image was not linked using the OpenVMS Alpha linker. User Action: Use the OpenVMS Alpha linker to properly build the image before attempting to run it on an OpenVMS Alpha system. NOTPRESOPT, not a legal PRESERVE option Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected an illegal option to the PRESERVE qualifier to the MACRO/MIGRATION command. User Action: Revise the code to include only legal PRESERVE options. NOTVAXEOM, Alpha end of module record found in VAX object file 'filename', Facility: LINK, Linker Utility Explanation: An OpenVMS Alpha end-of-module record was found in the specified OpenVMS VAX object file. This is a language processor error. User Action: Submit a Software Performance Report (SPR) for the language processor. NOTVAXGSD, Alpha GSD record for symbol 'symbol-name' found in VAX object file 'filename', Facility: LINK, Linker Utility Explanation: An OpenVMS Alpha global symbol definition record for the specified symbol was found in the specified OpenVMS VAX object file. This is a language processor error. User Action: Submit a Software Performance Report (SPR) for the language processor. A-44 New OpenVMS System Messages NOTVAXHDR, Alpha module header record found in VAX object file 'filename', Facility: LINK, Linker Utility Explanation: An OpenVMS Alpha text information and relocation (TIR) record was found in the specified OpenVMS VAX object file. This is a language processor error. User Action: Submit a Software Performance Report (SPR) for the language processor. NOUSERSPEC, no user specified; mail not sent Facility: MAIL, Mail Utility Explanation: An attempt was made to send a file using the DCL command MAIL. However, no addressee was specified on the command line or at the To: prompt. The file was not sent. User Action: Specify the address of the user to whom you want to mail the file. Enter the address on the command line or in response to the To: prompt. NULPTRERR, null pointer error, PC='xxxxxxxx', PS='xxxxxxxx' Facility: SYSTEM, System Services Explanation: An exception occurred as the result of attempting to dereference a pointer and access location 0. 0 is not a valid pointer. User Action: Examine the PC location displayed in the message; check the program listing to verify that operands or variables are specified correctly. OCTAWORD, octaword data type not supported Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: An octaword data element was detected. User Action: Recode with a supported data type. OPTBASNOT, BASE= option not allowed for Alpha images Facility: LINK, Linker Utility Explanation: The linker encountered a BASE= option statement in a linker options file. User Action: Remove the BASE= option from the options file. If you are linking an executable image, you can specify a base address by using the CLUSTER= option with the base A-45 New OpenVMS System Messages address argument. Based shareable images are not supported on OpenVMS Alpha systems. OPTIGNALPHA, 'option' option ignored; not allowed for Alpha images Facility: LINK, Linker Utility Explanation: An option was supplied that does not apply to an OpenVMS Alpha image. The linker ignores the option. User Action: None. OPTIGNVAX, 'option' option ignored, not allowed for VAX images, Facility: LINK, Linker Utility Explanation: An option was supplied that does not apply to an OpenVMS VAX image. The linker ignores the option. User Action: None. OUTERR, error creating output file 'filespec' Facility: MSGHLP, Help Message Utility Explanation: Help Message cannot create the output file specified by the /OUTPUT qualifier for the reason stated in an accompanying message. User Action: Take action based on the accompanying message. OVERWRITE, this statement attempts to write over existing statements at offset 'hexadecimal-number' in psect 'psect- descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: This type of overwriting static data is not allowed on OpenVMS Alpha. User Action: If possible, change your code to one of the forms of overwriting data that is allowed. PAGECRIT, page file nearly full; system trying to continue Facility: SYSTEM, System Services Explanation: The system is running out of page file space. This message is more critical than the PAGEFRAG message. User Action: Create a new page file with more space. See the OpenVMS System Manager's Manual. A-46 New OpenVMS System Messages PAGEFRAG, page file filling up; please create more space Facility: SYSTEM, System Services Explanation: The system is running out of page file space. User Action: Create a new page file with more space. See the OpenVMS System Manager's Manual. PAGINGERR, error returned from paging subsystem Facility: MSGHLP, Help Message Utility Explanation: An error occurred while trying to output paged data to the terminal. User Action: Take action based on the accompanying message. PAGMISMATCH, page size of resulting image prevents execution on this machine, Facility: LINK, Linker Utility Explanation: The page size specified for the image by the /BPAGE qualifier is not compatible with the architecture of the system on which the image is being generated. The generated image will not run on the machine on which it was built. User Action: If the image is intended to run on OpenVMS Alpha systems having a page size larger than that specified by the /BPAGE qualifier, relink the image and specify a page size at least as large as the page size of any OpenVMS Alpha system on which the image is intended to run. PARSE, unable to parse keyword search string Facility: MSGHLP, Help Message Utility Explanation: An error occurred while trying to parse the keyword search string. User Action: Take action based on the accompanying message. PDRANGE_INVALID, /PD qualifier cannot be used with range Facility: SDA, System Dump Analyzer Explanation: An EXAMINE command has been issued that specifies both the /PD qualifier and a range of memory locations. User Action: Reenter the command and specify either the /PD qualifier or a range, but not both. A-47 New OpenVMS System Messages POSCODEGEN, possible run-time code generation Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected a branch to a stack location or to a static data area. Runtime code generation is not allowed on OpenVMS Alpha systems. User Action: Either remove or modify any code that branches to stack locations or to static data areas, or that builds instructions for later execution. POSCOROUT, possible co-routine call in routine 'routine- descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected a coroutine call that transfers control, by means of a JSB instruction, to a return address on the stack. Such coroutine calls are not supported on OpenVMS Alpha. User Action: Rewrite the routines participating in the coroutine linkage to exchange explicit callback addresses. Put the callback addresses in separate routines, one for each coroutine. Each coroutine can then invoke the other by using a JSB instruction to the other's callback address routine. PREVERROR, previous errors prevent further analysis Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler cannot continue its analysis. User Action: Correct the previous errors and recompile. PRIVINSTR, Emulation of privileged instruction 'instruction' requested. Facility: TIE, Translated Image Environment Explanation: The translated program attempted to execute a VAX privileged instruction by means of the TIE emulation facility. If the system were to respond correctly, it would issue an OPCDEC exception when the offending code executes. User Action: Rewrite the code in the original image to eliminate the unsupported privileged instruction and submit a Software Performance Report (SPR) for a VEST error. A-48 New OpenVMS System Messages PSCALIOPT, psect 'psect-name' alignment 'decimal-number' exceeds page size, reset to 'decimal-number' in options file 'filename', Facility: LINK, Linker Utility Explanation: The alignment of the specified program section places it on a boundary of greater granularity than the size of the page specified for the image. The linker reset the alignment of the psect to the size of the page. User Action: None required. If a psect alignment of greater granularity is required, relink the image and specify the /BPAGE qualifier with a value equal to or greater than the granularity required for the psect. QUADMEMREF, quadword memory references may be unaligned in routine 'routine-descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected a quadword memory reference that might be unaligned. Generally, the compiler tracks the alignment of registers only up to longword alignment. However, there are two exceptions: o The stack, which is tracked up to octaword alignment. o Registers used with an offset that has been declared quadword-aligned by the .SYMBOL_ALIGNMENT QUAD directive; these registers are always assumed to be quadword aligned. User Action: To improve performance, ensure that quadword references are quadword aligned. RANGEERR, range error, PC='xxxxxxxx', PS='xxxxxxxx' Facility: SYSTEM, System Services Explanation: An exception occurred as the result of encountering a value that was outside the range specified by the program or language. User Action: Examine the PC location displayed in the message; check the program listing to verify that operands or variables are specified correctly. A-49 New OpenVMS System Messages RETRANSLATE, The TIE interpreted an average of 'number' instructions per CPU second. Retranslate images that have .HIF files to improve performance. Facility: TIE, Translated Image Environment Explanation: When a translated program completes execution, the TIE issues this message if it has interpreted code. User Action: If an .HIF file is available, retranslate the original image so that VEST can use the .HIF file entries to locate and translate more code. The resulting translated image will require less interpretation at runtime. RD_IMAGE_ERR, 'filename' is sliced or has a symbol vector; use /IMAGE or /SYMVA qualifier Facility: SDA, System Dump Analyzer Explanation: The image file specified in a READ command is a sliced image or an image that has a symbols vector, but no /IMAGE or /SYMVA qualifier has been specified. User Action: Reenter the READ command and include the applicable /IMAGE or /SYMVA qualifier. RD_SYSIMG_ERR, 'filename' is a system image; use /IMAGE or /FORCE qualifier Facility: SDA, System Dump Analyzer Explanation: The image file specified in a READ command is an executive image, but no /IMAGE or /FORCE qualifier has been specified. User Action: Reenter the READ command and include the /IMAGE or /FORCE qualifier. REGDECCON, register declaration conflict Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected a conflict within a routine between a PRESERVE register clause and an OUTPUT or SCRATCH clause. User Action: Correct the register declarations. A-50 New OpenVMS System Messages RETADDRMOD, return address modified in routine 'routine- descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected an attempt to modify the return address. This is not allowed on OpenVMS Alpha. User Action: Rewrite the code that modifies the return address on the stack to instead return a status value to its caller. The status value can either cause the caller to branch to a given location or can contain the address of a special .JSB_ENTRY routine the caller should invoke. In the latter case, the caller should RSB immediately after issuing the JSB to a special .JSB_ENTRY routine. RETADDRPOP, return address popped in routine 'routine- descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected the removal of the return address from the stack. This is not allowed on OpenVMS Alpha. User Action: Rewrite the routine so that it returns a status value to its caller that indicates that the caller should return to its caller. Alternatively, the initial caller could pass the address of a continuation routine, to which the lowest-level routine can JSB. When the continuation routine RSBs back to the lowest-level routine, the lowest- level routine RSBs. RETADDRREF, return address referenced in routine 'routine- descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected an attempt to read the return address from the top of the stack. This method is often used in VAX MACRO code to save the return address for a later JMP. The return address cannot be accessed on OpenVMS Alpha. User Action: Rewrite the code to do a normal RSB. A-51 New OpenVMS System Messages RETCALLER, return to caller's caller in routine 'routine- descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected the removal of the return address from the stack. This is not allowed on OpenVMS Alpha. User Action: Rewrite the routine so that it returns a status value to its caller that indicates that the caller should return to its caller. Alternatively, the inital caller could pass the address of a continuation routine, to which the lowest-level routine can JSB. When the continuation routine RSBs back to the lowest-level routine, the lowest-level routine RSBs. RETINJSB, RET in JSB_ENTRY 'routine-descriptor' with non- scratch registers Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: A RET instruction was detected in a JSB_ENTRY routine that preserves registers. These registers will not be restored when taking the RET path. User Action: Verify that the registers preserved by the JSB_ENTRY routine do not need to be restored when the RET instruction is executed. RUNTIMSTK, run time stack differences prevent accurate stack tracing Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: A label was found that can be reached with two different stack depths, depending on flow path. This can produce less efficient code. User Action: Check stack updates for correctness on all paths. SELFMODCOD, self-modifying code in routine 'routine-descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected a branch to a stack location or to a static data area. User Action: Either remove or modify the code that branches to stack locations, or branches to static data areas, or builds instructions for later execution. A-52 New OpenVMS System Messages SETLONG, SETLONG target not recognized, target='hexadecimal- number' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: This message indicates a problem with the compiler, not with your code. User Action: Call Digital Services and file a Software Performance Report (SPR). SHRWRNERS, compilation warnings in shareable image file 'filename', Facility: LINK, Linker Utility Explanation: The specifed shareable image has compilation warnings. User Action: Correct the source, recompile and relink the shareable image, and relink any images linked against the shareable image. SORTERR, error returned while sorting Facility: MSGHLP, Help Message Utility Explanation: An error occurred while trying to sort the output text. User Action: Take action based on the accompanying message. If you get a NO_WRK message, the sort you are attempting requires more memory than is available, and MSGHLP is not currently designed to use work files. Try any of the following alternatives: o Ask your system manager to raise your SYSUAF quota (by specifying the /PGFLQUOTA qualifier in the AUTHORIZE command MODIFY). Then log in again and retry the MSGHLP operation. o Ask a user with a higher SYSUAF quota (for example, a system manager) to attempt the MSGHLP operation for you. o Retry the MSGHLP operation and specify /BRIEF with /SORT. o Retry the MSGHLP operation without specifying /SORT. A-53 New OpenVMS System Messages STACKNTFND, stack range not found; dumping up to invalid page Facility: SDA, System Dump Analyzer Explanation: The range of memory locations specified in a SHOW STACK command is invalid. User Action: Reissue the SHOW STACK command, specifying a valid memory range. STKBNDEXC, stack boundary exceeded in routine 'routine- descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The stack was popped beyond the current routine's return address. User Action: Either remove the stack frame reference or pre- allocate space on the stack. In the latter case, if the size of a field is extended, the current instruction will not access all the data. However, by pre-allocating the space, the compiler can detect and report that problem. STKFRMREF, stack frame reference in routine 'routine- descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected a reference to a location at a negative offset from FP. User Action: Eliminate the reference to data pushed on the stack by its caller. Instead, pass the required data as parameters or pass a pointer to the stack base from which the data can be read. STKOVF, stack overflow, PC='xxxxxxxx', PS='xxxxxxxx' Facility: SYSTEM, System Services Explanation: An attempt to allocate working storage on the stack exceeded the memory available for the stack. User Action: Examine the PC location displayed in the message; check the program listing to verify that operands or variables are specified correctly. A-54 New OpenVMS System Messages STORCODLAB, stored code labels must be declared entry points Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: An instruction such as MOVAx or PUSHAx that is used to store the address of a code label was not declared as an entry point. User Action: Add the appropriate entry declaration, either .JSB_ENTRY, or .JSB32_ENTRY, or .CALL_ENTRY. STR, user structure (FAB/RAB) became invalid during operation Facility: RMS, VMS Record Management Services Explanation: The FAB or RAB is invalid. This error can be detected only by testing R0. User Action: Verify that the call to the VMS RMS service is coded correctly. Ensure that a pointer is passed to an accessible FAB or RAB. If the FAB or RAB was dynamically allocated, include a test for the allocation failing. STRLENERR, string length error, PC='xxxxxxxx', PS='xxxxxxxx' Facility: SYSTEM, System Services Explanation: The length specified for a string was negative or it was larger than allowed. User Action: Examine the PC location displayed in the message; check the program listing to verify that operands or variables are specified correctly. SUBRNG1, subscript 1 range error, PC='xxxxxxxx', PS='xxxxxxxx' Facility: SYSTEM, System Services Explanation: The first subscript of an array reference was outside the declared bounds. User Action: Examine the PC location displayed in the message; check the program listing to verify that operands or variables are specified correctly. SUBRNG2, subscript 2 range error, PC='xxxxxxxx', PS='xxxxxxxx' Facility: SYSTEM, System Services Explanation: The second subscript of an array reference was outside the declared bounds. User Action: Examine the PC location displayed in the message; check the program listing to verify that operands or variables are specified correctly. A-55 New OpenVMS System Messages SUBRNG3, subscript 3 range error, PC='xxxxxxxx', PS='xxxxxxxx' Facility: SYSTEM, System Services Explanation: The third subscript of an array reference was outside the declared bounds. User Action: Examine the PC location displayed in the message; check the program listing to verify that operands or variables are specified correctly. SUBRNG4, subscript 4 range error, PC='xxxxxxxx', PS='xxxxxxxx' Facility: SYSTEM, System Services Explanation: The fourth subscript of an array reference was outside the declared bounds. User Action: Examine the PC location displayed in the message; check the program listing to verify that operands or variables are specified correctly. SUBRNG5, subscript 5 range error, PC='xxxxxxxx', PS='xxxxxxxx' Facility: SYSTEM, System Services Explanation: The fifth subscript of an array reference was outside the declared bounds. User Action: Examine the PC location displayed in the message; check the program listing to verify that operands or variables are specified correctly. SUBRNG6, subscript 6 range error, PC='xxxxxxxx', PS='xxxxxxxx' Facility: SYSTEM, System Services Explanation: The sixth subscript of an array reference was outside the declared bounds. User Action: Examine the PC location displayed in the message; check the program listing to verify that operands or variables are specified correctly. SUBRNG7, subscript 7 range error, PC='xxxxxxxx', PS='xxxxxxxx' Facility: SYSTEM, System Services Explanation: The seventh subscript of an array reference was outside the declared bounds. User Action: Examine the PC location displayed in the message; check the program listing to verify that operands or variables are specified correctly. A-56 New OpenVMS System Messages SUBSTRERR, substring error, PC='xxxxxxxx', PS='xxxxxxxx' Facility: SYSTEM, System Services Explanation: An error occurred in a substring operation. Either the starting position or ending position was outside the bounds of the string. User Action: Examine the PC location displayed in the message; check the program listing to verify that operands or variables are specified correctly. SWITIGNALPHA, 'qualifier' switch ignored; not allowed for Alpha images Facility: LINK, Linker Utility Explanation: A qualifier was specified that is not supported for OpenVMS Alpha images. The linker ignores the qualifier. User Action: Modify the qualifier or option and relink. SWITIGNVAX, 'qualifier' switch ignored; not allowed for VAX images, Facility: LINK, Linker Utility Explanation: While building an OpenVMS VAX image, the linker ignored the specified qualifier or option because it is not allowed for such images. User Action: None. SYMABNORMAL, procedure 'name' called from module 'module-name' in file 'filename' defined as data in module 'module-name' Facility: LINK, Linker Utility Explanation: The specified symbol was referenced as a procedure in the calling module, but is defined as data in the called module. User Action: Modify the called module to define the symbol as a procedure, or correct the reference to the procedure in the calling module, recompile, and relink. A-57 New OpenVMS System Messages SYMVABNORMAL, Symbol 'string' defined in module 'module-name' as DATA was declared in options as PROCEDURE Facility: LINK, Linker Utility Explanation: The specified symbol was defined to be data in the specified module, but was declared as a procedure in a SYMBOL_VECTOR option. User Action: Correct the SYMBOL_VECTOR= option and relink. SYMVALRDEF, symbol 'symbol-name' already defined in SYMBOL_ VECTOR Facility: LINK, Linker Utility Explanation: The specified symbol name was defined more than once in a SYMBOL_VECTOR= option. User Action: Remove the duplicate definitions from the option and relink. SYMVECMIS, shareable image's symbol vector table mismatch Facility: IMGACT, Image Activator Explanation: There is an inconsistency between a shareable image that was activated at runtime and information used to create an image that calls it. If the calling image is native, the inconsistency is with the shareable image that the calling image was linked against. If the calling image is translated, the inconsistency is with the shareable image's .IIF file used during the translation of the calling image. An accompanying message identifies the calling image and the shareable image. User Action: Link the calling image against the correct version of the shareable image or, for a translated image, use the correct .IIF file if the image is built using the VEST utility. SYSERR, error returned by system service Facility: MSGHLP, Help Message Utility Explanation: An error occurred while trying to call a system service or RTL routine. User Action: Take action based on the accompanying message. A-58 New OpenVMS System Messages TBL2SMALL, cannot completely format data structure; only 'integer' symbols are displayed Facility: SDA, System Dump Analyzer Explanation: The FORMAT command did not allocate enough space for the data structure. User Action: Enter another FORMAT command that allocates sufficient space for the data structure. TOOFEWCAS, too few CASE definitions found Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: Not enough destination offsets were provided for a CASE statement. User Action: Add the required destination offsets. TRANSCALLER, routine at 'address' cannot be called by translated code Facility: SYSTEM, System Services Explanation: The autojacketing routine EXE$TRANSLATED_ TO_NATIVE aborted the user program. The native routine at the specified address cannot be called by a translated routine because the native routine does not have a procedure signature block associated with it. User Action: Compile the native routine using the /TIE qualifier. The debugger can identify the native routine by the address cited in the message. TRANSINSTR, Emulation of normally translated instruction 'instruction'. Facility: TIE, Translated Image Environment Explanation: The TIE has emulated an instruction that VEST should have translated. User Action: Submit a Software Performance Report (SPR) for VEST that describes this error message and the image that incurred it. A-59 New OpenVMS System Messages TRANSLATEBUG, Please submit an SPR. Facility: TIE, Translated Image Environment Explanation: This message is a TIE return value signifying that it has detected a VEST error. It always follows another TIE message that indicates the translation error (VECTORINSTR, for example). User Action: Submit a Software Performance Report (SPR) describing the error. UDEFCLI, attempt to reference undefined conditional linkage index 'decimal-number.' in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: A module referenced an undefined linkage pair. User Action: Submit a Software Performance Report (SPR) on the appropriate language processor. UNALGLOLAB, unaligned global label Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected an unaligned global (also known as external) label. Alignment of global references is required. User Action: Align this global reference. UNALIGNED, unaligned address 'address'; converting to aligned address Facility: SDA, System Dump Analyzer Explanation: An unaligned address was detected. User Action: None. OpenVMS Alpha SDA automatically converts the address to an aligned address. UNALIGNFIX, unaligned 'length'word fixup at location 'address' Facility: LINK, Linker Utility Explanation: The linker encountered either a longword address fixup that is not longword-aligned, or a quadword address fixup that is not quadword-aligned at the specified address. In either case, the reference was to a shareable image. User Action: None required. However, alignment faults degrade the performance of the image during execution A-60 New OpenVMS System Messages of references to the address. To avoid this, correct the source to avoid unaligned address references, recompile, and relink. UNALIGNRELO, Unaligned 'length'word relocation generated at location 'address' Facility: LINK, Linker Utility Explanation: The linker encountered either a longword .ADDRESS that is not longword-aligned or a quadword .ADDRESS that is not quadword-aligned at the specified address. As a result, the linker generated an unaligned relocation. User Action: None required. However, alignment faults degrade the performance of the image during execution of references to the address. To avoid this, correct the source to avoid unaligned address references, recompile, and relink. UNALIGN_SP_LOAD, unaligned load of SP, virtual address='xxxxxxxx', PC='xxxxxxxx', PS='xxxxxxxx' Facility: SYSTEM, System Services Explanation: The image performed a load of the stack pointer from an unaligned location. The virtual address parameter is the virtual address of the source from which to load the stack pointer. User Action: Check the program listing to verify that the location is properly aligned. UNALMEMSTO, unaligned memory address stored in routine 'routine-descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected the storage of an unaligned memory reference in the routine. Stored memory addresses are assumed to be aligned. Aligned memory references to unaligned addresses can impair performance. User Action: To improve performance, align the memory address. A-61 New OpenVMS System Messages UNALSTKREF, unaligned stack reference in routine 'routine- descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected a stack references that are not octaword-aligned. User Action: To improve performance, align the stack. UNDECCALL, undeclared call Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The call destination was not declared with .CALL_ENTRY. User Action: Add the .CALL_ENTRY declaration. UNDECJSB, undeclared local JSB target: 'routine-descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The target routine of a local JSB was not declared. User Action: Declare the entry point with either the .JSB_ ENTRY or the .JSB32_ENTRY directive. UNRCHCODE, unreachable code Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected code that cannot be reached. User Action: Check for missing entry declarations. UNSUPASSIGN, unsupported assignment Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected a form of static initialization of an external symbol that is not allowed on OpenVMS Alpha. User Action: If possible, change your code to one of the forms that is allowed. UNSUPTIR, unsupported command type 'command' encountered Facility: LINK, Linker Utility Explanation: The linker encountered a text information and relocation record of an unsupported type. User Action: File a Software Performance Report (SPR) against the appropriate language processor. A-62 New OpenVMS System Messages UPDERRS, errors encountered updating HELP/MESSAGE database Facility: MSGHLP, Help Message Utility Explanation: A problem occurred while trying to insert or delete information in a .MSGHLP$DATA file. An accompanying message gives more information about the error. User Action: Take action based on the accompanying message and try the update operation again. UPLEVRET, uplevel return in routine 'routine-descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The routine is returning to an address beyond its caller's caller. User Action: Rewrite the routine so that it returns a status value to its caller that indicates that the caller should return to its caller. Alternatively, the initial caller could pass the address of a continuation routine, to which the lowest-level routine can JSB. When the continuation routine RSBs back to the lowest-level routine, the lowest- level routine RSBs. UPLEVSTK, uplevel stack reference in routine 'routine- descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected a reference in the routine to data pushed onto the stack by its caller. User Action: Eliminate the reference. Instead, pass the required data as parameters or pass a pointer to the stack base from which the data was read. UPSCNOCONTRI, universal psect 'psect-name' was not contributed by any object module; deleted from Global Symbol Table Facility: LINK, Linker Utility Explanation: The program section name was specified in a SYMBOL_VECTOR= option but was not found in any of the object modules or libraries that the linker searched. The psect symbol will not be available to users of the shareable image, but space will be reserved in the symbol vector. User Action: Ensure that the specified program section is included in the search path, and relink. A-63 New OpenVMS System Messages UPSCNORELGBL, universal psect 'psect-name' must be REL and GBL; deleted from Global Symbol Table Facility: LINK, Linker Utility Explanation: The program section name was specified in a SYMBOL_VECTOR= option but did not have the REL and/or GBL attributes set. A program section must be relocatable and global to be specifed in a SYMBOL_VECTOR= option. The psect symbol will not be available to callers of the shareable image. User Action: Modify the source to properly set the program section attributes and recompile, or modify the appropriate program section attributes with a PSECT_ATTR= option and relink the image. USEUNDEFSYMV, undefined symbol 'symbol-name' referenced in symbol vector option Facility: LINK, Linker Utility Explanation: The symbol was specified as an alias in a SYMBOL_VECTOR= option but was not found in any of the inputs to the linker. The symbol will not be available to users of the shareable image. User Action: Ensure that the specified symbol is included in the linker input, and relink. VARSIZSTK, variable-sized stack update prevents accurate stack tracing in routine 'routine-descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: A non-compile-time constant has been applied to the stack. This causes the generation of additional code that will lower the performance of the routine. User Action: Change the stack update to a compile-time constant, if possible, to improve performance. VECTORINSTR, Emulation of vector instruction 'instruction' requested. Facility: TIE, Translated Image Environment Explanation: The translated program attempted to execute a VAX vector instruction by means of the TIE emulation A-64 New OpenVMS System Messages facility. If the system were to respond correctly, it would issue an OPCDEC exception when the offending code executes. User Action: Rewrite the code in the original image to eliminate the unsupported vector instruction and submit a Software Performance Report (SPR) for a VEST error. WORDALSTK, word aligned stack in routine 'routine-descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: A word-aligned stack in the routine conflicts with the octaword alignment of the stack by the compiler. This conflict can cause unaligned stack references or cause the stack pointer to become unaligned. User Action: Change the alignment in the routine from word- aligned to octaword-aligned. WRITOARG, write to argument list in routine 'routine- descriptor' Facility: AMAC, MACRO-32 Compiler for OpenVMS Alpha Explanation: The compiler detected a write to the argument list, invoked with CALLG. On VAX, a routine invoked with CALLG can return values to its caller by writing into the argument list, but this does not work on Alpha. User Action: You can ignore the informational if the routine is never invoked with CALLG or if it is invoked with CALLG, but the caller does not expect to receive data back in the argument block. Otherwise, you must change both the routine and its callers to pass the return value by reference or by another supported method. The flagging option ARGLIST can be used to disable this flagging. WRTINDZRO, store into location 'address' in psect 'psect-name' from module 'module-name' file 'filename' is into a DZRO image section Facility: LINK, Linker Utility Explanation: An attempt was made to write into a demand- zero image section. Demand-zero image sections cannot be initialized by an object module. No image will be generated. User Action: Collect all relevant information about the program section and the language processor that created A-65 New OpenVMS System Messages the object module and submit a Software Performance Report (SPR). A-66 B _________________________________________________________________ DECTPU and EVE Release Notes This appendix provides information about DECTPU and EVE, including new features, enhancements, restrictions, and problems that have been fixed. B.1 DECTPU New Features This section gives a brief description of the new features that have been added to the DECTPU product. Although the product is now referred to as DECTPU, it is not a new product; only the name of the product has changed. ________________________ Note ________________________ You must rebuild your private section file to enable any new features that have been added to DECTPU. If you do not rebuild the section file, the new features might not work correctly. ______________________________________________________ B.1.1 EDIT Command and Multiple Input Files DECTPU is invoked through the EDIT command. With this release, the default EDIT command becomes EDIT/TPU. You no longer need to include the /TPU qualifier on your command. You can now specify multiple input files on the command line that invokes DECTPU. The files must be separated by commas or with optional white space. If wildcard characters are present in the file names, EVE displays the matching files for only the first wildcarded file name that has more than one match. For the other ambiguous file names, EVE displays a warning message. Two new GET_INFO built-ins are available to get the input file names and are described in Section B.3.3. B-1 DECTPU and EVE Release Notes B.1 DECTPU New Features B.1.2 Choosing Alternate Character Sets DECTPU allows you to control which character set is used to display 8-bit characters, that is, characters with the 8th bit set. By default, DECTPU uses the DEC Multinational Character Set (DEC_MCS) which is composed of two parts: the ASCII Graphics character set for 7-bit characters and the DEC Supplemental Graphics character set for 8-bit characters. You can choose the character set for displaying 8-bit characters by specifying one of the following values for either the /CHARACTER_SET qualifier or for the TPU$CHARACTER_SET logical name: o DEC_MCS. This is the default setting that uses the DEC Supplemental Graphics character set containing supplemental and multinational characters, such as letters with accents and umlauts. o ISO_LATIN1. This character set contains supplemental and multinational characters containing LATIN1 characters, such as the nonbreaking space, multiplication and division signs, and the trademark sign. o GENERAL. DECTPU does not specify a character set for 8-bit characters. 8-bit characters are displayed in the same way as they were before you started DECTPU. The choice of character set affects how DECTPU performs the following operations on characters: o Converting to lowercase o Converting to uppercase o Inverting case o Removing diacritical marks o Converting to uppercase and removing diacritical marks The choice of character set also affects how your text appears when printed. For the text displayed in DECTPU to appear in the same way when printed as it appeared on the screen, you must choose the same character set for both DECTPU and the printer. B-2 DECTPU and EVE Release Notes B.1 DECTPU New Features Table B-1 shows the values you can specify with the qualifier or logical name. For compatibility with previous versions of DECTPU, the default value is DEC_MCS if you do not specify the qualifier or do not define the logical name. Table_B-1_Character_Set_Values_____________________________ Value_________________Description__________________________ DEC_MCS Designates DEC supplemental ISO_LATIN1 Designates ISO Latin1 GENERAL Display of 8-bit characters remains unchanged from what they were before ______________________you_entered_DECTPU___________________ B.1.3 Motif User Interface Support Added for DECTPU DECTPU provides support for the Motif user interface on OpenVMS Alpha AXP systems with DECwindows Motif for OpenVMS AXP installed. DECTPU no longer supports the XUI interface. DECTPU Motif applications, however, can still run on a system running the XUI window manager. B.2 EVE New Features This section gives a brief description of the new features that have been added to the EVE product. ________________________ Note ________________________ You must rebuild your private section file to enable any new features that have been added to EVE. If you do not rebuild the section file, the new features might not work correctly. ______________________________________________________ B-3 DECTPU and EVE Release Notes B.2 EVE New Features B.2.1 Motif User Interface Support Added for EVE EVE provides a Motif user interface on OpenVMS Alpha AXP systems with DECwindows Motif for OpenVMS AXP installed. EVE no longer provides an XUI interface. You can, however, run EVE Motif applications on a system running the XUI window manager. The way EVE handles widget resource strings and callback reasons has been changed. In previous versions, EVE defined a set of constants to point to these strings and integers. These were used to control the operation of EVE's widgets. EVE has two new global array variables, EVE$X_RESOURCE_ ARRAY and EVE$X_CALLBACK_ARRAY, that are loaded at startup time with the correct values for the Motif environment. EVE$X_RESOURCE_ARRAY contains the strings that EVE uses to get and set values from widgets. EVE$X_CALLBACK_ARRAY contains the integer values that identify the reason for a widget callback. A set of indices is provided with which to access the arrays. Table B-2 and Table B-3 show the old EVE constants with the new resource or callback array indices. To convert from the XUI constants to the DECwindows Motif for OpenVMS AXP arrays, replace the old constant name with an array reference, as follows: V2.0 EVE$DWT$C_NINC V3.0 EVE$X_RESOURCE_ARRAY {EVE$K_NSCROLL_INC} V2.0 EVE$DWT$C_CRUNIT_INC_CALLBACK V3.0 EVE$X_CALLBACK_ARRAY {EVE$K_CR_INCREMENT} ... Table_B-2_EVE_Widget_Resource_Name_Conversions_____________ Index into EVE$X_RESOURCE_ Obsolete_XUI_Constant___________ARRAY______________________ eve$dwt$c_ninc eve$k_nscroll_inc eve$dwt$c_npage_inc eve$k_nscroll_page_inc eve$dwt$c_nmax_value eve$k_nmax_value (continued on next page) B-4 DECTPU and EVE Release Notes B.2 EVE New Features Table_B-2_(Cont.)_EVE_Widget_Resource_Name_Conversions_____ Index into EVE$X_RESOURCE_ Obsolete_XUI_Constant___________ARRAY______________________ eve$dwt$c_nmin_value eve$k_nmin_value eve$dwt$c_nvalue eve$k_nvalue eve$dwt$c_nlabel eve$k_nlabel eve$dwt$c_nshown eve$k_nslider_size eve$dwt$c_ndirmask eve$k_ndirmask eve$dwt$c_nhorizontal_scroll_ eve$k_nhorizontal_scroll_ bar bar eve$dwt$c_nvertical_scroll_bar eve$k_nvertical_scroll_bar eve$dwt$c_nselected_items eve$k_nselected_items eve$dwt$c_nx eve$k_nx eve$dwt$c_ny eve$k_ny eve$dwt$c_width eve$k_nwidth eve$dwt$c_height eve$k_nheight eve$kt_selecteditemscount eve$k_nselected_count eve$kt_itemscountstring eve$k_nitems_count eve$kt_ eve$k_nselected_items_count selecteditemscountstring "pageDecCallback" eve$k_npagedec_callbk "pageIncCallback" eve$k_npageinc_callbk "unitDecCallback" eve$k_nunitdec_callbk "unitIncCallback" eve$k_nunitinc_callbk "valueChangedCallback" eve$k_nvaluechng_callbk "toTopCallback" eve$k_ntotop_callbk "toBottomCallback" eve$k_ntobottom_callbk "minWidth" eve$k_nminwidth "minHeight" eve$k_nminheight "noResize"______________________eve$k_nnoresize____________ B-5 DECTPU and EVE Release Notes B.2 EVE New Features Table_B-3_EVE_Widget_Callback_Reason_Conversions___________ Index into EVE$X_CALLBACK_ Obsolete_XUI_Constant___________ARRAY______________________ eve$dwt$c_crunit_inc_callback eve$k_cr_increment eve$dwt$c_crunit_dec_callback eve$k_cr_decrement eve$dwt$c_crpage_inc_callback eve$k_cr_page_increment eve$dwt$c_crpage_dec_callback eve$k_cr_page_decrement eve$dwt$c_crto_top_callback eve$k_cr_to_top eve$dwt$c_crto_bottom_callback eve$k_cr_to_bottom eve$dwt$c_crcancel_callback eve$k_cr_cancel eve$dwt$c_cractivate_callback eve$k_cr_activate eve$dwt$c_crvalue_change_ eve$k_cr_value_changed callback eve$dwt$c_crhelp_callback eve$k_cr_help eve$dwt$c_cryes_callback eve$k_cr_yes eve$dwt$c_crno_match_callback___eve$k_cr_no________________ Note that it might take more than a simple text replacement to convert your code. The old names are EVE constants, while the new names are EVE run-time variables. If you have used the EVE constants where compile-time constants are required (such as the selectors in a CASE statement), you must recode. This is an example of the old code: case dwt_reason [EVE$DWT$C_NINC] : scroll (1); [otherwise] : message ("not a scroll"): endcase; This is an example of the new code: if dwt_reason = EVE$X_RESOURCE_ARRAY {EVE$K_NSCROLL_INC} then scroll (1); else message ("not a scroll"); endif; B-6 DECTPU and EVE Release Notes B.2 EVE New Features The index constants are defined in the file EVE$CONSTANTS.TPU. The arrays are loaded in the routine EVE$DECWINDOWS_MODULE_PRE_INIT which is in the module EVE$DECWINDOWS.TPU. For additional information, refer to the EVE*.TPU example source files in the SYS$EXAMPLES directory on OpenVMS Alpha AXP. B.2.2 Selecting the Keypad in EVE You can define the logical name EVE$KEYPAD to select the keypad in EVE. Valid keypad names are EDT, EVE, NUMERIC, VT100, and WPS. If you have extended EVE with your own keypad, you can select your keypad by defining the EVE$KEYPAD logical to be the name of your keypad. For example, assume you have created a keypad named SIMPLE, and have a procedure named EVE_SET_KEYPAD_SIMPLE that sets the keypad. The following logical definition causes EVE to invoke your keypad during startup: $ DEFINE EVE$KEYPAD SIMPLE If the logical name is not set or is set to EVE, you get the same keypad as before-the VT100 keypad on VT100 terminals or the numeric keypad on VT200 and later terminals. The logical name overrides any keypad setting saved in a section file. You can override their effect by setting the keypad in your initialization file or in your command file. B.3 New DECTPU Built-ins The following sections describe new built-ins that have been implemented for DECTPU. B.3.1 DECwindows Motif for OpenVMS AXP Environment Built-in A new built-in allows applications to determine if they are running in the Motif environment. This built-in returns a one (1) if you are running the DECTPU Motif interface; otherwise, it returns a zero (0). {0 | 1} := GET_INFO (SCREEN, "motif") B-7 DECTPU and EVE Release Notes B.3 New DECTPU Built-ins In addition, the meaning of the GET_INFO (SCREEN, "decwindows") and GET_INFO (SCREEN, "xui") built-ins have changed. o The following built-in returns a zero (0), since DECTPU no longer supports the XUI interface: {0 | 1} := GET_INFO (SCREEN, "xui") o The following built-in returns a one (1) if you are using the DECwindows Motif for OpenVMS AXP interface, and returns a zero if you are using the character cell interface: {0 | 1} := get_info (screen, "decwindows") request) B.3.2 First Input Action Built-in The following new built-in specifies the program or learn sequence that DECTPU executes when it gets the first key or button event: [{0 | 1}] := set (FIRST_INPUT_ACTION, {NONE | program_source}) EVE uses this SET built-in to designate an action routine that removes the copyright notice from the title bar when you first press a key or mouse button. This built-in is valid only until DECTPU gets the first event; after that, it signals the following: TPU$_BUILTININV, "Built-in is invalid at this time" The keyword NONE disables the current action routine. The following get_info returns the program or learn sequence implementing the application's first input action routine. If no such routine is set, it returns zero (0). {program | learn | 0} := get_info (SCREEN, "first_input_routine") The following get_info returns one (1) if DECTPU has received its first key or button event; otherwise, it returns zero (0). {1 | 0} := get_info (SCREEN, "first_input") B-8 DECTPU and EVE Release Notes B.3 New DECTPU Built-ins B.3.3 Input File Name Built-in Two new built-ins allow applications to determine all of the input files specified on the input command line. o The following built-in returns the first file name entered on the command line that invoked DECTPU, or zero (0) if none were specified: {string|0} := get_info (command_line, "first_file_name") Note how this built-in differs from GET_INFO (COMMAND_ LINE, "file_name") in the case where no file name is specified. If no file is specified, the built-in returns zero (0). The GET_INFO (COMMAND_LINE, "file_name") built-in returns the null string. o The following built-in returns the next file name entered on the command line that invoked DECTPU. It returns zero (0) if none were specified, or if there are no more file names to return. {string|0} := get_info (command_line, "next_file_name") B.3.4 Built-ins to Lower and Raise a Widget The LOWER_WIDGET built-in places the widget at the bottom of a viewing stack. This prevents the window associated with the widget from obscuring any sibling windows. The specified widget must be a subclass of WindowObjClass. The format of LOWER_WIDGET is as follows, where widget_ variable is the widget to lower: LOWER_WIDGET (widget_variable) The RAISE_WIDGET built-in places the widget at the top of a viewing stack. This ensures that the window associated with the widget is not obscured by any sibling windows. The specified widget must be a subclass of WindowObjClass. The widget window is mapped if it is not already mapped. The format of RAISE_WIDGET is as follows, where widget_ variable is the widget to raise: RAISE_WIDGET (widget_variable) B-9 DECTPU and EVE Release Notes B.3 New DECTPU Built-ins B.3.5 Motif Widget Context Help Built-in The following built-in enters the Motif context-sensitive help mode: SET (WIDGET_CONTEXT_HELP, widget_variable, {on|1|off|0}) The mouse pointer changes to a question mark, and DECTPU waits for you to select a widget by clicking on MB1. DECTPU then executes the help callback of the selected widget (or of its parent if the selected widget has no help callback). The widget_variable is the widget within which the modal help interaction will occur, usually the top level widget returned from the GET_INFO (SCREEN, "widget") built-in. The last parameter confines the question mark pointer to the specified widget if ON or one (1), or does not confine the pointer if OFF or zero (0). ________________________ Note ________________________ This built-in is disabled due to a problem in the Motif toolkit. ______________________________________________________ B.3.6 Popup Parent Widget Built-in The following built-in returns the parent widget for application popup widgets: widget := GET_INFO (SCREEN, "pop_up_parent_widget") The parent widget must be specified when creating the popup widgets using the CREATE_WIDGET built-in. B.3.7 Screen Pixel Size Built-in Two built-ins allow applications to determine the length and width of the screen in pixels. Both built-ins signal the error TPU$_REQUIRESDECW on character cell terminals. o This built-in returns the length (height) of the current display device in pixels: integer := get_info (screen, "pixel_length") o This built-in returns the width of the current display device in pixels: integer := get_info (screen, "pixel_width") B-10 DECTPU and EVE Release Notes B.3 New DECTPU Built-ins B.3.8 Top Level Widget Built-in A new built-in has been added to return DECTPU's top level widget. widget := get_info (SCREEN, "widget") This get_info returns DECTPU's top level widget, the application shell widget created by calling XtAppCreateShell. In character cell environments, this get_info returns TPU$_REQUIRESDECW. B.3.9 UID Built-in The SET (DRM_HIERARCHY) built-in was not named with transportable code in mind. The Motif UID routines are named XRM instead of DRM routines. To allow for more generic code, DECTPU has implemented the SET (UID) built-in as a synonym for the SET (DRM_HIERARCHY) built-in. SET (UID) and SET (DRM_HIERARCHY) are the same in all respects, but SET (UID) is the preferred form for new code. B.3.10 Widget Resource Types Built-in The following built-in adds new widget resource types to the list of supported resource types: [{0 | 1}] := SET (WIDGET_RESOURCE_TYPES, widget_data_type, widget_resource_types) The second parameter is a string that specifies the data type of the widget resource types, such as "boolean" or "short", which is supplied by the third parameter. The third parameter is either an array of strings, or a comma- separated list of strings. Any valid DECTPU array index can be used. The array elements contain the names of either widget resources (for example, "dialogStyle"), or of widget resource types (for example, "Int"). The comma-separated list gives the names of the widget resources or resource types. The following get_info returns an array indexed by strings that are support widget resource data types ("boolean", "callback", and so on). array := GET_INFO (WIDGET, "widget_resource_types") B-11 DECTPU and EVE Release Notes B.3 New DECTPU Built-ins Each array element is another array, integer-indexed from zero (0), containing the names of widget resources or resource types that match the specified data type. For example, suppose you have array element whose index is "int". After using this GET_INFO built-in, the element "int" contains another array, indexed with integers. The two elements of this second array, by default, are the two strings "Int" and "Cardinal". B.3.11 Built-ins for the X Resource Database The following two built-ins allow DECTPU applications to reload the display's X resource database and merge in a user-specified resource file: SET (DEFAULT_FILE, string) GET_INFO (SCREEN, "default_file") Their use affects subsequent GET_DEFAULT calls. The SET (DEFAULT_FILE) built-in merges the exact file specified, and does not apply any defaults to the user's file specification. o The following DECTPU built-in loads the display's database using XtDatabase, and then merges in the user-specified file by calling the toolkit routine XrmMergeDatabases: SET (DEFAULT_FILE, "") The current database, merged during editor initialization or by a previous SET (DEFAULT_FILE), is lost. o The following DECTPU built-in returns the name of the user-specified file that has been merged, either during editor initialization or by the SET (DEFAULT_FILE) built-in: string := GET_INFO (SCREEN, "default_file") B.4 Modified DECTPU Built-ins The following sections describe changes that have been made to DECTPU built-ins. B-12 DECTPU and EVE Release Notes B.4 Modified DECTPU Built-ins B.4.1 COMMAND_LINE The GET_INFO (COMMAND_LINE, "character_set") built-in returns the character set in use for the editing session. The return values are the keywords DEC_MCS (the default), GENERAL, or ISO_LATIN1. B.4.2 DECwindows Motif for OpenVMS AXP Environment This built-in returns a one (1) if you are using the DECwindows Motif for OpenVMS AXP interface, and returns an integer if you are using the character cell interface. The syntax is as follows: {0 | 1} := GET_INFO (SCREEN, "decwindows") B.4.3 DECwindows Motif for OpenVMS AXP Hierarchy The SET (DRM_HIERARCHY) built-in no longer applies any default file specification to the UID file specification in the first parameter. New code should use the SET (UID) built-in. See Section B.3.9 for more information about this built-in. B.4.4 Defining a WIDGET Class The DEFINE_WIDGET_CLASS built-in allows you to specify the second parameter (the name of the widget create routine) using either the VMS-binding name or the C-binding name. VMS-binding names can contain the dollar sign character and are not case-sensitive. For example, you can specify DWT$SCROLL_BAR_CREATE. C-binding creation routine names do not contain a dollar sign and are case-sensitive, for example, DwtScrollBarCreate. B.4.5 GET_INFO (SYSTEM) Built-in Procedure The GET_INFO (SYSTEM) built-in features a new request string "operating_system" that returns the TPU application's host operating system. The following example shows how to specify the new request string: keyword := GET_INFO (SYSTEM, "operating_system") B-13 DECTPU and EVE Release Notes B.4 Modified DECTPU Built-ins This GET_INFO returns a DECTPU keyword that denotes the operating system. Valid keywords and their respective host operating systems are shown in Table B-4. Table_B-4_GET_INFO_Keywords________________________________ Keyword_______________Host_Operating_System________________ VMS OpenVMS VAX OPEN_VMS_ALPHA OpenVMS Alpha AXP ULTRIX________________RISC/ULTRIX__________________________ It is not possible to determine the type of CPU being used. B.4.6 Global Select Applications can voluntarily relinquish global selections. DECTPU allows applications to do this through an optional fourth parameter on the SET (GLOBAL_SELECT) built-in. The fourth parameter is a keyword that tells DECTPU which action to take regarding the specified selection. Use GLOBAL_SELECT_GRAB as the fourth parameter to grab the selection. Use GLOBAL_SELECT_UNGRAB to relinquish it. If neither is specified, GLOBAL_SELECT_GRAB is the default. SET (GLOBAL_SELECT, SCREEN, PRIMARY, GLOBAL_SELECT_GRAB) . . . SET (GLOBAL_SELECT, SCREEN, PRIMARY, GLOBAL_SELECT_UNGRAB) B.4.7 Icon Handling The third parameter to the SET (ICON_PIXMAP, integer, string) built-in specifies the case-sensitive name of the icon in the UIL file to be set for the DECTPU application. Motif applications must have three icons in their UIL file as supported by the Motif Window Manager: a small icon (32 by 32 pixels), a medium icon (50 by 50 pixels), and a large icon (75 by 75 pixels). The icon name passed to this built- in must match only the root name of the three icon names in the UIL file. The UIL names start with the root name, and end with a dimension "_nXn". For example, EVE's root name is "EVE_ICON". The three icon names in EVE's Motif UIL B-14 DECTPU and EVE Release Notes B.4 Modified DECTPU Built-ins file are therefore "EVE_ICON_32X32", "EVE_ICON_50X50", and "EVE_ICON_75X75". When you execute the SET(ICON_PIXMAP) built-in, or change the window manager icon size and restart the Motif Window Manager, Motif DECTPU automatically selects the application's largest icon currently allowed by the Motif Window Manager. This lets the icon pixmap correctly fill the image area decoration of the icon. This means that Motif applications cannot specify which icon to display; DECTPU makes that decision. ________________________ Note ________________________ The SET (ICONIFY_PIXMAP) built-in is no longer supported, since it applies only to the XUI environment. There is no icon in the iconify button in a DECwindows Motif for OpenVMS AXP application window. ______________________________________________________ B.4.8 Menu Positioning The Motif Style Guide differs from the XUI Style Guide in that it does not require popup menus to put the previously activated menu item under the mouse pointer when you press MB3 again. The SET (MENU_POSITION) built-in on Motif is no longer used for this popup positioning. However, it is still required in order to position the popup menu below and to the right of the pointer. If you do not use it, the popup appears in the upper left corner of your screen. B.4.9 Sending Strings to Processes The SEND built-in has an upper limit of 1024 characters that can be sent with a single SEND call. The previous limit was 140 characters, which forced commands to be broken up and sent to the process using several SEND calls. B.4.10 SCREEN Information The GET_INFO (SCREEN) built-in accepts three new request strings: o "VT400" returns true if the terminal is set to a VT400. o "DEC_CRT3" returns true if the terminal is a DEC_CRT3 terminal. B-15 DECTPU and EVE Release Notes B.4 Modified DECTPU Built-ins o "DEC_CRT4" returns true if the terminal is a DEC_CRT4 terminal. B.4.11 Screen Update Behavior The SET (SCREEN_UPDATE) built-in takes a window variable as an optional third parameter. If updates are turned off for the specified window, the window is called a "no-update" window. The screen updater simply ignores no-update windows. Applications which modify part of the screen through some external means, may map a no-update window to that portion or portions of the screen to prevent DECTPU from overwriting it. EVE does not support the use of no-update windows. For more information, see help on SET (SCREEN_UPDATE). The following built-in returns the update status of a window. Zero implies that updates are off, while one (1) implies that the window is updated normally: {0 | 1} := get_info (window_variable, "screen_update") A new detached cursor reason has been added, as shown in the following example: TPU$K_NO_UPDATE := get_info (SCREEN, "detached_reason") The constant TPU$K_NO_UPDATE, an integer of value 32, specifies that the current window is a no-update window. This is considered to be a detached cursor situation since the cursor does not accurately reflect the editing point within the current buffer. TPU$K_NO_UPDATE can be set in conjunction with any other detached reason, with the exception of TPU$K_UNMAPPED. Most applications using no_update windows should trap this detached cursor reason, and position to a normal window. EVE Version 3.0 traps this condition in its detached cursor action routine, and positions to the topmost normal window. B-16 DECTPU and EVE Release Notes B.4 Modified DECTPU Built-ins B.4.12 WIDGET Identification The meaning of the fourth parameter to the following built- in changes with DECwindows Motif for OpenVMS AXP: GET_INFO (WIDGET, "widget_id"...) DECTPU performs a secondary check to allow for common usage of this built-in between the XUI environment and the DECwindows Motif for OpenVMS AXP environment. The XUI environment expects the first widget name in the fully qualified name to be the name of the root widget specified in the third parameter. DECwindows Motif for OpenVMS AXP expects the first name to be a child of the root widget. As an example, EVE's FIND dialog box contains a label. The FIND dialog box is the parent of the label. The XUI name for the label was FIND_DIALOG.FIND_LABEL, while the DECwindows Motif for OpenVMS AXP name is FIND_LABEL. In order to resolve this ambiguity, the GET_INFO (WIDGET, "WIDGET_ID) built-in searches for a widget with either name. For example, assume that your code contains the following statement: w := GET_INFO (WIDGET, "widget_id", eve$x_find_dialog, "FIND_DIALOG.FIND_LABEL") The built-in first searches for the exact name specified in the fourth parameter. If this fails, it strips off the characters up to and including the first period (FIND_ DIALOG.) and tries again. This allows EVE and other DECwindows Motif for OpenVMS AXP applications to work unmodified on the XUI environment or on DECwindows Motif for OpenVMS AXP. B.4.13 Writing Buffers WRITE_FILE takes an optional parameter to determine whether to pad the text written to a file. [string2 :=] WRITE_FILE ({buffer|range} [,string1] [, {ON|OFF|1|0}) B-17 DECTPU and EVE Release Notes B.4 Modified DECTPU Built-ins If the new optional fourth parameter is the keyword ON or integer one (1), then the output is padded with spaces to keep the first character of each record at the same column as the text in the buffer. This is the default behavior. If the parameter is the keyword OFF or the integer zero (0), then no padding spaces are inserted when writing to the file. This change is upward-compatible. B.5 Miscellaneous DECTPU Enhancements This section discusses miscellaneous DECTPU enhancements. B.5.1 Command File Input DECTPU no longer signals TPU$_FILEIN when reading the command file. This means that applications which are implemented as DECTPU command files no longer display a spurious DECTPU message unrelated to their functions. Note that it is not possible to turn this message back on. DECTPU will always read command files silently. B.5.2 FAO, MESSAGE and MESSAGE_TEXT Built-ins The FAO, MESSAGE and MESSAGE_TEXT built-ins accept up to 127 parameters. These built-ins can return strings of the maximum size supported by DECTPU, which is currently 65535 characters. B.5.3 ON and OFF States All SETs which contain a keyword ON or OFF parameter also accept the integer one (1) (equivalent to ON) and the integer zero (0) (equivalent to OFF). Most sets return the previous state as well. The primary reason for this change is to allow programmers to generate better code. It also regularizes the use of SETs, since many SETs returned undocumented state values in Version 2.6. The following examples demonstrate how the new changes can be used to generate smaller and faster code. The key to this is that DECTPU uses a non-optimizing interpreter, so the fewer built-ins that are called, the better the resulting code. B-18 DECTPU and EVE Release Notes B.5 Miscellaneous DECTPU Enhancements For example, assume that you call a routine that returns a true or false. As a result of that, you set DECTPU's timer on or off. After you finish doing some other operations, you reset the timer to its previous state. The following example accomplishes this code using GET_ INFOs to interrogate the current setting before changing it with a SET. Note the extra calls to GET_INFOs, and the code that translates numeric values into the keywords required by the SETs. old_setting := get_info (system, "timer"); old_string := get_info (system, "timed_message"); IF should_timer_be_on_because_next_operation_takes_a_while THEN set (timer, on, "Hang on - we're going to take a while.") ELSE set (timer, off); ENDIF; do_the_operation; IF old_setting THEN set (timer, on, old_string); ELSE set (timer, off, old_string); ENDIF; When you use the state information returned by the SET, the calls to the get_infos are eliminated. The state information can also be used without translation when restoring the original state, as shown below. This code segment is exactly equivalent to the previous example, yet it takes far fewer operations. old_string := get_info (system, "timed_message"); old_setting := set (timer, should_timer_be_on_because_next_operation_takes_a_while, "Hang on - we're going to take a while."); do_the_operation; ! ! Old_setting is a keyword, either ON or OFF. ! set (timer, old_setting, old_string); B-19 DECTPU and EVE Release Notes B.5 Miscellaneous DECTPU Enhancements Finally, the results from a get_info can be used directly in a SET as well: old_string := get_info (system, "timed_message"); old_setting := get_info (system, "timer"); a_routine_that_sets_the_timer_message; ! ! Old_setting is an integer, either 0 or 1. ! set (timer, old_setting, old_string); B.5.4 OpenVMS Alpha AXP DCL Qualifier Changes The /DISPLAY=DECWINDOWS and /INTERFACE=DECWINDOWS qualifiers invoke DECTPU with the DECwindows Motif for OpenVMS AXP interface. The XUI interface is no longer supported. DECTPU DECwindows Motif for OpenVMS AXP applications can, however, still run on a system running the XUI window manager. B.5.5 Work File If DECTPU cannot open its work file, it displays the following error message: TPU$_WORKFILEFAIL, "Error opening the work file" To resolve this problem, you should check the directory specification, or any item specified in an accompanying RMS message, to be sure that you are trying to open a valid work file. Alternatively, use the /NOWORK qualifier on the command line. In OpenVMS Alpha AXP, DECTPU displays the same error message but will continue to enter as if the user had specified the /NOWORK qualifier on the command line. DECTPU's work file is used only when very large files are being processed and when DECTPU requires more memory than the system can allocate. B.6 New EVE Commands This section discusses new EVE commands. B-20 DECTPU and EVE Release Notes B.6 New EVE Commands B.6.1 GET Command This is a synonym for the GET FILE command. It maintains the behavior of GET being the abbreviation for the GET FILE command, and not the new GET WILDCARDED FILES command. B.6.2 GET WILDCARDED FILES Command This command creates a buffer for each file specified- similar to GET FILE, except that multiple files are read in simultaneously. This allows you to quickly open a series of related files. The command leaves you in the last buffer that matches the wildcard file specification. For more information, see the online Help for GET WILDCARDED FILES. B.6.3 GLOBAL REPLACE Command A new variant of EVE's REPLACE command, GLOBAL REPLACE, has been implemented. The GLOBAL REPLACE command does not prompt you before it makes a change. It simply searches the current buffer for a specified string and replaces it with another string. Invoke the new command as follows: GLOBAL REPLACE old_string new_string Do not use this command unless you are sure you want all occurrences of old_string changed to new_string. B.6.4 SET FUNCTION KEYS MOTIF Command This enables some function keys as in other DECwindows Motif for OpenVMS AXP applications. This is the default when using the DECwindows Motif for OpenVMS AXP interface for EVE. See the EVE online help topic SET FUNCTION KEYS MOTIF for more information. B.6.5 SET SELECTION GRAB FOCUS Command This command makes EVE grab the primary selection when you give EVE input focus. EVE then conforms to the Motif Style Guide "focus-based" model for moving the primary selection among applications. B.6.6 SET SELECTION GRAB SELECTION Command This command makes EVE grab the DECwindows Motif for OpenVMS AXP primary selection when you select text. EVE then conforms to the Motif Style Guide "selection-based" model for moving the primary selection among applications. B-21 DECTPU and EVE Release Notes B.7 Miscellaneous EVE Enhancements B.7 Miscellaneous EVE Enhancements This section discusses miscellaneous EVE enhancements. B.7.1 Commands Available Within System Buffers You can execute the following commands in EVE systems buffers: o CENTER LINE o FILL o FILL PARAGRAPH o FILL RANGE o SET BUFFER o SET LEFT MARGIN o SET RIGHT MARGIN B.7.2 Edit Handlers Edit handlers work in system buffers. Previously, EVE allowed pre-action and post-action edit handlers to execute only in user buffers and not in system buffers. Edit handlers are procedures that execute either before EVE performs specific types of actions that navigate or modify text, or after an operation that puts the editing point on an invisible record, or off the screen to the left or right. B.7.3 Faster Command Parser The performance of the EVE command parser has been improved. This improvement eliminates the EVE system buffer name "$MATCHES$" that is held in variable EVE$MATCH_BUFFER. It also eliminates the restriction that commands could have a maximum of five tokens, for example, SET THIS WHEN THAT HAPPENS. There is no maximum token count. B-22 DECTPU and EVE Release Notes B.7 Miscellaneous EVE Enhancements B.7.4 FILL Permitted with DIGITAL Standard Runoff (DSR) and VAX Document Tags EVE lets you fill RUNOFF commands and VAX DOCUMENT tags at the start of lines. The default setting prevents you from filling the tags. To enable EVE to fill lines that start with RUNOFF or DOCUMENT tags (remove them from the list of paragraph boundaries), use the following new command: SET FILL TAGS To disable the feature you can use the following: SET FILL NOTAGS ________________________ Note ________________________ A usage note in the FILL-related help topics warns you that this new feature might be dangerous to use. The danger is that FILL, in a RUNOFF or DOCUMENT buffer containing no blank lines or page breaks, can fill the entire buffer, making it unreadable. ______________________________________________________ B.7.5 Menu Changes Table B-5 lists the names of the EVE menus that changed for DECwindows Motif for OpenVMS AXP, as well as the changed entries in the Help pulldown menu. Table_B-5_Name_Changes_or_Additions_to_EVE's_Pulldown_Menus DECwindows Motif for Pulldown OpenVMS Menu________XUI_Name__AXP_Name____Description______________ View Display View Changing user's view of data Option Customize Option Customizing the application (continued on next page) B-23 DECTPU and EVE Release Notes B.7 Miscellaneous EVE Enhancements Table B-5 (Cont.) Name Changes or Additions to EVE's __________________Pulldown_Menus___________________________ DECwindows Motif for Pulldown OpenVMS Menu________XUI_Name__AXP_Name____Description______________ Help - Help Mode Context-sensitive help Help - Using Help How to use help Help List of Index Index of help topics Topics Help Overview EVE Overview of EVE Overview Help Keys Keyboard Keypad diagram Help About Product Current version of EVE ______________________Information__________________________ B.7.6 Obsolete EVE Constants The following EVE constants are no longer supported. If you have used one of these constants, you might need to define your own variables or extend EVE's arrays. These constants are not required by EVE itself. Since the resource and callback arrays are defined at runtime, instead of compile time, unused values are no longer initialized. eve$dwt$c_ntakefocus eve$dwt$c_crscroll_start_callback eve$dwt$c_crdrag_callback eve$dwt$c_crscroll_end_callback eve$dwt$c_crarm_callback eve$dwt$c_crdisarm_callback eve$dwt$c_crno_callback eve$dwt$c_crto_position_callback eve$dwt$c_crmap_callback eve$dwt$c_crunmap_callback eve$dwt$c_crpull_down_callback eve$dwt$c_cfocus_callback eve$dwt$c_single_selection_callback eve$dwt$c_single_select_and_confirm_callback eve$dwt$c_extend_select_callback eve$dwt$c_extend_select_and_confirm_callback B-24 DECTPU and EVE Release Notes B.7 Miscellaneous EVE Enhancements eve$dwt$c_crcommand_entereed_callback eve$dwt$c_crcreate_callback eve$dwt$c_crhelp_requested_callback eve$dwt$c_crselection_callback eve$dwt$c_crclipboard_data_request_callback eve$dwt$c_crclipboard_data_delete_callback eve$dwt$c_crexpose_callback eve$dwt$c_crlost_focus_callback eve$dwt$c_crapply_callback B.7.7 SPELL Command Available for DECwindows Motif for OpenVMS AXP The SPELL command works in DECwindows Motif for OpenVMS AXP EVE interfaces. The SPELL command creates a temporary DECterm and runs DECspell in that new terminal window. DECspell is an optional layered product available from Digital. B.7.8 Title Bar Copyright DECwindows Motif for OpenVMS AXP EVE displays a copyright notice in the title bar at application startup. Using an action routine set by the new SET(FIRST_INPUT_ACTION) built-in, when EVE gets the first key or button event, EVE changes the title bar to display the new application title resource ("EVE"). If you make a private copy of the EVE resource file, and invoke DECTPU using the TPU$DEFAULTS logical defined on OpenVMS Alpha AXP, you will not see this behavior. To enable the behavior, make a private copy of the new EVE resource file in SYS$LIBRARY:EVE.DAT. That file contains the new copyright notice and application title resource. B.8 DECTPU and EVE Restrictions The following restrictions apply to DECTPU and EVE. These are general restrictions which Digital does not expect to address in the DECTPU Version 3.1 release. B-25 DECTPU and EVE Release Notes B.8 DECTPU and EVE Restrictions B.8.1 DECwindows Motif for OpenVMS AXP Applications that Execute READ_KEY and READ_CHAR Built-ins Restriction: DECTPU signals an error if a READ_KEY or READ_CHAR built-in is aborted by any of the following events: resize, widget callback, loss of primary selection, and client message. The following example shows an error handler returning from a procedure that has a READ_KEY built-in aborted when a widget callback occurs: procedure get_a_key (the_key) on_error [TPU$_READABORTED]: message ("Prompt terminated.", 0); return; endon_error; loop ... the_key := read_key; ... endloop; endprocedure; Workaround: If your DECwindows Motif for OpenVMS AXP application executes READ_KEY and READ_CHAR built-ins, you should use error handlers containing the TPU$_READABORTED selector. The code associated with that selector should return from the procedure by executing either an ABORT or RETURN statement. If the procedure executes another READ_KEY or READ_CHAR built-in instead of returning, DECTPU enters an infinite loop. B.8.2 SET (MAPPED_WHEN_MANAGED) Built-in Restriction: The SET (MAPPED_WHEN_MANAGED) built-in does not return the previous state of the modified widget. Workaround: There is no workaround to this restriction. B-26 DECTPU and EVE Release Notes B.8 DECTPU and EVE Restrictions B.8.3 Small Display Monitors and DECwindows Motif for OpenVMS AXP Applications Restriction: When running DECwindows Motif for OpenVMS AXP DECTPU on small display monitors, the main window might not be fully visible. Workaround: To correct this, follow these steps: 1. Add the following resources to your DECTPU X resource file: Tpu.Tpu$MainWindow.X: 0 Tpu.Tpu$MainWindow.Y: 0 Tpu.Tpu$Mainwindow.Rows: 21 Tpu*condensedFont: on Tpu*fontSetSelection: 1 2. Copy the resource file from SYS$LIBRARY:EVE.DAT and add the above lines. 3. Use logical name TPU$DEFAULTS to point at the new resource file. The following example invokes the EVE DECwindows Motif for OpenVMS AXP interface using the X resource file named EVE_SMALL_WINDOW.DAT in your login directory to edit the file LOGIN.COM. $ DEFINE TPU$DEFAULTS SYS$LOGIN:EVE_SMALL_WINDOW.DAT $ EDIT/TPU/INTER=DECWINDOWS LOGIN.COM B.9 DECTPU Problems That Have Been Fixed The following sections describe DECTPU problems that have been fixed. B.9.1 Aborting Compilation with Ctrl/C In previous versions, DECTPU would crash if you pressed the Ctrl/C key (either by accident or to abort the compilation) while compiling TPU code. This problem has been fixed. B-27 DECTPU and EVE Release Notes B.9 DECTPU Problems That Have Been Fixed B.9.2 !AF FAO Directive Dropped from DECTPU Messaging DECTPU no longer uses the !AF FAO directive in its message file. All the messages are available to those writing applications in DECTPU. B.9.3 Ctrl/C Key Definition DECTPU allows you to execute your Ctrl/C key definition. However, before you execute Ctrl/C on a character cell terminal, you must enter the following DCL command: $ SET TERMINAL/PASTHRU No special settings are required to execute your Ctrl/C key definition in the DECwindows Motif for OpenVMS AXP interface. Note that if you define the Ctrl/C key, the key does not abort any executing procedures, nor does it terminate the READ_LINE built-in in the DECwindows Motif for OpenVMS AXP interface. B.9.4 Ctrl/C and Startup DECTPU on OpenVMS Alpha AXP enables the Ctrl/C handler earlier in startup. This allows applications to trap Ctrl/C errors using TPU$_CONTROLC selectors in case-style error handlers in the following startup code segments: o /DEBUG debugger file o TPU$INIT_PROCEDURE procedure o /COMMAND command file o TPU$INIT_POSTPROCEDURE procedure DECTPU also enables the Ctrl/C handler when in /NODISPLAY mode. This allows applications to trap Ctrl/C errors even if they are implemented entirely in a /COMMAND file and never get to DECTPU's main key-reading loop. B.9.5 DEFINE_WIDGET_CLASS Built-in DECTPU initializes the widget class that you define using the DEFINE_WIDGET_CLASS built-in. This means that when you use the CREATE_WIDGET built-in to create the first widget of that class, you can specify all widget resources supported by that widget class. Previously, when DECTPU tried to validate all of the resources passed to CREATE_ B-28 DECTPU and EVE Release Notes B.9 DECTPU Problems That Have Been Fixed WIDGET, it would signal the following message and would not create the widget: TPU$_NONAMES, "There are no names matching the one requested" This happened because the X Intrinsics do not know about type conversions for some widget resources until you create the first widget of that class. B.9.6 HELP_TEXT Built-in The HELP_TEXT built-in correctly displays help text if you turn on prompting on OpenVMS Alpha AXP. The built-in also no longer causes the editor to crash when you use positioning or search built-ins after exiting help that had prompting mode turned on and had the help window mapped to the screen. B.9.7 Improved DECwindows Motif for OpenVMS AXP Error Codes In the past, DECTPU returned the message code TPU$_FAILURE_ STATUS without pinpointing any error. DECTPU displays a meaningful message when any of the following errors occur: o DECTPU cannot open a User Interface Definition (UID) file specified with the SET(UID) built-in (TPU$_ UIDOPENERR). o DECTPU cannot read an icon from a UID file specified with the SET(ICON_PIXMAP) built-in (TPU$_UIDICONERR). o DECTPU cannot read a bitmap file specified with the SET(ICON_PIXMAP) built-in (TPU$_BITMAPREADERR). o DECTPU cannot read a widget from a UID file specified with the CREATE_WIDGET built-in (TPU$_UIDWIDGETERR). o DECTPU cannot return the icon name specified with the GET_INFO(SCREEN,"icon_name") built-in because the user has not set one using the SET(ICON_NAME) built-in (TPU$_ ICONNAMERDERR). o DECTPU encounters an unknown compound string component when converting a compound string (from a widget) into a simple DECTPU string (TPU$_UNKCSCOMP). B-29 DECTPU and EVE Release Notes B.9 DECTPU Problems That Have Been Fixed B.9.8 Journaling Performance Improvement The READ_FILE built-in stores the name of the file in the buffer change journal, instead of journalling each line in the file as it is read in. ________________________ Note ________________________ The means the source file must be present if you try to recover from the journal. ______________________________________________________ As a result, READ_FILE is much faster when reading in large files. The RECOVER_BUFFER built-in has been updated to read in the file that was included. If the included file is not present, you will be prompted for a new file specification. B.9.9 KEY_NAME and CTRL_MODIFIED DECTPU returns the correct keyname for KEY_NAME("i",CTRL_ MODIFIED) and KEY_NAME("m",CTRL_MODIFIED). B.9.10 Logical Names and Journal File Conflict The SET (JOURNALING) built-in turns on buffer-change journaling for a buffer by first converting the buffer name to a journal file name. Previously, if that journal file name was a logical name, the built-in would open the journal file whose name was the logical name (but not supply default values for any fields not in the journal file name from the default file name TPU$JOURNAL:.TPU$JOURNAL). For example, if the logical name was TT, data written to the journal file was actually written to your terminal screen. This has been fixed so there is no conflict with journal file names and logical names. B-30 DECTPU and EVE Release Notes B.9 DECTPU Problems That Have Been Fixed B.9.11 DECwindows Motif for OpenVMS AXP and Cursor Blink DECTPU honors the cursorBlinkEnable resource in the DECwindows Motif for OpenVMS AXP interface. Previously, DECTPU would make the cursor blink whenever it received input focus, and turn off the blink when it lost input focus. Now, when DECTPU receives input focus, it makes the cursor blink only if it was blinking when DECTPU lost input focus. B.9.12 DECwindows Motif for OpenVMS AXP Interface and TPU$TPU Callable Routine Applications can use TPU$TPU and specify the /INTERFACE=MOTIF qualifier. There were two separate problems in previous versions of DECTPU. The first error was DECTPU's failure to remove its main widget from the screen after returning control to the calling application. The second error occurred if the application called TPU$TPU more than once. DECTPU would appear to start up correctly but would not accept input from the keyboard or mouse. Both of these problems have been fixed. B.9.13 DECwindows Motif for OpenVMS AXP Resize DECwindows Motif for OpenVMS AXP DECTPU has fixed the following resize problems: o If you activate the Maximize button, DECTPU resizes the window to fill the entire screen. Previously, when you activated the Maximize button the first time, the screen would not fill unless the screen dimensions were multiples of a DECTPU character height and width. This would leave a small gap between the window and the screen edge. Activating the Maximize button a second time would then fill the screen with the DECTPU window instead of restoring the previous size and location. Activating the button a third time would restore the size that left the small gap. o If you activate the Maximize button with DECTPU already maximized, DECTPU restores the window to its previous size and location. o If you make the window narrower (or wider) such that the menu bar wraps to more (or fewer) rows, DECTPU correctly adjusts the size of its window to display the text. B-31 DECTPU and EVE Release Notes B.9 DECTPU Problems That Have Been Fixed B.9.14 Multiple-line Text Strings in DECwindows Motif for OpenVMS AXP Applications DECTPU allows applications to send multiple-line text strings to widgets. The separate lines must be separated by a line-feed character (ASCII (10)) to be displayed correctly in the widgets. B.9.15 Partial Escape Sequence Errors DECTPU no longer crashes with a partial escape error when it receives a partial escape sequence. DECTPU signals an error of partial escape sequence read and continues. B.9.16 READ_KEY Built-in The READ_KEY built-in returns integer zero (0) if aborted in the DECwindows Motif for OpenVMS AXP interface by any of the following events: resize events, widget callback events, loss of primary selection events, and client messages. B.9.17 READ_KEY and READ_CHAR Prompts in DECwindows Motif for OpenVMS AXP Applications DECwindows Motif for OpenVMS AXP DECTPU does not abort READ_KEY and READ_CHAR prompts if focus-in or focus-out events occur. Prompts are still aborted for resize events, widget callback events, loss of primary selection events, and client messages. Application writers should note that focus-grab and focus- ungrab action routines can execute asynchronously while waiting for a READ_KEY or READ_CHAR to complete. Those action routines should not do anything that can affect the state of the active prompt. Actions to avoid include: o Calling the same routine that is currently prompting for input. Only if the prompt routine is reentrant can it be safely called again. It is reentrant if all variables it uses are local variables (on the stack). o Changing the mapping of the window and buffer currently prompting, or positioning to other windows or buffers. The prompting routine can cause errors once the prompt is terminated because the mapping is different than when the prompt was issued. B-32 DECTPU and EVE Release Notes B.9 DECTPU Problems That Have Been Fixed B.9.18 READ_LINE Built-in for DECwindows Motif for OpenVMS AXP Applications The READ_LINE built-in has been fixed as follows: o DECTPU no longer crashes when you exit from an editing session in which you use the READ_LINE built-in. o Clicking the Cancel button in the READ_LINE dialog box no longer unmanages and immediately redisplays the dialog box. o The READ_LINE built-in correctly aborts when you press Ctrl/C in the READ_LINE dialog box. o The READ_LINE built-in correctly terminates and returns the following keynames from the LAST_KEY built-in when you press the corresponding terminator key in the READ_ LINE dialog box: DO, RET_KEY, CTRL_Z_KEY. B.9.19 READ_LINE Prompt String Limited to 255 Characters DECTPU limits READ_LINE prompt strings to 255 characters. Previously, DECTPU would crash if you specified a prompt string that exceeded 2000 characters. B.9.20 Reverse Searches From the Beginning of a Line DECTPU no longer crashes searching in reverse for a pattern that starts at the beginning of a line. B.9.21 Screen Adjustments in DECwindows Motif for OpenVMS AXP Applications DECwindows Motif for OpenVMS AXP DECTPU used to bugcheck if you adjusted a window on your screen downward, and, before the screen updater could repaint the new, larger window, you clicked mouse button MB1 in the new lines at the bottom of that window. DECTPU correctly adjusts the window, and then moves the cursor to the mouse position. B-33 DECTPU and EVE Release Notes B.9 DECTPU Problems That Have Been Fixed B.9.22 SET (ICON_PIXMAP) Built-in The SET (ICON_PIXMAP) built-in returns a true (1) or false (0) status value indicating that it succeeded or failed to read an icon from your UID file or bitmap file. This status value is useful, for example, for applications running with a window manager that does not support multiple icon sizes. When the application tries to set the icon by specifying just the root name for the icon in the UID file, the window manager fails to find the icon. The application can test the return value from SET (ICON_PIXMAP) to see if it failed, and call the built-in again, this time specifying the complete name of the icon. B.9.23 SET (TIMER) Built-in Problem Corrected This release fixes the following two problems with the SET (TIMER) built-in procedure: o Timer messages were not displayed on the screen until you pressed Ctrl/T. This problem occurred only in the character cell interface. o A timing problem would sometimes cause the cursor to be incorrectly positioned after the timer had completed. As a result, messages were sometimes displayed outside of the message window and the cursor was left in the prompt window after the timer message had stopped. This problem occurred in the DECwindows Motif for OpenVMS AXP interface. B.9.24 SET (WIDGET_CALLBACK) Built-in on Leaf Widgets DECTPU allows using the SET(WIDGET_CALLBACK) built-in on leaf widgets, that is, widgets that have a parent. DECTPU previously crashed. B.9.25 Space Padding DECTPU correctly pads with spaces, instead of random text, when padding a buffer with more than 255 spaces. B-34 DECTPU and EVE Release Notes B.9 DECTPU Problems That Have Been Fixed B.9.26 TRANSLATE and EDIT Screen Display Fixed DECTPU was not updating the screen correctly in the following two cases where it modified a line containing a tab: o When you used the TRANSLATE built-in to replace a tab with another character o When you used the EDIT built-in to compress all tabs and spaces into a single space In both cases, the text was correct but the display was incorrect. This problem has been fixed so that the screen is updated correctly after both operations. B.9.27 UID Hierarchy Identifier DECTPU no longer crashes if you specify an invalid UID hierarchy identifier to the CREATE_WIDGET or SET (ICON_ PIXMAP) built-ins. B.10 EVE Problems That Have Been Fixed This section discusses the problems that have been fixed with this version of EVE. B.10.1 BOX CUT Command Improved The BOX CUT command correctly cuts selected text that extends past the end of file. B.10.2 Box Operations in Overstrike Mode EVE correctly performs box operations in overstrike mode buffers that have left margins greater than one. Previously, EVE would erase text by copying space characters instead of overstriking space characters when adjusting for the left margins. B.10.3 Command File and SAVE ATTRIBUTES Command EVE would incorrectly write the command file you specified with SAVE ATTRIBUTES or SAVE SYSTEM ATTRIBUTES to save attribute settings in a DECTPU command file. Specifically, EVE would not set the new output file specification for the $LOCAL$INI$ buffer, and trim the buffer if you had assigned an integer one (1) into variable EVE$X_TRIMMING. This has been fixed. B-35 DECTPU and EVE Release Notes B.10 EVE Problems That Have Been Fixed B.10.4 DCL or SHELL Subprocesses and the DECwindows Motif for OpenVMS AXP Environment If EVE could not create the DCL or SHELL subprocess in the DECwindows Motif for OpenVMS AXP environment, EVE reported the following error message: Parameter 1's data type, STRING, unsupported This has been fixed so that EVE reports the correct error message stating that the subprocess could not be created. B.10.5 DECspell Error Was Not Resetting State If the DECspell layered product was not installed and a user entered the SPELL command in EVE, EVE would not reset the output of success messages or release its scratch buffer, thus causing other EVE operations to fail. This problem has been fixed. B.10.6 DECwindows Motif for OpenVMS AXP EVE and Window Managers Other than Motif You can run DECwindows Motif for OpenVMS AXP EVE on a window manager other than the DECwindows Motif for OpenVMS AXP window manager. If your window manager does not support multiple sizes for application icons, it fails to find the icon using the root name "EVE_ICON" that EVE passes to the SET (ICON_PIXMAP) built-in. When this failure occurs, EVE tries to set the icon pixmap using the exact name for the small icon pixmap, "EVE_ICON_32X32". (The DECwindows Motif for OpenVMS AXP window manager uses the root name and the setting for the current icon size to find the icon in the UID file.) B.10.7 Error Handling in GET [WILD] FILE[S] If the GET FILE or GET WILDCARDED FILES commands failed to open the journal file or if you pressed Ctrl/C before the commands finished, EVE would not delete the new empty buffer. This problem is fixed. B.10.8 EVE$BUILD EVE$BUILD allows you to create a section file not built upon EVE without error messages occurring during the build about ambiguous EVE symbols or undefined EVE procedures. B-36 DECTPU and EVE Release Notes B.10 EVE Problems That Have Been Fixed B.10.9 EVE$TEARDOWN_WINDOWS and EVE$SETUP_WINDOWS Procedures Applications can call two procedures to tear down all EVE windows and then set them back up once the application has finished using its own windows. The procedures are EVE$TEARDOWN_WINDOWS and EVE$SETUP_WINDOWS. If you set up DECwindows Motif for OpenVMS AXP EVE windows using the context block returned from tearing down the windows, DECTPU would signal the following warning message and EVE would fail to set the window scroll margins: TPU$_BADMARGINS, "Margins specified incorrectly" This problem is fixed. B.10.10 EVE and Concealed Logical Names EVE is able to read a file specified by a device and directory equal to a concealed logical name that is a search list, and by a file name and type (and optional version number) that matches a file in more than one component of the search list. EVE reads in the first file found in the search list. Previously, EVE could not resolve the ambiguity, and would display the same file specification multiple times in the choice buffer. B.10.11 EVE Parser and User's Facility Name The EVE parser correctly parses your commands when passed an optional second parameter equal to your facility name. For example, assume the name of your facility is FOO, and a procedure FOO_BAR has been compiled. When passed the command name "b" in the first parameter, and the prefix "foo_" in the second parameter, the parser correctly returns the executable string "FOO_BAR" as the name of the procedure to execute. The parser procedure, EVE$$PARSE, is not part of the supported EVE public interface because it has two dollar signs. This information is being provided for those who want to take advantage of the current EVE parser behavior, knowing that it may change in future releases of EVE. B-37 DECTPU and EVE Release Notes B.10 EVE Problems That Have Been Fixed B.10.12 EVE Repeat Operations The following problems are corrected in the REPEAT command and GOLD-number repeat keys: o EVE did not let you use the REPEAT command in an initialization file unless you entered commands on the keyboard. This was because EVE had to prompt you for the command to repeat. EVE allows you to optionally specify the command to repeat when you enter the REPEAT command. Thus, to use the repeat command in an initialization file without keyboard intervention, you specify the command to repeat on the same line as the REPEAT command. The following example is a line in an initialization file that repeats the MOVE BY PAGE command 5 times. REPEAT 5 MOVE BY PAGE o If you entered a repeat count using an EDT or WPS keypad GOLD-number key, and then entered a command, the command ignored the repeat count and executed only once. EVE repeats the command the specified number of times. o If you repeated a learn sequence containing a command, the learn sequence would execute only once because the command would consume the repeat count. You can successfully repeat learn sequences containing commands entered from the command line. The learn sequence can also contain other repeat commands or keys, and learn sequences containing repeat commands or keys. o If you nested repeat keys, EVE ignored the first repeat count and used only the second repeat count. For example, if you pressed the EDT or WPS keypad GOLD-3 key followed by the GOLD-4 key, your next key was repeated only 4 times as EVE ignored the first repeat count of 3. EVE will multiply all nested repeat counts so that, for the example above, your next key is repeated 12 times. o If you entered a REPEAT M command followed by a REPEAT N command, EVE would prompt you M times for the command to repeat N times. EVE multiplies M times N, and prompts you only once for the command to repeat that number of times. B-38 DECTPU and EVE Release Notes B.10 EVE Problems That Have Been Fixed o If you set the WPS keypad and repeated a learn sequence that removed text more than 9 times, the learn sequence would fail. The problem was that the repeat count was being mistaken for the number of an alternate WPS paste buffer, and alternate paste buffers are limited from one to nine. This is fixed so that the WPS remove key (MINUS on the keypad or REMOVE) does not use the learn sequence repeat count as the number of an alternate WPS paste buffer. ________________________ Note ________________________ Applications that have customizations that reference EVE$X_REPEAT_COUNT must be re-coded. This EVE variable is now an array. ______________________________________________________ B.10.13 FIND SELECTED with Box Select Active If you made a box selection containing text on two lines, the FIND SELECTED command would find the next occurrence of the text on the first line of the selection instead of rejecting the command. This problem has been fixed. Also, if you had a found range active (you had just used the FIND command and the string was displayed in reverse video) and a box selection active in different buffers, FIND SELECTED would use the found range instead of the box selection. This problem has been fixed so that FIND SELECTED prioritizes the use of selections as do other EVE commands. Standard (linear) selections are used first, box selections are used next, and found ranges are used last. B.10.14 FILL RANGE The FILL RANGE command ensures that the range being filled starts at the left margin when the buffer has a nonzero paragraph indent. This is a restriction in the DECTPU FILL built-in. Previously, DECTPU would signal the following error: TPU$_INVRANGE, "Invalid range enclosure specified" B-39 DECTPU and EVE Release Notes B.10 EVE Problems That Have Been Fixed B.10.15 GET Command and Input File EVE puts into the command buffer the initial GET command even if the command failed, for example, when the input file could not be read. B.10.16 Help On GET_INFO Built-in Improved EVE correctly parses requests for help on the GET_INFO built-in. For example, you can get help on GET_INFO(SCREEN) by entering a command such as the following: "help tpu g i (scre" B.10.17 Help Messages Improved If you put an ambiguous help command in an /INITIALIZATION file, for example HELP ERAS, EVE reported the following error message: Operand combination INTEGER < UNSPECIFIED unsupported This has been fixed so that EVE rejects the ambiguous help command, as it does other ambiguous commands during initialization file processing. B.10.18 Improved SHOW BUFFERS Command It is easier to select or remove buffers from the SHOW BUFFERS and SHOW SYSTEM BUFFERS lists if the buffer has a long name. For these buffers, EVE puts a continuation hyphen (-) at the end of the buffer name, and puts the line count and attributes on a separate line. Previously, you could select or remove a buffer with a long name only if the cursor was on the line containing the buffer name. Now, you can also select or remove the buffer with the cursor on the line containing the line count and attributes. B.10.19 Improved Operations on White Space EVE operations on very long lines of white space are much faster. Previously, EVE contained loops that moved one character at a time, and tested to see if the current character was either a space or a tab. This option was very slow in long lines, especially now that DECTPU allows lines containing 32767 characters. The loops have been replaced with the much faster POSITION and SEARCH_ QUIETLY built-ins. Affected EVE commands include CENTER LINE, ERASE PREVIOUS WORD, ERASE WORD, FIND (after a SET B-40 DECTPU and EVE Release Notes B.10 EVE Problems That Have Been Fixed FIND WHITESPACE command), and MOVE BY WORD. Affected EVE operations include trimming trailing white space from a line or buffer, word wrapping beyond the right margin, and appending a line to a previous line. B.10.20 Improved Window Buffering If you unmap all windows, DECTPU calls EVE's detached cursor action routine with the TPU$K_UNMAPPED reason code. If there are no user buffers, EVE would cause the following error: Request of 'JOURNALING' of UNSPECIFIED is not understood EVE creates buffer MAIN without displaying that error message. B.10.21 Invoking EVE with Ambiguous Input File Specifications If you invoked EVE with an ambiguous input file specification causing the choices buffer to be displayed, EVE would set the $DEFAULTS$ buffer attributes from the command buffer and not from the first user buffer. As a result, new user buffers would get the command buffer attributes like reverse direction, no end of buffer text, and so on. This has been fixed. B.10.22 DECwindows Motif for OpenVMS AXP "Quick Cut" Operation Improved If you moved text within EVE by a "Quick Cut" mouse drag operation, EVE would correctly move the underlined secondary selection to the current editing position, but would add an extra linebreak after the pasted text. This has been fixed. B.10.23 Mouse Button MB1 and Range Removal Positioning the cursor by clicking MB1 did not remove the EVE found range highlighting. This occurred because pre_key and post_key procedures set on the EVE mouse key map list EVE$X_MOUSE_LIST were not executing. This has been fixed. B-41 DECTPU and EVE Release Notes B.10 EVE Problems That Have Been Fixed B.10.24 Mouse Drag During a secondary select mouse drag, EVE moved the cursor from the current editing position to the mouse pointer position where the underlined range was created. Since the current editing position is usually separate from the underlined range, you could lose track of where the selected text would be inserted at the end of the drag operation. EVE leaves the cursor at the current editing position during the drag operation to show where the secondary select range will be inserted. B.10.25 Open Dialog Box Filter Corrected EVE incorrectly set the file filter for its OPEN dialog box when invoked from Fileview while you were in a subdirectory. This problem has been fixed. B.10.26 Open Dialog Box and Wildcard Active If you enabled EVE to get all files matching your wildcarded file specification, the Open menu entry would prompt you for the file name from the prompt area instead of from a file selection box. This problem has been fixed. If you want EVE to read in all files that match a wildcard specification, use the following TPU command, either interactively, in a command file, or in an EVE initialization file: eve$x_get_wild_active := true; B.10.27 OPEN SELECTED Command and Context Resetting The OPEN SELECTED command in EVE was not resetting the context for the FILE_SEARCH built-in, causing it to fail every other time you tried opening a file. EVE resets the context and reads the selected file. B.10.28 OPEN SELECTED Command and Multiple File Selections The OPEN SELECTED command in EVE did not read any files if more than one file specification existed in the primary global selection of another DECwindows Motif for OpenVMS AXP application, or if multiple lines existed in the EVE select range, box select range, or found range. EVE reads all selected file names assuming each line is a separate file specification. By default, if the selection contains B-42 DECTPU and EVE Release Notes B.10 EVE Problems That Have Been Fixed more than one ambiguous file specification, EVE ignores all but the first, and displays choices for the first ambiguous file specification. B.10.29 OSF/Motif Style Guide Conformance The following changes were made to EVE in order to conform with the OSF/Motif Style Guide: o The Option pulldown menu is named Options. o The Buffer Attribute default button is the Cancel button, not the Ok button, since Cancel is the lesser damaging button. o The Restore pullright menu in the Edit pulldown menu is ordered by size of the text entity being restored: Character, Word, Line, Sentence, Selection. o The Help pulldown menu entries have been reordered and renamed to be more user-friendly. o The message dialog box that requires you to acknowledge an error has an Ok button, not an Acknowledge button. The dialog box no longer shrinks to a useless size that occludes objects in the box. o Pullright menus in the Extend Menu dialog box no longer have "->" in the selection box entries. o The Extend Menu dialog box has an Ok button instead of a Dismiss button. o The menu item previously labeled "@EVE File" is labeled "@" to agree with the command you enter from the command line. This menu item is in the Option pulldown menu. B.10.30 Primary Cut Mouse Operation If EVE did not have input focus, it would not remove text cut to another application by a "Primary Cut" mouse operation. EVE correctly removes the text into the $RESTORE$SELECTION$ buffer, from which it can be restored by the RESTORE SELECTION command. B-43 DECTPU and EVE Release Notes B.10 EVE Problems That Have Been Fixed B.10.31 Prompt Replies Trimmed EVE was not trimming prompt replies that would later be used for string comparisons. If the reply was a buffer name and it contained leading or trailing white space, EVE could not find the buffer in the SHOW BUFFERS list. If the reply was to the REPLACE command and contained leading white space, EVE would ignore the reply and prompt again. These problems have been fixed. B.10.32 /RECOVER and Ctrl/C If you specified /RECOVER on the DCL command line, and pressed Ctrl/C at any prompts during the recovery operation, EVE would return you to DCL. You could continue from the DCL prompt if using character cell DECTPU, but that would simply put you back at the recovery prompt. When using the DECwindows Motif for OpenVMS AXP EVE interface, you could not continue because pressing Ctrl/C would exit the image. Now, EVE will continue with startup after you press Ctrl/C at a recovery prompt. B.10.33 RECOVER BUFFER and Logical Names EVE would not recover your edits if you specified a buffer name whose name, when converted to a journal file name, was a logical name. This has been fixed so that there is no conflict with journal file names and logical names. B.10.34 Resize Action Fixed When you executed a procedure like the one below on a character cell terminal or DECterm emulator, EVE often resized your windows incorrectly, leaving the editor in a useless state with no command window or message window. procedure eve_set_height (arg) ! Change screen height, call resize handler eve$$x_resize_old_length := get_info (screen, 'visible_length'); eve$$x_resize_new_length := eve$$x_resize_old_length + int (arg); eve$$x_resize_old_width := 80; eve$$x_resize_new_width := 80; set (height, screen, get_info (screen, 'visible_length') + int (arg)); eve$$resize_handler; endprocedure; B-44 DECTPU and EVE Release Notes B.10 EVE Problems That Have Been Fixed The EVE resize action procedure has been fixed to correct this problem. B.10.35 SET SCROLLING command A major usability problem in EVE would not let you turn off scrolling to get better performance, especially on bigger screens. Four new EVE commands fix this problem: 1. SET SCROLL ON This command enables new text to scroll as it is brought into your window. It is the default EVE setting. This setting does not affect moving to a position off screen by more than (approximately) one window's length. In this case, the entire window is repainted with the new text in one operation. This command allows EVE to scroll the text using either SMOOTH or JUMP scrolling. 2. SET SCROLL OFF This command disables scrolling of new text as it is brought into your window. Instead, the screen is repainted with the new text in one operation. This is the fastest way to display new text. This command prevents EVE from scrolling text using either SMOOTH or JUMP scrolling. 3. SET SCROLL JUMP This command repaints new text brought into your window in one operation. Scrolling operations first scroll the text that will remain in your window to make room for the new text, leaving part of your window empty. New text is then displayed by a single repaint operation. This makes for slightly faster scrolling than with SET SCROLL SMOOTH because only part of your window is scrolled. This setting has no effect if you use SET SCROLL OFF. 4. SET SCROLL SMOOTH This command causes each new line of text to scroll into your window. This makes for slightly slower scrolling than with SET SCROLL JUMP, which scrolls only part of your window before repainting all new text in one operation. It is the default setting. This setting has no effect if you use SET SCROLL OFF. B-45 DECTPU and EVE Release Notes B.10 EVE Problems That Have Been Fixed B.10.36 SHOW BUFFERS and Buffer Deletion If you deleted the last buffer from the SHOW BUFFER display while in the bottom of two windows, EVE would display the status line for the MAIN buffer in both windows. EVE correctly displays the status line for the BUFFER LIST buffer in the bottom window. B.10.37 SHOW Command Improved The SHOW command correctly displays the line count for buffers containing more than one million lines. It used to limit the line count to six decimal digits, and displayed "******" for the line count of buffers exceeding the old limit. The limit is eight decimal digits. B.10.38 SYSTEM Buffers are Marked Permanent EVE makes all but two of its system buffers permanent buffers so you cannot delete them. The two exceptions are the DCL and the SPELL buffers. These buffers have an associated subprocess, and deleting the buffer is the easiest way to allow you to delete the subprocess and thus consume fewer system resources. B.10.39 Wildcard Input File Specification If you invoked EVE with a wildcard input file specification that has more than one matching file, EVE displayed the choices buffer and put the cursor in the command buffer where you could resolve the ambiguity. If you erased the ambiguous GET command, pressed RETURN to exit the command window and started editing, and some time later read in a file with a GET command, EVE incorrectly applied the following file-related OpenVMS Alpha AXP qualifiers to that new buffer: /MODIFY, /OUTPUT, /READ_ONLY, and /WRITE. EVE no longer applies those qualifiers to the buffer created from that first GET command. It also displays a message to that effect when you erase the initial ambiguous command. B-46 DECTPU and EVE Release Notes B.10 EVE Problems That Have Been Fixed B.10.40 EVE Word Operations The following problems that existed in EVE's word operations have been corrected: o If you put the cursor on white space between words, ERASE WORD first erased all but the left-most white space character, and then erased the next word. The erased white space was lost and could not be restored. This is fixed so that the white space is restored with the erased word when you use the RESTORE or RESTORE WORD commands. o If you put the cursor on a nonwhite space word separator, ERASE WORD erased the previous word and not the next word, which in this case is just the word separator. This is fixed so that ERASE WORD erases the word separator under the cursor. This fix required modifying the procedure EVE$AT_START_OF_WORD to return true if positioned on a nonwhite space word separator. o When positioned on white space between words, EVE sometimes treated the word to the left of the cursor as the current word, and other times treated the word to the right as the current word. Consistent behavior would imply that as long as you are not at the start of the next word, you are still on the previous word. Inconsistent commands are CAPITALIZE WORD, ERASE WORD, LOWERCASE WORD, and UPPERCASE WORD that all operate on the word to the right of the white space. The default behavior of the CAPITALIZE, LOWERCASE, and UPPERCASE WORD commands has not changed. However, you can make these commands operate on the word to the left of the cursor by assigning a TRUE value to a new EVE variable EVE$X_WORD_IS_ON_LEFT: EVE$X_WORD_IS_ON_LEFT := TRUE; ! cap/low/upp use word to left This fix required modifying the procedure EVE$CURRENT_ WORD to provide the default or optional behavior depending upon the value of the new variable. The ERASE WORD command behavior has not changed since you can erase the word to the left by using the ERASE PREVIOUS WORD command, or by changing the buffer direction to reverse, and then using ERASE WORD. B-47 DECTPU and EVE Release Notes B.10 EVE Problems That Have Been Fixed o MOVE BY WORD did not treat white space word separators the same as nonwhite space word separators. Given the text "ABC [DEF" with the bracket "[" being a word separator, MOVE BY WORD would not move the same when positioned on the word "ABC" as when positioned on the space. From anywhere in the word "ABC", MOVE BY WORD moved to the "[", while from the space, it moved to the "D". This is fixed so that MOVE BY WORD moves to the "[" in both cases. This change required changing the pattern variable EVE$PATTERN_END_OF_WORD. o CAPITALIZE WORD of a range did not restrict itself to the end of the range, but would change all letters (except the first) in the last word to lowercase even if they extended past the range. This is fixed so that CAPITALIZE WORD restricts itself to the select range, as do LOWERCASE WORD and UPPERCASE WORD. o LOWERCASE WORD and UPPERCASE WORD of a range jumped to the start of the word following the range. This is fixed so that they move to the character following the range as does CAPITALIZE WORD. o While positioned in the command window, the ERASE PREVIOUS WORD and ERASE WORD commands, and the EDT keypad F13, Ctrl/J, and LINEFEED keys erased not only the previous word, but also the white space before that word. This was inconsistent with how they operated in other windows where they erased only the previous word. This has been fixed so that they erase only the previous word whether or not positioned in the command window. o A tab character could not be used as a word separator since it was already used in EVE's definition of white space. This prevented you from using the MOVE BY WORD command to move by tabs. A workaround exists for this restriction. EVE has a new procedure, EVE$ASSIGN_ WHITESPACE, that takes a single string argument equal to the desired white space characters. EVE passes a string constant, EVE$KT_WHITESPACE, containing a space and a tab to set the default white space. As in the following example, you can call this procedure and pass only a space character. This removes the tab character from EVE's white space definition and allows moving by tabs. B-48 DECTPU and EVE Release Notes B.10 EVE Problems That Have Been Fixed EVE$ASSIGN_WHITESPACE (" "); ! Use only space as white space Note that constant EVE$KT_WHITESPACE is only the default white space. EVE holds the current white space definition in variable EVE$X_WHITESPACE. Applications should use that variable when testing if on a white space character. B-49 _________________________________________________________________ Index A CLUSTER_CONFIG.COM procedure _______________________________ unsupported on OpenVMS Alpha, Accounting utility 4-18 spurious message, 4-2 CLU_MOUNT_DISK.COM procedure APPEND/PROTECTION command supported on standalone incorrect behavior, 3-1 OpenVMS Alpha using DSSI Associated documents, xii disks, 4-18 Authorize utility (AUTHORIZE), CMA, 5-9 4-2 restrictions, 5-9 AUTOGEN command procedure, 4-3 Computer Interconnect Automated pool management, 4-7 See CI AWSTIME system parameter, 4-6 CONSCOPY procedure B not available on OpenVMS _______________________________ Alpha, 4-8 Backing up an OpenVMS Alpha Console volume system disk, 4-7 copying Backup utility (BACKUP) CONSCOPY.COM not available restrictions, 4-7 on OpenVMS Alpha, 4-8 BASIC images COPY/PROTECTION command translated, 5-34 incorrect behavior, 3-1 BLAS CRDENABL system parameter, 6-4 translated, 5-34 CREATE/FDL command, 5-11 C______________________________ D______________________________ chan argument, 5-20 DCL commands and utilities, CI (Computer Interconnect) 3-1 unsupported on OpenVMS Alpha, APPEND/PROTECTION, 3-1 4-8 COPY/PROTECTION, 3-1 Cluster aliases $DCLCMH system service, 5-21 unsupported on OpenVMS Alpha, 4-17 Index-1 DDCMP (DIGITAL Data DECTPU Communications Message aborting READ_* built- Protocol) ins in DECwindows Motif unsupported on OpenVMS Alpha, applications, B-26 4-8 DCL command line Debugger, 5-2 /CHARACTER_SET qualifier, known problems, 5-2 to 5-9 B-2 restrictions, 5-2 to 5-9 /DISPLAY qualifier, B-20 DEC 3000 AXP Model 400, 2-7 multiple input files, B-1 multi-head configuration, DECwindows Motif interface 2-7 C binding, B-13 platform for the DECwindows cursor blink, B-31 X11 display server, 2-3, DEFINE_WIDGET_CLASS built- 2-4 in, B-13, B-28 DEC 3000 AXP Model 500, 2-8 detached cursor action multi-head configuration, routine, B-41 2-7 icon control, B-14 platform for the DECwindows icon name, B-34 X11 display server, 2-3, icon sizes, B-15 2-4 resize, B-31 DEC 3000 AXP series computers, resource files, B-27 2-3 small monitors, B-27 See also DEC 3000 AXP Model UID files, B-11 400 VMS binding, B-13 widget create routine, See also DEC 3000 AXP Model B-13, B-28 500 DEFINE_WIDGET_CLASS built-in, support for the DECwindows B-13, B-28 X11 display server, 2-3, /DISPLAY qualifier, B-20 2-4 enhancements DEC 4000 AXP, 2-8 modified built-ins, B-12 restrictions, 2-8 to B-18 DEC 7000 AXP Model 600 series, new built-ins, B-7 to 2-9 B-12 DSA device naming, 2-9 FAO built-in, B-18 DSA disk and tape support, GET_INFO built-ins 2-9 COMMAND_LINE keyword restrictions, 2-9 CHARACTER_SET request, SCSI support, 2-12 B-13 DECnet for OpenVMS Alpha, 4-8 FIRST_FILE_NAME request restrictions, 4-8 , B-9 DECthreads, 5-9 NEXT_FILE_NAME request, restrictions, 5-9 B-9 SCREEN keyword Index-2 DECTPU DECTPU (cont'd) GET_INFO built-ins modified built-ins, B-12 to SCREEN keyword (cont'd) B-18 DECwindows Motif multiple character sets, B-2 request, B-13 multiple input files DEC_CRT3 request, B-15 See DCL command line DEC_CRT4 request, B-15 new built-ins, B-7 to B-12 DEFAULT_FILE request, LOWER_WIDGET, B-9 B-12 RAISE_WIDGET, B-9 FIRST_INPUT request, new error messages B-8 TPU$_WORKFILEFAIL, B-20 FIRST_INPUT_ACTION new features, B-1 to B-3 request, B-8 OFF keyword, B-18 to B-20 MOTIF request, B-7 ON keyword, B-18 to B-20 PIXEL_LENGTH request, problems fixed, B-27 to B-35 B-10 aborted READ_KEY, B-32 PIXEL_WIDTH request, BUFFER CHANGE JOURNALING, B-10 B-30 POP_UP_PARENT_WIDGET callable interface, B-31 request, B-10 crash with partial escape VT400 request, B-15 sequence, B-32 WIDGET request, B-11 Ctrl/C and aborting XUI request, B-8 compilation, B-27 SCREEN KEYWORD Ctrl/C definition, B-28 DECwindows Motif, B-8 Ctrl/C during startup, SYSTEM B-28 operating_system cursor blink, B-31 request, B-13 DECwindows Motif READ_LINE WIDGET keyword cancel button, B-33 WIDGET_ID request, DECwindows Motif READ_LINE B-17 crash, B-33 WIDGET_RESOURCE_TYPES DECwindows Motif READ_LINE request, B-11 terminators, B-33 WINDOW keyword DECwindows Motif resize, SCREEN_UPDATE request, B-31 B-16 DEFINE_WIDGET_CLASS, B-28 /INTERFACE qualifier, B-20 error opening work file, journaling performance with B-20 included files, B-30 FAO !AF directive no logical names longer used, B-28 TPU$CHARACTER_SET, B-2 focus events abort prompts LOWER_WIDGET built-in, B-9 , B-32 MESSAGE built-in, B-18 HELP_TEXT with prompting MESSAGE_TEXT built-in, B-18 on, B-29 Index-3 DECTPU DECTPU (cont'd) problems fixed (cont'd) READ_FILE built-in journaling improved DECwindows Motif performance, B-30 error messages, B-29 RECOVER_BUFFER built-in, invalid UID hierarchy B-30 identifier crash, B-35 RECOVER_BUFFER built-in and journaling performance, included files, B-30 B-30 restrictions, B-25 to B-27 KEY_NAME of Ctrl/I or Ctrl aborted READ_CHAR, B-26 /M, B-30 aborted READ_KEY, B-26 LAST_KEY, B-33 SET built-in logical name conflict with MAPPED_WHEN_MANAGED journal file name, B-30 keyword, B-26 mouse click during ADJUST_ small display monitors, WINDOW, B-33 B-27 multiple-line text strings SEND built-in character limit for widgets, B-32 , B-15 padding with more than 255 SET built-in spaces, B-34 DEFAULT_FILE keyword, READ_FILE built-in, B-30 B-12 READ_KEY built-in, B-32 DRM_HIERARCHY keyword, READ_LINE abort with Ctrl B-11, B-13 /C, B-33 FIRST_INPUT_ACTION keyword READ_LINE crash with long , B-8 prompt string, B-33 GLOBAL_SELECT keyword, reverse SEARCH crash, B-14 B-33 ICONIFY_PIXMAP keyword, SET (TIMER) built-in, B-15 B-34 ICON_PIXMAP keyword, B-14 SET built-in MENU_POSITION keyword, ICON_PIXMAP Keyword, B-15 B-34 SCREEN_UPDATE keyword, JOURNALING keyword, B-16 B-30 UID keyword, B-11 WIDGET_CALLBACK keyword WIDGET_CONTEXT_HELP , B-34 keyword, B-10 SET(DEFAULT_DIRECTORY) WIDGET_RESOURCE_TYPES built-in, B-32 keyword, B-11 TPU$TPU and UID files, B-11 /INTERFACE=DECWINDOWS, WRITE_FILE built-in, B-17 B-31 DECwindows Motif TRANSLATE and screen EVE Motif interface updating, B-35 See EVE Motif Interface RAISE_WIDGET built-in, B-9 Index-4 DECwindows Motif (cont'd) Documentation correction using EVE in a DECterm (cont'd) emulator, 3-3 OpenVMS DCL Dictionary, 6-1 DECwindows transport OpenVMS Linker Utility Manual restrictions, 2-5 , 6-2 DECwindows X11 display server VMS National Character Set and driver, 2-3, 2-4 Utility Manual, 6-2 error recovery, 2-6 Documentation release notes, font compiler restrictions, 6-1 2-5 DPML font formats, 2-4 See Digital Portable known problems, 2-6 Mathematics Library multi-head support, 2-7 DSA device naming, 2-9 reporting errors, 2-6 DSA disk restrictions, 2-6 local device naming server extensions, 2-3, 2-4 differences on OpenVMS Defined system logicals, 5-31 Alpha and OpenVMS VAX, Device drivers 2-9 supplied by Digital DSA disk and tape support, 2-9 file name format change, DSSI (Digital Storage Systems 4-9 Interconnect) Device naming using CLU_MOUNT_DISK.COM DSA differences on OpenVMS procedure, 4-18 Alpha and OpenVMS VAX, 2-9 E______________________________ DIGITAL Data Communications EDIT command Message Protocol default editor changed to See DDCMP TPU, 3-2 Digital Portable Mathematics EDT, 3-2 Library (DPML), 5-14 selecting EDT keypad in DIGITAL Storage Architecture EVE, 3-3 disk used with DCL command See DSA disk procedures, 3-2 multiple input files, B-1 Digital Storage Systems overriding the default editor Interconnect , 3-2 See DSSI /TPU, B-1 DKDRIVER /DISPLAY qualifier, B-20 restriction, 2-12 /INTERFACE qualifier, Documentation correction B-20 ALARM ACE, 6-1 ALARM_JOURNAL ACE, 6-1 OpenVMS Alpha Guide to System Security, 6-4 Index-5 Edit/FDL utility (EDIT/FDL), EVE (cont'd) 5-11 GET WILDCARDED FILES command, ERF B-21 See Error Log Report GLOBAL REPLACE command, B-21 Formatter miscellaneous enhancements, Error Log Report Formatter B-22 to B-25 (ERF), 4-9 Motif interface restrictions, 4-9 handling callbacks, B-4 Error messages handling resources, B-4 new messages, A-1 new commands, B-20 to B-21 EVE new features, B-3 to B-7 commands in system buffers, parser prefix, B-37 B-22 problems fixed, B-35 to B-49 CENTER LINE command, B-22 ambiguous help command in FILL command, B-22 /init, B-40 FILL PARAGRAPH command, BOX CUT from beyond eof of B-22 buffer, B-35 FILL RANGE command, B-22 box operations in SET BUFFER command, B-22 overstrike with left SET LEFT MARGIN command, margins, B-35 B-22 buffer selection in SET RIGHT MARGIN command, SHOW [SYSTEM] BUFFERS B-22 command, B-40 copyright, B-25 CCT resize, B-44 DECwindows Motif interface concealed logical names, input focus, B-21 B-37 MB1 and found range, B-41 creating buffer MAIN after menu changes, B-23 detached cursor, B-41 primary selection, B-21 Ctrl/C and RECOVER, B-44 Quick Cut, B-41 cursor position during SET FUNCTION KEYS MOTIF, mouse drag, B-42 B-21 DECspell not installed, title bar copyright, B-25 B-36 edit handlers in system DECwindows Motif interface buffers, B-22 DECwindows Motif EVE$$PARSE procedure, B-37 primary cut, B-43 EVE$KEYPAD logical name, B-7 input focus, B-43 EVE$SETUP_WINDOWS procedure, Quick Cut adds B-37 linebreak, B-41 EVE$TEARDOWN_WINDOWS subprocess creation, procedure, B-37 B-36 FILL commands, B-23 EVE open dialog box filter FILL RANGE procedure, B-39 , B-42 GET command, B-21 Index-6 EVE EVE problems fixed (cont'd) problems fixed (cont'd) EVE$AT_START_OF_WORD prompt reply trimmed, procedure changed, B-44 B-47 /RECOVER qualifier, B-44 EVE$BUILD, B-36 repeat operations, B-38 EVE$CURRENT_WORD procedure command line commands, optional behavior, B-47 B-38 EVE$PATTERN_END_OF_WORD commands, B-38 pattern changed, B-47 initialization file EVE$SETUP_WINDOWS (init), B-38 procedure, B-37 learn sequences, B-38 EVE$TEARDOWN_WINDOWS optional argument, procedure, B-37 B-38 FILL RANGE procedure, prompting of repeated B-39 REPEAT commands, FIND SELECTED, B-39 B-38 GET [WILD] FILE[S], B-36 repeat counts not help on GET_INFO built-in, multiplied, B-38 B-40 WPS remove and repeat initial GET command in counts, B-38 command buffer, B-40 SAVE ATTRIBUTES command, initialization file (init) B-35 , B-40 SAVE SYSTEM ATTRIBUTES large line count in SHOW command, B-35 display, B-46 secondary selection, B-42 learn sequences and the setting icon pixmap on repeat command, B-38 window managers other $LOCAL$INI$ buffer, B-35 than Motif, B-36 logical name conflict with SHOW BUFFERS command journal file name, B-44 and two windows, B-46 long-named buffers, B-40 choosing a buffer, MB1 and found range, B-41 B-40 Motif Style Guide fixes, slow operations when very B-43 long lines of white Open dialog box and space., B-40 wildcard files, B-42 system buffers, B-46 OPEN SELECTED command, use of SET(HEIGHT) DECTPU B-42 built-in, B-44 and multiple file users can shut off selections, B-42 scrolling, B-45 parser prefix, B-37 wildcard files from Open prompt buffer, B-46 dialog Box, B-42 wildcard input file, B-46 Index-7 EVE EVE (cont'd) problems fixed (cont'd) SPELL command, B-25 word operations, B-47 system buffers, B-22 CAPITALIZE WORD user-defined keypad, B-7 exceeded end of Executive range, B-48 missing functions, 5-10 ERASE WORD lost white SYS.EXE renamed to SYS$BASE_ space, B-47 IMAGE.EXE, 5-10 ERASE WORD on a nonwhite space word F______________________________ separator, B-47 FDL Erasing word in command See File Definition Language window, B-48 File Definition Language (FDL) EVE$AT_START_OF_WORD , 5-11 changed, B-47 File system EVE$CURRENT_WORD support, 5-10 optional behavior, Font formats, 2-4 B-47 $FORMAT_AUDIT width argument, inconsistent interword 5-22 behavior, B-47 LOWERCASE and UPPERCASE G______________________________ movement, B-48 General user MOVE BY WORD and information, 3-1 nonwhite space word separators, B-47 H______________________________ tab not a word Help Message utility (MSGHLP), separator, B-48 3-4 wrong $DEFAULTS$ buffer features, 3-4 settings, B-41 restriction, 3-5, 4-10 restrictions, B-25 to B-27 SET FILL [NO]TAGS command, I B-23 _______________________________ SET SCROLL JUMP command, I/O configuration support in B-45 SYSMAN, 4-15 SET SCROLL OFF command, B-45 IEEE floating point standard, SET SCROLL ON command, B-45 5-11 SET SCROLL SMOOTH command, IIFs B-45 See image information files SET SELECTION GRAB FOCUS Image information files (IIFs) command, B-21 , 5-24, 5-30 SET SELECTION GRAB SELECTION provided with OpenVMS Alpha, command, B-21 5-29 SHOW SYSTEM BUFFERS command choosing a buffer, B-40 Index-8 Installation MSGHLP of operating system, 2-2 See Help Message utility MTHRTL, 5-14 L______________________________ translated, 5-34 LAT, 4-10 Multi-head configuration startup, 4-10 on a DEC 3000 AXP Model 400, License Management facility 2-7 (LMF), 4-11 on a DEC 3000 AXP Model 500, Linker utility 2-7 restrictions, 5-12 LMF N______________________________ See License Management National Character Set (NCS), facility 5-11 Logical names Native debugger support, 5-2 EVE keypad selection, B-7 NCS TPU character set selection, See National Character Set B-2 O______________________________ M______________________________ OPCOM functions, 4-14 MACRO-32 Compiler for OpenVMS OpenVMS Linker Utility Manual Alpha, 5-12 documentation correction, restriction, 5-12 6-2 Mail utility (MAIL) Operating system change in default editor, differences between OpenVMS 3-5 VAX Version 5.5 and MAT functions, 5-34 OpenVMS Alpha, 1-2 Messages environment, 2-1 new messages, A-1 installation, 2-2 MONITOR CLUSTER command, 4-18 reporting software problems, MONITOR MSCP command 1-3 on OpenVMS Alpha, 4-14 unsupported components and MONITOR SCS command, 4-18 functionality, 1-2 Monitor utility (MONITOR), 4-13 P restrictions, 4-13 _______________________________ MOUNT command, 4-14 PALcode /CLUSTER qualifier required version, 2-3 unsupported, 4-17 Password generation, 4-14 Mount utility (MOUNT), 4-14 Performance measurements, 4-6 restrictions, 4-14 PFCDEFAULT system parameter MPW_WRTCLUSTER system changed maximum value on parameter OpenVMS Alpha, 4-4 changed default value on OpenVMS Alpha, 4-4 Index-9 PFRATH system parameter Restrictions (cont'd) changed default value on SCSI port driver for DEC 4000 OpenVMS Alpha, 4-4 AXP, 2-8 PHYSICALPAGES system parameter SET PASSWORD command, 4-14 , 4-6 SORT/MERGE, 3-6 PHYSICAL_MEMORY system SUMSLP Utility (SUMSLP), parameter, 4-6 5-17 Programming environment, 5-1 System Dump Analyzer (SDA) utility, 5-18 Q______________________________ system services, 5-22 QUANTUM system parameter, 4-6 terminal fallback facility, 4-17 R______________________________ translated callers to Reporting software problems, CRF$FREE_VM or CRF$GET_ 1-3 VM, 5-35 Restrictions TZK10, 2-12 backing up an OpenVMS Alpha UETP, 3-7 system disk, 4-7 UIC values, 4-2 BREAKPOINTS system parameter, VAX FORTRAN RTL, 5-38 VMScluster, 4-17 5-25 Run-time libraries, 5-14 debugger, 5-2 to 5-9 accessing the D56 form, 5-34 DEC 4000 AXP, 2-8 Running OpenVMS Alpha, 2-1 DEC 7000 AXP Model 600 series , 2-9 S______________________________ DECnet for OpenVMS Alpha, SCSI 4-8 data check functionality DECthreads, 5-9 restrictions, 2-12 DECwindows transport, 2-5 DKDRIVER restriction, 2-12 DECwindows X11 display server restricted use on DEC 4000 , 2-6 AXP, 2-8 Error Log Report Formatter restrictions on OpenVMS Alpha (ERF), 4-9 platforms, 2-12 executive, 5-10 support on DEC 7000 AXP Model font compiler, 2-5 600 series, 2-12 Linker utility, 5-12 MACRO-32 Compiler for OpenVMS SDA Alpha, 5-12 See System Dump Analyzer Monitor utility, 4-13 utility (SDA) Mount utility, 4-14 SET CLUSTER command, 4-18 password generation, 4-14 SET PASSWORD command privileges, protections, and restriction, 4-14 quotas, 4-15 SHOW CLUSTER command, 4-18 QIC standard, 2-12 SCSI, 2-12 Index-10 SHOW MACHINE_CHECK command, System Dump Analyzer utility 5-17 (SDA) (cont'd) Small computer systems incorrect SHOW CRASH display, interface (SCSI) port driver 5-20 restriction, 2-8 problem using the SHOW LOCK supported on the DEC 7000 AXP command, 5-19 Model 600 series, 2-12 restrictions, 5-18, 5-19, SORT/MERGE command, 3-6 5-20 Sort/Merge utility (SORT RMS commands, 5-20 /MERGE) SHOW MACHINE_CHECK command, restrictions, 3-6 5-17 Spinlock changes, 5-10 System generation utility STARLET data structures and (SYSGEN), 4-15 definitions, 5-15 unsupported commands, 4-15 SUMSLP Utility (SUMSLP), 5-17 System management Supported systems, 2-1 to 2-12 features, 4-2 Symbolic traceback, 5-22 System management utility SYS$BASE_IMAGE.EXE, 5-10 (SYSMAN), 4-15 SYS.EXE renamed to SYS$BASE_ System messages IMAGE.EXE, 5-10 new messages, A-1 SYSGEN utility, 4-15 System parameters, 4-6 unsupported commands, 4-15 and performance measurements, SYSMAN (System Management 4-6 utility) AWSTIME, 4-6 CONFIGURATION SET CLUSTER_ CRDENABL, 6-4 AUTHORIZATION command, MPW_WRTCLUSTER 4-18 changed default value on CONFIGURATION SHOW CLUSTER_ OpenVMS Alpha, 4-4 AUTHORIZATION command, PFCDEFAULT 4-18 changed maximum value on SET ENVIRONMENT/CLUSTER OpenVMS Alpha, 4-4 command, 4-18 PFRATH SHOW/CLUSTER command, 4-18 changed default value on SYSMAN utility, 4-15 OpenVMS Alpha, 4-4 I/O configuration support, PHYSICAL_MEMORY, 4-6 4-15 QUANTUM, 4-6 System Dump Analyzer utility removed from OpenVMS Alpha, (SDA) 4-7 features, 5-17 WSINC general register symbols not changed default value on valid, 5-19 OpenVMS Alpha, 4-4 incorrect behavior of ANALYZE System services, 5-20 /CRASH_DUMP and ANALYZE chan argument, 5-20 /SYSTEM commands, 5-19 Index-11 System services (cont'd) Translation (cont'd) changes in this version, of images, 5-29 to 5-38 5-20 of MTHRTL, 5-34 $DCLCMH, 5-21 of run-time libraries, 5-33 $FORMAT_AUDIT, 5-22 TZK10 restrictions, 5-22 restriction, 2-12 Systems supported, 2-1 to 2-12 U______________________________ T UETP _______________________________ device test support, 3-7 Terminal Fallback facility restrictions, 3-7 (TFF), 4-16 Unsupported restrictions, 4-17 components and functionality, Terminal Fallback utility 1-2 (TFU), 4-16 SYSGEN commands, 4-15 TFF Upgrade See Terminal Fallback requirement, 2-2 facility V TFU _______________________________ See Terminal Fallback utility VAX C Run-Time Library, 5-36 Threads, 5-9 to 5-38 restrictions, 5-9 functional restrictions, TIE 5-36 See Translated Image interoperability restrictions Environment , 5-37 TIE$SHARE shareable image, VAX FORTRAN RTL restriction, 5-38 5-23 VAXTPU TPU See DECTPU See DECTPU VMS National Character Set Traceback handler Utility Manual (NCS) support, 5-22 documentation correction, Translated VAX BASIC Run-Time 6-2 Library, 5-35 VMScluster capabililty restrictions, 5-35 affects maintenance commands Translated Image Environment and features, 4-17 (TIE), 5-23 VMScluster support, 4-17 restrictions, 5-25 VMSINSTAL, 2-2 Translation of BASIC images, 5-34 of BLAS$, 5-34 of callers to CRF$FREE_VM or CRF$GET_VM, 5-35 of executables, 5-29 to 5-38 Index-12 W______________________________ Watch chip (BBW) change in time range, 4-19 WSINC system parameter changed default value on OpenVMS Alpha, 4-4 Index-13