K ---------------------------------------------------------------------------                 H                     ____________________________________________________'                     OpenVMS Version 7.3 ;                     New Features and Documentation Overview     -                     Order Number: AA-QSBFD-TE                          April 2001  E                     This manual describes the new features associated F                     with the OpenVMS Alpha and OpenVMS VAX Version 7.3F                     operating systems, and provides an overview of the=                     documentation that supports the software.               G                     Revision/Update Information:  This is a new manual.   G                     Software Version:             OpenVMS Alpha Version 5                                                   7.3 I                                                   OpenVMS VAX Version 7.3       /                     Compaq Computer Corporation "                     Houston, Texas                 J           ________________________________________________________________  ,            2001 Compaq Computer Corporation  C           Compaq, AlphaServer, POLYCENTER, VAX, VMS, and the Compaq >           logo Registered in U.S. Patent and Trademark Office.  @           OpenVMS and Tru64 are trademarks of Compaq InformationA           Technologies Group, L.P. in the United States and other            countries.  A           UNIX and X/Open are trademarks of The Open Group in the ,           United States and other countries.  D           All other product names mentioned herein may be trademarks(           of their respective companies.  C           Confidential computer software. Valid license from Compaq C           required for possession, use, or copying. Consistent with >           FAR 12.211 and 12.212, Commercial Computer Software,A           Computer Software Documentation, and Technical Data for D           Commercial Items are licensed to the U.S. Government under/           vendor's standard commercial license.   ?           Compaq shall not be liable for technical or editorial ?           errors or omissions contained herein. The information ?           in this document is provided "as is" without warranty B           of any kind and is subject to change without notice. TheE           warranties for Compaq products are set forth in the express A           limited warranty statements accompanying such products. ?           Nothing herein should be construed as constituting an            additional warranty.  E                                                                ZK6620   >           The Compaq OpenVMS documentation set is available on           CD-ROM.   D           This document was prepared using VAX DOCUMENT Version 2.1.                                 C   _________________________________________________________________   C                                                            Contents       C   Preface...................................................     xi   *   Part I  OpenVMS Version 7.3 New Features    0   1  Summary of OpenVMS Version 7.3 New Features  '   2  Compaq OpenVMS e-Business Features   C         2.1   Compaq Secure Web Server for OpenVMS Alpha....    2-2 C         2.2   Compaq COM for OpenVMS........................    2-2 6         2.3   Compaq Java 2 SDK, Standard Edition, forC               OpenVMS Alpha.................................    2-2 ;         2.4   Compaq Fast Virtual Machine (Fast VM) for the C               Java 2 Platform...............................    2-3 C         2.5   Compaq XML Technology.........................    2-3 C         2.6   Attunity Connect "On Platform" Package........    2-3 6         2.7   Compaq Enterprise Directory Services forC               e-Business....................................    2-4 C         2.8   Reliable Transaction Router (RTR).............    2-4 C         2.9   Compaq BridgeWorks............................    2-5      3  General User Features  C         3.1   DCL Commands and Lexical Functions............    3-1 C         3.2   New Online Help Topics for Utility Routines...    3-4 C         3.3   MIME Utility Enhancements.....................    3-5 C         3.4   WWPPS Utility (Alpha).........................    3-6             C                                                                 iii                    !     4  System Management Features   =           4.1   OpenVMS Support for New AlphaServer GS Series E                 Systems.......................................    4-1 5           4.1.1     OpenVMS Support for Hard and Soft E                     Partitions................................    4-1 :           4.1.2     OpenVMS Resource Affinity Domain (RAD)E                     Support for Applications..................    4-2 E           4.1.3     OpenVMS Support for CPU Online Replace....    4-2 E           4.2   Automatic Setting of Daylight Savings Time....    4-3 E           4.3   Class Scheduler for CPU Scheduling............    4-3 E           4.4   Dedicated CPU Lock Manager (Alpha)............    4-5 7           4.4.1     Implementing the Dedicated CPU Lock E                     Manager...................................    4-5 E           4.4.2     Enabling the Dedicated CPU Lock Manager...    4-6 =           4.4.3     Using the Dedicated CPU Lock Manager With E                     Affinity..................................    4-7 =           4.4.4     Using the Dedicated CPU Lock Manager with E                     Fast Path Devices.........................    4-8 ;           4.4.5     Using the Dedicated CPU Lock Manager on E                     the AlphaServer GS Series Systems.........    4-8 ;           4.5   OpenVMS Enterprise Directory for e-Business E                 (Alpha).......................................    4-9 E           4.6   Extended File Cache (Alpha)...................   4-10 7           4.7   /ARB_SUPPORT Qualifier Added to INSTALL E                 Utility (Alpha)...............................   4-11 E           4.8   MONITOR Utility New Features..................   4-11 E           4.9   OpenVMS Cluster Systems.......................   4-11 E           4.9.1     Clusterwide Intrusion Detection...........   4-12 8           4.9.2     Fast Path for SCSI and Fibre ChannelE                     (Alpha)...................................   4-12 =           4.9.3     Floppy Disks Served in an OpenVMS Cluster E                     System (Alpha)............................   4-13 E           4.9.4     New Fibre Channel Support (Alpha).........   4-13 4           4.9.4.1     New Fibre Channel Tape SupportE                       (Alpha).................................   4-15 E           4.9.5     LANs as Cluster Interconnects.............   4-15 E           4.9.5.1     SCA Control Program.....................   4-16 E           4.9.5.2     New Error Message About Packet Loss.....   4-16 E           4.9.6     Warranted and Migration Support...........   4-17 4           4.10  OpenVMS SMP Performance ImprovementsE                 (Alpha).......................................   4-18 E           4.11  New SYSMAN Commands and Qualifiers............   4-21 E           4.12  New System Parameters.........................   4-22        iv                   I               4.12.1    AUTO_DLIGHT_SAV...........................   4-22 I               4.12.2    FAST_PATH_PORTS...........................   4-22 I               4.12.3    GLX_SHM_REG...............................   4-23 I               4.12.4    LCKMGR_CPUID (Alpha)......................   4-23 I               4.12.5    LCKMGR_MODE (Alpha).......................   4-23 I               4.12.6    NPAGECALC.................................   4-24 I               4.12.7    NPAGERAD (Alpha)..........................   4-24 I               4.12.8    RAD_SUPPORT (Alpha).......................   4-25 I               4.12.9    SHADOW_MAX_UNIT...........................   4-25 I               4.12.10   VCC_MAX_IO_SIZE (Alpha)...................   4-26 I               4.12.11   VCC_READAHEAD (Alpha).....................   4-26 I               4.12.12   WBM_MSG_INT...............................   4-27 I               4.12.13   WBM_MSG_LOWER.............................   4-27 I               4.12.14   WBM_MSG_UPPER.............................   4-28 I               4.12.15   WBM_OPCOM_LVL.............................   4-29 I               4.13  Volume Shadowing for OpenVMS..................   4-29 ?               4.13.1    Minicopy in Compaq Volume Shadowing for I                         OpenVMS (Alpha)...........................   4-29 9               4.13.2    New Volume Shadowing Features for I                         Multiple-Site OpenVMS Cluster Systems.....   4-30 =               4.13.2.1    How to Use the New DISMOUNT and SET I                           Command Qualifiers......................   4-34 8               4.13.3    Using INITIALIZE/SHADOW/ERASE to<                         Streamline the Formation of a ShadowI                         Set.......................................   4-37            5  Programming Features   I               5.1   3D Graphics Support...........................    5-1 @               5.2   3X-DAPBA-FA and 3X-DAPCA-FA ATM LAN AdaptersI                     (Alpha).......................................    5-2 I               5.3   Compaq COBOL Run-Time Library Enhancements....    5-2 I               5.4   Compaq C Run-Time Library Enhancements........    5-3 I               5.4.1     Strptime Function Is XPG5-Compliant.......    5-3 <               5.4.2     Limitation of Eight Nested DirectoryI                         Levels Was Lifted (Alpha).................    5-4 :               5.4.3     Improved Support for Extended FileI                         Specifications (Alpha)....................    5-4 A               5.4.3.1     Compaq C RTL Supports Case Preservation I                           in File Names...........................    5-4 9               5.4.3.2     Most C RTL Functions Now Accept >                           Long OpenVMS File Names As ArgumentsI                           (Alpha).................................    5-5     I                                                                         v                    9           5.4.4     Compaq C RTL Supports Exact Case Argv E                     Arguments (Alpha).........................    5-5 >           5.4.5     Compaq C RTL Can Implicitly Open Files forE                     Shared Access.............................    5-6 :           5.4.6     Alternate Way of Translating UNIX FileE                     Specifications............................    5-6 E           5.4.7     New Functions.............................    5-7 E           5.5   Fortran Support for 64-Bit Address (Alpha)....    5-7 E           5.6   Large Page-File Sections (Alpha)..............    5-7 E           5.7   Multipath System Services.....................    5-9 E           5.8   Multiprocess Debugging (Alpha)................   5-10 =           5.9   Performance Application Programming Interface E                 (API).........................................   5-11 8           5.10  POLYCENTER Software Installation UtilityE                 Enhancements..................................   5-11 E           5.11  New Process Dump Tools (Alpha)................   5-12 E           5.11.1    DCL ANALYZE/PROCESS_DUMP Command..........   5-13 E           5.11.2    Debugger ANALYZE/PROCESS_DUMP Command.....   5-13 E           5.11.3    Debugger SDA Command......................   5-14 8           5.11.4    Analyzing Process Dumps on DifferentE                     Systems...................................   5-14 E           5.11.5    Forcing a Process Dump....................   5-15 9           5.11.6    Process Dumps: Security and Diskquota E                     Guidelines................................   5-15 E           5.11.6.1    Special Rights Identifiers..............   5-16 E           5.11.6.2    Privileged Users and Process Dumps......   5-16 E           5.11.6.3    Nonprivileged Users and Process Dumps...   5-16 E           5.11.6.4    Protecting Process Dumps................   5-17 E           5.12  RMS Locking Enhancements......................   5-18 8           5.12.1    RMS Locking Performance EnhancementsE                     (Alpha)...................................   5-18 E           5.12.1.1    RMS Global Buffer Read-Mode Locking.....   5-19 E           5.12.1.2    No Query Record Locking Option..........   5-20 >           5.12.2    Record Locking Options to Control DeadlockE                     Detection.................................   5-23 E           5.13  OpenVMS Registry..............................   5-24 E           5.13.1    REG$CP Registry Utility...................   5-25 3           5.14  Alpha SDA Commands, Parameters, and E                 Qualifiers....................................   5-25                  vi                   I               5.14.1    New Alpha SDA Commands....................   5-25 I               5.14.1.1    DUMP....................................   5-26 I               5.14.1.2    SET SYMBOLIZE...........................   5-29 I               5.14.1.3    SHOW MEMORY.............................   5-29 I               5.14.1.4    SHOW RAD................................   5-32 I               5.14.1.5    SHOW TQE................................   5-32 I               5.14.1.6    UNDEFINE................................   5-33 B               5.14.2    New Parameters and Qualifiers for ExistingI                         Commands..................................   5-33 I               5.14.2.1    REPEAT..................................   5-33 I               5.14.2.2    SEARCH..................................   5-34 I               5.14.2.3    SET OUTPUT..............................   5-34 I               5.14.2.4    SET PROCESS.............................   5-35 I               5.14.2.5    SHOW DEVICE.............................   5-35 I               5.14.2.6    SHOW GCT................................   5-36 I               5.14.2.7    SHOW LOCK...............................   5-36 I               5.14.2.8    SHOW PFN_DATA...........................   5-36 I               5.14.2.9    SHOW POOL...............................   5-36 I               5.14.2.10   SHOW PROCESS............................   5-37 I               5.14.2.11   SHOW RESOURCE...........................   5-38 I               5.14.2.12   SHOW SPINLOCKS..........................   5-39 I               5.14.2.13   SHOW SUMMARY............................   5-39 =               5.15  New SDA Commands for the Spinlock Tracing I                     Utility.......................................   5-39 I               5.15.1    SPL LOAD..................................   5-40 I               5.15.2    SPL SHOW COLLECT..........................   5-40 I               5.15.3    SPL SHOW TRACE............................   5-40 I               5.15.4    SPL START COLLECT.........................   5-42 I               5.15.5    SPL START TRACE...........................   5-42 I               5.15.6    SPL STOP COLLECT..........................   5-44 I               5.15.7    SPL STOP TRACE............................   5-44 I               5.15.8    SPL UNLOAD................................   5-44 I               5.16  System Services...............................   5-44 B               5.17  TCP/IP Files for SDA READ Command That ContainI                     Global Symbols and Locations..................   5-46 I               5.18  Visual Threads Version 2.1 (Alpha)............   5-48                   I                                                                       vii                    #     6  Associated Products Features   E           6.1   Availability Manager..........................    6-1 7           6.2   Compaq Advanced Server V7.3 for OpenVMS E                 (Alpha).......................................    6-2 E           6.3   Compaq DECwindows Motif for OpenVMS...........    6-3 E           6.4   Compaq DCE for OpenVMS........................    6-3 E           6.4.1     Compaq DCE Remote Procedure Call (RPC)....    6-4-E           6.4.2     New Ethernet Device Support...............    6-4_E           6.4.3     For More DCE Information..................    6-4pE           6.5   DECram for OpenVMS Version 3.0 (Alpha)........    6-5OE           6.6   Enterprise Capacity and Performance (ECP).....    6-5 E           6.6.1     ECP Collector for OpenVMS Version 5.4.....    6-6h8           6.6.2     ECP Performance Analyzer for OpenVMSE                     Version 5.4 ..............................    6-6 E           6.7   Kerberos for OpenVMS..........................    6-7tE           6.7.1     New DCL Command KERBEROS..................    6-7iE           6.8   Universal LDAPv3 API (Alpha)..................    6-8 <           6.9   Compaq PATHWORKS V6.0D for OpenVMS (AdvancedE                 Server).......................................    6-8 E           6.10  Compaq Service Tools and DECevent.............    6-9 :           6.11  Compaq TCP/IP Services for OpenVMS VersionE                 5.1...........................................    6-9_E           6.11.1    New Features and Changes..................   6-10C/           6.11.2    TCP/IP Services for OpenVMSCE                     Documentation.............................   6-11e  .     Part II  Overview of OpenVMS Documentation  %     7  OpenVMS Documentation Overviewn  E           7.1   OpenVMS Documentation Changes.................    7-1   /     8  OpenVMS Printed and Online Documentationr  E           8.1   Printed Documentation.........................    8-1nE           8.1.1     OpenVMS Media Kit Documentation...........    8-1dE           8.1.2     OpenVMS Documentation Sets................    8-2i7           8.1.3     Documentation for System Integrated E                     Products..................................    8-6 E           8.1.4     Archived OpenVMS Documentation............    8-6rE           8.2   Online Documentation on CD-ROM................    8-7IE           8.2.1     Online Formats............................    8-7d         viii c  e              I               8.2.2     PDF Viewers...............................    8-7o;               8.3   Online Documentation on the OpenVMS WebtI                     Site..........................................    8-7nI               8.4   Online Help...................................    8-8   *         9  Descriptions of OpenVMS Manuals  I               9.1   Manuals Included in the OpenVMS Media Kit.....    9-1nI               9.2   Manuals in the OpenVMS Documentation Set......    9-2aI               9.2.1     OpenVMS Base Documentation Set............    9-22I               9.2.2     Continuation of Full Documentation Set....    9-3 I               9.3   OpenVMS Alpha Device Driver Manual............   9-10sI               9.4   RMS Journaling Manual.........................   9-10_I               9.5   Archived Manuals..............................   9-10   
         Index              Tables  @               1-1       Summary of OpenVMS VAX and OpenVMS AlphaI                         Version 7.3 Software Features.............    1-3n  I               4-1       SYSMAN command: class_schedule............    4-4   ?               4-2       OpenVMS Cluster Warranted and Migration I                         Support...................................   4-18   I               5-1       PDL Changes...............................   5-11.  A               5-2       Methods Available for Specifying No QueryiI                         Record Locking............................   5-22.  9               5-3       Qualifiers for the SPL SHOW TRACEgI                         Command...................................   5-41f  <               5-4       Qualifiers for the SPL START COLLECTI                         Command...................................   5-42.  :               5-5       Qualifiers for the SPL START TRACEI                         Command...................................   5-43.  B               5-6       Modules Containing Global Symbols and DataI                         Structures Used by SDA....................   5-47H  @               5-7       Modules Defining Global Locations WithinI                         the Executive Image.......................   5-47A  <               7-1       Changes to Documentation for OpenVMSI                         Version 7.3...............................    7-1   I               8-1       OpenVMS Media Kit Manuals.................    8-2   I                                                                        ix. .  .              2           8-2       OpenVMS Full Documentation SetE                     (QA-001AA-GZ.7.3).........................    8-3-  E           9-1       Archived OpenVMS Manuals..................   9-10   3           9-2       Archived Networking Manuals and E                     Installation Supplements..................   9-13                                                                                  x                              I         _________________________________________________________________r  I                                                                   PrefaceC               Intended Audiencea  I               This manual is intended for general users, system managers,tB               and programmers who use the Compaq OpenVMS Operating               System.M  I               This document describes the new features related to Version I               7.3 of the OpenVMS Alpha and OpenVMS VAX operating systems. F               For information about how some of the new features mightC               affect your system, read the release notes before you 3               install, upgrade, or use Version 7.3.            Document Structure  D               This manual contains the following parts and chapters:  9               o  Part I, OpenVMS Version 7.3 New Featuresd  C                  -  Chapter 1 contains a summary of the new OpenVMSP&                     software features.  D                  -  Chapter 2 provides information on the e-BusinessH                     technologies that are included in the Compaq OpenVMSH                     e-Business Infrastructure Package with OpenVMS Alpha                      Version 7.3.  C                  -  Chapter 3 describes new features of interest toFF                     general users of the OpenVMS VAX and OpenVMS Alpha&                     operating systems.  H                  -  Chapter 4 describes new features that are applicable>                     to the tasks performed by system managers.  A                  -  Chapter 5 describes new features that supporti&                     programming tasks.  G                                                                      xi  A  a              C              -  Chapter 6 describes significant layered product newg                 features.4  7           o  Part II, Overview of OpenVMS DocumentationL  E              -  Chapter 7 describes the OpenVMS documentation changes.*                 from the previous version.  <              -  Chapter 8 describes how the documentation is                 delivered.  >              -  Chapter 9 describes each manual in the OpenVMS"                 documentation set.       Related Documents.  ?           For additional information about OpenVMS products and @           services, access the following World Wide Web address:  (           http://www.openvms.compaq.com/       Reader's Comments   C           Compaq welcomes your comments on this manual. Please send48           comments to either of the following addresses:  +           Internet    openvmsdoc@compaq.com   1           Mail        Compaq Computer Corporation :                       OSSG Documentation Group, ZKO3-4/U08(                       110 Spit Brook Rd.+                       Nashua, NH 03062-2698   )     How To Order Additional Documentation.  ;           Use the following World Wide Web address to orderM#           additional documentation:4  (           http://www.openvms.compaq.com/  B           If you need help deciding which documentation best meets(           your needs, call 800-282-6672.           xii  2                          Conventions.  @               The following conventions are used in this manual:  G               Ctrl/x           A sequence such as Ctrl/x indicates that.F                                you must hold down the key labeled CtrlH                                while you press another key or a pointing-                                device button..  F               PF1 x            A sequence such as PF1 x indicates thatG                                you must first press and release the key E                                labeled PF1 and then press and releaseSG                                another key or a pointing device button.o  D               <Return>         In examples, a key name enclosed in aD                                box indicates that you press a key onH                                the keyboard. (In text, a key name is not2                                enclosed in a box.)  I                                In the HTML version of this document, this E                                convention appears as brackets, rather *                                than a box.  @                . . .           A horizontal ellipsis in examples=                                indicates one of the followingR-                                possibilities:   D                                o  Additional optional arguments in a>                                   statement have been omitted.  D                                o  The preceding item or items can be=                                   repeated one or more times..  I                                o  Additional parameters, values, or other =                                   information can be entered.   I               .                A vertical ellipsis indicates the omission F               .                of items from a code example or commandD               .                format; the items are omitted becauseH                                they are not important to the topic being)                                discussed..  >               ( )              In command format descriptions,I                                parentheses indicate that you must encloseCG                                the options in parentheses if you choose.-                                more than one.   D                                                                 xiii c  .                C           [ ]              In command format descriptions, bracketsg>                            indicate optional elements. You canC                            choose one, none, or all of the options..B                            (Brackets are not optional, however, in?                            the syntax of a directory name in ans?                            OpenVMS file specification or in theSA                            syntax of a substring specification inD4                            an assignment statement.)  C           [|]              In command format descriptions, verticalI@                            bars separating items inside bracketsA                            indicate that you choose one, none, orm8                            more than one of the options.  A           { }              In command format descriptions, braces ?                            indicate required elements; you must <                            choose one of the options listed.  9           bold text        This text style represents the.A                            introduction of a new term or the namefE                            of an argument, an attribute, or a reason.   B                            In the HTML version of this ConventionsC                            table, this convention appears as italic                              text.  :           italic text      Italic text indicates important:                            information, complete titles ofC                            manuals, or variables. Variables include C                            information that varies in system output >                            (Internal error number), in commandA                            lines (/PRODUCER=name), and in command1B                            parameters in text (where dd representsD                            the predefined code for the device type).  B           UPPERCASE TEXT   Uppercase text indicates a command, theD                            name of a routine, the name of a file, orC                            the abbreviation for a system privilege.                  xivo .  .                I               Monospace text   Monospace type indicates code examples and.;                                interactive screen displays..  G                                In the C programming language, monospacenD                                type in text identifies the following?                                elements: keywords, the names of4H                                independently compiled external functions?                                and files, syntax summaries, and E                                references to variables or identifiers 8                                introduced in an example.  F                                In the HTML version of this ConventionsG                                table, this convention appears as italic.$                                text.  F               -                A hyphen at the end of a command formatF                                description, command line, or code lineF                                indicates that the command or statement?                                continues on the following line.   D               numbers          All numbers in text are assumed to beI                                decimal unless otherwise noted. Nondecimal H                                radixes-binary, octal, or hexadecimal-are4                                explicitly indicated.                                        D                                                                      xv 2                       I                                                                    Part I.I         _________________________________________________________________.  I                                          OpenVMS Version 7.3 New Features. .  .                    I                                                                         1 I         _________________________________________________________________   I                               Summary of OpenVMS Version 7.3 New Features     D               Compaq OpenVMS Version 7.3 delivers the highest levelsE               of availability, scalability, flexibility, performance, F               and security that are required for e-Business. With moreG               than 20 years of proven reliability, OpenVMS continues to G               improve its availability and performance by including new G               technology into the base operating system and the OpenVMS4C               Cluster software environment. The base infrastructure.D               technologies needed to support e-Business applicationsF               are being incorporated into the OpenVMS license, so that7               OpenVMS is e-Business and Internet ready..  E               OpenVMS Version 7.3 new features include the following:.  ?               o  Continuous improvement of OpenVMS availabilityF  F                  -  Improved disaster tolerant capabilities with ATM &E                     Gigabit Ethernet as cluster interconnects becauserH                     of their inherent high performance and long distance!                     capabilities.   C                  -  Greater system availability during backups withrH                     faster reintegration of shadow members after copies.  H                  -  Enhanced OpenVMS support for the latest ENSA Storage                     offerings.  E                  -  Greater serviceability for the new AlphaServer GS 4                     systems with CPU Online Replace.  :               o  Higher system and application performance  G                  -  Substantial application performance benefits can be >                     realized with the new Extended File Cache.  H                  -  Improved cluster, SMP and system performance throughI                     enhancements to RMS and the clusterwide Lock Manager, E                     as well as FastPath support for Fibre Channel and /                     SCSI storage architectures..  I                           Summary of OpenVMS Version 7.3 New Features 1-1            /     Summary of OpenVMS Version 7.3 New Features       .           o  Expanded OpenVMS security options  ?              -  OpenVMS adds industry standard Kerberos Version.@                 5 security, which allows OpenVMS applications to>                 communicate and authenticate with Windows 2000+                 domains and UNIX platforms.v  9              -  OpenVMS Intrusion Detection expands to be B                 clusterwide, reducing chances of system break-ins.  =           o  Expanded OpenVMS license includes new e-Business               technologies.  D              -  Compaq Secure Web Server for OpenVMS Alpha (based on                 Apache)6  &              -  Compaq COM for OpenVMS  "              -  Compaq BridgeWorks  ;              -  Extensible Markup Language API (XML parser)O  ,              -  Java 2 SDK, Standard Edition  C              -  Attunity Connect "On Platform Package" (native JDBCn                  driver included)  1              -  Reliable Transaction Router (RTR)   C              -  OpenVMS Enterprise Directory for e-Business (X.500)   >           OpenVMS Version 7.3 includes all the capabilities ofE           OpenVMS Version 7.2, OpenVMS Version 7.2-1, and the OpenVMSi+           Version 7.2-1H1 hardware release.m  E           Table 1-1 summarizes each feature provided by OpenVMS Alpha.A           and OpenVMS VAX Version 7.3 and presents these features.>           according to their functional component (e-Business,E           general user, system management, programming, or associated.           product).d  C           New features that are available only on the OpenVMS AlpharD           platform are identified with the word Alpha in the summary@           table and in the section title. These features are not@           available on OpenVMS VAX systems. However, some of theD           OpenVMS Alpha features may be part of a mixed architecture           cluster.  3     1-2 Summary of OpenVMS Version 7.3 New Features  n         I                               Summary of OpenVMS Version 7.3 New FeaturesS      F         Table 1-1 Summary of OpenVMS VAX and OpenVMS Alpha Version 7.3I         __________Software_Features______________________________________S  <                     Compaq OpenVMS e-Business InfrastructureI         ______________Package_for_OpenVMS_Alpha_Version_7.3______________.  F         Compaq OpenVMS e-     This chapter provides information on theH         Business              following e-Business technologies that areG                               included in the Compaq OpenVMS e-Business G                               Infrastructure Package with OpenVMS Alpha *                               Version 7.3:  E                               o  Compaq Secure Web Server for OpenVMSe8                                  Alpha (based on Apache)  7                               o  Compaq COM for OpenVMS   D                               o  Compaq Java 2 SDK, Standard Edition  F                               o  Compaq Fast Virtual Machine (Fast VM)I                                  for the Java 2 Platform on OpenVMS Alpha   6                               o  Compaq XML Technology  G                               o  Attunity Connect "On Platform" Package-  I                               o  Compaq Enterprise Directory Services for.+                                  e-Business   B                               o  Reliable Transaction Router (RTR)  3                               o  Compaq Bridgeworks.  ;                               The Compaq OpenVMS e-BusinessyA                               Infrastructure Package provides key.I                               Internet and e-Business software technologyoB                               that enhances the base OpenVMS AlphaF                               operating system. These technologies areG                               licensed with the OpenVMS Alpha operating.%                               system.   I                                                  (continued on next page)       I                           Summary of OpenVMS Version 7.3 New Features 1-3     -      /     Summary of OpenVMS Version 7.3 New Features       >     Table 1-1 (Cont.) Summary of OpenVMS VAX and OpenVMS AlphaE     __________________Version_7.3_Software_Features__________________   E     _________________________________________________________________iE     ______________________General_User_Features______________________   D     DCL commands          Several DCL commands have been updated for&                           Version 7.3.  E     Utility routines      As of Version 7.3, online help now includes C     online help           all the OpenVMS utility routines that arenC                           described in the OpenVMS Utility Routines !                           Manual.   E     MIME utility          The MIME utility has been enhanced with newy2                           commands and qualifiers.  @     OpenVMS Alpha         The OpenVMS Version 7.3 CD-ROM packageD     firmware              includes the Alpha Systems Firmware Update?                           Version 5.9 CD-ROM and Release Notes.y>                           Please read the Release Notes before2                           installing the firmware.  B     World-Wide            WWPPS is a new utility that allows usersB     PostScript Printing   to print text files in many languages onA     Subsystem (Alpha)     generic PostScript printers that do noth7                           have resident language fonts.   E     _________________________________________________________________ E     ____________________System_Management_Features___________________   B     OpenVMS support for   OpenVMS Version 7.3 provides support forD     new AlphaServer GS    Compaq's AlphaServer GS80, GS160 and GS3209     series systems        systems. This support includes:e  >                           o  OpenVMS support for hard and softE                              partitions (Galaxy) on AlphaServer GS160e.                              and GS320 systems  C                           o  OpenVMS Resource Affinity Domain (RAD)e5                              support for applications   /                           o  CPU Online Replace   E                                              (continued on next page)   3     1-4 Summary of OpenVMS Version 7.3 New Featuresr c  e      I                               Summary of OpenVMS Version 7.3 New Featurese      B         Table 1-1 (Cont.) Summary of OpenVMS VAX and OpenVMS AlphaI         __________________Version_7.3_Software_Features__________________p  I         ___________________System_Management_Features____________________   B         Automatic daylight    System parameter can be set to allowD         savings time change   OpenVMS to automatically change systemE                               time to and from Daylight Savings Time.e  D         CPU Online Replace    OpenVMS Alpha Version 7.3 supports CPUI         (AlphaServer GS160    Online Replace. CPU Online Replace providesmC         /320 systems)         the ability to replace secondary CPUshD                               on a running system without rebooting,H                               which increases system maintainability and-                               serviceability.   D         Class scheduler for   A new class scheduler for both VAX andC         CPU scheduling        Alpha systems allows you to designatesD                               the amount of CPU time that a system'sE                               users may receive by placing users into 1                               scheduling classes.t  G         Dedicated CPU Lock    Compaq for OpenVMS Version 7.3 provides a H         Manager (Alpha)       dedicated CPU lock manager, which improvesE                               SMP system and application performance.   I         OpenVMS Enterprise    OpenVMS Enterprise Directory for e-BusinessdH         Directory for e-      is a massively scalable directory service,I         Business              providing both X.500 and LDAPv3 services on I                               OpenVMS Alpha with no separate license fee.   I                                                  (continued on next page)                           I                           Summary of OpenVMS Version 7.3 New Features 1-5r y         /     Summary of OpenVMS Version 7.3 New Features       >     Table 1-1 (Cont.) Summary of OpenVMS VAX and OpenVMS AlphaE     __________________Version_7.3_Software_Features__________________   E     ____________________System_Management_Features___________________   @     Extended File Cache   XFC improves I/O performance and givesB     (XFC) (Alpha)         you control over the choice of cache andC                           cache parameters. The Extended File CachetE                           improves I/O performance with the followingxB                           features that are not available with the,                           Virtual I/O Cache:  /                           o  Read-ahead cachingl  <                           o  Automatic resizing of the cache  6                           o  Larger maximum cache size  C                           o  No limit on the number of closed files /                              that can be cached   A                           o  Control over the maximum size of I/O /                              that can be cachedd  A                           o  Control over whether cache memory ise.                              static or dynamic  @     INSTALL utility       You can use the /ARB_SUPPORT qualifierD     has /ARB_SUPPORT      with the ADD, CREATE, and REPLACE commandsA     qualifier             in the INSTALL Utility. The ARB_SUPPORT @                           qualifier provides Access Rights BlockA                           (ARB) support to products that have nott>                           yet been updated with the per-threadD                           security Persona Security Block (PSB) data$                           structure.  A     MONITOR utility       Two new MONITOR command parameters have C     enhancements          been added to enhance the OpenVMS displaygD                           of system information. RLOCK and TIMER areD                           used to monitor, respectively, the dynamicC                           lock remastering statistics and the Timer A                           Queue Entry (TQE) statistics of a node.   E                                              (continued on next page)   3     1-6 Summary of OpenVMS Version 7.3 New Features            I                               Summary of OpenVMS Version 7.3 New Features       B         Table 1-1 (Cont.) Summary of OpenVMS VAX and OpenVMS AlphaI         __________________Version_7.3_Software_Features__________________   I         ___________________System_Management_Features____________________   I                                                  (continued on next page)                                                                               I                           Summary of OpenVMS Version 7.3 New Features 1-7t y  r      /     Summary of OpenVMS Version 7.3 New Features       >     Table 1-1 (Cont.) Summary of OpenVMS VAX and OpenVMS AlphaE     __________________Version_7.3_Software_Features__________________v  E     ____________________System_Management_Features___________________t  ?     OpenVMS Cluster       The following are new OpenVMS Cluster #     systems               features:t  @                           Clusterwide      Clusterwide intrusion?                           intrusion        detection is enabled =                           detection        by the integration @                                            of intrusion data and@                                            information from eachD                                            system into a clusterwideB                                            intrusion database. The?                                            clusterwide databaseaD                                            contains all unauthorizedD                                            attempts and the state of?                                            any intrusion event.   E                           Fast Path for    Fast Path is now supported.C                           SCSI and Fibre   on KZPBA (parallel SCSI) D                           Channel (Alpha)  and KGPSA (Fibre Channel)1                                            ports.i  D                           Floppy disk      MSCP supports the serving@                           served in an     of floppy disks in anB                           OpenVMS Cluster  OpenVMS Cluster system,C                           system (Alpha)   provided the devices arelC                                            named in accordance withxE                                            the port allocation namingn7                                            conventions.e  A                           Fibre Channel    Support for larger I/O A                           support (Alpha)  packets, for new Fibre D                                            Channel hardware, and forC                                            larger configurations ise4                                            included.  B                           LANs as cluster  Use of ATM as a cluster@                           interconnects    interconnect improvesD                                            performance, scalability,@                                            and manageability. InE                                            addition, a new management C                                            utility, the SCA Control D                                            Program (SCACP), performsE                                            certain privileged cluster_@                                            management functions.  D                           Warranted        OpenVMS Alpha Version 7.3:     1-8                   and migration    and OpenVMS VAX>                           support          Version 7.3 provideA                                            two levels of support,fC                                            warranted and migration,V@                                            for mixed-version andE                                            mixed-architecture OpenVMSy;                                            Cluster systems.h  E                                              (continued on next page)m v  t      I                               Summary of OpenVMS Version 7.3 New Featuresh      B         Table 1-1 (Cont.) Summary of OpenVMS VAX and OpenVMS AlphaI         __________________Version_7.3_Software_Features__________________s  I         ___________________System_Management_Features____________________   G         POLYCENTER Software   The /FULL qualifier has been added to therI         Installation Utility  PRODUCT LIST command. Use of this qualifieriF         qualifier             produces output in 132-column format andE                               displays supplemental information aboutMG                               each file in the product kit, such as therD                               size of the file and remarks about its$                               usage.  I         Symmetric Multi-      OpenVMS Alpha Version 7.3 contains software ?         Processing (SMP)      changes that improve SMP scaling.p         performance          improvements  H         SYSMAN commands and   Several new SYSMAN commands and qualifiersF         qualifiers            have been added for OpenVMS Version 7.3.  G         System parameters     Several new and updated system parameters F                               have been added for OpenVMS Version 7.3.  E         Volume Shadowing for  Volume Shadowing for OpenVMS introduces 1         OpenVMS               three new features:   ?                               o  Minicopy operation, which is a E                                  streamlined copy operation. Minicopy G                                  can significantly decrease the time it G                                  takes to perform a full copy operation C                                  and can significantly increase thefE                                  availability of the shadow sets that 2                                  use this feature.  E                               o  New qualifiers added to the DISMOUNTsG                                  and SET commands for disaster toleranttE                                  support for OpenVMS Cluster systems.   ?                               o  A new /SHADOW qualifier to the 4                                  INITIALIZE command.  I                                                  (continued on next page)t    I                           Summary of OpenVMS Version 7.3 New Features 1-9e n         /     Summary of OpenVMS Version 7.3 New Featuresr      >     Table 1-1 (Cont.) Summary of OpenVMS VAX and OpenVMS AlphaE     __________________Version_7.3_Software_Features__________________   E     _______________________Programming_Features______________________"  B     3D graphics support   The PowerStorm 300/350 (PBXGD-AD, PBXGD-A                           AE) graphics cards are now supported oniE                           Alpha based systems. The OpenGL 3D graphicsnA                           API is now provided as part of the baseV+                           operating system.   A     ATM LAN adapters      Compaq OpenVMS Version 7.3 provides twoeC     (Alpha)               new ATM LAN adapters, the 3X-DAPBA-FA ands&                           3X-DAPCA-FA.  C     Compaq COBOL Run-     The following enhancements have been made +     Time Library          to the COBOL RTL:   D                           o  Five new intrinsic functions with four-/                              digit year formatsl  =                           o  Improved performance for DISPLAY B                              redirected to a file and for programsC                              compiled with /MATH=CIT3 and MATH=CIT4n$                              (Alpha)  D                           o  Improved compatibility of Alpha and VAXA                              in the handling of the ON SIZE ERRORu  E                                              (continued on next page)r                              4     1-10 Summary of OpenVMS Version 7.3 New Features _  _      I                               Summary of OpenVMS Version 7.3 New Featuresn      B         Table 1-1 (Cont.) Summary of OpenVMS VAX and OpenVMS AlphaI         __________________Version_7.3_Software_Features__________________m  I         ______________________Programming_Features_______________________   B         Compaq C Run-Time     The following enhancements have beenG         Library enhancements  made to the Compaq C Run-Time Library forp2                               OpenVMS Version 7.3:  E                               o  The strptime function was made XPG5-n+                                  compliant.(  I                               o  The limitation of eight nested directory F                                  levels was lifted for an ODS-5 device)                                  (Alpha).a  B                               o  Case preservation in file name is3                                  supported (Alpha).   E                               o  Most C RTL functions now accept long G                                  OpenVMS-style file names as arguments.   G                               o  Exact-case argv arguments is supported )                                  (Alpha).   C                               o  Files can be implicitly opened for /                                  shared access.   ?                               o  There is an alternative way of F                                  translating UNIX file specifications.  F                               o  Several new C RTL functions have been'                                  added.   @         Fortran 64-bit        Support has been added for FortranE         address support       developers to use static data in 64-bit.,         (Alpha)               address space.  D         Large Page-File       Previous limits for page-file sectionsF         sections (Alpha)      have been extended significantly to takeF                               advantage of larger physical memory. NowG                               images that use 64-bit addressing can map E                               and access an amount of dynamic virtual F                               memory that is larger than the amount ofF                               physical memory available on the system.  I                                                  (continued on next page)   I                          Summary of OpenVMS Version 7.3 New Features 1-11  ,  l      /     Summary of OpenVMS Version 7.3 New Featuresh      >     Table 1-1 (Cont.) Summary of OpenVMS VAX and OpenVMS AlphaE     __________________Version_7.3_Software_Features__________________   E     _______________________Programming_Features______________________y  A     Multipath system      New services have been added that allowlD     services              you to return path information and enable,C                           disable, and switch specific I/O paths to %                           any device.N  D     Multiprocess          Debugger support for multiprocess programsC     debugging (Alpha)     has been extensively overhauled. Problems D                           have been corrected and the user-interface,                           has been improved.  C     Nonpaged executive    In previous releases, some of the OpenVMS B     (Alpha)               Alpha executive code was nonpageable (itE                           resided permanently in memory) and some was_D                           pageable. As of OpenVMS Alpha Version 7.3,B                           the base operating system images contain0                           nonpageable code only.  B                           This new nonpageable design improves theB                           performance of system services from 5 toD                           20 percent and uses almost no extra memory@                           because of the method used to link the!                           images.   A     Performance API       The Performance Application Programmingi?                           Interface (API) provides a documented A                           functional interface-the $GETRMI system B                           service-that allows performance softwareB                           engineers to access a predefined list of1                           performance data items.   <     POLYCENTER Software   Enhancements have been made to theB     Installation Utility  POLYCENTER Software Installation Utility>     enhancements          product description language and theB                           POLYCENTER Software Installation Utility,                           Developer's Guide.  E                                              (continued on next page)       4     1-12 Summary of OpenVMS Version 7.3 New Features e  o      I                               Summary of OpenVMS Version 7.3 New Featuresa      B         Table 1-1 (Cont.) Summary of OpenVMS VAX and OpenVMS AlphaI         __________________Version_7.3_Software_Features__________________n  I         ______________________Programming_Features_______________________   E         Process dump tools    New dump format and tools for analyzing I         (Alpha)               process dumps allow you to do the following 8                               consistently and reliably:  G                                  Transport a dump to another system for )                                  analysistF                                  Analyze threaded and 64-bit processesD                                  Analyze images with shared linkages  I                                                  (continued on next page)                                                             I                          Summary of OpenVMS Version 7.3 New Features 1-13            /     Summary of OpenVMS Version 7.3 New Features       >     Table 1-1 (Cont.) Summary of OpenVMS VAX and OpenVMS AlphaE     __________________Version_7.3_Software_Features__________________a  E     _______________________Programming_Features______________________o  E     RMS locking           RMS includes the following enhancements for .     enhancements          OpenVMS Version 7.3:  C                           o  Global buffer read-mode bucket locking =                              (Alpha)-Improves RMS applicationaA                              performance on OpenVMS Alpha systems_D                              by minimizing locking for shared access@                              to global buffers. Does not require>                              changes to existing applications.  =                           o  No query record locking (Alpha)-xA                              Improves RMS application performancenA                              on OpenVMS Alpha systems by allowing A                              applications to read records without:@                              locking them. Avoids the processingA                              associated with record locking calls C                              to the lock manager. Can be enabled on B                              a per-record read operation or at theE                              file level. Includes the new /QUERY_LOCKhA                              qualifier and values to the SET RMS_cD                              DEFAULT command to disable query record:                              locking at the process level.  >                           o  Record Locking options to controlE                              deadlock detection-Allow RMS to directlyu@                              control deadlock detection. Options@                              correspond to existing lock request?                              flags used by the distributed lock A                              manager (through $ENQ system service $                              calls).  C     OpenVMS Registry      The OpenVMS Registry includes the abilityOC                           to specify the number of seconds that theaD                           $REGISTRY service will wait for a response3                           from the Registry Server.M  E                                              (continued on next page)m      4     1-14 Summary of OpenVMS Version 7.3 New Features h  i      I                               Summary of OpenVMS Version 7.3 New Features       B         Table 1-1 (Cont.) Summary of OpenVMS VAX and OpenVMS AlphaI         __________________Version_7.3_Software_Features__________________   I         ______________________Programming_Features_______________________a  E         System Dump Analyzer  New Alpha SDA commands, parameters, and_H         (SDA) commands,       qualifiers expand the functionality of the8         parameters, and       System Dump Analysis tool.         qualifiers (Alpha)  B         System Dump Analyzer  The new SDA Spinlock Tracing utilityF         (SDA) commands for    has commands for gathering and analyzingI         the Spinlock Tracing  spinlock performance data. The SDA Spinlock G         utility (Alpha)       Tracing utility was introduced in OpenVMS-4                               Alpha Version 7.2-1H1.  I         System services       Several system services have been added and_6                               updated for Version 7.3.  I         TCP/IP files for      TCP/IP files contain the global symbols and F         Alpha and VAX SDA     locations within the Executive Image forA                               the Alpha and VAX SDA READ command.o  F         Visual Threads        The Visual Threads diagnostic tool helpsG         Version 2.1 (Alpha)   you analyze and refine your multithreadedsC                               applications. You can use it to debugfC                               potential thread-related problems anduE                               to pinpoint bottlenecks and performance.'                               problems.   A                               Visual Threads Version 2.1 contains D                               functionality and enhancements to helpG                               you find application problems before theya$                               occur.  I         _________________________________________________________________ I         __________________Associated_Products_Features___________________   G         Availability Manager  OpenVMS Version 7.3 contains Availability I         Version 1.4           Manager Version 1.4. Soon after the releaserB                               of OpenVMS Version 7.3, AvailabilityH                               Manager Version 2.0 will become available,E                               which includes several new features and +                               enhancements.   I                                                  (continued on next page)p  I                          Summary of OpenVMS Version 7.3 New Features 1-15s           /     Summary of OpenVMS Version 7.3 New Featuresr      >     Table 1-1 (Cont.) Summary of OpenVMS VAX and OpenVMS AlphaE     __________________Version_7.3_Software_Features__________________d  E     ___________________Associated_Products_Features__________________e  B     Compaq Advanced       Compaq Advanced Server V7.3 contains new9     Server V7.3 for       functionality and enhancements.      OpenVMS (Alpha)   <     Compaq BASIC for      Compaq BASIC now supports the IEEE4     OpenVMS Alpha         floating-point data types.     enhancements  E     Compaq DECwindows     Compaq DECwindows Motif for OpenVMS Version D     Motif for OpenVMS     1.2-6 provides a full range of changes and8                           enhancements for your desktop.  E     Compaq Distributed    The following enhancements are available in =     Computing             Compaq DCE for OpenVMS Version 7.3: C     Environment (DCE)     o  The NT Lan Manager security in DCE RPC 1     for OpenVMS              is fully functional.   E                           o  New Ethernet devices may be defined with D                              the system logical DCE$IEEE_802_DEVICE.  C     DECram Version 3.0    DECram Version 3.0 contains the following =     (Alpha)               performance enhancements for Galaxy $                           customers:  C                           o  Capability to use Galaxy shared memory D                              to create an OpenVMS shared memory disk  D                           o  Faster access for data in a shared disk(                              environment  ;                           DECram Version 3.0 and supporting C                           documentation are included in the OpenVMS A                           Version 7.3 CD-ROM in the [.DECRAM_030] $                           directory.  =     Enterprise Capacity   Beginning with OpenVMS Version 7.3,w>     and Performance       the performance management tools ECP@     (ECP)                 Data Collector for OpenVMS and the ECP>                           Performance Analyzer for OpenVMS are=                           included with the operating system.t  E                                              (continued on next page)u  4     1-16 Summary of OpenVMS Version 7.3 New Features a  r      I                               Summary of OpenVMS Version 7.3 New Features-      B         Table 1-1 (Cont.) Summary of OpenVMS VAX and OpenVMS AlphaI         __________________Version_7.3_Software_Features__________________m  I         __________________Associated_Products_Features___________________u  B         Kerberos for OpenVMS  Kerberos is a network authenticationA                               protocol designed to provide strong >                               authentication for client/server>                               applications by using secret-key+                               cryptography.   D         LDAP API (Alpha)      The LDAP API is an addition to OpenVMSD                               that provides the capability to accessF                               remote directory services such as X.500,C                               ActiveDirectory or Novell's NDS using G                               the Lightweight Directory Access Protocol I                               (LDAP). Compaq provides the tools to create F                               a client or add LDAP functionality to anH                               existing application so that it can access1                               remote directories.   A         Compaq PATHWORKS for  OpenVMS Version 7.3 supports Compaq C         OpenVMS (Advanced     PATHWORKS V6.0D for OpenVMS (Advanced D         Server)               Server). Earlier versions of PATHWORKSC                               for OpenVMS servers must be upgraded.   I                                                  (continued on next page)e                                    I                          Summary of OpenVMS Version 7.3 New Features 1-17a           /     Summary of OpenVMS Version 7.3 New Features_      >     Table 1-1 (Cont.) Summary of OpenVMS VAX and OpenVMS AlphaE     __________________Version_7.3_Software_Features__________________   E     ___________________Associated_Products_Features__________________   C     Compaq Service Tools  The Compaq Services new web-based service B     and DECevent          tool functionality is known as Web-BasedA                           Enterprise Services (WEBES). The Compaq E                           System Tools CD-ROM included in the OpenVMSpD                           Version 7.3 CD-ROM package includes WEBES.C                           (WEBES includes the Compaq Crash AnalysisPE                           Tool (CCAT) and Compaq Analyze components.)n  A                           In addition to WEBES, the Compaq System B                           Tools CD-ROM includes DECevent, DSNLINK,<                           and the Revision and Configuration1                           Management (RCM) tools.   =     Compaq TCP/IP         Compaq TCP/IP Services contains new D     Services for OpenVMS  functionality and enhancements for OpenVMSE     Version_5.1___________Version_7.3._______________________________o                                                4     1-18 Summary of OpenVMS Version 7.3 New Features                         I                                                                         2 I         _________________________________________________________________   I                                        Compaq OpenVMS e-Business Features     A               This chapter provides information on the e-Business_E               technologies that are included in the Compaq OpenVMS e- H               Business Infrastructure Package with OpenVMS Alpha VersionD               7.3. This package provides key Internet and e-BusinessF               software technology that enhances the base OpenVMS AlphaH               operating system. These technologies are licensed with the-               OpenVMS Alpha operating system.n  B               The Compaq OpenVMS e-Business Infrastructure Package=               Version 1.1 contains the following software and )               accompanying documentation:f  I               o  Compaq Secure Web Server for OpenVMS Alpha Version 1.0-1 "                  (based on Apache)  4               o  Compaq COM for OpenVMS Version 1.1B  >               o  Compaq Java 2 SDK, Standard Edition v 1.2.2-3  E               o  Compaq Fast Virtual Machine (Fast VM) for the Java 2f4                  Platform on OpenVMS Alpha v 1.2.2-1  C               o  Compaq XML (Extensible Markup Language) Technology                   Version 1.0  G               o  Attunity Connect "On Platform" Package Version 3.0.0.4   D               o  Compaq Enterprise Directory Services for e-Business                  Version 5.0  >               o  Reliable Transaction Router (RTR) Version 4.0  0               o  Compaq BridgeWorks Version 1.0A  C               Refer to the Compaq OpenVMS e-Business Infrastructure G               Package Version 1.1 CD-ROM Booklet and the Compaq OpenVMS D               e-Business Infrastructure Package Version 1.1 SoftwareF               Product Description, 80.58.00 included in the e-Business4               package for more detailed information.  I                                    Compaq OpenVMS e-Business Features 2-1            &     Compaq OpenVMS e-Business Features      :           For up-to-date information on OpenVMS e-Business8           technologies, refer to the following web site:  ;           http://www.openvms.compaq.com/business/index.html   @           The following sections briefly describe the e-BusinessA           software and provide pointers and web sites for further >           information. Refer to the  Compaq OpenVMS e-BusinessA           Infrastructure Package SPD for technology descriptions, A           other software requirements, and licensing information.lE           The technology on the e-Business CD-ROM has been tested and_?           qualified with OpenVMS Alpha Version 7.2-1 and later._  2     2.1 Compaq Secure Web Server for OpenVMS Alpha  D           Compaq Secure Web Server for OpenVMS Alpha (CSWS) is basedC           on the popular Apache Web Server from the Apache SoftwareeA           Foundation. Building on the source code from the ApachepE           Software Foundation (http://www.apache.org), Compaq OpenVMS C           engineering has incorporated and fully integrated OpenSSLaD           with mod_ssl, the most popular open-source implementations           of SSL.r  E           The product is also available to download from the CSWS web.           site:e  M           http://www.openvms.compaq.com/openvms/products/ips/apache/csws.html        2.2 Compaq COM for OpenVMS  E           Component Object Model (COM) is a technology from Microsoft >           that allows developers to create distributed network>           objects. Digital Equipment Corporation and MicrosoftE           jointly developed the COM specification. The Compaq COM for D           OpenVMS kit included on the e-Business CD-ROM provides allC           the code and documentation you need to install Compaq COM E           for OpenVMS on your system and to develop COM applications.   >     2.3 Compaq Java 2 SDK, Standard Edition, for OpenVMS Alpha  :           The Java Software Development Kit (SDK) provides<           an environment in which to develop and deploy Java>           applications on OpenVMS Alpha. Java applications can>           be written once and run on any operating system thatB           implements the Java run-time environment, which consists6           primarily of the Java Virtual Machine (JVM).  *     2-2 Compaq OpenVMS e-Business Features O  E      I                                        Compaq OpenVMS e-Business FeaturesYI                2.3 Compaq Java 2 SDK, Standard Edition, for OpenVMS Alphac    H               The Java 2 SDK, Standard Edition, for OpenVMS Alpha kit isI               included on the e-Business CD-ROM, or you can download this E               kit from the Compaq Java home page at the following web-               address:  <               http://www.compaq.com/java/download/index.html  I         2.4 Compaq Fast Virtual Machine (Fast VM) for the Java 2 Platformn  E               The Compaq Fast VM for Java 2 is new Just-In-Time (JIT)eG               compiler technology designed to provide optimal Java run-_H               time performance on OpenVMS Alpha systems. The Fast VM forG               Java 2 offers significant performance advantages over the G               Classic JIT provided with the Compaq Java 2 SDK, Standard                Edition.  E               The Fast VM for OpenVMS Alpha kit is included on the e-hI               Business CD-ROM, or you can also download this kit from the A               Compaq Java home page at the following web address:   <               http://www.compaq.com/java/download/index.html  !         2.5 Compaq XML Technology   E               The following components are provided on the e-Business H               CD-ROM using open source software from the Apache Software               Foundation:   ,               o  XML parsers in Java and C++  <               o  XSLT style sheet processors in Java and C++  I               This technology provides applications the ability to parse,_F               generate, manipulate, validate, and transform Extensible7               Markup Language (XML) documents and data.f  2         2.6 Attunity Connect "On Platform" Package  A               Attunity Connect is object-oriented middleware thataF               facilitates the development of applications that access,E               integrate, and update data from multiple, heterogeneoushH               sources across a wide range of operating system platforms.?               With Attunity Connect, you can extend the life ofrC               your existing data and applications and preserve your.)               significant IT investments.e  I                                    Compaq OpenVMS e-Business Features 2-3  f  a      &     Compaq OpenVMS e-Business Features.     2.6 Attunity Connect "On Platform" Package    A           The e-Business CD-ROM contains the Attunity Connect "On D           Platform" Package for OpenVMS Alpha. You can also download=           the Attunity Connect "On Platform" Package from the %           following OpenVMS web site:d  F           http://www.openvms.compaq.com/openvms/products/ips/attunity/  ;     2.7 Compaq Enterprise Directory Services for e-BusinessY  E           Compaq OpenVMS Enterprise Directory for e-Business combinesc=           the best of both industry standard LDAPv3 and X.500 B           capabilities, and delivers robust and scalable directoryC           services across intranets, extranets, and the Internet to B           customers, suppliers and partners. Lightweight DirectoryB           Access Protocol (LDAP) support allows access by a myriad?           of LDAP-based clients, user agents, and applications. @           The X.500 support brings high performance, resilience,C           advanced access controls, and easy replication across the            enterprise.   >           For further information, refer to the Compaq OpenVMS>           Enterprise Directory for e-Business Software Product?           Description (SPD 40.77.xx) included on the e-Business C           CD-ROM in the Enterprise Directory Services documentation            directory.  )     2.8 Reliable Transaction Router (RTR)   =           Reliable Transaction Router (RTR) is fault tolerant E           transactional messaging middleware used to implement large,SB           distributed applications using client/server technology.C           Reliable Transaction Router enables computing enterprises.E           to deploy distributed applications on OpenVMS Alpha and VAX_           systems.  >           Refer to the Reliable Transaction Router for OpenVMSA           Software Product Description (SPD 51.04.xx) included onlB           the e-Business CD-ROM for additional information; or you)           can access the RTR web site at:f  $           http://www.compaq.com/rtr/        *     2-4 Compaq OpenVMS e-Business Features A  o      I                                        Compaq OpenVMS e-Business FeaturesiI                                                    2.9 Compaq BridgeWorks              2.9 Compaq BridgeWorks  I               Compaq BridgeWorks is a distributed application developmenty?               and deployment tool for OpenVMS 3GL applications. C               BridgeWorks consists of a GUI development tool on the/H               Windows NT desktop, a server manager component on OpenVMS,H               and extensive online help. BridgeWorks provides developersI               with an easy means to create distributed applications usingrD               OpenVMS as the enterprise server and Windows NT as the"               departmental server.  F               For more information on Compaq BridgeWorks, refer to theG               Compaq OpenVMS e-Business Infrastructure Package Softwarep"               Product Description.                                                              I                                    Compaq OpenVMS e-Business Features 2-5s r  n                    I                                                                         3 I         _________________________________________________________________   I                                                     General User Features_    D               This chapter provides new features information for all;               users of the Compaq OpenVMS Operating System.p  .         3.1 DCL Commands and Lexical Functions  B               This section describes new and changed DCL commands,H               qualifiers, and lexical functions for OpenVMS Version 7.3.F               The following table contains a summary of these changes.  H               For more information, refer to the OpenVMS DCL Dictionary.  I               ___________________________________________________________ I               DCL_Command________Documentation_Update____________________p  C               ANALYZE/IMAGE      A new qualifier, /SELECT, has beenV>                                  added, along with an example.  C               ANALYZE/OBJECT     A new qualifier, /SELECT, has beeno>                                  added, along with an example.  F               ANALYZE/PROCESS    A new qualifier, /[NO]IMAGE_PATH, hasC                                  been added, along with an example.u  I               DELETE             A new qualifier, /BITMAP, has been added 9                                  to support Write Bitmap.   H               DELETE/INTRUSION   A new qualifier, /NODE, has been added,B                                  along with an example, to support8                                  Cluster-wide Intrusion.  E               DIRECTORY          A new qualifier, /CACHING_ATTRIBUTE,tH                                  has been added to support Extended File-                                  Cache (XFC).n  I               DISMOUNT           A new qualifier, /POLICY, has been addedM9                                  to support Write Bitmap.   E                                  A new qualifier, /FORCE_REMOVAL, has H                                  been added to support Volume Shadowing.  I                                                 General User Features 3-1r c  n           General User Features *     3.1 DCL Commands and Lexical Functions  E           ___________________________________________________________ E           DCL_Command________Documentation_Update____________________   @           DUMP               A new qualifier, /PROCESS, has been#                              added.   @           INITIALIZE         The INITIALIZE description has beenA                              updated to include information about 7                              Extended File Cache (XFC).   E                              A new qualifier, /SHADOW, has been addedi9                              to support Volume Shadowing.f  D           MOUNT              The MOUNT command has been moved to theD                              OpenVMS DCL Dictionary from the OpenVMSB                              System Management Utilities Reference$                              Manual.  C                              The MOUNT description has been updated B                              to include information about Extended.                              File Cache (XFC).  E                              A new qualifier, /POLICY, has been addedS5                              to support Write Bitmap.F  B           SET AUDIT          A new keyword, SERVER, has been addedD                              under the LOGFAILURE, LOGIN, and LOGOUT&                              keywords.  D                              New text has been added to the /NEW_LOG'                              qualifier.c  C           SET CACHE/RESET    This new DCL command has been added tot?                              support Extended File Cache (XFC).P  C           SET DEVICE         The following new qualifiers have been ?                              added to support Volume Shadowing: =                              /FORCE_REMOVAL, /MEMBER_TIMEOUT, B                              /MVTIMEOUT, /READ_COST, /SITE, /COPY_9                              SOURCE, /ABORT_VIRTUAL_UNIT.e  B           SET DISPLAY        The logical, DECW$SETDISPLAY_DEFAULT_>                              TRANSPORT, has been added to this%                              command.   E           SET FILE           Two new qualifiers, /SHARE and /CACHING_ <                              ATTRIBUTE, have been added. TheB                              /CACHING_ATTRIBUTE qualifier supports7                              Extended File Cache (XFC).        3-2 General User Featuresr r  r      I                                                     General User FeaturesrI                                    3.1 DCL Commands and Lexical Functionsx  I               ___________________________________________________________yI               DCL_Command________Documentation_Update____________________e  D               SET PROCESS        The functionality of the qualifier,H                                  /[NO]DUMP, has been extended to includeE                                  other processes. The /DUMP qualifiersH                                  also has a new option, NOW, to initiateF                                  an immediate dump of another process.  G               SET RMS_DEFAULT    Two new qualifiers, /CONTENTION_POLICYSI                                  and /QUERY_LOCK have been added, and theh<                                  examples have been updated.  @               SET SERVER         Added support for the Registry,G                                  including new qualifiers and examples.a  D               SET VOLUME         A new qualifier, /[NO]WRITETHROUGH,H                                  has been added to support Extended File-                                  Cache (XFC).e  F                                  The /HIGHWATER qualifier is valid forC                                  Files-11 On-Disk Structure Level 5 '                                  disks.n  G               SHOW CPU           The following new qualifiers have been_D                                  added: /EXACT, /HIGHLIGHT, /OUTPUT,;                                  /PAGE, /SEARCH, and /WRAP.   I               SHOW DEVICES       A new qualifier, /BITMAP, has been added D                                  to support Write Bitmap, along with*                                  examples.  E                                  The /FULL qualifier now displays the F                                  worldwide identifier (WWID) for Fibre6                                  Channel tape devices.  H               SHOW INTRUSION     A new qualifier, /NODE, has been added,B                                  along with an example, to support8                                  Cluster-wide Intrusion.  B               SHOW LICENSE       The qualifier, /CHARGE_TABLE, hasG                                  been added as a synonym for the /UNIT_ 8                                  REQUIREMENTS qualifier.  G               SHOW MEMORY        The /CACHE qualifier and examples have E                                  been updated for Extended File CacheW'                                  (XFC).   D                                  The /FILES and /FULL qualifiers andE                                  examples have been updated for Largei,                                  Page Files.  I                                                 General User Features 3-3V A  a           General User Featuresm*     3.1 DCL Commands and Lexical Functions  E           ___________________________________________________________OE           DCL_Command________Documentation_Update____________________i  :           SHOW RMS_DEFAULT   The example has been updated.  C           SHOW SERVER        This command has been added in support -                              of the Registry..  B           UNLOCK             This command is now obsolete. Use theE           ___________________SET_FILE/UNLOCK_command.________________p  E           ___________________________________________________________aE           DCL_Lexical________Documentation_Update____________________e  >           F$GETDVI           The item codes, MT3_DENSITY, MT3_A                              SUPPORTED, and WWID have been added, @                              and the MOUNTCNT item code has been%                              updated.n  C                              The item codes, DEVTYPE, DEVCLASS, and:D                              DEVICE_TYPE_NAME have been updated, andB                              an example has been added. Tables 1-77                              and 1-8 have been removed.t  C           F$GETQUI           The JOB_STATUS item code list has been %                              updated.t  ?           F$GETJPI           The MULTITHREAD item code has beend#                              added.h  E           F$GETSYI           The MULTITHREAD and DECNET_VERSION itemslE           ___________________have_been_added.________________________c  3     3.2 New Online Help Topics for Utility Routinesc  E           As of Version 7.3, online help now includes all the OpenVMSr@           utility routines that are described in OpenVMS Utility3           Routines Manual, including the following:                 ACL_Editort              BACKUP_APIa              CLI_Routinese              CONV$_Routinesl              CQUAL_Routines               DCX_Routinesp              DECTPUp              EDT_RoutinesS              FDL_Routinesc              LBR_Routinesl       3-4 General User Features  e         I                                                     General User Features I                           3.2 New Online Help Topics for Utility Routinesi                      LDAP_Routines                  LGI_Routines                   MAIL_Routines                  NCS_Routinest                  PSM_Routines                   SMB_Routines                   SOR_Routineso  F               For OpenVMS Version 7.3, several online help topics have'               been renamed, as follows:n  I               ___________________________________________________________oI               Old_Topic_Name___New_Topic_Name____________________________e  -               BACKUP           BACKUP_Commandm  (               FDL              FDL_Files  +               MAIL             MAIL_Command   I               NCS______________NCS_Command_______________________________n  %         3.3 MIME Utility Enhancementst  G               The following new commands and qualifiers have been added I               to the Multipurpose Internet Mail Extension (MIME) utility:e  I               ___________________________________________________________aI               Command__________Description_______________________________a  C               ADD/BINARY       Sets the Content-Type to applicationaB                                /octet-stream and Content-Transfer-E                                Encoding to Base64. This format can beeI                                used to represent an arbitrary binary data &                                stream.  B               SHOW option      Displays information about the MIMEI                                environment. Possible options are CONTENT_nI               _________________TYPE,_FILE_TYPES,_and_VERSION.____________d  F               For more information about the MIME utility commands and=               qualifiers, refer to the OpenVMS User's Manual.e      I                                                 General User Features 3-5q v              General User Featurest     3.4 WWPPS Utility (Alpha)V         3.4 WWPPS Utility (Alpha)   A           The World-Wide PostScript Printing Subsystem (WWPPS) ishC           a utility that allows you to print a PostScript file withgC           various language characters on any PostScript printer. BynC           embedding font data within the PostScript printable file,oC           you can print the language characters even if the printerR;           does not have the local language character fonts.   B           For detailed instructions about using the WWPPS utility,-           refer to the OpenVMS User's Manual.i  9           For more information about the installation andiC           administration of the WWPPS utility, refer to the OpenVMSa"           System Manager's Manual.                                                                 3-6 General User FeaturesP f  "                    I                                                                         4aI         _________________________________________________________________r  I                                                System Management Featureso    C               This chapter provides information about new features,t<               changes, and enhancements for system managers.  A         4.1 OpenVMS Support for New AlphaServer GS Series Systemsc  E               OpenVMS Alpha Version 7.3 provides support for Compaq's B               AlphaServer GS80, GS160 and GS320 systems, which wasB               introduced in OpenVMS Version 7.2-1H1, and includes:  I               o  OpenVMS support for hard and soft partitions (Galaxy) ont4                  AlphaServer GS160 and GS320 systems  C               o  OpenVMS Resource Affinity Domain (RAD) support for                   applicationsd  #               o  CPU Online Replace.  :         4.1.1 OpenVMS Support for Hard and Soft Partitions  E               Hard partitioning is a physical separation of computingsC               resources by hardware-enforced access barriers. It issA               impossible to read or write across a hard partitionsA               boundary. There is no resource sharing between hard,               partitions.t  F               Soft partitioning is a separation of computing resourcesD               by software-controlled access barriers. Read and writeF               access across a soft partition boundary is controlled byG               the operating system. OpenVMS Galaxy is an implementationc#               of soft partitioning.i  A               The way customers choose to partition their systemsmE               depends on their computing environments and applicationeA               requirements. For more information about using hardcG               partitions and OpenVMS Galaxy, refer to the OpenVMS Alphar,               Partitioning and Galaxy Guide.  I                                            System Management Features 4-1R e  R           System Management Features=     4.1 OpenVMS Support for New AlphaServer GS Series Systems     <     4.1.2 OpenVMS Resource Affinity Domain (RAD) Support for           Applications  ?           OpenVMS Alpha Version 7.3 provides non-uniform memoryiC           awareness (NUMA) in OpenVMS memory management and process =           scheduling, which was introduced in OpenVMS Version ?           7.2-1H1. This capability provides application support >           for resource affinity domains (RADs), to ensure that>           applications running on a single instance of OpenVMS@           on multiple quad building blocks (QBBs) can execute asC           efficiently as possible in a NUMA environment. A RAD is a B           set of hardware components (CPU, memory, IO) with common@           access characteristics, and corresponds to a QBB in an,           AlphaServer GS160 or GS320 system.  B           For more information about using the OpenVMS RAD support>           for application features, refer to the OpenVMS Alpha(           Partitioning and Galaxy Guide.  0     4.1.3 OpenVMS Support for CPU Online Replace  C           With OpenVMS Alpha Version 7.3, you can replace secondaryrD           CPUs on a running system without rebooting, which providesC           increased system maintainability and serviceability. This E           feature is supported only on AlphaServer GS160/320 systems. A           Note that replacing the primary CPU requires rebooting.   >           To use this feature, you must first download console<           firmware Version 5.9B from the following location:  8           http://ftp.digital.com/pub/DEC/Alpha/firmware/  E           After you upgrade the console with the latest firmware, you B           can then use the following DCL commands to replace a CPU           without rebooting:  D           1. Direct OpenVMS to stop scheduling processes on the CPU:                $ STOP/CPU n   8              (n is the number of the CPU to be stopped.)  '           2. Power off the running CPU:a  "              $ SET CPU/POWER=OFF n  C           3. When the light on the CPU module has turned from greenx@              to amber, physically remove the CPU module from the+              system. Then put in a new CPU.   "     4-2 System Management Features    .      I                                                System Management Features I                 4.1 OpenVMS Support for New AlphaServer GS Series Systems     "               4. Power on the CPU:  &                  $ SET CPU/POWER=ON  n  E               OpenVMS automatically adds the CPU to the active set of                processors.n  C               Note that the Galaxy Configuration Utility (GCU) alsod'               supports this capability.   6         4.2 Automatic Setting of Daylight Savings Time  G               System parameter AUTO_DLIGHT_SAV controls whether OpenVMS H               will automatically change system time to and from DaylightG               Savings Time when appropriate. A value of 1 tells OpenVMSEG               to automatically make the change. The default is 0 (off). )               This is a static parameter.   F               However, if you have a time service (such as DTSS), thatI               time service continues to control time changes, and OpenVMS B               does not interfere. Do not enable automatic daylight<               savings time if you have another time service.  I               For more information, refer to the OpenVMS System Manager's                Manual.   .         4.3 Class Scheduler for CPU Scheduling  C               With OpenVMS Version 7.3, there is a new SYSMAN-based G               interface for class scheduling. This new class scheduler,wF               implemented on both VAX and Alpha systems, gives you theI               ability to designate the amount of CPU time that a system's D               users may receive by placing the users into schedulingI               classes. Each class is assigned a percentage of the overall_E               system's CPU time. As the system runs, the combined setnF               of users in a class are limited to the percentage of CPUH               execution time allocated to their class. The users may getH               some additional CPU time if /windfall is enabled for theirH               scheduling class. Enabling the /windfall allows the systemF               to give a small amount of CPU time to a scheduling classH               when a CPU is idle and the scheduling class' allotted time                has been depleted.  ?               To invoke the class scheduler, you use the SYSMANeE               interface. SYSMAN allows you to create, delete, modify,mH               suspend, resume, and display scheduling classes. Table 4-1  I                                            System Management Features 4-3T M  T           System Management Features*     4.3 Class Scheduler for CPU Scheduling    @           shows the SYSMAN command, CLASS_SCHEDULE, and its sub-           commands.   E           Table_4-1_SYSMAN_command:_class_schedule___________________   E           Sub-command___Meaning______________________________________d  6           ADD           Creates a new scheduling class  2           DELETE        Deletes a scheduling class  D           MODIFY        Modifies the characteristics of a scheduling                         class   A           SHOW          Shows the characteristics of a scheduling                          classt  ?           SUSPEND       Suspends temporarily a scheduling classP  E           RESUME________Resumes_a_scheduling_class___________________   >           By implementing the class scheduler using the SYSMAN@           interface, you create a permanent database that allowsC           OpenVMS to class schedule processes automatically after a D           system has been booted and rebooted. This database residesC           on the system disk in SYS$SYSTEM:VMS$CLASS_SCHEDULE.DATA. B           SYSMAN creates this file as an RMS indexed file when theB           first scheduling class is created by the SYSMAN command,           CLASS_SCHEDULE ADD.   @           In a cluster environment, SYSMAN creates this databaseC           file in the SYS$COMMON root of the [SYSEXE] directory. As A           a result, the database file is shared among all clusterrA           members. By using SYSMAN's SET ENVIRONMENT command, you C           can define scheduling classes either on a cluster-wide or3           per-node basis.   ?           If desired, a system manager (or application manager)_?           uses the permanent class scheduler to place a processiB           into a scheduling class at process creation time. When aB           new process is created, Loginout determines whether this>           process belongs to a scheduling class. Given process?           information from the SYSUAF file, Loginout then class ?           schedules the process if Loginout determines that the 0           process belongs to a scheduling class.  "     4-4 System Management Features A         I                                                System Management Features/I                                    4.3 Class Scheduler for CPU Schedulingp    E               By using the SYSMAN utility to perform class schedulingrG               operations instead of $SCHED system service, you gain the !               following benefits:   I               o  You need not modify individual program images to control B                  class scheduling. You can add, delete, and modifyD                  scheduling classifications from the SYSMAN utility.  ?               o  You can use SYSMAN to create a permanent classlF                  scheduling database file which allows processes to beD                  class scheduled at process creation time and allowsF                  class definitions to be preserved in case of a system                  reboot.  C               For more detailed information, refer to the followingS               manuals:  >                  OpenVMS Programming Concepts Manual, Volume I,                  OpenVMS DCL Dictionary: N-ZC                  OpenVMS System Services Reference Manual: A-GETUAIU  .         4.4 Dedicated CPU Lock Manager (Alpha)  B               The Dedicated CPU Lock Manager is a new feature thatG               improves performance on large SMP systems that have heavy C               lock manager activity. The feature dedicates a CPU to 1               performing lock manager operations.   F               A dedicated CPU has the following advantages for overall,               system performance as follows:  4               o  Reduces the amount of MP_SYNCH time  4               o  Provides good CPU cache utilization  9         4.4.1 Implementing the Dedicated CPU Lock Manager   I               For the Dedicated CPU Lock Manager to be effective, systemsoF               must have a high CPU count and a high amount of MP_SYNCHF               due to the lock manager. Use the MONITOR utility and theI               MONITOR MODE command to see the amount of MP_SYNCH. If your F               system has more than five CPUs and if MP_SYNCH is higherI               than 200%, your system may be able to take advantage of theaG               Dedicated CPU Lock Manager. You can also use the spinlock_E               trace feature in the System Dump Analyzer (SDA) to helpnG               determine if the lock manager is contributing to the highD&               amount of MP_SYNCH time.  I                                            System Management Features 4-5                 System Management Features*     4.4 Dedicated CPU Lock Manager (Alpha)    D           The Dedicated CPU Lock Manager is implemented by a LCKMGR_D           SERVER process. This process runs at priority 63. When theD           Dedicated CPU Lock Manager is turned on, this process runsB           in a compute bound loop looking for lock manager work toD           perform. Because this process polls for work, it is always@           computable; and with a priority of 63 the process will<           never give up the CPU, thus consuming a whole CPU.  E           If the Dedicated CPU Lock Manager is running when a program ?           calls either the $ENQ or $DEQ system services, a lockdE           manager request is placed on a work queue for the Dedicated D           CPU Lock Manager. While a process waits for a lock requestE           to be processed, the process spins in kernel mode at IPL 2. C           After the dedicated CPU processes the request, the statusE<           for the system service is returned to the process.  E           The Dedicated CPU Lock Manager is dynamic and can be turned D           off if there are no perceived benefits. When the DedicatedC           CPU Lock Manager is turned off, the LCKMGR_SERVER process ?           is in a HIB (hibernate) state. The process may not be            deleted once started.e  1     4.4.2 Enabling the Dedicated CPU Lock Manager,  D           To use the Dedicated CPU Lock Manager, set the LCKMGR_MODED           system parameter. Note the following about the LCKMGR_MODE           system parameter:   E           o  Zero (0) indicates the Dedicated CPU Lock Manager is offS              (the default).   C           o  A number greater than zero (0) indicates the number of E              CPUs that should be active before the Dedicated CPU Locka"              Manager is turned on.  ?           Setting LCKMGR_MODE to a number greater than zero (0) D           triggers the creation of a detached process called LCKMGR_B           SERVER. The process is created, and it starts running if@           the number of active CPUs equals the number set by the'           LCKMGR_MODE system parameter..  B           In addition, if the number of active CPUs should ever beC           reduced below the required threshold by either a STOP/CPU_C           command or by CPU reassignment in a Galaxy configuration,_@           the Dedicated CPU Lock Manager automatically turns offD           within one second, and the LCKMGR_SERVER process goes into  "     4-6 System Management Features    C      I                                                System Management FeaturesiI                                    4.4 Dedicated CPU Lock Manager (Alpha)r    E               a hibernate state. If the CPU is restarted, the LCKMGR_o6               SERVER process again resumes operations.  @         4.4.3 Using the Dedicated CPU Lock Manager With Affinity  C               The LCKMGR_SERVER process uses the affinity mechanismID               to set the process to the lowest CPU ID other than theG               primary. You can change this by indicating another CPU ID G               with the LCKMGR_CPUID system parameter. The Dedicated CPU H               Lock Manager then attempts to use this CPU. If this CPU isI               not available, it reverts back to the lowest CPU other thanh               the primary.  H               The following shows how to dynamically change the CPU used+               by the LCKMGR_SERVER process:_  $               $RUN SYS$SYSTEM:SYSGEN               SYSGEN>USE ACTIVEm'               SYSGEN>SET LCKMGR_CPUID 2 !               SYSGEN>WRITE ACTIVE                SYSGEN>EXIT   B               This change applies to the currently running system.D               A reboot reverts back to the lowest CPU other than theH               primary. To permanently change the CPU used by the LCKMGR_D               SERVER process, set LCKMGR_CPUID in your MODPARAMS.DAT               file.   F               To verify the CPU dedicated to the lock manager, use the.               SHOW SYSTEM command, as follows:  1               $ SHOW SYSTEM/PROCESS=LCKMGR_SERVERaJ    OpenVMS V7.3 on node JYGAL  24-OCT-2000 10:10:11.31  Uptime  3 20:16:56N    Pid    Process Name    State  Pri      I/O       CPU       Page flts  PagesP    4CE0021C LCKMGR_SERVER   CUR  2  63        9   3 20:15:47.78        70     84  F               Note that the State field shows the process is currently               running on CPU 2.   G               Compaq highly recommends that a process not be given hard I               affinity to the CPU used by the Dedicated CPU Lock Manager. H               With hard affinity when such a process becomes computable,F               it cannot obtain any CPU time, because the LCKMGR_SERVERB               process is running at the highest possible real-timeE               priority of 63. However, the LCKMGR_SERVER detects once G               per second if there are any computable processes that arerI               set by the affinity mechanism to the dedicated lock manager   I                                            System Management Features 4-7                 System Management Features*     4.4 Dedicated CPU Lock Manager (Alpha)    C           CPU. If so, the LCKMGR_SERVER switches to a different CPUt=           for one second to allow the waiting process to run.p  E     4.4.4 Using the Dedicated CPU Lock Manager with Fast Path Devicesi  D           OpenVMS Version 7.3 also introduces Fast Path for SCSI andC           Fibre Channel Controllers along with the existing supportaD           of CIPCA adapters. The Dedicated CPU Lock Manager supports>           both the LCKMGR_SERVER process and Fast Path devices@           on the same CPU. However, this may not produce optimal           performance.  A           By default, the LCKMGR_SERVER process runs on the firste>           available nonprimary CPU. Compaq recommends that theA           CPU used by the LCKMGR_SERVER process not have any FastfA           Path devices. This can be accomplished in either of thee           following ways:b  A           o  You can eliminate the first available nonprimary CPU ?              as an available Fast Path CPU. To do so, clear theiC              bit associated with the CPU ID from the IO_PREFER_CPUSm              system parameter.  C              For example, let's say your system has eight CPUs withoC              CPU IDs from zero to seven and four SCSI adapters thateC              will use Fast Path. Clearing bit 1 from IO_PREFER_CPUsaA              would result in the four SCSI devices being bound toeA              CPUs 2, 3, 4, and 5. CPU 1, which is the default CPUtC              the lock manager will use, will not have any Fast Path               devices.e  B           o  You can set the LCKMGR_CPUID system parameter to tellB              the LCKMGR_SERVER process to use a CPU other than the@              default. For the above example, setting this systemE              parameter to 7 would result in the LCKMGR_SERVER process E              running on CPU 7. The Fast Path devices would by default -              be bound to CPUs 1, 2, 3, and 4.t  D     4.4.5 Using the Dedicated CPU Lock Manager on the AlphaServer GS           Series Systems  A           The new AlphaServer GS Series Systems (GS80, GS160, andnA           the GS320) have NUMA memory characteristics. When usingnE           the Dedicated CPU Lock Manager on one of these systems, the D           best performance is obtained by utilizing a CPU and memory9           from within a single Quad Building Block (QBB).S  "     4-8 System Management Features e  r      I                                                System Management Features.I                                    4.4 Dedicated CPU Lock Manager (Alpha)V    E               For OpenVMS Version 7.3, the Dedicated CPU Lock ManagerwD               does not yet have the ability to decide from where QBBG               memory should be allocated. However, there is a method toAH               preallocate lock manager memory from the low QBB. This canF               be done with the LOCKIDTBL system parameter. This systemH               parameter indicates the initial size of the Lock ID Table,H               along with the initial amount of memory to preallocate for+               lock manager data structures.l  E               To preallocate the proper amount of memory, this systemoD               parameter should be set to the highest number of locksD               plus resources on the system. The command MONITOR LOCKD               can provide this information. If MONITOR indicates theI               system has 100,000 locks and 50,000 resources, then settingFB               LOCKIDTBL to the sum of these two values will ensureB               that enough memory is initially allocated. Adding inF               some additional overhead may also be beneficial. Setting=               LOCKIDTBL to 200,000 thus might be appropriate.   D               If necessary, use the LCKMGR_CPUID system parameter toI               ensure that the LCKMGR_SERVER runs on a CPU in the low QBB.o  B         4.5 OpenVMS Enterprise Directory for e-Business (Alpha)[1]  H               OpenVMS Enterprise Directory for e-Business is a massivelyI               scalable directory service, providing both X.500 and LDAPv3aE               services on OpenVMS Alpha with no separate license fee. F               OpenVMS Enterprise Directory for e-Business provides the               following:  C               o  Large percentage of the Fortune 500 already deployfB                  Compaq X.500 Directory Service (the forerunner of=                  OpenVMS Enterprise Directory for e-Business)n  7               o  World's first 64-bit directory servicec  E               o  Seamlessly combines the scalability and distributions:                  features of X.500 with the popularity and3                  interoperability offered by LDAPv3i  I               o  Inherent replication/shadowing features may be exploited *                  to guarantee 100% up-time  "               ____________________F               [1]   On OpenVMS VAX a similar service, but without LDAPG                     support and with more limited performance, is still I                     available with Compaq X.500 Directory Service Versionn                     3.1.    I                                            System Management Features 4-9  b  t           System Management Features;     4.5 OpenVMS Enterprise Directory for e-Business (Alpha)t    E           o  Systems distributed around the world can be managed frome              a single point   =           o  Ability to store all types of authentication andnC              security certificates across the enterprise accessibleC              from any location  '           o  Highly configurable schemat  E           o  In combination with AlphaServer technology and in-memoryrA              database delivers market leading performance and low               initiation time  D           For more detailed information, refer to the Compaq OpenVMSD           e-Business Infrastructure CD-ROM package which is included0           in the OpenVMS Version 7.3 CD-ROM kit.  #     4.6 Extended File Cache (Alpha)   >           The Extended File Cache (XFC) is a new virtual blockA           data cache provided with OpenVMS Alpha Version 7.3 as ae0           replacement for the Virtual I/O Cache.  E           Similar to the Virtual I/O Cache, the XFC is a clusterwide,tB           file system data cache. Both file system data caches are7           compatible and coexist in an OpenVMS Cluster.   =           The XFC improves I/O performance with the followinguE           features that are not available with the Virtual I/O Cache:_             o  Read-ahead caching   ,           o  Automatic resizing of the cache  &           o  Larger maximum cache size  ?           o  No limit on the number of closed files that can beo              cached   D           o  Control over the maximum size of I/O that can be cached  C           o  Control over whether cache memory is static or dynamicP  E           For more information, refer to the chapter on Managing Data_B           Caches in the OpenVMS System Manager's Manual, Volume 2:2           Tuning, Monitoring, and Complex Systems.  #     4-10 System Management Featuresn a  a      I                                                System Management Features I               4.7 /ARB_SUPPORT Qualifier Added to INSTALL Utility (Alpha)     C         4.7 /ARB_SUPPORT Qualifier Added to INSTALL Utility (Alpha)   G               Beginning with OpenVMS Alpha Version 7.3, you can use thesF               /ARB_SUPPORT qualifier with the ADD, CREATE, and REPLACEH               commands in the INSTALL utility. The ARB_SUPPORT qualifierI               provides Access Rights Block (ARB) support to products that G               have not yet been updated the per-thread security Persona 2               Security Block (PSB) data structure.  C               This new qualifier is included in the INSTALL utility-F               documentation in the OpenVMS System Management Utilities               Reference Manual.   (         4.8 MONITOR Utility New Features  D               The MONITOR utility has two new class names, RLOCK and2               TIMER, which you can use as follows:  G               o  MONITOR RLOCK: the dynamic lock remastering statistics                   of a node  B               o  MONITOR TIMER: Timer Queue Entry (TQE) statistics  D               These enhancements are discussed in more detail in theH               MONITOR section of the OpenVMS System Management UtilitiesI               Reference Manual and in the appendix that discusses MONITORt,               record formats in that manual.  I               Also in the MONITOR utility, the display screens of MONITORAD               CLUSTER, PROCESSES/TOPCPU, and SYSTEM now have new andI               higher scale values. Refer to the OpenVMS System ManagementsC               Utilities Reference Manual: M-Z for more information.t  #         4.9 OpenVMS Cluster Systemsd  E               The following OpenVMS Cluster features are discussed ini               this section:l  0               o  Clusterwide intrusion detection  =               o  Fast Path for SCSI and Fibre Channel (Alpha)h  I               o  Floppy disks served in an OpenVMS Cluster system (Alpha)i  2               o  New Fibre Channel support (Alpha)  7               o  Switched LAN as a cluster interconnecto  0               o  Warranted and migration support  I                                           System Management Features 4-11o m  g           System Management Features     4.9 OpenVMS Cluster SystemsZ    )     4.9.1 Clusterwide Intrusion Detectionr  <           OpenVMS Version 7.3 includes clusterwide intrusion@           detection, which extends protection against attacks of>           all types throughout the cluster. Intrusion data and@           information from each system are integrated to protectA           the cluster as a whole. Member systems running versionspA           of OpenVMS prior to Version 7.3 and member systems thatt@           disable this feature are protected individually and doA           not participate in the clusterwide sharing of intrusion            information.  @           You can modify the SECURITY_POLICY system parameter onA           the member systems in your cluster to maintain either aeC           local or a clusterwide intrusion database of unauthorizedh9           attempts and the state of any intrusion events.e  E           If bit 7 in SECURITY_POLICY is cleared, all cluster members ?           are made aware if a system is under attack or has anyrB           intrusion events recorded. Events recorded on one systemE           can cause another system in the cluster to take restrictiveaB           action. (For example, the person attempting to log in is@           monitored more closely and limited to a certain numberB           of login retries within a limited period of time. Once a@           person exceeds either the retry or time limitation, heC           or she cannot log in.) The default for bit 7 in SECURITY_y           POLICY is clear.  >           For more information on the system services $DELETE_@           INTRUSION, $SCAN_INTRUSION, and $SHOW_INTRUSION, refer:           to the OpenVMS System Services Reference Manual.  D           For more information on the DCL commands DELETE/INTRUSION_=           RECORD and SHOW INTRUSION, refer to the OpenVMS DCL            Dictionary.t  B           For more information on clusterwide intrusion detection,8           refer to the OpenVMS Guide to System Security.  6     4.9.2 Fast Path for SCSI and Fibre Channel (Alpha)  D           Fast Path for SCSI and Fibre Channel (FC) is a new feature=           with OpenVMS Version 7.3. This feature improves theaB           performance of Symmetric Multi-Processing (SMP) machines-           that use certain SCSI ports, or FC.   #     4-12 System Management Features, e  o      I                                                System Management Features I                                               4.9 OpenVMS Cluster Systemsh    I               In previous versions of OpenVMS, SCSI and FC I/O completionrH               was processed solely by the primary CPU. When Fast Path isI               enabled, the I/O completion processing can occur on all the H               processors in the SMP system. This substantially increasesI               the potential I/O throughput on an SMP system, and helps to >               prevent the primary CPU from becoming saturated.  A               See Section 4.12.2 for information about the SYSGENGE               parameter, FAST_PATH_PORTS, that has been introduced to 0               control Fast Path for SCSI and FC.  F         4.9.3 Floppy Disks Served in an OpenVMS Cluster System (Alpha)  D               Until this release, MSCP was limited to serving disks.I               Beginning with OpenVMS Version 7.3, serving floppy disks inCF               an OpenVMS Cluster system is supported, enabled by MSCP.  I               For floppy disks to be served in an OpenVMS Cluster system,cF               floppy disk names must conform to the naming conventionsI               for port allocation class names. For more information about F               device naming with port allocation classes, refer to the-               OpenVMS Cluster Systems manual.r  E               OpenVMS VAX clients can access floppy disks served fromuE               OpenVMS Alpha Version 7.3 MSCP servers, but OpenVMS VAXoF               systems cannot serve floppy disks. Client systems can be@               any version that supports port allocation classes.  /         4.9.4 New Fibre Channel Support (Alpha)t  <               Support for new Fibre Channel hardware, largerE               configurations, Fibre Channel Fast Path, and larger I/O I               operations is included in OpenVMS Version 7.3. The benefitsa               include:  I               o  Support for a broader range of configurations: the lowerRF                  cost HSG60 controller supports two SCSI buses insteadC                  of six SCSI buses supported by the HSG80; multipleuG                  DSGGB 16-port Fibre Channel switches enable very largeK                   configurations.  F               o  Backup operations to tape, enabled by the new ModularG                  Data Router (MDR), using existing SCSI tape subsystemsC  I               o  Distances up to 100 kilometers between systems, enablingwE                  more configuration choices for multiple-site OpenVMSE                   Cluster systems  I                                           System Management Features 4-13S L  G           System Management Features     4.9 OpenVMS Cluster SystemsI    E           o  Better performance for certain types of I/O due to Fibre B              Channel Fast Path and support for larger I/O requests  E           The following new Fibre Channel hardware has been qualified >           on OpenVMS Version 7.2-1 and on OpenVMS Version 7.3:  "           o  KGPSA-CA host adapter  E           o  DSGGB-AA switch (8 ports) and DSGGB-AB switch (16 ports)   @           o  HSG60 storage controller (MA6000 storage subsystem)  -           o  Compaq Modular Data Router (MDR)Y  =           OpenVMS now supports Fibre Channel fabrics. A FibresE           Channel fabric is multiple Fibre Channel switches connected0E           together. (A Fibre Channel fabric is also known as cascaded4           switches.)  >           Configurations that use Fibre Channel fabrics can be=           extremely large. Distances up to 100 kilometers aretB           supported in a multisite OpenVMS Cluster system. OpenVMSA           supports the Fibre Channel SAN configurations describedfB           in the Compaq StorageWorks Heterogeneous Open SAN Design@           Reference Guide, available at the following Compaq web           site:g  '           http://www.compaq.com/storage   @           Enabling Fast Path for Fibre Channel can substantially@           increase the I/O throughput on an SMP system. For more@           information about this new feature, see Section 4.9.2.  A           Prior to OpenVMS Alpha Version 7.3, I/O requests largeraD           than 127 blocks were segmented by the Fibre Channel driver>           into multiple I/O requests. Segmented I/O operationsA           generally have lower performance than one large I/O. InnC           OpenVMS Version 7.3, I/O requests up to and including 256 -           blocks are done without segmenting.e  C           For more information about Fibre Channel usage in OpenVMSaE           Cluster configurations, refer to the Guidelines for OpenVMSa!           Cluster Configurations.D    #     4-14 System Management Features     h      I                                                System Management FeaturesvI                                               4.9 OpenVMS Cluster Systemsf    6         4.9.4.1 New Fibre Channel Tape Support (Alpha)  G               Fibre Channel tape functionality refers to the support ofbF               SCSI tapes and SCSI tape libraries in an OpenVMS ClusterF               system with shared Fibre Channel storage. The SCSI tapesC               and libraries are connected to the Fibre Channel by a C               Fibre-to-SCSI bridge known as the Modular Data Router                (MDR).  H               For configuration information, refer to the Guidelines for-               OpenVMS Cluster Configurations.e  +         4.9.5 LANs as Cluster Interconnectso  I               An OpenVMS Cluster system can use several LAN interconnects.F               for node-to-node communication, including Ethernet, Fast8               Ethernet, Gigabit Ethernet, ATM, and FDDI.  A               PEDRIVER, the cluster port driver, provides clustera@               communications over LANs using the NISCA protocol.C               Originally designed for broadcast media, PEDRIVER haslF               been redesigned to exploit all the advantages offered byH               switched LANs, including full duplex transmission and more)               complex network topologies.R  H               Users of LANs for their node-to-node cluster communicationD               will derive the following benefits from the redesigned               PEDRIVER:P  I               o  Removal of restrictions for using Fast Ethernet, Gigabith;                  Ethernet, and ATM as cluster interconnects   C               o  Improved performance due to better path selection, H                  multipath load distribution, and support of full duplex                  communication  $               o  Greater scalability  D               o  Ability to monitor, manage, and display informationD                  needed to diagnose problems with cluster use of LAN#                  adapters and paths         I                                           System Management Features 4-15                 System Management Features     4.9 OpenVMS Cluster Systemss         4.9.5.1 SCA Control Programr  @           The SCA Control Program (SCACP) utility is designed to@           monitor and manage cluster communications. (SCA is theD           abbreviation of Systems Communications Architecture, whichD           defines the communications mechanisms that enable nodes in4           an OpenVMS Cluster system to communicate.)  E           In OpenVMS Version 7.3, you can use SCACP to manage SCA usemE           of LAN paths. In the future, SCACP might be used to monitoruB           and manage SCA communications over other OpenVMS Cluster           interconnects.  C           This utility is described in more detail in a new chapterK>           in the OpenVMS System Management Utilities Reference           Manual: M-Z.  /     4.9.5.2 New Error Message About Packet Losse  >           Prior to OpenVMS Version 7.3, an SCS virtual circuitE           closure was the first indication that a LAN path had becomenD           unusable. In OpenVMS Version 7.3, whenever the last usableC           LAN path is losing packets at an excessive rate, PEDRIVER 1           displays the following console message:D  M           %PEA0, Excessive packet losses on LAN Path from local-device-name -n5            _  to device-name on REMOTE NODE node-nameo  ;           This message is displayed after PEDRIVER performse<           an excessively high rate of packet retransmissions=           on the LAN path consisting of the local device, the A           intervening network, and the device on the remote node. B           The message indicates that the LAN path has degraded andB           is approaching, or has reached, the point where reliableE           communications with the remote node are no longer possible.e=           It is likely that the virtual circuit to the remotei>           node will close if the losses continue. Furthermore,=           continued operation with high LAN packet losses cane@           result in a significant loss in performance because ofA           the communication delays resulting from the packet loss 7           detection timeouts and packet retransmission.w  +           The corrective steps to take are:   ?           1. Check the local and remote LAN device error counts A              to see if a problem exists on the devices. Issue theP-              following commands on each node:i  #     4-16 System Management Features            I                                                System Management Features I                                               4.9 OpenVMS Cluster Systems-    0                  $ SHOW DEVICE local-device-name                  $ MC SCACPo,                  SCACP> SHOW LAN device-name                  $ MC LANCP 5                  LANCP> SHOW DEVICE device-name/COUNT   G               2. If device error counts on the local devices are within F                  normal bounds, contact your network administrators toD                  request that they diagnose the LAN path between the                  devices.i  I                  If necessary, contact your COMPAQ support representativeeE                  for assistance in diagnosing your LAN path problems.   F               For additional PEDRIVER troubleshooting information, see?               Appendix F of the OpenVMS Cluster Systems manual.   -         4.9.6 Warranted and Migration Support.  B               Compaq provides two levels of support, warranted andI               migration, for mixed-version and mixed-architecture OpenVMSa               Cluster systems.  E               Warranted support means that Compaq has fully qualifiedIH               the two versions coexisting in an OpenVMS Cluster and willE               answer all problems identified by customers using theseO               configurations.h  D               Migration support is a superset of the Rolling UpgradeD               support provided in earlier releases of OpenVMS and isC               available for mixes that are not warranted. Migration F               support means that Compaq has qualified the versions forD               use together in configurations that are migrating in aD               staged fashion to a newer version of OpenVMS VAX or ofD               OpenVMS Alpha. Problem reports submitted against theseD               configurations will be answered by Compaq. However, inF               exceptional cases, Compaq may request that you move to aG               warranted configuration as part of answering the problem.a  E               Compaq supports only two versions of OpenVMS running ineE               a cluster at the same time, regardless of architecture.tI               Migration support helps customers move to warranted OpenVMS H               Cluster version mixes with minimal impact on their cluster               environments.   I                                           System Management Features 4-17     o           System Management Features     4.9 OpenVMS Cluster Systems     ?           Table 4-2 shows the level of support provided for all $           possible version pairings.  E           Table_4-2_OpenVMS_Cluster_Warranted_and_Migration_Support__t  1                                       Alpha V7.2-i*                         Alpha/VAX     xxx/E           ______________V7.3__________VAX_V7.2______Alpha/VAX_V7.1___e  =           Alpha/VAX     WARRANTED     Migration     Migration            V7.3  =           Alpha V7.2-   Migration     WARRANTED     MigrationE           xxx/           VAX V7.2  =           Alpha/VAX     Migration     Migration     WARRANTEDiE           V7.1_______________________________________________________i  B           In a mixed-version cluster with OpenVMS Version 7.3, youD           must install remedial kits on earlier versions of OpenVMS.C           For OpenVMS Version 7.3, two new features, XFC and VolumelB           Shadowing minicopy, cannot be run on any node in a mixedC           version cluster unless all nodes running earlier versionst@           of OpenVMS have installed the required remedial kit or>           upgrade. Remedial kits are available now for XFC. AnA           upgrade for systems running OpenVMS Version 7.2-xx thattA           supports minicopy will be made available soon after then)           release of OpenVMS Version 7.3.o  E           For a complete list of required remedial kits, refer to thec,           OpenVMS Version 7.3 Release Notes.  5     4.10 OpenVMS SMP Performance Improvements (Alpha)i  B           OpenVMS Alpha Version 7.3 contains software changes that@           improve SMP scaling. Designed for applications runningA           on the new AlphaServer GS-series systems, many of theserB           improvements will benefit all customer applications. TheE           OpenVMS SMP performance improvements in Version 7.3 include            the following:  '           o  Improved MUTEX Acquisition     #     4-18 System Management Featuress    e      I                                                System Management Features I                         4.10 OpenVMS SMP Performance Improvements (Alpha)     H                  Mutexes are used for synchronization of numerous eventsB                  on OpenVMS. The most common use of a mutex is forF                  synchronization of the logical names database and I/OF                  base. In releases prior to OpenVMS Alpha Version 7.3,C                  the manipulation of a mutex was completed with theaE                  SCHED spinlock held. Because the SCHED spinlock is atH                  heavily used spinlock with high contention on large SMPH                  systems and only a single CPU could manipulate a mutex,,                  bottlenecks often occurred.  F                  OpenVMS Alpha Version 7.3 changes the way mutexes areF                  manipulated. The mutex itself is now manipulated withC                  atomic instructions. Thus multiple CPUs manipulaterG                  different mutexes in parallel. In most cases, the need I                  to acquire the SCHED spinlock has been avoided. In casesnG                  where a process must be placed into a mutex wait state E                  or when mutex waiters must wake up, SCHED will still %                  need to be acquired.e  ,               o  Improved Process Scheduling  E                  Changes made to the OpenVMS process scheduler reduceOC                  contention on the SCHED spinlock. Prior to OpenVMSeC                  Version 7.3, when a process became computable, the,G                  scheduler released all IDLE CPUs to attempt to execute G                  the process. On NUMA systems, all idle CPUs in the RAD F                  were released. These idle CPUs competed for the SCHEDE                  spinlock, which added to the contention on the SCHEDtC                  spinlock. As of OpenVMS Version 7.3, the scheduler G                  only releases a single CPU. In addition, the scheduler G                  releases high numbered CPUs first. This has the effectVI                  of avoiding scheduling processes on the primary CPU whenM                  possible.  I                  To use the modified scheduler, users must set the systemeH                  parameter SCH_CTLFLAGS to 1. This parameter is dynamic.  %               o  Improved SYS$RESCHED   ?                  A number of applications and libraries use the D                  SYS$RESCHED system service, which requests a CPU toI                  reschedule another process. In releases prior to OpenVMS F                  Version 7.3, this system service would lock the SCHEDF                  spinlock and attempt to reschedule another computable$                  process on the CPU.  I                                           System Management Features 4-19m                System Management Features5     4.10 OpenVMS SMP Performance Improvements (Alpha)G    @              Prior to OpenVMS Version 7.3, when heavy contentionD              existed on the SCHED spinlock, using SYS$RESCHED systemB              increased resources contention. As of OpenVMS VersionD              7.3, the SYS$RESCHED system service attempts to acquireC              the SCHED spinlock with a NOSPIN routine. Thus, if the E              SCHED spinlock is currently locked, this thread will not 5              spin. It will return back to the caller.M  3           o  Lock Manager 2000 and 180 improvementst  ?              There are several changes to the lock manager. Foro>              OpenVMS Clusters, the lock manager no longer uses@              IOLOCK8 for synchronization. It now uses the LCKMGRA              spinlock, which allows locking and I/O operations tot              occur in parallel.f  B              Remaster operations can be performed much faster now.B              The remaster code sends large messages with data from@              many locks when remastering as opposed to sending a%              single lock per message.h  ?              The lock manager supports a Dedicated CPU mode. IneE              cases where there is very heavy contention on the LCKMGRtD              spinlock, dedicating a single CPU to performing lockingA              operations provides a much more efficient mechanism.   1           o  Enhanced Spinlock Tracing capabilityo  B              The spinlock trace capability, which first shipped in?              V7.2-1H1, can now trace forklocks. In systems with;>              heavy contention on the IOLOCK8 spinlock, much of>              the contention occurs in fork threads. CollectingC              traditional spinlock data only indicates that the fork '              dispatcher locked IOLOCK8.s  E              As of OpenVMS Version 7.3, the spinlock trace has a hooktB              in the fork dispatcher code. This allows the trace toD              report the routine that is called by the fork dispatch,D              which indicates the specific devices that contribute to&              heavy IOLOCK8 contention.  "           o  Mailbox driver change  A              Prior to OpenVMS Version 7.3, the mailbox driver FDTO>              routines called a routine that locked the MAILBOXC              spinlock and delivered any required attention ASTs. InaC              most cases, this routine did not require any attentionn@              ASTs to be delivered. Because the OpenVMS code that?              makes these calls already has the MAILBOX spinlock   #     4-20 System Management FeaturesM 0  t      I                                                System Management FeaturespI                         4.10 OpenVMS SMP Performance Improvements (Alpha)c    F                  locked, the spinlock acquisition was also an unneeded0                  second acquire of the spinlock.  D                  As of OpenVMS Version 7.3, OpenVMS now first checksE                  to see if any ASTs may need to be delivered prior totH                  calling the routine. This avoids both the call overheadH                  and the overhead of relocking the MAILBOX spinlock that#                  was already owned.o  /         4.11 New SYSMAN Commands and Qualifiersl  @               The SYSMAN utility has the following new commands:  (               o  CLASS_SCHEDULE commands  F                  The class scheduler provides the ability to limit theD                  amount of CPU time that a system's users receive by5                  placing users in scheduling classes.o  I                  ________________________________________________________kI                  Command_____________________Description_________________e  E                  CLASS_SCHEDULE ADD          Creates a new schedulingn2                                              class  G                  CLASS_SCHEDULE DELETE       Deletes a scheduling classh  I                  CLASS_SCHEDULE MODIFY       Modifies the characteristicsiB                                              of a scheduling class  G                  CLASS_SCHEDULE RESUME       Resumes a scheduling classaD                                              that has been suspended  I                  CLASS_SCHEDULE SHOW         Displays the characteristics B                                              of a scheduling class  C                  CLASS_SCHEDULE SUSPEND      Temporarily suspends aaI                  ____________________________scheduling_class____________a  >               o  IO FIND_WWID and IO_REPLACE_WWID (Alpha-only)  F                  These commands support Fibre Channel tapes, which are.                  discussed in Section 4.9.4.1.  I                  ________________________________________________________ I                  Command_____________________Description_________________   C                  IO FIND_WWID                Detects all previouslysC                                              undiscovered tapes and <                                              medium changers  I                                           System Management Features 4-21t T  a           System Management Features+     4.11 New SYSMAN Commands and Qualifiers   E              ________________________________________________________ E              Command_____________________Description_________________   ?              IO REPLACE_WWID             Replaces one worldwide ?                                          identifier (WWID) with E              ____________________________another_____________________   A           o  POWER_OFF qualifier for SYSMAN command SHUTDOWN NODEv  E              The /POWER_OFF qualifier specifies that the system is to 2              power off after shutdown is complete.  B           For more information, refer to the SYSMAN section of theD           OpenVMS System Management Utilities Reference Manual: M-Z.       4.12 New System Parameters  E           This section contains definitions of system parameters that )           are new in OpenVMS Version 7.3.s       4.12.1 AUTO_DLIGHT_SAV  D           AUTO_DLIGHT_SAV is set to either 1 or 0. The default is 0.  E           If AUTO_DLIGHT_SAV is set to 1, OpenVMS automatically makest6           the change to and from daylight saving time.       4.12.2 FAST_PATH_PORTS  E           FAST_PATH_PORTS is a static parameter that deactivates FastM$           Path for specific drivers.  A           FAST_PATH_PORTS is a 32-bit mask. If the value of a bitt@           in the mask is 1, Fast Path is disabled for the driverA           corresponding to that bit. A value of -1 specifies thatAC           Fast Path is disabled for all drivers that the FAST_PATH_h#           PORTS parameter controls.V  A           Bit position zero controls Fast Path for PKQDRIVER (for3A           parallel SCSI), and bit position one controls Fast PathtC           for FGEDRIVER (for Fibre Channel). Currently, the defaultcA           setting for FAST_PATH_PORTS is 0, which means that Fast ;           Path is enabled for both PKQDRIVER and FGEDRIVER.   *           In addition, note the following:  C           o  CI drivers are not controlled by FAST_PATH_PORTS. FastrC              Path for CI is enabled and disabled exclusively by the7(              FAST_PATH system parameter.  #     4-22 System Management Features  h  d      I                                                System Management Features I                                                4.12 New System Parameters     I               o  FAST_PATH_PORTS is relevant only if the FAST_PATH system H                  parameter is enabled (equal to 1). Setting FAST_PATH toG                  zero has the same effect as setting FAST_PATH_PORTS toE                  -1.  F               For additional information, see FAST_PATH and IO_PREFER_               CPUS.o           4.12.3 GLX_SHM_REG  D               On Galaxy systems, GLX_SHM_REG is the number of sharedA               memory region structures configured into the Galaxy F               Management Database (GMDB). If you set GLX_SHM_REG to 0,I               the default number of shared memory regions are configured.   #         4.12.4 LCKMGR_CPUID (Alpha)r  B               The LCKMGR_CPUID parameter controls the CPU that theF               Dedicated CPU Lock Manager runs on. This is the CPU thatE               the LCKMGR_SERVER process will utilize if you turn thish?               feature on with the LCKMGR_MODE system parameter.   D               If the specified CPU ID is either the primary CPU or aI               nonexistent CPU, the LCKMGR_SERVER process will utilize thee$               lowest nonprimary CPU.  2               LCKMGR_CPUID is a DYNAMIC parameter.  C               For more information, refer to the LCKMGR_MODE systema               parameter.  "         4.12.5 LCKMGR_MODE (Alpha)  G               The LCKMGR_MODE parameter controls usage of the Dedicated G               CPU Lock Manager. Setting LCKMGR_MODE to a number greaterlE               than zero (0) indicates the number of CPUs that must beWH               active before the Dedicated CPU Lock Manager is turned on.  A               The Dedicated CPU Lock Manager performs all lockingtD               operations on a single dedicated CPU. This can improveH               system performance on large SMP systems with high MP_Synch/               associated with the lock manager.   H               For more information about usage of the Dedicated CPU LockE               Manager, see the OpenVMS Performance Management manual.t  I                                           System Management Features 4-23t ,  e           System Management Features     4.12 New System Parameters    '           Specify one of the following:.  E           ___________________________________________________________ E           Value_____Description______________________________________a  D           0         Indicates the Dedicated CPU Lock Manager is off."                     (The default.)  D           >0        Indicates the number of CPUs that must be activeC                     before the Dedicated CPU Lock Manager is turnedsE           __________on.______________________________________________s  -           LCKMGR_MODE is a DYNAMIC parameter.        4.12.6 NPAGECALC  =           NPAGECALC controls whether the system automatically B           calculates the initial size for nonpaged dynamic memory.  E           Compaq sets the default value of NPAGECALC to 1 only duringfE           the initial boot after an installation or upgrade. When theeC           value of NPAGECALC is 1, the system calculates an initialmE           value for the NPAGEVIR and NPAGEDYN system parameters. ThisaD           calculated value is based on the amount of physical memory           in the system.  >           NPAGECALC's calculations do not reduce the values ofA           NPAGEVIR and NPAGEDYN from the values you see or set atfD           the SYSBOOT prompt. However, NPAGECALC's calculation might            increase these values.  E           AUTOGEN sets NPAGECALC to 0. NPAGECALC should always remain D           0 after AUTOGEN has determined more refined values for the2           NPAGEDYN and NPAGEVIR system parameters.       4.12.7 NPAGERAD (Alpha)m  B           NPAGERAD specifies the total number of bytes of nonpagedC           pool that will be allocated for Resource Affinity Domains D           (RADs) other than the base RAD. For platforms that have noC           RADs, NPAGERAD is ignored. Notice that NPAGEDYN specifiest9           the total amount of nonpaged pool for all RADs.   =           Also notice that the OpenVMS system might round the7@           specified values higher to an even number of pages for?           each RAD, which prevents the base RAD from having too B           little nonpaged pool. For example, if the hardware is an(           AlphaServer GS160 with 4 RADs:  #     4-24 System Management Features  A  N      I                                                System Management Features I                                                4.12 New System Parameters     &               NPAGEDYN = 6291456 bytes&               NPAGERAD = 2097152 bytes  C               In this case, the OpenVMS system allocates a total ofoE               approximately 6,291,456 bytes of nonpaged pool. Of thiseG               amount, the system divides 2,097,152 bytes among the RADseD               that are not the base RAD. The system then assigns the;               remaining 4,194,304 bytes to the base RAD.[1]n  "         4.12.8 RAD_SUPPORT (Alpha)  B               RAD_SUPPORT enables RAD-aware code to be executed onD               systems that support Resource Affinity Domains (RADs);5               for example, AlphaServer GS160 systems.M  B               A RAD is a set of hardware components (CPUs, memory,C               and I/O) with common access characteristics. For morewD               information about using OpenVMS RAD features, refer to>               the OpenVMS Alpha Partitioning and Galaxy Guide.           4.12.9 SHADOW_MAX_UNIT  I               SHADOW_MAX_UNIT specifies the maximum number of shadow setsfG               that can exist on a node. The setting must be equal to or H               greater than the number of shadow sets you plan to have onG               a system. Dismounted shadow sets, unused shadow sets, andsE               shadow sets with no write bitmaps allocated to them areo$               included in the total.  H               This system parameter is not dynamic; that is, a reboot is3               required when you change the setting.   E               The default setting on OpenVMS Alpha systems is 500; ondH               OpenVMS VAX systems, the default is 100. The minimum value5               is 10, and the maximum value is 10,000.m  D               Note that this parameter does not affect the naming ofH               shadow sets. For example, with the default value of 100, a8               device name such as DSA999 is still valid.  "               ____________________F               [1]   The system actually rounds up to an even number ofI                     pages on each RAD. In addition, the base RAD is neverhG                     assigned a value less than the smaller of the valueo0                     of NPAGEDYN and 4 megabytes.  I                                           System Management Features 4-25t   u              System Management Features     4.12 New System Parameters    #     4.12.10 VCC_MAX_IO_SIZE (Alpha)i  C           The dynamic system parameter VCC_MAX_IO_SIZE controls thelE           maximum size of I/O that can be cached by the Extended FilepA           Cache. It specifies the size in blocks. By default, thee           size is 127 blocks.   A           Changing the value of VCC_MAX_IO_SIZE affects reads and C           writes to volumes currently mounted on the local node, as D           well as reads and writes to volumes mounted in the future.  A           If VCC_MAX_IO_SIZE is 0, the Extended File Cache on theh?           local node cannot cache any reads or writes. However,fC           the system is not prevented from reserving memory for thenD           Extended File Cache during startup if a VCC$MIN_CACHE_SIZE3           entry is in the reserved memory registry.l  1           VCC_MAX_IO_SIZE is a DYNAMIC parameter.r  !     4.12.11 VCC_READAHEAD (Alpha)s  E           The dynamic system parameter VCC_READAHEAD controls whethereC           the Extended File Cache can use read-ahead caching. Read- D           ahead caching is a technique that improves the performance6           of applications that read data sequentially.  =           By default VCC_READAHEAD is 1, which means that theA=           Extended File Cache can use read-ahead caching. The ?           Extended File Cache detects when a file is being read B           sequentially in equal-sized I/Os, and fetches data aheadD           of the current read, so that the next read instruction can"           be satisfied from cache.  ?           To stop the Extended File Cache from using read-aheadP*           caching, set VCC_READAHEAD to 0.  =           Changing the value of VCC_READAHEAD affects volumesnA           currently mounted on the local node, as well as volumesp            mounted in the future.  @           Readahead I/Os are totally asynchronous from user I/Os@           and only take place if sufficient system resources are           available.  /           VCC_READAHEAD is a DYNAMIC parameter.E  #     4-26 System Management Featurese           I                                                System Management FeaturesDI                                                4.12 New System Parameters              4.12.12 WBM_MSG_INT   D               WBM_MSG_INT is one of three system parameters that areH               available for managing the update traffic between a masterD               write bitmap and its corresponding local write bitmapsF               in an OpenVMS Cluster system. (Write bitmaps are used byE               the volume shadowing software for minicopy operations.) C               The others are WBM_MSG_UPPER and WBM_MSG_LOWER. These C               parameters set the interval at which the frequency of H               sending messages is tested and also set an upper and lowerG               threshold that determine whether the messages are groupedc:               into one SCS message or are sent one by one.  I               In single-message mode, WBM_MSG_INT is the time interval inUI               milliseconds between assessments of the most suitable writeeE               bitmap message mode. In single-message mode, the writes E               issued by each remote node are, by default, sent one by H               one in individual SCS messages to the node with the masterH               write bitmap. If the writes sent by a remote node reach anF               upper threshold of messages during a specified interval,D               single-message mode switches to buffered-message mode.  I               In buffered-message mode, WBM_MSG_INT is the maximum time aaH               message waits before it is sent. In buffered-message mode,E               the messages are collected for a specified interval and G               then sent in one SCS message. During periods of increased H               message traffic, grouping multiple messages to send in oneF               SCS message to the master write bitmap is generally more=               efficient than sending each message separately.   F               The minimum value of WBM_MSG_INT is 10 milliseconds. TheC               maximum value is -1, which corresponds to the maximum G               positive value that a longword can represent. The defaultm!               is 10 milliseconds.I  1               WBM_MSG_INT is a DYNAMIC parameter.M           4.12.13 WBM_MSG_LOWER   F               WBM_MSG_LOWER is one of three system parameters that areH               available for managing the update traffic between a masterG               write bitmap and its corresponding local write bitmaps in G               an OpenVMS Cluster system. (Write bitmaps are used by therE               volume shadowing software for minicopy operations.) The H               others are WBM_MSG_INT and WBM_MSG_UPPER. These parametersI               set the interval at which the frequency of sending messageslF               is tested and also set an upper and lower threshold that  I                                           System Management Features 4-27N i  y           System Management Features     4.12 New System Parameters    A           determine whether the messages are grouped into one SCSl)           message or are sent one by one.m  @           WBM_MSG_LOWER is the lower threshold for the number of?           messages sent during the test interval that initiates_A           single-message mode. In single-message mode, the writes_A           issued by each remote node are, by default, sent one bySD           one in individual SCS messages to the node with the masterD           write bitmap. If the writes sent by a remote node reach anB           upper threshold of messages during a specified interval,@           single-message mode switches to buffered-message mode.  >           The minimum value of WBM_MSG_LOWER is 0 messages perA           interval. The maximum value is -1, which corresponds to C           the maximum positive value that a longword can represent.            The default is 10.  /           WBM_MSG_LOWER is a DYNAMIC parameter.        4.12.14 WBM_MSG_UPPER   B           WBM_MSG_UPPER is one of three system parameters that areD           available for managing the update traffic between a masterC           write bitmap and its corresponding local write bitmaps in C           an OpenVMS Cluster system. (Write bitmaps are used by therA           volume shadowing software for minicopy operations.) ThetD           others are WBM_MSG_INT and WBM_MSG_LOWER. These parametersE           set the interval at which the frequency of sending messagesrB           is tested and also set an upper and lower threshold thatA           determine whether the messages are grouped into one SCS )           message or are sent one by one.   @           WBM_MSG_UPPER is the upper threshold for the number of?           messages sent during the test interval that initiatesa>           buffered-message mode. In buffered-message mode, theB           messages are collected for a specified interval and then"           sent in one SCS message.  >           The minimum value of WBM_MSG_UPPER is 0 messages perA           interval. The maximum value is -1, which corresponds to C           the maximum positive value that a longword can represent.            The default is 100._  /           WBM_MSG_UPPER is a DYNAMIC parameter.W  #     4-28 System Management FeaturesT N  D      I                                                System Management Features I                                                4.12 New System Parametersa             4.12.15 WBM_OPCOM_LVLf  I               WBM_OPCOM_LVL controls whether write bitmap system messages G               are sent to the operator console. (Write bitmaps are usediH               by the volume shadowing software for minicopy operations.)?               Possible values are shown in the following table:t  I               ___________________________________________________________oI               Value__Description_________________________________________   -               0      Messages are turned off.   B               1      The default; messages are provided when writeH                      bitmaps are started, deleted, and renamed, and whenG                      the SCS message mode (buffered or single) changes.d  F               2      All messages for a setting of 1 are provided plusI               _______many_more.__________________________________________F  3               WBM_OPCOM_LVL is a DYNAMIC parameter.   )         4.13 Volume Shadowing for OpenVMSr  I               Volume Shadowing for OpenVMS introduces three new features,tB               the minicopy operation enabled by write bitmaps, newB               qualifiers for disaster tolerant support for OpenVMSA               Cluster systems, and a new /SHADOW qualifier to theRF               INITIALIZE command. These features are described in this               section.  F         4.13.1 Minicopy in Compaq Volume Shadowing for OpenVMS (Alpha)  E               The new minicopy feature of Compaq Volume Shadowing for2D               OpenVMS and its enabling technology, write bitmap, areE               fully implemented on OpenVMS Alpha systems. OpenVMS VAX F               nodes can write to shadow sets that use this feature butE               they can neither create master write bitmaps nor manage %               them with DCL commands.)  E               The minicopy operation is a streamlined copy operation.i@               Minicopy is designed to be used in place of a copyI               operation when you return a shadow set member to the shadow F               set. When a member has been removed from a shadow set, aI               write bitmap tracks the changes that are made to the shadowu9               set in its absence, as shown in Figure 4-1.D  I                                           System Management Features 4-29m r  e           System Management Features%     4.13 Volume Shadowing for OpenVMS     B           When the member is returned to the shadow set, the writeC           bitmap is used to direct the minicopy operation, as shown ?           in Figure 4-2. While the minicopy operation is taking C           place, the application continues to read and write to the            shadow set.U  E           Thus, minicopy can significantly decrease the time it takesKB           to return the member to membership in the shadow set andC           can significantly increase the availability of the shadow %           sets that use this feature.t  E           Typically, a shadow set member is removed from a shadow set_E           to back up the data on the disk. Before the introduction ofoE           the minicopy feature, Compaq required that the virtual unitoE           (the shadow set) be dismounted to back up the data from one E           of the members. This requirement has been removed, providedMB           that the guidelines for removing a shadow set member for@           backup purposes, as documented in Volume Shadowing for            OpenVMS, are followed.  @           For more information about this new feature, includingC           additional memory requirements for this version of Compaq E           Volume Shadowing for OpenVMS, refer to Volume Shadowing fora           OpenVMS.  B     4.13.2 New Volume Shadowing Features for Multiple-Site OpenVMS            Cluster Systems  ?           OpenVMS Version 7.3 introduces new command qualifiers.C           for the DCL commands DISMOUNT and SET for use with Volume.E           Shadowing for OpenVMS. These new command qualifiers provide_E           disaster tolerant support for multiple-site OpenVMS Cluster_E           systems. Designed primarily for multiple-site clusters thatfD           use Fibre Channel for a site-to-site storage interconnect,?           they can be used in other configurations as well. Foro@           more information about using these new qualifiers in aC           multiple-site OpenVMS Cluster system, see the white paperRD           Using Fibre Channel in a Disaster-Tolerant OpenVMS ClusterB           System, which is posted on the OpenVMS Fibre Channel web           site at:  6           http://www.openvms.compaq.com/openvms/fibre/  C           The new command qualifiers are described in this section.oE           Section 4.13.2.1 describes how to use these new qualifiers.E  #     4-30 System Management Featurest m         I                                                System Management FeaturesaI                                         4.13 Volume Shadowing for OpenVMSs    *               DISMOUNT/FORCE_REMOVAL ddcu:  H               One new qualifier to the DISMOUNT command, DISMOUNT/FORCE_E               REMOVAL ddcu:, is provided. If connectivity to a devicelH               has been lost and the shadow set is in mount verification,F               /FORCE_REMOVAL ddcu: can be used to immediately expell aE               named shadow set member (ddcu:) from the shadow set. IfNI               you omit this qualifier, the device is not dismounted untilGD               mount verification completes. Note that this qualifierE               cannot be used in conjunction with the /POLICY=MINICOPYo$               (=OPTIONAL) qualifier.  H               The device specified must be a member of a shadow set thatA               is mounted on the node where the command is issued.                  SET DEVICE  I               The following new qualifiers to the SET DEVICE command have E               been created for managing shadow set members located atA               multiple sites:i  %               o  /FORCE_REMOVAL ddcu:a  I                  If connectivity to a device has been lost and the shadowaH                  set is in mount verification, this qualifier causes theG                  member to be expelled from the shadow set immediately.   <                  If the shadow set is not currently in mount?                  verification, no immediate action is taken. If F                  connectivity to a device has been lost but the shadowF                  set is not in mount verification, this qualifier letsH                  you flag the member to be expelled from the shadow set,=                  as soon as it does enter mount verification.   F                  The device specified must be a member of a shadow setI                  that is mounted on the node where the command is issued.   -               o  /MEMBER_TIMEOUT=xxxxxx ddcu:t  I                  Specifies the timeout value to be used for a member of a1                  shadow set.  C                  The value supplied by this qualifier overrides the B                  SYSGEN parameter SHADOW_MBR_TMO for this specificF                  device. Each member of a shadow set can be assigned a0                  different MEMBER_TIMEOUT value.  G                  The valid range for xxxxxx is 1 to 16,777,215 seconds.   F                  The device specified must be a member of a shadow setI                  that is mounted on the node where the command is issued.a  I                                           System Management Features 4-31  s  s           System Management Features%     4.13 Volume Shadowing for OpenVMSo    '           o  /MVTIMEOUT=yyyyyy DSAnnnn:a  A              Specifies the mount verification timeout value to berD              used for this shadow set, specified by its virtual unit              name, DSAnnnn.   ?              The value supplied by this qualifier overrides thet@              SYSGEN parameter MVTIMEOUT for this specific shadow              set.e  C              The valid range for yyyyyy is 1 to 16,777,215 seconds.t  >              The device specified must be a shadow set that is=              mounted on the node where the command is issued.i  !           o  /READ_COST=zzz ddcu:_  A              The valid range for zzz is 1 to 4,294,967,295 units.a  B              The device specified must be a member of a shadow setE              that is mounted on the node where the command is issued.t  C              This qualifier allows you to modify the default "cost"eC              assigned to each member of a shadow set, so that readst?              are biased or prioritized toward one member versus.              another.s  B              The shadowing driver assigns default READ_COST values@              to shadow set members when each member is initiallyC              mounted. The default value depends on the device type,IB              and its configuration relative to the system mounting@              it. There are default values for a DECRAM device; aE              directly connected device in the same physical location;l@              a directly connected device in a remote location; a@              DECram served device; and a default value for other              served devices.  ?              The value supplied by this qualifier overrides the D              default assignment. The shadowing driver adds the valueC              of the current queue depth of the shadow set member to D              the READ_COST value and then reads from the member with              the lowest value.  B              Different systems in the cluster can assign different-              costs to each shadow set member.   C              If the /SITE command qualifier has been specified, the @              shadowing driver will take site values into account@              when it assigns default READ_COST values. Note thatB              in order for the shadowing software to determine if aD              device is in the category of "directly connected device  #     4-32 System Management Features            I                                                System Management FeaturesrI                                         4.13 Volume Shadowing for OpenVMSo    H                  in a remote location," the /SITE command qualifier mustD                  have been applied to both the shadow set and to the#                  individual device.n  G                  Reads requested for a shadow set from a system at Site F                  1 are performed from a shadow set member that is alsoH                  at Site 1. Reads requested for the same shadow set fromC                  Site 2 can read from the member located at Site 2.D  %               o  /READ_COST=y DSAnnnna  H                  The valid range for y is any non-zero number. The valueB                  supplied has no meaning in itself. The purpose ofF                  this qualifier is to switch the read cost setting forE                  all shadow set members back to the default read costeD                  settings established automatically by the shadowingG                  software. DSAnnnn must be a shadow set that is mounteds?                  on the node from which this command is issued.u  ;               o  /SITE=(nnn, logical_name) (ddcu: DSAnnnn:)y  E                  This qualifier indicates to the shadowing driver theWH                  site location of the shadow set member or of the shadowE                  set (represented by its virtual unit name). Prior toaG                  using this qualifier, you can define the site location H                  in the SYLOGICALS.COM command procedure to simplify its                  use.e  :                  The valid range for nnn is 1 through 255.  H                  The following example shows the site locations defined,<                  followed by the use of the /SITE qualifier:  +                  $ DEFINE/SYSTEM/EXEC ZKO 1d+                  $ DEFINE/SYSTEM/EXEC LKG 2d                  $!t'                  $! At the ZKO site ... B                  $ MOUNT/SYSTEM DSA0/SHAD=($1$DGA0:,$1$DGA1:) TEST-                  $ SET DEVICE/SITE=ZKO  DSA0:i                  $! '                  $! At the LKG site ...u@                  $ MOUNT/SYSTEM DSA0/SHAD=($1$DGA0,$1$DGA1) TEST-                  $ SET DEVICE/SITE=LKG  DSA0:                   $!i?                  $! At both sites, the following would be used:a0                  $ SET DEVICE/SITE=ZKO  $1$DGA0:0                  $ SET DEVICE/SITE=LKG  $1$DGA1:  .               o  /COPY_SOURCE (ddcu:,DSAnnnn:)  I                                           System Management Features 4-33s    t           System Management Features%     4.13 Volume Shadowing for OpenVMS     D              Controls whether one or both source members of a shadowA              set are used as the source for read data during fulltA              copy operations, when a third member is added to thepB              shadow set. This only affects copy operations that do$              not use DCD operations.  =              HSG80 controllers have a read-ahead cache, whichOA              significantly improves single-disk read performance.aA              Copy operations normally alternate reads between the @              two source members, which effectively nullifies theB              benefits of the read-ahead cache. This qualifier letsB              you force all reads from a single source member for a              copy operation.  D              If the shadow set is specified, then all reads for fullB              copy operations will be performed from whichever diskC              is the current "master" member, regardless of physical "              location of the disk.  =              If a member of the shadow set is specified, thene?              that member will be used as the source of all copyhA              operations. This allows you to choose a local sourcea8              member, rather than a remote master member.  )           o  /ABORT_VIRTUAL_UNIT DSAnnnn:s  C              To use this qualifier, the shadow set must be in mounts?              verification. When you specify this qualifier, thebD              shadow set aborts mount verification immediately on theD              node from which the qualifier is issued. This qualifierB              is intended to be used when it is known that the unit>              cannot be recovered. Note that after this command@              completes, the shadow set must still be dismounted.B              Use the following command to dismount the shadow set:  %              DISMOUNT/ABORT   DSAnnnnp  C     4.13.2.1 How to Use the New DISMOUNT and SET Command Qualifierse  E           The diagram in this section depicts a typical multiple-siteMC           cluster using Fibre Channel. It is used to illustrate theEE           steps which must be taken to manually recover one site whenaE           the site-to-site storage interconnect fails. Note that withiA           current Fibre Channel support, neither site can use thet:           MSCP server to regain a path to the DGA devices.  #     4-34 System Management Featuresi .  h      I                                                System Management Features I                                         4.13 Volume Shadowing for OpenVMSs    @               To prevent the shadowing driver from automaticallyF               recovering shadow sets from connection-related failures,=               three steps must be taken prior to any failure:r  H               1. Every device that is a member of a multiple-site shadowE                  set must have its member_timeout setting raised to ae9                  high value, using the following command:d  7                  $ SET DEVICE /MEMBER_TIMEOUT= x  ddcu:   E                  This command will override the SHADOW_MBR_TMO value,nH                  which would normally be used for a shadow set member. AG                  value for x of 259200 would be a seventy-two hour wait                   time.  I               2. Every shadow set that spans multiple sites must have its I                  mount verification timeout setting raised to a very higheH                  value, higher than the MEMBER_TIMEOUT settings for each*                  member of the shadow set.  @                  Use the following command to increase the mountA                  verification timeout setting for the shadow set:W  5                  $ SET DEVICE /MVTIMEOUT = y  DSAnnnnw  E                  The y value of this command should always be greater G                  than the x value of the $ SET DEVICE/MEMBER_TIMEOUT= x_                  ddcu:._  F                  The $ SET DEVICE /MVTIMEOUT = y command will overrideF                  the MVTIMEOUT value, which would normally be used forC                  the shadow set. A value for y of 262800 would be a )                  seventy-three hour wait.d  G               3. Every shadow set and every shadow set member must havesE                  a site qualifier. As already noted, a site qualifier1E                  will ensure that the read cost is correctly set. The_H                  other critical factor is three-member shadow sets. WhenI                  they are being used, the site qualifier will ensure thatSE                  the master member of the shadow set will be properly                   maintained.  F               In the following diagram, shadow set DSA42 is made up of'               $1$DGA1000 and $1$DGA2000m  I                                           System Management Features 4-35s e  r           System Management Features%     4.13 Volume Shadowing for OpenVMSn    G                    <><><><><><><><><><><>  LAN   <><><><><><><><><><><>y?                    Site A                                Site Bn=                       |                                     |lD                    F.C. SWITCH  <><><><> XYZZY <><><><>  F.C. SWITCH=                       |                                     | I                    HSG80 <><> HSG80                      HSG80 <><> HSG80 =                       |                                     |iC                    $1$DGA1000  --------- DSA42 --------- $1$DGA2000n  A           This diagram illustrates that systems at Site A or Sitet?           B have direct access to all devices at both sites via A           Fibre Channel connections. XYZZY is a theoretical pointiE           between the two sites. If the Fibre Channel connection were B           to break at this point, each site could access differentD           "local" members of DSA42 without error. For the purpose ofE           this example, Site A will be the sole site chosen to retain #           access to the shadow set.   C           The following actions must be taken to recover the shadown           set at Site A.             On Site A:  0           $ DISMOUNT /FORCE_REMOVAL= $1$DGA2000:  @           Once the command has completed, the shadow set will be+           available for use only at site A.c             On Site B:  1           $ SET DEVICE /ABORT_VIRTUAL_UNIT DSA42:t  C           Once the command completes, the shadow set status will bee           MntVerifyTimeout.o  A           Next, issue the following command to free up the shadows           set:  !           $ DISMOUNT/ABORT DSA42:   B           These steps must be taken for all affected multiple-site           shadow sets.      #     4-36 System Management Features            I                                                System Management FeaturesmI                                         4.13 Volume Shadowing for OpenVMSi    H         4.13.3 Using INITIALIZE/SHADOW/ERASE to Streamline the Formation                of a Shadow Set  E               The new /SHADOW qualifier to the DCL INITIALIZE commandtE               is available. The use of the INITIALIZE /SHADOW commandfC               to initialize multiple members of a future shadow seteG               eliminates the requirement for a full copy operation when ,               you later create a shadow set.  B               Compaq strongly recommends that you also specify theF               /ERASE qualifier with the INITIALIZE/SHADOW command whenC               initializing multiple members of a future shadow set.mE               Whereas the /SHADOW qualifier eliminates the need for apI               full copy operation when you later create a shadow set, theeF               /ERASE qualifier reduces the amount of time a full merge               will take.  H               If you omit the /ERASE qualifier, and a merge operation ofG               the shadow set is subsequently required (because a system F               on which the shadow set is mounted fails), the resulting@               merge operation will take much longer to complete.  @               The INITIALIZE command with the /SHADOW and /ERASE;               qualifiers performs the following operations:   H               o  Formats up to six devices with one command, so that anyI                  three can be subsequently mounted together as members ofs-                  a new host-based shadow set.   /               o  Writes a label on each volume.e  D               o  Deletes all information from the devices except forE                  the system files containing identical file structure H                  information. All former contents of the disks are lost.  D               You can then mount up to three of the devices that youI               have initialized in this way as members of a new host-based                shadow set.c  A               For more information, refer to Volume Shadowing fort               OpenVMS.        I                                           System Management Features 4-37e n  G                    I                                                                         5 I         _________________________________________________________________u  I                                                      Programming Featurese    I               This chapter describes new features relating to application B               and system programming on this version of the Compaq'               OpenVMS operating system.            5.1 3D Graphics Supportd  I               The PowerStorm 300 (PBXGD-AD) and PowerStorm 350 (PBXGD-AE) F               graphics cards are now supported on Alpha-based systems.C               The OpenGL 3D graphics API is now provided as part ofcF               the OpenVMS base operating system. The version of OpenGLI               supported on the PowerStorm 300 and PowerStorm 350 graphics #               cards is Version 1.1.   I               The implementation of OpenGL Version 1.1 for the PowerStormv?               300 or PowerStorm 350 is designed to coexist withtC               installations of the Open3D layered product for olderyG               graphics cards. The images shipped with OpenVMS are namedaI               DECW$OPENGLSHR_V11 and DECW$OPENGLUSHR_V11. The _V11 suffix B               is used to distinguish the OpenGL Version 1.1 imagesD               from the OpenGL Version 1.0 images shipped with Open3D3               (DECW$OPENGLSHR and DECW$OPENGLUSHR).e  H               Applications using only OpenGL V1.0 features may be linkedE               against either the Open3D images or the new Version 1.1iD               images. Applications using OpenGL Version 1.1 featuresI               should be linked explicitly against the Version 1.1 images.d  ?               For further information on OpenGL support for the H               PowerStorm 300 and PowerStorm 350, refer to the PowerStormH               300/350 Installation Guide and Release Notes documentation-               shipped with the graphics card.a  G                 _______________________ WARNING _______________________n  E                 If 3D graphics will be used extensively, particularlyVC                 in an environment using multiple PowerStorm 300 andnF                 PowerStorm P350s in a single system, read and strictly  I                                                  Programming Features 5-1                 Programming Features     5.1 3D Graphics Supportu    A              observe the guidelines for setting SYSGEN parameterssC              and account quotas contained in the PowerStorm 300/350f?              OpenVMS Graphics Support Release Notes Version 1.1 C              and the Compaq PowerStorm 300/350 Graphics Controllerso?              Installation Guide shipped with the graphics card.dB              The Release notes can also be accessed on the OpenVMS=              Documentation CD-ROM in the following directory:   C              ______________________________________________________dC              Directory____________________File_Name________________d  C              [73.DOCUMENTATION.PS_TXT]____P300_350_REL_NOTES.PS,TXTo  C              ______________________________________________________v  <     5.2 3X-DAPBA-FA and 3X-DAPCA-FA ATM LAN Adapters (Alpha)  A           The 3X-DAPBA-FA (HE155) and 3X-DAPCA-FA (HE622) are PCIeE           based ATM LAN adapters for Alpha based systems that provideuA           high performance PCI-to-ATM capability. The 3X-DAPBA-FArE           adapter offers a 155 Mbps fiber connection; the 3X-DAPCA-FAe5           adapter offers a 622 Mbps fiber connection.e  C           The datalink drivers for these adapters function in a newcE           OpenVMS ATM environment. The new OpenVMS ATM environment isaC           fully compatible with the existing legacy ATM support and C           allows both ATM environments to be configured on a single B           system. Also, the LANCP management interface is the same$           for both ATM environments.  D           For additional information about the 3X-DAPBA-FA PCI HE155B           ATM and 3X-DAPCA-FA PCI HE622 ATM LAN adapters, refer to           the following URL:  <           http://www.compaq.com/alphaserver/products/options  2     5.3 Compaq COBOL Run-Time Library Enhancements  @           The COBOL RTL for both Alpha and VAX supports five new;           intrinsic functions with four-digit year formats:R                YEAR-TO-YYYY               DATE-TO-YYYYMMDDd              DAY-TO-YYYYDDDf              TEST-DATE-YYYYMMDD               TEST-DAY-YYYYDDD        5-2 Programming Features t  a      I                                                      Programming FeatureseI                            5.3 Compaq COBOL Run-Time Library Enhancementsn    F               The COBOL RTL for Alpha has improved performance for theE               DISPLAY statement redirected to a file and for programs E               compiled with the /MATH=CIT3 and /MATH=CIT4 qualifiers.   I               This RTL's handling of ON SIZE ERROR is now more compatiblea8               with that of Compaq COBOL for OpenVMS VAX.  2         5.4 Compaq C Run-Time Library Enhancements  >               The following sections describe the Compaq C RTLD               enhancements included in OpenVMS Version 7.3. For more@               details, refer to the revision of the Compaq C RTLF               Reference Manual that ships with Compaq C Version 6.3 or               later.  1         5.4.1 Strptime Function Is XPG5-Compliant   E               The strptime function has been modified to be compliant I               with X/Open CAE Specification System Interfaces and Headers F               Issue 5 (commonly known as XPG5). The change for XPG5 isG               in how the strptime function processes the "%y" directiveIF               for a two-digit year within the century if no century is               specified.  F               When a century is not otherwise specified, XPG5 requiresC               that values for the "%y" directive in the range 69-99iC               refer to years in the twentieth century (1969 to 1999fH               inclusive), while values in the range 00-68 refer to yearsC               in the twenty-first century (2000 to 2068 inclusive).eD               Essentially, for the "%y" directive, strptime became aA               "pivoting" function, with 69 being a pivoting year.o  E               Before this change, the strptime function interpreted aMG               two-digit year with no century as a year within twentieth                century.  G               With OpenVMS Version 7.3, XPG5-compliant strptime becomes0G               a default strptime function in the Compaq C RTL. However, G               the previous nonpivoting XPG4-compliant strptime function$,               is retained for compatibility.  B               The pivoting is controlled by the DECC$XPG4_STRPTIMEG               logical name. To use the nonpivoting version of strptime,                either:/  G               o  Define DECC$XPG4_STRPTIME to any value before invoking !                  the application.A  I                                                  Programming Features 5-3s 3              Programming Features.     5.4 Compaq C Run-Time Library Enhancements                  OR   C           o  Call the nonpivoting strptime directly as the functions               decc$strptime_xpg4.  @     5.4.2 Limitation of Eight Nested Directory Levels Was Lifted           (Alpha)   C           The Compaq C RTL I/O subsystem was enhanced to remove the C           restriction of eight nested directory levels for an ODS-5vE           device. This affects Compaq C RTL functions such as access,e*           mkdir, opendir, rmdir, and stat.  C     5.4.3 Improved Support for Extended File Specifications (Alpha)c  ?           The following sections describe improved Compaq C RTLf3           support for extended file specifications.   A     5.4.3.1 Compaq C RTL Supports Case Preservation in File Names   ?           Programs linked against the Compaq C Run-Time LibraryeA           DECC$SHR can now preserve the case of file names on ODSdE           level 5 disks. This applies when creating or reporting filerE           names. By default, this feature is disabled. To enable thisI/           feature, enter the following command:   0           $ DEFINE DECC$EFS_CASE_PRESERVE ENABLE  ?           If file names are all in uppercase, use the followinglB           command to convert the names to lowercase when reporting!           the name in UNIX style:N  /           $ DEFINE DECC$EFS_CASE_SPECIAL ENABLE   =           If file names are not all in uppercase, then DEFINE 6           DECC$EFS_CASE_SPECIAL ENABLE preserves case.  E           The commands to disable the preceding logical-name settingsi           are:  1           $ DEFINE DECC$EFS_CASE_PRESERVE DISABLEt0           $ DEFINE DECC$EFS_CASE_SPECIAL DISABLE  A           The setting for the DECC$EFS_CASE_SPECIAL logical name,c?           if not set to DISABLE, supersedes any setting for theU.           DECC$EFS_CASE_PRESERVE logical name.  >           The DECC$EFS_CASE_PRESERVE and DECC$EFS_CASE_SPECIALB           logicals are checked only once per image activation, not"           on a file-by-file basis.       5-4 Programming Features l  e      I                                                      Programming FeaturesbI                                5.4 Compaq C Run-Time Library Enhancementsa    G         5.4.3.2 Most C RTL Functions Now Accept Long OpenVMS File Namesr$                 As Arguments (Alpha)  D               For OpenVMS Alpha Version 7.2, some basic Compaq C RTLD               I/O functions (creat, stat, and the functions from theD               open family of functions) were enhanced to accept long;               OpenVMS-style file names for an ODS-5 device.   C               For OpenVMS Alpha Version 7.3, all other Compaq C RTLoE               functions, except chdir and the functions from the execeD               family of functions, were also enhanced to accept long;               OpenVMS-style file names for an ODS-5 device.   A               All C RTL functions that accept or report full file H               specifications will process file specifications up to 4095D               bytes long, subject to the rules defined for the mediaF               format. For file specifications in OpenVMS format, thereE               are no special restrictions. In situations where a fullxI               file specification cannot be reported because the buffer is H               too short, the function attempts to report the abbreviated               name.v  >               UNIX file names have the following restrictions:  F               o  Names containing special characters, such as multipleD                  periods, caret, or multinational characters, may be                  rejected.  H               o  A function call may report failure if the output bufferB                  is not large enough to receive the full name. ForE                  OpenVMS style names, the reported name would contain G                  a file ID-abbreviated name. There is no representation ?                  of file ID-abbreviated names defined for UNIX.a  E         5.4.4 Compaq C RTL Supports Exact Case Argv Arguments (Alpha)l  B               Nonquoted command-line arguments passed to C and C++E               programs (argv arguments) can now optionally have their I               case preserved, rather than being lowercased as in previous                versions.   3               By default, this feature is disabled.   B               To enable this case preservation feature, define theD               logical name DECC$ARGV_PARSE_STYLE to "ENABLE" and setI               the process-level DCL parse style flag to "EXTENDED" in the *               process running the program:  I                                                  Programming Features 5-5a m  h           Programming Features.     5.4 Compaq C Run-Time Library Enhancements    /           $ DEFINE DECC$ARGV_PARSE_STYLE ENABLE ,           $ SET PROCESS/PARSE_STYLE=EXTENDED  @           Enabling this feature also ensures that the image name5           returned in argv[0] is also case-preserved.<  ?           To disable this feature, use any one of the followingS           commands:   0            $ SET PROCESS/PARSE_STYLE=TRADITIONAL             or  7           $ DEFINE/SYSTEM DECC$ARGV_PARSE_STYLE DISABLE              or  *           $ DEASSIGN DECC$ARGV_PARSE_STYLE  A           The value of the DECC$ARGV_PARSE_STYLE logical is case-            insensitive.  B     5.4.5 Compaq C RTL Can Implicitly Open Files for Shared Access  D           The Compaq C RTL was enhanced to open all files for sharedE           access as if the "shr=del,get,put,upd" option was specified %           in the open* or creat call.   D           To enable this feature, define the logical name DECC$FILE_;           SHARING to the value "ENABLE". The value is case-            insensitive.  :           DECC$FILE_SHARING is checked only once per image2           activation, not on a file-by-file basis.  ?     5.4.6 Alternate Way of Translating UNIX File Specifications   A           The Compaq C RTL was enhanced to allow interpreting theiE           leading part of a UNIX-style file specification as either a -           subdirectory name or a device name.C  E           The default translation of a "foo/bar" UNIX-style name to ah7           "foo:bar" VMS-style name remains the default.e  C           To translate a "foo/bar" UNIX-style name to a "[.foo]bar"NB           VMS-style name, define the logical name DECC$DISABLE_TO_,           VMS_LOGNAME_TRANSLATION to ENABLE.  A           DECC$DISABLE_TO_VMS_LOGNAME_TRANSLATION is checked only A           once per image activation, not on a file-by-file basis.h       5-6 Programming Features e  d      I                                                      Programming Features I                                5.4 Compaq C Run-Time Library Enhancementse             5.4.7 New Functions   C               The Compaq C RTL has added the following functions in."               OpenVMS Version 7.3:                 fchown               link               utime                utimes               writev  6         5.5 Fortran Support for 64-Bit Address (Alpha)  F               Support has been added to OpenVMS Alpha to allow FortranD               developers to use static data in 64-bit address space.  G               For more information about how to use this feature, refero+               to the Fortran documentation.m  ,         5.6 Large Page-File Sections (Alpha)  D               Page-file sections are used to store temporary data inH               private or global (shared) sections of memory. In previousH               releases of OpenVMS Alpha, the maximum amount of data thatG               could be backed up to page files was 32 GB per process (4EF               process page files, each 8 GB) and 504 GB per system (63%               page files, each 8 GB).E  E               With OpenVMS Alpha Version 7.3, the previous limits for D               page-file sections were extended significantly to takeF               advantage of larger physical memory. Now images that useG               64-bit addressing can map and access an amount of dynamicaG               virtual memory that is larger than the amount of physicall-               memory available on the system.u  I               With the new design, if a process requires additional page- H               file space, page files can be allocated dynamically. SpaceF               is no longer reserved in a distinct page file, and pagesE               are no longer bound to an initially assigned page file. G               Instead, if modified pages must be written back, they are 6               written to the best available page file.  F               Each page or swap file can hold approximately 16 millionB               pages (128 GB), and up to 254 page or swap files canE               be installed. Files larger than 128 GB are installed aso               multiple files.   I                                                  Programming Features 5-7                 Programming Features(     5.6 Large Page-File Sections (Alpha)    C           Note the following DCL command display changes and system ?           parameter changes as a result of the larger page-file_           section design:   E           o  The SHOW MEMORY/FILES display reflects the nonreservableh!              design. For example:e                 $ SHOW MEMORY/FILES  G                      System Memory Resources on 22-MAY-2000 19:04:19.67MK Swap File Usage (8KB pages):                   Index 1     Free        Size   ( DISK$ALPHASYS:[SYS48.SYSEXE]SWAPFILE.SYSK                                                   1         904         904y& DISK$SWAP:[SYS48.SYSEXE]SWAPFILE.SYS;1K                                                   2        1048        1048gK Total size of all swap files:                                          1952   K Paging File Usage (8KB pages):                 Index 2     Free        Size   & DISK$PAGE:[SYS48.SYSEXE]PAGEFILE.SYS;1K                                                 253       16888       16888e( DISK$ALPHASYS:[SYS48.SYSEXE]PAGEFILE.SYSK                                                 254       16888       16888g  K Total size of all paging files:                                       33776PK Total committed paging file usage: 3                                   1964G  E              1  Number of swap files. Begins with an index value of 1i'                 and increases in count.N  C              2  Number of page files. Begins with an index value ofp+                 254 and decreases in count.   ?              3  Total committed page file usage. As in previous E                 releases, more pages can reside in page-file sections D                 systemwide than would fit into installed page files.  B           o  The SHOW MEMORY/FILES/FULL display no longer contains@              separate usage information for page and swap files.E              Because page-file information is no longer reserved, theiE              system does not need to maintain the number of processes_E              interested in a distinct page or swap file. For example:          5-8 Programming Features v  ,      I                                                      Programming FeaturesnI                                      5.6 Large Page-File Sections (Alpha)     )                  $ SHOW MEMORY/FILES/FULL   K                          System Memory Resources on 22-MAY-2000 18:47:10.21DL Swap File Usage (8KB pages):                   Index        Free        Size( DISK$ALPHASYS:[SYS48.SYSEXE]SWAPFILE.SYSL                                                    1         904         904  L Paging File Usage (8KB pages):                 Index        Free        Size( DISK$ALPHASYS:[SYS48.SYSEXE]PAGEFILE.SYSL                                                  254       16888       16888L   Total committed paging file usage:                                    1960  B               o  System parameters PAGFILCNT and SWPFILCNT are now?                  obsolete. Up to 254 page and swap files can bei                  installed.   %         5.7 Multipath System Services3  I               The new Multipath system services provide the capability to_G               return path information and allow you to enable, disable,s:               and switch specific I/O paths to any device.  F               The concept of multiple I/O paths to storage devices wasH               introduced in OpenVMS Version 7.2-1. It is now possible toI               select more than one I/O path to a device in the event thatP*               the path in use should fail.  F               To assist in decision making when configuring a system'sA               I/O structure, the following DCL commands were madeSD               available to allow you to display I/O path informationD               and change the current settings affecting these paths:  D               o  SET DEVICE device-name/PATH=path-description-string                  /SWITCH  D               o  SET DEVICE device-name/PATH=path-description-string                  /[NO]ENABLE  2               o  SHOW DEVICE/MULTIPATH device-name  C               In OpenVMS Version 7.3, the capability to return pathaF               information and allow you to enable, disable, and switchH               specific I/O paths to any device is now implemented in the,               following new system services:  %               o  SYS$DEVICE_PATH_SCAN   I                                                  Programming Features 5-9                 Programming Features!     5.7 Multipath System Services     >              This service returns path information for a givenC              Multipath I/O device. Each call to the service returns B              the name of one of the paths to the device. A contextC              argument is used to maintain continuity between calls. D              This mechanism is similar to the one currently used for              SYS$GETDVI.             o  SYS$SET_DEVICE[W]  >              Use this service to switch the selected path thatD              handles I/O to a device, or to enable or disable a pathD              for future use in the event of failover. When switchingA              a path, the path change is initiated at the time then3              request is made by the system service.   E              The current functions of this service include forcing an C              immediate path switch and enabling or disabling paths.   D              A synchronous version of this service, SYS$SET_DEVICEW,A              is also provided. This service returns to the callernE              only after the path switch attempt has been made. ShouldeD              the path switch fail, an error condition is returned to              the caller.  C              Currently, $SET_DEVICE allows only one valid item list               entry.w  A           For additional information, refer to the OpenVMS System $           Services Reference Manual.  &     5.8 Multiprocess Debugging (Alpha)  E           For Version 7.3, debugger support for multiprocess programse=           has been extensively overhauled. Problems have been =           corrected and the user interface has been improved.   =           The multiprocess debugging enhancements include thee           following features:r  B           o  Greater control over individual process and groups of"              processes, including:  ?                 Execution of processes (or groups of processes)e@                 Suspension of processes (or groups of processes)C                 Exiting processes (or groups of processes), with orV.                 without exit handler execution  ?           o  Ability to create user-defined groups of processesr       5-10 Programming Featuresn o  g      I                                                      Programming Features I                                        5.8 Multiprocess Debugging (Alpha)     F               o  Easier to start a multiprocess debugging session; theD                  default configuration of the kept debugger is for a%                  multiprocess sessiont  F               o  Applications that use $HIBER WAIT (LIB$WAIT, $SCHDWK,A                  and so on) can now be debugged in a multiprocess."                  debugging session  =               These enhancements make it much easier to debugt$               multiprocess programs.  ?         5.9 Performance Application Programming Interface (API)d  E               The Performance Application Programming Interface (API)CD               provides a documented functional interface-the $GETRMIG               system service-that allows performance software engineersfD               to access a predefined list of performance data items.  F               For more information about $GETRMI, refer to the OpenVMS%               System Services Manual.w  B         5.10 POLYCENTER Software Installation Utility Enhancements  I               Table 5-1 shows the changes made to the product descriptionvE               language (PDL) for the POLYCENTER Software InstallationR               utility.  I               Table_5-1_PDL_Changes______________________________________   I               Statement_____________Description__________________________e  2               execute upgrade       New statement.  H               execute postinstall   Modified to execute on a reconfigure.                                     operation.  I                                                  (continued on next page)m                I                                                 Programming Features 5-11C F  A           Programming Features>     5.10 POLYCENTER Software Installation Utility Enhancements    E           Table_5-1_(Cont.)_PDL_Changes______________________________i  E           Statement_____________Description__________________________   B           file                  Refinements made to their conflictD           module                detection and resolution algorithms.E                                 For example, when a file from the kittE                                 contains the same non-zero generation ?                                 number as the same file already C                                 installed, the file from the kit isnE                                 selected to replace the file on disk. B                                 Previously, in this tie situation,@                                 the file on disk was retained to5                                 resolve the conflict.s  C           bootstrap block       Obsolete. However, the utility willhD           execute release       continue to process these statementsB           patch image           in a backward compatible manner toE           patch text            support existing kits that might have *                                 used them.  E           ___________________________________________________________lE           Function______________Description__________________________c  A           upgrade               Enhanced to fully support versionhE           ______________________range_checking.______________________-  B           The POLYCENTER Software Installation Utility Developer'sD           Guide has been extensively revised for this release. Major           improvements include:e  :           o  Updated descriptions for most PDL statements.  A           o  A comprehensive presentation on using custom command =              procedures with execute statements (added to the &              Advanced Topics chapter).  0           o  New tables, diagrams, and examples.  '     5.11 New Process Dump Tools (Alpha)e  D           OpenVMS Version 7.3 contains new tools for processing dumpC           files. Note that these new-style process dump and processcC           dump analysis tools are not compatible with the old-style C           process dumps. That is, if you have a problem you want to E           analyze with the new tools, you must generate a new process 0           dump using the new process dump image.       5-12 Programming Featurese S  y      I                                                      Programming FeaturesdI                                       5.11 New Process Dump Tools (Alpha)     <               The following sections describe the new tools.  /         5.11.1 DCL ANALYZE/PROCESS_DUMP Commando  F               The DCL ANALYZE/PROCESS_DUMP command invokes the OpenVMSF               debugger to analyze a process dump, giving you access toE               debugger commands for your analysis. In OpenVMS VersionsF               7.3, most of the old DCL ANALYZE/PROCESS_DUMP qualifiersF               have no effect. Only the /FULL and /IMAGE qualifiers areD               still valid. Both these qualifiers are still optional.  H               /FULL now causes the debugger to execute the debugger SHOWD               IMAGE, SHOW CALL, and SHOW THREAD/ALL commands after a0               process dump file has been opened.  B               /IMAGE has been renamed to /IMAGE_PATH, and is now aH               directory specification, rather than a file specification.E               /IMPAGE_PATH specifies a directory in which to look forlH               the debug symbol information files (.DSF or .EXE files, inH               that order) that belong to the process dump file. The nameF               of the symbol file must be the same as the image name inF               the process dump file. For example, for MYIMAGE.DMP, theD               debugger searches for file MYIMAGE.DSF or MYIMAGE.EXE.  F               Version 7.3 and later debuggers check for dumpfile imageF               specification and DST file link date-time mismatches and3               issue a warning if one is discovered.w  E               For more information about the DCL ANALYZE/PROCESS_DUMP=@               command, refer to the OpenVMS DCL Dictionary: A-M.  4         5.11.2 Debugger ANALYZE/PROCESS_DUMP Command  -               The debugger has a new command:o  H               ANALYZE/PROCESS_DUMP/IMAGE_PATH[=directory-spec] dumpfile.  F               This command is available only in the kept debugger. TheD               kept debugger is the image you invoke with the commandI               DEBUG/KEEP, which allows you to run and rerun programs froml)               the same debugging session.t  6               The qualifier /PROCESS_DUMP is required.  I               For more information, refer to the OpenVMS Debugger Manual.f  I                                                 Programming Features 5-13s e  f           Programming Features'     5.11 New Process Dump Tools (Alpha)b         5.11.3 Debugger SDA Commande  >           The new debugger SDA command invokes the System DumpD           Analyzer (SDA) to allow you to look at a process dump from3           within the OpenVMS debugger. For example:n              DBG> SDAs  3            OpenVMS (TM) Alpha process dump analyzer               SDA> ..            .            .            SDA> EXIT            DBG>   >           This allows you to use SDA to analyze a process dump1           without terminating a debugger session.q  E           For more information, refer to the OpenVMS Debugger Manual.o  7     5.11.4 Analyzing Process Dumps on Different Systems   C           You can analyze a process dump file on a system different C           from the one on which it was generated. However, if therea=           is a base image link date/time mismatch between thee?           generating system and analyzing system, you must copy A           SYS$BASE_IMAGE.EXE from the generating system and point @           to it with the SDA$READ_DIR logical name. For example:  K $ COPY other_node::SYS$LOADABLE_IMAGES:SYS$BASE_IMAGE.EXE my_disk$:[my_dir]mW $ DEFINE/USER SDA$READ_DIR my_disk$:[my_dir],SYS$SYSROOT:[SYS$LDR],SYS$SYSROOT:[SYSLIB] " $ ANALYZE/PROCESS_DUMP mycrash.dmp  B           For threaded process dump analysis on a system different@           from the one on which it was generated, it may also beA           necessary to copy and logically point to the generatingf@           system's PTHREAD$RTL and PTHREAD$DBGSHR (POSIX Threads0           Library debug assistant). For example:  K $ COPY other_node::SYS$LOADABLE_IMAGES:SYS$BASE_IMAGE.EXE my_disk$:[my_dir]e> $ COPY other_node::SYS$SHARE:PTHREAD$RTL.EXE my_disk$:[my_dir]A $ COPY other_node::SYS$SHARE:PTHREAD$DBGSHR.EXE my_disk$:[my_dir]tW $ DEFINE/USER SDA$READ_DIR my_disk$:[my_dir],SYS$SYSROOT:[SYS$LDR],SYS$SYSROOT:[SYSLIB] : $ DEFINE/USER PTHREAD$RTL my_disk$:[my_dir]PTHREAD$RTL.EXE@ $ DEFINE/USER PTHREAD$DBGSHR my_disk$:[my_dir]PTHREAD$DBGSHR.EXE" $ ANALYZE/PROCESS_DUMP mycrash.dmp     5-14 Programming Featuresr r         I                                                      Programming FeaturesaI                                       5.11 New Process Dump Tools (Alpha)w    %         5.11.5 Forcing a Process Dumpe  ?               You can force a process dump with the DCL commandaD               SET PROCESS/DUMP=NOW process-spec. This command causesH               the contents of the address space occupied by process-specH               to be written immediately to the file named image-name.DMPE               in the current directory (image-name is the same as the                file name).m  A               For more information about the DCL SET PROCESS/DUMP @               command, refer to the OpenVMS DCL Dictionary: N-Z.  ?         5.11.6 Process Dumps: Security and Diskquota Guidelines   F               A process dump is either complete or partial. A completeI               process dump contains all of process space and all process-OF               pertinent data from system space. A partial process dumpE               contains only user-readable data from process space andxG               only those data structures from system space that are not H               deemed sensitive. Privileged or protected data, such as anI               encryption key in third-party software, might be considered                sensitive.  H               In general, nonprivileged users should not be able to readG               complete process dumps, and by default they cannot do so.2H               However, certain situations require nonprivileged users toF               be able to read complete process dumps. Other situationsG               require enabling a user to create a complete process dump I               while at the same time preventing that user from being ables0               to read the complete process dump.  B               By default, process dumps are written to the currentG               default directory of the user. The user can override thisoE               by defining the logical name SYS$PROCDMP to identify anrI               alternate directory path. Note that the name of the processrH               dump file is always the same as the name of the main imageD               at the time the process dump is written, with the file               extension .DMP.y              I                                                 Programming Features 5-15F    p           Programming Features'     5.11 New Process Dump Tools (Alpha)a    '     5.11.6.1 Special Rights Identifierse  A           You can use the new rights identifier IMGDMP$READALL totE           allow a nonprivileged user to read a complete process dump.aA           You can use the new rights identifier IMGDMP$PROTECT to E           protect a complete process dump from being read by the user A           that created the process dump. These rights identifiers6D           are created during the installation of OpenVMS Version 7.3B           by the image SYS$SYSTEM:IMGDMP_RIGHTS.EXE, which is also@           run automatically during system startup to ensure thatD           these rights identifiers exist with the correct values and           attributes.   D           If these rights identifiers have been deleted, you can runE           SYS$SYSTEM:IMGDMP_RIGHTS.EXE to recreate them. For example:   $       $ RUN SYS$SYSTEM:IMGDMP_RIGHTSP       %PROCDUMP-I-CREATED, rights identifier IMGDMP$READALL successfully createdP       %PROCDUMP-I-CREATED, rights identifier IMGDMP$PROTECT successfully created  9           Note that IMGDMP$READALL has no attributes, butw@           IMGDMP$PROTECT is created with the RESOURCE attribute.  /     5.11.6.2 Privileged Users and Process Dumpsp  E           For this discussion, a privileged user is one who satisfiesr*           one of the following conditions:  >           o  Has one or more of the privileges CMKRNL, CMEXEC,'              SYSPRV, READALL, or BYPASSd  A           o  Is a member of a system UIC group (by default [10,n]dB              or lower). Such users are treated as though they hold              SYSPRV privilege.  @           Holders of CMKRNL or CMEXEC can write complete processB           dumps. Holders of any of the other privileges can read a4           process dump wherever it has been written.  2     5.11.6.3 Nonprivileged Users and Process Dumps  B           To allow a nonprivileged user to write and read completeC           process dumps, grant the rights identifier IMGDMP$READALLhC           to the user. If the IMGDMP$READALL rights identifier doestB           not exist, run the image SYS$SYSTEM:IMGDMP_RIGHTS.EXE toA           create it (see Section 5.11.6.1). Then use AUTHORIZE to ?           grant the rights identifier to the user. For example:        5-16 Programming Featuresa i  t      I                                                      Programming FeatureswI                                       5.11 New Process Dump Tools (Alpha)t    L                   $ DEFINE /USER SYSUAF SYS$SYSTEM:SYSUAF.DAT  !if necessary,                   $ RUN SYS$SYSTEM:AUTHORIZE>                   UAF> GRANT /IDENTIFIER IMGDMP$READALL <user>                   UAF> EXITt  D               Note that the user must log out and log in again to beI               able to receive the rights identifier. A nonprivileged uservF               with rights identifier IMGDMP$READALL can read and write9               complete process dumps without restriction.i  )         5.11.6.4 Protecting Process Dumpss  D               You can allow a nonprivileged user to write a completeE               process dump and at the same time prevent the user fromcF               reading the process dump just written. To do so, perform&               the following procedure:  H               1. If the IMGDMP$PROTECT rights identifier does not exist,H                  run the image SYS$SYSTEM:IMGDMP_RIGHTS.EXE to create it(                  (see Section 5.11.6.1).  D               2. Create a protected directory with rights identifier-                  IMGDMP$PROTECT. For example:p  6               $ CREATE /DIRECTORY DKA300:[PROCDUMPS] -E               /PROTECTION=(S:RWE,O:RWE,G,W) /OWNER_UIC=IMGDMP$PROTECTn;               $ SET SECURITY DKA300:[000000]PROCDUMPS.DIR -eP               /ACL=((DEFAULT_PROTECTION,SYSTEM:RWED,OWNER:RWED,GROUP:,WORLD:), ->               (IDENTIFIER=IMGDMP$PROTECT,ACCESS=READ+WRITE), -;               (IDENTIFIER=IMGDMP$PROTECT,OPTIONS=DEFAULT, - :               ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL), -$               (CREATOR,ACCESS=NONE))  G               3. Define protected logical name SYS$PROTECTED_PROCDMP too?                  point to the protected directory. For example:   P        $ DEFINE /SYSTEM /EXECUTIVE_MODE SYS$PROTECTED_PROCDMP DKA300:[PROCDUMPS]  F                  If DISKQUOTA is to be used on the disk containing theG                  protected directory, specify the maximum disk space to 8                  be used for process dumps. For example:        I                                                 Programming Features 5-17o    p           Programming Features'     5.11 New Process Dump Tools (Alpha)e    $              $ RUN SYS$SYSTEM:SYSMANC             SYSMAN> DISKQUOTA CREATE /DEVICE=DKA300  ! if necessaryeC             SYSMAN> DISKQUOTA ENABLE /DEVICE=DKA300  ! if necessarycP             SYSMAN> DISKQUOTA ADD IMGDMP$PROTECT /DEVICE=DKA300 /PERMQUOTA=10000C             SYSMAN> DISKQUOTA REBUILD /DEVICE=DKA300 ! if necessary              SYSMAN> EXIT  D              _______________________ Caution _______________________  C              Do not grant IMGDMP$PROTECT to any user. It is grantedn?              and revoked as needed by SYS$SHARE:IMGDMP.EXE froms<              executive mode while writing a process dump. If>              you grant it permanently to a user, that user hasA              access to all process dumps written to the protected               directory.m  C              ______________________________________________________   C           You can choose to set up additional ACLs on the protected A           directory to further control which users are allowed to -           read and write process dumps there.t  <           Note that to take a process dump when the image is:           installed with elevated privileges or belongs to:           a protected subsystem, the user must hold CMKRNL@           privilege, and is by definition a privileged user (see           Section 5.11.6.2).  !     5.12 RMS Locking Enhancementsa  D           This section introduces the new Record Management Services6           (RMS) enhancements provided in this release.  7     5.12.1 RMS Locking Performance Enhancements (Alpha)   A           The following sections describe RMS locking performance_D           enhancements that are in OpenVMS Alpha Version 7.2-1H1 and!           in OpenVMS Version 7.3.                    5-18 Programming Featuresn           I                                                      Programming Features I                                             5.12 RMS Locking Enhancements     4         5.12.1.1 RMS Global Buffer Read-Mode Locking  D               In the RMS run-time processing environment, the use ofC               global buffers can minimize I/O operations for sharedeE               files. This release introduces read-mode bucket locking_I               that minimizes locking for shared access to global buffers.e%               This new functionality:   E               o  Allows concurrent read access to the global buffers. I                  Accesses are no longer serialized, waiting to acquire an 2                  exclusive lock for a read access.  E               o  Caches the read-mode lock as a system lock, which istE                  retained over accesses and only lowered to null when F                  the lock is blocking an exclusive write request. ThisC                  functionality significantly reduces both local and D                  remote lock request traffic (the number of $ENQ andG                  $DEQ system service calls) as well as associated IPL-8 E                  spinlock activity and System Communications Servicesc.                  (SCS) messages for a cluster.  G               o  Does not increase lock resource names or the number of >                  active system or process locks on the system.  E               o  Is functionally compatible in mixed version clusters ;                  that include both Alpha and VAX computers._  ?               This new functionality applies to read operationsnD               (using the $GET and $FIND services) for all three fileG               organizations: sequential, relative, and indexed. It also_G               applies to a write operation (using the $PUT service) forEE               the read accesses used for index buckets the first timen2               through an index tree for the write.  F               You do not need to make changes to existing applicationsF               to implement the read-only global bucket locks. However,I               global buffers must be set on a data file to take advantage H               of the enhancement. Use the following DCL command, where n'               is the number of buffers:s  3               $ SET FILE/GLOBAL_BUFFER=n <filename>o  E               For information about specifying the number of buffers,w>               refer to the OpenVMS DCL Dictionary. For generalB               information about using global buffers, refer to theD               section entitled Using Global Buffers for Shared Files8               in the Guide to OpenVMS File Applications.  I                                                 Programming Features 5-19                 Programming Features!     5.12 RMS Locking Enhancementsu    @           In a mixed cluster environment where there may be highC           contention for specific buckets, the Alpha nodes that are E           using read-mode global bucket locking may dominate accesses D           to write-shared files, thereby preventing timely access by           other nodes.  >           With the new /CONTENTION_POLICY=keyword qualifier to@           the SET RMS_DEFAULT command, you can specify the level@           of locking fairness at the process or system level forB           environments that experience high contention conditions.  ;           For more information about using the /CONTENTION_ @           POLICY=keyword qualifier, refer to the SET RMS_DEFAULT0           section of the OpenVMS DCL Dictionary.  +     5.12.1.2 No Query Record Locking Option   E           This release introduces new functionality that can minimizeMC           record locking for read accesses to shared files, thereby @           avoiding the processing associated with record locking$           calls to the Lock Manager.  B           In previous releases, if a file is opened allowing write@           sharing, an exclusive record lock is taken out for all?           record operations (both read and write). ApplicationsiB           may obtain record locking modes other than the exclusiveD           lock (default) by specifying certain options to the RAB$L_C           ROP field. However, all the options involve some level ofcC           record locking. That is, the options require $ENQ or $DEQa3           system service calls to the Lock Manager.   C           The user record locking options include the RAB$V_NLK (noDB           lock) query locking option, which requests that RMS takeB           out a lock to probe for status and not hold the lock for@           synchronization. If the lock is not granted (exclusiveB           lock held) and the read-regardless (RAB$V_RRL) option isC           not set, the record access fails with an RMS$_RLK status.eE           Otherwise, the record is returned with one of the followingm           statuses:E  (           o  RMS$_SUC - No other writers  =           o  RMS$_OK_RLK - Record can be read but not written   ?           o  RMS$_OK_RRL - Exclusive lock is held (lock request B              denied) but the read-regardless (RAB$V_RRL) option is              set       5-20 Programming Featuresm    t      I                                                      Programming FeatureslI                                             5.12 RMS Locking Enhancementsg    H               When only the RAB$V_NLK option is specified, record accessB               can be denied. When both the RAB$V_NLK and RAB$V_RRLE               options are specified, an application can guarantee thehF               return of any record with a success or alternate success               status.T  I               This release introduces the no query record locking option,sC               which allows applications to read records (using $GET D               or $FIND services) without any consideration of record#               locking. This option:f  9               o  Does not make a call to the Lock Managerl  H               o  Is equivalent to both RAB$V_NLK and RAB$V_RRL being setG                  except that the RMS$_OK_RLK or RMS$_OK_RRL status willw                   not be returned  C               This functionality is independent of bucket locks. ItfG               applies to both local and global buffers and to all threeIE               file organizations (sequential, relative, and indexed).S  H               Three alternate methods for specifying the no query record7               locking option are outlined in Table 5-2.L  !               Note the following:   A               o  The first method allows the option to be enabled H                  externally, potentially without any application change.  F               o  You should use any of the methods only as appropriateE                  for the application. In particular, you should checkiE                  for any dependency in an existing application on the_E                  alternate success status RMS$_OK_RLK or RMS$_OK_RRL.E                        I                                                 Programming Features 5-21U    $           Programming Features!     5.12 RMS Locking EnhancementsB    >     Table 5-2 Methods Available for Specifying No Query RecordE     __________Locking________________________________________________/  E     To...______________________Use_This_Method...____________________   A     Disable query record       Enter the following DCL command toeC     locking at the process or  request that RMS use no query record B     system level.              locking for any read operation withC                                both RAB$V_NLK and RAB$V_RRL optionsE:                                set in the RAB$L_ROP field:  L                                $ SET RMS_DEFAULT/QUERY_LOCK=DISABLE[/SYSTEM]  >                                Keys on RAB$V_NLK and RAB$V_RRL@                                options in existing applications.  E     Enable no query record     Set the RAB$V_NQL option in the RAB$W_t+     locking on a per-record    ROP_2 field.nD     read operation.            The RAB$V_NQL option takes precedence  E                                over all other record locking options.pD                                Use only if the current read ($GET orE                                $FIND) operation is not followed by ann7                                $UPDATE or $DELETE call.   E     Enable no query record     Set the FAB$V_NQL option in the FAB$B_ C     locking at the file        SHR field to request that RMS use no B     level.                     query locking for the entire periodC                                the file is open for any read recorde@                                operation with both RAB$V_NLK andE                                RAB$V_RRL options set in the RAB$L_ROPs%                                field.o  ?                                This option can be used with any A                                combination of the other availableeA                                FAB$B_SHR sharing options. Keys onpA                                RAB$V_NLK and RAB$V_RRL options in E     ___________________________applications._________________________d  E           RMS precedence for the no query record locking option is ast           follows:  >           o  The RAB$V_NQL option set in the RAB$W_ROP_2 field  B           o  At file open (and applied, if RAB$V_NLK and RAB$V_RRL-              are set for the read operation):a  ?              -  The FAB$V_NQL option set in the FAB$B_SHR fieldh       5-22 Programming Features     t      I                                                      Programming FeaturesPI                                             5.12 RMS Locking Enhancementsn    I                  -  The SET RMS_DEFAULT/QUERY_LOCK=DISABLE setting at theD!                     process level1  E                  -  The SET RMS_DEFAULT/QUERY_LOCK=DISABLE setting attH                     the system level. If the process /QUERY_LOCK settingG                     equals SYSTEM_DEFAULT (the default when the processME                     is created), RMS uses the system specified value.r  A               For more information, see OpenVMS Record Managementt(               Services Reference Manual.  C         5.12.2 Record Locking Options to Control Deadlock DetectionS  I               RMS uses the distributed Lock Manager ($ENQ system service)s!               for record locking.   C               To help prevent false deadlocks, the distributed Lock A               Manager uses the following flags for lock requests:e  I               ___________________________________________________________rI               Flag[1]__________Purpose___________________________________E  E               LCK$M_NODLCKWT   When set, the lock management services-G                                do not consider this lock when trying to :                                detect deadlock conditions.  E               LCK$M_NODLCKBLK  When set, the lock management services2D                                do not consider this lock as blockingI                                other locks when trying to detect deadlockn*                                conditions.I               [1]Improper_use_of_these_flags_can_result_in_the_lock______ A               management services ignoring genuine deadlocks. For E               complete flag information, refer to the $ENQ section of I               the_OpenVMS_System_Services_Reference_Manual:_A-GETUAI.____t  F               In previous releases, RMS did not set these flags in its#               record lock requests.w  D               With this release, you can optionally request that RMSD               set these flags in record lock requests by setting theI               corresponding options RAB$V_NODLCKWT and RAB$V_NODLCKBLK inDI               the new RAB$W_ROP_2 field. For more information about using F               these options, refer to the flag information in the $ENQF               section of the OpenVMS System Services Reference Manual:               A-GETUAI.f  I                                                 Programming Features 5-23                 Programming Features     5.13 OpenVMS RegistryF         5.13 OpenVMS Registry   @           Beginning in OpenVMS Version 7.3, the $REGISTRY systemD           service and the OpenVMS Registry server have been enhancedE           to use the Intra-Cluster Communications (ICC) protocol. ICCTB           provides a high-performance communication mechanism thatD           is ideal for large transfers. Using ICC eases restrictionsC           on the amount of data that can be transferred between theuA           $REGISTRY system service and the Registry server. TheseaA           restrictions previously prevented large key values fromiD           being stored and retrieved, and prevented full searches ofB           large databases. The changes made in OpenVMS Version 7.3B           result in an incompatibility between the OpenVMS VersionC           7.2 $REGISTRY service and Registry server and the OpenVMS E           Version 7.3 $REGISTRY service and Registry server. However,g?           these changes substantially benefit OpenVMS customersSA           in this release and in future releases, when we plan too,           further reduce these restrictions.  >           Also in OpenVMS Version 7.3, registry operations areA           client/server based, and as such require some length ofRD           time for the server to respond to a request. If the serverA           is too busy or the timeout value is too small, or both,.?           the server will not respond in time and the $REGISTRY:D           service will return a REG$_NORESPONSE error. This does notC           necessarily mean that the operation failed; it only meansFA           that the server was not able to respond before the time-A           expired. Most operations complete immediately. However,rC           Compaq recommends that you specify the timeout value be at           minimum of 5 seconds.e  <           The new format of the $registry system service is:  J           $REGISTRY [efn], func, [ntcredentials], itmlst, [iosb] [,astadr]           [,astprm] [,timeout]  ;           Note that astadr, astprm and timeout are optionaltB           arguments. These optional arguments cannot be defaulted,D           which means that to specify the timeout argument, you must@           specify astadr and astprm (or specify them as 0). SomeB           languages, such as Bliss and Macro, provide macros to do           this for you.T           5-24 Programming Featuresr           I                                                      Programming FeaturesMI                                                     5.13 OpenVMS Registry     &         5.13.1 REG$CP Registry Utility  B               The REG$CP Registry Utility has been enhanced to useA               the timeout argument. REG$CP commands now support arF               /WAIT=numberofseconds qualifier, allowing you to specifyC               the number of seconds to wait for the Registry Server E               to respond to the command. /WAIT is negatable (by using B               /NOWAIT). However, like the timeout argument, CompaqA               recommends that you specify a minimum of 5 seconds._  C               The REG$CP Registry Utility has also been enhanced to D               display security descriptors. The LIST command can nowC               be used to display the security descriptor associateda?               with a particular key. This includes the securityrH               descriptor structure itself, and may also include SecurityF               Identifiers (SIDs), System Access-Control Lists (SACLs),F               and Discretionary Access-Control Lists (DACLs). You mustH               have access to the key to display the security descriptor;A               in other words, you must have proper credentials to D               read the security information, or you must be suitably               privileged.e  E               For more information, refer to the OpenVMS ConnectivityfF               Developer Guide, which is available on the OpenVMS Alpha3               CD-ROM in directory [COM_ALPHA_011A].   ;         5.14 Alpha SDA Commands, Parameters, and Qualifiers   I               The OpenVMS Version 7.3 software release offers a number of I               new Alpha SDA commands, parameters, and qualifiers. OpenVMS2H               Version 7.3 also offers many new parameters and qualifiers$               for existing commands.  G               For more detailed information, refer to the OpenVMS Alpha +               System Analysis Tools Manual.-  %         5.14.1 New Alpha SDA Commandsm  I               The following section lists and defines the new System DumpwE               Analyzer commands with their parameters and qualifiers.h          I                                                 Programming Features 5-25q e              Programming Features7     5.14 Alpha SDA Commands, Parameters, and Qualifiersm         5.14.1.1 DUMPc  >           The DUMP command displays the contents of a range ofD           memory formatted as a comma-separated variable (CSV) list,2           suitable for inclusion in a spreadsheet.  >           The following table shows the parameter for the DUMP           command:  E           ___________________________________________________________lE           Parameter_______Meaning____________________________________o  E           range           The range of locations to be displayed. The D                           range is specified in one of the following"                           formats:E                           ___________________________________________aE                           Format__Meaning____________________________p  C                           m:n     Range from address m to address nt+                                   inclusive$  E                           m;n_____Range_from_address_m_for_n_bytes___s  E           ___________________________________________________________i  ?           The following table shows the qualifiers for the DUMPa           command:                                         5-26 Programming Features     t      I                                                      Programming Features I                       5.14 Alpha SDA Commands, Parameters, and Qualifiers                                                                                               I                                                 Programming Features 5-27  b  e           Programming Features7     5.14 Alpha SDA Commands, Parameters, and Qualifierst  E           ___________________________________________________________OE           Qualifier_______________________Meaning____________________n  E           /COUNT=[{ALL|records}]          Gives the number of recordsa>                                           to be displayed. TheC                                           default is to display all 2                                           records.  A           /DECIMAL                        Outputs data as decimaln1                                           values.h  C           /FORWARD                        Causes SDA to display the @                                           records in the historyE                                           buffer in ascending address E                                           order. This is the default.=  E           /HEXADECIMAL                    Outputs data as hexadecimali=                                           values. This is they2                                           default.  C           /INDEX_ARRAY [={LONGWORD        Indicates to SDA that theuE           (default)|QUADWORD}]            range of addresses given iseE                                           a vector of pointers to the B                                           records to be displayed.B                                           The vector can be a list@                                           of longwords (default)C                                           or quadwords. The size ofoD                                           the range must be an exact@                                           number of longwords orC                                           quadwords as appropriate..  @           /INITIAL_POSITION ={ADDRESS=addrIndicatesDtouSDArwhichC                                           record is to be displayedsC                                           first. The default is the D                                           lowest addressed record ifC                                           /FORWARD is used, and the B                                           highest addressed recordB                                           if /REVERSE is used. TheA                                           initial position may befB                                           given as a record numberB                                           within the range, or theE                                           address at which the record 5                                           is located.   C           /LONGWORD                       Outputs each data item asrA                                           a longword. This is ther2                                           default.  ?           /PHYSICAL                       Indicates to SDA thatsB                                           all addresses (range andA                                           /or start position) are @                                           physical addresses. ByD     5-28 Programming Features             default, virtual addresses6                                           are assumed.  E           /QUADWORD                       Outputs each data item as a 3                                           quadword.h  D           /RECORD_SIZE=size               Indicates the size of eachC                                           record within the historyhC                                           buffer, the default beingaC                                           512 bytes. Note that thiswB                                           size must exactly divide@                                           into the total size ofA                                           the address range to bebC                                           displayed, unless /INDEX_ =                                           ARRAY is specified.   C           /REVERSE                        Causes SDA to display thep@                                           records in the history>                                           buffer in descendingE           ________________________________address_order._____________o           I                                                      Programming FeatureslI                       5.14 Alpha SDA Commands, Parameters, and Qualifierse             5.14.1.2 SET SYMBOLIZE  I               The SET SYMBOLIZE command enables or disables symbolizationnB               of addresses in the display from an EXAMINE command.  F               The following shows the parameters for the SET SYMBOLIZE               command:  I               ____________________________________________________________I               Parameter___Meaning________________________________________   <               ON          Enables symbolization of addresses  I               OFF_________Disables_symbolization_of_addresses____________a  7               There are no qualifiers for this command._           5.14.1.3 SHOW MEMORY  I               The SHOW MEMORY command displays the availability and usage_C               of those memory resources that are related to memory.c  E               There are no parameters for this command. The followingrI               shows the qualifiers for the SHOW MEMORY command, which are 7               the same as for the existing DCL command:R                                        I                                                 Programming Features 5-29D U  Q           Programming Features7     5.14 Alpha SDA Commands, Parameters, and QualifiersR                                                                                                   5-30 Programming Featureso n  e      I                                                      Programming Features I                       5.14 Alpha SDA Commands, Parameters, and Qualifiers   I               ___________________________________________________________oI               Qualifier_________Meaning__________________________________r  C               /ALL              Displays all available information; E                                 that is, information displayed by theoC                                 /FILES, /PHYSICAL_PAGES, /POOL, and F                                 /SLOTS qualifiers. This is the default(                                 display.  A               /BUFFER_OBJECTS   Displays information about system A                                 resources used by buffer objects.   F               /CACHE            Displays information about the VirtualF                                 I/O Cache facility. The cache facilityG                                 information is displayed as part of the F                                 SHOW MEMORY and SHOW MEMORY/CACHE/FULL)                                 commands.V  E               /FILES            Displays information about the use of_G                                 each paging and swapping file currentlyg*                                 installed.  E               /FULL             Displays additional information aboutAD                                 each pool area or paging or swappingH                                 file currently installed, when used withG                                 the /POOL or the /FILES qualifier. This F                                 qualifier is ignored unless the /FILESC                                 or the /POOL qualifier is specifiednE                                 explicitly. When used with the /CACHEED                                 qualifier, /FULL displays additionalH                                 information about the use of the Virtual3                                 I/O Cache facility.i  >               /GH_REGIONS       Displays information about theC                                 granularity hint regions (GHR) thatiB                                 have been established. For each ofG                                 these regions, information is displayed2A                                 about the size of the region, the D                                 amount of free memory, the amount ofG                                 memory in use, and the amount of memorydH                                 released to OpenVMS from the region. TheG                                 granularity hint regions information is_F                                 also displayed as part of SHOW MEMORY,E                                 SHOW MEMORY/ALL, and SHOW MEMORY/FULLe)                                 commands.   H               /PHYSICAL_PAGES   Displays information about the amount ofF                                 physical memory and the number of free3                                 and modified pages.   D               /POOL             Displays information about the usageC                                 of each dynamic memory (pool) area, I                                 including the amProgrammingeFeaturesn5-31fH                                 the size of the largest contiguous block-                                 in each area.   A               /RESERVED         Displays information about memory -                                 reservations.u  >               /SLOTS            Displays information about theG                                 availability of partition control block I               __________________(PCB)_vector_slots_and_balance_slots.____  e  h           Programming Features7     5.14 Alpha SDA Commands, Parameters, and Qualifiers$         5.14.1.4 SHOW RADB  E           The SHOW RAD command displays the settings and explanationsu=           of the RAD_SUPPORT system parameter fields, and thea@           assignment of CPUs and memory to the Resource AffinityB           Domains (RADs). This command is only useful on platforms=           that support RADs. By default, the SHOW RAD command C           displays the settings of the RAD_SUPPORT system parameter            fields.s  E           The following shows the parameter for the SHOW RAD command:   E           ___________________________________________________________ E           Parameter_____Meaning______________________________________   C           number        Displays information on CPUs and memory for E           ______________the_specified_RAD____________________________   E           The following shows the qualifier for the SHOW RAD command:G  E           ___________________________________________________________oE           Qualifier___Meaning________________________________________a  D           /ALL        Displays settings of the RAD_SUPPORT parameterC                       fields and the CPU and memory assignments formE           ____________all_RADs_______________________________________        5.14.1.5 SHOW TQEh  @           The SHOW TQE command displays the entries in the TimerE           Queue. The default output is a summary display of all timeru6           queue entries (TQEs) in chronological order.  A           There are no parameters for this command. The following 8           shows the qualifiers for the SHOW TQE command:                         5-32 Programming Featuresq e  m      I                                                      Programming FeaturesrI                       5.14 Alpha SDA Commands, Parameters, and Qualifiers   I               ___________________________________________________________ I               Qualifier_________Meaning__________________________________e  H               /ADDRESS=n        Outputs a detailed display of the TQE at5                                 the specified address.  F               /ALL              Outputs a detailed display of all TQEs  C               /BACKLINK         Outputs the display of TQEs, eithercF                                 detailed (/ALL) or brief (default), inD                                 reverse order, starting at the entry8                                 furthest into the future  C               /PID=n            Limits the display of the TQEs thateE                                 affect the process with the specified ,                                 internal PID  H               /ROUTINE=n        Limits the display of the TQEs for whichI               __________________the_specified_address_is_the_fork_PC_____T           5.14.1.6 UNDEFINEF  E               The UNDEFINE command causes SDA to remove the specified +               symbol from its symbol table.   I               The following shows the parameter for the UNDEFINE command:G  I               ___________________________________________________________hI               Parameter_________Meaning__________________________________r  D               symbol            The name of the symbol to be deletedI                                 from SDA's symbol table. A symbol name is I               __________________required.________________________________   7               There are no qualifiers for this command.p  B         5.14.2 New Parameters and Qualifiers for Existing Commands  H               The following section lists and defines new parameters and/               qualifiers for existing commands.T           5.14.2.1 REPEAT   A               The REPEAT command has the following new parameter:   I               ___________________________________________________________tI               Parameter_____Meaning______________________________________r  D               count         The number of times the previous commandF                             is to be repeated. The default is a singleI               ______________repeat.______________________________________r  A               The REPEAT command has the following new qualifier:r  I                                                 Programming Features 5-33                 Programming Features7     5.14 Alpha SDA Commands, Parameters, and Qualifiersw  E           ___________________________________________________________ E           Qualifier_________Meaning__________________________________Q  C           /UNTIL=condition  Defines a condition that terminates thefC                             REPEAT command. By default, there is nonE           __________________terminating_condition.___________________p       5.14.2.2 SEARCHs  C           The /STEPS qualifier of the SEARCH command now allows anyeC           step size. In addition to the keywords QUADWORD, LONGWORDy?           (default), WORD, or BYTE, any value can be specified.   E           ___________________________________________________________ E           Qualifier_____________________Meaning______________________   B           /STEPS={QUADWORD|LONGWORD|WORD Specifies the step factor=                                         of the search through4<           |BYTE|value}                  the specified memory?                                         range. After the SEARCH A                                         command has performed thee>                                         comparison between the?                                         value of expression andP@                                         memory location, it addsD                                         the specified step factor toA                                         the address of the memoryg?                                         location. The resultingaE                                         location is the next locationmB                                         to undergo the comparison.A                                         If you do not specify the_D                                         /STEPS qualifier, the SEARCHE                                         command uses a step factor of E           ______________________________a_longword.__________________        5.14.2.3 SET OUTPUT_  B           The SET OUTPUT command has the following new qualifiers:                       5-34 Programming Featuresm :         I                                                      Programming Features I                       5.14 Alpha SDA Commands, Parameters, and Qualifiers   I               ___________________________________________________________ I               Qualifier_________Meaning__________________________________   C               /[NO]HEADER       The /HEADER qualifier causes SDA tonI                                 include a heading at the top of each pageAH                                 of the output file. This is the default.E                                 The /NOHEADER qualifier causes SDA to_H                                 omit the page headings. Use of /NOHEADER1                                 implies /NOINDEX.   F               /SINGLE_COMMAND   Indicates to SDA that the output for aF                                 single command is to be written to theI                                 specified file and that subsequent outputpI               __________________should_be_written_to_the_terminal._______            5.14.2.4 SET PROCESS  F               The SET PROCESS command has the following new qualifier:  I               ___________________________________________________________rI               Qualifier_____Meaning______________________________________i  G               /NEXT         Causes SDA to locate the next valid processaH                             in the process list and select that process.F                             If there are no further valid processes inI               ______________the_process_list,_SDA_returns_an_error.______u           5.14.2.5 SHOW DEVICE  G               The SHOW DEVICE command has the following new qualifiers:o  I               ___________________________________________________________iI               Qualifier___Meaning________________________________________t  E                           Identifies the device by the address of its I               /CDT=address Connector Descriptor Table (CDT). This applies 8                            to cluster port devices only.  E               /PDT        Displays the Memory Channel Port Descriptor F                           Table. This qualifier is ignored for devices4                           other than memory channel.  E               /UCB=ucb-   This is a synonym for /ADDRESS=ucb-address. I               address____________________________________________________     I                                                 Programming Features 5-35                 Programming Features7     5.14 Alpha SDA Commands, Parameters, and Qualifiersi         5.14.2.6 SHOW GCT   ?           The SHOW GCT command has the following new qualifier:   E           ___________________________________________________________ E           Qualifier_______Meaning____________________________________   E           /CHILDREN       When used with /ADDRESS=n or /HANDLE=n, the C                           /CHILDREN qualifier causes SDA to display B                           all nodes in the configuration tree thatE           ________________are_children_of_the_specified_node.________        5.14.2.7 SHOW LOCK  E           The SHOW LOCK command's qualifier /STATUS has the following            new keyword:  E           ___________________________________________________________ E           Keyword_____Meaning________________________________________o  E           DPC_________Indicates_a_delete_pending_cache_lock__________l       5.14.2.8 SHOW PFN_DATA  D           The SHOW PFN_DATA command has the following new qualifier:  E           ___________________________________________________________ E           Qualifier_____Meaning______________________________________   A           /RAD          Displays data on the disposition of pagesi=           [={n|ALL}]    among the Resource Affinity Domain on E           ______________applicable_systems___________________________        5.14.2.9 SHOW POOL  A           The SHOW POOL command has the following new qualifiers:w                       5-36 Programming Featuresm    c      I                                                      Programming Features I                       5.14 Alpha SDA Commands, Parameters, and Qualifiers   I               ___________________________________________________________ I               Qualifier_________Meaning__________________________________   G               /BRIEF            Displays only general information about 7                                 pool and its addresses.   F               /CHECK            Checks all free packets for POOLCHECK-I                                 style corruption, in exactly the same way F                                 that the system does when generating a4                                 POOLCHECK crashdump.  I               /MAXIMUM_BYTES    Displays only the first n bytes of a pooln<               [=n]              packet; default is 64 bytes.  D               /STATISTICS [=    Displays usage statistics about eachD               ALL]              lookaside list and the variable freeB                                 list. For each lookaside list, itsF                                 queue header address, packet size, theG                                 number of packets, attempts, fails, and E                                 deallocations are displayed. (If pool_C                                 checking is disabled, the attempts, @                                 fails, and deallocations are notG                                 displayed.) For the variable free list,oG                                 its queue header address, the number ofrD                                 packets and the size of the smallestB                                 and largest packets are displayed.G                                 /STATISTICS can be further qualified by G                                 using either /NONPAGED, /BAP, or /PAGED E                                 to display statistics for a specifiedrE                                 pool area. (Note that for paged pool, F                                 only variable free list statistics are+                                 displayed.)   G                                 If /STATISTICS is specified without the.H                                 ALL keyword, only active lookaside listsG                                 are displayed. Use /STATISTICS = ALL tol<                                 display all lookaside lists.  G               /UNUSED           Displays only variable free packets and I               __________________lookaside_list_packets,_not_used_packets.            5.14.2.10 SHOW PROCESS  H               The SHOW PROCESS command has the following new qualifiers:    I                                                 Programming Features 5-37B E  B           Programming Features7     5.14 Alpha SDA Commands, Parameters, and Qualifiersd  E           ___________________________________________________________iE           Qualifier_____________Meaning______________________________y  D           /FID_ONLY             When used with /CHANNEL or /PROCESS_C                                 SECTION_TABLE (/PST), the /FID_ONLYnC                                 qualifier causes SDA to not attempt C                                 to translate the FID (File ID) to aoC                                 file name when invoked with ANALYZEr(                                 /SYSTEM.  ?           /GSTX=index           When used with the /PAGE_TABLESo@                                 qualifier, it causes SDA to onlyB                                 display page table entries for the8                                 specific global section.  E           /IMAGES [= ALL]       By default, /IMAGES now only displays @                                 the address of the image controlE                                 block, the start and end addresses of C                                 the image, the activation code, the B                                 protected and shareable flags, theC                                 image name, and the major and minor B                                 IDs of the image. If /IMAGES = ALLC                                 qualifier is used, it also displaysl@                                 the base, end, image offset, andC                                 section type for installed residents>                                 images in use by this process.  C           /NEXT                 Causes SDA to locate the next valid ?                                 process in the process list and A                                 select that process. It there are A                                 no further valid processes in the C                                 process list, SDA returns an error.   ?           /PST                  This is a synonym for /PROCESS_ E           ______________________SECTION_TABLE._______________________        5.14.2.11 SHOW RESOURCEn  D           The SHOW RESOURCE command has the following new qualifier:  E           ___________________________________________________________oE           Qualifier_____Meaning______________________________________   E           /OWNED________Causes_SDA_to_only_display_owned_resources___          5-38 Programming Features  o  (      I                                                      Programming FeaturessI                       5.14 Alpha SDA Commands, Parameters, and Qualifiersb              5.14.2.12 SHOW SPINLOCKS  I               The SHOW SPINLOCKS command has the following new qualifier:m  I               ___________________________________________________________SI               Qualifier_______Meaning____________________________________   F               /COUNTS         Produces a display of Acquire, Spin, andI               ________________Wait_counts_for_each_spinlock______________e           5.14.2.13 SHOW SUMMARY  G               The SHOW SUMMARY command has the following new qualifier:   I               ___________________________________________________________DI               Qualifier_________________Meaning__________________________d  H               /PROCESS_NAME=process_    Displays only processes with theI               name                      specified process name. Wildcards D                                         can be used in process_name,F                                         in which case SDA displays allG                                         matching processes. The default_I                                         action is for SDA to display data_H                                         for all processes, regardless ofI               __________________________process_name._____________________  >         5.15 New SDA Commands for the Spinlock Tracing Utility  G               The OpenVMS Version 7.3 software release includes the new_G               Spinlock Tracing utility. With the implementation of this_G               utility, you can now tell which spinlock is heavily used,fI               and who is acquiring and releasing the contended spinlocks.mD               The Spinlock Tracing utility allows a characterizationE               of spinlock usage, as well as collection of performanceTG               data for a given spinlock on a per-CPU basis. The tracingtD               ability can be enabled or disabled while the system isE               running, allowing the collection of spinlock data for ah?               given period of time without system interruption.e  F               To use the Spinlock Tracing utility, SDA has implementedA               new commands and qualifiers. These SDA commands ando2               qualifiers are described as follows:      I                                                 Programming Features 5-39_ _  _           Programming Features:     5.15 New SDA Commands for the Spinlock Tracing Utility         5.15.1 SPL LOAD   E           This command loads the SPL$DEBUG execlet. This must be done C           prior to starting spinlock tracing. It has no qualifiers.        5.15.2 SPL SHOW COLLECTd  A           This command displays the data collected for a specificp)           spinlock. It has no qualifiers.        5.15.3 SPL SHOW TRACEb  =           This command displays spinlock tracing information.,:           Table 5-3 shows the qualifiers for this command.                                                                   5-40 Programming Features            I                                                      Programming Features I                    5.15 New SDA Commands for the Spinlock Tracing Utilitys    I               Table_5-3_Qualifiers_for_the_SPL_SHOW_TRACE_Command________s  I               Qualifier_______Meaning____________________________________E  D               /SPINLOCK=spinlock Specifies the display of a specificE                               spinlock, for example, /SPINLOCK=LCKMGRe1                               or /SPINLOCK=SCHED._  >               /NOSPINLOCK     Specifies that no spinlock traceG                               information be displayed. If omitted, all D                               spinlock trace entries are decoded and(                               displayed.  D               /FORKLOCK=forklock Specifies the display of a specificF                               forklock, for example, /FORKLOCK=IOLOCK80                               or /FORKLOCK=IPL8.  >               /NOFORKLOCK     Specifies that no forklock traceC                               information be displayed. If omitted,fD                               all fork trace entries are decoded and(                               displayed.  A               /ACQUIRE        Displays any spinlock acquisitions._  @               /NOACQUIRE      Ignores any spinlock acquisitions.  =               /RELEASE        Displays any spinlock releases.   <               /NORELEASE      Ignores any spinlock releases.  ?               /WAIT           Displays any spinwait operations._  >               /NOWAIT         Ignores any spinwait operations.  G               /FRKDSPTH       Displays all invocations of fork routines E                               within the fork dispatcher. This is the &                               default.  B               /NOFRKDSPTH     Ignores all of the operations of the2                               /FRKDSPTH qualifier.  E               /FRKEND         Displays all returns from fork routines E                               within the fork dispatcher. This is the &                               default.  C               /NOFRKEND       Ignores all operations of the /FRKENDt(                               qualifier.  H               /SUMMARY        Stops the entire trace buffer and displaysD                               a summary of all spinlock and forklockD                               activity. It also displays the top ten&                               callers.  H               /CPU=n          Specifies the display of information for aG                               specific CPU only, for example, /CPU=5 orSI                               /CPU=PRIMARY. By default, all trace entriesa9                               for all CPUs are displayed.p  I               /TOP=n          Displays a differeProgrammingtFeatures 5-41CE                               top ten callers or fork PC. By default, G                               the top ten are displayed. This qualifier F                               is only useful when you also specify theI               ________________/SUMMARY_qualifier.________________________                 Programming Features:     5.15 New SDA Commands for the Spinlock Tracing Utility         5.15.4 SPL START COLLECT  =           This command accumulates information for a specific D           spinlock. Table 5-4 shows the qualifiers for this command:  E           Table_5-4_Qualifiers_for_the_SPL_START_COLLECT_Command_____   E           Qualifier_______Meaning____________________________________   @           /SPINLOCK=spinlock Specifies the tracing of a specificA                           spinlock, for example, /SPINLOCK=LCKMGR_,                           or /SPINLOCK=SCHED  =           /ADDRESS=n      Specifies the tracing of a specificsE           ________________spinlock_by_address________________________F       5.15.5 SPL START TRACE  D           This command enables spinlock tracing. Table 5-5 shows the&           qualifiers for this command.                                                       5-42 Programming Features_ _  _      I                                                      Programming Features_I                    5.15 New SDA Commands for the Spinlock Tracing Utilitys    I               Table_5-5_Qualifiers_for_the_SPL_START_TRACE_Command_______h  I               Qualifier_______Meaning____________________________________l  D               /SPINLOCK=spinlock Specifies the tracing of a specific'                               spinlock.t  D               /NOSPINLOCK     Disables spinlock tracing and does notH                               collect any spinlock data. If omitted, all3                               spinlocks are traced.e  D               /FORKLOCK=forklock Specifies the tracing of a specificF                               forklock, for example, /FORKLOCK=IOLOCK80                               or /FORKLOCK=IPL8.  D               /NOFORKLOCK     Disables forklock tracing and does notH                               collect any forklock data. If omitted, all/                               forks are traced.f  D               /BUFFER=pages   Specifies the size of the trace bufferC                               (in Alpha page units). It defaults to D                               128 pages, which is equivalent to 1MB,)                               if omitted.e  G               /ACQUIRE        Traces any spinlock acquisitions. This isu*                               the default.  @               /NOACQUIRE      Ignores any spinlock acquisitions.  G               /RELEASE        Traces any spinlock releases. This is the_&                               default.  <               /NORELEASE      Ignores any spinlock releases.  I               /WAIT           Traces any spinwait operations. This is the &                               default.  >               /NOWAIT         Ignores any spinwait operations.  E               /FRKDSPTH       Traces all invocations of fork routinesoE                               within the fork dispatcher. This is ther&                               default.  F               /NOFRKDSPTH     Ignores all of the /FRKDSPTH operations.  C               /FRKEND         Traces all returns from fork routines_E                               within the fork dispatcher. This is the &                               default.  B               /NOFRKEND       Ignores all of the operations of the0                               /FRKEND qualifier.  E               /CPU=n          Specifies the tracing of a specific CPU H                               only, for example, /CPU=5 or /CPU=PRIMARY.I               ________________By_default,_all_CPUs_are_traced.___________   I                                                 Programming Features 5-43                 Programming Features:     5.15 New SDA Commands for the Spinlock Tracing Utility         5.15.6 SPL STOP COLLECT   B           This command stops the spinlock collection, but does not6           stop spinlock tracing. It has no qualifiers.       5.15.7 SPL STOP TRACEh  A           This command disables spinlock tracing, but it does not_<           deallocate the trace buffer. It has no qualifiers.       5.15.8 SPL UNLOAD_  C           This command unloads and cleans up the SPL$DEBUG execlet.n@           Tracing is automatically disabled and the trace buffer,           deallocated. It has no qualifiers.  A           For more information, refer to the OpenVMS Alpha System_            Analysis Tools Manual.       5.16 System Services  >           The following table describes new and updated system+           services for OpenVMS Version 7.3.   A           For additional information, refer to the OpenVMS System_$           Services Reference Manual.  E           ___________________________________________________________mE           System_Service_____Documentation_Update____________________r  E           $CHECK_PRIVILEGES  The description of the 'prvadr' argument .                              has been updated.  A           $CLRAST            This service has been documented for )                              Version 7.3._  D           $DCLEXH            The description has been updated, and a:                              BASIC example has been added.  E           $DELETE_INTRUSION  This service has been updated in support 6                              of Clusterwide Intrusion.  @           $DEVICE_PATH_SCAN  This is a new service in support of'                              Multipath.t  ?           $DISMOU            The following item codes have beenwC                              added: DMT$M_MINICOPY_REQUIRED, DMT$M_.@                              MINICOPY_OPTIONAL, and DMT$M_FORCE.  ?           $EXPREG            The text for condition value, SS$_ 9                              ILLPAGCNT, has been updated.a       5-44 Programming Features  ]         I                                                      Programming FeaturesiI                                                      5.16 System Servicesd  I               ___________________________________________________________tI               System_Service_____Documentation_Update____________________   E               $GETDVI            The item codes, MT3_DENSITY and MT3_d<                                  SUPPORTED, have been added.  I                                  The item codes, DVI$_FC_NODE_NAME, DVI$_iG                                  FC_PORT_NAME, and DVI$_WWID, have beens'                                  added.   F                                  The description for the DVI$_MOUNTCNT<                                  item code has been updated.  C               $GETJPI            The following item codes have been A                                  added: JPI$_RMS_DFMBC, JPI$_RMS_ G                                  DFMBFIDX, JPI$_RMS_DFMBFREL, JPI$_RMS_ G                                  DFMBFSDK, JPI$_RMS_DFMBFSMT, JPI$_RMS_ D                                  DFMBFSUR, JPI$_RMS_DFNBC, JPI$_RMS_D                                  EXTEND_SIZE, JPI$_RMS_FILEPROT, and3                                  JPI$_RMS_PROLOGUE.   C                                  The following item codes have been F                                  added for Multithreads support: JPI$_I                                  INITIAL_THREAD_PID, JPI$_KT_COUNT, JPI$_ D                                  MULTITHREAD, and JPI$_THREAD_INDEX.  F                                  The code example has been updated for5                                  VAX and Alpha usage.h  D               $GETRMI            This is a new service in support of1                                  Performance API.   F               $GETQUI            The item code, QUI$V_JOB_REQUEUE, has,                                  been added.  G               $GETSYI            The item code, SYI$_SERIAL_NUMBER, hase,                                  been added.  D               $IO_PERFORM        The 'porint' argument in the formatI                                  section has been changed to 'devdata, to 7                                  match the C prototype.   B               $MGBLSC            The text for the 'inadr' argumentE                                  has been updated, and the SS$_INVARG @                                  condition value has been added.  C               $MOUNT             The following item codes have been G                                  added: MNT$M_MINICOPY_OPTIONAL, MNT$M_ B                                  MINICOPY_REQUIRED, MNT$M_REQUIRE_B                                  MEMBERS, and MNT$M_VERIFY_LABELS.  I                                                 Programming Features 5-45a c  r           Programming Features     5.16 System Services  E           ___________________________________________________________oE           System_Service_____Documentation_Update____________________l  D           $PERSONA_QUERY     Tables for Common, General, and NT item3                              codes have been added.a  E           $PROCESS_SCAN      The following item codes have been addediA                              for Multithreads support: PSCAN$_KT_a:                              COUNT and PSCAN$_MULTITHREAD.  >           $REGISTRY          This service is now documented inB                              the OpenVMS System Services Reference>                              Manual: GETUTC-Z and online help.  E           $SCAN_INTRUSION    This service has been updated in support 6                              of Clusterwide Intrusion.  B           $SCHED             The condition value, SS$_INCLASS, has@                              been added, and SS$_ILLSER has been%                              deleted.   @           $SET_DEVICE        This is a new service in support of'                              Multipath.   B           $SET_SECURITY      The condition value, SS$_INVFILFOROP,,                              has been added.  B           $SET_SYSTEM_EVENT  A new item code, SYSEVT$C_TDF_CHANGE,,                              has been added.  E           $SHOW_INTRUSION    This service has been updated in supporti6                              of Clusterwide Intrusion.  <           $WAKE              This service now accepts 64-bitE           ___________________addresses.______________________________   >     5.17 TCP/IP Files for SDA READ Command That Contain Global          Symbols and Locations  >           Table 5-6 shows the TCP/IP files that contain global:           symbols for the VAX and Alpha SDA READ commands.               5-46 Programming Features            I                                                      Programming Features_I  Files     for SDA READ Command That Contain Global Symbols and LocationsW    B               Table 5-6 Modules Containing Global Symbols and DataI               __________Structures_Used_by_SDA____________________________  I               File________________________Contents________________________  A               TCPIP$NET_GLOBALS.STB       Contains data structure I                                           definitions for TCP/IP InternetsG                                           driver, execlet, and ACP datan4                                           structures  A               TCPIP$NFS_GLOBALS.STB       Contains data structure D                                           definitions for TCP/IP NFS0                                           server  A               TCPIP$PROXY_GLOBALS.STB     Contains data structure F                                           definitions for TCP/IP proxy1                                           execletT  A               TCPIP$PWIP_GLOBALS.STB      Contains data structureaE                                           definitions for TCP/IP PWIPiI                                           driver, and ACP data structureso  A               TCPIP$TN_GLOBALS.STB        Contains data structuregG                                           definitions for TCP/IP TELNETlD                                           /RLOGIN server driver dataI               ____________________________structures_____________________C  C               These files are only available if TCP/IP services hasdG               been installed. They are found in SYS$SYSTEM, and are notpG               automatically read in when you issue a READ/EXEC command.e  A               Table 5-7 shows the TCP/IP files that define globalhB               locations within the Executive Image for the VAX SDA               command.  D               Table 5-7 Modules Defining Global Locations Within theI               __________Executive_Image__________________________________g  I               File________________________Contents_______________________   @               TCPIP$BGDRIVER.STB          TCP/IP Internet driver  =               TCPIP$INETACP.STB           TCP/IP Internet ACPo  A               TCPIP$INTERNET_             TCP/IP Internet execlet                SERVICES.STB  I                                                  (continued on next page)e  I                                                 Programming Features 5-47k a  g           Programming FeaturesT     5.17 TCP/IP Files for SDA READ Command That Contain Global Symbols and Locations    D           Table 5-7 (Cont.) Modules Defining Global Locations WithinE           __________________the_Executive_Image______________________   E           File________________________Contents_______________________   @           TCPIP$NFS_SERVICES.STB      Symbols for the TCP/IP NFS,                                       server  B           TCPIP$PROXY_SERVICES.STB    Symbols for the TCP/IP proxy-                                       execlet   5           TCPIP$PWIPACP.STB           TCP/IP PWIP ACPK  8           TCPIP$PWIPDRIVER.STB        TCP/IP PWIP driver  A           TCPIP$TNDRIVER.STB          TCP/IP TELNET/RLOGIN server E           ____________________________driver_________________________   ?           These files are only available if TCP/IP services hasdC           been installed. They are found in SYS$SYSTEM, and are not=C           automatically read in when you issue a READ/EXEC command.   A           For more detailed information, refer to the OpenVMS VAX C           System Dump Analyzer Utility Manual and the OpenVMS Alpha '           System Analysis Tools Manual.   +     5.18 Visual Threads Version 2.1 (Alpha)d  =           Visual Threads is a unique tool that lets you debugd=           and analyze multithreaded applications. You can use B           Visual Threads to automatically diagnose common problems<           associated with multithreading including deadlock,B           mutex, and thread usage errors. Also, you can use VisualA           Threads to monitor the thread-related performance of an E           application, helping you to identify bottlenecks or locking A           granularity problems. Visual Threads helps you identifyFA           problem areas in an application even if the application *           does not show specific symptoms.  9           Visual Threads includes the following features:   D           o  Collects detailed information about significant thread-.              related state changes ("events").  C           o  Analyzes common threading problems automatically based =              on predefined rules applied to the event stream.i  C           o  Rule customization for application-specific parametersN              and actions.o       5-48 Programming Features            I                                                      Programming Features I                                   5.18 Visual Threads Version 2.1 (Alpha)o    F               o  Automatic statistics gathering, by sampling the event                  stream.  E               o  Categories of analysis: data protection errors (raceiA                  conditions), deadlocks, programming errors, lockf'                  activity, performance.   D               o  Graphical visualization of the frequency of thread-I                  related events and thread state, snapshots of historical C                  program state, and object-specific graphs for each %                  collected statistic.d  F               o  Lock activity profiling to reveal where various typesD                  of lock activity are occurring in your application,D                  including: Number of Locks, Contended Locks, LockedD                  Time, and Wait Time. Lock activity is collected and0                  displayed for individual locks.  A               o  Summarizes the program run and provides reports.i  G               o  Threads Snapshot view displays the historical state ofeI                  threads represented at specific times in the main threadL                   overview graph.  I               o  Find and Filter support in the Event Window to allow youL5                  to quickly locate particular events.   H               o  CPU Utilization Window shows the CPU percentage used by                  each thread.   H               o  Thread Transitions Window depicts each state change for!                  a detailed view._  E               For more information about these features, refer to thecI               Visual Threads product documentation, which is available onfI               the OpenVMS Alpha CD-ROM in directory [VISUAL_THREADS_021],21               or by using the online Help system.                 I                                                 Programming Features 5-49D o  n                    I                                                                         6TI         __________________________________________________________________  I                                              Associated Products Featuresi    G               This chapter describes significant new features of CompaqNI               OpenVMS operating system associated products. For a listing A               and directory information on the OpenVMS associated A               products, refer to the Guide to OpenVMS Version 7.3k               CD-ROMs.            6.1 Availability Manager  G               OpenVMS Version 7.3 contains Availability Manager Version A               1.4. Soon after the release of OpenVMS Version 7.3,sG               Availability Manager Version 2.0 will be announced on the 6               following Availability Manager web site:  F               http://www.openvms.compaq.com/openvms/products/availman/  B               Version 2.0 will include the following new features:  E               o  A new internal infrastructure supports new operating 9                  system features more easily and quickly.d  A               o  To support NUMA or OpenVMS "RADs" and to provide G                  preliminary support for Wildfire/Galaxy, the followingA0                  features have been implemented:  A                  -  A new Memory view of OpenVMS Alpha V7.3 nodesh.                     displays RAD-related data.  =                  -  When monitoring OpenVMS Alpha V7.3 nodes, F                     Availability Manager displays a new single-process5                     memory tab called "RAD Counters."   E                  -  The CPU modes display includes the RAD for a CPU.T  D                  -  The CPU process list shows the home RAD for each                     process.  G                  -  The Node summary display now includes the number of F                     configured RADs, the system serial number, and the0                     Galaxy ID of a node, if any.  I                                          Associated Products Features 6-1                  Associated Products Features     6.1 Availability Manager    C           o  Displays now include additional switched LAN and NISCAu"              data, when available.  ;           o  New user-defined event notifications have been               implemented.m  9           o  A built-in browser now displays online help.y  E           o  A built-in Java runtime environment is now included. (In C              other words, you no longer need to install Java on theg              system.).  6           o  ODS-5 file system support has been added.  9           o  A new PGFLQUOTA process-level "fix" has beent              implemented.   @           o  A simpler mechanism for site-specific configuration              setup now exists.  7     6.2 Compaq Advanced Server V7.3 for OpenVMS (Alpha)   ?           The Compaq Advanced Server Version 7.3 for OpenVMS is B           supported on Alpha systems only, and is the only versionA           of the Advanced Server for OpenVMS supported on OpenVMSs@           Alpha Version 7.3. New features include the following:  C           o  Member server role (allowing the server to participates1              in Windows 2000 native-mode domains)S  E           o  Greater compatibility with a wide variety of clients and 2              legacy applications, with support of:  E              -  Extended character sets, in addition to Extended File                  Specifications  @              -  Alias file names, created for shared files whoseA                 names do not comply with the more restricted file_A                 naming conventions of legacy applications such as                  MS-DOS  ?           o  Remote Windows NT printer management (SpoolSS) for ?              printers shared on the Advanced Server for OpenVMS   ,           o  DNS for resolving NetBIOS names  C           o  Cluster load balancing using DNS to resolve the server               cluster alias name.  +           o  PCSI for installing the servera  $     6-2 Associated Products Features           I                                              Associated Products FeaturessI                       6.2 Compaq Advanced Server V7.3 for OpenVMS (Alpha)     7               o  Windows 2000 client and domain support   A               Earlier versions of the Advanced Server for OpenVMS E               (Versions 7.2 and 7.2A) must be upgraded to Version 7.3 G               to run on OpenVMS Alpha Version 7.3. Both the current and F               earlier versions of the Advanced Server for OpenVMS also1               run on OpenVMS Alpha Version 7.2-1.   B               For information about installing Advanced Server forF               OpenVMS, refer to the Compaq Advanced Server for OpenVMSG               Server Installation and Configuration Guide provided withm$               the kit documentation.  C               To access Advanced Server V7.3 for OpenVMS on OpenVMS3C               Alpha Version 7.3, clients must be licensed using thebG               new Advanced Server V7.3 license PAK: PWLMXXXCA07.03. ForDG               more information, refer to the Compaq Advanced Server forWA               OpenVMS Guide to Managing Advanced Server Licenses.   G               For information about the latest release of the PATHWORKS F               for OpenVMS (Advanced Server) product, supported on bothI               OpenVMS Alpha and VAX Version 7.3 systems, see Section 6.9.   /         6.3 Compaq DECwindows Motif for OpenVMS   A               The Compaq DECwindows Motif for OpenVMS (DECwindows C               Motif), Version 1.2-6 kit for OpenVMS VAX and OpenVMS E               Alpha is now available. DECwindows Motif, Version 1.2-6 D               is a maintenance release that delivers a full range ofI               changes and enhancements to your desktop. From faster batch E               scrolling to support for the Common Desktop Environment G               (CDE) screen saver and lock extensions, these changes are E               intended to provide you with a more efficient, flexible H               DECwindows Motif environment that is more in line with theG               OSF/Motif, MIT X11 Release 5 (X11 R5), and Common Desktop F               Environment (CDE) standards. For a full list of specificH               changes, enhancements, and corrections implemented in thisG               release, refer to the Compaq DECwindows Motif for OpenVMS,               Release Notes.  "         6.4 Compaq DCE for OpenVMS  ?               This section describes the enhancements in Compaq I               Distributed Computing Environment (DCE) for OpenVMS Versione               7.3.  I                                          Associated Products Features 6-3e t  t            Associated Products Features     6.4 Compaq DCE for OpenVMS    0     6.4.1 Compaq DCE Remote Procedure Call (RPC)  B           Beginning with OpenVMS Version 7.2-1, the NT Lan Manager2           security in DCE RPC is fully functional.  %     6.4.2 New Ethernet Device SupportU  C           If DCE RPC does not recognize the Ethernet device in your C           system, one new device may be added to the table of known D           devices by defining the system logical DCE$IEEE_802_DEVICE8           to be the device name of your Ethernet device.  D           For example, to define a single DE500 Ethernet device, set!           the logical as follows:s  2           $ DEFINE/SYSTEM DCE$IEEE_802_DEVICE EWA0  "     6.4.3 For More DCE Information  <           Refer to the OpenVMS Version 7.3 Release Notes for=           important information about Compaq DCE for OpenVMS.m  D           If you have the full DCE kit installed, you can use online*           help for additional information:             $ HELP DCE           $ HELP DCE$SETUP           $ HELP DCE_CDS           $ HELP DCE_DTS           $ HELP DCE_IDL           $ HELP DCE_RPC           $ HELP DCE_SECURITY            $ HELP DCE_THREADS  <           You can also refer to the following documentation:  9           o  Compaq DCE for OpenVMS VAX and OpenVMS Alpha-?              Installation and Configuration Guide (order numbera              AA-PV4CE-TE)   A           o  Compaq DCE for OpenVMS VAX and OpenVMS Alpha ProductS-              Guide (order number AA-PV4FE-TE)S  C           o  Compaq DCE for OpenVMS VAX and OpenVMS Alpha Referencen-              Guide (order number AA-QHLZB-TE)   $     6-4 Associated Products Features i  i      I                                              Associated Products Features I                                6.5 DECram for OpenVMS Version 3.0 (Alpha)s    2         6.5 DECram for OpenVMS Version 3.0 (Alpha)  H               DECram Version 3.0 supports the OpenVMS for Alpha platformH               only. The following are the new features that can be found               in this release:  B               o  In DECram for OpenVMS Alpha Version 3.0, DECram'sA                  capability supports the use of shared memory for_A                  creation of RAM disks in an Adaptive PartitionedaE                  MultiProcessing (APMP) environment. This environment E                  is also know as Compaq Galaxy Software Architecture.A  G               o  On OpenVMS Version 7.2-1H1 or higher, the limit on the D                  DECram file size has been extended to 4,294,967,296                  blocks.  H               o  DECram for OpenVMS Version 3.0 is fully compatible withD                  DECram Version 2.3. There can be any combination of>                  these two versions of DECram in a VMScluster.  C               o  Multiple DECram devices can be members of a Volume_F                  Shadowing for OpenVMS shadow set and can be served byD                  Mass Storage Control Protocol (MSCP) or QIO served.  F               o  Volume Shadowing for OpenVMS will support shadow setsI                  composed of DECram devices and other disk class devices.   I               o  A new DECram command interface (DECRAM>) can be used for C                  creating, initializing, and mounting DECram disks.   A               DECram Version 3.0 and supporting documentation areLI               included in the OpenVMS Version 7.3 CD-ROM in the [.DECRAM_                030] directory.   5         6.6 Enterprise Capacity and Performance (ECP)   ?               Beginning with OpenVMS Version 7.3, the following B               Enterprise Capacity and Performance (ECP) managementD               tools will be provided at no additional costs. The ECPE               Data Collector for OpenVMS and ECP Performance AnalyzerrI               for OpenVMS will be available to customers who have a validlD               license to operate OpenVMS Version 6.2 or later. TheseF               products are available from the following World Wide Web               site:   K                http://www.openvms.compaq.com/openvms/system_management.htmla  I                                          Associated Products Features 6-5  d               Associated Products Features1     6.6 Enterprise Capacity and Performance (ECP)     ?           Software Support Services for these products are soldr?           separately and are available on an incremental basis.o@           Please contact your Compaq Services representative for           further details.  /     6.6.1 ECP Collector for OpenVMS Version 5.4_  C           ECP Collector for OpenVMS Version 5.4 gathers performanceIB           and capacity planning data on OpenVMS operating systems.E           OpenVMS data collection has three main criteria; the amountEC           of performance data collected, the time interval, and theBD           efficiency or amount of overhead impacting the system. ECP7           Collector for OpenVMS provides the following:   C           o  Robust data collection set. It collects system metrics 8              on over 250 OpenVMS performance parameters.  D           o  Flexible data collection. The sampling rate of data can3              be tuned down to sub-second intervals._  D           o  Low overhead. Audited production systems have routinelyA              shown that ECP Collector for OpenVMS has less than aF$              1.5% impact on the CPU.  <           Satisfying the needs of Enterprise Management, ECPB           Collector for OpenVMS also contains an API that provides?           an interface for the access of performance data. ThisC?           interface converts the contents of the .CPC data fileBB           generated by the data collector into a formatted, comma-D           separated ASCII file that can then be used for performance*           analysis and reporting programs.  :     6.6.2 ECP Performance Analyzer for OpenVMS Version 5.4  >           Compaq's ECP Analyzer for OpenVMS Version 5.4, whichA           runs under Motif, analyzes the data provided by the ECP @           Collector for OpenVMS data collector. ECP Analyzer forC           OpenVMS provides the entry point into the data collector,h@           and allows the user to select the sampling rate and toD           view the performance data in graphical format. The productB           provides historical information in standard graphs basedC           upon the requested time interval. Graphs are provided fore@           all common performance issues that need to be analyzedB           including the CPU, the memory, and the I/O. ECP AnalyzerE           for OpenVMS provides both graphic (MOTIF-based) and tabularc           reports for the data.h  $     6-6 Associated Products Features n         I                                              Associated Products FeaturesbI                                                  6.7 Kerberos for OpenVMSo              6.7 Kerberos for OpenVMS  E               Kerberos Version 1.0 for OpenVMS Alpha and OpenVMS VAX,aH               based on MIT Kerberos Version 5 Release 1.0.5, is includedF               on the OpenVMS Version 7.3 distribution media. (KerberosF               documentation provided by MIT is included on the OpenVMS3               documentation CD-ROM in HTML format.)c  D               Kerberos is a network authentication protocol designed@               to provide strong authentication for client/server<               applications by using secret-key cryptography.  D               Kerberos was created by the Massachusetts Institute ofH               Technology as a solution to network security problems. TheI               Kerberos protocol uses strong cryptography so that a clientrH               can prove its identity to a server (and vice versa) acrossG               an insecure network connection. After a client and serverlG               have used Kerberos to prove their identity, they can alsotG               encrypt all of their communications to assure privacy anda               data integrity.f  F               General information about Kerberos is available from the/               following World Wide Web address:   .               http://web.mit.edu/kerberos/www/  &         6.7.1 New DCL Command KERBEROS  E               OpenVMS Kerberos is an authentication security product.dC               It allows for user authentication for a wide range ofdE               communication programs such as RLOGIN, TELNET, and FTP.n                 Format:   '               KERBEROS [/ADMIN | /USER]yA                        [/INTERFACE=[DECWINDOWS | CHARACTER_CELL]]                  Qualifiers:r                 /ADMIN  C               Activates the Kerberos administration utility for the !               selected interface.                  /USER (default)v  I                                          Associated Products Features 6-7e y               Associated Products Features     6.7 Kerberos for OpenVMS    >           Activates the Kerberos user utility for the selected           interface.  -           /INTERFACE=CHARACTER_CELL (default)            /INTERFACE=DECWINDOWSs  ?           Activates the display device requested, if available.p  A           For more information, refer to the Kerberos for OpenVMS /           Installation Guide and Release Notes.   $     6.8 Universal LDAPv3 API (Alpha)  @           OpenVMS Version 7.3 includes the Lightweight DirectoryD           Access Protocol (LDAPv3) Application Programming InterfaceB           (API) that allows OpenVMS application developers, third-B           party applications, and users to access LDAP directoriesD           anywhere in the enterprise, intranet, extranet or InternetD           hosted by non-OpenVMS systems. The multi-threaded API willC           automatically support both 64-bit and 32-bit applicationso1           and be Common Object Model (COM) aware.r  @           The universal LDAPv3 API is certified with Microsoft'sC           Active Directory, Novell's NDS and Compaq's X.500 VersioneA           4.0, and supports various security mechanisms including.:           Kerberos V5 and Public Key Infrastructure (PKI).  E           The LDAPv3 kits are available from the following World Wide            Web address:  O           http://www.openvms.compaq.com/openvms/products/mgmt_agents/index.htmls  D           For additional information on the LDAPv3 API, refer to the*           OpenVMS Utility Routines Manual.  <     6.9 Compaq PATHWORKS V6.0D for OpenVMS (Advanced Server)  A           Compaq PATHWORKS V6.0D for OpenVMS (Advanced Server) isAD           the only PATHWORKS for OpenVMS server supported on OpenVMSA           Version 7.3 (in addition to Compaq Advanced Server V7.3aA           for OpenVMS). Earlier versions of PATHWORKS for OpenVMSeB           servers must be upgraded. For more information, refer to0           the OpenVMS Version 7.3 Release Notes.  C           You can run PATHWORKS V6.0D for OpenVMS (Advanced Server) D           on either OpenVMS Alpha Versions 7.3, 7.2-1, or 6.2, or on0           OpenVMS VAX Versions 7.3, 7.2, or 6.2.  $     6-8 Associated Products Features           I                                              Associated Products Features.I                  6.9 Compaq PATHWORKS V6.0D for OpenVMS (Advanced Server)     E               To access PATHWORKS V6.0D for OpenVMS (Advanced Server) D               on OpenVMS Version 7.3, clients must be licensed using@               the license PAK PWLMXXXCA06.00, PWLMXXXCA07.02, orG               PWLMXXXCA07.03. For more information, refer to the Compaq D               Advanced Server for OpenVMS Guide to Managing Advanced               Server Licenses.  I               For information about the latest release of Compaq Advanced >               Server Version 7.3 for OpenVMS, see Section 6.2.  .         6.10 Compaq Service Tools and DECevent  I               Compaq Services new web-based service tool functionality is H               known as Web-Based Enterprise Services (WEBES). The CompaqE               System Tools CD-ROM included in the OpenVMS Version 7.3oG               CD-ROM package includes WEBES. (WEBES includes the CompaqsH               Crash Analysis Tool (CCAT) and Compaq Analyze components.)E               This is the supported service tools for all AlphaServer D               DS, ES, and GS systems running OpenVMS, except for theC               AlphaServer GS60 and AlphaServer GS140 platforms. The G               AlphaServer GS60 and GS140 platforms must continue to useh+               the DECevent diagnostic tool.w  B               In addition to WEBES, the Compaq System Tools CD-ROM>               includes DECevent, DSNLINK, and the Revision and3               Configuration Management (RCM) tools.o  C               DECevent and WEBES can be used together in a cluster.   E               Installation and documentation on the service tools are A               included on the Compaq System Tools CD-ROM. Use theaF               following web site to access the most up-to-date service               tool information:   5               http://www.support.compaq.com/svctools/   ;         6.11 Compaq TCP/IP Services for OpenVMS Version 5.1r  C               The Compaq TCP/IP Services for OpenVMS product is thedD               Compaq implementation of the TCP/IP protocol suite andA               internet services for OpenVMS Alpha and OpenVMS VAXe               systems.  I               TCP/IP Services provides a comprehensive suite of functionsiG               and applications that support industry-standard protocols C               for heterogeneous network communications and resourcep               sharing.  I                                          Associated Products Features 6-9p                 Associated Products Features7     6.11 Compaq TCP/IP Services for OpenVMS Version 5.1n    #     6.11.1 New Features and Changes   @           The new features of Compaq TCP/IP Services for OpenVMS           Version 5.1 include:  B           o  A new kernel, based on Compaq Tru64 UNIX Version 5.1.  <           o  Support for Internet Protocol Version 6 (IPv6).  !           o  DHCP client support.   )           o  Xterminal support using XDM.e  9           o  Services that can be restarted individually.o              o  GATED enhancements.  :           o  BIND dynamic updates management enhancements.  2           o  Cluster failover for the BIND server.  2           o  Cluster failover for the load broker.  /           o  Updated SNMP that supports AgentX.n  *           o  SMTP enhancements, including:  >              -  AntiSPAM (configuration to control mail relay)  )              -  SMTP SFF (Send From File)e  #              -  SMTP outbound aliasm  ?           o  Metric server logicals that can be changed without *              restarting the Metric server.  D           o  The DHCP server can be configured to dynamically update              the BIND database.q  C           o  TELNET client enhancements to support SNDLOC and NAWS.o  C           o  Support for the NFS V3 protocol in addition to the NFSo+              V2 protocol in the NFS server.h  :           o  TCP options for improving certain performance              characteristics.t  C           For more information about configuring and managing these C           services, refer to the Compaq TCP/IP Services for OpenVMSf@           Management guide provided with the TCP/IP Services for'           OpenVMS Version 5.1 software.   %     6-10 Associated Products Featuresi a  r      I                                              Associated Products FeaturesnI                       6.11 Compaq TCP/IP Services for OpenVMS Version 5.1m    8         6.11.2 TCP/IP Services for OpenVMS Documentation  G               For installation instructions, refer to the Compaq TCP/IPsI               Services for OpenVMS Installation and Configuration manual.   C               The TCP/IP Services for OpenVMS Release Notes provideD>               version-specific information that supersedes theA               information in the documentation set. The features, B               restrictions, and corrections in this version of theF               software are described in the release notes. Always read?               the release notes before installing the software.   H               The TCP/IP Services for OpenVMS documentation set includes&               the following new items:  A               o  Compaq TCP/IP Services for OpenVMS Guide to IPv6.  F                  This manual describes the IPv6 environment, the rolesG                  of systems in this environment, the types and functioneF                  of the different IPv6 addresses, and how to configure=                  TCP/IP Services to access the 6bone network.   >               o  Compaq TCP/IP Services for OpenVMS Tuning and                   Troubleshooting  F                  This manual provides information about how to isolateC                  the causes of network problems and how to tune theOC                  TCP/IP Services software for the best performance.   F               o  Compaq TCP/IP Services for OpenVMS Management Command%                  Quick Reference Card   E                  This reference card summarizes the TCP/IP managementPE                  commands, organizing them by function and component.   @               o  Compaq TCP/IP Services for OpenVMS UNIX Command                  Reference CardA  H                  This reference card describes how to use UNIX utilities6                  on OpenVMS to manage TCP/IP services.  H               The following existing TCP/IP Services for OpenVMS manuals)               have been updated for V5.1:o  D               o  Compaq TCP/IP Services for OpenVMS Installation and                  Configuration  >               o  Compaq TCP/IP Services for OpenVMS Management  F               o  Compaq TCP/IP Services for OpenVMS Management Command                  Reference  I                                         Associated Products Features 6-11                  Associated Products Features7     6.11 Compaq TCP/IP Services for OpenVMS Version 5.1i    ?           o  Compaq TCP/IP Services for OpenVMS Sockets API andM(              System Services Programming  D           o  Compaq TCP/IP Services for OpenVMS SNMP Programming and              Reference                                                                                %     6-12 Associated Products Featuresr o                       I                                                                   Part IIsI         _________________________________________________________________s  I                                         Overview of OpenVMS Documentation  -                       I                                                                         72I         _________________________________________________________________   I                                            OpenVMS Documentation Overviewb    >               This chapter outlines the changes to the OpenVMS6               documentation from the previous version.  )         7.1 OpenVMS Documentation Changes   F               Table 7-1 lists the changes to the OpenVMS documentation&               for OpenVMS Version 7.3.  I         Table_7-1_Changes_to_Documentation_for_OpenVMS_Version_7.3_______s  I         Area_of_Change________Description________________________________d  I         ____________________Expanded_Online_Offerings____________________u  H         Documentation CD-ROM  The OpenVMS documentation is now availableF                               on a single ISO9660 Level 2 CD-ROM. ThisI                               CD-ROM can be used on OpenVMS, Windows, and 0                               Macintosh systems.  <                               For more information about theD                               documentation CD-ROM, see Section 8.2.  D         Online formats        OpenVMS documentation is now availableC                               in PDF as well as HTML formats on ther3                               documentation CD-ROM.   C         Adobe Acrobat Reader  The documentation CD-ROM includes two G                               versions of the Adobe Acrobat Reader. One I                               is an executable file for PCs; one is a ZIP I                               file that can be installed on OpenVMS AlphaeC                               systems running Java Version 1.1.8-5.d  I                                                  (continued on next page)n      I                                        OpenVMS Documentation Overview 7-1     s      "     OpenVMS Documentation Overview%     7.1 OpenVMS Documentation Changess    B     Table 7-1 (Cont.) Changes to Documentation for OpenVMS VersionE     __________________7.3____________________________________________o  E     Area_of_Change________Description________________________________a  E     ____________________Expanded_Online_Offerings____________________   A     Online help           Reference information for the followingEE                           OpenVMS utility routines is now included in 9                           online help under RTL_Routines:s  =                              Access Control List (ACL) Editor '                              (ACLEDIT$)e6                              Backup (BACKUP) (BACKUP$):                              Command Language (CLI) (CLI$);                              Command File Qualifier (UTIL$) 6                              Convert (CONVERT) (CONV$)D                              Data Compression/Expansion (DCX) (DCX$)A                              DEC Text Processing Utility (DECTPU)5#                              (TPU$)iB                              EDT (EDT$EDIT; FILEIO; WORKIO; XLATE)B                              File Definition Language (FDL) (FDL$)3                              Librarian (LBR) (LBR$) 2                              LOGINOUT (LGI) (LGI$)8                              Mail Utility (MAIL) (MAIL$)@                              National Character Set (NCS) (NCS$)E                              Print Symbiont Modification (PSM) (PSM$;.$                              USER-x)D                              Symbiont/Job Controller Interface (SMB)#                              (SMB$)f4                              Sort/Merge (SOR) (SOR$)  <     Master Index          The OpenVMS Master Index manual inB                           ASCII text format is now included on the/                           documentation CD-ROM.   E                                              (continued on next page)u                &     7-2 OpenVMS Documentation Overview r  s      I                                            OpenVMS Documentation Overview I                                         7.1 OpenVMS Documentation Changesl    F         Table 7-1 (Cont.) Changes to Documentation for OpenVMS VersionI         __________________7.3____________________________________________   I         _________________________________________________________________   I         ___________________________New_Manual____________________________   G         Availability Manager  This new manual for Version 7.3 describeseH         User's Guide          how to use the Compaq Availability ManagerD                               system management tool, from either anI                               OpenVMS Alpha or a Windows node, to monitoroF                               one or more OpenVMS nodes on an extendedC                               local area network (LAN) or to target.E                               a specific node or process for detailedn'                               analysis.n  I                                                  (continued on next page)y                                                        I                                        OpenVMS Documentation Overview 7-3r e  i      "     OpenVMS Documentation Overview%     7.1 OpenVMS Documentation Changest    B     Table 7-1 (Cont.) Changes to Documentation for OpenVMS VersionE     __________________7.3____________________________________________e  E     _________________________________________________________________   E     __________________________Revised_Titles_________________________r  ?     Title changes         Note the following titles changes fore&                           Version 7.3:  @                           o  Compaq C Run-Time Library Reference7                              Manual for OpenVMS Systems.  D                              Revised to reflect the Compaq C product"                              name.  @                           o  Compaq Portable Mathematics Library  @                              Revised to reflect the Compaq name.  ;                           o  Guide to POSIX Threads Library/  C                              Formerly entitled Guide to DECthreads.]  B                           o  OpenVMS Alpha Partitioning and Galaxy"                              Guide  D                              Formerly entitled OpenVMS Galaxy Guide.  @                           o  OpenVMS MACRO-32 Porting and User's"                              Guide  E                              Formerly entitled Porting VAX MACRO Code .                              to OpenVMS Alpha.  A                           o  OpenVMS Version 7.3 New Features andA3                              Documentation Overviews  ?                              Now includes information about thep=                              OpenVMS documentation offerings.p  E                                              (continued on next page)r      &     7-4 OpenVMS Documentation Overview o  .      I                                            OpenVMS Documentation OverviewiI                                         7.1 OpenVMS Documentation Changese    F         Table 7-1 (Cont.) Changes to Documentation for OpenVMS VersionI         __________________7.3____________________________________________n  I         _________________________________________________________________   I         ___________________Restructured_Documentation____________________n  E         OpenVMS Programming   The OpenVMS Programming Concepts ManualAH         Concepts Manual       has been restructured and expanded. It nowD                               consists of the following two volumes:  E                               o  OpenVMS Programming Concepts Manual,u)                                  Volume Ir  D                                  Contains an introduction to OpenVMSE                                  programming followed by three parts:xH                                  Process and Synchronization; InterruptsG                                  and Condition Handling; and AddressingR7                                  and Memory Management.q  E                               o  OpenVMS Programming Concepts Manual,T*                                  Volume II  G                                  Contains two additional parts: Calling G                                  a System Routine; and I/O, System, and 6                                  Programming Routines.  C         DCL command MOUNT     Reference information about the MOUNT G                               command is now located in the OpenVMS DCLp.                               Dictionary: A-M.  C         Information           The Overview of OpenVMS DocumentationPC         about OpenVMS         manual no longer exists as a separate H         documentation         manual. Instead, information about OpenVMSF                               documentation is included in the OpenVMSH                               Version 7.3 New Features and Documentation'                               Overview.   I                                                  (continued on next page)             I                                        OpenVMS Documentation Overview 7-5e o  p      "     OpenVMS Documentation Overview%     7.1 OpenVMS Documentation Changes     B     Table 7-1 (Cont.) Changes to Documentation for OpenVMS VersionE     __________________7.3____________________________________________m  E     _________________________________________________________________a  E     _________________________Archived_Manuals________________________r  C     Four archived         Beginning with Version 7.3, the followingnC     manuals               manuals are archived. The online versionsuB                           are included with other archived manuals@                           in a separate directory on the OpenVMS/                           documentation CD-ROM.   B                           o  Migrating an Application from OpenVMS1                              VAX to OpenVMS Alpha1  E                           o  OpenVMS Alpha Guide to 64-Bit Addressings-                              and VLM Featuresd  E                              Portions are now included in the OpenVMS C                              Programming Concepts Manual, Volume I.i  D                           o  OpenVMS Programming Interfaces: Calling-                              a System Routinen  E                              Portions are now included in the OpenVMScD                              Programming Concepts Manual, Volume II.  A                           o  TCP/IP Networking on OpenVMS Systems-  B                              For information about using TCP/IP onD                              OpenVMS systems, see the OpenVMS SystemC                              Manager's Manual and the documentationcC                              set for the Compaq TCP/IP Services forf-                              OpenVMS product.n  E     Addition to the       The Standard TECO Text Editor and Corrector.@     archived manuals      for the VAX, PDP-11, PDP-10, and PDP-8B     offering              manual is now included with the archived>                           manuals on the documentation CD-ROM.@                           Note that this manual is not availableE     ______________________in_printed_form.___________________________       &     7-6 OpenVMS Documentation Overview m                       I                                                                         8 I         _________________________________________________________________.  I                                  OpenVMS Printed and Online Documentation.    G               This chapter outlines the following OpenVMS documentation                components:   4               o  Printed documentation (Section 8.1)  =               o  Online documentation on CD-ROM (Section 8.2)   =               o  Online documentation on the OpenVMS web sitee                  (Section 8.3)  *               o  Online Help (Section 8.4)  !         8.1 Printed Documentationd  F               This section describes the OpenVMS printed documentation               offerings:  H               o  Upgrade and installation documentation that is includedE                  with your OpenVMS software media kit (Section 8.1.1)o  =               o  The OpenVMS Full and Base Documentation setsn                   (Section 8.1.2)  D               o  Documentation for System Integrated Products (SIPs)                   (Section 8.1.3)  1               o  Archived manuals (Section 8.1.4)e  -         8.1.1 OpenVMS Media Kit Documentation   F               Upgrade and installation manuals and the OpenVMS LicenseD               Management Utility Manual are included in your OpenVMS               media kit.  G               OpenVMS Alpha customers receive the OpenVMS Alpha VersionnG               7.3 Upgrade and Installation Manual. This manual contains/G               step-by-step upgrade and installation information as wellP7               as device-naming and booting information.   I                              OpenVMS Printed and Online Documentation 8-1            ,     OpenVMS Printed and Online Documentation     8.1 Printed DocumentationC    C           OpenVMS VAX customers receive the OpenVMS VAX Version 7.3sA           Upgrade and Installation Manual, the primary source forcD           step-by-step upgrade and installation procedures using the           VMSINSTAL utility.  >           Table 8-1 lists the installation manuals included in?           the OpenVMS media kit. You can also order the manuals B           individually. Note that the manuals in the media kit are9           not part of the OpenVMS Full Documentation set.   E           Table_8-1_OpenVMS_Media_Kit_Manuals________________________s  E           Manual______________________________________Order_Number___h  E           Upgrade_and_Installation_Manuals___________________________o  A           OpenVMS Alpha Version 7.3 Upgrade and       AA-QSE8D-TE            Installation Manual   A           OpenVMS VAX Version 7.3 Upgrade and         AA-QSBQD-TEI           Installation Manual   A           OpenVMS License Management Utility Manual   AA-PVXUF-TK   E           Guide_to_OpenVMS_Version_7.3_CD-ROMs________AA-QSBRE-TE____   $     8.1.2 OpenVMS Documentation Sets  =           OpenVMS documentation is available in the followingo           documentation sets:   E           ___________________________________________________________o           Documentation E           Set_________Description____________________Order_Number____   D           Full set    Intended for users who         QA-001AA-GZ.7.30                       need extensive explanatory/                       information for all majore1                       OpenVMS resources. Containsa3                       all the OpenVMS documentationd3                       in one offering. Includes the -                       Base Documentation set.       0     8-2 OpenVMS Printed and Online Documentation           I                                  OpenVMS Printed and Online DocumentationpI                                                 8.1 Printed DocumentationP  I               ___________________________________________________________                Documentation/I               Set_________Description____________________Order_Number____   H               Base set    Subset of the Full             QA-09SAA-GZ.7.35                           Documentation set. Intendedm6                           for general users and system6                           managers of small standalone/                           systems. Includes the 4                           most commonly used OpenVMSI               ____________manuals._______________________________________   I               In addition to ordering the Full or Base Documentation set,o<               you can order any OpenVMS manual individually.  F               Table 8-2 lists the manuals in the OpenVMS Base and FullG               Documentation sets. For a description of each manual, see                Section 9.2.  I         Table_8-2_OpenVMS_Full_Documentation_Set_(QA-001AA-GZ.7.3)________  I         Manual______________________________________________Order_Number_   E                                                             QA-09SAA- I         OpenVMS_Base_Documentation_Set______________________GZ.7.3_______   G         OpenVMS DCL Dictionary: A-M                         AA-PV5KG-TK   G         OpenVMS DCL Dictionary: N-Z                         AA-PV5LG-TK   G         OpenVMS Guide to System Security                    AA-Q2HLE-TE   G         OpenVMS Master Index                                AA-QSBSD-TEt  G         OpenVMS System Management Utilities Reference       AA-PV5PF-TKc         Manual: A-L   G         OpenVMS System Management Utilities Reference       AA-PV5QF-TKf         Manual: M-Z3  G         OpenVMS System Manager's Manual, Volume 1:          AA-PV5MF-TK_         Essentials  G         OpenVMS System Manager's Manual, Volume 2: Tuning,  AA-PV5NF-TK '         Monitoring, and Complex Systemsu  G         OpenVMS User's Manual                               AA-PV5JE-TK6  I                                                  (continued on next page)p  I                              OpenVMS Printed and Online Documentation 8-3            ,     OpenVMS Printed and Online Documentation     8.1 Printed Documentationu    ?     Table 8-2 (Cont.) OpenVMS Full Documentation Set (QA-001AA-pE     __________________GZ.7.3)________________________________________P  E     Manual______________________________________________Order_Number_t  A                                                         QA-09SAA-RE     OpenVMS_Base_Documentation_Set______________________GZ.7.3_______c  C     OpenVMS Version 7.3 New Features and Documentation  AA-QSBFD-TE      Overview  C     OpenVMS Version 7.3 Release Notes                   AA-QSBTD-TEp  E     _________________________________________________________________1A                                                         QA-001AA-nE     Continuation_of_Full_Documentation_Set______________GZ.7.3_______S  C     Availability Manager User's Guide                   AA-RNSJA-TEv  C     Compaq C Run-Time Library Utilities Reference       AA-R238C-TE.
     Manual  C     Compaq Portable Mathematics Library                 AA-PV6VE-TE_  C     DECamds User's Guide                                AA-Q3JSE-TEt  C     DEC Text Processing Utility Reference Manual        AA-PWCCD-TEd  C     Extensible Versatile Editor Reference Manual        AA-PWCDD-TEe  C     Guidelines for OpenVMS Cluster Configurations       AA-Q28LE-TK   C     Guide to Creating OpenVMS Modular Procedures        AA-PV6AD-TKh  C     Guide to OpenVMS File Applications                  AA-PV6PD-TK   C     Guide to POSIX Threads Library                      AA-QSBPD-TE   C     Guide to the DEC Text Processing Utility            AA-PWCBD-TE   C     OpenVMS Alpha Partitioning and Galaxy Guide         AA-REZQC-TEF  C     OpenVMS Alpha Guide to Upgrading Privileged-Code    AA-QSBGD-TE(     Applications  C     OpenVMS Alpha System Analysis Tools Manual          AA-REZTB-TE   C     OpenVMS Calling Standard                            AA-QSBBD-TE   C     OpenVMS Cluster Systems                             AA-PV5WE-TKO  C     OpenVMS Command Definition, Librarian, and Message  AA-QSBDD-TE      Utilities Manual  C     OpenVMS Debugger Manual                             AA-QSBJD-TE   E                                              (continued on next page))  0     8-4 OpenVMS Printed and Online Documentation e  e      I                                  OpenVMS Printed and Online DocumentationSI                                                 8.1 Printed Documentationm    C         Table 8-2 (Cont.) OpenVMS Full Documentation Set (QA-001AA-fI         __________________GZ.7.3)________________________________________   I         Manual______________________________________________Order_Number_e  E                                                             QA-001AA- I         Continuation_of_Full_Documentation_Set______________GZ.7.3_______   G         OpenVMS Delta/XDelta Debugger Manual                AA-PWCAD-TE   G         OpenVMS Guide to Extended File Specifications       AA-REZRB-TE   G         OpenVMS I/O User's Reference Manual                 AA-PV6SD-TKl  G         OpenVMS Linker Utility Manual                       AA-PV6CD-TKn  G         OpenVMS MACRO-32 Porting and User's Guide           AA-PV64D-TE   G         OpenVMS Management Station Overview and Release     AA-QJGCD-TE_
         Notes_  G         OpenVMS Performance Management                      AA-R237C-TE   G         OpenVMS Programming Concepts Manual, Volume I       AA-RNSHA-TKs  G         OpenVMS Programming Concepts Manual, Volume II      AA-PV67E-TK   G         OpenVMS Record Management Services Reference        AA-PV6RD-TK          Manual  G         OpenVMS Record Management Utilities Reference       AA-PV6QD-TK          Manual  G         OpenVMS RTL General Purpose (OTS$) Manual           AA-PV6HD-TK)  G         OpenVMS RTL Library (LIB$) Manual                   AA-QSBHD-TEr  G         OpenVMS RTL Screen Management (SMG$) Manual         AA-PV6LD-TK   G         OpenVMS RTL String Manipulation (STR$) Manual       AA-PV6MD-TK   G         OpenVMS System Messages: Companion Guide for Help   AA-PV5TD-TKO         Message Userse  G         OpenVMS System Services Reference Manual: A-GETUAI  AA-QSBMD-TEM  G         OpenVMS System Services Reference Manual: GETUTC-Z  AA-QSBND-TEn  G         OpenVMS Utility Routines Manual                     AA-PV6EE-TK_  G         OpenVMS VAX RTL Mathematics (MTH$) Manual           AA-PVXJD-TE_  I                                                  (continued on next page)_  I                              OpenVMS Printed and Online Documentation 8-5e           ,     OpenVMS Printed and Online Documentation     8.1 Printed DocumentationL    ?     Table 8-2 (Cont.) OpenVMS Full Documentation Set (QA-001AA-tE     __________________GZ.7.3)________________________________________o  E     Manual______________________________________________Order_Number_C  A                                                         QA-001AA-vE     Continuation_of_Full_Documentation_Set______________GZ.7.3_______t  C     OpenVMS VAX System Dump Analyzer Utility Manual     AA-PV6TD-TEl  C     POLYCENTER Software Installation Utility            AA-Q28MD-TKP     Developer's Guide   C     VAX MACRO and Instruction Set Reference Manual      AA-PS6GD-TEe  E     Volume_Shadowing_for_OpenVMS________________________AA-PVXMG-TE__S  6     8.1.3 Documentation for System Integrated Products  =           The following System Integrated Products (SIPs) areV=           included in the OpenVMS software. You must purchase +           separate licenses to enable them.n  A           o  Compaq Galaxy Software Architecture on OpenVMS Alphae             o  OpenVMS Clusters   '           o  RMS Journaling for OpenVMS   )           o  Volume Shadowing for OpenVMSi  C           The OpenVMS Cluster and Volume Shadowing documentation ise9           included in the OpenVMS Full Documentation set.i  D           You must purchase RMS Journaling documentation separately.C           Use the following part number to order the RMS Journalingn*           for OpenVMS Manual: AA-JG41C-TE.  (     8.1.4 Archived OpenVMS Documentation  A           OpenVMS continuously updates, revises, and enhances the_D           OpenVMS operating system documentation. From time to time,C           manuals are archived. You can access the archived manualseD           online from the documentation CD-ROM or from the following           web site:n  '           http://www.compaq.com/openvms   9           For a list of the archived OpenVMS manuals, see            Section 9.5.  0     8-6 OpenVMS Printed and Online Documentation           I                                  OpenVMS Printed and Online DocumentationVI                                        8.2 Online Documentation on CD-ROMe    *         8.2 Online Documentation on CD-ROM  F               Beginning with OpenVMS Version 7.3, online documentationB               for the OpenVMS operating system and many associatedF               products is provided on a single ISO9660 Level 2 CD-ROM.H               This CD-ROM is readable on OpenVMS, Windows, and Macintosh               systems.           8.2.1 Online Formats  I               The documentation CD-ROM contains documentation in a numberaD               of formats, including HTML, PDF, PostScript, and ASCIIC               text. Bookreader files are no longer available on the #               documentation CD-ROM.c           8.2.2 PDF Viewers   H               Tools are supplied on the documentation CD-ROM for viewingE               PDF files on OpenVMS Alpha systems and Windows systems.   D               For OpenVMS Alpha users, the Adobe Acrobat Viewer (forF               Java) is provided. Instructions for installing this JavaD               implementation of the Acrobat Viewer are provided in a(               README file on the CD-ROM.  F               For users of Windows systems, an executable file for theI               Adobe Acrobat Viewer is provided. This self-extracting file F               can be installed on a personal computer running Windows.  B               For information about how to access documents on theF               documentation CD-ROM and about the PDF viewers, refer to7               the Guide to OpenVMS Version 7.3 CD-ROMs.m  8         8.3 Online Documentation on the OpenVMS Web Site  F               You can access OpenVMS manuals in various online formats2               from the following OpenVMS web site:  +               http://www.compaq.com/openvms_  H               The OpenVMS web site contains links to current versions ofF               manuals in the OpenVMS Full Documentation set as well as4               manuals for selected layered products.    I                              OpenVMS Printed and Online Documentation 8-7e e  S      ,     OpenVMS Printed and Online Documentation     8.4 Online Help          8.4 Online Helpl  C           The OpenVMS operating system provides online help for the1D           commands, utilities, and system routines documented in the!           Full Documentation set.a  A           You can use the Help Message facility to quickly accessl>           online descriptions of system messages. In addition,=           you can add your own source files, such as messagesVA           documentation that you have written to the Help MessageS@           database. The OpenVMS System Messages: Companion GuideD           for Help Message Users manual explains how to use the HelpA           Message facility. You can also access DCL Help for Helpr           Message by entering:             $ HELP HELP/MESSAGEr                                                          0     8-8 OpenVMS Printed and Online Documentation                         I                                                                         9CI         _________________________________________________________________   I                                           Descriptions of OpenVMS Manuals     @               This chapter provides summary descriptions for the.               following OpenVMS documentation:  ?               o  Manuals in the OpenVMS Media Kit (Section 9.1)C  >               o  Manuals in the OpenVMS Full Documentation set                  (Section 9.2)  E               o  Manual about how to write device drivers for OpenVMSu,                  Alpha systems (Section 9.3)  4               o  RMS Journaling manual (Section 9.4)  /               o  Archived manuals (Section 9.5)_  5         9.1 Manuals Included in the OpenVMS Media Kit   2               Guide to OpenVMS Version 7.3 CD-ROMs  F               Provides information about the OpenVMS Alpha and OpenVMSC               VAX operating system and documentation CD-ROMs. ListsdE               the contents of the OpenVMS Version 7.3 CD-ROM package,n@               includes pointers to installation information, andC               gives instructions about how to access manuals on the #               Documentation CD-ROM.   7               OpenVMS License Management Utility Manualn  B               Describes the License Management Facility (LMF), theG               OpenVMS license management tool. LMF includes the LicensedD               Management Utility (LICENSE) and the command procedureD               VMSLICENSE.COM, which is used to register, manage, and.               track software licenses on line.  G               OpenVMS Alpha Version 7.3 Upgrade and Installation Manual   C               Provides step-by-step instructions for installing and C               upgrading the OpenVMS Alpha operating system on AlpharF               computers. Includes information about booting, shutdown,/               backup, and licensing procedures.S  I                                       Descriptions of OpenVMS Manuals 9-1h p  M      #     Descriptions of OpenVMS Manuals 1     9.1 Manuals Included in the OpenVMS Media Kit     A           OpenVMS VAX Version 7.3 Upgrade and Installation Manual   ?           Provides step-by-step instructions for installing and C           upgrading the OpenVMS VAX operating system on OpenVMS VAX B           computers. Includes information about booting, shutdown,+           backup, and licensing procedures.   0     9.2 Manuals in the OpenVMS Documentation Set  (     9.2.1 OpenVMS Base Documentation Set              OpenVMS DCL Dictionary  C           Describes the DIGITAL Command Language (DCL) and providesAC           an alphabetical listing of detailed reference informationuB           and examples for all DCL commands and lexical functions.(           This manual is in two volumes.  *           OpenVMS Guide to System Security  B           Describes the security features available in the OpenVMS?           Alpha and VAX operating systems. Explains the purposeuB           and proper application of each feature in the context of"           specific security needs.             OpenVMS Master Index  E           Offers an edited compilation of indexes from the manuals in -           the OpenVMS Full Documentation set.e  >           OpenVMS System Management Utilities Reference Manual  D           Presents reference information about the utilities you canB           use to perform system management tasks on your system asD           well as the tools to control and monitor system access andB           resources. Includes a description of the AUTOGEN command3           procedure. This manual is in two volumes._  ?           OpenVMS System Manager's Manual, Volume 1: Essentials   >           Provides instructions for setting up and maintaining<           routine operations such as starting up the system,E           installing software, and setting up print and batch queues. B           Also explains routine disk and magnetic tape operations.  <           OpenVMS System Manager's Manual, Volume 2: Tuning,)           Monitoring, and Complex Systemsr  D           Describes how to configure and control the network, how toB           monitor the system, and how to manage system parameters.B           Also includes information about OpenVMS Cluster systems,9           network environments, and DECdtm functionality.r  '     9-2 Descriptions of OpenVMS Manuals_ _  _      I                                           Descriptions of OpenVMS Manuals I                              9.2 Manuals in the OpenVMS Documentation Set     #               OpenVMS User's Manuall  G               Provides an overview of the operating system and presentsII               basic concepts, task information, and reference information H               that allow you to perform daily computing tasks. DescribesI               how to work with files and directories. Also includes these                 additional topics:  E               o  Sending messages with the Mail utility and the Phoneo                  utility  -               o  Using the Sort/Merge utilityn  0               o  Using logical names and symbols  +               o  Writing command procedures   @               o  Editing files with the EVE and EDT text editors  I               OpenVMS Version 7.3 New Features and Documentation Overviewm  E               Describes new and improved components for the Alpha and_I               VAX operating systems for the Version 7.3 release. Includes I               information about OpenVMS documentation changes for VersionnI               7.3 as well as the printed and online OpenVMS documentation                offerings.  /               OpenVMS Version 7.3 Release Notes-  G               Describes changes to the software; installation, upgrade,eF               and compatibility information; new and existing softwareG               problems and restrictions; and software and documentationg               corrections.  4         9.2.2 Continuation of Full Documentation Set  /               Availability Manager User's Guide5  I               Describes how to use the Compaq Availability Manager systemmH               management tool, from either an OpenVMS Alpha or a WindowsG               node, to monitor one or more OpenVMS nodes on an extended F               local area network (LAN) or to target a specific node or,               process for detailed analysis.  B               Compaq C Run-Time Library Utilities Reference Manual  E               Provides detailed usage and reference information about B               the Compaq C Run-Time Library utilities for managingG               localization and time zone data in international software0               applications._  I                                       Descriptions of OpenVMS Manuals 9-3_ _  _      #     Descriptions of OpenVMS Manuals 0     9.2 Manuals in the OpenVMS Documentation Set    -           Compaq Portable Mathematics Library_  C           Documents the mathematics routines in the Compaq Portables@           Mathematics Library (DPML), supplied only with OpenVMSD           Alpha systems. VAX programmers should refer to the OpenVMS,           VAX RTL Mathematics (MTH$) Manual.             DECamds User's Guide  C           Provides information for installing and using the DECamdsDE           software. DECamds is a system management tool that lets yourC           monitor, diagnose, and track events in OpenVMS system and '           OpenVMS Cluster environments.C  6           DEC Text Processing Utility Reference Manual  @           Describes the DEC Text Processing Utility (DECTPU) and=           provides reference information about the EDT Keypadt(           Emulator interfaces to DECTPU.  6           Extensible Versatile Editor Reference Manual  C           Contains command reference information about the EVE text E           editor. Also provides a cross-reference between EDT and EVE            commands.   7           Guidelines for OpenVMS Cluster ConfigurationsD  =           This manual provides information to help you chooseA@           systems, interconnects, storage devices, and software.?           It can help you configure these components to achievedB           high availability, scalability, performance, and ease ofE           system management. Detailed directions using SCSI and FibremC           Channel in an OpenVMS Cluster system are also included int           this manual.  6           Guide to Creating OpenVMS Modular Procedures  @           Describes how to perform a complex programming task by>           dividing it into modules and coding each module as a           separate procedure.   ,           Guide to OpenVMS File Applications  :           Contains guidelines for designing, creating, andE           maintaining efficient data files by using Record Management A           Services (RMS). This manual is intended for applicationtA           programmers and designers responsible for programs thatoB           use RMS files, especially if performance is an important           consideration.  '     9-4 Descriptions of OpenVMS Manuals_ _  _      I                                           Descriptions of OpenVMS ManualsrI                              9.2 Manuals in the OpenVMS Documentation Set     ,               Guide to POSIX Threads Library  A               Describes the POSIX Threads Library (formerly namedDC               DECthreads) package, Compaq's multithreading run-timeoG               libraries. Use the routines in this package to create andsF               control multiple threads of execution within the addressE               space provided by a single process. Offering both usageMH               tips and reference synopses, this document describes threeI               interfaces: routines that conform to the IEEE POSIX 1003.1c_F               standard (called pthread), routines that provide thread-B               related services in nonthreaded applications (calledF               thread-independent services or tis), and a set of CompaqF               proprietary routines (called cma) that provide a stable,,               upwardly compatible interface.  6               Guide to the DEC Text Processing Utility  E               Provides an introduction to developing DECTPU programs.n  9               OpenVMS Alpha Partitioning and Galaxy GuideB  C               Provides complete details about how to use all of theMC               OpenVMS Galaxy features and capabilities available int@               OpenVMS Alpha Version 7.3. Includes procedures forD               creating, managing, and using OpenVMS Galaxy computingG               environments on AlphaServer 8400, 8200, and 4100 systems.U  >               OpenVMS Alpha Guide to Upgrading Privileged-Code               Applications  G               Explains the OpenVMS Alpha Version 7.0 changes that might B               impact Alpha privileged-code applications and deviceE               drivers as a result of the OpenVMS Alpha 64-bit virtualnG               addressing and kernel threads support provided in OpenVMSo                Alpha Version 7.0.  I               Privileged-code applications from versions prior to OpenVMS E               Alpha Version 7.0 might require the source-code changes &               described in this guide.  8               OpenVMS Alpha System Analysis Tools Manual  F               Describes the following system analysis tools in detail,H               while also providing a summary of the dump off system disk>               (DOSD) capability and the DELTA/XDELTA debugger:  +               o  System Dump Analysis (SDA)   +               o  System code debugger (SCD)   +               o  System dump debugger (SDD)   I                                       Descriptions of OpenVMS Manuals 9-5u S  o      #     Descriptions of OpenVMS ManualsP0     9.2 Manuals in the OpenVMS Documentation Set               o  Watchpoint utilityo  ?           Intended primarily for the system programmer who mustiD           investigate the causes of system failures and debug kernel-           mode code, such as a device driver.y  "           OpenVMS Calling Standard  B           Documents the calling standard for the OpenVMS Alpha and           VAX operating system.   !           OpenVMS Cluster Systemsh  A           Describes procedures and guidelines for configuring andnA           managing OpenVMS Cluster systems. Also describes how tot?           provide high availability, building-block growth, and =           unified system management across clustered systems.   <           OpenVMS Command Definition, Librarian, and Message           Utilities Manual  B           Contains descriptive and reference information about the           following utilities:  '           o  Command Definition utility              o  Librarian utility             o  Message utility  !           OpenVMS Debugger Manualr  ;           Explains the features of the OpenVMS Debugger forc           programmers.  .           OpenVMS Delta/XDelta Debugger Manual  C           Describes the Delta/XDelta utility used to debug programscA           that run in privileged processor mode or at an elevatedP#           interrupt priority level.   7           OpenVMS Guide to Extended File Specifications   B           Provides an overview of Extended File Specifications andD           describes the overall differences and impact Extended File>           Specifications introduce to the OpenVMS environment.  -           OpenVMS I/O User's Reference Manual6  B           Contains the information that system programmers need toB           program I/O operations using the device drivers that are-           supplied with the operating system.D  '     9-6 Descriptions of OpenVMS Manuals            I                                           Descriptions of OpenVMS ManualsoI                              9.2 Manuals in the OpenVMS Documentation Set     +               OpenVMS Linker Utility Manual   F               Describes how to use the Linker utility to create imagesI               that run on OpenVMS systems. Also explains how to control a C               link operation with link qualifiers and link options.   7               OpenVMS MACRO-32 Porting and User's Guidea  H               Describes how to port existing VAX MACRO assembly languageC               code to an OpenVMS Alpha system by using the featuresnE               of the MACRO-32 compiler. Also documents how to use thei3               compiler's 64-bit addressing support.   C               OpenVMS Management Station Overview and Release Notes   D               Provides an overview of OpenVMS Management Station andF               describes how to get started using the software. OpenVMSA               Management Station is a powerful, Microsoft WindowseB               based management tool for system managers and othersF               who perform user account and printer management tasks onD               OpenVMS systems. OpenVMS Management Station provides aF               comprehensive user interface to OpenVMS user account andI               printer management. Also includes release notes for OpenVMS !               Management Station.t  ,               OpenVMS Performance Management  E               Introduces and explains the techniques used to optimizep/               performance on an OpenVMS system.n  1               OpenVMS Programming Concepts Manual   I               Describes concepts such as process creation, kernel threadstD               and the kernel threads process structure, interprocessE               communication, process control, data sharing, conditionkD               handling, and ASTs. This two-volume manual uses systemD               services, utility routines, and run-time library (RTL)E               routines to illustrate mechanisms for utilizing OpenVMS                features.M  A               OpenVMS Record Management Services Reference Manualm  >               Provides reference and usage information for all1               programmers who use RMS data files.s  I                                       Descriptions of OpenVMS Manuals 9-7            #     Descriptions of OpenVMS Manualsn0     9.2 Manuals in the OpenVMS Documentation Set    >           OpenVMS Record Management Utilities Reference Manual  B           Contains descriptive and reference information about the"           following RMS utilities:  %           o  Analyze/RMS_File utilitys  2           o  Convert and Convert/Reclaim utilities  .           o  File Definition Language facility  3           OpenVMS RTL General Purpose (OTS$) ManualM  A           Documents the general-purpose routines contained in thenB           OTS$ facility of the OpenVMS Run-Time Library. IndicatesE           which routines are specific to Alpha or VAX, as well as how 7           routines function differently on each system.   +           OpenVMS RTL Library (LIB$) Manual   A           Documents the general-purpose routines contained in the.B           LIB$ facility of the OpenVMS Run-Time Library. IndicatesE           which routines are specific to Alpha or VAX, as well as howo7           routines function differently on each system.t  5           OpenVMS RTL Screen Management (SMG$) Manual   C           Documents the screen management routines contained in the B           SMG$ facility of the OpenVMS Run-Time Library. IndicatesE           which routines are specific to Alpha or VAX, as well as howo7           routines function differently on each system.a  7           OpenVMS RTL String Manipulation (STR$) Manuals  E           Documents the string manipulation routines contained in thetB           STR$ facility of the OpenVMS Run-Time Library. IndicatesE           which routines are specific to Alpha or VAX, as well as how 7           routines function differently on each system.t  C           OpenVMS System Messages: Companion Guide for Help Messaged           Usersn  A           Describes features of the Help Message facility, a toolaE           that you can use to display message descriptions. DescribesoC           the HELP/MESSAGE command and qualifiers and also includes,A           detailed information about customizing the Help Message ?           database. Also provides descriptions of messages that B           can occur when the system and Help Message are not fully           operable.   '     9-8 Descriptions of OpenVMS ManualsA e  o      I                                           Descriptions of OpenVMS ManualstI                              9.2 Manuals in the OpenVMS Documentation Sett    6               OpenVMS System Services Reference Manual  I               Presents the set of routines that the operating system uses H               to control resources, allow process communication, controlE               I/O, and perform other such operating system functions.i,               This manual is in two volumes.  -               OpenVMS Utility Routines Manuali  D               Describes the routines that allow a program to use the?               callable interface of selected OpenVMS utilities.   7               OpenVMS VAX RTL Mathematics (MTH$) Manuale  F               Documents the mathematics routines contained in the MTH$I               facility of the OpenVMS Run-Time Library, which is relevantaG               only to programmers using OpenVMS VAX. (Alpha programmers.C               should refer to Compaq Portable Mathematics Library.)i  =               OpenVMS VAX System Dump Analyzer Utility Manuall  E               Explains how to use the System Dump Analyzer utility toeG               investigate system failures and examine a running OpenVMSiF               VAX system. VAX programmers should refer to this manual;H               Alpha programmers should refer to the OpenVMS Alpha System+               Dump Analyzer Utility Manual.o  H               POLYCENTER Software Installation Utility Developer's Guide  A               Describes the procedure and provides guidelines for G               developing software products that will be installed using H               the POLYCENTER Software Installation utility. Intended forF               developers who are designing installation procedures forH               software products layered on the OpenVMS operating system.  <               VAX MACRO and Instruction Set Reference Manual  F               Documents both the assembler directives of VAX MACRO and&               the VAX instruction set.  *               Volume Shadowing for OpenVMS  H               Describes how to provide high data availability with phase"               II volume shadowing.  I                                       Descriptions of OpenVMS Manuals 9-9            #     Descriptions of OpenVMS Manualso*     9.3 OpenVMS Alpha Device Driver Manual    *     9.3 OpenVMS Alpha Device Driver Manual  3           Writing OpenVMS Alpha Device Drivers in C   >           Provides definitive information about writing deviceE           drivers in the C programming language for devices connectedoC           to Alpha processors. Writing OpenVMS Alpha Device DriverssE           in C is available from Digital Press. For more information,u(           access the following web site:  (           http://www.bh.com/digitalpress       9.4 RMS Journaling Manual   +           RMS Journaling for OpenVMS Manuali  @           Describes the three types of RMS Journaling as well as?           other OpenVMS components that support RMS Journaling. =           This manual also describes the RMS Recovery utility A           (which is used to recover data saved using journaling),e@           the transaction processing system services, and system>           management tasks required when using RMS Journaling.       9.5 Archived Manuals  <           Table 9-1 lists the OpenVMS manuals that have been.           archived. Please note the following:  ?           o  Most archived manuals can be ordered separately in C              printed format from Compaq. To order archived manuals,c?              call 800-344-4825 and have the book title and part               number.  >           o  Archived manuals are available in various formats>              (PostScript and PDF) on the documentation CD-ROM.  @           o  Most information from the archived manuals has been<              incorporated in other documents or online help.  E           Table_9-1_Archived_OpenVMS_Manuals_________________________   E           Manual_____________________________________Order_Number____   @           A Comparison of System Management on       AA-PV71B-TE%           OpenVMS AXP and OpenVMS VAXo  E                                              (continued on next page)i  (     9-10 Descriptions of OpenVMS Manuals t  t      I                                           Descriptions of OpenVMS ManualsmI                                                      9.5 Archived Manualsa    I               Table_9-1_(Cont.)_Archived_OpenVMS_Manuals_________________   I               Manual_____________________________________Order_Number____t  D               Building Dependable Systems: The OpenVMS   AA-PV5YB-TE               Approach  D               Creating an OpenVMS Alpha Device Driver    AA-R0Y8A-TE/               from an OpenVMS VAX Device Drivert  D               Creating an OpenVMS AXP Step 2 Device      AA-Q28TA-TE0               Driver from a Step 1 Device Driver  D               Creating an OpenVMS AXP Step 2 Device      AA-Q28UA-TE6               Driver from an OpenVMS VAX Device Driver  D               Guide to OpenVMS AXP Performance           AA-Q28WA-TE               Management  D               Guide to OpenVMS Performance Management    AA-PV5XA-TE  D               Migrating an Application from OpenVMS VAX  AA-KSBKB-TE               to OpenVMS Alpha  D               Migrating an Environment from OpenVMS VAX  AA-QSBLA-TE               to OpenVMS Alpha  D               Migrating to an OpenVMS AXP System:        AA-PV62A-TE$               Planning for Migration  D               Migrating to an OpenVMS AXP System:        AA-PV63A-TE4               Recompiling and Relinking Applications  D               OpenVMS Alpha Guide to 64-Bit Addressing   AA-QSBCC-TE               and VLM Features  D               OpenVMS Alpha System Dump Analyzer         AA-PV6UC-TE               Utility Manual  D               OpenVMS AXP Device Support: Developer's    AA-Q28SA-TE               Guide   D               OpenVMS AXP Device Support: Reference      AA-Q28PA-TE  D               OpenVMS Bad Block Locator Utility Manual   AA-PS69A-TE  D               OpenVMS Compatibility Between VAX and      AA-PYQ4C-TE               Alphae  D               OpenVMS Developer's Guide to VMSINSTAL     AA-PWBXA-TE  D               OpenVMS DIGITAL Standard Runoff Reference  AA-PS6HA-TE               Manual  I                                                  (continued on next page)a  I                                      Descriptions of OpenVMS Manuals 9-11o           #     Descriptions of OpenVMS Manualsc     9.5 Archived Manuals    E           Table_9-1_(Cont.)_Archived_OpenVMS_Manuals_________________c  E           Manual_____________________________________Order_Number____   @           OpenVMS EDT Reference Manual               AA-PS6KA-TE  @           OpenVMS Exchange Utility Manual            AA-PS6AA-TE  @           OpenVMS Glossary                           AA-PV5UA-TK  @           OpenVMS National Character Set Utility     AA-PS6FA-TE           Manual  @           OpenVMS Obsolete Features Manual           AA-PS6JA-TE  @           OpenVMS Programming Environment Manual     AA-PV66B-TK  @           OpenVMS Programming Interfaces: Calling a  AA-PV68B-TK           System Routine  @           OpenVMS RTL DECtalk (DTK$) Manual          AA-PS6CA-TE  @           OpenVMS RTL Parallel Processing (PPL$)     AA-PV6JA-TK           Manual  @           OpenVMS Software Overview                  AA-PVXHB-TE  @           OpenVMS SUMSLP Utility Manual              AA-PS6EA-TE  @           OpenVMS System Messages and Recovery       AA-PVXKA-TE*           Procedures Reference Manual: A-L  @           OpenVMS System Messages and Recovery       AA-PVXLA-TE*           Procedures Reference Manual: M-Z  @           OpenVMS Terminal Fallback Utility Manual   AA-PS6BA-TE  @           OpenVMS VAX Card Reader, Line Printer,     AA-PVXGA-TE1           and LPA11-K I/O User's Reference Manuali  @           OpenVMS VAX Device Support Manual          AA-PWC8A-TE  @           OpenVMS VAX Device Support Reference       AA-PWC9A-TE           Manual  @           OpenVMS VAX Patch Utility Manual           AA-PS6DA-TE  @           OpenVMS Wide Area Network I/O User's       AA-PWC7A-TE           Reference Manual  @           PDP-11 TECO User's Guide                   AA-K420B-TC  @           POLYCENTER Software Installation Utility   AA-Q28NA-TK           User's Guide  @           TCP/IP Networking on OpenVMS Systems       AA-QJGDB-TE  E                                              (continued on next page)e  (     9-12 Descriptions of OpenVMS Manuals           I                                           Descriptions of OpenVMS ManualsAI                                                      9.5 Archived Manualss    I               Table_9-1_(Cont.)_Archived_OpenVMS_Manuals_________________h  I               Manual_____________________________________Order_Number____   G               Standard TECO Text Editor and Corrector    Available only I               for_the_VAX,_PDP-11,_PDP-10,_and_PDP-8_____on_CD-ROM_______   E               Table 9-2 lists the networking manuals and installationi2               supplements that have been archived.  D               Table 9-2 Archived Networking Manuals and InstallationI               __________Supplements______________________________________   I               Manual_____________________________________Order_Number____   D               DECnet for OpenVMS Guide to Networking     AA-PV5ZA-TK  D               DECnet for OpenVMS Network Management      AA-PV61A-TK               Utilitiesu  D               DECnet for OpenVMS Networking Manual       AA-PV60A-TK  D               OpenVMS VAX Upgrade and Installation       AA-PS6MA-TE.               Supplement: VAX 8820, 8830, 8840  D               OpenVMS VAX Upgrade and Installation       AA-PS6PA-TE4               Supplement: VAX 8200, 8250, 8300, 8350  D               OpenVMS VAX Upgrade and Installation       AA-PS6QA-TE6               Supplement: VAX 8530, 8550, 8810 (8700),               and 8820-N (8800)   D               OpenVMS VAX Upgrade and Installation       AA-PS6UA-TE(               Supplement: VAX 8600, 8650  D               VMS Upgrade and Installation Supplement:   AA-LB29B-TE               VAX-11/780, 785   D               VMS Upgrade and Installation Supplement:   AA-LB30B-TEI               VAX-11/750_________________________________________________   A               Descriptions of the archived OpenVMS manuals are asi               follows:    I                                      Descriptions of OpenVMS Manuals 9-13            #     Descriptions of OpenVMS Manualsu     9.5 Archived Manuals    >           A Comparison of System Management on OpenVMS AXP and           OpenVMS VAX   E           Discusses system management tools, the impact of Alpha page E           sizes on system management operations, the system directory =           structure, interoperability issues, and performance E           information. Designed for system managers who need to learn 8           quickly how to manage an OpenVMS Alpha system.  ;           Building Dependable Systems: The OpenVMS Approachl  :           Offers practical information about analyzing theB           dependability requirements of your business applicationsC           and deciding how to use your computing systems to supporttD           your dependability goals. This information is complementedA           by technical summaries of the dependability features ofDE           OpenVMS and related hardware and layered software products.   E           Creating an OpenVMS Alpha Device Driver from an OpenVMS VAX            Device Drivern  A           Describes the procedures for converting a device driverkE           used on OpenVMS VAX to a device driver that runs on OpenVMSlC           Alpha. This book also contains data structures, routines, ?           and macros for maintaining an Alpha driver written ink           Macro-32.o  D           Creating an OpenVMS AXP Step 2 Device Driver from a Step 1           Device Drivero  C           Provides information for upgrading a Step 1 device drivern?           (used in earlier versions of OpenVMS AXP) to a Step 2e?           device driver. A Step 2 device driver is required for "           OpenVMS AXP Version 6.1.  >           Creating an OpenVMS AXP Step 2 Device Driver from an#           OpenVMS VAX Device Driver   D           Provides information for migrating a device driver used onC           OpenVMS VAX to a Step 2 device driver used on OpenVMS AXPS           Version 6.1.  5           Guide to OpenVMS AXP Performance Management   A           Introduces and explains the techniques used to optimized1           performance on an OpenVMS Alpha system.   1           Guide to OpenVMS Performance Management   A           Introduces and explains the techniques used to optimize /           performance on an OpenVMS VAX system.s  (     9-14 Descriptions of OpenVMS Manuals S  i      I                                           Descriptions of OpenVMS ManualsaI                                                      9.5 Archived Manualsa    H               Migrating an Application from OpenVMS VAX to OpenVMS Alpha  D               Describes how to create an OpenVMS Alpha version of anF               OpenVMS VAX application. Provides an overview of the VAXI               to Alpha migration process and information to help you plan F               a migration. It discusses the decisions you must make inF               planning a migration and the ways to get the informationH               you need to make those decisions. In addition, this manualG               describes the migration methods available so that you cannF               estimate the amount of work required for each method andC               select the method best suited to a given application.   H               Migrating an Environment from OpenVMS VAX to OpenVMS Alpha  F               Describes how to migrate a computing environment from anG               OpenVMS VAX system to an OpenVMS Alpha system or a mixed-eF               architecture cluster. Provides an overview of the VAX toF               Alpha migration process and describes the differences inG               system and network management on VAX and Alpha computers.   H               Migrating to an OpenVMS AXP System: Planning for Migration  ;               Describes the general characteristics of RISCpG               architectures, compares the Alpha architecture to the VAXnE               architecture, and presents an overview of the migrationaB               process and a summary of migration tools provided byC               Compaq. The information in this manual is intended to E               help you define the optimal migration strategy for your                application.  A               Migrating to an OpenVMS AXP System: Recompiling and $               Relinking Applications  I               Provides detailed technical information for programmers who F               must migrate high-level language applications to OpenVMSI               Alpha. Describes how to set up a development environment tonI               facilitate the migration of applications, helps programmers B               identify application dependencies on elements of theE               VAX architecture, and introduces compiler features that E               help resolve these dependencies. Individual sections oftC               this manual discuss specific application dependencies F               on VAX architectural features, data porting issues (suchF               as alignment concerns), and the process of migrating VAX               shareable images.G  I                                      Descriptions of OpenVMS Manuals 9-15h e  M      #     Descriptions of OpenVMS Manualsu     9.5 Archived Manuals    C           OpenVMS Alpha Guide to 64-Bit Addressing and VLM Featuresi  A           Introduces and describes OpenVMS Alpha operating systemiE           support for 64-bit virtual addressing and Very Large Memory A           (VLM). Intended for system and application programmers,eD           this guide highlights the features and benefits of OpenVMSB           Alpha 64-bit and VLM capabilities. It also describes howB           to use these features to enhance application programs toB           support 64-bit addresses and to efficiently harness very            large physical memory.  ;           OpenVMS Alpha System Dump Analyzer Utility Manual   A           Explains how to use the System Dump Analyzer utility tonC           investigate system failures and examine a running OpenVMS >           Alpha system. Alpha programmers should refer to thisA           manual; VAX programmers should refer to the OpenVMS VAX .           System Dump Analyzer Utility Manual.  7           OpenVMS AXP Device Support: Developer's GuideS  A           Describes how to write a driver for OpenVMS Alpha for aa(           device not supplied by Compaq.  /           OpenVMS AXP Device Support: Referencea  A           Provides the reference material for the Writing OpenVMS :           Alpha Device Drivers in C by describing the data@           structures, macros, and routines used in device-driver           programming.  2           OpenVMS Bad Block Locator Utility Manual  ?           Describes how to use the Bad Block Locator utility toe4           locate bad blocks on older types of media.  5           OpenVMS Compatibility Between VAX and Alphaa  D           Compares and contrasts OpenVMS on VAX and Alpha computers,@           focusing on the features provided to end users, system$           managers, and programmers.  0           OpenVMS Developer's Guide to VMSINSTAL  @           Describes the VMSINSTAL command procedure and provides?           guidelines for designing installation procedures thattB           conform to standards recommended by Compaq. Intended forB           developers who are designing installation procedures forD           software products layered on the OpenVMS operating system.  :           OpenVMS DIGITAL Standard Runoff Reference Manual  4           Describes the DSR text-formatting utility.  (     9-16 Descriptions of OpenVMS Manuals           I                                           Descriptions of OpenVMS Manuals I                                                      9.5 Archived Manuals     *               OpenVMS EDT Reference Manual  I               Contains complete reference information for the EDT editor.   -               OpenVMS Exchange Utility Manualp  I               Describes how to use the Exchange utility to transfer filesuD               between some foreign format volumes and OpenVMS native               volumes.                 OpenVMS Glossary  H               Defines terms specific to OpenVMS that are used throughout                the documentation.  ;               OpenVMS National Character Set Utility ManualD  H               Describes how to use the National character set utility to)               build NCS definition files.e  .               OpenVMS Obsolete Features Manual  G               Presents the DCL commands, system services, RTL routines,fD               and utilities made obsolete by VMS Version 4.0 throughD               Version 5.0. Includes an appendix of DCL commands, RTLF               routines, and utilities eliminated from VMS Version 4.0.  4               OpenVMS Programming Environment Manual  C               Provides a general description of Compaq products andRG               tools that define the programming environment. IntroduceshI               facilities and tools such as the compilers, the linker, thewF               debugger, the System Dump Analyzer, system services, and                routine libraries.  F               OpenVMS Programming Interfaces: Calling a System Routine  E               Describes the OpenVMS programming interface and definese@               the standard conventions to call an OpenVMS systemH               routine from a user procedure. The Alpha and VAX data typeG               implementations for various high-level languages are alsoc'               presented in this manual._  /               OpenVMS RTL DECtalk (DTK$) Manual_  E               Documents the DECtalk support routines contained in the_<               DTK$ facility of the OpenVMS Run-Time Library.  ;               OpenVMS RTL Parallel Processing (PPL$) Manual   I               Documents the parallel-processing routines contained in thepF               PPL$ facility of the OpenVMS Run-Time Library. IndicatesI               which routines are specific to Alpha or VAX, as well as how ;               routines function differently on each system.   I                                      Descriptions of OpenVMS Manuals 9-17  u  _      #     Descriptions of OpenVMS Manualsm     9.5 Archived Manuals    #           OpenVMS Software Overview   B           Provides an overview of the OpenVMS operating system and)           some of its available products.   '           OpenVMS SUMSLP Utility Manualt  B           Describes how to use the SUMSLP batch-oriented editor to           update source files.  C           OpenVMS System Messages and Recovery Procedures Referencev           Manual  C           Contains an alphabetical listing of the errors, warnings, D           and informational messages issued by the operating system.C           Also provides the meaning of each message and a statementnE           of the action to be taken in response to each message. This #           manual is in two volumes.e  2           OpenVMS Terminal Fallback Utility Manual  ?           Describes how to use the Terminal Fallback utility to @           manage the libraries, character conversion tables, andE           terminal parameters that are available within this utility.p  @           OpenVMS VAX Card Reader, Line Printer, and LPA11-K I/O!           User's Reference Manual   :           Describes the card reader, laboratory peripheral?           accelerator, and line printer drivers on OpenVMS VAX.m  +           OpenVMS VAX Device Support Manual   C           Describes how to write an OpenVMS VAX driver for a device'!           not supplied by Compaq.d  5           OpenVMS VAX Device Support Reference Manual   D           Provides the reference material for the OpenVMS VAX DeviceC           Support Manual by describing the data structures, macros,n9           and routines used in device-driver programming.p  *           OpenVMS VAX Patch Utility Manual  ?           Describes how to use the Patch utility to examine andA=           modify executable and shareable OpenVMS VAX images.   ?           OpenVMS Wide Area Network I/O User's Reference Manual   @           Describes the DMC11/DMR11, DMP11 and DMF32, DR11-W andE           DRV11-WA, DR32, and asynchronous DDCMP interface drivers on            OpenVMS VAX.  (     9-18 Descriptions of OpenVMS Manuals           I                                           Descriptions of OpenVMS Manuals I                                                      9.5 Archived Manuals     &               PDP-11 TECO User's Guide  D               Describes the operating procedures for the PDP-11 TECO2               (Text Editor and Corrector) program.  C               POLYCENTER Software Installation Utility User's Guide   =               Provides information on the POLYCENTER SoftwareiI               Installation utility, a new component that lets you install G               and manage software products that are compatible with the                utility.  2               TCP/IP Networking on OpenVMS Systems  H               Provides an introductory overview of TCP/IP networking andD               describes OpenVMS DCL support for TCP/IP capabilities.                                                          I                                      Descriptions of OpenVMS Manuals 9-19f n  M                            F      _________________________________________________________________  F                                                                  Index    B      A                                 Compaq 3X-DAPCA-FA adapter,-      _______________________________      5-2R;      Advanced Server for OpenVMS,      Compaq Analyze,  6-9a?         6-2                            Compaq BridgeWorks,  2-5fC      ANALYZE/PROCESS_DUMP command,     Compaq COM for OpenVMS,  2-2aA         5-13                           Compaq Crash Analysis ToolA6      ATM                                  (CCAT),  6-99        cluster interconnect, 4-15      Compaq C RTL,  5-3 B      Attunity Connect "On Platform"      case preservation in file6         Package, 2-3                        names, 5-4C      Availability Manager,  6-1          exact case argv arguments, /                                             5-5nF      B______________________________     long file names as arguments,/      Backup using Volume Shadowing          5-5oD         for OpenVMS, 4-30                nested directory limitation7      64-bit addresses                       lifted, 5-4_<        support for, 5-7                  new functions,  5-7<                                          shared access,  5-6@      C                                   strptime function,  5-3B      _______________________________     support for extended file?      Case preservation in file              specifications, 5-4rD         names, C RTL, 5-4                UNIX file-spec translation,/      Class scheduler                        5-6ND        CPU scheduling, 4-3             Compaq DECwindows Motif,  6-3B      Cluster interconnects             Compaq Enterprise DirectoryB        LANs as cluster interconects,      Services for e-Business,-          4-16                             2-4VB      Clusterwide intrusion             Compaq Fast Virtual MachineB         detection, 4-12                   (Fast VM) for the Java 28      Compaq 3X-DAPBA-FA adapter,          Platform,  2-3         5-2p        F                                                                Index-1    0              ;     Compaq Java 2 SDK, Standard        DCL command (cont'd) 9        Edition, for OpenVMS Alpha,      SHOW SERVER,  3-4 4        2-2                              UNLOCK,  3-42     Compaq Secure Web Server for       DCL lexical6        OpenVMS Alpha, 2-2               F$GETDVI,  3-46     Compaq System Tools CD-ROM,         F$GETJPI,  3-46        6-9                              F$GETQUI,  3-46     Compaq Volume Shadowing for         F$GETSYI,  3-4<        OpenVMS, 4-29                   Debugger multiprocess=     Compaq XML Technology,  2-3          functionality,  5-10 4     CPU Online Replace,  4-2           DECevent, 6-9B     CPU scheduling                     Dedicated CPU Lock Manager,,       class scheduler,  4-3              4-56                                         enabling,  4-6:     D______________________________     implementing,  4-5>     Daylight Savings Time               setting affinity,  4-7E       automatic setting,  4-3           supporting fast path devices, .     DCL command                            4-8E       ANALYZE/IMAGE,  3-1              DISMOUNT/FORCE_REMOVAL commande/       ANALYZE/OBJECT,  3-1                 4-31t<       ANALYZE/PROCESS,  3-1            DSGGB-AA switch, 4-14<       DELETE,  3-1                     DSGGB-AB switch, 4-149       DELETE/INTRUSION,  3-1           DUMP command, 5-26n1       DIRECTORY,  3-1                  Dump filesf8       DISMOUNT,  3-1                    analyzing,  5-12@       DUMP,  3-2                           on different systems,2       INITIALIZE,  3-2                        5-146       MOUNT,  3-2                       forcing,  5-15         SET AUDIT,  3-2 F       SET CACHE,  3-2                  E______________________________  9       SET DEVICE,  3-2                 ECP Collector, 6-6sD       SET DISPLAY,  3-2                ECP Performance Analyzer, 6-6>       SET FILE,  3-2                   Enterprise Capacity and@       SET PROCESS,  3-3                  Performance (ECP),  6-5=       SET RMS_DEFAULT,  3-3            /ERASE qualifier, 4-37TC       SET RMS_DEFAULT/QUERY_LOCK       Exact case argv arguments, Cr2          (Alpha), 5-21                   RTL,  5-50       SET SERVER,  3-3                 Executive>       SET VOLUME,  3-3                  nonpaged design,  1-12A       SHOW CPU,  3-3                   Extended File Cache, 4-10,i-       SHOW DEVICES,  3-3                 4-18eC       SHOW INTRUSION,  3-3             Extended file specificationse:       SHOW LICENSE,  3-3                Compaq C RTL,  5-4       SHOW MEMORY,  3-3M       SHOW RMS_DEFAULT,  3-4       Index-2  n                 F                                           LCKMGR_SERVER process,  4-6,0         F______________________________      4-74         FAB$B_SHR field, 5-21             LDAP,  6-8F         Fibre Channel support, 4-13       Lightweight Directory AccessA         Fibre Channel tape support,          Protocol (LDAP), 6-8r9           4-15                            Long file nameseI         Firmware, 1-4                       arguments to C RTL functions,i1         Floppy disks                          5-5             serving,  4-13 I                                           M______________________________   I         G______________________________   MA6000 storage subsystem,  4-14   D         Gigabit Ethernet                  MDR (Modular Data Router),1          cluster interconnect,  4-15         4-15pC         GLX_SHM_REG system parameter,     Minicopy operation,  4-29o?           4-23                              write bitmaps, 4-29 9                                           MONITOR utilityf>         H______________________________     new features, 4-11G         HSG60 storage controller, 4-14    Multiprocess debugging,  5-10d  I         I                                 N______________________________oE         _______________________________   Nested directory limitationh?         INITIALIZE command                   lifted, C RTL, 5-4 @          /ERASE qualifier,  4-37          Network authentication9          /SHADOW qualifier,  4-37           Kerberos, 6-7iD         Intrusion detection               Nonpaged executive change,1          clusterwide,  4-12                  1-12t         IO_PREFER_CPUS system +           parameter,  4-8                 OxI                                           _______________________________oH         K______________________________   OpenVMS Cluster systems,  4-15F         Kerberos, 6-7                       disaster-tolerant support,2         KGPSA-CA host adapter, 4-14           4-30G                                             Fibre Channel support, 4-13iE         L                                   floppy disk serving, 4-13cG         _______________________________     mixed-architecture support, 2         LANs                                  4-17G          switched,  4-15                    mixed-version support, 4-17t?         LCKMGR_CPUID system parameter,      remedial kits, 4-18iF           4-7                               switched LAN support, 4-15C         LCKMGR_MODE system parameter,       warranted and migration <           4-6                                 support,  4-17G                                           OpenVMS e-Business,  1-3, 2-1g  I                                                                   Index-3t e  p              5     OpenVMS Enterprise Directory       REPEAT commandn>        for e-Business                   count parameter,  5-33C       LDAP,  4-9                        /UNTIL=condition qualifier,u/       X.500,  4-9                          5-33 A     OpenVMS Registry,  5-24            Revision and Configuration   E                                          Management (RCM) tools,  6-9 *     P______________________________    RMS<     Page-file sections                  controlling deadlock:       larger limits (Alpha),  5-7          detection, 5-23E     PATHWORKS for OpenVMS,  6-8         minimizing locking for sharednC     PEDRIVER,  4-15                        access to global buffers.8     POLYCENTER Software                    (Alpha), 5-19E        Installation Utility, 5-11       minimizing record locking forsB     Process dumps                          read accesses to sharedC       disk quota,  5-15                    files (Alpha only), 5-20yC       privileged users,  5-16           setting global buffers on ah:       security,  5-15, 5-17                data file, 5-19B     Process dump tools,  5-12           specifying no query record@     Programming features,  1-10            locking (Alpha), 5-21  F     R______________________________    S______________________________  @     RAB$V_NLK option,  5-21            SCA Control Program, 4-16,     RAB$V_NODLCKBLK option,  5-23      SCACP?     RAB$V_NODLCKWT option,  5-23        See SCA Control Programn?     RAB$V_NQL option,  5-21            SDA commands, 5-14, 5-25aA     RAB$V_RRL option,  5-21             Spinlock Tracing utility,d/     RAB$W_ROP field,  5-21                 5-39 E     RAB$W_ROP_2 field,  5-21, 5-23     SDA qualifiers and parameters,o!     RAD_SUPPORT system parameter, -        4-25                              5-25 C     Record locking with RMS            SDA Spinlock Tracing utilityi?       controlling deadlock              SPL LOAD command,  5-40aE          detection, 5-23                SPL SHOW TRACE command,  5-40rB       specifying no query record        SPL START COLLECT command,/          locking (Alpha), 5-21             5-42 @       using read-mode bucket            SPL START TRACE command,/          locking (Alpha), 5-19             5-42 A     REG$CP,  5-25                       SPL STOP COLLECT command, /     Registry system service,  5-24         5-44 E     $REGISTRY system service,  5-24     SPL STOP TRACE command,  5-44oA     Reliable Transaction Router         SPL UNLOAD command,  5-44a5        (RTR), 2-4                      SEARCH command ?                                         /STEPS qualifier,  5-34r       Index-4v s                 A         Security                          SHOW RAD command,  5-32 ?          clusterwide intrusion            SHOW RESOURCE commandoB             detection,  4-12                /OWNED qualifier, 5-38@          Kerberos,  6-7                   SHOW SPINLOCKS commandC         SET DEVICE command                  /COUNTS qualifier, 5-39e>          new volume shadowing             SHOW SUMMARY commandF             qualifiers,  4-31               /PROCESS_NAME=process_name>          site qualfiers,  4-33                qualifier,  5-39A         SET OUTPUT command                SHOW TQE command,  5-32nA          /HEADER/NOHEADER qualifiers,     strptime function,  5-3cE             5-34                          System management features,i0         SET PROCESS command                  1-4;          /DUMP qualifier,  5-15           System parameterseA          /NEXT qualifier,  5-35             AUTO_DLIGHT_SAV, 4-22uA         SET RMS_DEFAULT/QUERY_LOCK          FAST_PATH_PORTS, 4-22m>           command (Alpha),  5-21            LCKMGR_CPUID, 4-23=         SET SYMBOLIZE command, 5-29         LCKMGR_MODE, 4-23t;         /SHADOW qualifier, 4-37             NPAGECALC, 4-24t:         Shared access, C RTL, 5-6           NPAGERAD, 4-24A         SHOW DEVICE command                 SHADOW_MAX_UNIT, 4-25 A          /CDT qualifier,  5-35              VCC_MAX_IO_SIZE, 4-26n?          /PDT qualifier,  5-35              VCC_READAHEAD, 4-260=          /UCB qualifier,  5-35              WBM_MSG_INT, 4-27L?         SHOW GCT                            WBM_MSG_LOWER, 4-27f?          /CHILDREN qualifier,  5-36         WBM_MSG_UPPER, 4-28m?         SHOW LOCK command                   WBM_OPCOM_LVL, 4-29p9          DPC keyword,  5-36               System servicesaC         SHOW MEMORY command, 5-29           $CHECK_PRIVILEGES, 5-44c9         SHOW PFN_DATA command               $CLRAST, 5-44r9          /RAD [=n] qualifier,  5-36         $DCLEXH, 5-44 C         SHOW POOL command                   $DELETE_INTRUSION, 5-44sC          /BRIEF qualifier,  5-36            $DEVICE_PATH_SCAN, 5-44g9          /CHECK qualifier,  5-36            $DISMOU, 5-44c9          /MAXIMUM_BYTES qualifier,          $EXPREG, 5-44 9             5-36                            $GETDVI, 5-45 9          /STATISTICS [=ALL] qualifier,      $GETJPI, 5-45a9             5-36                            $GETQUI, 5-45 9          /UNUSED qualifier,  5-36           $GETRMI, 5-45u9         SHOW PROCESS command                $GETSYI, 5-45 =          /FID_ONLY qualifier,  5-37         $IO_PERFORM, 5-45 9          /GSTX=index qualifier,  5-37       $MGBLSC, 5-45 8          /IMAGES [=ALL] qualifier,          $MOUNT, 5-45@             5-37                            $PERSONA_QUERY, 5-46?          /NEXT qualifier,  5-37             $PROCESS_SCAN, 5-46o;          /PST qualifier,  5-37              $REGISTRY, 5-46oA                                             $SCAN_INTRUSION, 5-46   I                                                                   Index-5p M  a              9     System services (cont'd)           User features, 1-3 7       $SCHED,  5-46                    Utility routinesn9       $SET_DEVICE,  5-46                online help,  3-4          $SET_SECURITY,  5-46F       $SET_SYSTEM_EVENT,  5-46         V______________________________.       $SHOW_INTRUSION,  5-46           VAX SDA;       $WAKE,  5-46                      TCP/IP files,  5-46c  5                                        Visual ThreadslB     T______________________________     new version support,  5-48  C     TCP/IP files                       Volume Shadowing for OpenVMSnB       VAX SDA,  5-46                    disaster-tolerant support,/     TCPIP$BGDRIVER.STB                     4-30 =       global symbols,  5-47             minicopy,  4-18, 4-29c     TCPIP$INTEETACP.STB F       global symbols,  5-47            W______________________________D     TCPIP$INTERNET_SERVICES.STB        Web-Based Enterprise Services6       global symbols,  5-47              (WEBES),  6-9E     TCPIP$NET_GLOBALS.STB file,        World-Wide PostScript Printing 8        5-47                              Subsystem,  3-6:     TCPIP$NFS_GLOBALS.STB file,        Write bitmaps, 4-291        5-47                            WWPPS, 3-6       TCPIP$NFS_SERVICES.STB file,(        5-48                            XF     TCPIP$PROXY_GLOBALS.STB file,      _______________________________*        5-47                            XFC  ?     TCPIP$PROXY_SERVICES.STB file,      See Extended File Cachen          5-48      TCPIP$PWIPACP.STBl       global symbols,  5-48t     TCPIP$PWIPDRIVER.STB       global symbols,  5-48r      TCPIP$PWIP_GLOBALS.STB file,        5-47c     TCPIP$TNDRIVER.STB       global symbols,  5-48e     TCPIP$TN_GLOBALS.STB file,        5-47i  #     U______________________________        UNDEFINE command,  5-33i!     UNIX file-spec translation, Ce        RTL, 5-6        Index-6h