                                           H                     ____________________________________________________'                     OpenVMS Version 6.2 '                     New Features Manual     -                     Order Number: AA-QJEEA-TE                          May 1995  I                     This manual describes the new features of the OpenVMS E                     VAX Version 6.2 and the OpenVMS Alpha Version 6.2 &                     operating systems.              G                     Revision/Update Information:  This is a new manual.   ?                     Software Version:             OpenVMS Alpha =                                                   Version 6.2 E                                                   OpenVMS VAX Version 5                                                   6.2       1                     Digital Equipment Corporation *                     Maynard, Massachusetts                 N               ________________________________________________________________               May 1995  D               Digital Equipment Corporation makes no representationsE               that the use of its products in the manner described in F               this publication will not infringe on existing or futureF               patent rights, nor do the descriptions contained in thisF               publication imply the granting of licenses to make, use,B               or sell equipment or software in accordance with the               description.  F               Possession, use, or copying of the software described inE               this publication is authorized only pursuant to a valid H               written license from Digital or an authorized sublicensor.  F               Digital conducts its business in a manner that conservesG               the environment and protects the safety and health of its 6               employees, customers, and the community.  H                Digital Equipment Corporation 1995. All rights reserved.  ?               The following are trademarks of Digital Equipment F               Corporation: AlphaServer, AlphaStation, AXP, Bookreader,B               CI, DECchip, DECmcc, DECmigrate, DECnet, DECnet/OSI,H               DECserver, DECwindows, Digital, HSC, HSJ, HSZ, InfoServer,B               LAT, MicroVAX, MSCP, OpenVMS, PATHWORKS, POLYCENTER,G               StorageWorks, ThinWire, TMSCP, TURBOchannel, ULTRIX, VAX, D               VAX DOCUMENT, VAXcluster, VMS, VMScluster, VT, and the               DIGITAL logo.   7               The following are third-party trademarks:   5               Adaptec is a trademark of Adaptec, Inc.   I               Futurebus/Plus is a registered trademark of Force Computers                GMBH, Germany.  E               IBM is a registered trademark of International Business #               Machines Corporation.   F               IEEE is a registered trademark and POSIX is a registeredC               certification mark of the Institute of Electrical and $               Electronics Engineers.  B               Internet is a registered trademark of Internet, Inc.  E               Microsoft, MS, and MS-DOS are registered trademarks and >               Windows is a trademark of Microsoft Corporation.  I               NetView is a registered trademark of International Business #               Machines Corporation.   @               Proteon is a trademark of Proteon Associates, Inc.  I               UNIX is a registered trademark of Unix System Laboratories, <               Inc. a wholly-owned subsidiary of Novell, Inc.  D               All other trademarks and registered trademarks are the3               property of their respective holders.   I                                                                    ZK6442   3               This document is available on CD-ROM.   H               This document was prepared using VAX DOCUMENT Version 2.1.                                Send Us Your Comments   C               We welcome your comments on this or any other OpenVMS H               manual. If you have suggestions for improving a particularD               section or find any errors, please indicate the title,A               order number, chapter, section, and page number (if E               available). We also welcome more general comments. Your C               input is valuable in improving future releases of our                documentation.  @               You can send comments to us in the following ways:  E               o  Internet electronic mail: openvmsdoc@zko.mts.dec.com   F               o  Fax: 603-881-0120 Attn: OpenVMS Documentation, ZKO3-4                  /U08                  o  Online form  C                  Print or edit the online form SYS$HELP:OPENVMSDOC_ @                  COMMENTS.TXT. Send the completed online form byE                  electronic mail to our Internet address, or send the E                  completed hardcopy form by fax or through the postal                   service.   4                  Please send letters or the form to:  .                  Digital Equipment Corporation2                  Information Design and Consulting&                  OpenVMS Documentation0                  110 Spit Brook Road, ZKO3-4/U08'                  Nashua, NH  03062-2698                   USA                 Thank you.                I                                                                       iii                    -         How To Order Additional Documentation   G               Use the following table to order additional documentation =               or information. If you need help deciding which C               documentation best meets your needs, call 800-DIGITAL                (800-344-4825).                                                                               
         iv                                 F      _________________________________________________________________  F                                                               Contents      F      Preface...................................................     xv  +      1  Summary of Version 6.2 New Features           2  General User Features   F            2.1   OpenVMS Freeware for VAX and Alpha Systems....    2-1F            2.1.1     Features of the Freeware Disc.............    2-2F            2.1.2     Guidelines for Software...................    2-2F            2.1.3     Submission of Freeware....................    2-3F            2.2   Automatic Foreign Commands from DCL (Paths)...    2-3F            2.3   DCL Commands - Changes and Enhancements.......    2-3F            2.4   Sort/Merge Utility (SORT/MERGE)...............    2-6F            2.5   DCL Commands for TCP/IP Users.................    2-7F            2.6   Specifying User Addresses in Mail.............    2-7  "      3  System Management Features  8            3.1   OpenVMS Management Station Bundled withF                  OpenVMS.......................................    3-2<            3.1.1     What Can You Do with OpenVMS ManagementF                      Station?..................................    3-4;            3.1.2     What Account Management Operations Are F                      Supported?................................    3-58            3.1.3     Where Is OpenVMS Management StationF                      Documented?...............................    3-5F            3.2   Volume Shadowing New Features.................    3-69            3.2.1     Support for Geometry-Based Shadowing F                      Device Recognition........................    3-69            3.2.2     Increased Limits on Numbers of Disks F                      Allowed in Shadow Sets....................    3-6F            3.2.2.1     Configuration Guidelines................    3-7  F                                                                      v                   9               3.2.3     StorageWorks RAID Array Subsystem I                         Support...................................    3-8 I               3.3   VMScluster Systems New Features...............    3-9 :               3.3.1     Support for SCSI Interconnect in aI                         VMScluster System.........................    3-9 <               3.3.2     Support for Multiple-Site VMSclusterI                         Systems...................................   3-11 I               3.3.3     OpenVMS Cluster Client Software...........   3-11 >               3.3.4     DECnet Software No Longer Required forI                         VMScluster Software.......................   3-11 I               3.3.5     Support for TMSCP Served SCSI Tapes.......   3-12 :               3.3.5.1     No TMSCP Server Support for SCSII                           Retension Command.......................   3-13 I               3.3.6     DECamds Enhancements......................   3-13 >               3.3.7     Enhanced Support for HSJ, HSC, and HSDI                         Series Controller Failover................   3-13 A               3.3.8     Warranted and Migration VMScluster System I                         Configurations............................   3-13 7               3.4   Local Area Network (LAN) Management I                     Enhancements..................................   3-14 @               3.5   Booting VMScluster Satellite Nodes Using theI                     New LANCP Utility ............................   3-15 I               3.5.1     Overview..................................   3-15 I               3.5.2     Using LANACP to Boot Satellites...........   3-16 I               3.5.2.1     New Installations.......................   3-16 I               3.5.2.2     Existing Installations..................   3-17 I               3.6   AUTOGEN Changes...............................   3-21 :               3.6.1     Changes to Computation of SYSMWCNTI                         Parameter.................................   3-21 I               3.6.2     Preventing Autoconfigure..................   3-21 I               3.6.3     Suppression of Informational Messages.....   3-21 <               3.6.4     Preventing AUTOGEN from Running As aI                         Spawned Subprocess........................   3-22 I               3.6.5     Overriding Parameters Related to DECnet...   3-22 I               3.7   New and Changed System Parameters.............   3-22 I               3.8   Backup Manager................................   3-24 I               3.9   BACKUP Changes................................   3-24 I               3.9.1     New Qualifier, /[NO]ALIAS.................   3-25 <               3.9.2     Increased Number of Directory LevelsI                         Supported.................................   3-25 I               3.10  Full Name Support.............................   3-25 I               3.10.1    Use of Full Names with SYSMAN.............   3-25       
         vi                   ?               3.11  Two Proxy Authorization Files, NETPROXY.DAT I                     and NET$PROXY.DAT.............................   3-26 I               3.11.1    Creation of Proxy Authorization Files.....   3-26 I               3.11.2    Proxy Modifications.......................   3-27 I               3.12  Security Server Process.......................   3-27 I               3.13  New LAT System Management Features............   3-28 >               3.14  New /NO_SHARE Qualifier for LICENSE MODIFYI                     Command.......................................   3-28 I               3.15  Choosing Languages and Date/Time Formats......   3-29 :               3.16  Operator Communication Manager (OPCOM)I                     Changes.......................................   3-30 I               3.16.1    Enabling Selected Operator Classes........   3-30 I               3.16.2    OPC$V_OPR_* Replaces OPR$V_*..............   3-30 @               3.16.3    Using OPC$OPA0_ENABLE to Override ValuesI                         for Workstations..........................   3-30 I               3.16.4    Using New Field Names.....................   3-31 I               3.17  Invalid Symbiont Message Codes................   3-31 I               3.17.1    Informational Invalid Symbiont Messages...   3-31 @               3.17.2    Messages That Cause the Queue Manager toI                         Abort the Symbiont........................   3-32 I               3.18  Erasing Old Home Blocks.......................   3-33 I               3.19  Additional SHUTDOWN.COM Logicals..............   3-34 @               3.20  Installing or Upgrading from a Running AlphaI                     System........................................   3-34 I               3.21  OpenVMS Support for TCP/IP Networking.........   3-35 I               3.22  Dump File Off the System Disk.................   3-35 I               3.23  DECamds.......................................   3-35 I               3.24  Inclusion of Selected Layered Products........   3-36            4  ProgrammingFeatures  I               4.1   DECnet/OSI Full Name Support..................    4-1 I               4.1.1     DECnet/OSI Full Name Support Routines.....    4-2 I               4.2   LAN Programming Features......................    4-2 I               4.2.1     New Devices and Drivers...................    4-2 I               4.2.2     New LAN Device Names and Devices..........    4-3 I               4.2.3     New Controller Characteristics............    4-3 :               4.2.4     New Procedures for Configuring ISAI                         Devices...................................    4-4 7               4.2.4.1     OpenVMS LAN Devices Requiring I                           Configuration...........................    4-6 I               4.2.4.1.1    DE202 Ethernet.........................    4-6 I               4.2.4.1.2    DW110 Token Ring.......................    4-7     I                                                                       vii                    I               4.3   LAT Programming Features......................    4-8 I               4.4   System Services Changes and Enhancements......    4-8 I               4.4.1     Intrusion Database System Services........    4-8 I               4.4.2     Proxy Database System Services............    4-9 9               4.4.3     Cluster Event Notification System I                         Services..................................   4-10 I               4.4.4     Persona System Services...................   4-10 I               4.4.4.1     $PERSONA_ASSUME.........................   4-11 I               4.4.4.2     $PERSONA_CREATE.........................   4-13 I               4.4.4.3     $PERSONA_DELETE.........................   4-15 I               4.5   OpenVMS Alpha Support for SCSI-2 Devices......   4-16 I               4.6   C++ RTL Object Library........................   4-17 I               4.7   New Linker Option RMS_RELATED_CONTEXT=........   4-17   ,         5  DEC C XPG4 Localization Utilities  I               5.1   GENCAT........................................    5-2 I               5.1.1     Format....................................    5-2 I               5.1.1.1     Parameters..............................    5-2 I               5.1.1.2     Qualifiers..............................    5-2 I               5.1.2     Description...............................    5-2 I               5.1.3     Errors....................................    5-6 I               5.1.4     Examples..................................    5-6 I               5.2   ICONV COMPILE.................................    5-8 I               5.2.1     Format....................................    5-8 I               5.2.1.1     Parameters..............................    5-8 I               5.2.1.2     Qualifier...............................    5-9 I               5.2.2     Description...............................    5-9 I               5.2.3     Errors....................................   5-14 I               5.2.4     Example...................................   5-15 I               5.3   ICONV CONVERT.................................   5-15 I               5.3.1     Format....................................   5-15 I               5.3.1.1     Parameters..............................   5-15 I               5.3.1.2     Qualifiers..............................   5-15 I               5.3.2     Description...............................   5-16 I               5.3.3     Example...................................   5-16 I               5.4   LOCALE COMPILE................................   5-17 I               5.4.1     Format....................................   5-17 I               5.4.1.1     Parameter...............................   5-17 I               5.4.1.2     Qualifiers..............................   5-17iI               5.4.2     Description...............................   5-19aI               5.4.3     Errors....................................   5-19 I               5.4.4     Example...................................   5-20              viii                   I               5.5   LOCALE LOAD...................................   5-20qI               5.5.1     Format....................................   5-20 I               5.5.1.1     Parameter...............................   5-20_I               5.5.1.2     Qualifiers..............................   5-21pI               5.5.2     Description...............................   5-21sI               5.6   LOCALE UNLOAD.................................   5-21nI               5.6.1     Format....................................   5-21oI               5.6.1.1     Parameter...............................   5-22sI               5.6.1.2     Qualifiers..............................   5-22 I               5.6.2     Description...............................   5-22oI               5.7   LOCALE SHOW CHARACTER_DEFINITIONS.............   5-22rI               5.7.1     Format....................................   5-22oI               5.7.1.1     Parameters..............................   5-22 I               5.7.1.2     Qualifiers..............................   5-23sI               5.7.2     Description...............................   5-23nI               5.7.3     Example...................................   5-23rI               5.8   LOCALE SHOW CURRENT...........................   5-23 I               5.8.1     Format....................................   5-24 I               5.8.1.1     Parameters..............................   5-24 I               5.8.1.2     Qualifiers..............................   5-24AI               5.8.2     Description...............................   5-24rI               5.8.3     Example...................................   5-25TI               5.8.4     Errors....................................   5-26 I               5.9   LOCALE SHOW PUBLIC............................   5-26dI               5.9.1     Format....................................   5-26 I               5.9.1.1     Parameters..............................   5-26 I               5.9.1.2     Qualifiers..............................   5-26 I               5.9.2     Description...............................   5-26aI               5.9.3     Example...................................   5-26tI               5.10  LOCALE SHOW VALUE.............................   5-27 I               5.10.1    Format....................................   5-27rI               5.10.1.1    Parameter...............................   5-27 I               5.10.1.2    Qualifiers..............................   5-31sI               5.10.2    Errors....................................   5-31iI               5.10.3    Description...............................   5-31 I               5.10.4    Examples..................................   5-32 I               5.11  Locale File Format............................   5-33 I               5.11.1    Locale Categories.........................   5-33pI               5.11.1.1    Overriding Defaults.....................   5-33 I               5.11.1.2    Category Source Definitions.............   5-34l          I                                                                        ixo .                 I               5.11.2    The LC_COLLATE Category...................   5-35 I               5.11.2.1    The collating-element Statement.........   5-36uI               5.11.2.2    The collating-symbol Statement..........   5-37oI               5.11.2.3    The order_start Statement...............   5-37nI               5.11.3    The LC_CTYPE Category.....................   5-41rI               5.11.4    The LC_MESSAGES Category..................   5-47eI               5.11.5    The LC_MONETARY Category..................   5-48mI               5.11.5.1    LC_MONETARY Keywords....................   5-49mI               5.11.5.2    Monetary Format Variations..............   5-55:I               5.11.6    The LC_NUMERIC Category...................   5-57OI               5.11.7    The LC_TIME Category......................   5-59MI               5.11.7.1    Keywords................................   5-59 I               5.11.7.2    Field Descriptors.......................   5-64 I               5.11.7.3    Sample Locale Definition................   5-68 I               5.12  Character Set Description (Charmap) File .....   5-70 I               5.12.1    Portable Character Set....................   5-70nI               5.12.2    Components of a Charmap File..............   5-73   ;         6  Local Area Network (LAN) Management EnhancementsN  I               6.1   The LANCP Utility.............................    6-5 I               6.1.1     Invoking and Exiting the LANCP Utility....    6-6iI               6.1.2     LAN Databases.............................    6-7 I               6.1.3     LAN Device Management.....................    6-8 I               6.1.3.1     Setting Device Parameters...............    6-9 I               6.1.3.2     Displaying Device Parameters............   6-213I               6.1.3.3     Displaying Device Configuration.........   6-27 I               6.1.3.4     Firmware Updates........................   6-27_I               6.1.4     LANACP Device Database Management.........   6-28 >               6.1.4.1     Entering Devices into the LAN DeviceI                           Databases...............................   6-29 >               6.1.4.2     Displaying Devices in the LAN DeviceI                           Databases...............................   6-34.>               6.1.4.3     Deleting Devices from the LAN DeviceI                           Databases...............................   6-35.I               6.1.4.4     Enabling MOP Downline Load Service......   6-36.I               6.1.4.5     Disabling MOP Downline Load Service.....   6-36 I               6.1.5     LANACP Node Database Management...........   6-362:               6.1.5.1     Entering Nodes into the LAN NodeI                           Databases...............................   6-37.<               6.1.5.2     Displaying Devices in the LAN NodeI                           Databases...............................   6-421      	         xm    t              :               6.1.5.3     Deleting Nodes from the LAN NodeI                           Databases...............................   6-43t8               6.1.6     LANACP MOP Downline Load ServiceI                         Management................................   6-43 <               6.1.6.1     Displaying the Status and CountersI                           Data....................................   6-44 I               6.1.6.2     Clearing the Counters Data..............   6-44 A               6.1.6.3     Displaying the Status and Counters Data I                           for Individual Nodes....................   6-44DI               6.1.6.4     OPCOM Messages..........................   6-46eI               6.1.6.5     Load Trace Facility.....................   6-47tI               6.1.7     LANCP MOP Console Carrier.................   6-48eI               6.1.8     LANCP MOP Trigger Boot....................   6-50 I               6.1.9     LANCP Miscellaneous Functions.............   6-52gI               6.2   The LANACP LAN Server Process.................   6-52.I               6.2.1     Running the LANACP Process................   6-54aI               6.2.2     Stopping the LANACP LAN Server Process....   6-54rI               6.3   LAN MOP Downline Load Services................   6-54.I               6.3.1     Coexistence with DECnet MOP...............   6-54 I               6.3.2     Migrating from DECnet MOP to LAN MOP......   6-55 <               6.3.3     Using CLUSTER_CONFIG_LAN.COM and LANI                         MOP.......................................   6-56rI               6.3.3.1     Sample Satellite Load...................   6-57 I               6.3.3.2     Cross-Architecture Booting..............   6-58   4         7  SCSI as a VMScluster Storage Interconnect  I               7.1   Conventions Used in This Chapter..............    7-21I               7.1.1     SCSI ANSI Standard........................    7-21I               7.1.2     Symbols Used in Figures...................    7-2 I               7.2   Accessing SCSI Storage........................    7-2 =               7.2.1     Single-Host SCSI Access in VMScluster I                         Systems...................................    7-3 ?               7.2.2     Multiple-Host SCSI Access in VMScluster I                         Systems...................................    7-3 ;               7.3   Configuration Requirements and Hardware I                     Support.......................................    7-3 I               7.3.1     Configuration Requirements................    7-3 I               7.3.2     Hardware Support..........................    7-5 I               7.4   SCSI Interconnect Concepts....................    7-7 I               7.4.1     Number of Devices.........................    7-8 I               7.4.2     Performance...............................    7-8 I               7.4.3     Distance..................................    7-9     I                                                                        xiv i  A              I               7.4.4     Cabling and Termination...................   7-11nI               7.5   SCSI VMScluster Hardware Configurations.......   7-12uI               7.5.1     Systems Using Add-On SCSI Adapters........   7-12.>               7.5.1.1     Building a Basic System Using Add-OnI                           SCSI Adapters...........................   7-13r9               7.5.1.2     Building a System That Allows a.;                           Server to Be Removed (Using DWZZAAI                           Converters).............................   7-14 B               7.5.1.3     Building a System That Allows AdditionalA                           Features and Performance Using an HSZ40 I                           Controller..............................   7-15 @               7.5.1.4     Building a System with More EnclosuresI                           or Greater Separation...................   7-15 I               7.5.1.5     Planning for the Future.................   7-16i=               7.5.2     Building a System Using Internal SCSI.I                         Adapters..................................   7-16uI               7.6   Installation..................................   7-17.3               7.6.1     Step 1: Meet SCSI GroundingeI                         Requirements..............................   7-18eI               7.6.2     Step 2: Configure SCSI Node IDs...........   7-18eA               7.6.2.1     Configuring Device IDs on Multiple-HostnI                           SCSI Buses..............................   7-19i?               7.6.2.2     Configuring Device IDs on Single-Host.I                           SCSI Buses..............................   7-19.8               7.6.3     Step 3: Power Up and Verify SCSII                         Devices...................................   7-20 9               7.6.4     Step 4: Show and Set SCSI Console I                         Parameters................................   7-23 =               7.6.5     Step 5: Install the OpenVMS Operating3I                         System....................................   7-263I               7.6.6     Step 6: Configure Additional Systems......   7-273I               7.7   Supplementary Information.....................   7-273:               7.7.1     Running the CLUSTER_CONFIG CommandI                         Procedure.................................   7-27.<               7.7.2     Errors Reports and OPCOM Messages inI                         Multiple-Host SCSI Environments...........   7-30sI               7.7.2.1     SCSI Bus Resets.........................   7-31RI               7.7.2.2     SCSI Timeouts...........................   7-31.I               7.7.2.3     Mount Verify............................   7-32.I               7.7.2.4     Shadow Volume Processing................   7-33.B               7.7.2.5     Expected OPCOM Messages in Multiple-HostI                           SCSI....................................   7-33dI               7.7.2.6     Error-Log Basics........................   7-34              xii  e  p              <               7.7.2.7     Error-Log Entries in Multiple-HostI                           SCSI....................................   7-35sI               7.7.3     Restrictions and Known Problems...........   7-36vI               7.7.4     Troubleshooting...........................   7-38sI               7.7.4.1     Termination Problems....................   7-38a@               7.7.4.2     Booting or Mounting Failures Caused byI                           Incorrect Configurations................   7-38.9               7.7.4.2.1    Bugchecks During the Bootstrap I                            Process................................   7-38.I               7.7.4.2.2    Mount Failures.........................   7-41.I               7.7.4.3     Grounding...............................   7-42.I               7.7.4.4     Interconnect Lengths....................   7-42 I               7.7.5     SCSI Arbitration Considerations...........   7-42r=               7.7.5.1     Arbitration Issues in Multiple-Disk I                           Environments............................   7-43 =               7.7.5.2     Solutions for Resolving Arbitration I                           Problems................................   7-44 I               7.7.5.3     Arbitration and Bus Isolators...........   7-45 =               7.7.6     Removal and Insertion of SCSI Devices 6                         While the VMScluster System isI                         Operating.................................   7-46.8               7.7.6.1     Terminology for Describing HotI                           Plugging................................   7-46.I               7.7.6.2     Rules for Hot Plugging..................   7-47oB               7.7.6.3     Procedures for Ensuring That a Device orI                           Segment Is Inactive.....................   7-51oA               7.7.6.4     Procedure for Hot Plugging StorageWorksaI                           SBB Disks...............................   7-52.I               7.7.6.5     Procedure for Hot Plugging HSZ40s.......   7-52.9               7.7.6.6     Procedure for Hot Plugging Host.I                           Adapters................................   7-54.I               7.7.6.7     Procedure for Hot Plugging DWZZAs.......   7-55.@               7.7.7     OpenVMS Requirements for Devices Used onI                         Multiple-Host SCSI VMScluster Systems.....   7-57mI               7.7.8     Grounding Requirements....................   7-59O                    I                                                                      xiii. .  .              6         8  VMScluster Systems That Span Multiple Sites  I               8.1   What Is a Multiple-Site VMScluster System?....    8-1.I               8.1.1     ATM, DS3, and FDDI Intersite Links........    8-2.<               8.1.2     Benefits of Multiple-Site VMSclusterI                         Systems ..................................    8-3.I               8.1.3     General Configuration Guidelines..........    8-5.9               8.2   Using FDDI to Configure Multiple-Site I                     VMScluster Systems............................    8-5 A               8.3   Using WAN Services to Configure Multiple-Site I                     VMScluster Systems............................    8-6 I               8.3.1     The ATM Communications Service............    8-7 I               8.3.2     The DS3 Communications Service............    8-7 I               8.3.3     FDDI-to-WAN Bridges.......................    8-8 A               8.3.4     Guidelines for Configuring ATM and DS3 in I                         a VMScluster System.......................    8-8 I               8.3.4.1     Requirements............................    8-9 I               8.3.4.2     Recommendations.........................   8-10 I               8.3.5     Availability Considerations...............   8-13 I               8.3.6     Specifications............................   8-13 ?               8.4   Managing VMScluster Systems Across Multiple.I                     Sites.........................................   8-27.I               8.4.1     Methods and Tools.........................   8-29eI               8.4.2     Shadowing Data............................   8-29fI               8.4.3     Monitoring Performance....................   8-30t  &         A  New OpenVMS System Messages  
         Index.             Examples  ?               4-1       Using the isacfg Command at the ConsoletI                         Prompt....................................    4-6a  <               4-2       Using the SYS$MANAGER:ISA_CONFIG.DATI                         Entry.....................................    4-6.  ?               4-3       Using the isacfg Command at the Console I                         Prompt....................................    4-7   <               4-4       Using the SYS$MANAGER:ISA_CONFIG.DATI                         Entry.....................................    4-7   I               7-1       Adding a Node to a SCSI VMScluster........   7-29            xiv.                            Figures.  9               3-1       Sample OpenVMS Management Station.I                         Screen....................................    3-3.  ;               3-2       Managing User Accounts with OpenVMStI                         Management Station........................    3-4a  I               7-16      SCSI Bus Topology.........................   7-48f  I               7-17      Hot Plugging a Bus Isolator...............   7-49o  >               8-2       Multiple-Site VMScluster ConfigurationI                         with Remote Satellites ...................    8-5   I               8-3       ATM/SONET OC-3 Service....................    8-7E  I               8-4       DS3 Service...............................    8-8m           Tables  @               1-1       Summary of OpenVMS VAX and OpenVMS AlphaI                         Version 6.2 Software Features.............    1-1.  I               2-1       DCL Dictionary Command Updates............    2-3.  I               3-1       Number of Shadow Sets Supported...........    3-7.  I               3-2       SCSI VMScluster System Hardware...........   3-10.  I               3-3       The TMSCP_SERVE_ALL System Parameter......   3-12.  I               3-4       New and Changed System Parameters.........   3-23.  >               3-5       Informational Invalid Symbiont MessageI                         Type Definitions..........................   3-32.  I               3-6       Invalid Symbiont Message Definitions......   3-33.  I               4-1       Supported Communication Devices...........    4-2.  I               4-2       LAN Device Names and Devices..............    4-3.  2               4-3       Ethernet Controller DeviceI                         Characteristics...........................    4-41  I               4-4       ISA Configuring Concepts..................    4-5   I               4-5       Intrusion Database System Services........    4-8   I               4-6       Proxy Database System Services............    4-9   9               4-7       Cluster Event Notification System.I                         Services..................................   4-10.  <               4-8       OpenVMS Alpha Tagged Command QueuingI                         Support...................................   4-16t  I               5-1       Special Characters........................    5-5.  I               5-2       Codeset Declarations......................   5-10.  I               5-3       Locale Categories and Keywords............   5-27.  I                                                                        xv. .  .              I               5-4       LC_COLLATE Category Keywords..............   5-36   I               5-5       LC_CTYPE Category Keywords................   5-41   I               5-6       LC_MESSAGES Category Keywords.............   5-47   I               5-7       LC_MONETARY Category Keywords.............   5-49   I               5-8       Monetary Format Variations................   5-56   I               5-9       LC_NUMERIC Category Keywords..............   5-57   I               5-10      LC_TIME Category Keywords.................   5-59   I               5-11      LC_TIME Locale Field Descriptors..........   5-65   I               5-12      Portable Character Set....................   5-70c  I               6-1       LAN System Management Enhancements........    6-2C  I               6-2       Functions of the LANCP Utility............    6-5i  I               6-3       Invoking the LANCP Utility................    6-6a  I               6-4       LAN Devices...............................    6-9e  I               6-5       LANCP SET DEVICE Command Qualifiers.......   6-11e  >               6-6       Default Functional Address Mapping forI                         Token Ring Devices........................   6-20   I               6-7       LANCP SHOW DEVICE Command Qualifiers......   6-22i  I               6-8       LANCP DEVICE Command Qualifiers...........   6-30P  I               6-9       LANCP NODE Command Qualifiers.............   6-38i  I               6-10      LANCP CONNECT NODE Command Qualifiers.....   6-49.  I               6-11      LANCP TRIGGER NODE Command Qualifiers.....   6-51   I               6-12      The LANACP Utility........................   6-52.  8               7-1       Requirements for SCSI VMSclusterI                         Configurations............................    7-4.  >               7-2       Supported Hardware for SCSI VMSclusterI                         Systems...................................    7-6e  @               7-3       Maximum Data Transfer Rates in MegabytesI                         per Second................................    7-9s  I               7-4       Maximum SCSI Interconnect Distances.......   7-10.  I               7-5       Internal SCSI Cable Lengths...............   7-17e  >               7-6       Steps for Installing a SCSI VMSclusterI                         System....................................   7-18   I               7-7       SCSI Environment Parameters...............   7-23.  I               7-8       Steps for Installing Additional Nodes.....   7-27   I               7-9       Steps for Ensuring Proper Grounding.......   7-59.  I               8-1       DS3 Protocol Options......................   8-10   @               8-2       Bellcore and VMScluster Requirements andI                         Goals Terminology.........................   8-154           xvi  .  .              :               8-3       VMScluster DS3 and SONET OC3 ErrorI                         Performance Requirements..................   8-16                                                                                       I                                                                      xviio l  a                        I         _________________________________________________________________   I                                                                   Preface6               Intended AudienceA  I               This manual is intended for general users, system managers,nC               and programmers who use the OpenVMS operating system.   I               This document contains descriptions of the new features forOH               Version 6.2 of the OpenVMS VAX and OpenVMS Alpha operatingI               systems. For information about how some of the new features D               might affect your system, read the OpenVMS Version 6.2G               Release Notes before you install, upgrade, or use Version.               6.2.           Document Structure  2               This manual is organized as follows:  H               o  Chapter 1 contains a summary of the new OpenVMS Version'                  6.2 software features.V  H               o  Chapter 2 describes new features of interest to generalG                  users of the OpenVMS VAX and OpenVMS Alpha Version 6.2a#                  operating systems.   H               o  Chapter 3 describes new features that are applicable to8                  the tasks performed by system managers.  >               o  Chapter 4 describes new features that support#                  programming tasks.   D               o  Chapter 5 describes the new DEC C XPG4 localization                  utilities.   H               o  Chapter 6 describes local area network (LAN) management                  enhancements.  I                                                                        xv. .  .              G               o  Chapter 7 describes how VMScluster systems support the.E                  Small Computer Systems Interface (SCSI) as a storage.                  interconnect.  =               o  Chapter 8 discusses multiple-site VMScluster                    configurations.  F               o  Appendix A describes new or changed messages from the'                  Help Message database.            Related Documents   G               Refer to the following documents for detailed information C               about the software features described in this manual. F               For more information about how to order these documents,G               see the Overview of OpenVMS Documentation or contact your.%               Digital representative.   D               o  DEC C Run-Time Library Reference Manual for OpenVMS                  Systems  %               o  DECamds User's Guide   5               o  DECnet for OpenVMS Networking Manual   -               o  DECnet/OSI DECdns Management   9               o  Guidelines for VMScluster ConfigurationsZ  C               o  OpenVMS Alpha Version 6.2 Upgrade and Installation                   Manual.  '               o  OpenVMS DCL Dictionaryi  1               o  OpenVMS Guide to System Securityn  4               o  OpenVMS I/O User's Reference Manual  .               o  OpenVMS Linker Utility Manual  F               o  OpenVMS Management Station Overview and Release Notes  2               o  OpenVMS RTL Library (LIB$) Manual  E               o  OpenVMS System Management Utilities Reference Manual7  0               o  OpenVMS System Manager's Manual  B               o  OpenVMS System Messages: Companion Guide for Help                  Message Users  9               o  OpenVMS System Services Reference Manual7           xvi     .              &               o  OpenVMS User's Manual  H               o  OpenVMS VAX Version 6.2 Upgrade and Installation Manual  2               o  OpenVMS Version 6.2 Release Notes  5               o  TCP/IP Networking on OpenVMS Systemsu  /               o  VMScluster Systems for OpenVMS.           Conventions.  C               The name of the OpenVMS AXP operating system has beeneE               changed to OpenVMS Alpha. Any references to OpenVMS AXP.@               or AXP are synonymous with OpenVMS Alpha or Alpha.  H               The following conventions are used to identify information:               specific to OpenVMS Alpha or to OpenVMS VAX:  D               In this manual, every use of DECwindows and DECwindowsD               Motif refers to DECwindows Motif for OpenVMS software.  E               The following conventions are also used in this manual:2  G               Ctrl/x           A sequence such as Ctrl/x indicates that2F                                you must hold down the key labeled CtrlH                                while you press another key or a pointing-                                device button..  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.)  <                . . .           Horizontal ellipsis points inE                                examples indicate one of the following.-                                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                                                                      xvii                      D               .                Vertical ellipsis points indicate theD               .                omission of items from a code exampleG               .                or command format; the items are omitted D                                because they are not important to the5                                topic being discussed.   >               ( )              In command format descriptions,G                                parentheses indicate that, if you choose I                                more than one option, you must enclose the 6                                choices in parentheses.  G               [ ]              In command format descriptions, brackets.B                                indicate optional elements. You canG                                choose one, none, or all of the options..F                                (Brackets are not optional, however, inC                                the syntax of a directory name in an.C                                OpenVMS file specification or in the.E                                syntax of a substring specification in 8                                an assignment statement.)  E               { }              In command format descriptions, braces.I                                indicate a required choice of options; you E                                must choose one of the options listed.   H               boldface text    Boldface text represents the introductionH                                of a new term or the name of an argument,9                                an attribute, or a reason.7  F                                Boldface text is also used to show userB                                input in Bookreader versions of the&                                manual.  >               italic text      Italic text indicates important>                                information, complete titles ofG                                manuals, or variables. Variables include @                                information that varies in systemC                                messages (Internal error number), in E                                command lines (/PRODUCER=name), and in H                                command parameters in text (where device-D                                name contains up to five alphanumeric+                                characters).   F               UPPERCASE TEXT   Uppercase text indicates a command, theH                                name of a routine, the name of a file, orG                                the abbreviation for a system privilege.   
         xviiit e  t                D               struct           Monospace type in text identifies theI                                following C programming language elements:-C                                keywords, the names of independently E                                compiled external functions and files, B                                syntax summaries, and references toE                                variables or identifiers introduced in *                                an example.  G               -                A hyphen in code examples indicates thattF                                additional arguments to the request areA                                provided on the line that follows.l  D               numbers          All numbers in text are assumed to beI                                decimal unless otherwise noted. NondecimalmH                                radixes-binary, octal, or hexadecimal-are4                                explicitly indicated.                                                        I                                                                       xix. 8                       I                                                                         1.I         _________________________________________________________________h  I                                       Summary of Version 6.2 New Featuresw    G               This chapter contains Table 1-1, which summarizes the newiD               software features supported by OpenVMS VAX and OpenVMS                Alpha Version 6.2.  F         Table 1-1 Summary of OpenVMS VAX and OpenVMS Alpha Version 6.2#                   Software Features   3                               General User Features   H         OpenVMS Freeware      Contains free software tools and utilitiesD         disc                  to aid software developers in creatingB                               applications, and managing and using.                               OpenVMS systems.  H         Automatic foreign     It is now possible to tell DCL to search aH         commands from DCL     specific set of directories for executableH                               images or command procedures and have themF                               automatically invoked without defining a)                               DCL symbol.g  G         DCL commands          Several DCL commands have been changed or.'                               enhanced.   A         Sort/Merge utility    The VALUE keyword is now available.e  F         DCL commands for      Several DCL commands have new qualifiersH         TCP/IP users          that make frequently used TCP/IP functions/                               easier to access.o  D         Specifying user       Permits user addresses to be specifiedF         addresses in Mail     in the Internet format without requiringD                               a transport name or quotes (unless theD                               address contains reserved characters).  I                                                  (continued on next page)S  I                                   Summary of Version 6.2 New Features 1-1. .  .      +         Summary of Version 6.2 New Featuresa      B         Table 1-1 (Cont.) Summary of OpenVMS VAX and OpenVMS Alpha7                           Version 6.2 Software Features   8                               System Management Features  C         OpenVMS Management    This powerful Microsoft Windows based.I         Station               management tool is now bundled with OpenVMS.&                               systems.  3         Volume Shadowing      New features include:   E                               o  Support for geometry-based shadowing 3                                  device recognition   E                               o  Increased limits on numbers of disks.7                                  allowed in shadow setsd  B                               o  StorageWorks RAID Array subsystem(                                  support  E         VMScluster systems    Includes support for SCSI interconnect, F                               multiple-site clusters, and TMSCP served)                               SCSI tapes..  B         Local area network    Two new LAN utilities perform systemI         (LAN) management      management tasks related to LAN operations.n         enhancements  F         Booting VMScluster    The new LANCP facility allows VMSclusterH         satellite nodes       systems to boot satellites without the useI                               of DECnet and provides several features not @                               available with DECnet MOP booting.  @         AUTOGEN               Changes to computation of SYSMWCNTE                               parameter, suppression of informational I                               messages, and overriding parameters related (                               to DECnet.  I                                                  (continued on next page)             /         1-2 Summary of Version 6.2 New Features4           I                                       Summary of Version 6.2 New Features       B         Table 1-1 (Cont.) Summary of OpenVMS VAX and OpenVMS Alpha7                           Version 6.2 Software Features.  8                               System Management Features  -         System parameters     New parameters:   -                               o  DR_UNIT_BASE.  D                               o  RMTDBG_SCRATCH_PAGES (Alpha systems&                                  only)  0                               o  TMSCP_SERVE_ALL  <                               o  VCC_PTES (VAX systems only)  1                               Changed parameters:   A                               o  LGI_BRK_LIM, minimum value now 1n  6                               o  SHADOWING, new values  I         Backup Manager        Provides a screen-oriented interface to the >                               OpenVMS Backup utility (BACKUP).  G         OpenVMS BACKUP        The new /[NO]ALIAS qualifier allows users H                               more control over how alias (synonym) fileI                               entries are processed by the OpenVMS Backup &                               utility.  D                               BACKUP now supports up to 32 directory%                               levels.3  F         Full names            Naming conventions for DECnet node namesC                               correspond to the two types of DECnetr,                               functionality.  B         Two proxy             OpenVMS Version 6.2 offers two proxyE         authorization files   authorization files, NET$PROXY.DAT (thetF                               primary proxy database) and NETPROXY.DATD                               (for use by DECnet for OpenVMS and for6                               backward compatibility).  H         Security Server       Creates and manages the system's intrusionG         process               database, and maintains the network proxy ,                               database file.  I                                                  (continued on next page).  I                                   Summary of Version 6.2 New Features 1-3            +         Summary of Version 6.2 New Features.      B         Table 1-1 (Cont.) Summary of OpenVMS VAX and OpenVMS Alpha7                           Version 6.2 Software Featuresn  8                               System Management Features  A         LAT                   New features have been added to the C                               SET HOST/LAT command, the LAT Control >                               Program (LATCP) utility, and the6                               programming environment.  F         LICENSE MODIFY        The new /[NO]NO_SHARE qualifier lets youI         command               add the NO_SHARE option to a PAK registereda:                               in a license database (LDB).  E         Choosing languages    System managers can select the time and H         and date/time         date formats for many SHOW commands from aI         formats               predefined list or define new time and date_&                               formats.  ?         OPCOM                 Changes include enabling selected E                               operator classes, overriding values fore@                               workstations, and new field names.  H         Invalid symbiont      The invalid symbiont message errors loggedF         message codes         to the operator console and operator logB                               file now contain integer values thatC                               identify why the symbiont message was '                               rejected.S  B         Erasing old home      The new /HOMEBLOCKS qualifier on theD         blocks                ANALYZE/DISK_STRUCTURE command enables;                               you to erase old home blocks.   G         Determining volume    You can now find out whether volumes that C         rebuild status        are mounted need rebuilding using thesB                               SHOW DEVICES/REBUILD_STATUS command.  B         SHUTDOWN.COM          Two new logicals in the SHUTDOWN.COMH         logicals              command procedure allow system managers toG                               determine the time when DECnet and queues ,                               are shut down.  G         Installing or         Beginning with OpenVMS Alpha Version 6.2,CG         upgrading from a      you can install or upgrade from a runningiE         running Alpha system  OpenVMS Alpha system to a target system #                               disk.e  I                                                  (continued on next page)   /         1-4 Summary of Version 6.2 New Featuresr d  r      I                                       Summary of Version 6.2 New Features       B         Table 1-1 (Cont.) Summary of OpenVMS VAX and OpenVMS Alpha7                           Version 6.2 Software Features   8                               System Management Features    A         OpenVMS TCP/IP        New OpenVMS manual describes TCP/IPsF         support               networking support, including DCL TCP/IP'                               commands.m  I         Dump file off the     On some VAX configurations, the system dump G         system disk (VAX      file can be placed on a device other than .         systems only)         the system disk.  D         DECamds               Console now supported on OpenVMS AlphaC                               systems. In addition, DECamds now has E                               the ability to adjust VMScluster quorum H                               values and supports some new customization&                               options.  E         Inclusion of          The OpenVMS CD-ROM distribution kit hasAD         selected layered      been expanded to include many softwareC         products on           products that previously required theSC         distribution kit      purchase of additional CD-ROMs. Also,eG                               all OpenVMS online documentation will now F                               be included on one OpenVMS documentation%                               CD-ROM.a  I         _________________________________________________________________7I         ______________________Programming_Features_______________________e  B         DECnet/OSI full       Several run-time routines and systemI         names                 services are provided to support DECnet/OSI )                               full names.   G         LAN (Alpha systems    LAN programming features added to OpenVMSg8         only)                 Alpha Version 6.2 include:  8                               o  New devices and drivers  A                               o  New LAN device names and devicesn  ?                               o  New controller characteristicsM  C                               o  New procedures for configuring ISAa(                                  devices  I                                                  (continued on next page)   I                                   Summary of Version 6.2 New Features 1-5c    n      +         Summary of Version 6.2 New Featuresi      J                 Table 1-1 (Cont.) Summary of OpenVMS VAX and OpenVMS Alpha7                           Version 6.2 Software Features     *                       Programming Features  H         LAT                   $QIO has a new LAT function modifier and a9                               new LAT SENSEMODE argument.   A         System services       Intrusion database system services:h  2                               o  $DELETE_INTRUSION  0                               o  $SCAN_INTRUSION  0                               o  $SHOW_INTRUSION  =                               Proxy database system services:   +                               o  $ADD_PROXYy  .                               o  $DELETE_PROXY  /                               o  $DISPLAY_PROXYr  .                               o  $VERIFY_PROXY  I                               Cluster event notification system services:   +                               o  $CLRCLUEVT   +                               o  $SETCLUEVT   +                               o  $TSTCLUEVTe  6                               Persona system services:  0                               o  $PERSONA_ASSUME  0                               o  $PERSONA_CREATE  0                               o  $PERSONA_DELETE  H         OpenVMS Alpha         On Alpha systems, OpenVMS now supports theH         programming support   tagged command queuing architecture of the.         for SCSI-2 devices    SCSI-2 standard.  A         C++ RTL object        Object modules are now available in 6         library               SYS$LIBRARY:STARLET.OLB.  I                                                  (continued on next page)   /         1-6 Summary of Version 6.2 New Features  t         I                                       Summary of Version 6.2 New Features       B         Table 1-1 (Cont.) Summary of OpenVMS VAX and OpenVMS Alpha7                           Version 6.2 Software Features   (                     Programming Features  4         Linker                The new linker option,G                               RMS_RELATED_CONTEXT=, enables or disablesiH                               RMS related name context processing within5                               the linker option file.n  8                        DEC C XPG4 Localization Utilities  I         Localization          OpenVMS Version 6.2 provides XPG4-compliantnF         utilities             utilities for managing localization dataH                               for international software applications or/                               layered products.   @                 Local Area Network (LAN) Management Enhancements  B         Two new LAN           You can perform the following systemI         utilities             management tasks related to LAN operations:   H                               o  Set LAN parameters to customize the LAN-                                  environment.   C                               o  Display LAN settings and counters.   H                               o  Provide Maintenance Operations ProtocolH                                  (MOP) downline load support for booting,                                  satellites.  I         _________________________________________________________________I;                   SCSI as a VMScluster Storage Interconnect   F         Storage interconnect  VMScluster systems now support the SmallD                               Computer Systems Interface (SCSI) as aD                               shared multihost storage interconnect.  I                                                  (continued on next page)P        I                                   Summary of Version 6.2 New Features 1-7w e  v      +         Summary of Version 6.2 New Featuresu      B         Table 1-1 (Cont.) Summary of OpenVMS VAX and OpenVMS Alpha7                           Version 6.2 Software Featureso  =                   VMScluster Systems That Span Multiple Sites   F         Multiple-site         VMScluster systems can have member nodesI         VMScluster            in geographically separate areas, using the E         configurations        new DS3 and ATM communications service.                                                                           /         1-8 Summary of Version 6.2 New Featuresn                         I                                                                         2 I         _________________________________________________________________r  I                                                     General User Featuresl    >               This chapter provides the following new featuresH               information for all users of the OpenVMS operating system:  ;               o  OpenVMS Freeware for VAX and Alpha systemsh  <               o  Automatic foreign commands from DCL (paths)  8               o  DCL commands - changes and enhancements  3               o  New keyword for Sort/Merge utility   .               o  DCL commands for TCP/IP users  2               o  Specifying user addresses in Mail  6         2.1 OpenVMS Freeware for VAX and Alpha Systems  C               OpenVMS Engineering is sponsoring an OpenVMS Freeware C               CD-ROM, which contains "public domain" and "freeware" E               software that runs on OpenVMS Version 6.0 or later. The_B               purpose of the OpenVMS Freeware CD-ROM is to provideA               OpenVMS customers with easy access to public domain D               software and free internal Digital software and tools.  D               The OpenVMS Freeware disc contains free software toolsG               and utilities to aid software developers in both creatingdI               applications and managing or using OpenVMS systems. Many of I               these tools are popular packages already in use, and others G               are internally developed Digital tools that our engineers E               are making available to OpenVMS customers. For example, G               this disc includes Bliss-32 for OpenVMS VAX, Bliss-32 forM<               OpenVMS Alpha, and Bliss-64 for OpenVMS Alpha.        I                                                 General User Features 2-1     c               General User Features 6         2.1 OpenVMS Freeware for VAX and Alpha Systems    +         2.1.1 Features of the Freeware Disce  @               The Freeware disc includes the following features:  G               o  An easy-to-use 4GL-based menu system for examining the '                  contents of the CD-ROMt  G               o  Files-11 format to make it readable on OpenVMS systemsn  H               o  Binaries, source code (except for the Bliss compilers),"                  and documentation  G               o  Some of the most popular free packages, plus new items )                  never before made publics  G                 ____ Disclaimer on Testing, Quality, and Licensing ____o  E                 The OpenVMS Freeware for VAX and Alpha Systems CD-ROMn?                 is provided "as is" without a warranty. Digital F                 imposes no restrictions on its distribution nor on theD                 redistribution of anything on it. Be aware, however,?                 that some of the packages on the disc may carryiB                 restrictions on their use, imposed by the originalA                 authors. Therefore, you should carefully read theo8                 documentation accompanying the products.  F                 ______________________________________________________  %         2.1.2 Guidelines for Software   D               The guidelines for the software to be contained on the*               OpenVMS Freeware CD-ROM are:  G               o  The software is unencumbered to the public. No licensefG                  fees shall be requested of or required by the customero                  for its use.   G               o  The software must run on OpenVMS Version 6.0 or later.   E               o  Digital does not issue a warranty for this software.a  I               o  Digital does not provide services for this software, fix D                  the software, or guarantee that it works correctly.  F               o  Customers are free to adapt the source files to their                  needs.   !         2-2 General User Featurest k         I                                                     General User FeaturessI                            2.1 OpenVMS Freeware for VAX and Alpha Systemsc    $         2.1.3 Submission of Freeware  I               Instructions for submission of software are included on thee               disc.   7         2.2 Automatic Foreign Commands from DCL (Paths)   G               In previous versions of the OpenVMS operating system, DCL G               symbols needed to be defined to implement user-defined or                foreign commands.i  C               With this release of the OpenVMS operating system, itiC               is now possible in many cases to tell DCL to search a B               specific set of directories for executable images orD               command procedures and have them automatically invoked,               without defining a DCL symbol.  B               For more information, see the OpenVMS User's Manual.  3         2.3 DCL Commands - Changes and Enhancements   H               Table 2-1 lists the new and updated DCL commands. Refer to5               the OpenVMS DCL Dictionary for details.m  I               Note that BOOT and LOGIN have been added as keywords to the G               /BEFORE and /SINCE qualifiers for many commands to select G               files dated prior to or since the last system boot or theT                user's last login.  6               Table 2-1 DCL Dictionary Command Updates  ?               Command               DCL Dictionary Modification   9               ANALYZE/IMAGE         Documentation updated   5               APPEND                /BEFORE (updated)M4                                     /SINCE (updated)  8               ASSIGN                /USER_MODE (updated)  5               COPY                  /BEFORE (updated)I4                                     /SINCE (updated)7                                     /TRUNCATE (updated) :                                     /WRITE_CHECK (updated)  8               CREATE/NAME_TABLE     /USER_MODE (updated)  I                                                  (continued on next page)   I                                                 General User Features 2-3C    e               General User Features 3         2.3 DCL Commands - Changes and Enhancements     >               Table 2-1 (Cont.) DCL Dictionary Command Updates  ?               Command               DCL Dictionary Modificationh  8               DEASSIGN              /USER_MODE (updated)  8               DEFINE                /USER_MODE (updated)  5               DELETE                /BEFORE (updated)r4                                     /SINCE (updated)  9               DIFFERENCES           /CHANGE_BAR (updated)y  5               DIRECTORY             /BEFORE (updated) 4                                     /SINCE (updated)1                                     /TIME (added)   5               EXCHANGE/NETWORK      /BEFORE (updated) 4                                     /SINCE (updated)  1               F$CONTEXT lexical     NEQ (updated)r  >               F$GETQUI lexical      INTERVENING_BLOCKS (added)<                                     INTERVENING_JOBS (added)  =               F$GETSYI lexical      ++CONSOLE_VERSION (added)m=                                     ++PALCODE_VERSION (added)r3                                     QUANTUM (added) :                                     USED_GBLPAGCNT (added):                                     USED_GBLPAGMAX (added):                                     CLUSTER_EVOTES (added)7                                     NODE_EVOTES (added) 8                                     REAL_CPUTYPE (added)  6               INITIALIZE            /DENSITY (updated)  5               PRINT                 /BEFORE (updated)m4                                     /SINCE (updated)  5               PURGE                 /BEFORE (updated) 4                                     /SINCE (updated)  ;               RECALL                Documentation (updated)   5               RENAME                /BEFORE (updated)c?                                     /INHERIT_SECURITY (updated)v4                                     /SINCE (updated)  9               RUN (process)         Documentation updatedn                 ++Alpha specific.d  I                                                  (continued on next page)   !         2-4 General User Featuresn n  t      I                                                     General User Features I                               2.3 DCL Commands - Changes and Enhancements     >               Table 2-1 (Cont.) DCL Dictionary Command Updates  ?               Command               DCL Dictionary Modification   5               SEARCH                /BEFORE (updated)n0                                     /KEY (added)6                                     /MATCH=XOR (added)6                                     /MATCH=EQV (added)4                                     /SINCE (updated)5                                     /WARNINGS (added)   E               SET AUDIT             /ENABLE=(AUDIT=ILLFORMED) (added)   5               SET DIRECTORY         /BEFORE (updated)q4                                     /SINCE (updated)  5               SET FILE              /BEFORE (updated)p4                                     /SINCE (updated)3                                     Example (added)   8               SET HOST/DTE          Baud rates (updated)  1               SET HOST/LAT          /DIAL (added) :                                     /[NO]EIGHT_BIT (added)2                                     /SPEED (added)  9               SET MAGTAPE           Documentation updatedV  5               SET SECURITY          /BEFORE (updated) 4                                     /SINCE (updated)  <               SET TERMINAL          /SECURE_SERVER (updated)  <               SET TIME              /CLUSTER (now supported)  9               SET VOLUME            Documentation updatedp  ;               SHOW DEVICES          /REBUILD_STATUS (added)   2               SHOW DEVICES/SERVED   /EXACT (added)6                                     /HIGHLIGHT (added)1                                     /PAGE (added)c3                                     /SEARCH (added)   1               SHOW PROCESS          /DUMP (added) 7                                     /INTERVAL (updated)   5               SHOW SECURITY         /BEFORE (updated) 4                                     /SINCE (updated)  I                                                  (continued on next page)i  I                                                 General User Features 2-5  h  p               General User Features 3         2.3 DCL Commands - Changes and Enhancementsm    >               Table 2-1 (Cont.) DCL Dictionary Command Updates  ?               Command               DCL Dictionary Modificationl  8               SHOW SYSTEM           /[NO]BATCH (updated)8                                     /[NO]HEADING (added)2                                     /IDENT (added)<                                     /[NO]INTERACTIVE (added):                                     /[NO]NETWORK (updated)6                                     /OWNER_UIC (added):                                     /[NO]PROCESS (updated)2                                     /STATE (added)=                                     /[NO]SUBPROCESS (updated) 4                                     Examples (added)  2               SHOW TERMINAL         /BRIEF (added)1                                     /FULL (added) 4                                     Examples (added)  8               SHOW USERS            /[NO]BATCH (updated)8                                     /[NO]HEADING (added)>                                     /[NO]INTERACTIVE (updated):                                     /[NO]NETWORK (updated)=                                     /[NO]SUBPROCESS (updated) 4                                     Examples (added)  9               SPAWN                 Documentation updated   9               STOP                  Documentation updated   5               SUBMIT                /BEFORE (updated)e4                                     /SINCE (updated)  5               TYPE                  /BEFORE (updated)t4                                     /SINCE (updated)3                                     /TAIL (updated)   +         2.4 Sort/Merge Utility (SORT/MERGE)t  H               The VALUE keyword is now available for use with the /FIELDD               qualifier in Sort/Merge specification files. The VALUEI               keyword allows you to define a constant field and assign it I               a value of any valid Sort/Merge data-type. You can use this G               constant field in /KEY, /DATA, and /CONDITION statements.P  !         2-6 General User Features  $  P      I                                                     General User Features I                                       2.4 Sort/Merge Utility (SORT/MERGE)     H               The following are sample formats for the /FIELD qualifier:  O               /FIELD=(NAME=field-name,POSITION:n,SIZE:n[,DIGITS:n][,data-type])s  L               /FIELD=(NAME=field-name,VALUE:n,SIZE:n[,DIGITS:n][,data-type])  D               If you specify VALUE:n, do not specify POSITION:n. TheC               VALUE field is a constant and is not part of an inputs               record.r  H               For more information about the Sort/Merge utility, see the$               OpenVMS User's Manual.  )         2.5 DCL Commands for TCP/IP Users   @               Several DCL commands have new qualifiers that makeC               frequently used TCP/IP functions easier to access and <               better integrated. Some of these commands are:                 o  COPY /FTP                 o  COPY /RCP                 o  DIRECTORY /FTPn  !               o  SET HOST /RLOGINl  !               o  SET HOST /TELNETa  !               o  SET HOST /TN3270   G               Note that in order for the new commands to work, you musttE               install a TCP/IP product that supports them. DEC TCP/IP B               Services for OpenVMS (UCX) Version 3.2 supports onlyF               the SET HOST /RLOGIN command; the other commands require               Version 3.3.  D               For more information, see TCP/IP Networking on OpenVMS               Systems.  -         2.6 Specifying User Addresses in Mails  F               When you use the Mail utility or callable Mail routines,G               you can now specify user addresses in the Internet formataD               without specifying the transport or quotes (unless the4               address contains reserved characters).  I                                                 General User Features 2-7m                    General User Featuress-         2.6 Specifying User Addresses in Mail     ;               For example, in previous versions of OpenVMS, B               SMTP%"user@node.org" was required to send mail to anB               Internet address. The string may now be specified as               user@node.org.  G               o  If the Internet transport on your machine is not SMTP,dE                  then the logical name MAIL$INTERNET_TRANSPORT may be :                  defined to select an alternate transport.  C               o  The user@node syntax can also be used to specify acD                  DECnet phase IV node name or a DECnet/OSI alias. In8                  this case, it is treated as node::user.                                                                  !         2-8 General User Features            I                                                     General User Features I                                     2.6 Specifying User Addresses in Mail     !               Note the following:e  E               o  This feature is available in character-cell mail andp!                  DECwindows mail.o  F               o  Although this change removes the requirement that youH                  include the transport and quotes when specifying a userH                  address, you must still include quotes if you choose to'                  specify the transport.s  E               o  You can specify the user@node.org format only from a                   local system.  B               For more information about the Mail utility, see theH               OpenVMS User's Manual. For more information about callable<               Mail, see the OpenVMS Utility Routines Manual.                                                          I                                                 General User Features 2-9    s  a                    I                                                                         3SI         _________________________________________________________________y  I                                                System Management Features     G               This chapter contains information about the following newkF               features, changes, and enhancements for system managers:  @               o  OpenVMS Management Station bundled with OpenVMS  .               o  Volume Shadowing new features  0               o  VMScluster systems new features  A               o  Local area network (LAN) management enhancementsd  G               o  Booting VMScluster satellite nodes using the new LANCP                   utility                  o  AUTOGEN changes  2               o  New and changed system parameters                 o  Backup Manageri  ,               o  New OpenVMS BACKUP features  "               o  Full name support  @               o  Two proxy authorization files, NETPROXY.DAT and                  NET$PROXY.DAT  (               o  Security Server process  3               o  New LAT system management features   C               o  New /NO_SHARE qualifier for LICENSE MODIFY command,  9               o  Choosing languages and date/time formatst  ?               o  Operator Communication Manager (OPCOM) changesn  /               o  Invalid symbiont message codess  (               o  Erasing old home blocks  1               o  Additional SHUTDOWN.COM logicals   D               o  Installing or upgrading from a running Alpha system  I                                            System Management Features 3-1            "         System Management Features      B               o  OpenVMS support for Transmission Control Protocol7                  /Internet Protocol (TCP/IP) networking   A               o  Dump file off the system disk (VAX systems only)                  o  DECamds  7               o  Inclusion of selected layered productsb  ;         3.1 OpenVMS Management Station Bundled with OpenVMSe  H               OpenVMS Management Station is a powerful Microsoft WindowsF               based management tool for system managers and others whoB               perform account management tasks on OpenVMS systems.F               OpenVMS Management Station provides a comprehensive userE               interface to OpenVMS account management across multiples               systems.  I               OpenVMS Management Station coexists with all of the currentb2               OpenVMS system management utilities.  B               Figure 3-1 shows a sample OpenVMS Management Station               screen.                                             &         3-2 System Management Features           I                                                System Management Features I                       3.1 OpenVMS Management Station Bundled with OpenVMS_    A               Figure 3-1 Sample OpenVMS Management Station Screen                                                   H               OpenVMS Management Station addresses the problem of havingA               to use multiple OpenVMS utilities to manage OpenVMS F               accounts. For example, creating an account traditionally.               consists of the following steps:  #               o  Adding a UAF entryo  ,               o  Granting rights identifiers  %               o  Creating a directorya  %               o  Creating disk quotasv  )               o  Granting network proxies   C               This operation requires you to use DCL, the Authorize @               utility, and the DISKQUOTA component of the SystemE               Management utility. OpenVMS Management Station provides I               an easy-to-use interface to this process so that you do note-               need to use multiple utilities.w  I                                            System Management Features 3-3            "         System Management Features;         3.1 OpenVMS Management Station Bundled with OpenVMSu    H               OpenVMS Management Station consists of two components. You               install:  G               o  The Microsoft Windows based client software on a PC tos2                  perform all management operations  G               o  The server component on all of the OpenVMS systems you                   want to managea  E               You do not interact directly with the server component.o  >         3.1.1 What Can You Do with OpenVMS Management Station?  C               OpenVMS Management Station allows you to organize the.D               systems you need to manage in ways that are meaningfulH               to you and your environment, and allows you to manage user(               accounts on those systems.  I               You can easily manage user accounts across multiple OpenVMS I               systems, depending on your needs. The systems might be some I               of the clusters in a network, all of the systems on a given E               floor of a building, a mix of clusters and nonclustered "               nodes, and so forth.  C               Figure 3-2 shows how a screen might look when you areo%               managing user accounts.f  G               Figure 3-2 Managing User Accounts with OpenVMS Management                            Station                                &         3-4 System Management Features           I                                                System Management Features I                       3.1 OpenVMS Management Station Bundled with OpenVMSp    >               You can use OpenVMS Management Station to manageE               OpenVMS user accounts in a convenient, easy manner. For D               example, when creating an account on multiple systems,E               OpenVMS Management Station can add a user authorization C               file (UAF) entry, grant rights identifiers, create an F               OpenVMS directory, set a disk quota, set up OpenVMS MailE               characteristics, and so forth, for each instance of them               account.  F               OpenVMS Management Station manages the following OpenVMS               resources:  3               o  SYSUAF.DAT user authorization file   0               o  RIGHTSLIST.DAT user rights file  '               o  Network proxy database   .               o  Account login-directory trees  )               o  User account disk quotasd  7               o  OpenVMS Mail VMSMAIL_PROFILE.DATA file   ?         3.1.2 What Account Management Operations Are Supported?   G               OpenVMS Management Station supports the following account $               management operations:  '               o  Creating user accounts   5               o  Modifying user accounts (any aspect)   '               o  Deleting user accountsC  '               o  Renaming user accounts   3               o  Displaying user account attributesl  =         3.1.3 Where Is OpenVMS Management Station Documented?   >               The features and functions of OpenVMS ManagementE               Station are completely described in extensive MicrosoftAE               Windows help files. The help files include step-by-step)1               instructions and numerous examples.S  G               The OpenVMS Management Station Overview and Release Notes I               document provides an overview of OpenVMS Management StationEB               and describes how to get started using the software.  I                                            System Management Features 3-5            "         System Management Features;         3.1 OpenVMS Management Station Bundled with OpenVMS     H               Information about installing OpenVMS Management Station onF               your Alpha or VAX computer and your PC is located in the                following manuals:  C               o  OpenVMS Alpha Version 6.2 Upgrade and Installation                   Manualu  H               o  OpenVMS VAX Version 6.2 Upgrade and Installation Manual  )         3.2 Volume Shadowing New Featuresn  E               Volume Shadowing for OpenVMS contains the following new                features:   H               o  Support for geometry-based shadowing device recognition  G               o  Increased limits on numbers of disks allowed in shadow                   setsU  :               o  StorageWorks RAID Array Subsystem support  D               In addition to these new features in Volume Shadowing,C               OpenVMS Alpha Version 6.2 and OpenVMS VAX Version 6.2 C               now support the HSJ40, HSJ30, HSD30, HSZ40, and HSD05 D               controllers. See the OpenVMS SPD for the complete list*               of controllers and firmware.  E         3.2.1 Support for Geometry-Based Shadowing Device RecognitionL  C               Formerly, Volume Shadowing checked device IDs and thedH               maximum logical block numbers (LBNs) on devices. With thisI               release, Volume Shadowing checks for geometries and maximum E               LBNs instead. This enables devices such as the RZ28 and F               the RZ28B to operate in the same shadow set. Even thoughH               their device IDs differ, their geometries and maximum LBNsE               will match when configured on like controllers (two HSJD(               controllers, for example).  I         3.2.2 Increased Limits on Numbers of Disks Allowed in Shadow Setsu  I               Table 3-1 shows the new limits for numbers of disks allowed                in shadow sets:_      &         3-6 System Management Features           I                                                System Management FeaturespI                                         3.2 Volume Shadowing New Features     7               Table 3-1 Number of Shadow Sets Supported                  Type of Shadow-               Set              Sets Supported   -               Single member    Unlimited sets   D               Multimember      Total of 400 disks in two- and three-3                                member sets, or botht  D               These limits apply per cluster. For example, 400 totalB               disks could be configured into 200 two-member shadowG               sets or into 133 three-member shadow sets per cluster. If G               single, two- and three-member shadow sets are all present E               on a single cluster, then a maximum of 400 disks may beEA               contained in the two- and three-member shadow sets.m  (         3.2.2.1 Configuration Guidelines  B               Increasing the number of shadow sets supported on anE               OpenVMS cluster also increases the risk that the systemAB               overhead required to perform shadowing functionalityD               will exceed customer expectations. Customers are urgedG               to use care in configuring clusters with large numbers of I               shadow sets. The Volume Shadowing for OpenVMS manual is theOF               best source for shadowing configuration information. TheF               following are areas where users of the shadowing product!               should use caution:d  .               o  Shadow copy/merge performance  C                  The purpose of the shadowing product is to enhance D                  storage availability. Copy and merge operations may/                  have an impact on performance.   E                  Shadow copy/merge operations require that the entire E                  disk be accessed. On very large devices that are notOE                  attached to controllers with shadowing assists, this F                  can take a long time. A shadow copy on a one-gigabyteF                  disk without copy assists will take about an hour. ItE                  will take longer if the copy operation competes with E                  heavy user I/O, is served over a slow Ethernet link,NG                  or both. A large number of shadow sets performing copy F                  /merge operations in parallel will compete for systemF                  resources. The system overhead involved in performingE                  shadow copy and merge may limit the number of shadowt;                  sets mounted on a given system or cluster.t  I                                            System Management Features 3-7i           "         System Management Features)         3.2 Volume Shadowing New Features     B               o  Satellite-initiated copy/merge is not recommended  H                  Cluster satellite nodes should set the system parameterD                  SHADOW_MAX_COPY to zero. This will prevent copy andC                  merge operations from occurring over the Ethernet. E                  This is especially important for slow Ethernet links F                  or for high Ethernet traffic. Satellite nodes doing aD                  large number of copies or merges will substantiallyH                  degrade performance of the satellite node, the EthernetH                  link, or both. Shadow copies should occur on nodes withG                  direct connections to shadow set members. This work isnF                  controlled by the system parameter SHADOW_MAX_COPY on#                  each cluster node.T                 o  Pool size  C                  Mounting large numbers of shadow sets will requireeH                  additional nonpaged pool. For a larger number of shadowG                  sets, the NPAGEDYN parameter may need to be increased. 2                  See the documentation on AUTOGEN.  2               o  Mount /CLUSTER only when required  H                  Mounting shadow sets only on cluster nodes that requireA                  them to be mounted will reduce cluster shadowing =                  overhead, especially on very large clusters.T  7         3.2.3 StorageWorks RAID Array Subsystem Support2  A               The StorageWorks RAID Array 210 subsystem (KZESC-AA B               or KZESC-BA EISA Backplane RAID controllers) and theE               StorageWorks PCI Backplane RAID controller (KZPSC-AA or.H               KZPSC-BA) have their own firmware implementations of RAID,I               levels 0, 1, and 5. You can use the firmware implementationoI               of RAID level 1 (shadowing) to create shadow sets using thecF               SCSI disks attached locally to a single RAID controller.  C               With OpenVMS Version 6.2, the SCSI disks connected to C               these controllers can also be included in shadow setsaD               created using host-based Volume Shadowing for OpenVMS.F               In previous releases, these disks were not accessible byE               Volume Shadowing. With host-based Volume Shadowing, nowaI               you can create a RAID1 shadow set containing two like disks E               or two like RAID arrays, each of which is attached to adD               separate RAID controller located within a cluster. YouD               also can create a RAID1 shadow set using one SCSI diskG               attached to the StorageWorks RAID controller and one SCSI   &         3-8 System Management Features t  I      I                                                System Management Features I                                         3.2 Volume Shadowing New Featuress    I               disk attached elsewhere in the cluster (as long as the disk *               geometries and sizes match).  D               See the StorageWorks RAID Array Subsystem User's GuideG               for more information on using Volume Shadowing with theseh               controllers.  +         3.3 VMScluster Systems New Features   D               In OpenVMS Version 6.2, VMScluster systems include the%               following new features:n  E               o  Support for SCSI interconnect in a VMScluster systeme  =               o  Support for multiple-site VMScluster systems   0               o  OpenVMS Cluster Client Software  B               o  DECnet software no longer required for VMScluster                  softwareM  4               o  Support for TMSCP served SCSI tapes  %               o  DECamds enhancements   I               o  Enhanced support for HSJ, HSC, and HSD series controller                   failover   I               o  Warranted and migration VMScluster system configurationsu  =               These features further enhance the performance, H               availability, and functionality of VMScluster systems. TheH               following sections describe these features in more detail.H               In addition, Section 3.3.8 charts the most recent pairingsI               information for supported VMScluster system configurations.   B         3.3.1 Support for SCSI Interconnect in a VMScluster System  I               You can use the SCSI interconnect as a storage interconnectlB               for multiple Alpha systems in a VMScluster system. AF               SCSI interconnect, also referred to as a SCSI bus, is anG               industry-standard interconnect that supports SCSI storage ;               devices, controllers, and support components.G  ?               VMScluster Software for OpenVMS Alpha Version 6.2 F               provides support for a limited set of multiple-host SCSIG               configurations. You can configure systems, SCSI adapters,oF               controllers and disk devices on multiple-host SCSI buses0               using the components in Table 3-2.  I                                            System Management Features 3-9O A  q      "         System Management Features+         3.3 VMScluster Systems New Featuresm    7               Table 3-2 SCSI VMScluster System Hardware                  Supported *               Component        Description  /               Alpha Systems:   AlphaServer 2100 /                                AlphaServer 2000 /                                AlphaServer 1000n.                                AlphaServer 4000                                AlphaStation 2500/                                AlphaStation 400 /                                AlphaStation 200o  I               SCSI Adapters:   The embedded SCSI adapter available in all ;                                the supported Alpha systems. >                                Optional add-on KZPAA adapters.  F               Controllers:     HSZ40 and all its supported disks. NoteC                                that DWZZA single-ended to fast-wide H                                differential converters are required when=                                configuring HSZ40 controllers.e  E               Disks:           You can directly connect the followingo=                                disks on a multihost SCSI bus:a#                                RZ28 $                                RZ28B#                                RZ26i$                                RZ26L$                                RZ29B  8               In a VMScluster system, you can configure:  >               o  Up to two systems to a multiple-host SCSI bus  F               o  A system to a maximum of two multiple-host SCSI buses  5               o  Any number of single-host SCSI busesF  A               Chapter 7 provides a complete discussion about SCSId4               configurations, setup, and management.          '         3-10 System Management Features            I                                                System Management FeaturesoI                                       3.3 VMScluster Systems New Featuresp    :         3.3.2 Support for Multiple-Site VMScluster Systems  @               Since OpenVMS Version 6.1, VMScluster systems haveD               supported DS3 technology, also called T3, as a clusterA               interconnect when used in conjunction with FDDI and >               appropriate bridging technology. Using DS3 as anC               interconnect, nodes in a VMScluster can be located inhI               multiple, geographically separate sites as far apart as 150tG               miles. With OpenVMS Version 6.2, this feature is enhanced (               to include ATM technology.  G               Chapter 8 provides a complete discussion of multiple-sitei               clusters.   -         3.3.3 OpenVMS Cluster Client Softwareu  C               OpenVMS Version 6.2 introduces a new license type for E               OpenVMS cluster software, called OpenVMS Cluster ClientnC               software. The new license provides a low-cost cluster <               client product for Alpha and VAX workstations.  @               The OpenVMS Cluster Client software provides fullyF               functional OpenVMS Cluster software with two exceptions:  ?               o  Clients cannot provide VOTES to the VMSclustero                  configurationse  E               o  Clients cannot MSCP serve disks or TMSCP serve tapes   F               OpenVMS Cluster Client software is available for VAX andC               Alpha systems. The software uses a License ManagementnG               Facility (LMF) license name of VMSCLUSTER-CLIENT. OpenVMSgI               Cluster Client software is included in the NAS 150 package,aI               and can be ordered separately. Refer to the OpenVMS ClusterdD               Software Product Description for ordering information.  H         3.3.4 DECnet Software No Longer Required for VMScluster Software  I               Prior to OpenVMS Version 6.2, DECnet Phase IV or DECnet/OSIdG               software was a prerequisite for VMScluster software. With G               OpenVMS Version 6.2, there is no longer a requirement for3               DECnet software.  D               DECnet software is required in VMScluster environments-               under the following conditions:t  E               o  When applications perform node-to-node communication '                  using DECnet mailboxes   I                                           System Management Features 3-11            "         System Management Features+         3.3 VMScluster Systems New Featuresn    9               o  When the MONITOR/CLUSTER utility is usedc  H               Note that DECnet is not required for the correct operationD               of SYSMAN in a VMScluster configuration. Also, you canI               perform SET HOST operations without DECnet by using the SETs               HOST/LAT command.   1         3.3.5 Support for TMSCP Served SCSI Tapesh  G               VMScluster Systems for OpenVMS has been enhanced to allowgD               the TMSCP server to serve SCSI tapes. The TMSCP serverB               makes locally connected tapes of the following types)               available across a cluster:t  '               o  TA series tapes for CIc  )               o  TF series tapes for DSSI   *               o  TZ and TLZ tapes for SCSI  B               The TMSCP server is controlled by the TMSCP_LOAD and0               TMSCP_SERVE_ALL system parameters.  D               o  The TMSCP_LOAD parameter controls whether the TMSCPF                  server is loaded. By default, the value of the TMSCP_G                  LOAD parameter is set to zero so that the TMSCP server G                  is not loaded. Refer to VMScluster Systems for OpenVMS >                  for information about setting this parameter.  F               o  The TMSCP_SERVE_ALL system parameter is new with thisE                  release. This parameter specifies TMSCP tape-servingoE                  functions when the TMSCP server is loaded. If TMSCP_wC                  LOAD is set to zero, the TMSCP_SERVE_ALL parametertD                  is ignored. Table 3-3 describes the TMSCP_SERVE_ALL$                  parameter settings.  <               Table 3-3 The TMSCP SERVE ALL System Parameter  #               Value     Descriptione  B               0         Serve no tapes. This is the default value.  2               1         Serve all available tapes.  ;               2         Serve only locally connected tapes.M  '         3-12 System Management Features            I                                                System Management Features I                                       3.3 VMScluster Systems New Featureso    B         3.3.5.1 No TMSCP Server Support for SCSI Retension Command  I               The SCSI Retension command modifier is not supported by therI               TMSCP server. Retension operations should be performed fromw(               the node serving the tape.  "         3.3.6 DECamds Enhancements  G               DECamds includes enhancements to provide additional eventeH               filtering and the ability to perform real-time recomputingE               of VMScluster quorum. Additionally, the DECamds console I               has been ported from VAX so that you can run it on an Alpha                system.n  5               For more information, see Section 3.23..  F         3.3.7 Enhanced Support for HSJ, HSC, and HSD Series Controller               Failover  G               In previous releases of VMScluster software, dual porting F               of disks between pairs of HSJ and HSC series controllersC               was supported when the controllers were attached to a F               common star coupler. Beginning with OpenVMS Version 6.2,C               you can connect dual-ported disks to pairs of HSJ and,C               HSC series controllers that are attached to differentBG               star couplers. This feature enhances availability because H               failure of a CI adapter need not cause both controllers to!               become unreachable.   A               This feature is available for HSJ and HSC series CInD               controllers and for HSD30 DSSI controllers. It permitsF               HSD30 controllers to be configured across different DSSI               buses.  F         3.3.8 Warranted and Migration VMScluster System Configurations  C               OpenVMS Alpha Version 6.2 and OpenVMS VAX Version 6.2 H               provide two levels of support for mixed-version and mixed-F               architecture VMScluster systems. These two support types*               are warranted and migration.  F               Warranted support means that Digital has fully qualifiedI               the two versions coexisting in a VMScluster system and willtE               answer all problems identified by customers using thesee               configurations.   I                                           System Management Features 3-13  m  ,      "         System Management Features+         3.3 VMScluster Systems New Features     D               Migration support is a superset of the rolling upgradeE               support provided in earlier releases of OpenVMS, and is C               available for mixes that are not warranted. Migration C               support means that Digital has qualified the versions F               for use together in configurations that are migrating inF               a staged fashion to a newer version of OpenVMS VAX or toD               OpenVMS Alpha. Problem reports submitted against theseE               configurations will be answered by Digital. However, inpG               exceptional cases, Digital may request that you move to acD               warranted configuration as part of fixing the problem.  E               Migration support will help customers move to warrantedwC               VMScluster version mixes with minimal impact on their #               cluster environments.   D               Figure 3-3 shows the level of support provided for all(               possible version pairings.  E               Note that Digital does not support the use of more thanlD               two versions in a VMScluster system at a time. In manyE               cases, more than two versions will successfully operateuI               but Digital cannot commit to resolving problems experiencedc'               with such configurations.e  I               The next major release of the OpenVMS operating system willoG               coexist in a mixed-version VMScluster system with OpenVMSoG               Version 6.2 (both VAX and Alpha). This is consistent with G               the Digital policy of providing mixed-version coexistence C               across adjacent OpenVMS releases. However, due to the E               development of many significant new features within theoD               OpenVMS operating system, it is expected that the nextI               major release will not coexist with OpenVMS Version 6.1 andm               earlier releases.o  <         3.4 Local Area Network (LAN) Management Enhancements  H               The local area network (LAN) software has been enhanced toI               include system management tools for LAN configurations. TheaH               enhancements include two LAN utilities that perform system               management tasks.   2               Chapter 6 discusses these utilities.      '         3-14 System Management Featureso h  w      I                                                System Management FeaturestH       3.5 Booting VMScluster Satellite Nodes Using the New LANCP Utility    B         3.5 Booting VMScluster Satellite Nodes Using the New LANCP             Utility   C               LANCP (LAN Control Program) and LANACP (LAN Ancillary C               Control Process) are new images supplied with OpenVMS E               Version 6.2. These images provide a general purpose MOP I               booting service that can be used for VMScluster satellites. E               This new utility, along with the CLUSTER_CONFIG_LAN.COM E               procedure, allows VMScluster systems to boot satellites I               without the use of DECnet and provides several features notd0               available with DECnet MOP booting.  B               By default in OpenVMS Version 6.2, DECnet is used toI               service satellite boot requests. However, you might want to G               use use LANCP/LANACP for satellite booting if you wish tosG               operate a VMScluster without DECnet or for other reasons.eG               This section provides instructions for using LANCP/LANACPn$               for satellite booting.  G               For more information on the LANCP utility, see Chapter 6.r           3.5.1 Overview  F               LANCP is the control program for LANACP, which runs as aI               detached process to service boot requests. LANCP and LANACPo/               utilize the following data files:r  3               o  SYS$SYSTEM:LAN$DEVICE_DATABASE.DATa  A                  This file maintains information about devices on C                  the local node. By default, the file is created inCI                  SYS$SPECIFIC:[SYSEXE], and the system looks for the filehH                  in that location. However, you can modify the file nameG                  or location for this file by redefining the systemwiden2                  logical name LAN$DEVICE_DATABASE.  1               o  SYS$SYSTEM:LAN$NODE_DATABASE.DATs  I                  This file contains information about the nodes for whichoE                  LANACP will supply boot service. This file should be D                  shared among all nodes in the VMScluster, includingD                  both Alpha and VAX systems. By default, the file isI                  created in SYS$COMMON:[SYSEXE], and the system looks foriG                  the file in that location. However, you can modify theSF                  file name or location for this file by redefining the;                  systemwide logical name LAN$NODE_DATABASE.   I                                           System Management Features 3-15            "         System Management FeaturesJ         3.5 Booting VMScluster Satellite Nodes Using the New LANCP Utility    -         3.5.2 Using LANACP to Boot Satellitess  H               You can use the LANACP utility to service all types of MOPH               downline load requests. This includes VMScluster satelliteD               nodes, terminal servers, LAN resident printers, and X-               terminals.  F                 ________________________ Note ________________________  A                 Digital recommends that customers currently usingi<                 DECnet Phase IV or DECnet/OSI to perform MOPA                 operations such as satellite loading, continue toqE                 do so. The new LANACP/LANCP feature is only necessaryp=                 for configurations that are not using DECnet.h  F                 ______________________________________________________  H               The next sections describe how to use LANACP for satelliteG               booting for new installations and existing installations.rF               Support for using LANCP and LANACP for satellite bootingI               requires all VMScluster nodes to be running OpenVMS Versions               6.2.  !         3.5.2.1 New Installationsd  C               For new OpenVMS installations to use LANCP/LANACP foro4               satellite booting, follow these steps:  3               1. Add the startup command for LANACPV  B                  You should start up LANACP as part of your systemG                  startup procedure. To do this, remove the comment fromMH                  the line in SYS$MANAGER:SYSTARTUP_VMS.COM that runs theI                  LAN$STARTUP command procedure. If your VMScluster systemsG                  will have more than one system disk, see Section 3.5.1sF                  for a description of logicals that can be defined for5                  locating LANACP configuration files.t  +                  $ @SYS$STARTUP:LAN$STARTUPo  B                  You should now either reboot the system or invokeF                  the above command procedure from the system manager's)                  account to start LANACP.   G               2. Follow the steps in the VMScluster Systems for OpenVMS F                  manual for configuring a VMScluster system and addingF                  satellites. Use the command procedure CLUSTER_CONFIG_E                  LAN.COM instead of CLUSTER_CONFIG.COM. If you invoke C                  CLUSTER_CONFIG.COM, it will give you the option to   '         3-16 System Management Features            I                                                System Management Features H       3.5 Booting VMScluster Satellite Nodes Using the New LANCP Utility    G                  switch to running CLUSTER_CONFIG_LAN.COM if the LANACP *                  process has been started.  &         3.5.2.2 Existing Installations  D               For an existing installation to migrate to using LANCPH               /LANACP for satellite booting, several steps are required.E               These include configuration of LANACP and configurationWE               of the node database with the nodes to be MOP booted bytG               LANACP. This initial release of LANCP/LANACP is primarilyiI               targeted for new VMScluster installations. There does existoF               some support to assist in migrating from DECnet Phase IVH               and minimal support for migrating from DECnet/OSI to LANCP               /LANACP.  &               Configuring LANCP/LANACP  @               To configure the data files SYS$SYSTEM:LAN$DEVICE_G               DATABASE.DAT and SYS$SYSTEM:LAN$NODE_DATABASE.DAT, follow                these steps:  6               1. Define LANCP/LANACP database logicals  G                  Define systemwide logicals for LAN$DEVICE_DATABASE and-H                  LAN$NODE_DATABASE if you wish these files to be locatedE                  in other than the default locations specified above. H                  These definitions should be added to the system startup                  files.   /               2. Create the LAN$DEVICE_DATABASE   H                  Use LANCP to configure LAN devices for MOP booting. TheH                  permanent LAN$DEVICE_DATABASE is created when the firstI                  DEVICE command is issued. To create the database and geth4                  a list of available devices, enter:                    $ MCR LANCP+                  LANCP> LIST DEVICE /MOPDLL E                  %LANCP-I-FNFDEV, File not found, LAN$DEVICE_DATABASE E                  %LANACP-I-CREATDEV, Created LAN$DEVICE_DATABASE filel  4                  Device Listing, permanent database:D                    --- MOP Downline Load Service Characteristics ---O                  Device    State   Access Mode      Client            Data SizesO                  ------    -----   -----------      ------            --------- N                  ESA0    Disabled NoExlusive  NoKnownClientsOnly     246 bytesN                  FCA0    Disabled NoExlusive  NoKnownClientsOnly     246 bytes  ?               3. Use LANCP to enable LAN device for MOP bootinge  I                                           System Management Features 3-17            "         System Management FeaturesJ         3.5 Booting VMScluster Satellite Nodes Using the New LANCP Utility    H                  By default, the LAN devices have MOP booting capabilityG                  disabled. Determine the LAN devices for which you wantsF                  to enable MOP booting. Then use the DEFINE command inI                  the LANCP utility to enable these devices to service MOPaI                  boot requests in the permanent database, as shown in theE#                  following example:s  6                  LANCP> DEFINE DEVICE ESA0:/MOP=ENABLE  0               4. Configure the LAN$NODE_DATABASE  D                  If you are running DECnet Phase IV, you can use theA                  command procedure SYS$EXAMPLES:LAN$POPULATE.COM.uD                  This procedure extracts all MOP booting informationC                  from a DECnet Phase IV NETNODE_REMOTE.DAT file andeB                  produces a site-specific command procedure calledD                  LAN$DEFINE.COM. You can then execute LAN$DEFINE.COM/                  to populate LAN$NODE_DATABASE.i  F                  For DECnet Phase IV sites, the LAN$POPULATE procedureE                  scans all DECnet areas (1-63) by default. If you MOPcG                  boot systems from only a single or a few DECnet areas, G                  you can cause the LAN$POPULATE procedure to operate on E                  a single area at a time by providing the area numbereF                  as the P1 parameter to the procedure, as shown in the3                  following example (including log):c  0                  $ @SYS$EXAMPLES:LAN$POPULATE 15  %                   LAN$POPULATE - V1.0   -                   Do you want help (Y/N) <N>:t  ?                   LAN$DEFINE.COM has been successfully created..  P                   To apply the node definitions to the LANCP permanent database,F                   invoke the created LAN$DEFINE.COM command procedure.  N               Digital recommends that you review LAN$DEFINE.COM and remove anyI               obsolete entries prior to executing this command procedure.   O                   A total of 2 MOP definitions were entered into LAN$DEFINE.COM   C                  The LAN$DEFINE procedure is created as part of the G                  LAN$POPULATE procedure. In the following sequence, therH                  LAN$DEFINE.COM procedure that was just created is typed1                  on the screen and then executed:l  '         3-18 System Management Features  A  a      I                                                System Management Features H       3.5 Booting VMScluster Satellite Nodes Using the New LANCP Utility             $ TYPE LAN$DEFINE.COM            $ !TO         $ ! This file was generated by LAN$POPULATE.COM on 16-DEC-1994 09:20:31h         $ ! on node CLU21.         $ !o,         $ ! Only DECnet Area 15 was scanned.         $ !d         $ MCR LANCP H           Define Node PORK    /Address=08-00-2B-39-82-85 /File=APB.EXE -O                            /Root=$21$DKA300:<SYS11.> /Boot_type=Alpha_SatellitetI            Define Node JYPIG   /Address=08-00-2B-A2-1F-81 /File=APB.EXE -rO                            /Root=$21$DKA300:<SYS10.> /Boot_type=Alpha_Satellites            EXITa            $ @LAN$DEFINE  <           %LANCP-I-FNFNOD, File not found, LAN$NODE_DATABASE;           -LANCP-I-CREATNOD, Created LAN$NODE_DATABASE file 
          $  H                  If you are currently running DECnet/OSI, information onH                  the nodes that DECnet/OSI will MOP boot can be obtained0                  with the following NCL command:                    $ MCR NCL+                  NCL> SHOW MOP CLIENT * ALLt  F                  Nodes for MOP booting can then be added to LANCP with.                  the following define command:                    $ MCR LANCP/                  LANCP> DEFINE NODE node-name -s&                  /ADDRESS=hw-address -=                  /BOOT_TYPE={VAX_SATELLITE,ALPHA_SATELLITE} -n/                  /ROOT=disk-device:<root-name.>   I                  Section 6.1.5 provides detailed information on the LANCP                    DEFINE command.                 5. Start LANACP   G                  To start LANACP, execute the startup command procedure.                  as follows:  I                                           System Management Features 3-19            "         System Management FeaturesJ         3.5 Booting VMScluster Satellite Nodes Using the New LANCP Utility    +                  $ @SYS$STARTUP:LAN$STARTUPnP                    %RUN-S-PROC_ID, identification of created process is 2920009B                    $  F                  You should start up LANACP for all boot nodes as partF                  of your system startup procedure. To do this, includeF                  the following line in your site-specific startup file1                  (SYS$MANAGER:SYSTARTUP_VMS.COM):u  +                  $ @SYS$STARTUP:LAN$STARTUPr  D                  If you have defined logicals for either LAN$DEVICE_F                  DATABASE or LAN$NODE_DATABASE, be sure that these areC                  defined in your startup files prior to starting upr                  LANACP.                                                            '         3-20 System Management FeaturesM l         I                                                System Management FeaturespH       3.5 Booting VMScluster Satellite Nodes Using the New LANCP Utility      +               6. Disable DECnet MOP bootinga  G                  If you use LANCP/LANACP for satellite booting, you maylI                  no longer need DECnet to handle MOP requests. If this issI                  the case for your site, you can turn off this capabilitymF                  with the appropriate NCP command (DECnet Phase IV) or+                  NCL commands (DECnet/OSI).r           3.6 AUTOGEN Changes   H               This section describes the changes made to AUTOGEN and how0               these changes affect this release.  :         3.6.1 Changes to Computation of SYSMWCNT Parameter  A               The formula AUTOGEN uses for computing the SYSMWCNTtH               parameter has been changed slightly. It will now typicallyD               calculate from 200 to 400 pages more than the previousF               formula. The number of pages might be higher on MicroVAX               systems.  &         3.6.2 Preventing Autoconfigure  >               You can prevent AUTOGEN from performing a SYSGENI               AUTOCONFIGURE by defining the AGEN$NO_AUTOCONFIGURE logicalgD               to be TRUE or 1. This makes it safer to run AUTOGEN onF               an active system because the AUTOCONFIGURE can interfereH               with active I/O on certain devices, and will not interfereB               with normal startup as incautious use of the logicalF               STARTUP$AUTOCONFIGURE_ALL might. It has the disadvantageG               that the GETDATA phase will record only the hardware that <               is already present and will not look for more.  3         3.6.3 Suppression of Informational Messages   G               You can suppress the display of informational messages on I               your terminal by defining the AGEN$REPORT_NO_INFORMATIONALS F               logical to TRUE or 1. Informational messages are enteredI               in SYS$SYSTEM:AGEN$PARAMS.REPORT regardless of the value ofd,               AGEN$REPORT_NO_INFORMATIONALS.        I                                           System Management Features 3-21     i      "         System Management Features         3.6 AUTOGEN Changess    E         3.6.4 Preventing AUTOGEN from Running As a Spawned Subprocess   ?               You can prevent AUTOGEN from running as a spawned F               subprocess by defining the AGEN$NO_SPAWN logical to TRUEI               or 1. AUTOGEN normally runs as a spawned subprocess for twoe               reasons:  H               o  AUTOGEN uses a large number of DCL symbols in its work,E                  and when run in a process that already has defined a G                  large number of symbols, it can run out of room in thecI                  symbol table. Running in a spawned subprocess makes thise%                  occurrence unlikely.i  E               o  When run in a spawned subprocess, AUTOGEN can define @                  some additional symbols in order to improve its                  performance..  I               If you define AGEN$NO_SPAWN to force AUTOGEN to run without G               spawning and it runs out of room in its symbol table, yout7               will receive the following error message:A  ?               %AUTOGEN-F-SYMOVF, no room for symbol definitions I               %AUTOGEN-F-DEL_EXP, delete some symbols or expand CLISYMTBLe  5         3.6.5 Overriding Parameters Related to DECnetn  H               The MODPARAMS.DAT file can now include the pseudoparameterG               LOAD_DECNET_IMAGES. Setting LOAD_DECNET_IMAGES to be TRUEtC               (or FALSE) overrides AUTOGEN's observations regardingeD               the presence or absence of DECnet. This is expected toF               be useful for sites with no synchronous network hardware3               that want to run asynchronous DECnet.r  -         3.7 New and Changed System Parameters   G               Table 3-4 describes the new and changed system parameters &               for OpenVMS Version 6.2.                '         3-22 System Management Featuresn u  o      I                                                System Management Features I                                     3.7 New and Changed System Parameters     3         Table 3-4 New and Changed System Parametersr  )         Parameter             Descriptionh  A         DR_UNIT_BASE          Specifies the base value from which B         (New Special          unit numbers for DR devices (DigitalH         Parameter)            StorageWorks RAID Array 200 Family logical7                               RAID drives) are counted.e  D         DUMPSTYLE+ (Changed)  Specifies the method of writing system$                               dumps.  G         LGI_BRK_LIM           Specifies the number of failures that can H         (Changed)             occur at login time before the system willF                               take action against a possible break-in.  F         RMTDBG_SCRATCH_       On Alpha systems, the number of pages ofG         PAGES++               memory allocated for the remote debugger.tI         (New)                 See the OpenVMS Alpha Device Support Manualt3                               for more information.   H         SHADOWING (Changed)   Digital does not support Phase I shadowingG                               for versions greater than OpenVMS VersionaH                               6.1. Use Phase II shadowing instead. PhaseD                               II shadowing provides shadowing of allH                               disks located on a standalone system or an5                               OpenVMS cluster system.   E                               SHADOWING has the following new values:d  F                               0   No shadowing is enabled; SHDRIVER is7                                   not loaded. (Default)t  I                               2   Phase II shadowing is enabled; SHDRIVERe,                                   is loaded.  I         TMSCP_SERVE_ALL       Specifies TMSCP tape-serving functions when F         (New)                 TMSCP server is loaded. If TMSCP_LOAD isH                               set to 0, the TMSCP_SERVE_ALL parameter isF                               ignored. Refer to VMScluster Systems forG                               OpenVMS for information about setting the.8                               TMSCP_SERVE_ALL parameter.           +VAX onlyt           ++Alpha only  I                                                  (continued on next page)_  I                                           System Management Features 3-23i           "         System Management Features-         3.7 New and Changed System Parametersr    ;         Table 3-4 (Cont.) New and Changed System Parameters   )         Parameter             Descriptionp  @         VCC_PTES+ (New)       Used on VAX systems to specify theE                               MAXIMUM size that the virtual I/O cache F                               is permitted to expand dynamically. VCC_E                               PTES is a static parameter and requireslH                               that the system reboot after being changed7                               by the AUTOGEN mechanism.          +VAX onlyNI         _________________________________________________________________p  H               Refer to the OpenVMS System Management Utilities ReferenceH               Manual for more information about these system parameters.           3.8 Backup Manager  H               Backup Manager provides a screen-oriented interface to theI               OpenVMS Backup utility (BACKUP) based on the OpenVMS ScreenbE               Management Run-Time Library (RTL) routines. It presentsfF               a subset of BACKUP's capabilities in an intuitive, task-E               oriented, self-documenting manner that does not require G               knowledge of BACKUP command syntax and qualifiers. Backup H               Manager is designed to help the user perform common systemF               management tasks such as backing up files to a save set,G               restoring files from a save set, and listing the contents                of a save set.  C               To start Backup Manager, issue the following command:s  -               $ RUN SYS$SYSTEM:BACKUP$MANAGERu  E               Documentation on features, concepts, and how to use theiE               utility is available on line through each screen's helppF               menu. Context-sensitive help on any field is provided by$               pressing the Help key.           3.9 BACKUP Changes  B               This section describes the new features added to the6               OpenVMS Backup utility for this release.  E               See the OpenVMS System Manager's Manual for informationb&               about how to use BACKUP.  '         3-24 System Management Featuresm l         I                                                System Management Features I                                                        3.9 BACKUP Changes     '         3.9.1 New Qualifier, /[NO]ALIASC  I               The /[NO]ALIAS qualifier has been added to allow users moreAI               control over how alias (synonym) file entries are processed D               by the OpenVMS Backup utility (BACKUP). The default is               /ALIAS.t  C               See the OpenVMS System Management Utilities Reference ?               Manual for more information about this qualifier.-  <         3.9.2 Increased Number of Directory Levels Supported  C               BACKUP now supports saving individual files or groupsiE               of files located in disk directories greater than eightyC               levels in depth, up to 32 levels of disk directories. I               Prior versions of BACKUP (and OpenVMS utilities in general) I               could not access, and thus could not save, files located ina=               directories greater than eight levels in depth.T  I               BACKUP also supports restoring these files selectively in a H               BACKUP restore operation. Note, however, that OpenVMS fileI               system restrictions still apply when restoring these files.TI               For nonimage and nonphysical restore operations, individuallE               files or groups of files may be restored to a disk, but G               the destination directories must be no greater than eight                levels deep.  F               This new feature is of most interest to PATHWORKS users.           3.10 Full Name Support  H               Information about full name support that was documented inI               OpenVMS Version 6.1 manuals as VAX specific also applies tos(               Alpha Version 6.2 systems.  ,         3.10.1 Use of Full Names with SYSMAN  E               SYSMAN now supports longer node names in an environment D               command. A valid node name can be up to 255 characters               long.e                 ExampleP  I               SYSMAN> SET ENVIRONMENT/NODE=VMS:.ZKO.VMSORG.SYSMAN.CLIENT1a  I                                           System Management Features 3-25w s         "         System Management Features         3.10 Full Name Support    E               In a local cluster, when full names are used instead of I               SCSNODE name in an environment command, DECnet will be used G               for communication, even though the systems are clustered. I               For example, if SYS1 and SYS2 are two systems in a cluster, C               the following command would result in usage of DECnet F               services for communication rather than SCS services. DueF               to this difference, the user will be prompted to enter a               remote password.  I               The following command is issued from SYS1 to SYS2. SYS1 and I               SYS2 are assumed to be clustered and are running DECnet/OSI$               for OpenVMS.  8               SYSMAN> SET ENVIRONMENT/NODE=VMS:.ZKO.SYS2               Remote Password:9               %SYSMAN-I-ENV, current command environment:65                       Individual nodes: VMS:.ZKO.SYS2m?                       At least one node is not in local clusteruE                       Username SYSTEM  will be used on nonlocal nodesa  D               For more information, see the OpenVMS System Manager's               Manual.h  <         3.11 Two Proxy Authorization Files, NETPROXY.DAT and              NET$PROXY.DAT  D               Proxy authorization file information that was shown inI               OpenVMS Version 6.1 manuals as VAX specific also applies to (               Alpha Version 6.2 systems.  4         3.11.1 Creation of Proxy Authorization Files  F               OpenVMS Alpha Version 6.2 offers two proxy authorizationF               files, NETPROXY.DAT and NET$PROXY.DAT, which are created5               with the following default protections:   6               NETPROXY.DAT    S:RWED, O:RWED, G:RWE, W-               NET$PROXY.DAT   S:RWED, O, G, WP  D               The primary proxy database that the system uses is theA               NET$PROXY.DAT file. NETPROXY.DAT is maintained for:N  *               o  Use by DECnet for OpenVMS  '               o  Backward compatibilityc  '         3-26 System Management Features            I                                                System Management Features I        3.11 Two Proxy Authorization Files, NETPROXY.DAT and NET$PROXY.DATe    "         3.11.2 Proxy Modifications  D               To properly maintain proxy database consistency acrossC               all members of a mixed-version VMScluster system, youNE               must perform all proxy modifications from either of the                following:  4               o  A VAX Version 6.1 (or later) system  ,               o  An Alpha Version 6.2 system  I               This restriction ensures that the NET$PROXY.DAT database is05               updated with correct proxy information.n  H               For more information about proxy accounts, see the OpenVMS'               Guide to System Security.t  $         3.12 Security Server Process  F               The Security Server process, which is created as part ofE               normal operating system startup, performs the followingE               tasks:  D               o  Creates and manages the system's intrusion database  :               o  Maintains the network proxy database file                   (NET$PROXY.DAT)  H               The intrusion database is used by the system to keep trackC               of failed login attempts. This information is scannedgI               during process login to determine if the system should takemG               restrictive measures to prevent access to the system by a F               suspected intruder. The contents of this database may beI               examined by the DCL SHOW INTRUSION command. Information caneI               be deleted from the database using the DCL DELETE/INTRUSIONr               command.  E               The network proxy database file (NET$PROXY.DAT) is used D               during network connection processing to determine if aE               specific remote user may access a local account without A               using a password. The information contained in thisg;               database is managed by the Authorize utility.s  F               The following example shows the expanded expiration time5               field in the new SHOW INTRUSION output:    $ SHOW INTRUSIONA Intrusion       Type       Count        Expiration         SourcerO   NETWORK      SUSPECT       1   21-OCT-1994 12:41:01.07  DEC:.ZKO.TIDY::SYSTEMr  I                                           System Management Features 3-27e e  i      "         System Management Features$         3.12 Security Server Process    C               For more information, see the OpenVMS Guide to Systemd               Security.D  /         3.13 New LAT System Management FeaturesA  C               The OpenVMS VAX Version 6.2 operating system includeslC               new features that have been added to the SET HOST/LAT G               command, the LAT Control Program (LATCP) utility, and theF&               programming environment.  B               Because these features were added to the OpenVMS AXPG               Version 6.1 operating system, see the following documents ,               for more detailed information:  @               o  OpenVMS System Manager's Manual, for LAT system'                  management informationt  F               o  OpenVMS System Management Utilities Reference Manual,6                  for new LATCP commands and qualifiers  F               o  OpenVMS DCL Dictionary, for information about the SET!                  HOST/LAT command   E               o  OpenVMS I/O User's Reference Manual, for informations3                  about new LAT programming features   ?         3.14 New /NO_SHARE Qualifier for LICENSE MODIFY CommandM  F               This new qualifier lets you add the NO_SHARE option to aF               PAK registered in a license database (LDB). The NO_SHAREH               PAKs are assigned to a single node in a VMScluster system.C               A NO_SHARE PAK cannot be shared with other VMSclustero               nodes.  >               The use of this qualifier remedies problems thatE               occasionally occur when you attempt to use the PAK of aUG               software product for which you already have other PAKs in H               your LDB. The PAK does not combine with the other PAKs forF               the same software product, resulting in LICENSE-W-NOCOMBI               warnings. Often, the license is not loaded on the nodes youn                want it loaded on.  7               To remedy this problem, do the following:.  G               1. Add the NO_SHARE option to the PAK or PAKs causing theo                   NOCOMB warnings  >               2. Assign each PAK to a specific VMScluster node  '         3-28 System Management Features            I                                                System Management FeaturesoI                   3.14 New /NO_SHARE Qualifier for LICENSE MODIFY Commando    F               For more information, see the OpenVMS License Management               Utility Manual.r  5         3.15 Choosing Languages and Date/Time FormatsR  E               Beginning with OpenVMS Version 6.2, system managers cangE               select the time and date formats for many SHOW commands I               from a predefined list or define new time and date formats.n  F                 ________________________ Note ________________________  C                 The SHOW TIME command does not include this featureOE                 because the SHOW TIME command is processed completelys>                 by DCL, which does not have access to the LIB$>                 routines that are needed to format the output.  B                 In addition, the SHOW commands for batch and printC                 operations were modified to include, in the default F                 timestamp, seconds as well as hours and minutes. These<                 new features were not previously documented.  F                 ______________________________________________________  G               For example, rather than 15-JAN-1995 10:16:25.14, you cano<               use a different format, such as the following:                 $ SHOW USERS  G                     OpenVMS User Processes at JANUARY 15, 1995 10:16 AM F                   Total number of users = 7,  number of processes = 11  D                Username     Node     Interactive  Subprocess   Batch.                MCDERMOT    ARD26B            1B                PASTERNAK   ARD26B            -         2         1                  .                  .                  .  I               Users can override the system defaults set up by the systemTA               manager and select their own date and time formats.a  C               System managers can also specify languages other thaneE               English. From the list that the system manager defines,dI               users can later select a language that they want displayed.e  D               For more information, see the OpenVMS System Manager's               Manual.m  I                                           System Management Features 3-29  2  s      "         System Management Features;         3.16 Operator Communication Manager (OPCOM) Changest    ;         3.16 Operator Communication Manager (OPCOM) Changese  B               The following Operator Communication Manager (OPCOM)@               changes appear in the OpenVMS Version 6.2 release:  D               o  Selected operator classes are enabled, depending on=                  whether or not the operator log file is open   -               o  OPC$V_OPR_* replaces OPR$V_*   ?               o  OPC$OPA0_ENABLE is used to override values fort                  workstationsn  )               o  New field names are used   D               For more information, see the OpenVMS System Manager's               Manual.a  1         3.16.1 Enabling Selected Operator Classes   C               In previous versions of the OpenVMS operating system,eF               after the initial creation of the OPERATOR.LOG file, anyF               subsequent REPLY/LOG command created a new log file with2               all of the operator classes enabled.  E               In OpenVMS Version 6.2, this functionality has changed:   F               o  If a log file is already open, the list of classes isE                  preserved and enabled on the newly created log file.   D               o  If a log file is not open, the value of the logicalI                  OPC$ENABLE_LOGFILE_CLASSES is used. If that logical does H                  not exist, all classes are enabled on the new log file.  +         3.16.2 OPC$V_OPR_* Replaces OPR$V_*   F               The bit definitions OPR$V_*, which were loosely based onH               the operator classes, are now obsolete. (These definitions@               were never documented.) OPC$V_OPR_* replaces these1               definitions in OpenVMS Version 6.2.   H         3.16.3 Using OPC$OPA0_ENABLE to Override Values for Workstations  E               You can now use the OPC$OPA0_ENABLE logical to override H               the values for the symbols for a workstation in a cluster.H               In previous versions of the OpenVMS operating system, if aH               system was defined as a workstation in a cluster, the OPA0,               device was set to NOBROADCAST.  '         3-30 System Management Featuresm o  b      I                                                System Management Features I                       3.16 Operator Communication Manager (OPCOM) Changes     %               In OpenVMS Version 6.2:   B               o  For workstations in a cluster, you can define theH                  OPC$OPA0_ENABLE logical as TRUE to override NOBROADCAST;                  and thus set the OPA0 device to BROADCAST.e  G               o  For all systems that are not workstations in clusters,oG                  you can define the logical OPC$OPA0_ENABLE as FALSE to 4                  set the OPA0 device to NOBROADCAST.  $         3.16.4 Using New Field Names  I               In OpenVMS Version 6.2, the following fields have new names G               (although you can still use the old names to refer to theh               fields):  B               o  Change OPC$B_MS_TARGET to OPC$Z_MS_TARGET_CLASSES  G                  This is a three-byte field that stores the bit mask of_)                  target operator classes.e  @               o  Change OPC$B_MS_ENAB to OPC$Z_MS_ENAB_TERMINALS  I                  This is a value that indicates whether the given classes @                  should be disabled (zero) or enabled (nonzero).  +         3.17 Invalid Symbiont Message Codes   H               The invalid symbiont message errors logged to the operatorF               console and operator log file now contain integer valuesH               that identify why the symbiont message was rejected. There>               are two types of symbiont message errors logged:  8               o  Informational invalid symbiont messages  C               o  Messages that cause the queue manager to abort the                   symbionts  6         3.17.1 Informational Invalid Symbiont Messages  I               The informational invalid symbiont messages that are loggedaG               to the operator console are listed in Table 3-5. When thecD               queue manager logs these messages, the contents of theF               message causing the error are ignored. The queue manager=               continues to accept messages from the symbiont.   I                                           System Management Features 3-31            "         System Management Features+         3.17 Invalid Symbiont Message Codesr    F               In the following example, the queue manager signals thatI               the symbiont sent a STOP_STREAM request at an inappropriate (               time for queue TEST_QUEUE:  7 %%%%%%%%%%%  OPCOM  ss-MMM-ddd hh:mm:ss.hh  %%%%%%%%%%%  Message from user QUEUE_MANAGEP %QMAN-I-INVSMBMSG2, invalid data 10 in message from symbiont on queue TEST_QUEUE  I         Table 3-5 Informational Invalid Symbiont Message Type Definitionse           Value  Description  ;         00     Error processing symbiont message item list.   H         01     Job in symbiont message is not valid for queue, or job isD                not active. The job does exist in the queue database.           02     Unused.  F         03     Job state is starting but symbiont message received was                not START_TASK.  E         04     Symbiont device status requesting that tasks be pausedrC                when queue state is not pausing, busy, or available.d  F         05     Symbiont device status requesting that queue be stalled3                when queue is not busy or available.   G         06     Symbiont PAUSE_TASK message received when queue state is(                not pausing.r  H         07     Symbiont RESUME_TASK message received when queue state is                not resuming.  I         08     Symbiont START_STREAM message received when queue state isr                not starting.           09     Unused.  F         10     Symbiont stopped the stream when the queue state is not                stopping.  A         3.17.2 Messages That Cause the Queue Manager to Abort theh                Symbiont,  G               Invalid symbiont messages that cause the queue manager toiH               request the symbiont to abort are listed in Table 3-6. TheG               queue manager returns a JBC$_INVMSG status in the iosb of E               the $SNDJBC SYMBIONT_SERVICE request that generated the H               error. The PRTSMB or LATSYM process will exit, producing aG               dump file. For example, if a start queue requiring that atH               new symbiont process be created is immediately followed by  '         3-32 System Management Featuresn s  o      I                                                System Management FeatureseI                                       3.17 Invalid Symbiont Message CodesP    F               a stop queue for the same queue, an invalid message typeE               number 53 might be logged, as in the following example:r  ?         %%%%%%%%%%%  OPCOM  ss-MMM-ddd hh:mm:ss.hh  %%%%%%%%%%% &         Message from user QUEUE_MANAGEI         %QMAN-I-INVSMBMSG2, invalid data 53 in message from symbiont id 4C  6         Table 3-6 Invalid Symbiont Message Definitions           Value  Description  I         51     Symbiont message SMBMSG$K_STRUCTURE_LEVEL field is invalidYB                or message length less than SMBMSG$S_REQUEST_HEADER  ;         52     Invalid symbiont id number in message headerv  C         53     All queues were stopped before message received; thet0                symbiont is expected to terminate  C         54     The current incarnation of the queue manager did notnE                create the symbiont process sending the message (mightd(                be seen during failovers)  F         55     The symbiont sent a duplicate START_SYMBIONT message to                 the queue manager  G         56     The maximum streams in the START_SYMBIONT message is out                 of rangei  G         57     The stream number in the message is greater than maximumtH                allowable streams, or the PID of the symbiont sending the6                message is unknown to the queue manager  $         3.18 Erasing Old Home Blocks  H               When you initialize a volume, the initialize operation mayH               not erase old home blocks. These are home blocks that were8               created by previous initialize operations.  F               If a volume that has old home blocks is damaged, you may0               not be able to recover the volume.  G               You can now erase old home blocks manually, using the newoI               /HOMEBLOCKS qualifier on the ANALYZE/DISK_STRUCTURE commandw               as follows:   8               $ ANALYZE/DISK_STRUCTURE/REPAIR/HOMEBLOCKS  C               Note that this operation can take up to 30 minutes to                complete.   I                                           System Management Features 3-33  E  R      "         System Management Features$         3.18 Erasing Old Home Blocks    G               For further information, see the OpenVMS System Manager'se@               Manual and the OpenVMS System Management Utilities               Reference Manual.e  -         3.19 Additional SHUTDOWN.COM Logicals   D               Two new logicals in the SHUTDOWN.COM command procedureI               allow system managers to determine the time when DECnet ando#               queues are shut down:x  I               ___________________________________________________________f1               Logical Name            Descriptionn  C               SHUTDOWN$DECNET_        Defines the number of minutes D               MINUTES                 remaining before shutdown whenB                                       DECnet is shut down; must beI                                       defined with the /SYSTEM qualifier.p  ?                                       The default is 6 minutes.i  C               SHUTDOWN$QUEUE_MINUTES  Defines the number of minutesiD                                       remaining before shutdown whenC                                       queues are shut down; must be:I                                       defined with the /SYSTEM qualifier.   >                                       The default is 1 minute.  F               For more information about SHUTDOWN.COM, see the OpenVMS&               System Manager's Manual.  @         3.20 Installing or Upgrading from a Running Alpha System  G               Beginning with OpenVMS Alpha Version 6.2, you can install A               or upgrade from a running OpenVMS Alpha system to a G               target system disk. To do this, run the same installation H               procedure that you use to install or upgrade OpenVMS Alpha1               from the distribution compact disc.D  H               This new feature provides functionality that is similar toF               that of the command procedure VMSKITBLD.COM, which is no0               longer supported on Alpha systems.  E               For more information, see the OpenVMS Alpha Version 6.2 1               Upgrade and Installation Manual. <>t  '         3-34 System Management Featurest A  o      I                                                System Management FeaturesoI                                3.21 OpenVMS Support for TCP/IP NetworkingT    2         3.21 OpenVMS Support for TCP/IP Networking  E               For this release, the OpenVMS operating system supports.F               Transmission Control Protocol/Internet Protocol (TCP/IP)F               parameters and qualifiers for the DCL commands SET HOST,C               COPY, and DIRECTORY. These commands invoke the TCP/IPoE               layered software products that access remote terminals,u%               files, and directories.a  H               For more information, see the TCP/IP Networking on OpenVMS               Systems manual.e  *         3.22 Dump File Off the System Disk  A               To enable OpenVMS VAX customers to place the systemyA               dump file on a device other than the system disk, a C               new capability has been added for a restricted set ofe               configurations.   A               The current mechanism of using the system disk as a:D               dump device will not be otherwise affected by this new               capability.   D               For more information, see the OpenVMS System Manager's               Manual. <>           3.23 DECamds  F               The Digital Availability Manager for Distributed SystemsB               (DECamds) is a real-time monitoring, diagnostic, andE               correction tool that assists system managers to improve D               OpenVMS system and VMScluster availability. DECamds isD               also helpful to system programmer/analysts to target aH               specific node or process for detailed analysis, and systemH               operators and service technicians to help resolve hardware$               and software problems.  A               DECamds simultaneously collects and analyzes systemlD               data and process data from multiple nodes and displaysD               the output on a DECwindows Motif display. Based on theE               collected data, DECamds analyzes, detects, and proposesuI               actions to correct resource and denial issues in real time.i  ;               New features for OpenVMS Version 6.2 include:d  F               o  Console application support for OpenVMS Alpha systems  1               o  Ability to modify cluster quoruma  I                                           System Management Features 3-35            "         System Management Features         3.23 DECamds    F               o  Enhanced customization options for Locks, Events, and                  Disk Volumes   A               o  Ability to search for specific processes by name   H               For more information, see the DECamds User's Guide and the$               DECamds Release Notes.  3         3.24 Inclusion of Selected Layered Productsa  G               OpenVMS is introducing additional software to the OpenVMS G               CD-ROM distribution kit with the release of OpenVMS AlphaeD               and OpenVMS VAX Version 6.2. The kit has been expandedC               to include software products that previously required D               the purchase of additional CD-ROMs. This new packagingE               strategy simplifies customer purchases and installation G               processes. In addition, all OpenVMS VAX and OpenVMS Alpha F               online documentation will now be included on one OpenVMS#               documentation CD-ROM.   C               The following products have been added to the OpenVMSt.               Version 6.2 CD-ROM distribution:  I               ___________________________________________________________ '                                     VAX =                                     Version     Alpha Version   3               POSIX                 2.0         2.0   5               DECwindows Motif      1.2-3       1.2-3_  3               Softwindows           N/A         1.01  3               SoftPC                4.0         N/Ai  3               TCP/IP Services       3.3         3.3   4               DECmigrate            1.1A        1.1A  3               DCE Runtime Services  1.3         1.3a  3               DCE Security Server   1.3         1.3   3               DCE Cell Directory    1.3         1.3s               Server  3               DCE Application       1.3         1.3E               Developer's Kit   A               These layered software products will continue to be H               included on the quarterly VAX CONDIST distribution and theH               Alpha Layered Product Software Library, except for the DCEH               products, which are available as a separate kit. Customers  '         3-36 System Management Features     t      I                                                System Management FeaturesaI                               3.24 Inclusion of Selected Layered Productsm    G               should continue to purchase these quarterly distributions C               to have access to the most current software versions.gF               The OpenVMS CD-ROM distribution will contain the layeredG               product version that is available at the time the OpenVMS +               operating system is released.a  B               The rights to use POSIX and DCE Runtime Services areF               granted with the OpenVMS VAX and OpenVMS Alpha operatingE               system licenses. All other layered products continue to 4               require a license to run the software.  E               This new packaging will require changes to the contents D               of the OpenVMS CD-ROM distribution kits. The new media4               contents of these kits are as follows:  ?               o  OpenVMS Alpha V6.2 CD-ROM H-kit (QA-MT1AA-H8):E  ;                  -  OpenVMS Alpha Version 6.2 Binary CD-ROM   <                  -  OpenVMS VAX and Alpha Version 6.2 Online(                     Documentation CD-ROM  C                  -  OpenVMS Freeware CD-ROM for VAX & Alpha Systemsf  )                  -  Alpha Firmware CD-ROMl  =               o  OpenVMS VAX V6.2 CD-ROM H-kit (QA-XULAA-H8):t  9                  -  OpenVMS VAX Version 6.2 Binary CD-ROMl  <                  -  OpenVMS VAX and Alpha Version 6.2 Online(                     Documentation CD-ROM  C                  -  OpenVMS Freeware CD-ROM for VAX & Alpha Systemsl  P               o  OpenVMS Combined (VAX & Alpha) V6.2 CD-ROM H-kit (QA-MT3AA-H8):  ;                  -  OpenVMS Alpha Version 6.2 Binary CD-ROMl  9                  -  OpenVMS VAX Version 6.2 Binary CD-ROM   <                  -  OpenVMS VAX and Alpha Version 6.2 Online(                     Documentation CD-ROM  C                  -  OpenVMS Freeware CD-ROM for VAX & Alpha SystemsP  )                  -  Alpha Firmware CD-ROMi  I                                           System Management Features 3-37r e  l      "         System Management Features3         3.24 Inclusion of Selected Layered Products     D               The OpenVMS Freeware CD-ROM has also been added to allH               OpenVMS VAX V6.2 and OpenVMS Alpha V6.2 distribution kits.G               This CD-ROM contains free software tools and utilities to G               aid software developers in both creating applications ande0               managing or using OpenVMS systems.  D               See Section 2.1 for more information about the OpenVMS               Freeware CD-ROM.  I               See the OpenVMS Version 6.2 CD-ROM User's Guide for product 6               directory and documentation information.                                                                    '         3-38 System Management Featurese h  P                    I                                                                         4eI         _________________________________________________________________t  I                                                       ProgrammingFeaturesi    I               This chapter describes new features relating to applicationsC               and system programming on this version of the OpenVMSa7               operating system. These features include:   -               o  DECnet/OSI full name supportC  6               o  LAN programming features (Alpha only)  )               o  LAT programming featuresr  9               o  System services changes and enhancementsA  E               o  OpenVMS Alpha programming support for SCSI-2 devicesi  '               o  C++ RTL object library   7               o  New linker option RMS_RELATED_CONTEXT=   (         4.1 DECnet/OSI Full Name Support  D               DECnet/OSI full names are supported in this version ofE               OpenVMS Alpha. Full names are hierarchically structureduA               node names that can be a maximum of 255 bytes long.eG               Several run-time routines and several system services are E               provided to support this function. They are documented, H               respectively, in the OpenVMS RTL Library (LIB$) Manual and>               in the OpenVMS System Services Reference Manual.  E               For each of the full name routines and system services,aI               this documentation currently states that they are availableWE               for VAX only. This is no longer true. The documentation F               will be updated to reflect the availability of full name@               routines on both OpenVMS Alpha and OpenVMS VAX. <>      I                                                   ProgrammingFeatures 4-1                     ProgrammingFeaturese(         4.1 DECnet/OSI Full Name Support    3         4.1.1 DECnet/OSI Full Name Support Routinesh  @               The DECnet/OSI full name support routines that areF               currently available in LIBRTL on both OpenVMS VAX and on                OpenVMS Alpha are:  #               o  LIB$BUILD_NODESPECg  %               o  LIB$COMPARE_NODENAMES  &               o  LIB$COMPRESS_NODENAME  $               o  LIB$EXPAND_NODENAME  !               o  LIB$FIT_NODENAMEs  (               o  LIB$GET_FULLNAME_OFFSET  !               o  LIB$GET_HOSTNAMEe  "               o  LIB$TRIM_FULLNAME  H               For more information, see the documentation on each of the               routines.T  $         4.2 LAN Programming Features  A               The following sections describe new LAN programmingt5               features for OpenVMS Alpha Version 6.2.T  %         4.2.1 New Devices and Driverss  B               Table 4-1 lists new devices and drivers supported by"               OpenVMS Version 6.2.  7               Table 4-1 Supported Communication Devices   4               Device                          Driver  6               Proteon PROnet-4/16 ISA NIC     IRDRIVER               (DW110)s  6               Digital FDDI PCI-bus (DEFPA)    FWDRIVER  6               Digital Quad Ethernet PCI-bus   EWDRIVER               (DE436)m  6               Digital Ethernet PCI-bus        EWDRIVER               (DE434)r  I                                                  (continued on next page)m           4-2 ProgrammingFeaturesu    t      I                                                       ProgrammingFeatureseI                                              4.2 LAN Programming Featuresy    ?               Table 4-1 (Cont.) Supported Communication Devicess  4               Device                          Driver  6               Digital Ethernet ISA-bus        ERDRIVER               (DE200)   6               Digital Ethernet ISA-bus        ERDRIVER               (DE201).  6               Digital Ethernet ISA-bus        ERDRIVER               (DE202)r  H               For more information, see the OpenVMS I/O User's Reference               Manual.d  .         4.2.2 New LAN Device Names and Devices  H               Table 4-2 lists the new device names and devices supported%               by OpenVMS Version 6.2.   4               Table 4-2 LAN Device Names and Devices  6               Device Name     Device            Medium  :               IRc0:           DW110             Token Ring  5                FWc0:           DEFPA             FDDI   8               EWc0:           DE436             Ethernet  8               EWc0:           DE434             Ethernet  8               ERc0:           DE200             Ethernet  8               ERc0:           DE201             Ethernet  8               ERc0:           DE202             Ethernet  H               For more information, see the OpenVMS I/O User's Reference               Manual.   ,         4.2.3 New Controller Characteristics  A               Table 4-3 lists the new Ethernet controller and itseE               device characteristics when using the Get Device/Volume D               Information (SYS$GETDVI) system service with the DVI$_.               DEVTYPE and DVI$_DEVCLASS items.  I                                                   ProgrammingFeatures 4-3T s  i               ProgrammingFeatures $         4.2 LAN Programming Features    B               Table 4-3 Ethernet Controller Device Characteristics                 Ethernet<               Controller  Device Type      Device Class Name  3               DW110       DT$_IR_DW300     DC$_SCOMa  3               DEFPA       DT$_FW_DEFPA     DC$_SCOM   3               DE200       DT$_ER_DE422     DC$_SCOM.  3               DE201       DT$_ER_DE422     DC$_SCOMi  3               DE202       DT$_ER_DE422     DC$_SCOM   3               DE436       DT$_EW_DE435     DC$_SCOMt  3               DE434       DT$_EW_DE435     DC$_SCOMo  H               For more information, see the OpenVMS I/O User's Reference               Manual.   8         4.2.4 New Procedures for Configuring ISA Devices  B               There are two ways to configure an ISA LAN device on+               OpenVMS. They are as follows:R  H               o  Create an entry in the SYS$MANAGER:ISA_CONFIG.DAT file.  I               o  Use the isacfg command at the console prompt (>>>). Thist7                  requires the use of SYSMAN IO CONNECT.   F               If you choose to create an entry in the SYS$MANAGER:ISA_I               CONFIG.DAT file, see SYS$MANAGER:ISA_CONFIG.TEMPLATE for ansH               example. To use the isacfg command at your console prompt,H               see the hardware documentation associated with your system#               for more information.   B               Regardless of which configuration method you choose,A               you should become familiar with the concepts listedyC               in Table 4-4. See your LAN hardware documentation foruG               configuring information on how to set the jumper settings_5               for those features listed in Table 4-4.              4-4 ProgrammingFeatures  T  N      I                                                       ProgrammingFeatures J                                               4.2 LAN Programming Features    0               Table 4-4 ISA Configuring Concepts  -               Concept             Explanation   G               ISA slot number     Also called node. The ISA slot number D                                   that the device is in. The OpenVMSG                                   Alpha Device Support Manual describes :                                   how to number ISA slots.  A               IRQ                 Interrupt request line. Used toiG                                   establish the interrupt level. Boards B                                   support IRQs from 1 to 15. SinceG                                   OpenVMS does not support shared IRQs,UH                                   every ISA device must have its own IRQF                                   value reserved for it by the console1                                   ISACFG utility.a  F               Port address        I/O base control and status registerH                                   (CSR) address. Boards usually have I/OE                                   addresses associated with their CSRoE                                   locations. These locations must notnF                                   be in use by any other device on the)                                   system.i  I               Memory address      Also called shared memory. This addresstH                                   range is used to share memory residentF                                   on the adapter card between the hostG                                   CPU and the LAN device on the adapterNI                                   card. If the device uses shared memory, A                                   the I/O addresses for accessing E                                   this memory must be reserved. These I                                   locations must not be used by any other 7                                   device on the system.P  D               DMA channel         If the device performs DMA (eitherH                                   slave or bus mastering), a DMA channelD                                   is required. Channels are numberedA                                   1 to 7, but channel 4 is always C                                   reserved for the system. See your H                                   adapter documentation for DMA channels:                                   supported by the device.        I                                                   ProgrammingFeatures 4-5i a  :               ProgrammingFeaturest$         4.2 LAN Programming Features    ;         4.2.4.1 OpenVMS LAN Devices Requiring Configuratione  E               The DE202 Ethernet and DW110 Token Ring devices requireDF               configuring. The following information and examples show               how this is done.   &               4.2.4.1.1 DE202 Ethernet  H               The DE202 is a shared memory Ethernet device. To configure?               the jumper settings on the board, see the adaptersD               documentation. Example 4-1 and Example 4-2 show how toB               configure the OpenVMS software to use the DE202. The5               examples illustrate a configuration of:                  o  Slot 1   !               o  IO Base at %x300                  o  IRQ 5  @               o  Shared memory at %xd0000 with length of %x10000  H               Example 4-1 Using the isacfg Command at the Console Prompt  F               >>> isacfg -slot 1 -etyp 1 -ena 1 -irq0 5 -iobase0 %x300N                          -membase0 %xd0000 -memlen0 %x10000 -handle "DE20" -mk  H               The -mk command makes an isacfg entry for an ISA device atG               slot 1. It is a single-port type of device (-etyp 1). TheeG               -handle parameter tells the operating system what type of                device it is.   D               Example 4-2 Using the SYS$MANAGER:ISA_CONFIG.DAT Entry                    [ERA0]                   NAME=ER$                  DRIVER=SYS$ERDRIVERN                  NODE=1                       ; plugged into ISA Option slot 1                  IRQ=5H                  PORT=(300:f)                 ; 15 bytes starting at 300K                  MEM= (D0000:10000)           ; 64 Kbytes starting at D0000                  4-6 ProgrammingFeaturesu a         I                                                       ProgrammingFeatures I                                              4.2 LAN Programming Features     (               4.2.4.1.2 DW110 Token Ring  E               The DW110 is a bus mastering DMA device on the ISA bus.rG               In addition to setting up the ISA I/O parameters, you mayaG               configure ring speed (4 or 16 Mb) and media (UTP or STP).oI               By using LANCP, you can also configure ring speed and media E               during system startup. Example 4-3 and Example 4-4 showSI               how to configure the OpenVMS software to use the DW110. Thec5               examples illustrate a configuration of:o                 o  Slot 4                  o  IRQ 10_                 o  DMA channel 7                 o  Base %x4e20  ,               o  Shielded twisted pair (STP)  !               o  Ring speed of 16o  H               Example 4-3 Using the isacfg Command at the Console Prompt  E               >>> isacfg -slot 4 -etyp 1 -ena 1 -irq0 %xa -dmachan0 7 B                          -iobase0 %x4e20 -handle "DW11,STP,16" -mk  H               The -mk command makes an isacfg entry for an ISA device atG               slot 4. It is a single-port type of device (-etyp 1). ThemG               -handle parameter tells the operating system that this is F               a DW110, that STP media is to be used, and that the ring               speed is 16.  D               Example 4-4 Using the SYS$MANAGER:ISA_CONFIG.DAT Entry                    [IRA0]                   NODE=4                   NAME=IR$                  DRIVER=SYS$IRDRIVER                  IRQ=A                  DMA=7                  PORT=(4E20:20)a$                  USER_PARAM="STP,16"  G               For more information, see the OpenVMS Version 6.2 ReleaseS#               Notes, Appendix A. <>   I                                                   ProgrammingFeatures 4-7a                    ProgrammingFeaturesi$         4.3 LAT Programming Features    $         4.3 LAT Programming Features  F               Several LAT programming features are new for OpenVMS VAXD               Version 6.2, but they were introduced with OpenVMS AXP(               Version 6.1. They include:  A               o  LAT $QIO function modifier IO$M_LT_QUE_CHG_NOTIF   I               o  LAT SENSEMODE and SETMODE argument LAT$C_ENT_QUEUE_ENTRY   F               o  LAT SENSEMODE item codes for port node counters, nodeG                  counters, protocol errors, service counters subblocks,r1                  port entities, and queue entriesi  H               o  LAT SETMODE item codes for node entities, service type,                  and port type  H               For more information, see the OpenVMS I/O User's Reference               Manual.s  4         4.4 System Services Changes and Enhancements  F               This section contains information about new features for               system services.  0         4.4.1 Intrusion Database System Services  C               Table 4-5 describes the new OpenVMS Alpha Version 6.2 C               system services for accessing the intrusion database:   :               Table 4-5 Intrusion Database System Services  (               System Service    Function  D               $DELETE_          Searches for and deletes all recordsF               INTRUSION         in the intrusion database matching the7                                 caller's specifications   I               $SCAN_INTRUSION   Scans the intrusion database for suspects D                                 or intruders during a login attempt,A                                 audits login failures and updatesyC                                 records, or adds new records to thei2                                 intrusion database  I                                                  (continued on next page)            4-8 ProgrammingFeatures            I                                                       ProgrammingFeatures I                              4.4 System Services Changes and Enhancementsr    B               Table 4-5 (Cont.) Intrusion Database System Services  (               System Service    Function  D               $SHOW_INTRUSION   Searches for and returns informationG                                 about records in the intrusion databaseeD                                 matching the caller's specifications  G               For details about these services, see the OpenVMS VersionaI               6.1 OpenVMS System Services Reference Manual. (These system =               services are already available on OpenVMS VAX.)   ,         4.4.2 Proxy Database System Services  C               Table 4-6 describes the new OpenVMS Alpha Version 6.2 ?               system services for accessing the proxy database:   6               Table 4-6 Proxy Database System Services                 System$               Service       Function  G               $ADD_PROXY    Adds a new proxy to or modifies an existing 7                             proxy in the proxy databases  E               $DELETE_      Deletes an existing proxy, or removes thenI               PROXY         default user or a local user from an existingn7                             proxy in the proxy databaseC  A               $DISPLAY_     Returns information about one or moree,               PROXY         existing proxies  F               $VERIFY_      Verifies that a proxy exists and returns aE               PROXY         valid local user for the caller to use toi0                             create a local login  G               For details about these services, see the OpenVMS VersionEI               6.1 OpenVMS System Services Reference Manual. (These systemr=               services are already available on OpenVMS VAX.)             I                                                   ProgrammingFeatures 4-9y    g               ProgrammingFeaturesr4         4.4 System Services Changes and Enhancements    8         4.4.3 Cluster Event Notification System Services  H               Table 4-7 describes the new OpenVMS VAX Version 6.2 systemC               services for detection of cluster membership changes:   B               Table 4-7 Cluster Event Notification System Services                 System$               Service       Function  E               $CLRCLUEVT    Removes one or more notification requestst?                             previously established by a call tof&                             $SETCLUEVT  I               $SETCLUEVT    Establishes a request for notification when a A                             VMScluster configuration event occursg  A               $TSTCLUEVT    Simulates the occurrence of a cluster I                             configuration event to test the functionalityO3                             of the notification AST   G               For details about these services, see the OpenVMS VersionnI               6.1 OpenVMS System Services Reference Manual. (These systemL?               services are already available on OpenVMS Alpha.)   %         4.4.4 Persona System Services   G               In the past, a privileged server had to explicitly verifyTE               that a client's access to an OpenVMS object was allowedLE               by the site-defined security policy. The server processcF               used privileges to access the OpenVMS objects, then usedF               $CHCKPRO or $CHECK_ACCESS to determine a client's accessH               rights to an object. The following three problems resulted!               from this approach:   B               o  It was difficult to duplicate the security checks9                  performed by the base system components.e  I               o  Superfluous security auditing messages resulted from thevE                  server's privileged access to the host system files.   H               o  The performance of the server was adversely affected byA                  having to perform secondary protection checking.   H               The persona system services allow programmers to eliminateH               the extraneous audits and the cost of secondary protectionE               checks, and to determine access with the normal OpenVMS                access tests.             4-10 ProgrammingFeatures e         I                                                       ProgrammingFeatures I                              4.4 System Services Changes and Enhancements     C               The three new services are $PERSONA_ASSUME, $PERSONA_n*               CREATE, and $PERSONA_DELETE.           4.4.4.1 $PERSONA_ASSUMEe  E               The $PERSONA_ASSUME system service modifies the contextiD               of the current process to match the context of a givenG               persona. This service allows an OpenVMS process to assume E               the identity of another user or to discard a persona to 7               return the process to its original state.c                 Format  1               SYS$PERSONA_ASSUME persona, [flags]-                 Argumentsc                 personae  #               OpenVMS       integer /               usage:        longword (unsigned)e                Type:         read(               Access:       by reference               Mechanism:  B               Address of a longword in which the persona handle is               expected.   G               If the value of the context passed is 1, then the current G               persona is discarded and the state of the calling process F               is returned to the state that existed prior to the first&               call to $PERSONA_CREATE.                 flagse  )               OpenVMS       mask_longword /               usage:        longword (unsigned)t%               Type:         read onlys$               Access:       by value               Mechanism:  H               Flag mask specifying which persona services options are toG               be employed when the persona is assumed. This argument ism8               ignored when a persona is being discarded.  I                                                  ProgrammingFeatures 4-11t n  l               ProgrammingFeatures 4         4.4 System Services Changes and Enhancements    6               The following table describes each flag:  I               ___________________________________________________________ /               Flag                  DescriptionS  .I               IMP$M_ASSUME_         Assume access rights, UIC, authorizedEG               SECURITY              privileges, user name, and securityD.                                     audit flag  :               IMP$M_ASSUME_ACCOUNT  Assume OpenVMS account  E               IMP$M_ASSUME_JOB_     Assume the new persona, even in a 4               WIDE                  multiprocess job                 Descriptiona  E               When assuming a persona using the IMP$M_ASSUME_SECURITYfB               option, any previously enabled image privileges willB               be disabled. The caller's process will have only the@               privileges of the impersonated user enabled. TheseA               privileges are enabled in the Current, Process, andy)               Authorized privilege masks.F  I               When using IMP$M_ASSUME_SECURITY, access to the job logicallE               name table may no longer be possible since the table is B               protected by the UIC of the user on whose behalf theD               current process was created. Also, a new access to theI               process' controlling terminal may fail, and the process may D               be in a different default resource domain for locking.  E               Any persona is automatically discarded and deleted upon I               image exit. Hence, it is not possible to permanently change =               the persona of a process using $PERSONA_ASSUME.   D               The arguments are read in caller's mode, so an invalidD               argument may cause an access violation to be signaled.  +               Required Access or Privilegess                 None.p                 Required Quota                 None.m                 Related Services  .               $PERSONA_CREATE, $PERSONA_DELETE            4-12 ProgrammingFeatures           I                                                       ProgrammingFeatures I                              4.4 System Services Changes and Enhancements     '               Condition Values Returned   I               SS$_NORMAL              The service completed successfully.   I               IMP$_NOCHJIB            The Job Information Block cannot be /                                       modified.   ?               IMP$_PERSONANONGRATA    Invalid persona argument.n           4.4.4.2 $PERSONA_CREATE   G               The $PERSONA_CREATE system service creates a persona that ?               may be assumed using the $PERSONA_ASSUME service.n                 Format  7               SYS$PERSONA_CREATE persona, usrnam, flagss                 Arguments                  personar  #               OpenVMS       integer /               usage:        longword (unsigned)t!               Type:         write (               Access:       by reference               Mechanism:  D               Address of a longword into which the persona handle is               written.                 usrnam  '               OpenVMS       char_stringm7               usage:        character coded text stringa%               Type:         read only C               Access:       by descriptor (fixed-length descriptor)                Mechanism:  2               Name of the user to be impersonated.  I               The usrnam argument is the address of a descriptor pointing H               to a character string containing the user name. The stringB               may contain a maximum of 12 alphanumeric characters.                 flagsi  I                                                  ProgrammingFeatures 4-13s A  i               ProgrammingFeatures 4         4.4 System Services Changes and Enhancements      )               OpenVMS       mask_longword /               usage:        longword (unsigned)7%               Type:         read only $               Access:       by value               Mechanism:  H               Flag mask specifying which persona services options are to6               be employed when the persona is created.  6               The following table describes each flag:  I               ___________________________________________________________ /               Flag                  Descriptionn  F               IMP$M_ASSUME_DEFPRIV  Create a persona with only default.                                     privileges  A               IMP$M_ASSUME_         Create a persona with default 2               DEFCLASS              classification                 Description   I               On calling the $PERSONA_CREATE system service, the required F               information concerning the OpenVMS user specified by theF               usrnam argument is read from the user authorization fileD               and rights database, and is stored in system memory. AG               handle to refer to the created persona is returned in the                persona argument.   I               It is not possible to create a persona for a user name that%                has been disabled.  H               No changes are made to the caller's process as a result of&               calling $PERSONA_CREATE.  A               Some of the $PERSONA_CREATE service executes in thehF               caller's access mode (assumed to be user mode). ImproperI               use of the usrnam argument may cause an access violation toi               be signaled.  +               Required Access or Privilegest  G               All calls to $PERSONA_CREATE require DETACH privilege and :               access to the system authorization database.                 Required Quota                 None.D                 Related Services  .               $PERSONA_ASSUME, $PERSONA_DELETE            4-14 ProgrammingFeatures           I                                                       ProgrammingFeatures I                              4.4 System Services Changes and Enhancements     '               Condition Values Returned   G               SS$_NORMAL            The service completed successfully.   B               SS$_ACCVIO            The persona argument cannot be:                                     written by the caller.  H               SS$_NODETACH          Operation requires DETACH privilege.  8               SS$_INSFMEM           Insufficient memory.  7               IMP$_USERDISABLED     User name disabled.i  I               Any condition value returned by $LKWSET, $GETUAI, or $FIND_p(               HELD may also be returned.           4.4.4.3 $PERSONA_DELETE4  B               The $PERSONA_DELETE system service deletes a persona8               created using the $PERSONA_CREATE service.                 Format  (               SYS$PERSONA_DELETE persona                 Argumentsa                 persona   #               OpenVMS       integere/               usage:        longword (unsigned)e                Type:         read(               Access:       by reference               Mechanism:  B               Address of a longword in which the persona handle is               expected.e                 Description   I               The $PERSONA_DELETE service frees the resources used by the G               persona. No changes to the caller's process are made as a 0               result of calling $PERSONA_DELETE.  +               Required Access or Privilegesa                 None.e                 Required Quota                 None.                  Related Services  .               $PERSONA_ASSUME, $PERSONA_CREATE  I                                                  ProgrammingFeatures 4-15  I  =             ProgrammingFeaturesQ4         4.4 System Services Changes and Enhancements  '               Condition Values Returned"  G               SS$_NORMAL            The service completed successfully.S  C               SS$_INUSE             Persona is in use; it cannot be ,                                     deleted.  4         4.5 OpenVMS Alpha Support for SCSI-2 Devices  G               On Alpha systems, OpenVMS now supports the tagged command B               queuing functionality of the SCSI-2 standard. TaggedI               command queuing allows a SCSI class driver to pass multiple C               queued I/O requests directly to a port driver withoutnC               waiting for any one I/O request to complete. The portdG               driver then sends each I/O request directly to the targetEE               SCSI device, where the device queues the request on itso-               internal command device queues.   I               Tagged command queuing functionality increases overall diskEH               I/O performance. Because a device knows which I/O requestsD               are in progress, it can optimize the order in which itI               handles the requests based on its own hardware capabilities E               (dynamic positioning and latency schedules, and spindlee               configuration).y  F               The OpenVMS Alpha implementation includes tagged commandI               queuing support only on DISK class devices on the SCSI port )               drivers shown in Table 4-8.s  D               Table 4-8 OpenVMS Alpha Tagged Command Queuing Support                 PortA               Driver      Adapter          Adapter Classificationh  @               PKCDRIVER   NCR 53C94        DEC 3000 Alpha familyB                                            supporting TURBOchannel  @               PKTDRIVER   NCR 53C710       DEC 4000 Alpha familyD                                            supporting Futurebus/Plus  ?               PKEDRIVER   NCR 53C810       Digital Alpha family 9                                            supporting PCI   F               PKSDRIVER   KZTSA            SIMport TURBOchannel add-on2                                            adapter  E                           KZPSA            SIMport PCI add-on adaptern  I               PKQDRIVER   KZPBA, P1SE,     Qlogic PCI SCSI add-on adapter                            P2SE            4-16 ProgrammingFeatures s  a      I                                                       ProgrammingFeaturessI                              4.5 OpenVMS Alpha Support for SCSI-2 DevicesS      F               OpenVMS Alpha continues to support nonqueuing operationsG               for SCSI magnetic tapes, class drivers, and the following                 SCSI port drivers:  1               o  PKJDRIVER - Adaptec 1742A (EISA)e  (               o  PKZDRIVER - KZMSA (XMI)  
         <>  "         4.6 C++ RTL Object Library  F               With OpenVMS Version 6.2, the C++ RTL object modules areI               available in SYS$LIBRARY:STARLET.OLB. Most C++ programs can-H               include these object modules directly by linking /NOSYSSHRH               in their link commands. C++ programs that include the TaskG               class must explicitly include the CMA shared library when ?               they link /NOSYSSHR, as in the following example:m  0               $ LINK/NOSYSSHR foo,SYS$INPUT:/OPT)               SYS$SHARE:CMA$LIB_SHR/SHARE                ^Z  A               For more information, see the DEC C++ Class Librarye               Reference Manual.n  2         4.7 New Linker Option RMS_RELATED_CONTEXT=  F               This option enables or disables RMS related name contextD               processing within the linker option file. This is alsoD               known as file specification stickiness. The default isB               to have RMS related name context processing enabled.D               This default applies at the start of each options fileC               regardless of the setting in a previous options file. E               The related name context itself (the collection of data B               structures RMS maintains to supply the most recently  I                                                  ProgrammingFeatures 4-17                     ProgrammingFeatures 2         4.7 New Linker Option RMS_RELATED_CONTEXT=    C               specified fields) does not carry over from one linkeraH               options file to the next (that is, specified fields in theI               previous options file are not used to fill in absent fields C               for file specifications in the current options file).m  '               The format is as follows:   (               RMS_RELATED_CONTEXT=YES/NO                 Option Values:                 o  YES  E                  Enables RMS related name context processing startingTD                  with the context previously saved by a RMS_RELATED_@                  CONTEXT=NO command. If RMS related name contextB                  processing is already enabled, this option has no                  effect.                 o  NOr  C                  Disables RMS related name context processing. WhentE                  RMS related name context processing is disabled, the D                  current context is saved for a possible future RMS_H                  RELATED_CONTEXT=YES option. If RMS related name contextH                  processing is already disabled, specifying RMS_RELATED_*                  CONTEXT=NO has no effect.  H               When RMS related name processing is enabled (by default atF               the beginning of each options file), file specificationsC               that do not have all fields of the file specificationMD               present will have the missing fields replaced with theE               corresponding fields most recently specified in earliergD               file specifications. When disabled, fields in the fileA               specification that are absent are not replaced with C               corresponding fields of previous file specifications. G               When RMS related name processing is disabled, the current B               related name context is saved. When RMS related nameF               processing is enabled via this option, the saved related'               name context is restored.p  H               For more information about linker options, see the OpenVMS$               Linker Utility Manual.              4-18 ProgrammingFeatures d                       I                                                                         5 I         _________________________________________________________________   I                                         DEC C XPG4 Localization Utilities     G               OpenVMS Version 6.2 provides XPG4-compliant utilities for C               managing localization data for international software D               applications or layered products. Localization data isH               defined separately from the application and is bound to it               only at run time.o  F                 ________________________ Note ________________________  F                 The addition of the DEC C XPG4 code to OpenVMS Version@                 6.2 means that developers who link their code onB                 OpenVMS VAX Version 6.2 will not be able to run it+                 on OpenVMS VAX Version 6.1.   F                 ______________________________________________________  H               The following localization utilities are described in this               chapter:                 o  GENCATr                 o  ICONV COMPILE                 o  ICONV CONVERT                 o  LOCALE COMPILEs                 o  LOCALE LOAD                 o  LOCALE UNLOAD  2               o  LOCALE SHOW CHARACTER_DEFINITIONS  $               o  LOCALE SHOW CURRENT  #               o  LOCALE SHOW PUBLICr  "               o  LOCALE SHOW VALUE  :               These utilities are provided only on CD-ROM.  I                                     DEC C XPG4 Localization Utilities 5-1g           )         DEC C XPG4 Localization Utilities       ?               Because these utilities support the XPG4 model ofnG               internationalization, they are only useful for localizing >               applications written to that model. See the userF               documentation for each application or layered product to;               see if it supports XPG4 internationalization.m  H               This chapter also describes the locale file format and the7               character set description (charmap) file.            5.1 GENCAT  G               The GENCAT command merges one or more message text source_0               files into a message catalog file.           5.1.1 Format  *               GENCAT msgfile[,...] catfile           5.1.1.1 Parameters                 msgfileY  G               The file specification of a message text source file. The H               default file type for a message text source file is .MSGX.                 catfile   E               The file specification of the message catalog file that E               is created. If catfile already exists, a new version is I               created that includes the messages in the existing catalog. ?               The file type for a message catalog file is .CAT.            5.1.1.2 Qualifiers                 None.v           5.1.2 Descriptionv  F               The GENCAT command creates new message catalogs from oneE               or more input source files and an existing catalog fileiC               (if there is one). A message catalog is a binary filesG               containing the messages for an application. This includessE               all messages that the application issues, such as errorhB               messages, screen displays, and prompts. ApplicationsI               retrieve messages from a message catalog using the catopen, H               catgets, and catclose C run-time library routines. See theI               DEC C Run-Time Library Reference Manual for OpenVMS Systemsl,               for details of these routines.  -         5-2 DEC C XPG4 Localization Utilities     h      I                                         DEC C XPG4 Localization Utilities I                                                                5.1 GENCATc    G               A message text source file is a text file that you createsG               to hold messages printed by your program. You can use any F               text editor to enter messages into the text source file.E               Messages can be grouped into sets, usually to represent D               functional subsets of your program. Each message has aF               numeric identifier, which must be unique within its set.D               The message text source file can also contain commandsG               recognized by GENCAT for manipulating sets and individual                messages.   G               If a message catalog with the name catfile exists, GENCAT A               creates a new version of the file that includes thenD               contents of the older version and then modifies it. IfI               the catalog does not exist, GENCAT creates the catalog withe               the name catfile.E  F               You can specify any number of message text source files.D               The GENCAT command processes multiple source files oneI               after the other in the sequence that you specify them. Eacho:               successive source file modifies the catalog.  =               The catfile can contain the following commands:   $                  message_number text  G                  Inserts text as a message with the identifier message_m1                  number. Follow these guidelines:   B                  o  Numbers must be ascending within each set. YouF                     can skip a number, but you cannot go back to add aI                     missing number or replace an existing number during as#                     GENCAT session.   I                  o  If the message text is empty and a space or tab field F                     separator is present, an empty string is stored in(                     the message catalog.  E                  o  If a message source line has a message number but C                     neither a field separator nor message text, theaI                     existing message with that number (if any) is deleted %                     from the catalog.r  #                  $delset set_numberd  E                  Deletes the set of messages indicated by set_number.s  !                  $quote charactern  I                                     DEC C XPG4 Localization Utilities 5-3            )         DEC C XPG4 Localization Utilities.         5.1 GENCAT    H                  Sets the quote character to character. See the Examples.                  section for more information.                     $set set_number  G                  Indicates that all messages entered after this commanduC                  are placed in the set indicated by set_number. YouME                  can change the set by entering another $set command.AI                  However, set numbers must be entered in ascending order; F                  you cannot go back to a lower numbered set during theH                  GENCAT session. If the command is not used, the default!                  set number is 1.e  F               Each initial keyword or number must be followed by whiteI               space. The GENCAT utility ignores any line that begins withiH               a space, a tab, or a dollar sign ($) character followed byH               a space, a tab, or a newline character. Therefore, you canD               use these sequences to start comments in your catfile.B               Blank lines are also ignored. Finally, you can placeE               comments on the same line after the $delset, $quote, or H               $set commands because GENCAT ignores anything that follows               these commands.t  A               A line beginning with a digit marks a message to be D               included in the catalog. You can specify any amount ofG               white space between the message ID number and the messagehF               text; however, when the message text is not delimited byI               quotation marks, one space or tab character is recommended.AH               When message text is not in quotation marks, GENCAT treatsI               additional white space as part of the message. When message A               text is enclosed in quotation marks, GENCAT ignoresnE               all spaces or tabs between the message ID and the first "               quotation character.  F               Escape sequences like those recognized by the C languageI               can be used in text. The escape character (\), a backslash,eE               can be used to insert special characters in the messagev"               text. See Table 5-1.              -         5-4 DEC C XPG4 Localization UtilitiesB           I                                         DEC C XPG4 Localization UtilitiesEI                                                                5.1 GENCAT.    *               Table 5-1 Special Characters                 Escape#               Sequence    Charactere  "               \n          New Line  (               \t          Horizontal Tab  &               \v          Vertical Tab  #               \b          Backspace   )               \r          Carriage Return   #               \f          Form Feed   B               \\          Backslash Character (\). Use to continue=                           message text on the following line.n  G               \ddd        The single-byte character associated with the G                           octal value ddd. You can specify one, two, oreG                           three octal digits. However, you must includerG                           leading zeros if the characters following the C                           octal digits are also valid octal digits; D                           for example, the octal value for $ (dollarF                           sign) is 44. To insert $5.00 into a message,G                           use \0445.00, not \445.00; otherwise the 5 is <                           parsed as part of the octal value.  G                 ________________________ Notes ________________________e  ?                 GENCAT conforms to X/Open specifications. In ancF                 X/Open conforming application, the set numbers must beC                 integers in the range of 1 to NL_SETMAX, inclusive;.B                 message numbers must be integers in the range of 1D                 to NL_MSGMAX, inclusive. NL_SETMAX and NL_MSGMAX areE                 defined in the <limits.h> header file that comes with C                 DEC C and DEC C++. For OpenVMS Version 6.2, each ofu&                 these limits is 65535.  B                 The value of LC_CTYPE from the LOCALE SHOW CURRENTE                 command determines the interpretation of message text 7                 in the message source files msgfile....c  F                 ______________________________________________________  I                                     DEC C XPG4 Localization Utilities 5-5s           )         DEC C XPG4 Localization Utilities          5.1 GENCAT             5.1.3 Errors  E               When GENCAT reports an error, no action is taken on anyuA               commands and an existing catalog is left unchanged.c           5.1.4 Examples                 1.  5                  $set 10 Communication Error Messagesp  G                  This example uses the $set command in a source file tou<                  assign a set number to a group of messages.  E                  The message set number is 10. All messages after the A                  $set command and up to the next $set command are B                  assigned a message set number of 10. (Set numbersF                  must be assigned in ascending order but they need notF                  be contiguous.) You can include a comment in the $set                  command.4                 2.  8                  $delset 10 Communication Error Messages  G                  This example uses the $delset command to remove from a H                  catalog all messages belonging to the specified message(                  set (10, in this case).  E                  The $delset command must be placed in the proper set F                  number order with respect to any $set commands in theC                  same source file. You can include a comment in thep!                  $delset command.E                 3.  "                  12 "file removed"  E                  This example shows how to enter the message text and B                  assign a message ID number to it. In this case, aF                  message ID of 12 is assigned to the text that follows                  it.  C                  You must leave at least one space or tab character G                  between the message ID number and the message text butAF                  you can include more spaces or tabs if you prefer. IfE                  you do include more spaces or tabs, they are ignoredhI                  when the message text is in quotation marks and they areTI                  considered part of the text when the message text is notr$                  in quotation marks.  -         5-6 DEC C XPG4 Localization Utilitiesl           I                                         DEC C XPG4 Localization Utilities I                                                                5.1 GENCAT     D                  Message numbers must be in ascending order within aD                  single message set but they need not be contiguous.  D                  All text following the message number and up to theD                  end of the line is included as message text. If youI                  place the escape character (\), a backslash, as the lasttI                  character on the line, the message text continues on thef@                  following line. Consider the following example:  3                  This is the text associated with \s"                  message number 5.  B                  The two lines in the example define the following%                  single-line message:e  C                  This is the text associated with message number 5.s                 4.  F                  $quote "   Use a double quote to delimit message textM                  $set 10            Message Facility - Quote command messages B                  1 "Use the $quote command to define a character \3                  \n for delimiting message text" \n M                  2 "You can include the \"quote\" character in a message \n \ ?                  by placing a \\ (backslash) in front of it" \n J                  3 You can include the "quote" character in a message \n \D                  by having another character as the first nonspace \<                  \n character after the message ID number \n                  $quoteE>                  4 You can disable the quote mechanism by \n \B                  using the $quote command without \n a character \                  after it \n  D                  This example shows the effect of a quote character.  G                  The $quote command defines the double quote (") as the G                  quote character. The quote character must be the first F                  nonspace character after the message number. Any textH                  following the next occurrence of the quote character is                  ignored.S  F                  This example also shows two ways to include the quote/                  character in the message text:   >                  o  Place a \ in front of the quote character.  I                  o  Use another character as the first nonspace character E                     after the message number. This disables the quotef4                     character for that message only.  I                                     DEC C XPG4 Localization Utilities 5-7  l  m      )         DEC C XPG4 Localization Utilities          5.1 GENCAT    7                  This example also shows the following:o  C                  o  A \ is still required to split a quoted messagei!                     across lines.s  I                  o  To display a \ in a message, you must place another \ #                     in front of it.   I                  o  You can format your message with a new-line charactert                      by using \n.  C                  o  If you use the $quote command with no charactero>                     argument, you disable the quote mechanism.           5.2 ICONV COMPILEo  G               The ICONV COMPILE command creates a conversion table file I               from a conversion source file. The conversion table file is_H               used by the ICONV CONVERT command to convert characters in1               a file from one codeset to another.            5.2.1 Format  0               ICONV COMPILE sourcefile tablefile           5.2.1.1 Parameters                 sourcefile  G               The file specification of the conversion source file. ThetD               default file type is .ISRC. The file naming convention:               Digital uses for conversion source files is:  (               fromcodeset_tocodeset.isrc                 tablefile   G               The file specification of the conversion table file to be G               created. The default file type is .ICONV. The file naming 7               convention for conversion table files is:   )               fromcodeset_tocodeset.iconv   I               You must follow this convention for naming conversion tablehD               files for the ICONV CONVERT command to recognize them.  H               Public conversion table files are in the directory definedD               by the logical name SYS$I18N_ICONV. Put new conversionH               table files in the same directory if you want to make them#               available systemwide.T  -         5-8 DEC C XPG4 Localization Utilities            I                                         DEC C XPG4 Localization Utilities I                                                         5.2 ICONV COMPILE              5.2.1.2 Qualifier   !               /LISTING[=listfile]   D               Directs ICONV COMPILE to produce a listing file, whichE               contains the source file listing and any error messages G               generated during compilation. If the file name is omittedtB               from the qualifier, the default listing file name is               sourcefile.LIS.            5.2.2 Descriptionr  G               The ICONV commands support any 1- to 4-byte codesets that H               are state independent. They do not support state-dependent               codesets.   F                 ________________________ Note ________________________  =                 There is an implementation restriction in the ?                 tocodeset encodings in this implementation. Thee@                 characters in tocodeset must not use 0XFF in the                 fourth byte.  F                 ______________________________________________________  ?               The conversion source file contains the character 9               conversion rules for a specific conversion.i  G               The format of a codeset conversion source file is definedn               as follows:   '       <fromcodeset_mb_cur_max>    valuec'       <fromcodeset_mb_cur_min>    value '       <tocodeset_mb_cur_max>      value '       <tocodeset_mb_cur_min>      valuee'       <fallback_code>             value '       <escape_char>               values'       <comment_char>              valuemO       <fromcodeset_range>         value...value;value...value;...;value...valueo       ICONV_TABLEl/       fromvalue                         tovaluee/       fromvalue                         tovalue ,          .                                 .,          .                                 .,          .                                 ./       fromvalue                         tovaluel       END ICONV_TABLE   I                                     DEC C XPG4 Localization Utilities 5-9            )         DEC C XPG4 Localization Utilitiesn         5.2 ICONV COMPILE     E               where the <...> symbols and their associated values aretG               codeset declarations, and the fromvalue/tovalue pairs arec)               character conversion rules.   "               Codeset Declarations  A               The codeset declarations must precede the charactertF               conversion rules. Each declaration consists of a symbol,@               starting in column 1 and including the surroundingH               brackets, followed by one or more blanks (tabs or spaces),E               followed by the value to be assigned to the symbol. Seep               Table 5-2.  ,               Table 5-2 Codeset Declarations  )               Symbol                Valuee  D               <fromcodeset_mb_cur_  The maximum number of bytes in aF               max>                  character in the fromcodeset. This8                                     value defaults to 1.  D               <fromcodeset_mb_cur_  The minimum number of bytes in aF               min>                  character in the fromcodeset. ThisG                                     value must be less than or equal tosI                                     fromcodeset_mb_cur_max. If this valueaH                                     is not specified, it defaults to theD                                     value of fromcodeset_mb_cur_max.  D               <tocodeset_mb_cur_    The maximum number of bytes in aD               max>                  character in the tocodeset. This8                                     value defaults to 1.  D               <tocodeset_mb_cur_    The minimum number of bytes in aD               min>                  character in the tocodeset. ThisG                                     value must be less than or equal touG                                     tocodeset_mb_cur_max. If this value H                                     is not specified, it defaults to theB                                     value of tocodeset_mb_cur_max.  I                                                  (continued on next page)o          .         5-10 DEC C XPG4 Localization Utilities    h      I                                         DEC C XPG4 Localization UtilitiesnI                                                         5.2 ICONV COMPILE     4               Table 5-2 (Cont.) Codeset Declarations  )               Symbol                Valuer  H               <fallback_code>       The tovalues for the fromvalues thatI                                     appear in the <fromcodeset_range> but$I                                     are not specified between ICONV_TABLEtG                                     and END ICONV_TABLE. Specify one ofe:                                     three kinds of values:  I                                     o  SAME - specifies that the tovaluesnF                                        are the same as the fromvalues.  A                                     o  ERROR - specifies that theaD                                        conversion from the fromvalueE                                        to a tovalue is not supported.HE                                        ICONV CONVERT issues a warning I                                        and ignores the rest of the recordGG                                        read. The DEC C run-time librarysC                                        routine iconv returns to the I                                        caller with an "illegal character"i-                                        error.t  A                                     o  User-defined tovalue - the,F                                        fromvalues are converted to theF                                        specified user-defined tovalue.  C                                        The user-defined tovalue can F                                        represent a multibyte characterE                                        with the restriction that 0xffmE                                        cannot be used as the value inoD                                        the fourth byte. The settingsD                                        for user-defined tovalues forC                                        <fallback_code> are the sameeD                                        as the settings for characterF                                        conversion rule values. You canI                                        use octal, decimal, or hexadecimalsE                                        digits. If the <fallback_code>GG                                        is not specified, it defaults ton,                                        SAME.  I                                                  (continued on next page)       I                                    DEC C XPG4 Localization Utilities 5-11            )         DEC C XPG4 Localization Utilitiese         5.2 ICONV COMPILE     4               Table 5-2 (Cont.) Codeset Declarations  )               Symbol                Value   I               <escape_char>         The escape character used to indicate B                                     that subsequent characters areA                                     interpreted in a special way. D                                     The escape character defaults to2                                     backslash (\).  F               <comment_char>        The character that, when placed inF                                     column 1 of a line, indicates thatI                                     the line will be ignored. The defaulttH                                     comment character is the number sign(                                     (#).  D               <fromokcodeset_       The fromcodeset encoding ranges.C               range>                Specify this declaration if the G                                     fromcodeset is a multibyte codeset.nE                                     If the fromcodeset is omitted, itaE                                     defaults to a single-byte codesetxB                                     and the table created by ICONVI                                     COMPILE will support only single-byte4<                                     fromcodeset conversions.  =               When specifying codeset encoding ranges for the_I               fromcodeset, every zone of characters must be specified. IfcH               any zones of characters are missing from the <fromcodeset_C               range> specification, the codeset conversion might behD               incorrect. It is very important to specify the codesetF               encoding ranges correctly for the fromcodesets supportedI               by the rest of the DEC C run-time library (RTL). If this ishI               not done, the codeset support for iconv and the rest of theV/               DEC C RTL will not be consistent.i  I               For example, the fromcodeset ranges for EUCJP are specifiedC               as:   ?            <fromcodeset_range>  \x0...\x7f;\x8e\xa1...\x8e\xfe; O                                 \xa1\xa1...\xfe\xfe;\x8f\xa1\xa1...\x8f\xfe\xfe_  I               The settings for <fromcodeset_range> values are the same as H               the settings for character conversion rule values. You can7               use octal, decimal or hexadecimal digits.   .         5-12 DEC C XPG4 Localization Utilities e  r      I                                         DEC C XPG4 Localization UtilitieseI                                                         5.2 ICONV COMPILE     (               Character Conversion Rules  F               The character conversion rules are all the lines betweenH               the string ICONV_TABLE starting in column 1 and END ICONV_)               TABLE starting in column 1.s  @               Character conversion rules must begin in column 1.  D               Empty lines and lines containing a comment_char in the>               first column are ignored. Comments are optional.  C               Character conversion rules can have one of two forms:a  1               fromvalue                   tovalue   1               fromvalue...fromvalue       tovaluec  I               Place one or more blanks (tabs or spaces) between fromvalued               and tovalue.  ?               Use the first format to define a single-character +               conversion rule. For example:                  \d32       \d101               \d37       \d106  B               Use the second format to define a range of characterI               conversion rules. In this format, the ending fromvalue must E               be equal to or greater than the starting fromvalue. The I               subsequent fromvalues defined by the range are converted tom+               tovalues in increasing order.e  7               For example, consider the following line:s  4               \d223\d32...\d223\d35       \d129\d254  *               This line is interpreted as:  (               \d223\d32       \d129\d254(               \d223\d33       \d129\d255&               \d223\d34       \d130\d0&               \d223\d35       \d130\d1  4               For settings of fromvalue and tovalue:  D               o  A decimal constant is defined as one, two, or threeD                  decimal digits preceded by the escape character and0                  lowercase d. For example: \d42.  I               o  An octal constant is defined as one, two, or three octaltF                  digits preceded by the escape character. For example:                  \141.  I                                    DEC C XPG4 Localization Utilities 5-13            )         DEC C XPG4 Localization Utilitiesn         5.2 ICONV COMPILE     @               o  A hexadecimal constant is defined as one or twoD                  hexadecimal digits preceded by the escape character6                  and a lowercase x. For example: \x6a.  C               Each constant represents a single-byte value. You cantE               represent multibyte values by concatenating two or morei7               decimal, octal, or hexadecimal constants.h  F                 ________________________ Note ________________________  E                 When constants are concatenated for multibyte values,i>                 they must have the same radix (decimal, octal,@                 or hexadecimal). Only characters in the PortableA                 Character Set can be used to construct conversion                  source files.e  F                 ______________________________________________________  1               Also see the ICONV CONVERT command.c           5.2.3 Errors  I               If an error is encountered during processing, ICONV COMPILE D               does not generate an output tablefile. If a warning isB               encountered, a valid table file is created. However,E               because a warning can indicate a user error, you should 2               check the returned warning messages.  F               Some ICONV COMPILE error messages and their descriptions               follow.t  P               %ICONV-E-INVFCSRNG, syntax error in <fromcodeset_range> definition  H               This error occurs when the definition of the <fromcodeset_H               range> symbol does not conform to the required syntax. TheG               <fromcodeset_range> symbol defines encoding ranges and is .               required for multibyte codesets.  5               %ICONV-E-INVSYNTAX, invalid file syntax   B               This error occurs when a line in the source does not-               conform to the required syntax.s  G               %ICONV-E-BADTABLE, bad table caused by invalid value for o,               <fromcodeset_range> definition  B               This error occurs when an invalid value is specifiedF               for the codeset encoding ranges. The encoding ranges are8               defined by the <fromcodeset_range> symbol.  .         5-14 DEC C XPG4 Localization Utilities           I                                         DEC C XPG4 Localization Utilities I                                                         5.2 ICONV COMPILEc             5.2.4 Example   @               $ ICONV COMPILE/LISTING EUCTW_DECHANYU.ISRC EUCTW_         DECHANYU.ICONV  F               This example shows how to create a conversion table fileG               to convert the EUCTW codeset to the DECHANYU codeset. ThemE               listing file, EUCTW_DECHANYU.LIS, contains a listing of E               the source file and any error messages generated by the                compiler..           5.3 ICONV CONVERTu  @               The ICONV CONVERT command converts characters in aE               file from one codeset to another codeset. The converted 7               characters are written to an output file.i           5.3.1 Format  *               ICONV CONVERT infile outfile           5.3.1.1 Parameters                 infile  B               The file specification of the file that contains theA               characters to be converted. The /FROMCODE qualifierNC               specifies the codeset of the characters in this file.                  outfile   A               The file specification of the file created by ICONV E               CONVERT. The /TOCODE qualifier specifies the codeset of *               the characters in this file.           5.3.1.2 Qualifiers  #               /FROMCODE=fromcodeset   D               A required qualifier that specifies the codeset of the2               characters in the input file infile.                 /TOCODE=tocodesetm  D               A required qualifier that specifies the codeset of the4               characters in the output file outfile.  I                                    DEC C XPG4 Localization Utilities 5-15i           )         DEC C XPG4 Localization Utilities          5.3 ICONV CONVERTo             5.3.2 Descriptiono  I               The ICONV CONVERT command converts the characters in infileiD               from the codeset identified by the /FROMCODE qualifierE               to the codeset identified by the /TOCODE qualifier. TheL3               converted file is written to outfile.   8               The conversion is done in one of two ways:  G               o  Using a conversion table file to look up the converted G                  characters. This is the default method. The conversion 1                  table file naming convention is:i  ,                  fromcodeset_tocodeset.iconv  G                  ICONV CONVERT searches your current directory for thisiI                  file. If it cannot find the file, it searches the system F                  directory defined by the logical name SYS$I18N_ICONV.B                  You can create a conversion table using the ICONV!                  COMPILE command.   ?                  Note that if you add conversion tables to your G                  system, they must use the same file naming convention._F                  Otherwise, the ICONV CONVERT will not recognize them.  H               o  Using an algorithm. This is implemented as a conversionH                  function that is built into the DEC C run-time library.D                  If there is an algorithm available for the specificA                  conversion, ICONV CONVERT uses it instead of theuD                  conversion table. You cannot use this method to add3                  codeset converters to your system.   G               The ICONV commands support any 1- to 4-byte codesets that H               are state independent. They do not support state-dependent               codesets.t           5.3.3 Example   N         $ ICONV CONVERT/FROMCODE=EUCTW/TOCODE=DECHANYU FROMFILE.DAT TOFILE.DAT  F               This example shows a conversion from EUCTW characters toC               DECHANYU characters. The EUCTW characters in the fileaF               FROMFILE.DAT are converted to the corresponding DECHANYUI               characters. The converted characters are stored in the file                TOFILE.DAT.   .         5-16 DEC C XPG4 Localization Utilities    .      I                                         DEC C XPG4 Localization Utilities I                                                        5.4 LOCALE COMPILE              5.4 LOCALE COMPILE  F               The LOCALE COMPILE command converts a locale source fileG               into a binary locale file. The binary locale file is used I               by those utilities and C routines that are dependent on theuE               setting of the international environment logical names.            5.4.1 Format  '               LOCALE COMPILE sourcefilet           5.4.1.1 Parametere                 sourcefile  I               The file specification of the locale source file. This fileuH               defines each category of the locale. The default file typeE               for the source file is .LSRC. For the definition of the :               locale source file format, see Section 5.11.           5.4.1.2 Qualifiers  -               /CHARACTER_DEFINITIONS=filename 1               /NOCHARACTER_DEFINITIONS  (default)_  F               Specifies a character-set description file (charmap) forC               the locale. This file maps characters to their actual D               character encodings. If a charmap is not specified, noE               symbolic names (other than collating symbols defined innC               a collating symbol keyword) are allowed in the localetE               source file. For definition of the charmap file format,eF               see Section 5.12. The default file type for a charmap is               .CMAP.  !               /DISPLAY[=[NO]HOLE]   H               Used with certain Chinese locales and terminals to specifyC               that 4-byte characters occupy four printing positions D               (columns) on the terminal display. The default value (F               /DISPLAY=NOHOLE) specifies that 4-byte characters occupy%               two printing positions.                  /IGNORE=WARNINGS!               /NOIGNORE (default)   D               Generates an output file even if LOCALE COMPILE issuesB               warning messages. Use the /IGNORE keyword cautiouslyF               because the warnings could indicate user errors that youE               might want to correct before using the resulting locale                file.   I                                    DEC C XPG4 Localization Utilities 5-17C G  o      )         DEC C XPG4 Localization Utilities          5.4 LOCALE COMPILE    3               /LISTING [=filename]  (batch default) /               /NOLISTING  (interactive default)   I               Specifies the name of the listing file. The /SHOW qualifieryG               controls the information included in the listing file. IfaF               the file name is omitted, the default is sourcefile.LIS.                  /OUTPUT=[filename]               /NOOUTPUT   C               Specifies the name of the output file. If the /OUTPUT C               qualifier is omitted, the default output file name is A               sourcefile.LOCALE. Public locales are stored in the D               directory defined by the logical name SYS$I18N_LOCALE.H               If the output file is in any other location, the locale is               private.  H               If /NOOUTPUT is specified, the compiler does not create anA               output file, even if the compilation is successful.u  %               /SHOW[=(keyword[,...])]   F               Use /SHOW together with /LIST to control the informationI               included in the listing file. You can specify the following                keywords:e  I               ___________________________________________________________v*               Keyword          Description  7               ALL              Include all information.   E               BRIEF            Include a summary of the symbol table.   @               [NO]CHARACTER_   Include or omit the charmap file.               DEFINITIONSe  G               NONE             Do not print any information. If NONE isaH                                specified, the listing file only contains<                                the error messages generated.  F               [NO]SOURCE       Include or omit a listing of the source$                                file.  C               [NO]STATISTICS   Include or omit compiler performance +                                information.   G               [NO]SYMBOLS      Include or omit a listing of the charmap ,                                symbol table.  I               [NO]TERMINAL     Display compiler messages at the terminal.a  5               The default is /SHOW=(SOURCE,TERMINAL).   .         5-18 DEC C XPG4 Localization Utilities           I                                         DEC C XPG4 Localization UtilitiesgI                                                        5.4 LOCALE COMPILE              5.4.2 Description   G               Use the LOCALE COMPILE command to add new locales to your I               system in addition to those supplied by Digital. To compile :               a locale, LOCALE COMPILE requires two files:  F               o  A charmap file that defines the character set for theG                  locale. If you do not specify a charmap file, symbolic E                  names cannot be specified in the locale source file.hC                  If this happens, LOCALE COMPILE issues an error or F                  warning message, depending on the category processed,F                  and no output file is produced. (Also see the /IGNORE                  qualifier.)  A               o  A locale source file. This file describes one orcE                  more of the locale categories: LC_CTYPE, LC_COLLATE, C                  LC_MESSAGES, LC_MONETARY, LC_NUMERIC, and LC_TIME.            5.4.3 Errors  G               Some LOCALE COMPILE error messages and their descriptionso               follow.n  Q               %LOCALE-E-CASEALRDY, case conversion already exists for 'character'   E               Where `character` is a character from the codeset. This H               error can occur when the locale compiler is processing theE               LC_CTYPE category. It indicates that more than one case 6               conversion is specified for `character`.  H               %LOCALE-E-PREOFCMAP, premature end of file in charmap file  G               This error occurs if there is no END CHARMAP statement in                the charmap file.g  G               %LOCALE-E-PREEOFSRC, premature end of file in source file   A               This error occurs if there is an error with the END 3               statements in the locale source file.p  F               %LOCALE-F-NOADDSYM, failed to add symbol to symbol table  D               This error can occur when there is insufficient memoryC               to finish the compilation. Check the amount of memoryt(               available to your process.  I                                    DEC C XPG4 Localization Utilities 5-19C r  t      )         DEC C XPG4 Localization Utilities          5.4 LOCALE COMPILE      D               %LOCALE-F-NOINITSYM, failed to initialize symbol table  F               This error may be caused if there is insufficient memoryC               to finish the compilation. Check the amount of memoryx(               available to your process.           5.4.4 Example.  9               $ LOCALE COMPILE EN_GB_ISO8859-1/CHARACTER_e         DEFINITIONS=ISO8859-1 -lC               /LIST/SHOW=(CHARACTER_DEFINITIONS,SYMBOLS,STATISTICS)s  H               This example shows how to generate a locale file named EN_E               GB_ISO8859-1.LOCALE from the source file EN_GB_ISO8859- H               1.LSRC, using the charmap file ISO8859-1.CMAP. To use thisG               locale file, copy it to the SYS$I18N_LOCALE directory andLI               set the LANG logical to "EN_GB.ISO8859-1". The listing filecG               contains a listing of the charmap file, the symbol table,IG               performance information, and any error messages generatedi               by the compiler.           5.5 LOCALE LOADs  C               This command loads the specified locale name into thei?               system's memory as shared, read-only global data.            5.5.1 Format                 LOCALE LOAD name           5.5.1.1 Parameterf                 name  I               A character string that identifies the locale to be loaded. /               This can be one of the following:   .               o  The name of the public locale  H                  Specifies the public locale. The format of the name is:  4                  language_country.codeset[@modifier]  G                  LOCALE LOAD searches for the public locale binary file F                  in the location defined by the logical name SYS$I18N_F                  LOCALE. The file type defaults to .LOCALE. The periodF                  (.) and at-sign (@)  characters in the name specified;                  are replaced by underscore (_) characters.e  .         5-20 DEC C XPG4 Localization Utilities e         I                                         DEC C XPG4 Localization Utilities3I                                                           5.5 LOCALE LOAD:    6                  For example, if the name specified isG                  "zh_CN.dechanzi@radical", LOCALE LOAD searches for the .                  following binary locale file:  >                  SYS$I18N_LOCALE:ZH_CN_DECHANZI_RADICAL.LOCALE  %               o  A file specificationt  H                  Specifies the binary locale file. This can be any validF                  file specification. If either the device or directoryH                  is not specified, LOCALE LOAD first applies the currentG                  caller's device and directory as defaults. If the file4F                  is not found, the device and directory defined by theG                  SYS$I18N_LOCALE logical name are used as defaults. The /                  file type defaults to .LOCALE.d  I                  Wildcards are not allowed. The binary locale file cannot )                  reside on a remote node.            5.5.1.2 Qualifiers                 None.            5.5.2 Descriptionn  C               This command loads the specified locale name into theuA               system's memory as several shared, read-only globalhH               sections. All processes that access the loaded locale thenG               use this one copy of the locale, thereby reducing overall &               demand on system memory.  D               LOCALE LOAD is a privileged OpenVMS command, typicallyH               issued by the system manager. The following privileges are               required:n                 o  SYSGBLo                 o  PRMGBL            5.6 LOCALE UNLOAD_  E               This command unloads the specified locale name from thec               system's memory.           5.6.1 Format                  LOCALE UNLOAD name  I                                    DEC C XPG4 Localization Utilities 5-21  n         )         DEC C XPG4 Localization Utilities          5.6 LOCALE UNLOAD              5.6.1.1 Parametern                 name  A               A character string that identifies the locale to be B               unloaded. See the LOCALE LOAD command for acceptable)               formats for this parameter.O           5.6.1.2 Qualifiers                 None.e           5.6.2 Descriptions  E               This command unloads the specified locale name from thegH               system's memory. If a process is accessing the locale whenD               the UNLOAD command is entered, the global sections are>               deleted after the process deaccesses the locale.  F               LOCALE UNLOAD is a privileged OpenVMS command, typicallyH               issued by the system manager. The following privileges are               required:D                 o  SYSGBLi                 o  PRMGBL   F                 ________________________ Note ________________________  C                 Only locale files loaded by the LOCALE LOAD commandg                  can be unloaded.  F                 ______________________________________________________  -         5.7 LOCALE SHOW CHARACTER_DEFINITIONS   @               This command lists character set description files               (charmaps).            5.7.1 Format  /               LOCALE SHOW CHARACTER_DEFINITIONSm           5.7.1.1 Parameters                 None.E  .         5-22 DEC C XPG4 Localization Utilities           I                                         DEC C XPG4 Localization UtilitieseI                                     5.7 LOCALE SHOW CHARACTER_DEFINITIONSi             5.7.1.2 Qualifiers                 None.            5.7.2 Description   H               This command lists all the character set description filesG               (charmaps) in the public directory defined by the logicalrH               name SYS$I18N_LOCALE. A charmap defines the symbolic namesI               and values of characters in a coded character set. Charmaps.E               are used by the LOCALE COMPILE command when compiling a.=               locale. A charmap file has the file type .CMAP.e           5.7.3 Examplee  1               $ LOCALE SHOW CHARACTER_DEFINITIONSn/               [SYS$I18N.LOCALES.SYSTEM]DECHANYUp/               [SYS$I18N.LOCALES.SYSTEM]DECHANZIe/               [SYS$I18N.LOCALES.SYSTEM]DECKANJI 0               [SYS$I18N.LOCALES.SYSTEM]DECKOREAN,               [SYS$I18N.LOCALES.SYSTEM]EUCJP,               [SYS$I18N.LOCALES.SYSTEM]EUCTW0               [SYS$I18N.LOCALES.SYSTEM]ISO8859-10               [SYS$I18N.LOCALES.SYSTEM]ISO8859-20               [SYS$I18N.LOCALES.SYSTEM]ISO8859-30               [SYS$I18N.LOCALES.SYSTEM]ISO8859-40               [SYS$I18N.LOCALES.SYSTEM]ISO8859-50               [SYS$I18N.LOCALES.SYSTEM]ISO8859-70               [SYS$I18N.LOCALES.SYSTEM]ISO8859-80               [SYS$I18N.LOCALES.SYSTEM]ISO8859-91               [SYS$I18N.LOCALES.SYSTEM]MITACTELEX50               [SYS$I18N.LOCALES.SYSTEM]SDECKANJI+               [SYS$I18N.LOCALES.SYSTEM]SJIS   G               This example shows a system with several charmap files inr,               the SYS$I18N_LOCALE directory.           5.8 LOCALE SHOW CURRENTR  <               This command displays a summary of the current=               international environment as defined by severale6               international environment logical names.      I                                    DEC C XPG4 Localization Utilities 5-23h o  r      )         DEC C XPG4 Localization Utilitiesf         5.8 LOCALE SHOW CURRENT              5.8.1 Format  #               LOCALE SHOW [CURRENT]            5.8.1.1 Parameters                 None.V           5.8.1.2 Qualifiers                 None.            5.8.2 Descriptionn  I               The LOCALE SHOW CURRENT command lists the settings for eachdI               locale category and the values of the environment variablesvE               LC_ALL and LANG. The CURRENT keyword is the default and F               is, therefore, optional. The logical name that defines aF               category has the same name as the category. For example,F               the LC_MESSAGES logical name defines the setting for the>               LC_MESSAGES category. The locale categories are:  I               ___________________________________________________________ *               Category         Description  E               LC_COLLATE       Information about collating sequences.   D               LC_CTYPE         Character classification information.  H               LC_MESSAGES      Information about the language of programI                                messages and the format of yes/no prompts.   ?               LC_MONETARY      Monetary formatting information.t  D               LC_NUMERIC       Information about formatting numbers.  9               LC_TIME          Time and date information.T  G               Each locale category is defined by scanning the following G               logical names in the order shown, until a logical name is I               found. If the logical name found does not represent a valid G               locale file, then LOCALE SHOW displays the string "C" for !               all the categories.6                 1. LC_ALLi  H               2. Logical names corresponding to the categories specifiedI                  in the table (for example, if LC_NUMERIC is specified as I                  a valid locale category, the LOCALE SHOW CURRENT commandOI                  displays the name of the category and the locale name itn                  defines).                 3. LANG   .         5-24 DEC C XPG4 Localization Utilities d  n      I                                         DEC C XPG4 Localization UtilitiessI                                                   5.8 LOCALE SHOW CURRENT                    4. SYS$LC_ALL   @               5. The system default for the locale categories asG                  specified by the SYS$* logical names. For example, thelF                  default for the category LC_NUMERIC is defined by the-                  SYS$LC_NUMERIC logical name.a                 6. SYS$LANGc  D               The system manager can choose to define SYS$* logicalsB               in the site-specific system startup files to set theD               default locale. If no definition is provided, programsF               operate using the built-in "C" locale, in which case theI               LOCALE SHOW CURRENT command displays the string "C" for the (               current locale categories.           5.8.3 Examplei  0               $ DEFINE LC_COLLATE EN_US.ISO8859-2         1 ! NOTE: the collate category in unquoted+               $ DEFINE LANG EN_GB_ISO8859-1                $ DEFINE LC_:         MESSAGES PRIVATE$DISK:[APPL.LOCALES]SPECIAL.LOCALE#               $ LOCALE SHOW CURRENT $               LANG="EN_GB_ISO8859-1"(               LC_CTYPE="EN_GB_ISO8859-1"(               LC_COLLATE=EN_US_ISO8859-1'               LC_TIME="EN_GB_ISO8859-1"c*               LC_NUMERIC="EN_GB_ISO8859-1"+               LC_MONETARY="EN_GB_ISO8859-1"iE               LC_MESSAGES=PRIVATE$DISK:[APPL.LOCALES]SPECIAL.LOCALE;1s               LC_ALL=N  F               This example shows a process where all locale categoriesE               except LC_COLLATE and LC_MESSAGES have defaulted to theeH               same locale, EN_GB.ISO8859-1. A setting enclosed in doubleI               quotes indicates that the setting is implied by the settingcB               of one of the following logical names: LANG, LC_ALL,G               SYS$LC_ALL, or SYS$LANG. A setting not enclosed by double F               quotes indicates that the logical name for that categoryF               defines the international environment. This example alsoH               shows that if a locale category is specified by a completeI               file specification, then the complete file specification ise               displayed.  I                                    DEC C XPG4 Localization Utilities 5-25s c  l      )         DEC C XPG4 Localization Utilities          5.8 LOCALE SHOW CURRENT              5.8.4 Errors  B               If any logical names that define the environment areH               improperly defined, no warning message is issued. However,G               the actual international environment is listed exactly asnI               it would be seen by an application that uses the DEC C run-tE               time library routine setlocale (for instance, if in theTF               previous example the SPECIAL.LOCALE file does not exist,F               then the display for the LC_MESSAGES category would show               LC_MESSAGES="C").            5.9 LOCALE SHOW PUBLIC  F               This command lists all the public locales on the system.           5.9.1 Format                  LOCALE SHOW PUBLIC           5.9.1.1 Parameters                 None._           5.9.1.2 Qualifiers                 None.n           5.9.2 Description   F               This command lists all the public locales on the system.E               The set of public locales contains all the locales thateA               reside in the directory defined by the logical name F               SYS$I18N_LOCALE as well as the system's built-in locales7               supplied with the DEC C run-time library.o           5.9.3 Example   "               $ LOCALE SHOW PUBLIC                 C (Built-in)               POSIX (Built-in)6               [SYS$I18N.LOCALES.SYSTEM]EN_GB_ISO8859_16               [SYS$I18N.LOCALES.SYSTEM]EN_US_ISO8859_16               [SYS$I18N.LOCALES.SYSTEM]FR_CA_ISO8859_1.               [SYS$I18N.LOCALES.SYSTEM]GRBAGE_)         LOCALE (bad file header checksum) -               [SYS$I18N.LOCALES.SYSTEM]JA_JP_ %         DECKANJI (Permanently Loaded)e  .         5-26 DEC C XPG4 Localization Utilities    /      I                                         DEC C XPG4 Localization Utilities I                                                    5.9 LOCALE SHOW PUBLICl    D               This example shows a system with three locale files inH               the SYS$I18N_LOCALE directory. The C and POSIX locales areI               built in with the system and, therefore, cannot be found inn(               SYS$I18N_LOCALE directory.  H               This example also shows the effect of having a bad file orH               a nonlocale file in the public directory and the effect ofI               having a locale file loaded into the system's memory by the "               LOCALE LOAD command.           5.10 LOCALE SHOW VALUE  E               This command displays the value of one or more keywordsw9               from the current international environment.            5.10.1 Formatf  *               LOCALE SHOW VALUE name[,...]           5.10.1.1 Parameter                 name[,...]  A               The name of a keyword or category. If you specify alF               keyword, the value of that keyword in the current localeD               is displayed. If you specify a category, the values ofF               the keywords in that category are displayed. For integerC               keywords that have no value assigned, the value CHAR_nC               MAX (127) is displayed. When a keyword value includess@               semicolons, double quotes, backslashes, or controlB               characters, they are preceded by an escape character$               (usually a backslash).  I               Table 5-3 lists the categories and keywords you can specify                for name.,  0         Table 5-3 Locale Categories and Keywords  ?         Category      Keyword               Keyword Description   D         LC_CTYPE                            Character classification1                                             namesh  >         LC_TIME       DAY                   Full weekday names  E                       ABDAY                 Abbreviated weekday namesM  I                                                  (continued on next page)w  I                                    DEC C XPG4 Localization Utilities 5-27e t  a      )         DEC C XPG4 Localization Utilities          5.10 LOCALE SHOW VALUE    8         Table 5-3 (Cont.) Locale Categories and Keywords  ?         Category      Keyword               Keyword DescriptionA  <                       MON                   Full month names  C                       ABMON                 Abbreviated month namesr  @                       D_T_FMT               Date and time format  7                       D_FMT                 Date format   7                       T_FMT                 Time formatE  F                       T_FMT_AMPM            Time format in the 12-hour1                                             clockL  @                       AM_PM                 Defines how the anteD                                             meridiem (a.m.) and postG                                             meridiem (p.m.) strings areO7                                             represented   I                       ERA                   Defines how years are countedtG                                             and displayed for eras in ao2                                             locale  ;                       ERA_D_FMT             Era date format   D                       ERA_D_T_FMT           Era date and time format  ;                       ERA_T_FMT             Era time format   G                       ALT_DIGITS            String defining alternative >                                             symbols for digits  G         LC_NUMERIC    DECIMAL_POINT         Character used as a decimali5                                             delimiterb  C                       THOUSANDS_SEP         Character used to groupaE                                             digits to the left of thea=                                             decimal delimiter   I                       GROUPING              Defines how characters to the I                                             left of the decimal delimiter 7                                             are grouped   I         LC_MONETARY   INT_CURR_SYMBOL       Character string representingdF                                             the international currency2                                             symbol  D                       CURRENCY_SYMBOL       String used as the local;                                             currency symbol   I                                                  (continued on next page)   .         5-28 DEC C XPG4 Localization Utilities    D      I                                         DEC C XPG4 Localization Utilities I                                                    5.10 LOCALE SHOW VALUEl    8         Table 5-3 (Cont.) Locale Categories and Keywords  ?         Category      Keyword               Keyword Description.  G                       MON_DECIMAL_POINT     Character used as a decimalLE                                             delimiter when formattingd?                                             monetary quantities,  I                       MON_THOUSANDS_SEP     Character used as a separatorgG                                             for groups of digits to the I                                             left of the decimal delimiterl  D                       POSITIVE_SIGN         String used to representH                                             positive monetary quantities  D                       NEGATIVE_SIGN         String used to representH                                             negative monetary quantities  F                       INT_FRAC_DIGITS       Number of digits displayedG                                             to the right of the decimal E                                             delimiter when formattingeI                                             monetary quantities using the I                                             international currency symbolS  F                       FRAC_DIGITS           Number of digits displayedG                                             to the right of the decimal E                                             delimiter when formattingUI                                             monetary quantities using theiA                                             local currency symbole  I                       P_CS_PRECEDES         For positive monetary values, I                                             this is set to 1 if the local H                                             currency symbol precedes theF                                             number and 0 if the symbol>                                             follows the number  I                       N_CS_PRECEDES         For negative monetary values,yI                                             this is set to 1 if the local H                                             currency symbol precedes theF                                             number and 0 if the symbol>                                             follows the number  I                                                  (continued on next page)D    I                                    DEC C XPG4 Localization Utilities 5-29_ _  _      )         DEC C XPG4 Localization Utilities          5.10 LOCALE SHOW VALUE    8         Table 5-3 (Cont.) Locale Categories and Keywords  ?         Category      Keyword               Keyword Description_  I                       P_SEP_BY_SPACE        For positive monetary values, H                                             this is set to 0 if there isI                                             no space between the currencyIF                                             symbol and the value, 1 ifF                                             there is a space, and 2 ifH                                             there is a space between theF                                             symbol and the sign string  I                       N_SEP_BY_SPACE        For negative monetary values, H                                             this is set to 0 if there isI                                             no space between the currency F                                             symbol and the value, 1 ifF                                             there is a space, and 2 ifH                                             there is a space between theF                                             symbol and the sign string  D                       P_SIGN_POSN           Integer used to indicateC                                             where the POSITIVE_SIGN8C                                             string should be placedC  D                       N_SIGN_POSN           Integer used to indicateC                                             where the NEGATIVE_SIGNMC                                             string should be placed   B                       MON_GROUPING          Defines how digits areC                                             grouped when formatting ;                                             monetary values   F         LC_MESSAGES   YESSTR                String representing YES in>                                             the current locale  I                       NOSTR                 String representing NO in theA:                                             current locale  F                       YESEXPR               Expression representing anG                                             affirmative response in theA:                                             current locale  E                       NOEXPR                Expression representing abD                                             negative response in the:                                             current locale  .         5-30 DEC C XPG4 Localization Utilities L  l      I                                         DEC C XPG4 Localization Utilities I                                                    5.10 LOCALE SHOW VALUE     F                 ________________________ Note ________________________  E                 When an environment variable that affects the settingiB                 of the current locale points to an invalid locale,+                 then the "C" locale is set.   F                 ______________________________________________________  G               Other valid keywords that are not displayed by default asa+               part of any category include:   I               o  CHARMAP - displays the file specification of the charmapt2                  used when the locale was created.  H               o  CODE_SET_NAME - defines the name of the coded character;                  set for which the charmap file is defined.   F               o  MB_CUR_MAX - defines the maximum number of bytes in a%                  multibyte character.t  F               o  MB_CUR_MIN - defines the minimum number of bytes in a6                  character in the coded character set.           5.10.1.2 Qualifierst                 /CATEGORY   @               Displays the category name before each keyword. IfB               /CATEGORY is not specified, the category name is not               displayed.                 /KEYWORD  F               Displays the keyword name before the value of a keyword.G               If /KEYWORD is not specified, the value of the keyword is *               displayed, but not its name.           5.10.2 Errorsr  ?               %LOCALE-E-NOKEYFND, no keyword keyword-name founds  G               The keyword-name is not a valid keyword. Specify only the.+               keywords listed in Table 5-3.r           5.10.3 Description  E               This command displays the value of one or more keywordse9               from the current international environment.O  I                                    DEC C XPG4 Localization Utilities 5-31y d  e      )         DEC C XPG4 Localization Utilities          5.10 LOCALE SHOW VALUE             5.10.4 ExamplesU                 1.  +                  $ LOCALE SHOW VALUE NOEXPR $                  "^[nN][[:alpha:]]*"  F                  Issuing LOCALE SHOW VALUE without qualifiers displays0                  the value of the NOEXPR string.                 2.  4                  $ LOCALE SHOW VALUE/CATEGORY NOEXPR                  LC_MESSAGES$                  "^[nN][[:alpha:]]*"  E                  Specifying /CATEGORY displays the category name (LC__A                  MESSAGES) before the value of the NOEXPR string.                  3.  3                  $ LOCALE SHOW VALUE/KEYWORD NOEXPRt,                  noexpr= "^[nN][[:alpha:]]*"  I                  Specifying /KEYWORD displays the keyword name before its                   value.h                 4.  <                  $ LOCALE SHOW VALUE/KEYWORD/CATEGORY NOEXPR                  LC_MESSAGES,                  noexpr= "^[nN][[:alpha:]]*"  H                  Specifying /KEYWORD and /CATEGORY displays the category;                  and keyword name before the keyword value.                     .         5-32 DEC C XPG4 Localization Utilities    E      I                                         DEC C XPG4 Localization UtilitiesRI                                                   5.11 Locale File FormatS             5.11 Locale File Format_  B               A locale definition source file contains one or moreI               categories that describe a locale. You can convert a locale F               definition source file into a locale by using the LOCALEF               COMPILE command. Locales can be modified only by editingG               a locale definition source file and then using the LOCALE G               COMPILE command again on the new source file. Each localetF               source file section defines a category of locale data. AF               source file cannot contain more than one section for the               same category.            5.11.1 Locale Categories  E               The following standard locale categories are supported:o  C               o  LC_COLLATE - Defines character or string collationn                  information  B               o  LC_CTYPE - Defines character classification, case;                  conversion, and other character attributess  E               o  LC_MESSAGES - Defines the format for affirmative and #                  negative responsesi  G               o  LC_MONETARY - Defines rules and symbols for formatting -                  monetary numeric informationo  E               o  LC_NUMERIC - Defines a list of rules and symbols for ;                  formatting nonmonetary numeric informationd  B               o  LC_TIME - Defines a list of rules and symbols for5                  formatting time and date informationp  $         5.11.1.1 Overriding Defaults  G               You can include optional declarations at the beginning of I               your locale source file to override the default comment and D               escape characters used in locale category definitions:  !               o  Escape character   G                  The escape character is used in decimal or hexadecimaleF                  constants when they are specified in the locale file.F                  The default escape character is the backslash (\). ToI                  define another escape character, include a line with the "                  following format:  +                  escape_char  <char_symbol>   "               o  Comment character  I                                    DEC C XPG4 Localization Utilities 5-33c n         )         DEC C XPG4 Localization Utilitiess         5.11 Locale File Format     D                  The comment character is the first character of anyH                  comment entries in the locale file. The default commentD                  character is the number sign (#). To define another=                  comment character, use the following format:9  ,                  comment_char  <char_symbol>  H               In the preceding formats, <char_symbol> is the character'sH               symbolic name as defined in the charmap file used to buildH               the locale's codeset. One or more blank characters (spacesE               or tabs) must separate escape_char or comment_char from                <char_symbol>.  ,         5.11.1.2 Category Source Definitions  H               Each category source definition consists of the following:  4               o  The category header (category_name)  H               o  The associated keyword or value pairs that comprise the                  category body  9               o  The category trailer (END category_name)                  For example:                 LC_CTYPE,               <source for LC_CTYPE category>               END LC_CTYPE  E               The source for all of the categories is specified usingeB               keywords, strings, character literals, and characterE               symbols. Each keyword identifies either a definition orfC               a rule. The remainder of the statement containing theeH               keyword contains the operands to the keyword. Operands areH               separated from the keyword by one or more blank charactersH               (spaces or tabs). A statement may be continued on the nextC               line by placing a backslash (\) as the last character E               before the new-line character that terminates the line. E               Lines containing the comment character (#) in the first 2               column are treated as comment lines.  @               A symbolic name begins with the left angle-bracketA               character (<) and ends with the right angle-bracketrG               character (>). The characters between the < and the > cantG               be any characters from the Portable Character Set, except D               for the control and space characters. For example, <A-F               diaeresis> could be a symbolic name for a character. AnyH               symbolic name referenced in the locale source file must be  .         5-34 DEC C XPG4 Localization Utilities           I                                         DEC C XPG4 Localization Utilities I                                                   5.11 Locale File Formatr    H               defined via the Portable Character Set or in the character=               set description (charmap) file for that locale.C  H               A character literal is the character itself, or a decimal,I               hexadecimal, or octal constant. A decimal constant containsCE               two or three decimal digits and has the following form, +               where n is any decimal digit:                  \dnn or \dnnn   H               A hexadecimal constant contains two hexadecimal digits andG               has the following form, where n is any hexadecimal digit:m                 \xnn  F               An octal constant contains two or three octal digits andA               has the following form, where n is any octal digit:M                 \nn or \nnne  B               The explicit definition of each category in a localeE               definition source file is not required. When a category I               is undefined in a locale definition source file, the LOCALE D               COMPILE command will not store any data value for this4               category in the resulting locale file.  &         5.11.2 The LC_COLLATE Category  H               The LC_COLLATE category defines the relative order betweenG               collation items. This category begins with the LC_COLLATEe>               header and ends with the END LC_COLLATE trailer.  G               A collation item is the unit of comparison for collation. B               A collation item may be a character or a sequence ofF               characters. Every collation item in the locale has a setH               of weights, which determine if the collation item collatesI               before, equal to, or after the other collation items in the G               locale. Each collation item is assigned collation weightsAF               by the LOCALE COMPILE command when the locale definitionG               source file is compiled. These collation weights are then A               used by applications programs that compare strings.   G               String comparison is performed by comparing the collation D               weights of each character in the string until either aE               difference is found or the strings are determined to be F               equal. This comparison may be performed several times ifH               the locale defines multiple collation orders. For example,D               in the French locale, the strings are compared using aH               primary set of collation weights. If they are equal on the  I                                    DEC C XPG4 Localization Utilities 5-35e           )         DEC C XPG4 Localization Utilities          5.11 Locale File Format     E               basis of this comparison, they are compared again using D               a secondary set of collation weights. A collation itemG               has a set of collation weights associated with it that isrI               equal to the number of collation sort rules defined for theO               locale.a  C               Every character defined in the charmap file (or everynC               character in the Portable Character Set if no charmapaG               file is specified) is itself a collation item. Additional H               collation items can be defined using the collating-element;               statement (see the description that follows).t  F               Table 5-4 lists the statement keywords recognized in the"               LC_COLLATE category.  4               Table 5-4 LC_COLLATE Category Keywords  -               Keyword             Description   C               copy                Specifies the name of an existing E                                   locale to be used as the definition I                                   of this category. If you specify a copy E                                   statement, you need not specify any B                                   other keywords in this category.  D               collating-element   Specifies multicharacter collation(                                   items.  H               collating-symbol    Specifies collation symbols for use in@                                   collation sequence statements.  F               order_start         Specifies collation order statementsB                                   that assign collation weights to2                                   collation items.  F               The collating-element, collating-symbol, and order_startI               statements are further described in the following sections.   0         5.11.2.1 The collating-element Statement  F               The collating-element statement specifies multicharacter               collation items.                 Syntax:   @               collating-element <character_symbol> from <string>  .         5-36 DEC C XPG4 Localization Utilities n  r      I                                         DEC C XPG4 Localization UtilitiesoI                                                   5.11 Locale File Formatt    I               The character_symbol argument defines a collation item that I               is a string of one or more characters as a single collation F               item. The character_symbol cannot duplicate any symbolicI               name in the current charmap file or any other symbolic name_3               defined in this collation definition.   C               The string argument specifies a string of two or moregG               characters that define the character_symbol argument. The E               following are examples of the syntax for the collating-e                element statement:  2               collating-element <ch> from "<c><h>";               collating-element <e-acute> from "<acute><e>"t2               collating-element <11> from "<1><1>"  C               A character_symbol argument defined by the collating- H               element statement is recognized only within the LC_COLLATE               category.e  /         5.11.2.2 The collating-symbol Statement   H               The collating-symbol statement specifies collation symbols7               for use in collation sequence statements.                  Syntax:s  1               collating-symbol <collating_symbol>   I               The collating_symbol argument cannot duplicate any symbolic I               name in the current charmap file or any other symbolic name E               defined in this collation definition. The following are 6               examples of collating-symbol statements:  +               collating-symbol <UPPER_CASE> %               collating-symbol <HIGH>P  F               An argument defined by the collating_symbol statement is=               recognized only within the LC_COLLATE category.   *         5.11.2.3 The order_start Statement  B               The order_start statement is followed by one or moreF               collation order statements that assign collation weightsF               to collation items and the order_end keyword. The order_6               start statement is a required statement.  I                                    DEC C XPG4 Localization Utilities 5-37            )         DEC C XPG4 Localization Utilitiese         5.11 Locale File FormatR                   Syntax:e  >               order_start sort_rules;sort_rules;...;sort_rules(               collation_order_statements               order_endr                 Sort Rules  B               The sort_rules directives have the following syntax:  *               keyword, keyword,...,keyword  >               where keyword is FORWARD, BACKWARD, or POSITION.  H               The sort_rules directives are optional. If specified, theyE               define the rules to apply during string comparison. ThetC               number of specified sort_rules directives defines the E               number of weights each collation item is assigned (that I               is, the directives define the number of collation orders in I               the locale). If no sort_rules directives are specified, one H               forward directive is assumed and comparisons are made on a9               character basis rather than a string basis._  I               If sort_rules directives are present, the first one applies E               when comparing strings that use the primary weight, the B               second when comparing strings that use the secondaryE               weight, and so on. Each set of sort_rules directives isiB               separated by a semicolon (;). A sort_rules directiveG               consists of one or more keywords separated by commas. Thee/               following keywords are supported:u  F                  FORWARD - Specifies that collation weight comparisonsI                  proceed from the beginning of a string to the end of them                  string.  G                  BACKWARD - Specifies that collation weight comparisons I                  proceed from the end of a string to the beginning of theh                  string.  G                  POSITION - Specifies that collation weight comparisons0F                  consider the relative position of nonignored elementsE                  in the string (that is, if strings compare as equal,tI                  the element with the shortest distance from the starting 9                  point of the comparison collates first).o  G               The forward and backward keywords are mutually exclusive.   .         5-38 DEC C XPG4 Localization Utilities t  t      I                                         DEC C XPG4 Localization UtilitiesoI                                                   5.11 Locale File Formatw    ;               Here is an example of a sort_rules directive:3  1               order_start        forward;backwards  (               Collation Order Statements  E               The following syntax rules apply to the collation order                statements:   I               o  Each collation order statement consists of a <character_4H                  symbol> specification followed by white space and a set%                  of collation orders.   B               o  Characters in the character set can be explicitly?                  specified in the collation order statements oraF                  implicitly specified using the ellipsis symbol (...).  A               o  A collation order statement that begins with theRB                  UNDEFINED special symbol specifies any charactersA                  that are in the character set but not explicitlyeA                  or implicitly specified by other collation ordert                  statements.  D               The optional operands for each collation item are usedE               to define the primary, secondary, or subsequent weightslG               for the collation item. The special symbol IGNORE is used E               to indicate a collation item that is to be ignored when #               strings are compared.   D               An ellipsis keyword appearing in place of a collating_D               element_list indicates the weights are to be assigned,H               for the characters in the identified range, in numericallyG               increasing order from the weight for the character symbol :               on the left side of the preceding statement.  F               The use of the ellipsis keyword results in a locale thatB               may collate differently when compiled with different?               character set description (charmap) source files.l  G               The UNDEFINED special symbol includes all coded character E               set values not specified explicitly or with an ellipsisnD               symbol. These characters are inserted in the characterE               collation order at the point indicated by the UNDEFINEDnB               special symbol and are all assigned the same weight.E               If no UNDEFINED special symbol exists and the collationtG               order does not specify all collation items from the coded B               character set, a warning is issued and all undefinedI               characters are placed at the end of the character collatione               order.  I                                    DEC C XPG4 Localization Utilities 5-39e h  c      )         DEC C XPG4 Localization Utilitiess         5.11 Locale File Formate                   ExampleE  H               The following is an example of a collation order statementE               section in the LC_COLLATE locale definition source filef               category:   .               order_start     forward;backward+               UNDEFINED       IGNORE;IGNOREn               <LOW> +               <space>         <LOW>;<space>o(               ...              <LOW>;...%               <a>             <a>;<a> +               <a-acute>       <a>;<a-acute>m+               <a-grave>       <a>;<a-grave>s%               <A>             <a>;<A>n+               <A-acute>       <a>;<A-acute> +               <A-grave>       <a>;<A-grave> '               <ch>            <ch>;<ch>e'               <Ch>            <ch>;<Ch>i%               <s>             <s>;<s>c+               <ss>            <s><s>;<s><s> 3               <eszet>         <s><s>;<eszet><eszet>c(               ...             <HIGH>;...               <HIGH>               order_end   5               This example is interpreted as follows:n  @               o  The UNDEFINED special symbol indicates that allC                  characters not specified in the definition (either F                  explicitly or by the ellipsis symbol) are ignored for$                  collation purposes.  E               o  All collation items between <space> and <a> have the.H                  same primary equivalence class and individual secondaryC                  weights based on their coded character-set values.e  G               o  All versions of the letter a (uppercase and lowercase,#E                  and with or without diacriticals) belong to the samew)                  primary collation class.a  H               o  The <c><h> multicharacter collation item is representedE                  by the <ch> collating symbol and belongs to the same G                  primary equivalence class as the <C><h> multicharacter                    collation item.  .         5-40 DEC C XPG4 Localization Utilities o         I                                         DEC C XPG4 Localization Utilities I                                                   5.11 Locale File Format     F               o  The <eszet> character is collated as an <s><s> stringC                  (that is, one <eszet> character is expanded to twoc.                  characters before comparing).  $         5.11.3 The LC_CTYPE Category  E               The LC_CTYPE category defines character classification,CC               case conversion, and other character attributes. ThiseD               category begins with the LC_CTYPE header and ends with'               the END LC_CTYPE trailer.t  G               All operands for LC_CTYPE category statements are defined B               as lists of characters. Each list consists of one orC               more characters or symbolic character names separatedsE               by semicolons. An ellipsis (...) can represent a seriesrD               of characters; for example, <a>;...;<z> represents the2               characters in the range a through z.  F               Table 5-5 lists the statement keywords recognized in theH               LC_CTYPE category. In the keyword descriptions, the phraseI               "automatically included" means that an error does not occur.C               if the referenced characters are included or omitted; F               the characters are provided if they are missing, and are+               accepted if they are present.e  2               Table 5-5 LC_CTYPE Category Keywords  "               Keyword  Description  E               copy     Specifies the name of an existing locale to be-@                        used as the definition for this category.  B                        If you specify a copy statement, you cannot1                        specify any other keyword.U  ;               upper    Defines uppercase letter characters.   I                        Do not specify any character defined by the cntrl, D                        digit, punct, or space keyword. The uppercaseH                        letters A through Z are automatically included in                         this set.  I                                                  (continued on next page)     I                                    DEC C XPG4 Localization Utilities 5-41     w      )         DEC C XPG4 Localization Utilitieso         5.11 Locale File Formaty    :               Table 5-5 (Cont.) LC_CTYPE Category Keywords  "               Keyword  Description  ;               lower    Defines lowercase letter characters.h  I                        Do not specify any character defined by the cntrl,tD                        digit, punct, or space keyword. The lowercaseH                        letters a through z are automatically included in                         this set.  5               alpha    Defines all letter characters.e  I                        Do not specify any character defined by the cntrl,fI                        digit, punct, or space keyword. Characters defined H                        by the upper and lower keywords are automatically8                        included in this character class.  8               digit    Defines numeric digit characters.  E                        Only the digits 0, 1, 2, 3, 4, 5, 6, 7, 8, andbE                        9 can be specified. The digits 0 through 9 areL:                        automatically included in this set.  6               space    Defines white-space characters.  I                        Do not specify any character defined by the upper, E                        lower, alpha, digit, graph, or xdigit keyword. G                        The space, form-feed, new-line, carriage-return, I                        tab, and vertical tab characters are automaticallya,                        included in this set.  2               cntrl    Defines control characters.  I                        Do not specify any character defined by the upper,aC                        lower, alpha, digit, punct, graph, print, orr&                        xdigit keyword.  6               punct    Defines punctuation characters.  @                        Do not specify the space character or anyD                        character defined by the upper, lower, alpha,8                        digit, cntrl, or xdigit keywords.  I                                                  (continued on next page)   .         5-42 DEC C XPG4 Localization Utilities o  r      I                                         DEC C XPG4 Localization UtilitiestI                                                   5.11 Locale File Format5    :               Table 5-5 (Cont.) LC_CTYPE Category Keywords  "               Keyword  Description  H               graph    Defines printable characters, excluding the space!                        character.i  H                        Do not specify any character defined by the cntrlD                        keyword. The characters defined by the upper,F                        lower, alpha, digit, xdigit, and punct keywordsC                        are automatically included in this character                         class.r  H               print    Defines printable characters, including the space!                        character.   B                        Do not specify any character defined by theH                        cntrl keyword. The space character and charactersI                        defined by the upper, lower, alpha, digit, xdigit,AG                        and punct keywords are automatically included in ,                        this character class.  <               xdigit   Defines hexadecimal digit characters.  G                        Only the digits 0, 1, 2, 3, 4, 5, 6, 7, 8, and 9oG                        can be specified. Any character, however, can becI                        specified for the hexadecimal values for 10 to 15. I                        These alternate hexadecimal digits are not used by I                        standard conversion routines when converting digit F                        strings from hexadecimal to numeric quantities.H                        The numbers 0 through 9 and the letters A throughF                        F and a through f are automatically included in                         this set.  0               blank    Defines blank characters.  B                        The space and horizontal tab characters areG                        included in this character class. Any characters B                        defined by this statement are automatically3                        included in the space class.   I                                                  (continued on next page)       I                                    DEC C XPG4 Localization Utilities 5-43l n  c      )         DEC C XPG4 Localization UtilitiesC         5.11 Locale File Formatn    :               Table 5-5 (Cont.) LC_CTYPE Category Keywords  "               Keyword  Description  E               toupper  Defines the mapping of lowercase characters to ,                        uppercase characters.  E                        Operands for this keyword consist of character H                        pairs separated by commas. Each character pair isH                        enclosed in parentheses () and separated from theH                        next pair by a semicolon (;). The first characterH                        in each pair is considered a lowercase character;F                        the second character is considered an uppercaseF                        character. Only characters defined by the lowerI                        and upper keywords can be specified. If toupper is>H                        not specified, a through z is mapped to A through$                        Z by default.  E               tolower  Defines the mapping of uppercase characters tot,                        lowercase characters.  E                        Operands for this keyword consist of character H                        pairs separated by commas. Each character pair isH                        enclosed in parentheses () and separated from theH                        next pair by a semicolon (;). The first characterI                        in each pair is considered an uppercase character;lE                        the second character is considered a lowercaserF                        character. Only characters defined by the lower;                        and upper keywords can be specified.x  H                        If tolower is not specified, the mapping defaultsE                        to the reverse mapping of the toupper keyword,aH                        if specified. If the toupper and tolower keywordsI                        are both omitted, the mapping for each defaults toa,                        that of the C locale.    .         5-44 DEC C XPG4 Localization Utilities l  o      I                                         DEC C XPG4 Localization UtilitiessI                                                   5.11 Locale File Formatr  I               Additional keywords can be provided to define new characteri+               classifications. For example:                  charclass vowel 2               vowel        <a>;<e>;<i>;<o>;<u>;<y>  C               The LC_CTYPE category does not support multicharactersB               elements (for example, the German Eszet character isA               traditionally classified as a lowercase letter). IniG               proper capitalization of German text, the Eszet charactero?               is replaced by the two characters SS; there is noOE               corresponding uppercase letter. This kind of conversiondG               is outside the scope of the toupper and tolower keywords.                                                                                       I                                    DEC C XPG4 Localization Utilities 5-45            )         DEC C XPG4 Localization Utilitiesi         5.11 Locale File Format     I               The following is an example of a possible LC_CTYPE categorys8               listed in a locale definition source file:                 LC_CTYPE8               #"alpha" is by default "upper" and "lower";               #"alnum" is by definition "alpha" and "digit"iM               #"print" is by default "alnum", "punct" and the space charactern8               #"graph" is by default "alnum" and "punct"G               #"tolower" is by default the reverse mapping of "toupper"y               # K               upper   <A>;<B>;<C>;<D>;<E>;<F>;<G>;<H>;<I>;<J>;<K>;<L>;<M>;\tI                       <N>;<O>;<P>;<Q>;<R>;<S>;<T>;<U>;<V>;<W>;<X>;<Y>;<Z>                #AK               lower   <a>;<b>;<c>;<d>;<e>;<f>;<g>;<h>;<i>;<j>;<k>;<l>;<m>;\oI                       <n>;<o>;<p>;<q>;<r>;<s>;<t>;<u>;<v>;<w>;<x>;<y>;<z>                #BF               digit   <zero>;<one>;<two>;<three>;<four>;<five>;<six>;\,                       <seven>;<eight>;<nine>               # B               space   <tab>;<newline>;<vertical-tab>;<form-feed>;\/                       <carriage-return>;<space>n               #eJ               cntrl   <alert>;<backspace>;<tab>;<newline>;<vertical-tab>;\G                       <form-feed>;<carriage-return>;<NUL>;<SOH>;<STX>;\eK                       <ETX>;<EOT>;<ENQ>;<ACK>;<SO>;<SI>;<DLE>;<DC1>;<DC2>;\aF                       <DC3>;<DC4>;<NAK>;<SYN>;<ETB>;<CAN>;<EM>;<SUB>;\9                       <ESC>;<IS4>;<IS3>;<IS2>;<IS1>;<DEL>i               # I               punct   <exclamation-mark>;<quotation-mark>;<number-sign>;\eK                       <dollar-sign>;<percent-sign>;<ampersand>;<asterisk>;\wK                       <apostrophe>;<left-parenthesis>;<right-parenthesis>;\ E                       <plus-sign>;<comma>;<hyphen>;<period>;<slash>;\rJ                       <colon>;<semicolon>;<less-than-sign>;<equals-sign>;\K                       <greater-than-sign>;<question-mark>;<commercial-at>;\rF                       <left-square-bracket>;<backslash>;<circumflex>;\I                       <right-square-bracket>;<underline>;<grave-accent>;\rD                       <left-curly-bracket>;<vertical-line>;<tilde>;\+                       <right-curly-bracket>l               #mF               xdigit  <zero>;<one>;<two>;<three>;<four>;<five>;<six>;\F                       <seven>;<eight>;<nine>;<A>;<B>;<C>;<D>;<E>;<F>;\-                       <a>;<b>;<c>;<d>;<e>;<f>o               #h#               blank   <space>;<tab>n  .         5-46 DEC C XPG4 Localization Utilities    o      I                                         DEC C XPG4 Localization Utilities I                                                   5.11 Locale File Format                    # I               toupper (<a>,<A>);(<b>,<B>);(<c>,<C>);(<d>,<D>);(<e>,<E>);\ I                       (<f>,<F>);(<g>,<G>);(<h>,<H>);(<i>,<I>);(<j>,<J>);\tI                       (<k>,<K>);(<l>,<L>);(<m>,<M>);(<n>,<N>);(<o>,<O>);\ I                       (<p>,<P>);(<q>,<Q>);(<r>,<R>);(<s>,<S>);(<t>,<T>);\ I                       (<u>,<U>);(<v>,<V>);(<w>,<W>);(<x>,<X>);(<y>,<Y>);\                        (<z>,<Z>)n               #n               END LC_CTYPE  '         5.11.4 The LC_MESSAGES Categorya  I               The LC_MESSAGES category defines the format for affirmative F               and negative system responses. This category begins withF               the LC_MESSAGES header and ends with the END LC_MESSAGES               trailer.  F               All operands for the LC_MESSAGES category are defined asG               strings or extended regular expressions bounded by doubleiD               quotation marks ("). These operands are separated fromE               the keyword they define by one or more blank characterseH               (spaces or tabs). Two adjacent double quotation marks ("")*               indicate an undefined value.  F               Table 5-6 lists the statement keywords recognized in the#               LC_MESSAGES category.e  5               Table 5-6 LC_MESSAGES Category Keywordsg  "               Keyword  Description  E               copy     Specifies the name of an existing locale to be ?                        used as the definition of this category.o  B                        If you specify a copy statement, you cannot1                        specify any other keyword.   D               yesexpr  Specifies an extended regular expression thatG                        describes the acceptable affirmative response toaF                        a question expecting an affirmative or negative                         response.  I                                                  (continued on next page)     I                                    DEC C XPG4 Localization Utilities 5-47            )         DEC C XPG4 Localization Utilitiese         5.11 Locale File Format     =               Table 5-6 (Cont.) LC_MESSAGES Category Keywordsa  "               Keyword  Description  D               noexpr   Specifies an extended regular expression thatF                        describes the acceptable negative response to aD                        question expecting an affirmative or negative                         response.  I               yesstr   Specifies the locale's equivalent of an acceptable.,                        affirmative response.  H                        This string is accessible to applications through@                        the nl_langinfo subroutine as nl_langinfoA                        (YESSTR). Note that yesstr is likely to be G                        withdrawn from the XPG4 standard; yesexpr is the /                        recommended alternative.c  I               nostr    Specifies the locale's equivalent of an acceptabler)                        negative response.y  H                        This string is accessible to applications throughI                        the nl_langinfo subroutine as nl_langinfo (NOSTR). E                        Note that nostr is likely to be withdrawn from C                        the XPG4 standard; noexpr is the recommended #                        alternative.e  C               The following is an example of a possible LC_MESSAGESeA               category listed in a locale definition source file:l                 LC_MESSAGES                # ?               yesexpr "<circumflex><left-square-bracket><y><Y>\ %               <right-square-bracket>"E?               noexpr  "<circumflex><left-square-bracket><n><N>\ %               <right-square-bracket>"a!               yesstr  "<y><e><s>">               nostr   "<n><o>"               #                END LC_MESSAGES>  '         5.11.5 The LC_MONETARY Category   D               The LC_MONETARY category defines rules and symbols forD               formatting monetary numeric information. This categoryA               begins with the LC_MONETARY header and ends with ane&               END LC_MONETARY trailer.  .         5-48 DEC C XPG4 Localization Utilities           I                                         DEC C XPG4 Localization UtilitieseI                                                   5.11 Locale File Formato    %         5.11.5.1 LC_MONETARY Keywordss  D               All operands for the LC_MONETARY category keywords areD               defined as string or integer values. String values areC               bounded by double quotation marks ("). All values areaI               separated from the keyword they define by one or more blankcH               characters (spaces or tabs). Two adjacent double quotationG               marks ("") indicate an undefined string value. A negativer<               one (-1) indicates an undefined integer value.  F               Table 5-7 lists the statement keywords recognized in the#               LC_MONETARY category.   5               Table 5-7 LC_MONETARY Category Keywords   *               Keyword          Description  G               copy             Specifies the name of an existing localeiC                                to be used as the definition of thish(                                category.  C                                If you specify a copy statement, youy@                                cannot specify any other keyword.  @               int_curr_symbol  Specifies the string used for the=                                international currency symbol.c  C                                The operand for this keyword is a 4-rA                                character string+. The first threee@                                characters contain the alphabeticH                                international currency symbol. The fourthF                                character defines a character separatorF                                for insertion between the internationalG                                currency symbol and a monetary quantity.   F               currency_symbol  Specifies the string used for the local/                                currency symbol.   I               mon_decimal_     Specifies the the decimal delimiter stringwG               point            used for formatting monetary quantities.u  I               +The_current_implementation_of_DEC_C_RTL_allows_more_than__l  G               four characters to be specified. However, the user should H               not rely on this fact and use it exactly as specified. TheG               4-character limit will be implemented in a future versione               of DEC C RTL.   I                                                  (continued on next page)   I                                    DEC C XPG4 Localization Utilities 5-490 ,         )         DEC C XPG4 Localization Utilitiesc         5.11 Locale File Formato    =               Table 5-7 (Cont.) LC_MONETARY Category Keywordse  *               Keyword          Description  E               mon_thousands_   Specifies the character separator usediE               sep              for grouping digits to the left of theoF                                decimal delimiter in formatted monetary*                                quantities.  G               mon_grouping     Specifies a string that defines the size C                                of each group of digits in formatteda3                                monetary quantities.h  D                                The operand for this keyword consistsE                                of a sequence of integers separated by E                                semicolons. Each integer specifies the E                                number of digits in a group. The first D                                integer defines the size of the groupE                                immediately to the left of the decimal D                                delimiter. Subsequent integers defineC                                succeeding groups to the left of the E                                previous group. If the last integer is H                                not -1, it is used to group any remainingD                                digits. If the last integer is -1, no=                                further grouping is performed.c  B                                A sample interpretation of the mon_E                                grouping statement follows. Assuming a E                                value of 123456789 to be formatted and G                                a mon_thousands_sep operand of ' (single E                                quotation mark), the following results %                                occur:D  =                                mon_grouping   Formatted Value   8                                3;-1           123456'789  9                                3              123'456'789y  9                                3;2;-1         1234'56'789   :                                3;2            12'34'56'789  F               positive_sign    Specifies the string used to indicate aG                                nonnegative formatted monetary quantity.h  I                                                  (continued on next page)2  .         5-50 DEC C XPG4 Localization Utilities n         I                                         DEC C XPG4 Localization UtilitiestI                                                   5.11 Locale File Formate  =               Table 5-7 (Cont.) LC_MONETARY Category Keywordsd  *               Keyword          Description  F               negative_sign    Specifies the string used to indicate aD                                negative formatted monetary quantity.  F               int_frac_digits  Specifies an integer value representingE                                the number of fractional digits (thoseaA                                after the decimal delimiter) to beaI                                displayed in a formatted monetary quantityA?                                using the int_curr_symbol value.a  F               frac_digits      Specifies an integer value representingE                                the number of fractional digits (thoseeA                                after the decimal delimiter) to benI                                displayed in a formatted monetary quantity ?                                using the currency_symbol value.n  D               p_cs_precedes    Specifies an integer value indicatingG                                whether the int_curr_symbol or currency_ D                                symbol string precedes or follows theI                                value for a nonnegative-formatted monetarys(                                quantity.  ?                                The following integer values are *                                recognized:  B                                0   The currency symbol follows the5                                    monetary quantity.   C                                1   The currency symbol precedes the 5                                    monetary quantity.w  I                                                  (continued on next page)>                    I                                    DEC C XPG4 Localization Utilities 5-51  Z         )         DEC C XPG4 Localization Utilitiesp         5.11 Locale File Format     =               Table 5-7 (Cont.) LC_MONETARY Category Keywords   *               Keyword          Description  D               p_sep_by_space   Specifies an integer value indicatingG                                whether the int_curr_symbol or currency_rI                                symbol string is separated by a space fromaI                                a nonnegative-formatted monetary quantity.t  ?                                The following integer values areo*                                recognized:  I                                0   No space separates the currency symbold>                                    from the monetary quantity.  H                                1   A space separates the currency symbol>                                    from the monetary quantity.  H                                2   A space separates the currency symbolC                                    and the positive_sign string, iff,                                    adjacent.  D               n_cs_precedes    Specifies an integer value indicatingG                                whether the int_curr_symbol or currency_ D                                symbol string precedes or follows theF                                value for a negative-formatted monetary(                                quantity.  ?                                The following integer values are *                                recognized:  B                                0   The currency symbol follows the5                                    monetary quantity.l  C                                1   The currency symbol precedes theo5                                    monetary quantity.s  I                                                  (continued on next page)               .         5-52 DEC C XPG4 Localization Utilities i  t      I                                         DEC C XPG4 Localization Utilities I                                                   5.11 Locale File Format     =               Table 5-7 (Cont.) LC_MONETARY Category Keywords   *               Keyword          Description  D               n_sep_by_space   Specifies an integer value indicatingG                                whether the int_curr_symbol or currency_fI                                symbol string is separated by a space fromyF                                a negative-formatted monetary quantity.  ?                                The following integer values arep*                                recognized:  I                                0   No space separates the currency symbold>                                    from the monetary quantity.  H                                1   A space separates the currency symbol>                                    from the monetary quantity.  H                                2   A space separates the currency symbolC                                    and the negative_sign string, ifr,                                    adjacent.  I                                                  (continued on next page)\                                            I                                    DEC C XPG4 Localization Utilities 5-53< m  e      )         DEC C XPG4 Localization Utilitiesa         5.11 Locale File Format     =               Table 5-7 (Cont.) LC_MONETARY Category Keywords   *               Keyword          Description  H               p_sign_posn      Specifies an integer value indicating theF                                positioning of the positive_sign stringC                                for a nonnegative-formatted monetaryI(                                quantity.  ?                                The following integer values aree*                                recognized:  @                                0   A left_parenthesis and right_F                                    parenthesis symbol enclose both theF                                    monetary quantity and the int_curr_D                                    symbol or currency_symbol string.  H                                1   The positive_sign string precedes theF                                    quantity and the int_curr_symbol or:                                    currency_symbol string.  G                                2   The positive_sign string follows the F                                    quantity and the int_curr_symbol or:                                    currency_symbol string.  G                                3   The positive_sign string immediately B                                    precedes the int_curr_symbol or:                                    currency_symbol string.  G                                4   The positive_sign string immediately A                                    follows the int_curr_symbol or :                                    currency_symbol string.  I                                                  (continued on next page)                       .         5-54 DEC C XPG4 Localization Utilities t         I                                         DEC C XPG4 Localization Utilities I                                                   5.11 Locale File Format     =               Table 5-7 (Cont.) LC_MONETARY Category Keywords   *               Keyword          Description  D               n_sign_posn      Specifies an integer value indicatingC                                the positioning of the negative_sign G                                string for a negative-formatted monetaryb(                                quantity.  ?                                The following integer values are *                                recognized:  @                                0   A left_parenthesis and right_F                                    parenthesis symbol enclose both theF                                    monetary quantity and the int_curr_D                                    symbol or currency_symbol string.  H                                1   The negative_sign string precedes theF                                    quantity and the int_curr_symbol or:                                    currency_symbol string.  G                                2   The negative_sign string follows theiF                                    quantity and the int_curr_symbol or:                                    currency_symbol string.  G                                3   The negative_sign string immediatelyaB                                    precedes the int_curr_symbol or:                                    currency_symbol string.  G                                4   The negative_sign string immediately A                                    follows the int_curr_symbol ori:                                    currency_symbol string.  +         5.11.5.2 Monetary Format Variations   D               You can produce a unique customized monetary format byG               changing the value of a single statement. Table 5-8 shows E               the results of using all combinations of defined valuesCD               for the p_cs_precedes, p_sep_by_space, and p_sign_posn               statements.i          I                                    DEC C XPG4 Localization Utilities 5-55a    a      )         DEC C XPG4 Localization Utilitieso         5.11 Locale File Formata    2               Table 5-8 Monetary Format Variations  0                                   p_sep_by_spaceI                                   =                   2        1        0 L               p_cs_precedes = 1   p_sign_posn = 0  ($1.25)  ($       ($1.25)A                                                             1.25)(  K                                   p_sign_posn = 1  + $1.25  +$ 1.25  +$1.25o  K                                   p_sign_posn = 2  $1.25 +  $ 1.25+  $1.25+a  K                                   p_sign_posn = 3  + $1.25  +$ 1.25  +$1.25a  K                                   p_sign_posn = 4  $ +1.25  $+ 1.25  $+1.25   L               p_cs_precedes = 0   p_sign_posn = 0  (1.25    (1.25    (1.25$)>                                                    $)       $)  K                                   p_sign_posn = 1  +1.25 $  +1.25 $  +1.25$G  K                                   p_sign_posn = 2  1.25$ +  1.25 $+  1.25$+   K                                   p_sign_posn = 3  1.25+ $  1.25 +$  1.25+$   K                                   p_sign_posn = 4  1.25$ +  1.25 $+  1.25$+S  I               The following is a sample LC_MONETARY category specified inc.               a locale definition source file:                 LC_MONETARY<               #s8               int_curr_symbol         "<U><S><D><space>"5               currency_symbol         "<dollar-sign>" 0               mon_decimal_point       "<period>"/               mon_thousands_sep       "<comma>"Y'               mon_grouping            3R3               positive_sign           "<plus-sign>" 0               negative_sign           "<hyphen>"'               int_frac_digits         2M'               frac_digits             2 '               p_cs_precedes           1 '               p_sep_by_space          2 '               n_cs_precedes           1 '               n_sep_by_space          2e'               p_sign_posn             3 '               n_sign_posn             3                #L               END LC_MONETARY   .         5-56 DEC C XPG4 Localization Utilities r  a      I                                         DEC C XPG4 Localization Utilities I                                                   5.11 Locale File Format     &         5.11.6 The LC_NUMERIC Category  C               The LC_NUMERIC category defines rules and symbols fornG               formatting nonmonetary numeric information. This category A               begins with the LC_NUMERIC header and ends with then%               END LC_NUMERIC trailer.   C               All operands for the LC_NUMERIC category keywords areRD               defined as string or integer values. String values areC               bounded by double quotation marks ("). All values are I               separated from the keyword they define by one or more blank H               characters (spaces or tabs). Two adjacent double quotationC               characters ("") indicate an undefined string value. AyE               negative one (-1) indicates an undefined integer value.e  F               Table 5-9 lists the statement keywords recognized in the"               LC_NUMERIC category.  4               Table 5-9 LC_NUMERIC Category Keywords  (               Keyword       Description   G               copy          Specifies the name of an existing locale to G                             be used as the definition of this category.   G                             If you specify a copy statement, you cannot 6                             specify any other keyword.  G               decimal_      Specifies the decimal delimiter string used E               point         to format nonmonetary numeric quantities.   H                             This keyword cannot be omitted and cannot be>                             set to the undefined string value.  C               thousands_    Specifies the string separator used for F               sep           grouping digits to the left of the decimalF                             delimiter in formatted nonmonetary numeric'                             quantities.c  I                                                  (continued on next page)           I                                    DEC C XPG4 Localization Utilities 5-57a t         )         DEC C XPG4 Localization Utilities          5.11 Locale File Format     <               Table 5-9 (Cont.) LC_NUMERIC Category Keywords  '               Keyword       Description0  G               grouping      Defines the size of each group of digits inc:                             formatted monetary quantities.  I                             The operand for the grouping keyword consists B                             of a sequence of integers separated byI                             semicolons. Each integer specifies the number C                             of digits in a group. The first integer H                             defines the size of the group immediately toI                             the left of the decimal delimiter. SubsequentoI                             integers define succeeding groups to the leftrH                             of the previous group. Grouping is performedG                             for each integer specified for the groupingpF                             keyword. If the last integer is not -1, itE                             is used repeatedly to group any remaining F                             digits. If the last integer is -1, no more2                             grouping is performed.  C                             A sample interpretation of the grouping B                             statement follows. Assuming a value ofF                             123456789 to be formatted and a thousands_I                             sep operand of ' (single quotation mark), theu4                             following results occur:  :                             grouping       Formatted Value  5                             3;-1           123456'789   6                             3              123'456'789  6                             3;2;-1         1234'56'789  7                             3;2            12'34'56'7896  H               The following is a sample LC_NUMERIC category specified in.               a locale definition source file:                 LC_NUMERIC               # (               decimal_point   "<period>"'               thousands_sep   "<comma>"p!               grouping        <3>                #                END LC_NUMERIC  .         5-58 DEC C XPG4 Localization Utilities 5  8      I                                         DEC C XPG4 Localization Utilities I                                                   5.11 Locale File Format     #         5.11.7 The LC_TIME Categorya  @               The LC_TIME category defines rules and symbols forA               formatting time and date information. This categoryeG               begins with the LC_TIME category header and ends with the "               END LC_TIME trailer.  @               All operands for the LC_TIME category keywords areD               defined as string or integer values. String values areC               bounded by double quotation marks ("). All values areeI               separated from the keyword they define by one or more blanksH               characters (spaces or tabs). Two adjacent double quotationG               characters ("") indicate an undefined string value. FieldeG               descriptors, described later in this section, are used byoI               commands and subroutines that query the LC_TIME category tot:               represent elements of time and date formats.           5.11.7.1 Keywords   G               Table 5-10 lists the statement keywords recognized in the                LC_TIME category.   2               Table 5-10 LC TIME Category Keywords  $               Keyword    Description  G               copy       Specifies the name of an existing locale to be A                          used as the definition of this category.t  D                          If you specify a copy statement, you cannot3                          specify any other keyword.   >               abday      Defines the abbreviated weekday namesB                          corresponding to the %a field descriptor.  C                          Recognized values consist of seven stringsnB                          separated by semicolons. The first stringD                          corresponds to the abbreviated name for theG                          first day of the week (Sun), the second to the I                          abbreviated name for the second day of the week, #                          and so on.   I                                                  (continued on next page)     I                                    DEC C XPG4 Localization Utilities 5-59     (      )         DEC C XPG4 Localization Utilities          5.11 Locale File FormatC    :               Table 5-10 (Cont.) LC_TIME Category Keywords  $               Keyword    Description  G               day        Defines the full spelling of the weekday namesaB                          corresponding to the %A field descriptor.  C                          Recognized values consist of seven strings B                          separated by semicolons. The first stringH                          corresponds to the full spelling of the name ofG                          the first day of the week (Sunday), the secondiG                          to the name of the second day of the week, and                           so on.c  <               abmon      Defines the abbreviated month namesB                          corresponding to the %b field descriptor.  @                          Recognized values consist of 12 stringsB                          separated by semicolons. The first stringD                          corresponds to the abbreviated name for theE                          first month of the year (Jan), the second toeI                          the abbreviated name for the second month of the )                          year, and so on.   E               mon        Defines the full spelling of the month namescB                          corresponding to the %B field descriptor.  @                          Recognized values consist of 12 stringsB                          separated by semicolons. The first stringE                          corresponds to the full spelling of the name G                          for the first month of the year (January), the H                          second to the full spelling of the name for the=                          second month of the year, and so on.e  A               d_t_fmt    Defines the string used for the standardnE                          date-and-time format corresponding to the %coE                          field descriptor. The string can contain anyiI                          combination of characters and field descriptors.P  F               d_fmt      Defines the string used for the standard dateI                          format corresponding to the %x field descriptor.RB                          The string can contain any combination of:                          characters and field descriptors.  I                                                  (continued on next page)r  .         5-60 DEC C XPG4 Localization Utilities i  e      I                                         DEC C XPG4 Localization UtilitieseI                                                   5.11 Locale File Formate    :               Table 5-10 (Cont.) LC_TIME Category Keywords  $               Keyword    Description  F               t_fmt      Defines the string used for the standard timeI                          format corresponding to the %X field descriptor.cB                          The string can contain any combination of:                          characters and field descriptors.  C               am_pm      Defines the strings used to represent a.m.nI                          (before noon) and p.m. (afternoon) corresponding 4                          to the %p field descriptor.  A                          Recognized values consist of two strings B                          separated by semicolons. The first stringH                          corresponds to the a.m. designation, the secondD                          string corresponds to the p.m. designation.  I               t_fmt_     Defines the string used for the standard 12-hour E               ampm       time format that includes an am_pm value (%p +                          field descriptor).i  C                          This statement corresponds to the %r fieldt?                          descriptor. The string can contain any I                          combination of characters and field descriptors. F                          If the string is empty, the 12-hour format is5                          not supported by the locale.   H               era        Defines how the years are counted and displayedG                          for each era in a locale, corresponding to theo6                          %E field descriptor modifier.  F                          For each era, there must be one string in the*                          following format:  I                          direction:offset:start_date:end_date:name:format   I                                                  (continued on next page)               I                                    DEC C XPG4 Localization Utilities 5-61  r  c      )         DEC C XPG4 Localization Utilities          5.11 Locale File Formate    :               Table 5-10 (Cont.) LC_TIME Category Keywords  $               Keyword    Description  D                          The variables for the era string format are,                          defined as follows:  G                          o  direction - Specifies a minus (-) or a plus *                             (+) character.  H                             The minus character (-) indicates that yearsG                             count in the negative direction when movingtI                             from the start date to the end date. The plus G                             character (+) indicates that years count in G                             the positive direction when moving from they7                             start date to the end date.   H                          o  offset - Specifies a number representing theF                             first year of the era corresponding to the1                             %Ey field descriptor.d  G                          o  start_date - Specifies the starting date of E                             the era in yyyy/mm/dd format, where yyyy, D                             mm, and dd are the year, month, and day,D                             respectively, on the Gregorian calendar.  >                             Years prior to the year A.D. 1 areI                             represented as negative numbers. For example,cI                             an era beginning March 5 in the year 100 B.C.r?                             would be represented as -100/03/05.   I                                                  (continued on next page)r                  .         5-62 DEC C XPG4 Localization Utilities o  w      I                                         DEC C XPG4 Localization Utilities I                                                   5.11 Locale File Format     :               Table 5-10 (Cont.) LC_TIME Category Keywords  $               Keyword    Description    G                          o  end_date - Specifies the ending date of thenH                             era in the same form used for the start_dateH                             variable or one of the two special values -*"                             or +*.  H                             A -* value indicates that the ending date ofH                             the era extends backward to the beginning ofF                             time. A +* value indicates that the endingF                             date of the era extends forward to the endF                             of time. Therefore, the ending date can beH                             chronologically before or after the startingE                             date of the era. For example, the stringslI                             for the Christian eras A.D. and B.C. would belH                             entered, respectively, in the following way:  9                              +:0:0000/01/01:+*:AD:%Ey %EC :                              +:1:-0001/12/31:-*:BC:%Ey %EC  F                          o  name - Specifies a string representing theI                             name ofDECeCeXPG4hLocalizationtUtilitiest5-63_1                             %EC field descriptor.   H                          o  format - Specifies a strftime, strptime, andI                             wcsftime format string to use when formatting 5                             the %EY field descriptor..  A                             This string can contain any strftime, A                             strptime, and wcsftime format control H                             characters (except %EY) and locale-dependent1                             multibyte characters.   I                                                  (continued on next page)   I                                    DEC C XPG4 Localization Utilities 5-63            )         DEC C XPG4 Localization Utilities1         5.11 Locale File Formatw    :               Table 5-10 (Cont.) LC_TIME Category Keywords  $               Keyword    Description  F                          An era value consists of one string (enclosedF                          in quotes) for each era. If more than one eraH                          is specified, each era string is separated by a'                          semicolon (;).   F               era_d_fmt  Defines the string used to represent the dateE                          in alternate-era format corresponding to the I                          %Ex field descriptor. The string can contain any I                          combination of characters and field descriptors.   E               era_t_fmt  Defines the locale's alternative time format_G                          as represented by the %EX field descriptor for :                          strftime, strptime, and wcsftime.  C               era_d_t_   Defines the locale's alternative date-and- D               fmt        time format as represented by the %Ec fieldI                          descriptor for strftime, strptime, and wcsftime.L  =               alt_       Defines alternate strings for digits B               digits     corresponding to the %O field descriptor.  H                          Recognized values consist of a group of stringsB                          separated by semicolons. The first stringF                          represents the alternate string for 0 (zero),C                          the second string represents the alternatenC                          string for 1, and so on. You can specify al:                          maximum of 100 alternate strings.  "         5.11.7.2 Field Descriptors  B               The LC_TIME locale definition source file uses fieldI               descriptors to represent elements of time and date formats.tE               You can combine these field descriptors to create otheriA               field descriptors or to create time and date formatrE               strings. When used in format strings that contain field E               descriptors and other characters, field descriptors are D               replaced by their current values. All other charactersC               are copied without change. Table 5-11 lists the fieldtE               descriptors used by commands and subroutines that queryc7               the LC_TIME category for time formatting.p  .         5-64 DEC C XPG4 Localization Utilities    p      I                                         DEC C XPG4 Localization Utilities I                                                   5.11 Locale File Formatd    5           Table 5-11 LC_TIME Locale Field Descriptors              Fieldn           Descriptor   Meaning  C               %a       Represents the abbreviated weekday name (for D                        example, Sun) defined by the abday statement.  E               %A       Represents the full weekday name (for example, <                        Sunday) defined by the day statement.  A               %b       Represents the abbreviated month name (for D                        example, Jan) defined by the abmon statement.  C               %B       Represents the full month name (for example,e?                        January) defined by the month statement.   I               %c       Represents the date-and-time format defined by theg)                        d_t_fmt statement.i  H               %C       Represents the century as a decimal number (00 to                        99).r  C               %d       Represents the day of the month as a decimala)                        number (01 to 31).   B               %D       Represents the date in %m/%d/%y format (for*                        example, 01/31/91).  C               %e       Represents the day of the month as a decimal (                        number (1 to 31).  ?                        If the day of the month is not a 2-digit G                        number, the leading digit is filled with a space !                        character.u  <               %Ec      Specifies the alternate date-and-time5                        representation for the locale.   F               %EC      Specifies the name of the base year (period) in=                        the locale's alternate representation.   F               %Ex      Specifies the alternate date representation for"                        the locale.  G               %Ey      Specifies the offset from %EC (year only) in the 9                        locale's alternate representation.   H               %EY      Specifies the full alternate year representation.  I                                                  (continued on next page)h  I                                    DEC C XPG4 Localization Utilities 5-65            )         DEC C XPG4 Localization Utilities          5.11 Locale File Format5    =           Table 5-11 (Cont.) LC_TIME Locale Field Descriptors              Field            Descriptor   Meaning  A               %h       Represents the abbreviated month name (for D                        example, Jan) defined by the abmon statement.D                        This field descriptor is a synonym for the %b(                        field descriptor.  E               %H       Represents the 24-hour clock hour as a decimal )                        number (00 to 23).   E               %I       Represents the 12-hour clock hour as a decimali)                        number (01 to 12).   I               %j       Represents the day of the year as a decimal number $                        (001 to 366).  D               %m       Represents the month of the year as a decimal)                        number (01 to 12).o  F               %M       Represents the minutes of the hour as a decimal)                        number (00 to 59).e  6               %n       Specifies a new-line character.  B               %Od      Specifies the day of the month by using the:                        locale's alternate numeric symbols.  B               %Oe      Specifies the day of the month by using the:                        locale's alternate numeric symbols.  F               %OH      Specifies the hour (24-hour clock) by using the:                        locale's alternate numeric symbols.  F               %OI      Specifies the hour (12-hour clock) by using the:                        locale's alternate numeric symbols.  @               %Om      Specifies the month by using the locale's1                        alternate numeric symbols.t  B               %OM      Specifies the minutes by using the locale's1                        alternate numeric symbols.   B               %OS      Specifies the seconds by using the locale's1                        alternate numeric symbols.   B               %OU      Specifies the week number of the year (withD                        Sunday as the first day of the week) by using>                        the locale's alternate numeric symbols.  I                                                  (continued on next page)b  .         5-66 DEC C XPG4 Localization Utilities           I                                         DEC C XPG4 Localization Utilities I                                                   5.11 Locale File Formatp    =           Table 5-11 (Cont.) LC_TIME Locale Field Descriptorsr             Fieldr           Descriptor   Meaning  H               %Ow      Specifies the weekday as a number in the locale's=                        alternate representation (Sunday = 0).   B               %OW      Specifies the week number of the year (withD                        Monday as the first day of the week) by using>                        the locale's alternate numeric symbols.  D               %Oy      Specifies the year (offset from %C) using the:                        locale's alternate numeric symbols.  H               %p       Represents the a.m. or p.m. string defined by the'                        am_pm statement.e  G               %r       Represents the 12-hour clock time with a.m./p.m.pG                        notation as defined by the t_fmt_ampm statement.g  H               %S       Represents the seconds of the minute as a decimal)                        number (00 to 59).l  1               %t       Specifies a tab character.e  B               %T       Represents 24-hour clock time in the format8                        %H:%M:%S (for example, 16:55:15).  C               %U       Represents the week of the year as a decimali)                        number (00 to 53).c  F                        Sunday, or its equivalent as defined by the dayD                        statement, is considered the first day of theC                        week for calculating the value of this fields"                        descriptor.  I               %w       Represents the day of the week as a decimal number                          (0 to 6).  B                        Sunday, or its equivalent as defined by theF                        day statement, is considered to be 0 (zero) forF                        calculating the value of this field descriptor.  I                                                  (continued on next page)   I                                    DEC C XPG4 Localization Utilities 5-67            )         DEC C XPG4 Localization Utilities          5.11 Locale File Formatf    =           Table 5-11 (Cont.) LC_TIME Locale Field Descriptorsc             Fieldl           Descriptor   Meaning  C               %W       Represents the week of the year as a decimal )                        number (00 to 53).e  F                        Monday, or its equivalent as defined by the dayD                        statement, is considered the first day of theC                        week for calculating the value of this fielde"                        descriptor.  F               %x       Represents the date format defined by the d_fmt!                        statement.%  F               %X       Represents the time format defined by the t_fmt!                        statement.   E               %y       Represents the year of the century (00 to 99).   C               %Y       Represents the year as a decimal number (foro&                        example, 1989).  >               %%       Specifies a % (percent sign) character.  )         5.11.7.3 Sample Locale Definition   G               The following is a sample LC_TIME category specified in a_,               locale definition source file:                 LC_TIME                # -               #Abbreviated weekday names (%a) G               abday   "<S><u><n>";"<M><o><n>";"<T><u><e>";"<W><e><d>";\c9                       "<T><h><u>";"<F><r><i>";"<S><a><t>"n  &               #Full weekday names (%A)A               day     "<S><u><n><d><a><y>";"<M><o><n><d><a><y>";\sM                       "<T><u><e><s><d><a><y>";"<W><e><d><n><e><s><d><a><y>";\ F                       <T><h><u><r><s><d><a><y>";"<F><r><i><d><a><y>";\/                       <S><a><t><u><r><d><a><y>"a  +               #Abbreviated month names (%b) G               abmon   "<J><a><n>";"<F><e><b>";"<M><a><r>";"<A><p><r>";\ G                       "<M><a><y>";"<J><u><n>";"<J><u><l>";"<A><u><g>";\ D                       <S><e><p>";"<O><c><t>";"<N><o><v>";"<D><e><c>"  .         5-68 DEC C XPG4 Localization Utilities           I                                         DEC C XPG4 Localization Utilities I                                                   5.11 Locale File Formato    $               #Full month names (%B)J               mon     "<J><a><n><u><a><r><y>";"<F><e><b><r><u><a><r><y>";\G                       "<M><a><r><c><h>";"<A><p><r><i><l>";"<M><a><y>";\ I                       <J><u><n><e>";"<J><u><l><y>";"<A><u><g><u><s><t>";\nM                       "<S><e><p><t><e><m><b><e><r>";"<O><c><t><o><b><e><r>";\aJ                       <N><o><v><e><m><b><e><r>";"<D><e><c><e><m><b><e><r>"  (               #Date-and-time format (%c)K               #Note that for improved readability, this section uses actualtO               #characters, rather than symbolic names, and is inconsistent with E               #the other sections in this example.  This is bad form. :               #In practice, symbolic names should be used.4               d_t_fmt         "%a %b %d %H:%M:%S %Y"               #C               #Date format (%x) (               d_fmt           "%m/%d/%y"               #                #Time format (%X) (               t_fmt           "%H:%M:%S"               #r'               #Equivalent of AM/PM (%p)n/               am_pm           "<A><M>";"<P><M>"e               #t'               #12-hour time format (%r) K               #Note that for improved readability, this section uses actualaO               #characters, rather than symbolic names, and is inconsistent with E               #the other sections in this example.  This is bad form. :               #In practice, symbolic names should be used.+               t_fmt_ampm      "%I:%M:%S %p"d               # >               era             "+:0:0000/01/01:+*:AD:%Ey %EC";\-               "+:1:-0001/12/31:-*:BC:%Ey %EC"i                 era_d_fmt     ""M               alt_digits    "<0><t><h>";"<1><s><t>";"<2><n><d>";"<3><r><d>";\ M                             "<4><t><h>";"<5><t><h>";"<6><t><h>";"<7><t><h>";\ B                             "<8><t><h>";"<9><t><h>";"<1><0><t><h>"               #                END LC_TIME             I                                    DEC C XPG4 Localization Utilities 5-69  h  r)         DEC C XPG4 Localization Utilities 5         5.12 Character Set Description (Charmap) Filen  5         5.12 Character Set Description (Charmap) FileG  H               This section describes the character set description file,I               or charmap file. The charmap file defines character symbolseG               as character encodings and is the source file for a codedr(               character set, or codeset.  %         5.12.1 Portable Character Set   D               All supported codesets have the Portable Character SetI               (PCS) as a proper subset. The PCS consists of the following F               character symbols (listed by their standardized symbolicE               names) and their hexadecimal encodings. See Table 5-12.i  /               Table 5-12 Portable Character Set_  8               Symbol Name           Hexadecimal Encoding  (               <NUL>                 \x00  (               <alert>               \x07  (               <backspace>           \x08  (               <tab>                 \x09  (               <newline>             \x0A  (               <vertical-tab>        \x0B  (               <form-feed>           \x0C  (               <carriage-return>     \x0D  (               <space>               \x20  (               <exclamation-mark>    \x21  (               <quotation-mark>      \x22  (               <number-sign>         \x23  (               <dollar-sign>         \x24  (               <percent>             \x25  (               <ampersand>           \x26  (               <apostrophe>          \x27  (               <left-parenthesis>    \x28  (               <right-parenthesis>   \x29  (               <asterisk>            \x2A  I                                                  (continued on next page)o  .         5-70 DEC C XPG4 Localization Utilities /I                                         DEC C XPG4 Localization UtilitiesyH                            5.12 Character Set Description (Charmap) File  7               Table 5-12 (Cont.) Portable Character Seta  8               Symbol Name           Hexadecimal Encoding  (               <plus-sign>           \x2B  (               <comma>               \x2C  (               <hyphen>              \x2D  (               <period>              \x2E  (               <slash>               \x2F  (               <zero>                \x30  (               <one>                 \x31  (               <two>                 \x32  (               <three>               \x33  (               <four>                \x34  (               <five>                \x35  (               <six>                 \x36  (               <seven>               \x37  (               <eight>               \x38  (               <nine>                \x39  (               <colon>               \x3A  (               <semi-colon>          \x3B  (               <less-than>           \x3C  (               <equal-sign>          \x3D  (               <greater-than>        \x3E  (               <question-mark>       \x3F  (               <commercial-at>       \x40  (               <A>                   \x41  (               <B>                   \x42  (               <C>                   \x43  (               <D>                   \x44  (               <E>                   \x45  (               <F>                   \x46  (               <G>                   \x47  I                                                  (continued on next page)a  I                                    DEC C XPG4 Localization Utilities 5-71s e)         DEC C XPG4 Localization Utilities 5         5.12 Character Set Description (Charmap) Filep  7               Table 5-12 (Cont.) Portable Character Setw  8               Symbol Name           Hexadecimal Encoding  (               <H>                   \x48  (               <I>                   \x49  (               <J>                   \x4A  (               <K>                   \x4B  (               <L>                   \x4C  (               <M>                   \x4D  (               <N>                   \x4E  (               <O>                   \x4F  (               <P>                   \x50  (               <Q>                   \x51  (               <R>                   \x52  (               <S>                   \x53  (               <T>                   \x54  (               <U>                   \x55  (               <V>                   \x56  (               <W>                   \x57  (               <X>                   \x58  (               <Y>                   \x59  (               <Z>                   \x5A  (               <left-bracket>        \x5B  (               <backslash>           \x5C  (               <right-bracket>       \x5D  (               <circumflex>          \x5E  (               <underscore>          \x5F  (               <grave-accent>        \x60  (               <a>                   \x61  (               <b>                   \x62  (               <c>                   \x63  (               <d>                   \x64  I                                                  (continued on next page)s  .         5-72 DEC C XPG4 Localization Utilities  I                                         DEC C XPG4 Localization UtilitiesoH                            5.12 Character Set Description (Charmap) File  7               Table 5-12 (Cont.) Portable Character Set   8               Symbol Name           Hexadecimal Encoding  (               <e>                   \x65  (               <f>                   \x66  (               <g>                   \x67  (               <h>                   \x68  (               <i>                   \x69  (               <j>                   \x6A  (               <k>                   \x6B  (               <l>                   \x6C  (               <m>                   \x6D  (               <n>                   \x6E  (               <o>                   \x6F  (               <p>                   \x70  (               <q>                   \x71  (               <r>                   \x72  (               <s>                   \x73  (               <t>                   \x74  (               <u>                   \x75  (               <v>                   \x76  (               <w>                   \x77  (               <x>                   \x78  (               <y>                   \x79  (               <z>                   \x7A  (               <left-brace>          \x7B  (               <vertical-line>       \x7C  (               <right-brace>         \x7D  (               <tilde>               \x7E  +         5.12.2 Components of a Charmap File   :               A charmap file has the following components:  G               o  An optional special symbolic name declarations sectione  I                                    DEC C XPG4 Localization Utilities 5-73r           )         DEC C XPG4 Localization Utilities-5         5.12 Character Set Description (Charmap) File     G                  Each declaration in this section consists of a specialdD                  symbolic name, followed by one or more space or tabF                  characters, and a value. The following list describesG                  the special symbolic names that you can include in thet&                  declarations section:  #                     <code_set_name>t  C                     Specifies the name of the codeset for which thetB                     charmap file is defined. This value determinesC                     the value returned by the nl_langinfo (CODESET) G                     subroutine. If <code_set_name> is not declared, the4@                     name for the Portable Character Set is used.                        <mb_cur_max>  H                     Specifies the maximum number of bytes in a characterI                     for the codeset. Valid values are 1 to 4. The default                      value is 1.d                        <mb_cur_min>  H                     Specifies the minimum number of bytes in a characterF                     for the codeset. Since all supported codesets haveG                     the Portable Character Set as a proper subset, this)$                     value must be 1.  !                     <escape_char>i  A                     Specifies the escape character that indicates C                     encodings in hexadecimal or octal notation. The 5                     default value is a backslash (\).t  "                     <comment_char>  F                     Specifies the character used to indicate a commentC                     within a charmap file. The default value is them$                     number sign (#).  +               o  The CHARMAP section header   D                  This header marks the beginning of the section that=                  associates character symbols with encodings.   A               o  Mapping statements for characters in the codeset   .         5-74 DEC C XPG4 Localization Utilities           I                                         DEC C XPG4 Localization Utilities H                            5.12 Character Set Description (Charmap) File    I                  Each statement specifies a symbolic name for a character B                  and the associated encoding for that character. A<                  mapping statement has the following format:  '                  <char_symbol> encodingt  C                  A symbolic name begins with the left angle-bracketrD                  (<) character and ends with the right angle-bracketC                  (>) character. For char_symbol (the name between < E                  and >), you can use any characters from the Portable H                  Character Set, except for control and space characters.I                  You can use a > in char_symbol; if you do, precede all > I                  characters except the last one with the escape characterCD                  (as specified by the <escape_char> special symbolic                  name).L  B                  An encoding is specified as one or more character@                  constants, with the maximum number of characterI                  constants specified by the <mb_cur_max> special symbolicMG                  name. The encoding may be specified as decimal, octal, E                  or hexadecimal constants with the following formats:   C                  o  Decimal constant: \dnn or \dnnn, where n is any !                     decimal digite  E                  o  Octal constant: \nn or \nnn, where n is any octale                     digit   >                  o  Hexadecimal constant: \xnn, where n is any%                     hexadecimal digitn  G                  The following are sample character symbol definitions:s  9                  <A>        \d65        #decimal constante=                  <B>        \x42        #hexadecimal constanttG                  <j10101>   \x81\xA1    #multiple hexadecimal constantsm  B                  You can also define a range of symbolic names andC                  corresponding encoded values, where the nonnumeric I                  prefix for each symbolic name is common, and the numericpC                  portion of the second symbolic name is equal to orMG                  greater than the numeric portion of the first symbolickE                  name. In this format, a symbolic name value consists E                  of zero or more nonnumeric characters followed by anyC                  integer of one or more decimal digits. This formateE                  defines a series of symbolic names. For example, the H                  string <j0101>...<j0104> is interpreted as the symbolic  I                                    DEC C XPG4 Localization Utilities 5-75            )         DEC C XPG4 Localization Utilities 5         5.12 Character Set Description (Charmap) Filee    F                  names <j0101>, <j0102>, <j0103>, and <j0104>, in that                  order.   E                  In statements defining ranges of symbolic names, the C                  specified encoded value is the value for the first5F                  symbolic name in the range. Subsequent symbolic namesF                  have encoded values in increasing order. Consider the,                  following sample statement:  4                  <j0101>...<j0104>        \d129\d254  A                  This sample statement is interpreted as follows:m  #                  <j0101> \d129\d254 #                  <j0102> \d129\d255e!                  <j0103> \d130\d0 !                  <j0104> \d130\d1   E                  You cannot assign multiple encodings to one symbolic H                  name, but you can create multiple names for one encodedI                  value because some characters have several common names.tH                  For example, the . character is called a period in someG                  parts of the world, and a full stop in others. You cant@                  specify both names in the charmap. For example:  %                  <period>        \x2eo%                  <full-stop>     \x2e9  H                  Any comments must begin with the character specified byI                  the <comment_char> special symbolic name. When an entiresG                  line is a comment, you must specify the <comment_char>o1                  in the first column of the line.   0               o  The END CHARMAP section trailer  @                  This trailer indicates the end of character map                  statements.  B               The following is a portion of a sample charmap file:                 CHARMAP 1               <code_set_name>         "ISO8859-1" '               <mb_cur_max>            1>'               <mb_cur_min>            1 '               <escape_char>           \;'               <comment_char>          #   .         5-76 DEC C XPG4 Localization Utilities e  t      I                                         DEC C XPG4 Localization Utilities<H                            5.12 Character Set Description (Charmap) File    *               <NUL>                   \x00*               <SOH>                   \x01*               <STX>                   \x02*               <ETX>                   \x03*               <EOT>                   \x04*               <ENQ>                   \x05*               <ACK>                   \x06*               <alert>                 \x07*               <backspace>             \x08*               <tab>                   \x09*               <newline>               \x0a*               <vertical-tab>          \x0b*               <form-feed>             \x0c*               <carriage-return>       \x0d               END CHARMAP                                                             I                                    DEC C XPG4 Localization Utilities 5-77N   t  r                    I                                                                         6iI         _________________________________________________________________i  I                          Local Area Network (LAN) Management Enhancementso    E               The local area network (LAN) software has been enhanced H               to include system management tools for LAN configurations.E               The enhancements include two LAN utilities that work in F               conjunction with the OpenVMS LAN driver system software.G               The LAN utilities perform system management tasks related ;               to LAN operations and provide other benefits.   5               The LAN system management enhancements:o  F               o  Allow you to set LAN parameters to customize your LAN                  environment.   3               o  Display LAN settings and counters.   G               o  Provide Maintenance Operations Protocol (MOP) downline C                  load support for devices such as terminal servers, E                  x-terminals, and LAN-based printers, and for booting0I                  satellites in a VMScluster environment. This enhancementlE                  provides an alternative to the traditional method of H                  using either DECnet for OpenVMS or DECnet/OSI software.                          I                      Local Area Network (LAN) Management Enhancements 6-1  T             I               Table 6-1 describes the LAN utilities and the functionality6D               supported on systems running OpenVMS Alpha and OpenVMS               VAX.  :               Table 6-1 LAN System Management Enhancements  =               Utility   Description           OpenVMS Supporta  I               LAN       Runs as a server      The LANACP utility provideseE               Auxiliary process whose         identical functionalityhF               Control   primary function      on VAX and Alpha systemsE               Program   is to provide         running OpenVMS Versiono2               (LANACP)  MOP downline load     6.2.                          service.  I                                                  (continued on next page)r                                                    <         6-2 Local Area Network (LAN) Management Enhancements    2              B               Table 6-1 (Cont.) LAN System Management Enhancements  =               Utility   Description           OpenVMS Supporta    C               LAN       Allows you to         OpenVMS Alpha Version F               Control   control LAN           6.1 contains the initialF               Program   software parameters   implementation of LANCP,D               (LANCP)   and obtain            which does not includeD                         information from      MOP-related functions.F                         the LAN software.     OpenVMS Version 6.2 (VAXI                         You can use the       and Alpha) adds MOP-relatedxC                         LANCP utility to:     functions and extendsr  D                         o  Obtain LAN         this capability to VAXD                            device counters,   systems. The followingE                            revision, and      table shows how the LAN C                            configuration      utility functions are H                            information        supported on VAX and Alpha6                                               systems:  I                                                  (continued on next page)                                   I                      Local Area Network (LAN) Management Enhancements 6-3            B               Table 6-1 (Cont.) LAN System Management Enhancements  =               Utility   Description           OpenVMS Supportp    I                         o  Change the         ___________________________ K                            operational                    OpenVMS   OpenVMS G                            parameters of                  Alpha     VAX I                            LAN devices on     Function____V6.2______V6.2_f  F                            the system         Update      Yes       No  7                         o  Maintain the LAN   firmware?g  F                            device database    Change      Yes       No4                            and the LAN node   opera-4                            database           tional4                         o  Update the         param-3                            firmware on LAN    eters 4                            devices            of LAN6                                               devices?K                         o  Control the        Display     Yes       Limited 1                            LANACP LAN         LAN 4                            Server process     device6                            (including MOP     informa-3                            downline load      tion? I                            server related     ___________________________ %                            functions)   '                         o  Initiate MOPE*                            console carrier*                            and MOP trigger*                            boot operations  I               ___________________________________________________________   <         6-4 Local Area Network (LAN) Management Enhancements                   H               This chapter describes how to invoke and use the LANCP and               LANACP utilities.L           6.1 The LANCP Utility   G               The LANCP utility implements commands to set and show LANxI               parameters. Section 6.1.1 describes how to invoke the LANCP E               utility. Table 6-2 describes LAN functions and provides D               section references to the LANCP commands that help you&               perform these functions.  6               Table 6-2 Functions of the LANCP Utility  H               Category         Function                        Reference  L               LAN device       Changes operational             Section 6.1.37               management       parameters, and displaysA2                                counters and status8                                information, and performs6                                firmware updates of LAN'                                devices.   L               LAN device       Enables or disables MOP         Section 6.1.45               database         downline load service, 8               management       and displays MOP counters:                                information for LAN devices7                                in the LAN permanent and 9                                volatile device databases.   L               LAN node         Changes node data and           Section 6.1.54               database         displays MOP counters5               management       information in the LANh:                                permanent and volatile node)                                databases.   L               LANACP MOP       Changes operational             Section 6.1.6;               downline         parameters, and displays andx9               load service     clears counters and status +               management       information.   L               LANCP MOP        Initiates console carrier       Section 6.1.7+               console          connections.                carrier   L               LANCP MOP        Sends trigger boot requests     Section 6.1.8.               trigger boot     to other nodes.  I                      Local Area Network (LAN) Management Enhancements 6-5s               4         6.1.1 Invoking and Exiting the LANCP Utility  C               Table 6-3 describes the ways you can invoke the LANCP -               utility (SYS$SYSTEM:LANCP.EXE).   2               Table 6-3 Invoking the LANCP Utility  &               Command          Example  @               Use the RUN      At the DCL command prompt, enter:5               command          $ RUN SYS$SYSTEM:LANCP   G                                The LANCP utility responds by displayingeF                                the LANCP prompt at which you can enter.                                LANCP commands.  G               Define LANCP     Either at the DCL prompt or in a startupn<               as a foreign     or login command file, enter:<               command          $ LANCP :== $SYS$SYSTEM:LANCP  G                                Then, you can enter the command LANCP atlG                                the DCL prompt to invoke the utility andp4                                enter LANCP commands.  @                                When you enter the LANCP command:  @                                o  Without specifying any commandH                                   qualifiers, the LANCP utility displaysI                                   the LANCP prompt at which you can enter +                                   commands.   D                                o  With command qualifiers, the LANCPF                                   utility terminates after it executesH                                   the command and the DCL command prompt/                                   is displayed.   I                                                  (continued on next page)u  <         6-6 Local Area Network (LAN) Management Enhancements e  V              :               Table 6-3 (Cont.) Invoking the LANCP Utility  &               Command          Example  @               Use the MCR      At the DCL command prompt, enter:*               command          $ MCR LANCP  D                                When you enter the MCR LANCP command:  @                                o  Without specifying any commandH                                   qualifiers, the LANCP utility displaysI                                   the LANCP prompt at which you can enterm+                                   commands.   D                                o  With command qualifiers, the LANCPF                                   utility terminates after it executesH                                   the command and the DCL command prompt/                                   is displayed.     E               For information about the LANCP utility, enter the HELPt*               command at the LANCP prompt.  G               To exit from the LANCP utility, enter the EXIT command atp/               the LANCP prompt or press Ctrl/Z.            6.1.2 LAN Databasesa  F               The LANCP and LANACP utilities manipulate two databases:  G               o  The device database, one for each node in the cluster,eB                  contains information about the LAN devices on the                  system.  G               o  The node database, usually one for the entire cluster,cH                  contains information about all the nodes on the LAN forB                  which LANCP/LANACP will provide MOP load service.  E               These two databases are stored on disk as the permanentrC               databases. When the LANACP is started (usually duringrA               system startup) the contents of these databases areuG               loaded into memory as the volatile databases. MaintainingtB               a version of the databases in memory improves LANACPC               performance. The volatile databases are reloaded fromcF               the permanent databases every time the LANACP process is8               started, and by explicit operator command.  I                      Local Area Network (LAN) Management Enhancements 6-7  e  a              I               The permanent (disk-resident) versions of the databases are =               manipulated by LANCP DEFINE and PURGE commands.   G               o  DEFINE commands are used to enter information into the                   databases.s  ?               o  PURGE commands are used to remove information.o  F               The volatile (memory-resident) versions of the databasesC               are manipulated by LANCP SET and CLEAR commands. TheycI               provide the same functions as the permanent database DEFINEtI               and PURGE commands, but only affect the volatile databases. B               Because the volatile databases are reloaded from theF               permanent databases each time the LANACP is started, theG               effect of SET and CLEAR commands is lost at each startup.1  C               Use DEFINE and PURGE commands to modify the permanentuG               databases for settings that you wish to keep permanently.nI               Use SET and CLEAR commands to modify the volatile databaseshE               for settings that you wish to keep only for the current I               session. LANCP commands are provided to update the volatile I               databases with changes made to the permanent databases, anda               vice versa.n  #         6.1.3 LAN Device Managemente  I               LAN device management consists of setting device parametersrD               and displaying device characteristics. You can use theB               LANCP utility to set parameters for the types of LAN)               devices shown in Table 6-4.                               <         6-8 Local Area Network (LAN) Management Enhancements                   #               Table 6-4 LAN Devicest                           Device2               LAN       Examples       Description  H               Ethernet  DE425,         Allow the selection of media typeH                         DE434,         (type of cable connected) and theG                         DE435,         speed of connection (Ethernet ora5                         DE436,         FastEthernet). B                         DE500,         Allow full-duplex operationH                         DECchip        (point-to-point operation betweenE                         21040          similar devices or between thee  <                                        device and a switch).  C               FDDI      DEFTA,         Allow full-duplex operation.                          DEFPA,                         DEFAA,$                         DEFEA, DEMFA  F               Token     DETRA,         Allow the setting of Token RingD               Ring      DW300, DW110   parameters and the definitionG                                        of source routing and functionald7                                        address mapping.   C               All       Any            Allow the setting of genericaD                                        parameters such as the number:                                        of receive buffers.  )         6.1.3.1 Setting Device Parametersy  B               All LAN devices are characterized by a collection of?               parameters. The parameters define the operational<D               characteristics of a LAN device on the medium to which&               the device is connected.  C               At the LANCP> prompt, enter the SET DEVICE command torA               set LAN device parameters. The LANCP utility issuessD               this command directly to the specified device (without:               interaction with the LANACP server process).  7               The syntax for the SET DEVICE command is:   /               SET DEVICE device-name/qualifiers   +               In this command, you specify:                  o  Device-name  I                      Local Area Network (LAN) Management Enhancements 6-9L l  t              H                  Supply the LAN controller device name. For example, youG                  can specify a DEMNA controller as either EXA, EXA0, or G                  EXA0:. To select all LAN devices, omit the device name 0                  and include the /ALL qualifier.                 o  Qualifiers   H                  See Table 6-5 for a description of the LANCP SET DEVICE$                  command qualifiers.                                                                        =         6-10 Local Area Network (LAN) Management Enhancements     a              5         Table 6-5 LANCP SET DEVICE Command Qualifiersd  '         Qualifier           Description-  E         /AGING_             Sets the amount of time in seconds to age G         TIMER=value         source routing cache entries before markingCB                             them stale. This timer expires when noC                             traffic is sent to or received from the ?                             remote node in this amount of time._  5                             Default value: 60 secondsw  ?                             Note: Increase this value when idleaD                             connections bounce between the stale andD                             known states. Setting this value too lowE                             may cause unnecessary explorer traffic tot-                             traverse the LAN..  7                             Devices: Token Ring devices   F         /ALL                Sets data for all LAN devices. If a deviceG                             name is specified, all matching LAN devices F                             are selected (for example, E to select allG                             Ethernet devices, F for FDDI devices, I forsG                             Token Ring devices, and EW for Ethernet PCIl+                             Tulip devices).e  E         /CACHE_             Sets the number of entries to reserve for C         ENTRIES=value       caching source routing address entries.e  6                             Default value: 200 entries  F                             Note: If your system directly communicatesI                             to a large number of systems, you may want to 1                             increase this number.e  7                             Devices: Token Ring devices   G         /CONTENDER          Specifies that the device is to participaterE                             in the Monitor Contention process when it +                             joins the ring.   7                             Default value: /NOCONTENDER   H                             Note: The default setting directs the deviceE                             not to challenge the current ring server.n  7                             Devices: Token Ring devicesi  I                                                  (continued on next page)   I                     Local Area Network (LAN) Management Enhancements 6-11.                   =         Table 6-5 (Cont.) LANCP SET DEVICE Command Qualifiers   '         Qualifier           Description   D         /DISCOVERY_         Sets the number of seconds to wait for aH         TIMER=value         reply from a remote node when performing theC                             source routing route discovery process.e  4                             Default value: 2 seconds  G                             Note: If you have nodes that respond slowlyoA                             on your extended LAN, you may need torE                             increase this number to reduce the amountLH                             of explorer traffic that traverses your LAN.  7                             Devices: Token Ring devices   F         /EARLY              Enables Early Token Release on the device.H                             The negated form of the qualifier, /NOEARLY,9                             disables Early Token Release.   1                             Default value: /EARLYc  D                             Devices: Token Ring devices operating on,                             16-megabit rings    I                                                  (continued on next page)i    =         6-12 Local Area Network (LAN) Management Enhancementsi                   =         Table 6-5 (Cont.) LANCP SET DEVICE Command Qualifiersy  '         Qualifier           Description     G         /FULL_DUPLEX        Enables usage of full-duplex operation on a E                             device. You may also need to specifically C                             set up the device or network connection B                             for full-duplex operation to get full-E                             duplex operation. The negated form of the_F                             qualifier, /NOFULL_DUPLEX, disallows full-G                             duplex operation regardless of the hardware *                             configuration.  9                             Default value: /NOFULL_DUPLEX   G                             Devices: DEMFA, DEFAA, DEFEA, DEFPA, DEFTA, E                             DE425, DE434, DE435, DE436, DECchip 21040   D         /MAP=(MULTICAST_ADDRESS=address, FUNCTIONAL_ADDRESS=address)  I                                                  (continued on next page)                             I                     Local Area Network (LAN) Management Enhancements 6-13  L                 =         Table 6-5 (Cont.) LANCP SET DEVICE Command Qualifiers   '         Qualifier           Description   C                             Defines or deletes a functional addresseD                             mapping entry. Token Ring devices do notF                             support IEEE 802 standard globally definedG                             group addresses. They do support functionalnH                             addresses. A functional address is a locallyB                             administered group address that has 31D                             possible values. Each functional addressI                             sets one bit in the third through sixth bytesrE                             of the address, and bytes 1 and 2 are 03-_C                             00 (C0:00 in bit reversed format). ThiscE                             command maps a standard multicast addresst4                             to a functional address.  >                             The negated form of the qualifier,F                             /NOMAP=(MULTICAST_ADDRESS=address), clearsE                             the mapping established for the specified $                             address.  F                             Specify the functional address as follows:  I                             o  The MULTICAST_ADDRESS qualifier requires alA                                standard 6-byte multicast address.   H                             o  The FUNCTIONAL_ADDRESS qualifier requiresF                                only the last 4 bytes of the functionalE                                address (the preceding 03-00 bytes aret7                                automatically prefixed).n  I                             o  The variable address, given as hexadecimal D                                byte characters separated by hyphens,B                                specifies the canonical form of theD                                address. Use a colon as the separatorE                                character to indicate the bit-reversedN3                                form of the address.e  E                             For example, to map the multicast address G                             CB-00-01-02-03-04 to the functional address6F                             03-00-00-80-00-00 on the Token Ring device>                             IRA0, enter the following command:  F                             SET DEVICE IRA0/MAP=(MULTI=CB-00-01-02-03-1                             04,FUNCT=00:01:00:00)o  H                             Default value: See Table 6-6 for the defaultE                             address mapping or issue the command SHOWa3                             DEVICE/MAP device-name.n  7                             Devices: Token Ring devicesi  J                                                   (continued on next page)  =         6-14 Local Area Network (LAN) Management Enhancementso e  s              =         Table 6-5 (Cont.) LANCP SET DEVICE Command Qualifiers   '         Qualifier           Descriptiona  I         /MAX_               Sets the maximum number of receive buffers togG         BUFFERS=value       be allocated and used by the LAN driver foriH                             the LAN device. The value must be within theH                             range 4 to 32. The value cannot be less thanB                             the minimum number of receive buffers.  -                             Default value: 32N  3                             Devices: Any LAN devicee  I                                                  (continued on next page)N                                                            I                     Local Area Network (LAN) Management Enhancements 6-15o    i              =         Table 6-5 (Cont.) LANCP SET DEVICE Command Qualifiers   '         Qualifier           DescriptionY  8         /MEDIA=value        To set the /MEDIA qualifier:  E                             o  For Token Ring devices, this qualifieroF                                selects the type of cable media that isG                                being used to connect the adapter to theoE                                Token Ring Media Access Unit (MAU) foraG                                devices that do not automatically detectaF                                cable types. Acceptable values for thisC                                qualifier are either UTP (unshielded E                                twisted pair) or STP (shielded twisted %                                pair).t  1                                Default value: STP   H                             o  For Ethernet devices DE425, DE434, DE435,D                                DE436, DE500, and DECchip 21040, thisF                                qualifier selects the cable connection.E                                Normally, the selection is made duringgD                                device initialization using a limitedI                                autosensing algorithm that selects twistedoE                                pair, but fails over to AUI if twistednE                                pair does not appear to be functional. I                                Thereafter, a cabling change would requireAE                                a reboot of the system to take effect.tF                                This qualifier allows you to change theF                                selection without rebooting. AcceptableA                                values are AUI (10Base2, 10Base5),tC                                TWISTEDPAIR (10BaseT), and AUTOSENSE G                                (perform the limited autosense algorithm &                                again).  7                                Default value: AUTOSENSEp  E                                Note: Some devices, such as the DE435,dF                                require a jumper change on the EthernetI                                card to switch between 10Base2 and 10Base5wG                                (ThinWire and thickwire). Other devices,nG                                such as the DE434, DE436 and DE500, onlye=                                have twisted-pair connections.   F                             Devices: Any LAN device that has software-4                             settable media selection  I                                                  (continued on next page)   =         6-16 Local Area Network (LAN) Management Enhancements     a              =         Table 6-5 (Cont.) LANCP SET DEVICE Command Qualifiersa  '         Qualifier           Description   E         /MIN_               This qualifier sets the minimum number of G         BUFFERS=value       receive buffers to be allocated and used by H                             the LAN driver for the LAN device. The valueG                             must be within the range 4 to 32. The value H                             can not exceed the maximum number of receive$                             buffers.  -                             Default value: 32h  3                             Devices: Any LAN devicer  D         /SOURCE_ROUTING     Enables source routing on the Token RingE                             device. If you have only one ring in your D                             LAN or you use transparent bridging, useG                             the /NOSOURCE_ROUTING qualifier to turn off)+                             source routing.   :                             Default value: /SOURCE_ROUTING  7                             Devices: Token Ring devicesF  I                                                  (continued on next page)s                                      I                     Local Area Network (LAN) Management Enhancements 6-17m h  A              =         Table 6-5 (Cont.) LANCP SET DEVICE Command Qualifiersa  '         Qualifier           DescriptionE  F         /SPEED=value        Sets the speed of the LAN. For Token Ring,G                             valid values are either 4 or 16, indicatingLD                             4 megabits per second or 16 megabits perI                             second. For Ethernet, valid values are eitherNH                             10 or 100, which selects the 10 megabits perH                             second Ethernet port or the 100 megabits per5                             second FastEthernet port.   F                             Default value: The default value for TokenF                             Ring is 16 unless the LAN adapter supportsD                             a nonvolatile mechanism for setting thisA                             parameter (as does the DEC Token Ring B                             Controller 700). The default value forD                             Ethernet is to sense automatically whichD                             type of port is connected and select the.                             appropriate speed.  E                             Devices: Token Ring devices and the DE500a8                             Ethernet/FastEthernet device  I                                                  (continued on next page)                                         =         6-18 Local Area Network (LAN) Management Enhancements     E              =         Table 6-5 (Cont.) LANCP SET DEVICE Command Qualifiers   '         Qualifier           Description   ?         /SR_ENTRY=(LAN_ADDRESS=address, RI=routing-information)   G                             Statically defines a specific source routed H                             route for a specific node. This caching willF                             remain valid while used or until the aging*                             timer expires.  E                             The negated form of the qualifier, /NOSR_ C                             ENTRY=(LAN_ADDRESS=address), clears the C                             previously defined static source routed "                             route.  H                             The address is a standard 6-byte LAN address@                             given as hexadecimal byte charactersE                             separated by hyphens, which specifies thehH                             canonical form of the address. Using a colonD                             as the separator character indicates the=                             bit-reversed form of the address.   I                             The routing-information is the source routing D                             field, specified as a series of two-byteG                             hexadecimal characters (each byte separated F                             by a hyphen). The field consists of a two-E                             byte routing control field followed by upaD                             to 14 two-byte segment identifiers, eachE                             containing the ring number and the bridgeN3                             number used in the hop.   >                             Default value: No routes specified  E                             Note: Use this only as a last resort whenAH                             isolating communication failures on extended+                             LAN topologies.   7                             Devices: Token Ring devices   H               Table 6-6 lists the default address mapping for Token Ring               devices.      I                     Local Area Network (LAN) Management Enhancements 6-190 c  A              C         Table 6-6 Default Functional Address Mapping for Token Ring                    Devicesa  #         Multicast        Functional 5         Address          Address          Descriptiono  4         09-00-2B-00-     03-00-00-00-     ISO ALL ES         00-04            02-00  4         09-00-2B-00-     03-00-00-00-     ISO ALL IS         00-05            01-00  <         CF-00-00-00-     03-00-00-08-     Loopback Assistant         00-00            00-00  ;         AB-00-00-01-     03-00-02-00-     DNA MOP Dump/Load          00-00            00-00  @         AB-00-00-02-     03-00-04-00-     DNA MOP Remote Console         00-00            00-00  8         AB-00-00-03-     03-00-08-00-     DNA L1 Routers         00-00            00-00  8         09-00-2B-02-     03-00-08-00-     DNA L2 Routers         00-00            00-00  E         09-00-2B-02-     03-00-08-00-     DNA Phase IV Primary Router          01-0A            00-00  6         AB-00-00-04-     03-00-10-00-     DNA Endnodes         00-00            00-00  D         09-00-2B-02-     03-00-10-00-     DNA Phase IV Prime Unknown5         01-0B            00-00            Destination   @         09-00-2B-00-     03-00-20-00-     PCSA NETBIOS Emulation         00-07            00-00  C         09-00-2B-00-     03-00-40-00-     LAT Service Advertisement          00-0F            00-00  =         09-00-2B-02-     03-00-80-00-     LAT Service Solicit          01-04            00-00  F         09-00-2B-02-     03-00-00-02-     LAT Xwindown Service Solicit         01-07            00-00  .         09-00-2B-04-     03-00-00-04-     LAST         00-00            00-00  I                                                  (continued on next page)   =         6-20 Local Area Network (LAN) Management Enhancementse T  n              F         Table 6-6 (Cont.) Default Functional Address Mapping for Token&                           Ring Devices  #         Multicast        Functional I         Address          Address          Description____________________e  H         09-00-2B-02-     03-00-00-00-     DNA Name Service Advertisement         01-00            08-00  B         09-00-2B-02-     03-00-00-00-     DNA Name Service Solicit         01-01            10-00  :         09-00-2B-02-     03-00-00-00-     DNA Time Service         01-02            20-00  :         03-00-00-00-     03-00-00-00-     NETBUI Emulation         00-01            00-01  .         03-00-02-00-     03-00-02-00-     RIPL         00-00            00-00  C               The following shows some SET DEVICE command examples:   !               SET DEVICE Examplesr  J               1. LANCP> SET DEVICE/CONTENDER/MEDIA=UTP/NOEARLY/SOURCE ICA0  C                  This command enables monitor contention, UTP cable D                  media, and source routing, and disables early token4                  release for Token Ring device ICA0.  3               2. LANCP> SET DEVICE/MEDIA=TWIST EWB0   I                  This command sets the media type to twisted pair for thet.                  second Tulip Ethernet device.  5               3. LANCP> SET DEVICE/ALL/MIN_BUFFERS=12   H                  This command sets the number of receive buffers for all3                  LAN devices to be no less than 12.   ,         6.1.3.2 Displaying Device Parameters  H               The SHOW DEVICE command displays LAN device parameters. AtF               the LANCP> prompt, enter the command using the following               syntax:n  2               SHOW DEVICE device-name[/qualifiers]  I                     Local Area Network (LAN) Management Enhancements 6-21e n  x              +               In this command, you specify:e                 o  Device-name  H                  Supply the LAN controller device name. For example, youD                  can specify a DEMNA controller as either EXA, EXA0,B                  or EXA0:. This refers to the LAN template device,F                  which is maintained for most of the device parametersC                  and counters. Also, the device name can refer to a E                  device unit representing an actual user or protocol. F                  For example, the cluster protocol can be started on aE                  device as EWA1. You can specify device units to view 5                  unit-specific parameter information.   G                  If no device name is given, all devices are displayed.   H                  If a device name is specified, all matching LAN devicesE                  are displayed (for example, E to select all Ethernet,G                  devices, F for FDDI devices, I for Token Ring devices,O8                  and EW for Ethernet PCI Tulip devices).                 o  Qualifiersx  C                  See Table 6-7 for a description of the SHOW DEVICEt$                  command qualifiers.  F                 ________________________ Note ________________________  >                 If you do not specify a qualifier, the utility@                 displays the matching devices without additional                 information.  F                 ______________________________________________________  <               Table 6-7 LANCP SHOW DEVICE Command Qualifiers  '               Qualifier     Descriptiona  5               /COUNTERS     Displays device counters.d  F                             Devices: All LAN devices, template devices                              only  I                                                  (continued on next page)   =         6-22 Local Area Network (LAN) Management Enhancements                    D               Table 6-7 (Cont.) LANCP SHOW DEVICE Command Qualifiers  '               Qualifier     Description   E               /MAP          Displays the current configuration of the =                             functional address mapping table.   I                             Devices: Token Ring devices, template devices(                              only  I               /PARAMETERS   Displays status and related information about '                             the device.   4                             Devices: All LAN devices  I               /REVISION     Displays the current firmware revision of theqH                             adapter, if available or applicable. Not allD                             LAN devices return revision information.  F                             Devices: All LAN devices, template devices                              only  G               /SR_ENTRY     Displays the contents of the current source 0                             routing cache table.  G                             This data is displayed for template devices I                             only, regardless of the device specification.   I                             Devices: Token Ring devices, template devicese                              only  D               The following examples show how to use the SHOW DEVICE               command:  "               SHOW DEVICE Examples  1               1. LANCP> SHOW DEVICE/COUNTERS EXA0s                I                     Local Area Network (LAN) Management Enhancements 6-23                    %                 Device Counters EXA0:i+                              Value  Counterh+                              -----  ------- =                             259225  Seconds since last zeroed 8                            5890496  Data blocks received=                            4801439  Multicast blocks received 3                             131074  Receive failurea2                          764348985  Bytes received<                          543019961  Multicast bytes received0                                  3  Data overrun4                            1533610  Data blocks sentA                             115568  Multicast packets transmitted D                             122578  Blocks sent, multiple collisionsA                              86000  Blocks sent, single collision C                             189039  Blocks sent, initially deferreda.                          198120720  Bytes sent?                           13232578  Multicast bytes transmittedt0                            7274529  Send failureB                                  0  Collision detect check failureB                                  0  Unrecognized frame destination=                                  0  System buffer unavailabley;                                  0  User buffer unavailable   I                  This command displays counters for Ethernet device EXA0.   ,               2. LANCP> SHOW DEVICE/MAP ICA0                                      =         6-24 Local Area Network (LAN) Management EnhancementsI C  a              =                 Multicast to Functional Address Mapping ICA0:vH                    Multicast address   Functional Address   Bit-ReversedH                    -----------------   ------------------   ------------M                    09-00-2B-00-00-04   03-00-00-00-02-00    C0:00:00:00:40:00eM                    09-00-2B-00-00-05   03-00-00-00-01-00    C0:00:00:00:80:00iM                    CF-00-00-00-00-00   03-00-00-08-00-00    C0:00:00:10:00:00tM                    AB-00-00-01-00-00   03-00-02-00-00-00    C0:00:40:00:00:00eM                    AB-00-00-02-00-00   03-00-04-00-00-00    C0:00:20:00:00:00 M                    AB-00-00-03-00-00   03-00-08-00-00-00    C0:00:10:00:00:00 M                    09-00-2B-02-00-00   03-00-08-00-00-00    C0:00:10:00:00:00eM                    09-00-2B-02-01-0A   03-00-08-00-00-00    C0:00:10:00:00:003M                    AB-00-00-04-00-00   03-00-10-00-00-00    C0:00:08:00:00:00 M                    09-00-2B-02-01-0B   03-00-10-00-00-00    C0:00:08:00:00:00 M                    09-00-2B-00-00-07   03-00-20-00-00-00    C0:00:04:00:00:00 M                    09-00-2B-00-00-0F   03-00-40-00-00-00    C0:00:02:00:00:00aM                    09-00-2B-02-01-04   03-00-80-00-00-00    C0:00:01:00:00:00,M                    09-00-2B-02-01-07   03-00-00-02-00-00    C0:00:00:40:00:00tM                    09-00-2B-04-00-00   03-00-00-04-00-00    C0:00:00:20:00:00gM                    09-00-2B-02-01-00   03-00-00-00-08-00    C0:00:00:00:10:00oM                    09-00-2B-02-01-01   03-00-00-00-10-00    C0:00:00:00:08:00nM                    09-00-2B-02-01-02   03-00-00-00-20-00    C0:00:00:00:04:00 M                    03-00-00-00-00-01   03-00-00-00-00-01    C0:00:00:00:00:80 M                    03-00-02-00-00-00   03-00-02-00-00-00    C0:00:40:00:00:00   I                  This command displays mapping information for Token Ring                   device ICA0.   .               3. LANCP> SHOW DEVICE/PARAM IRA0                                  I                     Local Area Network (LAN) Management Enhancements 6-25m    n              '                 Device Parameters IRA0: -                              Value  Parameter -                              -----  ---------.3                             Normal  Controller mode :                           External  Internal loopback mode8                  00-00-93-58-5D-32  Hardware LAN address8                         Token Ring  Communication medium;                            Enabled  Functional address mode 6                                 No  Full duplex enable;                                 No  Full duplex operationale@                                 16  Line speed (megabits/second).                            16 Mbps  Ring speed.                                STP  Line media7                            Enabled  Early token release 5                           Disabled  Monitor contendero4                                200  SR cache entries6                                  2  SR discovery timer2                                 60  SR Aging Timer2                            Enabled  Source routing>                                  3  Authorized access priority5                  AA-00-04-00-92-FF  Upstream neighbor /                                  0  Ring numberr  G                  This command displays status and parameter information ,                  for Token Ring device IRA0.  1               4. LANCP> SHOW DEVICE/REVISION FXA0A/                 Device revision FXA0:  05140823   D                  This command displays revision information for FDDI                  device FXA0.i  1               5. LANCP> SHOW DEVICE/SR_ENTRY ICA0O  ,             Source Routing Cache Table ICA0:N                   LAN address      State    XmtTmo   RcvTmo  StaleTmo DiscvTmoN                -----------------   -----   -------- -------- -------- --------N                AA-00-04-00-92-FF   LOCAL   00000028 00000028 00000245 00000000  G                  This command displays source routing entry informationu,                  for Token Ring device ICA0.        =         6-26 Local Area Network (LAN) Management Enhancements                    /         6.1.3.3 Displaying Device Configuration   H               The SHOW CONFIGURATION command displays the LAN devices onG               the system. At the LANCP> prompt, enter the command using #               the following syntax:s                  SHOW CONFIGURATION  @               The following example shows the output from a SHOWG               CONFIGURATION command that was entered on a node that has 8               three LAN devices: two DE435s and a DETRA.  '               LANCP> SHOW CONFIGURATION                 LAN Configuration:C                  Device   Medium      Default LAN Address   Version C                  ------   ------      -------------------   ------- D                   EWA0    CSMA/CD      08-00-2B-E4-00-BF    02000023D                   EWB0    CSMA/CD      00-00-C0-92-A4-0D    02000023D                   IRA0    Token Ring   00-00-93-58-5D-32    20000223  F               The version is the device-specific representation of theE               actual version. In this example, for two devices on thehE               PCI bus, the actual version is in the low byte (2.3 fornI               the DE435 adapters). A device that does not have a readablec/               version is shown as version zero.   E               Consult your device-specific documentation to correlateaI               the version returned with a particular hardware or firmwareL+               implementation of the device.             6.1.3.4 Firmware Updates  H               LAN devices contain firmware images in EEPROM or FLASH ROMI               that you can update using the LANCP utility. You can updatelH               devices such as the DEMNA, DEMFA, DEFAA, DEFTA, DEFEA, and               DEFPA.  F                 ________________________ Note ________________________  E                 You can also use methods other than the LANCP utility D                 to update firmware. For example, you can use the LFUC                 update utility on DEC 7000 and DEC 10000 systems to /                 update DEMNA and DEMFA devices.i  F                 ______________________________________________________  I                     Local Area Network (LAN) Management Enhancements 6-27o h  d              I               At the LANCP> prompt, enter the UPDATE DEVICE command usinge#               the following syntax:e  =               UPDATE DEVICE device-name/FILE=filename[/RESET]t  /               In this command, you can specify:                  o  Device-name  H                  Supply the LAN controller device name. For example, youG                  can specify a DEMNA controller as either EXA, EXA0, orl                  EXA0:.                  o  FILE=filename  H                  Provide the file specification of the file to be loadedE                  into the device. The file consists of a 2 block filer>                  header followed by the binary firmware image.                 o  /RESET   D                  This is an optional qualifier. The default setting,G                  /RESET, indicates that the device will begin using the F                  new image when the firmware update completes. Use the>                  /NORESET qualifier to prevent a device reset.  I               For example, the following command updates FDDI device FAA0sI               with the firmware image FBUS_MAIN.SYS located on DKA0:[FW]. F               The device begins using the new image after the firmwareD               update has completed and a device reset has been done.  C               LANCP> UPDATE DEVICE FAA0/FILE=DKA0:[FW]FBUS_MAIN.SYS   /         6.1.4 LANACP Device Database Managementt  B               The LAN volatile and permanent device databases eachD               contain a single entry for each LAN device that existsB               on the system. Each entry in the LAN volatile deviceC               database contains device information and MOP downline H               load counters information. Each entry in the LAN permanentI               device database contains device information that is used toeG               populate the volatile database when the LANACP LAN Server0!               process is started.     =         6-28 Local Area Network (LAN) Management Enhancements                    A               Typically, each database contains the same devices.0E               However, the permanent database may contain entries for D               devices that have not yet been configured or installedD               in the system. The LANACP LAN Server process maintainsG               the volatile device database. The LANCP utility maintains F               the permanent device database. You can manipulate eitherI               database using the LANCP utility commands depending on your *               user privileges, as follows:  B               o  Privileged users can add or delete device entriesC                  from each database, enable or disable MOP downline-C                  load service, and clear MOP downline load counters0,                  information for LAN devices  I               o  Unprivileged users can view the MOP downline load status )                  and counters information   E               The following sections describe how to enter and remove @               devices from the LAN permanent and volatile deviceH               databases, and how to enable and disable MOP downline load               service.  >         6.1.4.1 Entering Devices into the LAN Device Databases  I               Use the following command syntax to enter a device into theiH               LAN permanent device database or to change device data for;               an entry that already exists in the database:1  4               DEFINE DEVICE device-name[/qualifiers]  I               Use the following command syntax to enter a device into the0G               LAN volatile device database or to change device data for0;               an entry that already exists in the database:0  1               SET DEVICE device-name[/qualifiers]V  -               In these commands, you specify:E                 o  Device-name  H                  Supply the LAN controller device name. For example, youG                  can specify a DEMNA controller as either EXA, EXA0, ordG                  EXA0:. To select all LAN devices, omit the device namee0                  and include the /ALL qualifier.                 o  QualifiersB  E                  See Table 6-8 for a description of the LANCP commando                  qualifiers.  I                     Local Area Network (LAN) Management Enhancements 6-29S                   1         Table 6-8 LANCP DEVICE Command Qualifiersf  '         Qualifier           Descriptionn  G         /ALL                Defines data for all LAN devices in the LAN E                             permanent or volatile device database. If D                             a device name is specified, all matchingD                             LAN devices are selected (for example, EF                             to select all Ethernet devices, F for FDDII                             devices, I for Token Ring devices, and EW fore8                             Ethernet PCI Tulip devices).    I                                                  (continued on next page)y                                                          =         6-30 Local Area Network (LAN) Management Enhancements     i              9         Table 6-8 (Cont.) LANCP DEVICE Command Qualifiersc  +         Qualifier               Description   >         /MOPDLL=(enable-option, exclusive-option, size-option,          knownclientsonly-option)B                             Provides the MOP downline load service4                             settings for the device.  F                             Note that defaults apply to creation of anH                             entry in the device database. If an existingI                             entry is being modified, fields not specifiedd,                             are not changed.  ?                             In this qualifier, you can specify:d  4                             o  Enable-option keyword  D                                Specify ENABLE or DISABLE to indicateG                                that MOP downline load service should beiB                                enabled or disabled for the device.  7                             o  Exclusive-option keywordl  D                                Specify EXCLUSIVE to indicate that noB                                other provider of MOP downline loadF                                service is allowed on the specified LANI                                device at the same time as LANACP. SpecifycF                                NOEXCLUSIVE to indicate that LANACP MOPE                                downline load service can coexist with D                                other implementations (in particular,F                                the DECnet Phase IV implementation thatI                                operates the MOP protocol in shared mode).   I                                                  (continued on next page)                                         I                     Local Area Network (LAN) Management Enhancements 6-31  u  i              9         Table 6-8 (Cont.) LANCP DEVICE Command Qualifiersn  I         Qualifier           Description__________________________________     >                             o  Knownclientsonly-option keyword  C                                Specify KNOWNCLIENTSONLY to indicate E                                that MOP downline load requests shouldrF                                be serviced only for clients defined inF                                the LANACP volatile node database. WhenE                                NOKNOWNCLIENTSONLY is selected, LANACPAE                                searches the LAN$DLL directory for any C                                images requested by clients that are F                                not defined in the LANACP volatile node(                                database.  *                             o  Size-option  D                                Use SIZE=value to specify the size inE                                bytes of the file data portion of each I                                downline load message. The permitted range F                                is 246 to 1482 bytes. Use a larger sizeC                                for better load performance and less F                                server overhead. Note that some clients?                                may not support the larger size. F                                basis. See Section 6.1.5.1 for details.  G                                The recommended size is the largest sizerF                                that results in successful loads of allF                                clients. The 1482 value is derived fromB                                the maximum packet size for CSMA/CDE                                (Ethernet) of 1518 bytes less the 802eeD                                header and CRC is 1492 bytes, less 10C                                bytes of MOP protocol overhead. This F                                leaves 1482 bytes as the maximum lengthE                                of the file data portion of a downline81                                load data message.   =                             Default values: /MOPDLL=(DISABLE, F                             NOEXCLUSIVE, SIZE=246, NOKNOWNCLIENTSONLY)  I                                                  (continued on next page)u  F         6-32 Local Area NetworkY(LAN)nManagementtEnhancements per-node                   9         Table 6-8 (Cont.) LANCP DEVICE Command Qualifiers   '         Qualifier           Descriptionl  A         /PERMANENT_         Updates the device entries in the LAN B         DATABASE (SET       volatile device database with any dataD         command only)       currently set in the permanent database.B                             This allows you to update the volatileI                             database after changing data in the permanentoH                             database, rather than repeating the commandsG                             for each updated entry to apply the changes-5                             to the volatile database.-  @         /UPDATE             Adds existing LAN devices to the LANF                             permanent or volatile device database that>                             are not currently in the database.  A         /VOLATILE_          Updates the device entries in the LAN0C         DATABASE (DEFINE    permanent device database with any data0H         command only)       currently set in the volatile database. ThisG                             allows you to update the permanent database0I                             after changing data in the volatile database,AG                             rather than repeating the commands for each4E                             updated entry to apply the changes to the-/                             permanent database.:                                        I                     Local Area Network (LAN) Management Enhancements 6-33- 0  F              F               The following examples show how to use the DEFINE DEVICE&               and SET DEVICE commands:  3               DEFINE DEVICE and SET DEVICE Examples   D               1. LANCP> DEFINE DEVICE EXA0/MOPDLL=(ENABLE,EXCLUSIVE)  ?                  This command defines LAN device EXA0 to enable >                  LANACP MOP downline load service in exclusiveD                  mode. The settings of the KNOWNCLIENTSONLY and SIZEE                  characteristics are not changed. If the device entry E                  does not currently exist in the LAN permanent device8F                  database, these settings will be set to the defaults.  <               2. LANCP> DEFINE DEVICE/ALL/MOPDLL=NOEXCLUSIVE  E                  This command sets all LAN devices defined in the LAN C                  permanent device database to nonexclusive mode for 2                  LANACP MOP downline load service.  C               3. LANCP> SET DEVICE EXA0/MOPDLL=(ENABLE,NOEXCLUSIVE)mA                 LANCP> SET DEVICE FXA0/MOPDLL=(ENABLE,EXCL,KNOWN)   G                  These commands enable LANACP MOP downline load servicel                  for:   8                  o  LAN device EXA0 in nonexclusive mode  D                  o  LAN device FXB0 in exclusive mode for only known                     clientso  >         6.1.4.2 Displaying Devices in the LAN Device Databases  @               Use the following command syntax to display device?               information in the LAN permanent device database:   .               LIST DEVICE device-name[/MOPDLL]  @               Use the following command syntax to display device>               information in the LAN volatile device database:  .               SHOW DEVICE device-name[/MOPDLL]  -               In these commands, you specify:                  o  Device-name  H                  Supply the LAN controller device name. For example, youG                  can specify a DEMNA controller as either EXA, EXA0, or                   EXA0:.   =         6-34 Local Area Network (LAN) Management Enhancements     -              G                  If no device name is given, all devices are displayed.   H                  If a device name is specified, all matching LAN devicesE                  are displayed (for example, E to select all EthernetHG                  devices, F for FDDI devices, I for Token Ring devices, 8                  and EW for Ethernet PCI Tulip devices).                 o  /MOPDLL  7                  Display MOP downline load information.R  F                 ________________________ Note ________________________  >                 If you do not specify a qualifier, the utility@                 displays the matching devices without additional                 information.  F                 ______________________________________________________  >         6.1.4.3 Deleting Devices from the LAN Device Databases  F               Use the following command syntax to delete a device from0               the LAN permanent device database:  ,               PURGE DEVICE device-name[/ALL]  F               Use the following command syntax to delete a device from/               the LAN volatile device database:t  ,               CLEAR DEVICE device-name[/ALL]  -               In these commands, you specify:                  o  Device-name  H                  Supply the LAN controller device name. For example, youG                  can specify a DEMNA controller as either EXA, EXA0, oreG                  EXA0:. To select all LAN devices, omit the device nameG0                  and include the /ALL qualifier.                 o  /ALLm  D                  Deletes all LAN devices in the LAN permanent deviceF                  database. If a device name is specified, all matchingG                  LAN devices are selected (for example, E to select all0G                  Ethernet devices, F for FDDI devices, I for Token Ring0A                  devices, and EW for Ethernet PCI Tulip devices).-  I               The following examples show how to use the PURGE DEVICE and,$               CLEAR DEVICE commands:  I                     Local Area Network (LAN) Management Enhancements 6-35  3  d              4               PURGE DEVICE and CLEAR DEVICE Examples  (               1. LANCP> PURGE DEVICE/ALL  H                  This command deletes all devices from the LAN permanent!                  device database.l  )               2. LANCP> CLEAR DEVICE EXA0m  G                  This command deletes device EXA0 from the LAN volatile !                  device database.e  2         6.1.4.4 Enabling MOP Downline Load Service  E               Use the following command syntax to enable MOP downlineh               load service:D  2               SET DEVICE device-name/MOPDLL=ENABLE  F               In this command, use the device-name parameter to supply-               the LAN controller device name.C  D               See Section 6.1.4.1 for a complete description of this               command.  3         6.1.4.5 Disabling MOP Downline Load Service   F               Use the following command syntax to disable MOP downline               load service:_  3               SET DEVICE device-name/MOPDLL=DISABLEt  F               In this command, use the device-name parameter to supply-               the LAN controller device name.C  D               See Section 6.1.4.1 for a complete description of this               command.  -         6.1.5 LANACP Node Database Management   H               The LAN volatile and permanent node databases each containI               a single entry for each defined LAN node. Each entry in the F               LAN volatile node database contains node information andG               MOP downline load counters information. Each entry in thetH               LAN permanent node database contains node information thatG               is used to populate the volatile database when the LANACPl,               LAN Server process is started.  =         6-36 Local Area Network (LAN) Management Enhancementsr h  e              C               Typically, each database contains the same nodes. The C               LANACP LAN Server process maintains the volatile nodeUF               database. The LANCP utility maintains the permanent nodeD               database. You can manipulate either database using theG               LANCP utility commands depending on your user privileges,A               as follows:   E               o  Privileged users can add or delete node entries fromeD                  each database, and clear MOP downline load counters*                  information for LAN nodes  I               o  Unprivileged users can view the node information and MOPh>                  downline load status and counters information  E               The following sections describe how to enter and removenG               nodes from the LAN permanent and volatile node databases.e  :         6.1.5.1 Entering Nodes into the LAN Node Databases  I               Use the following command syntax to define node informationi1               in the LAN permanent node database:d  0               DEFINE NODE node-name[/qualifiers]  I               Use the following command syntax to define node information-0               in the LAN volatile node database:  -               SET NODE node-name[/qualifiers],  -               In these commands, you specify:                  o  Node-name  B                  Specify the node name, using up to 63 characters,F                  associated with the node address. You can include theG                  name of the LAN device in the node name to distinguishaE                  between multiple LAN devices on the same system. FortD                  example, use GALAXY_EXA, GALAXY_EXB, and GALAXY_FXAE                  to distinguish between the three LAN devices on nodea                  GALAXY.  I                  If a node name is specified with the /ALL qualifier, all H                  matching nodes are selected. For example, A/ALL selects,                  all nodes beginning with A.                 o  QualifiersL  E                  See Table 6-9 for a description of the LANCP commandn                  qualifiers.  I                     Local Area Network (LAN) Management Enhancements 6-37     e              /         Table 6-9 LANCP NODE Command Qualifiersa  '         Qualifier           Description,  E         /ADDRESS=node-      Specifies a unique LAN address associated F         address             with the node name. Specify the address asF                             6 bytes in hexadecimal notation, separatedG                             by hyphens. The address does not have to be I                             unique (as might be the case when the address E                             is not known, so a nonexistent address iswI                             specified). The default is 00-00-00-00-00-00.d  H                             If the qualifier is not present, the settingD                             will not be changed. You can specify theD                             /NOADDRESS qualifier to clear the field.  A         /ALL                Defines data for all nodes in the LANlE                             permanent or volatile node database. If acF                             node name is specified, all matching nodesH                             are selected. For example, A/ALL selects all3                             nodes beginning with A.   6         /BOOT_TYPE=VAX_SATELLITE|ALPHA_SATELLITE|OTHER  E                             Indicates the type of processing requiredtD                             for downline load requests. The downlineH                             load can be for a VAX satellite cluster bootG                             (VAX_SATELLITE), an Alpha satellite clustervD                             boot (ALPHA_SATELLITE), or the specifiedG                             image (OTHER). The distinction is necessarydH                             because cluster satellite loads require thatG                             additional cluster-related data be appended D                             to the load image indicated by the /FILEB                             qualifier. The default value is OTHER.  H                             If the qualifier is not present, the settingH                             will not be changed. Use the /NOBOOT_TYPE to,                             clear the field.  I                                                  (continued on next page)a          =         6-38 Local Area Network (LAN) Management Enhancements  P  =              7         Table 6-9 (Cont.) LANCP NODE Command Qualifiersy  '         Qualifier           Descriptiond  I         /FILE=file-         Supplies the file name you want provided wheneH         specification       the downline load request does not include aG                             requested file name. The file specification 9                             is limited to 127 characters.e  F                             If the /FILE qualifier is not present, theH                             setting will not be changed. Use the /NOFILE9                             qualifier to clear the field.   F         /ROOT=directory-    Supplies the directory specification to beF         specification       associated with the file name. For clusterB                             satellite service, the /ROOT qualifierC                             specifies the satellite root directory. B                             For noncluster service, this qualifierF                             specifies the location of the file. If theH                             file specification or the file name given inI                             the boot request includes the directory name, D                             this qualifier is ignored. The directoryG                             specification is limited to 127 characters.   H                             If you do not specify a /ROOT qualifier, theF                             setting remains unchanged. Use the /NOROOT7                             qualifier to clear a field.   @         /SIZE=value         Overrides the default load data sizeF                             specified for the device. This is the sizeE                             in bytes of the file data portion of each I                             downline load message. The permitted range is D                             246 to 1482 bytes. Use a larger size forC                             better load performance and less server B                             overhead. See Section 6.1.4.1 for more$                             details.  H                             If you do not specify a /SIZE qualifier, theF                             setting remains unchanged. Use the /NOSIZE;                             qualifier to clear the setting.O  I                                                  (continued on next page)       I                     Local Area Network (LAN) Management Enhancements 6-39a r               7         Table 6-9 (Cont.) LANCP NODE Command Qualifierse  '         Qualifier           Description   D         /V3                 Forces the server to respond to only MOPC                             Version 3 boot requests from this node. G                             This qualifer may be used to resolve a load I                             problem where the node does not implement MOP @                             Version 4 correctly and cannot boot.  F                             If you do not specify a /V3 qualifier, theD                             setting remains unchanged. Use the /NOV3;                             qualifier to clear the setting.   I         /VOLATILE_          Updates the node entries in the LAN permanent E         DATABASE (DEFINE    node database with any data currently set H         command only)       in the volatile database. This allows you toH                             update the permanent database after changingF                             data in the volatile database, rather thanC                             repeating the commands for each updated G                             entry to apply the changes to the permanent %                             database.   H         /PERMANENT_         Updates the node entries in the LAN volatileH         DATABASE (SET       node database with any data currently set inF         command only)       the permanent database. This allows you toG                             update the volatile database after changingLG                             data in the permanent database, rather than C                             repeating the commands for each updatedeF                             entry to apply the changes to the volatile%                             database.a                            =         6-40 Local Area Network (LAN) Management Enhancementsp e  h              H               The following examples show how to use the DEFINE NODE and                SET NODE commands:  /               DEFINE NODE and SET NODE Examples   ?               1. DEFINE NODE GALAXY/ADDRESS=08-00-2B-11-22-33 - 8                                   /FILE=NISCS_LOAD.EXE -<                                   /ROOT=$64$DIA14:<SYS10.> -:                                   /BOOT_TYPE=VAX_SATELLITE  F                  This command sets up node GALAXY in the LAN permanentD                  node database for booting as a VAX satellite into a#                  VMScluster system.   <                  The NISCS_LOAD.EXE file is actually located<                  on $64$DIA14: <SYS10.SYSCOMMON.SYSLIB>. TheH                  <SYSCOMMON.SYSLIB> is supplied by the LANACP LAN ServerD                  process and is not included in the root definition.  ?               2. DEFINE NODE ZAPNOT/ADDRESS=08-00-2B-11-22-33 - 1                                   /FILE=APB.EXE -e<                                   /ROOT=$64$DIA14:<SYS10.> -<                                   /BOOT_TYPE=ALPHA_SATELLITE  I                  This command sets up node ZAPNOT for booting as an Alphan4                  satellite into a VMScluster system.  8                  The APB.EXE file is actually located on>                  $64$DIA14:<SYS10.SYSCOMMON.SYSEXE>. Note thatH                  <SYSCOMMON.SYSEXE> is supplied by the LANACP LAN ServerD                  process and is not included in the root definition.  <               3. SET NODE CALPAL/ADDRESS=08-00-2B-11-22-33 -/                               /FILE=APB_061.EXEM  @                  This command sets up node CALPAL for booting anB                  InfoServer image. It defines the file that shouldE                  be loaded when a load request without a file name isL+                  received from node CALPAL.r  >                  Because the file does not include a directoryI                  specification, the logical name LAN$DLL defines where tosH                  locate the file. You could give directory specificationH                  by using the file name or by using the /ROOT qualifier.  I                     Local Area Network (LAN) Management Enhancements 6-41a t  o              E                  Note that specifying the file name explicitly in the F                  boot command overrides the file name specified in the%                  node database entry.L  <         6.1.5.2 Displaying Devices in the LAN Node Databases  >               Use the following command syntax to display node=               information in the LAN permanent node database:   '               LIST NODE node-name[/ALL]n  >               Use the following command syntax to display node<               information in the LAN volatile node database:  '               SHOW NODE node-name[/ALL]e  -               In these commands, you specify:d                 o  Node-name  D                  Supply the node name. If no node name is given, all%                  nodes are displayed.                                               =         6-42 Local Area Network (LAN) Management Enhancements                                   o  /ALL   D                  Displays data for all nodes in the LAN permanent orI                  volatile node database. If a node name is specified, allcH                  matching nodes are selected. For example, A/ALL selects,                  all nodes beginning with A.  :         6.1.5.3 Deleting Nodes from the LAN Node Databases  H               Use the following command syntax to delete a node from the*               LAN permanent node database:  (               PURGE NODE node-name[/ALL]  H               Use the following command syntax to delete a node from the)               LAN volatile node database:d  (               CLEAR NODE node-name[/ALL]  +               In this command, you specify:y                 o  Node-name  &                  Supply the node name.                 o  /ALL_  G                  Deletes all LAN nodes in the LAN permanent or volatile I                  node database. If a node name is specified, all matching I                  nodes are selected. For example, A/ALL deletes all nodes_*                  whose name begins with A.  9         6.1.6 LANACP MOP Downline Load Service Managementh  F               The LANACP LAN Server process maintains the LAN volatileC               node and device databases. The LANCP utility provides/               commands that:  >               o  Display MOP downline load status and counters                  information  +               o  Clear counters informationL  E               o  Enable or disable OPCOM messages and packet tracing.D  I               Counters and status information is maintained for each nodemG               and device. Counters information includes transmitted andEG               received byte and packet counts, transmit errors, logicaliI               errors such as protocol violations and timeouts, and number I               of load requests. Status includes the time of the last loade.               and the status of the last load.  I                     Local Area Network (LAN) Management Enhancements 6-43e p                 7         6.1.6.1 Displaying the Status and Counters Data,  F               Use the following command syntax to display MOP downline               load status:                 SHOW MOPDLL   D               The following display shows counters information for a               particular node.      LAN MOP DLL Status:M      EXA enabled in exclusive mode for known nodes only, data size 1482 bytesD      FXA disabled   L           #Loads   Packets        Bytes     Last load time       Last loadedP           ------   -------        -----  --------------------  -----------------D      EXA      5      1675      4400620  23-SEP-1994 10:27.51  GALAXY&      FXA      0         0            0  F               On this node, there are two LAN devices, EXA (DEMNA) andI               FXA (DEMFA). MOP downline load service is enabled on EXA ine               exclusive mode.o  F               Requests are answered only for nodes that are defined inG               the LANACP node database. The image data size in the load C               messages is 1482 bytes. There have been five downline B               loads, the last one occured on node GALAXY at 10:27.D               Finally, there are no recorded downline loads for FXA,D               which is currently disabled for downline load service.  I               Use the following command syntax to display recent downline I               load activity that has been logged in the LAN$ACP.LOG file:                  SHOW LOG  *         6.1.6.2 Clearing the Counters Data  I               Use the following command syntax to clear MOP downline load 1               counters for all nodes and devices:                  CLEAR MOPDLL  F         6.1.6.3 Displaying the Status and Counters Data for Individual                 Nodest  F               Use the following command syntax to display MOP downlineB               load information for nodes in the LAN permanent node               database:   @               LIST NODE node-name[/ALL][/OUTPUT=commandfilename]  =         6-44 Local Area Network (LAN) Management EnhancementsC                   F               Use the following command syntax to display MOP downlineG               load status and counters information for nodes in the LAN %               volatile node database:   H               SHOW NODE node-name[/ALL][/OUTPUT=commandfilename][/TOTAL]  1               In these commands, you can specify:m                 o  Node-name  E                  Specify the node name. The name can include up to 63tG                  characters associated with the node address. If a nodeoH                  is not specified, the /ALL qualifier is assumed. If youI                  use the /ALL qualifier, the node name is ignored and all %                  nodes are displayed.d                 o  /ALLp  C                  Display information for all nodes in the database.   (               o  /OUTPUT=commandfilename  C                  Indicate that the output should be directed to themD                  specified file in the form of a list of DEFINE NODEH                  or SET NODE commands. The resulting command file can be7                  used to create the LAN node databases.n  0               o  /TOTAL (SHOW NODE command only)  -                  Display counter totals only.e  D               The following shows sample output from a node on whichI               there are three nodes defined (GALAXY, ZAPNOT, and CALPAL). 4               CALPAL has received two load requests:  G               o  The first request is the multicast request that CALPAL &                  volunteered to accept  H               o  The second request is the load request sent directly toG                  CALPAL for the actual load data. The elapsed time fromnF                  the second load request to completion of the load was                  6.65 seconds.                 Node Listing:E  )               GALAXY (08-00-2B-2C-51-28): .                 MOP DLL:  Load file:   APB.EXE9                           Load root:   $64$DIA24:<SYS11.> 6                           Boot type:   Alpha satellite  I                     Local Area Network (LAN) Management Enhancements 6-45                        ZAPNOT (08-00-2B-18-7E-33):*      MOP DLL:  Load file:   NISCS_LOAD.EXE3                Load root:   LAVC$SYSDEVICE:<SYS10.> )                Boot type:   VAX satellite          CALPAL (08-00-2B-08-9F-4C):)      MOP DLL:  Load file:   READ_ADDR.SYS 0                Last file:   LAN$DLL:APB_X5WN.SYS!                Boot type:   Otheri/                2 loads requested, 1 volunteered $                1 succeeded, 0 failedD                Last request was for a system image, in MOP V4 formatO                Last load initiated 30-OCT-1994 09:11:17 on EXA0 for 00:00:06.65 >                527665 bytes, 4161 packets, 0 transmit failures      Unnamed (00-00-00-00-00-00):m  
    Totals:      Requests received    2       Requests volunteered 1o      Successful loads     1i      Failed loads         0       Packets sent         2080      Packets received     2081       Bytes sent           523481      Bytes received       4184;      Last load            CALPAL at 30-OCT-1994 09:11:17.29t           6.1.6.4 OPCOM Messages  B               By default, OPCOM messages are enabled. Messages areF               generated by the LANACP LAN Server process when a deviceC               status changes, load requests are received, and loadsoF               complete. These messages are displayed on the operator'sE               console and included in the log file written by LANACP, &               SYS$MANAGER:LAN$ACP.LOG.  A               Use the following command to enable OPCOM messages:                  SET ACP/OPCOMs  B               Use the following command to disable OPCOM messages:                 SET ACP/NOOPCOM   =         6-46 Local Area Network (LAN) Management Enhancements                    #         6.1.6.5 Load Trace Facilitye  A               If the error data produced by the LANACP LAN ServeriF               process for a load request is not sufficient to help youC               determine why the load is failing, you can direct theuD               server process to record trace data. The data consistsB               of transmit and receive packet information for everyE               transmit and receive done by the server, and written toeH               a log file for each load attempt. The name of the log fileH               is SYS$MANAGER:LAN$nodename.LOG. You can record either allD               packet data or only the first 32 bytes of each packet.  E               The following list describes the typical load sequence:   I               1. Receive a Program Request message on the Load Assistance D                  Multicast Address from the requesting node, code 8.  @               2. Transmit an Assistance Volunteer message to the)                  requesting node, code 3.d  G               3. Receive a Program Request message on your node addressc2                  from the requesting node, code 8.  F               4. Transmit a Memory Load message to the requesting node3                  with sequence number zero, code 2./  E               5. Receive a Request Memory Load message requesting theiF                  next sequence number (modulo 256), code 10 (decimal).  D               6. Repeat steps 4 and 5 until there is no more data to                  send.  B               7. Transmit a Memory or Parameter Load with Transfer9                  Address message, code 0 or 20 (decimal).T  G               8. Receive a final Request Memory Load message requestingoF                  the next sequence number (modulo 256) indicating thatG                  the last message has been received, code 10 (decimal).   G               For cluster satellite loads, the last Memory Load message E               contains cluster parameters. This message and the final G               Load with Transfer Address messages are displayed in full ?               even if only partial trace echo has been enabled.e  H               Note that packet tracing significantly slows downline loadF               operations for all requests and may result in very largeG               LAN$ACP.LOG files if packet tracing is inadvertently left                enabled.  I                     Local Area Network (LAN) Management Enhancements 6-47h e  e              D               Use the following command to enable partial tracing of               packet data:                 SET ACP/ECHO  H               Use the following command to enable full tracing of packet               data:                  SET ACP/ECHO/FULLa  D               Use the following command to disable tracing of packet               data:                  SET ACP/NOECHO  '         6.1.7 LANCP MOP Console Carrierf  B               Console carrier provides a mechanism to connect to aD               LAN device, such as a terminal server, that implementsB               a management interface using the MOP console carrierG               protocol. The LANCP utility provides this function in the -               form of a CONNECT NODE command.s  $               The command syntax is:  8               CONNECT NODE node-specification/qualifiers  +               In this command, you specify:   #               o  Node-specificationd  G                  Supply either the node name or the node address of the C                  target node. If you supply the node name, the nodelC                  address is obtained via lookup of the node name inoG                  the LAN volatile node database. If you supply the nodenG                  address, the corresponding node need not be defined inf0                  the LAN volatile node database.                 o  Qualifiers   F                  See Table 6-10 for a description of the LANCP command                  qualifiers.      =         6-48 Local Area Network (LAN) Management Enhancementst s  i              8         Table 6-10 LANCP CONNECT NODE Command Qualifiers  $         Qualifier        Description  G         /DEVICE=device-  Specifies the LAN controller device name to be F         name             used for the connection. For example, a DEMNAF                          controller, EXA, is specified as EXA, EXA0 or                          EXA0:.c  F         /DISCONNECT=     Specifies the disconnect character that LANCPC         disconnect-      will recognize to terminate the connection C         character        to the remote node. The default disconnectnD                          character is D, which indicates that a CtrlD                          /D will terminate the connection. Any ASCIII                          character is allowed from @ through Z, except C,t>                          M, Q, S, Y, and the left bracket ([).  C         /PASSWORD=16hexdiSpecifies the password to be used when thehE                          connection is initiated, in hexadecimal. For I                          example, /PASSWORD=0123456789ABCDEF. The default F                          password is zero. You can omit leading zeros.  E         /V3 or /V4       Allows override of the MOP format. Normally,IE                          LANCP determines the format by sending a MOPDF                          Request ID message in MOP Version 4 format toG                          the remote node, waiting for a response. If no-G                          response is received, LANCP sends a message in G                          MOP Version 3 format and waits for a response. G                          The LANCP utility repeats this process several D                          times until a response is received. You can,                          specify the format:  D                          o  To allow connection to nodes that do not7                             support Request ID messagess  G                          o  As a means of getting around implementationE<                             problems with one of the formats  I         _________________________________________________________________:  E               The following examples show how to use the CONNECT NODE                command:  #               CONNECT NODE Examples   0               1. CONNECT NODE GALAXY/DEVICE=EWA0  F                  This command attempts a console-carrier connection to<                  node GALAXY using the Ethernet device EWA0.  I                     Local Area Network (LAN) Management Enhancements 6-49                      O         2. CONNECT NODE 08-00-2B-11-22-33/DEVICE=EWA0/PASSWORD=0123456789ABCDEFA  F                  This command attempts a console-carrier connection toG                  the given node address using the Ethernet device EWA0, !                  with a password.   $         6.1.8 LANCP MOP Trigger Boot  C               Some systems recognize and respond to MOP remote boot E               requests. These systems typically require a password or D               other mechanism to prevent unwanted boot requests fromB               triggering a reboot of the system. The LANCP utilityD               provides this function in the form of the TRIGGER NODE               command.  /               Use the following command syntax:r  8               TRIGGER NODE node-specification/qualifiers  /               In this command, you can specify:   #               o  Node-specification   G                  Supply either the node name or the node address of the C                  target node. If you supply the node name, the node C                  address is obtained via lookup of the node name intG                  the LAN volatile node database. If you supply the nodeaG                  address, the corresponding node need not be defined in 0                  the LAN volatile node database.                              =         6-50 Local Area Network (LAN) Management EnhancementsL                                    o  Qualifiers   F                  See Table 6-11 for a description of the LANCP command                  qualifiers.  8         Table 6-11 LANCP TRIGGER NODE Command Qualifiers  $         Qualifier        Description  G         /DEVICE=device-  Specifies the LAN controller device name to be I         name             used for sending the boot messages. For example, F                          a DEMNA controller, EXA, is specified as EXA,'                          EXA0 or EXA0:.n  C         /PASSWORD=16hexdiSpecifies the password to be used when thenE                          connection is initiated, in hexadecimal (foroB                          example, /PASSWORD=0123456789ABCDEF). TheG                          default password is zero. You can omit leading                           zeros.]  H               Rather than specify the format to send MOP Version 3 or 4,G               the LANCP utility sends one message in each format to then               target node.  E               The following examples show how to use the TRIGGER NODE                command:  #               TRIGGER NODE Examples   0               1. TRIGGER NODE GALAXY/DEVICE=EWA0  E                  This command sends MOP trigger boot messages to nodec3                  GALAXY using Ethernet device EWA0.c  O         2. TRIGGER NODE 08-00-2B-11-22-33/DEVICE=EWA0/PASSWORD=0123456789ABCDEF   D                  This command sends MOP trigger boot messages to theH                  given node address using the Ethernet device EWA0, with$                  indicated password.          I                     Local Area Network (LAN) Management Enhancements 6-51P w  n              +         6.1.9 LANCP Miscellaneous Functions   I               Use the SPAWN command to create a subprocess of the currentsB               process. The SPAWN command copies the context of theE               subprocess from the current process. The syntax for thee*               SPAWN command is as follows:  +               SPAWN [optional command line]t  I               You can set up the LANCP utility to execute commands from alI               command file. The LANCP utility recognizes the command filecF               as the file name preceded by an at sign (@). The default*               file name extension is .COM.  )         6.2 The LANACP LAN Server Processp  H               The LANACP Server process provides the following services:  >               o  Maintenance of the LAN volatile node database  @               o  Maintenance of the LAN volatile device database  "               o  MOP downline load  G               Table 6-12 describes the logical name and a collection ofMB               files associated with the LANACP LAN Server process.  +               Table 6-12 The LANACP Utility   6               Component                    Description  D               LAN$ACP system logical       This logical name definesA               name                         the name of the LANACP6C                                            Server process log file, H                                            containing entries describingG                                            changes to the LAN permanentAE                                            device and node databases,eD                                            and load request and loadA                                            status information. ByiF                                            default, this is defined asL                                            SYS$SPECIFIC:[SYSMGR]LAN$ACP.LOG.  I                                                  (continued on next page)o    =         6-52 Local Area Network (LAN) Management Enhancements  t  t              3               Table 6-12 (Cont.) The LANACP Utilitye  6               Component                    Description  D               LAN$DEVICE_DATABASE system   This logical name definesC               logical name                 the name of the LAN per- E                                            manent device database. By F                                            default, this is defined asK                                            SYS$SPECIFIC:[SYSEXE]LAN$DEVICE_p8                                            DATABASE.DAT.  D               LAN$DLL system logical       This logical name definesH               name                         the location of downline loadG                                            files, where the location of F                                            the file is not provided inI                                            the load request or explicitly F                                            defined in the LAN volatileE                                            node database. By default,cB                                            this will be defined asB                                            MOM$SYSTEM. When DECnetC                                            is used for MOP downline D                                            loading, it is defined asD                                            SYS$SYSROOT:[MOM$SYSTEM].  D               LAN$NODE_DATABASE system     This logical name defines>               logical name                 the name of the LANF                                            permanent node database. ByF                                            default, this is defined asG                                            SYS$COMMON:[SYSEXE]LAN$NODE_a8                                            DATABASE.DAT.  F               SYS$MANAGER:SYSTARTUP_       This file contains an entryD               VMS.COM                      that may be used to startI                                            LANACP automatically at system 3                                            startup.,  F               SYS$STARTUP:LAN$STARTUP.COM  This file starts the LANACP:                                            server process.  E               SYS$SYSTEM:LANACP.EXE        This is the LANACP utilitye3                                            program.       I                     Local Area Network (LAN) Management Enhancements 6-53                    (         6.2.1 Running the LANACP Process  :               To start the LANACP LAN Server process, typeD               @SYS$STARTUP:LAN$STARTUP at the DCL prompt, or includeI               this line in the SYS$MANAGER:SYSTARTUP_VMS.COM command file<>               to start LANACP automatically at system startup.  C               The following shows the command line as it appears ins,               SYS$MANAGER:SYSTARTUP_VMS.COM:       $!O     $! To start the LANACP LAN server application, remove the comment delimiterC#     $! from the command line below.B     $!     $! @SYS$STARTUP:LAN$STARTUP      $!  4         6.2.2 Stopping the LANACP LAN Server Process  F               To stop the LANACP LAN Server process, enter the SET ACP8               /STOP command at the LANCP utility prompt.  *         6.3 LAN MOP Downline Load Services  G               The collection of utilities and startup command files for F               LANCP and LANACP provide the necessary functionality forG               MOP downline load service. These utilities and files loadnI               cluster satellites, terminal servers, and systems requiring E               downline load of special images, such as console updatedE               images or system software update images (for Infoserver                load).  E               This environment provides functionality that is similar E               to that provided by DECnet. The result is that a system G               manager can choose which functionality to use, DECnet MOP E               or LAN MOP. For VMScluster systems, LAN MOP permits the G               operation of a VMScluster without the presence of DECnet.   )         6.3.1 Coexistence with DECnet MOPo  H               LAN MOP can coexist with DECnet MOP in the following ways:  -               o  Running on different systemsO  F                  For example, DECnet MOP service is enabled on some ofG                  the systems on the LAN and LAN MOP is enabled on other                   systems.   D               o  Running on different LAN devices on the same system  =         6-54 Local Area Network (LAN) Management Enhancements  d  a              I                  For example, DECnet MP service is enabled on a subset of G                  the available LAN devices on the system and LAN MOP is *                  enabled on the remainder.  F               o  Running on the same LAN device on the same system but?                  targeting a different set of nodes for servicea  I                  For example, both DECnet MOP and LAN MOP are enabled butiH                  LAN MOP has limited the nodes to which it will respond.C                  This allows DECnet MOP to respond to the remainingr                  nodes.   2         6.3.2 Migrating from DECnet MOP to LAN MOP  8               To migrate to LAN MOP, follow these steps:  D               1. Decide which nodes are to provide MOP downline loadI                  service. These may be the same nodes that currently havei,                  service enabled for DECnet.  I               2. Populate the LAN permanent device database by typing MCRe>                  LANCP DEFINE DEVICE/UPDATE at the DCL prompt.  E               3. Populate the LAN permanent node database by entering D                  a node definition for each of the cluster satelliteE                  nodes and any other nodes that are similarly defined.@                  in the DECnet node database. You can enter this?                  data manually or execute the command procedure H                  SYS$EXAMPLES:LAN$POPULATE.COM, following the directions#                  and help provided.T  H               4. Disable service on each of the DECnet circuits where it?                  is currently enabled in the volatile database.n  G               5. Enable service on each LAN device in the LAN permanentnI                  device database that you would like to use by typing MCRaI                  LANCP DEFINE DEVICE device-name/MOPDLL=ENABLE at the DCL (                  prompt for each device.  G               6. If high performance is required, select a data size of F                  1482 bytes and only reduce this if some load requestsI                  now fail. Alternatively, set up one system to load those D                  clients that require a small data size and set up a<                  different system to load the other clients.  :               7. Start the LANACP server process by typing<                  @SYS$STARTUP:LAN$STARTUP at the DCL prompt.  I                     Local Area Network (LAN) Management Enhancements 6-55        s            9               To migrate permanently, follow these steps:k  F               1. Disable service on each of the DECnet circuits in the$                  permanent database.  F               2. Edit SYS$MANAGER:SYSTARTUP_VMS.COM to start LANACP at                   system startup.  @               To migrate back to DECnet MOP, follow these steps:  F               1. Stop the LANACP server process by issuing the SET ACP4                  /STOP command to the LANCP utility.  G               2. Reenable service on each of the DECnet circuits in the 2                  permanent and volatile databases.  I               3. Edit SYS$MANAGER:SYSTARTUP_VMS.COM to disable startup ofh*                  LANACP at system startup.  6         6.3.3 Using CLUSTER_CONFIG_LAN.COM and LAN MOP  A               A new cluster management command procedure has beentA               provided to facilitate the use of LANCP for LAN MOP C               booting of satellites. Called CLUSTER_CONFIG_LAN.COM, C               it resides in SYS$MANAGER and is a direct parallel tonC               CLUSTER_CONFIG.COM, which is used by cluster managerseC               to configure and reconfigure a VMScluster system. Thet?               two procedures perform the same functions, exceptoC               CLUSTER_CONFIG.COM uses DECnet MOP for downline load, E               whereas CLUSTER_CONFIG_LAN.COM uses LAN MOP. Therefore,eF               when you add a new node, CLUSTER_CONFIG_LAN.COM does notG               ask for the node's DECnet node name and address. Instead, H               it queries for an SCS node name and an SCS node id number.  I               For your convenience, you can still run CLUSTER_CONFIG.COM.cD               When you execute CLUSTER_CONFIG.COM, it checks whetherB               LANACP for MOP booting is running. It also checks to@               see if DECnet is running. If LANACP is running andB               DECnet is not, then CLUSTER_CONFIG.COM dispatches toE               CLUSTER_CONFIG_LAN.COM. If CLUSTER_CONFIG.COM discoverseB               that both LANACP and DECnet are running, it asks theE               user whether LAN MOP booting is being used, and whether A               it should call CLUSTER_CONFIG_LAN.COM for the user.A    =         6-56 Local Area Network (LAN) Management Enhancementsu Z  x              %         6.3.3.1 Sample Satellite Loade  D               The following shows how to issue commands to the LANCPG               utility to enable MOP downline load service and to defineh               node ZAPNOT:                 set acp/opcomR!               enable mop/dev=eza0 B               set node ZAPNOT/addr=08-00-2B-33-FB-F2/file=APB.EXE->                            /root=$64$DIA24:<SYS11.>/boot=Alpha  G               The following shows the OPCOM messages displayed when you 5               start up the LANACP LAN Server process:M  F               %%%%%%%%%%%  OPCOM  30-OCT-1994 06:47:35.18  %%%%%%%%%%%0               Message from user SYSTEM on GALAXY.               LANACP MOP Downline Load ServiceG               Found LAN device EZA0, hardware address 08-00-2B-30-8D-1C   F               %%%%%%%%%%%  OPCOM  30-OCT-1994 06:47:35.25  %%%%%%%%%%%0               Message from user SYSTEM on GALAXY.               LANACP MOP Downline Load ServiceG               Found LAN device EZB0, hardware address 08-00-2B-30-8D-1Dd  F               %%%%%%%%%%%  OPCOM  30-OCT-1994 06:47:54.80  %%%%%%%%%%%0               Message from user SYSTEM on GALAXY1               LANACP MOP V3 Downline Load Service =               Volunteered to load request on EZA0 from ZAPNOT_J               Requested file:  $64$DIA24:<SYS11.>[SYSCOMMON.SYSEXE]APB.EXE  F               %%%%%%%%%%%  OPCOM  30-OCT-1994 06:48:02.38  %%%%%%%%%%%0               Message from user SYSTEM on GALAXY1               LANACP MOP V3 Downline Load Service /               Load succeeded for ZAPNOT on EZA0nP          System image, $64$DIA24:<SYS11.>[SYSCOMMON.SYSEXE]APB.EXE (Alpha image)  I               The following display shows the contents of the LAN$ACP.LOG                file:               I                     Local Area Network (LAN) Management Enhancements 6-57     i              A 30-OCT-1994 06:47:35.02  Found LAN device EZA0, hardware address d*                          08-00-2B-30-8D-1CA 30-OCT-1994 06:47:35.18  Found LAN device EZB0, hardware address e*                          08-00-2B-30-8D-1D7 30-OCT-1994 06:47:35.25  LANACP initialization completesO 30-OCT-1994 06:47:45.39  Enabled LAN device EZA0 for MOP downline load service o*                          in exclusive modeH 30-OCT-1994 06:47:54.70  Volunteered to load request on EZA0 from ZAPNOT< Requested file:  $64$DIA24:<SYS11.>[SYSCOMMON.SYSEXE]APB.EXE: 30-OCT-1994 06:48:02.23  Load succeeded for ZAPNOT on EZA0H MOP V3 format, System image, $64$DIA24:<SYS11.>[SYSCOMMON.SYSEXE]APB.EXE" Packets:  2063 sent, 2063 received3 Bytes:    519416 sent, 4126 received, 507038 loaded . Elapsed time:  00:00:07.42, 68276 bytes/second  *         6.3.3.2 Cross-Architecture Booting  I               The LAN enhancements permit cross-architecture booting in aiH               VMScluster system. VAX boot nodes can provide boot serviceG               to Alpha satellites and Alpha boot nodes can provide boot I               service to VAX satellites. Note that each architecture mustlF               include a system disk that is used for installations and               upgrades.E                                                  =         6-58 Local Area Network (LAN) Management Enhancementsi o  f                    I                                                                         7nI         _________________________________________________________________i  I                                 SCSI as a VMScluster Storage Interconnect     H               One of the benefits of VMScluster systems is that multipleA               computers can simultaneously access storage devices G               connected to a VMScluster storage interconnect. Together,bI               these systems provide high performance and highly availabled                access to storage.  C               This chapter describes how VMScluster systems support F               the Small Computer Systems Interface (SCSI) as a storageI               interconnect. Multiple Alpha computers, also referred to asiI               hosts or nodes, can simultaneously access SCSI disks over atH               SCSI interconnect. A SCSI interconnect, also called a SCSII               bus, is an industry-standard interconnect that supports one H               or more computers, peripheral devices, and interconnecting               components.   E               The discussions in this chapter assume that you already A               understand the concept of sharing storage resources-B               in a VMScluster environment. VMScluster concepts andG               configuration requirements are described in the followingn'               VMScluster documentation:0  9               o  Guidelines for VMScluster Configurations   /               o  VMScluster Systems for OpenVMSn  F               o  VMScluster Systems for OpenVMS Alpha Software Product+                  Description (SPD 42.18.xx)m  6               This chapter includes two primary parts:  ?               o  Section 7.1 through Section 7.6.6 describe the H                  fundamental procedures and concepts that you would need@                  to plan and implement a SCSI VMScluster system.  C               o  Section 7.7 and its subsections provide additionaloE                  technical detail and concepts; these sections can besH                  seen as containing supplementary information about SCSI  I                             SCSI as a VMScluster Storage Interconnect 7-1h A  P              I                  VMScluster systems that would typically be located in anr                  appendix.  ,         7.1 Conventions Used in This Chapter  E               Certain conventions are used throughout this chapter to E               identify the ANSI Standard and for elements in figures.l            7.1.1 SCSI ANSI Standard  F               VMScluster systems configured with the SCSI interconnectH               must use standard SCSI-2 components. The SCSI-2 componentsG               supported must be compliant with the architecture defined A               in the American National Standards Institute (ANSI)eF               Standard SCSI-2. This standard defines extensions to theC               SCSI-1 standard. For ease of discussion, this chapternA               uses the term SCSI or SCSI-2 to refer to the SCSI-2cE               implementation as specified in the ANSI Standard SCSI-2 (               document X3T9.2, Rev. 10L.  %         7.1.2 Symbols Used in Figurese  @               Figure 7-1 is a key to the symbols used in figures&               throughout this chapter.  "         7.2 Accessing SCSI Storage  H               In VMScluster configurations, multiple VAX and Alpha hostsF               can directly access SCSI devices in any of the following               ways:   <               o  CI interconnect with HSJ or HSC controllers  E               o  Digital Storage Systems Interconnect (DSSI) with HSDe                  controller   I               o  SCSI adapters directly connected to VAX or Alpha systemsi  C               You can also access SCSI devices indirectly using then"               OpenVMS MSCP server.  G               The following sections describe single-host and multiple- 2               host access to SCSI storage devices.    5         7-2 SCSI as a VMScluster Storage InterconnectS X  A              ;         7.2.1 Single-Host SCSI Access in VMScluster Systems   G               Prior to OpenVMS Version 6.2, VMScluster systems provided D               support for SCSI storage devices connected to a singleG               host using an embedded SCSI adapter, an optional external F               SCSI adapter, or a special-purpose RAID (redundant arrayF               of independent disks) controller. Only one host could be&               connected to a SCSI bus.  =         7.2.2 Multiple-Host SCSI Access in VMScluster Systems   E               With OpenVMS Alpha Version 6.2, multiple Alpha hosts in G               a VMScluster system can be connected to a single SCSI busMD               to share access to SCSI storage devices directly. ThisE               capability allows you to build highly available serversi2               using shared access to SCSI storage.  C               Figure 7-2 shows a VMScluster configuration that usesSD               a SCSI interconnect for shared access to SCSI devices.G               Note that another interconnect (for example, a local area D               network [LAN]) is required for host-to-host VMSclusterH               (System Communications Architecture [SCA]) communications.  I               You can build a two-node VMScluster system using the sharedDF               SCSI bus as the storage interconnect, or you can includeI               shared SCSI buses within a larger VMScluster configuration. F               A quorum disk can be used on the SCSI bus to improve theF               availability of two-node configurations. Host-based RAIDF               (including host-based shadowing) and the MSCP server are8               supported for shared SCSI storage devices.  ;         7.3 Configuration Requirements and Hardware Support   C               This section lists the configuration requirements and H               supported hardware for SCSI VMScluster systems for OpenVMS               Version 6.2.  (         7.3.1 Configuration Requirements  F               Table 7-1 shows the requirements and capabilities of theI               basic software and hardware components you can configure inn'               a SCSI VMScluster system.d      I                             SCSI as a VMScluster Storage Interconnect 7-3     h              G               Table 7-1 Requirements for SCSI VMScluster ConfigurationsU  (               Requirement    Description  I               Software       All Alpha hosts sharing access to storage onoA                              a SCSI interconnect must be running:!  9                              o  OpenVMS Alpha Version 6.2   E                              o  VMScluster Software for OpenVMS Alpha +                                 Version 6.2p  C               Hardware       Table 7-2 lists the supported hardwarehD                              components for SCSI VMScluster systems.I                              See also Section 7.7.7 for information aboutOI                              other hardware devices that might be used ins=                              a SCSI VMScluster configuration.   C               SCSI tape,     You cannot configure SCSI tape drives, ?               floppies       floppy drives, or CD-ROM drives on F               and CD-ROM     multiple-host SCSI interconnects. If yourF               drives         configuration requires SCSI tape, floppy,H                              or CD-ROM drives, configure them on single-D                              host SCSI interconnects. Note that SCSIB                              tape, floppy, or CD-ROM drives may beG                              MSCP or TMSCP served to other hosts in theO6                              VMScluster configuration.  A               Maximum        You can connect up to two hosts on amF               hosts on a     multiple-host SCSI bus. You can configureH               SCSI bus       any mix of the hosts listed in Table 7-2 on?                              the same shared SCSI interconnect.i  F               Maximum SCSI   You can connect each host to a maximum ofH               buses per      two multiple-host SCSI buses. The number ofH               host           nonshared (single-host) SCSI buses that canH                              be configured is limited only by the number@                              of available slots on the host bus.  I               Host-to-host   All members of the cluster must be connectedoD               communica-     by an interconnect that can be used forB               tion           host-to-host (SCA) communication; for>                              example, DSSI, Ethernet, or FDDI.  I                                                  (continued on next page)   5         7-4 SCSI as a VMScluster Storage Interconnect  o  g              @               Table 7-1 (Cont.) Requirements for SCSI VMScluster.                                 Configurations  (               Requirement    Description  I               Host-          Supported in SCSI VMScluster configurations..               based RAID               (including               host-based               shadowing)  H               SCSI device    The name of each SCSI device must be uniqueC               naming         throughout the VMScluster system. WhencH                              configuring devices on systems that includeD                              a multiple-host SCSI bus, adhere to the4                              following requirements:  =                              o  A host can have, at most, oneEH                                 controller attached to a particular SCSI-                                 interconnect.E  H                              o  All host controllers attached to a givenD                                 SCSI interconnect must have the sameH                                 OpenVMS device name (for example, PKA0).  >                              o  Each system attached to a SCSIG                                 interconnect must have the same nonzero G                                 allocation class. Each disk device name E                                 (for example, DKB100), whether or notsD                                 on a shared SCSI bus, must be uniqueD                                 within an allocation class. Refer toC                                 Section 7.6.2 for more information.   I               ___________________________________________________________            7.3.2 Hardware Support  H               Table 7-2 shows the supported hardware components for SCSID               VMScluster systems; it also lists the minimum requiredB               revision for these hardware components (that is, forF               any component, you must use either the version listed in1               Table 7-2 or a subsequent version).O  D               The SCSI interconnect configuration and all devices onF               the SCSI interconnect must meet the requirements definedG               in the ANSI Standard SCSI-2 document and the requirementsT(               described in this chapter.  I                             SCSI as a VMScluster Storage Interconnect 7-5     p              @               See also Section 7.7.7 for information about otherF               hardware devices that might be used in a SCSI VMScluster               configuration.  F               Table 7-2 Supported Hardware for SCSI VMScluster Systems  5                                               Minimumi5                                               VersiontG                                               or H/W        How to FinddH               Component   Supported Item      Revision      Your Version  C               Hosts       AlphaServer 400     See           ConsoleaH                           4/xxx               footnote[1]   SHOW VERSIONC                                                             commande  C               Hosts       AlphaServer 1000    See           ConsoleLH                           4/xxx               footnote[1]   SHOW VERSIONC                                                             commande  1                           AlphaServer 2000    Seeq9                           4/xxx               footnote[1]   1                           AlphaServer 2100    SeeL9                           4/xxx               footnote[1]C  1                           AlphaStation 200    Seer9                           4/xxx               footnote[1]e  1                           AlphaStation 250    See 9                           4/xxx               footnote[1]   1                           AlphaStation 400    SeeC9                           4/xxx               footnote[1]C  C               Disks       RZ26                392A          ConsolegG                                                             SHOW DEVICE_C                                                             commanda  2                           RZ26L               442D  2                           RZ28                442D  @               [1]The minimum revision of this component for SCSIF               VMScluster configurations is the version included in theC               Version 3.2 Firmware Kit on the May, 1995 CD-ROM. ThevE               revision number is listed in the Firmware Release NotesX:               Overview that accompanies that Firmware Kit.  I                                                  (continued on next page)   5         7-6 SCSI as a VMScluster Storage Interconnects                   F               Table 7-2 (Cont.) Supported Hardware for SCSI VMScluster'                                 Systems   5                                               Minimumn5                                               Version G                                               or H/W        How to Find H               Component   Supported Item      Revision      Your Version  2                           RZ28B               0006  2                           RZ29B               0006  C               Controller  HSZ40               2.5           Console G                                                             SHOW DEVICEnC                                                             command   C               Bus         DWZZA-AA            E01           ExamineOC               Isolators                                     product4C                                                             stickerY  1                           DWZZA-VA            F01   1               Adapters[2] Integral system     N/A !                           adapter.  '                           KZPAA (PCI to                            SCSI)aD               [2]You can configure other types of SCSI adapters in a=               system for single-host access to local storage. I               ___________________________________________________________N  &         7.4 SCSI Interconnect Concepts  D               The SCSI standard defines a set of rules governing theG               interactions between initiators (typically, host systems)DD               and SCSI targets (typically, peripheral devices). ThisG               standard allows the host to communicate with SCSI devices F               (such as disk drives, tape drives, printers, and opticalI               media devices) without having to manage the device-specific1               characteristics.  G               The following sections describe the SCSI standard and thesG               default modes of operation. The discussions also describenC               some optional mechanisms you can implement to enhance   I                             SCSI as a VMScluster Storage Interconnect 7-7h c  e              F               the default SCSI capabilities in areas such as capacity,6               performance, availability, and distance.           7.4.1 Number of Deviceso  E               The SCSI bus is an I/O interconnect that can support upeF               to eight devices. The devices can include host adapters,E               peripheral controllers, and discrete peripheral devices G               such as disk or tape drives. The devices are addressed by-H               a unique ID number from 0 through 7. You assign the deviceH               IDs by entering console commands, or by setting jumpers or               switches._  I               To increase the number of devices on the SCSI interconnect, H               some devices implement a second level of device addressingG               using logical unit numbers (LUNs). For each device ID, up F               to eight LUNs (0-7) can be used to address a single SCSIF               device as multiple units. The maximum number of LUNs per!               device ID is eight.m  F                 ________________________ Note ________________________  D                 When connecting devices to a SCSI interconnect, eachD                 device on the interconnect must have a unique deviceD                 ID. You may need to change a device's default deviceC                 ID to make it unique. For information about settingtA                 a device's ID, refer to the owner's guide for the                  device.,  F                 ______________________________________________________           7.4.2 Performancee  F               The default mode of operation for all SCSI devices is 8-E               bit asynchronous mode. This mode, sometimes referred tonF               as narrow mode, transfers 8 bits of data from one deviceC               to another. Each data transfer is acknowledged by therC               device receiving the data. Because the performance ofcD               the default mode is limited, the SCSI standard definesG               optional mechanisms to enhance performance. The following F               list describes two optional methods for achieving higher               performance:  C               o  Increase the amount of data that is transferred in D                  parallel on the interconnect. The 16-bit and 32-bitD                  wide options allow a doubling or quadrupling of theF                  data rate, respectively. Because the 32-bit option is  5         7-8 SCSI as a VMScluster Storage Interconnectd o  o              G                  seldom implemented, this chapter discusses only 16-bit @                  operation and refers to it using the term wide.  D               o  Use synchronous data transfer. In synchronous mode,A                  multiple data transfers can occur in succession,dH                  followed by an acknowledgment from the device receivingH                  the data. The standard defines a Slow Mode (also calledD                  Standard Mode) and a Fast Mode for synchronous data                  transfers:s  G                  -  In Standard Mode, the interconnect achieves up to 5c1                     million transfers per second.   D                  -  In Fast Mode, the interconnect achieves up to 101                     million transfers per second.   E               Because all communications on a SCSI interconnect occurIF               between two devices at a time, each pair of devices mustH               negotiate to determine which of the optional features theyG               will use. Most, if not all, SCSI devices implement one or $               more of these options.  A               Table 7-3 shows data rates when using 8- and 16-bit A               transfers with Standard and Fast synchronous modes.1  D               Table 7-3 Maximum Data Transfer Rates in Megabytes per                         Second  6               Mode      Narrow (8-Bit)   Wide (16-Bit)  -               Standard    5                10a  -               Fast        10               20o           7.4.3 Distance  G               The maximum length of the SCSI interconnect is determined G               by the signaling method used in the configuration and, in H               some cases, by the data transfer rate. There are two types=               of electrical signaling for SCSI interconnects:I  '               o  Single-ended signaling   C                  The single-ended method is the most common and the F                  least expensive. It can operate in either Standard or  I                             SCSI as a VMScluster Storage Interconnect 7-9                    F                  Fast Mode. The mode used determines the length of the*                  interconnect, as follows:  H                  -  When standard transfers are in use, the interconnect6                     can be up to 6 meters in length[1]  H                  -  When fast transfers are in use, the interconnect can/                     be up to 3 meters in lengthd  '               o  Differential signaling   F                  This method provides higher signal integrity, therebyB                  allowing a SCSI bus to span distances of up to 25D                  meters. Differential signaling allows both standardH                  and fast data transfers regardless of the length of the                  SCSI bus.  H               When considering cable distance issues, be sure to includeF               both internal and external cabling in your calculations.D               Table 7-5 lists the internal cable lengths for various               configurations.a  C               Table 7-4 summarizes how the type of signaling methodo2               affects SCSI interconnect distances.  ;               Table 7-4 Maximum SCSI Interconnect Distancese  +               Signaling        Rate of DataiD               Technique        Transfer         Maximum Cable Length  9               Single ended     Standard         6 meters+e  8               Single ended     Fast             3 meters  9               Differential     Standard or      25 metersm#                                FastiG               +The SCSI standard specifies a maximum length of 6 metersaH               for this type of interconnect. However, Digital recommendsC               that, where possible, you limit the cable length to 4 C               meters to ensure the highest level of data integrity. I               ___________________________________________________________   A               A DWZZA converter is a single-ended to differential D               converter that you can use to connect single-ended and  "               ____________________D               [1]   See the note following Table 7-4 for informationD                     about the maximum length recommended by Digital.  6         7-10 SCSI as a VMScluster Storage Interconnect S  a              G               differential SCSI interconnect segments. The differentialS4               segments are useful for the following:  H               o  Overcoming the distance limitations of the single-ended                  interconnect   @               o  Allowing communication between single-ended and%                  differential devicese  C               Because the DWZZA is strictly a signal converter, youpC               do not need to assign a SCSI device ID to it. You can E               configure a maximum of two DWZZA converters in the path $               between any two hosts.  %         7.4.4 Cabling and Termination   B               Each single-ended and differential SCSI interconnectG               must have two terminators, one at each end. The specified G               maximum interconnect lengths are measured from terminatort               to terminator.  D               The interconnect terminators are powered from the SCSII               interconnect line called TERMPWR. Each Digital host adapter.F               and enclosure supplies the TERMPWR interconnect line, soF               that as long as one host or enclosure is powered on, the.               interconnect remains terminated.  D               Devices attach to the interconnect by short cables (orB               etch), called stubs. Stubs must be short in order toD               maintain the signal integrity of the interconnect. TheH               maximum stub lengths allowed are determined by the type of=               signaling used by the interconnect, as follows:S  H               o  For single-ended interconnects, the maximum stub length                  is .1 meters   H               o  For differential interconnects, the maximum stub length                  is .2 metersc  C               Additionally, the minimum distance between stubs on aSI               single-ended interconnect is .3 meters. Refer to Figure 7-3s3               for an example of this configuration.b  F                 ________________________ Note ________________________  =                 Terminate single-ended and differential buses ?                 individually, even when using DWZZA converters.m  F                 ______________________________________________________  I                            SCSI as a VMScluster Storage Interconnect 7-11a e  S              D               When you are extending the SCSI bus beyond an existingC               terminator, it is necessary to disable or remove thatn               terminator.   E               When using the host system's internal SCSI adapter, you F               must configure the system at the end of the single-endedC               SCSI segment. This is because the internal SCSI cableeE               lengths exceed the allowable SCSI stub length. However, H               host systems are not required to be configured at the endsE               of the bus segment when an add-on SCSI adapter is used.i  E               See Table 7-5 for information about internal SCSI cable                lengths.  3         7.5 SCSI VMScluster Hardware Configurations   E               The hardware configuration that you choose depends on al%               combination of factors:   =               o  Your computing needs-for example, continuous E                  availability, or the ability to disconnect or remove :                  a system from your SCSI VMScluster system  I               o  Your environment-for example, the physical attributes of (                  your computing facility  F               o  Your resources-for example, your capital equipment or(                  the available PCI slots  >               You can connect up to two hosts on a shared SCSID               interconnect. Each host can be connected to one or twoE               shared SCSI interconnects. The number of nonshared SCSIeH               buses that can be configured is limited only by the number1               of available slots on the host bus.   I               The following sections provide guidelines for building SCSI G               configurations and describe potential configurations that_2               might be suitable for various sites.  0         7.5.1 Systems Using Add-On SCSI Adapters  D               Shared SCSI bus configurations may use optional add-onD               KZPAA adapters. These adapters are generally easier toB               configure than internal adapters because they do notC               consume any SCSI cable length. Additionally, when you C               configure systems using KZPAA adapters for the shared H               SCSI bus, the internal adapter is available for connecting  6         7-12 SCSI as a VMScluster Storage Interconnect n  d              D               devices that cannot be shared (for example, SCSI tape,)               floppy, and CD-ROM drives).u  D               When using KZPAA adapters, storage is configured usingC               BA350, BA353, or HSZ40 StorageWorks enclosures. TheseeH               enclosures are suitable for all data disks, and for sharedG               VMScluster system and quorum disks. By using StorageWorkssH               enclosures, it is possible to shut down individual systems1               without losing access to the disks.   B               The following sections describe some SCSI VMSclusterD               configurations that take advantage of add-on adapters.  B         7.5.1.1 Building a Basic System Using Add-On SCSI Adapters  B               Figure 7-4 shows a logical representation of a basicB               configuration using SCSI adapters and a StorageWorks@               enclosure. This configuration has the advantage ofF               being relatively simple, while still allowing the use ofF               tapes, floppies, CD-ROMs, and disks with nonshared filesB               (for example, page files and swap files) on internalF               buses. Figure 7-5 shows this type of configuration using=               AlphaServer 1000 systems and a BA350 enclosure.   F               The BA350 enclosure uses 0.9 meters of SCSI cabling, andH               this configuration typically uses two 1-meter SCSI cables.D               (A BA353 enclosure also uses 0.9 meters, with the sameF               total cable length.) The resulting total cable length of9               2.9 meters allows Fast SCSI Mode operation./  <               Although the shared BA350 storage enclosure isH               theoretically a single point of failure, this basic systemD               is a very reliable SCSI VMScluster configuration. WhenH               the quorum disk is located in the BA350, you can shut downD               either of the AlphaStation systems independently whileE               retaining access to the VMScluster system. However, you F               cannot physically remove the AlphaStation system because8               that would leave an unterminated SCSI bus.  C               If you need the ability to remove a system while youreF               VMScluster system remains operational, build your systemI               using DWZZA converters, as described in Section 7.5.1.2. If G               you need continuous access to data if a SCSI interconnect 9               fails, you should do both of the following:f  E               o  Add a redundant SCSI interconnect with another BA350                   shelf.   I                            SCSI as a VMScluster Storage Interconnect 7-13                    !               o  Shadow the data.   H               In Figure 7-4 and the other logical configuration diagramsG               in this chapter, the required network interconnect is not G               shown. (See Figure 7-1 for the key to the symbols used in %               the following figures.)l    D         7.5.1.2 Building a System That Allows a Server to Be Removed(                 (Using DWZZA Converters)  G               The capability of removing an individual system from your G               SCSI VMScluster configuration (for maintenance or repair) H               while the other systems in the cluster remain active givesC               you an especially high level of availability. To have0H               this capability, use a configuration that includes a DWZZAG               converter (a SCSI bus isolator). DWZZA converters provide G               additional SCSI bus length capabilities because the DWZZA G               allows you to connect a single-ended device to a bus thatsI               uses differential signaling. As described in Section 7.4.3,_E               SCSI bus configurations that use differential signaling F               may span distances up to 25 meters, whereas single-endedG               configurations can span only 3 meters when Fast Mode dataC               transfer is used.   C               DWZZA converters are available as standalone, desktopiG               components or as StorageWorks compatible building blocks.rI               DWZZA converters can be used with the internal SCSI adaptere-               or the optional KZPAA adapters.   @               Figure 7-6 shows a logical view of a configuration@               that uses internal SCSI adapters and a pair of busD               isolators, and Figure 7-7 shows a physical view of theD               same configuration using two AlphaServer 1000 systems.E               In configurations such as those shown in Figure 7-6 and G               Figure 7-7, you can also remove either of the AlphaServeraA               enclosures because the SCSI bus remains terminated.   E               In each of these figures, note that a single-ended SCSI H               bus is used to connect a DWZZA to the AlphaServer systems,H               and another single-ended bus is used to connect the secondF               DWZZA to the disks. The two DWZZAs are connected to eachE               other by a differential bus. The differential signaling H               is necessary because the cabling between the DWZZA and theH               AlphaServer systems consumes virtually all of the 3 meters  6         7-14 SCSI as a VMScluster Storage Interconnect t  s            f  H               of single-ended cabling that is allowed for Fast Mode data               transfer.   F                 ________________________ Note ________________________  E                 See Figure 7-1 for the key to the symbols used in the "                 following figures.  F                 ______________________________________________________  E         7.5.1.3 Building a System That Allows Additional Features and 5                 Performance Using an HSZ40 Controller   ?               The HSZ40 is a high-performance differential SCSIeE               controller that can be connected to a differential SCSI F               bus, and supports up to 42 SCSI devices. An HSZ40 may beI               configured on a shared SCSI bus that includes DWZZA single-_G               ended to differential converters. Disk devices configuredaD               on HSZ40 controllers can be combined into RAID sets toH               further enhance performance and provide high availability.  E               Figure 7-8 shows a logical view of a configuration thatrF               uses differential SCSI controllers, and Figure 7-9 showsC               a physical example of the same configuration using an A               HSZ40 in an SW300 enclosure. Note that the DWZZA ismC               not needed in the StorageWorks enclosure in this typedC               of configuration because the HSZ40 is compatible withf%               differential signaling.h  A         7.5.1.4 Building a System with More Enclosures or Greatern                 Separation  C               If you need additional enclosures, or if the needs oflE               your site require a greater physical separation betweentF               systems, you can use a configuration in which DWZZAs areF               placed between systems with single-ended signaling and a+               differential-cabled SCSI bus.i  F               Figure 7-10 shows a logical view of a configuration thatG               uses additional DWZZAs to increase the potential physicalaA               separation (or to allow for additional enclosures),cC               and Figure 7-11 shows a sample representation of thise               configuration.    I                            SCSI as a VMScluster Storage Interconnect 7-15a                     '         7.5.1.5 Planning for the Futurer  H               In OpenVMS Version 6.2, you can connect up to two hosts onI               a multiple-host SCSI bus. In the future, Digital expects tohH               provide the capability for connecting up to three hosts on.               the same multiple-host SCSI bus.  B               Although this capability is not currently supported,C               Figure 7-12 is included to show how a three-host SCSIh4               VMScluster system might be configured.  <         7.5.2 Building a System Using Internal SCSI Adapters  I               You can build a multiple-host SCSI VMScluster configurationaF               with two systems using internal adapters that are joinedC               by a single SCSI cable. This type of configuration isbA               relatively inexpensive, and it provides some of the D               benefits of multiple-host SCSI VMScluster systems thatD               use external adapters (for example, fully shared disksD               and twice the serving performance of a single system).G               This system configuration can also be expanded to provide >               improved performance, availability, and scaling.  G               However, a multiple-host SCSI VMScluster system that uses H               only internal SCSI adapters has the following limitations:  H               o  On most systems, the internal cabling lengths exceeds 3I                  meters and therefore precludes the use of Fast Mode data *                  transfer (see Table 7-5).  D               o  You cannot remove either of the AlphaServer systems>                  for maintenance or repair while the remainingF                  cluster systems stay active (because the bus would be                  unterminated).   C               o  If these are the only members of the cluster, thennE                  quorum is lost when one (or either, depending on howeF                  the votes are allocated) of the enclosures goes down.  6               o  You cannot use tape or CD-ROM drives.  B               Some of the limitations associated with the internalE               adapter can be removed by using DWZZAs, additional SCSIt:               adapters, and additional storage enclosures.  6         7-16 SCSI as a VMScluster Storage Interconnect                   B               Figure 7-13 shows a conceptual view of a SCSI systemE               using internal adapters, and Figure 7-14 shows a samplel-               configuration of such a system.o      3               Table 7-5 Internal SCSI Cable Lengths-  H               System Type                          Internal Cable Length  =               AlphaServer 1000 rackmount           1.6 meterst  =               AlphaServer 1000 pedestal with an    2.0 meterst.               internal StorageWorks shelf in a'               dual-bus configuration[1]   =               AlphaServer 2000 pedestal with the   1.7 metersg1               internal StorageWorks shelf that is                not connected   =               AlphaServer 2100 rackmount           2.0 meters   =               AlphaServer 2100 pedestal with the   1.6 meters 1               internal StorageWorks shelf that isr               not connected   =               AlphaStation 200                     1.2 meters   =               AlphaStation 400                     1.4 meters   G               [1]See your hardware manual for an explanation of single- I               bus and dual-bus configurations, and how to switch from one                to the other.nI               ___________________________________________________________            7.6 Installation  E               This section describes the steps required to set up anduC               install the hardware in a SCSI VMScluster system. The I               assumption in this section is that a new VMScluster system, F               based on a shared SCSI bus, is being created. If, on theI               other hand, you are adding a shared SCSI bus to an existingoA               VMScluster configuration, then you should integrate D               the procedures in this section with those described inF               VMScluster Systems for OpenVMS to formulate your overall                installation plan.  I                            SCSI as a VMScluster Storage Interconnect 7-17o g                 F               Table 7-6 lists the steps required to set up and install7               the hardware in a SCSI VMScluster system.   E               Table 7-6 Steps for Installing a SCSI VMScluster Systemh  5               Description                   Reference   =             1  Ensure proper grounding      Section 7.6.1 ando9               between enclosures.           Section 7.7.8c  9             2  Configure SCSI host IDs.     Section 7.6.2n  9             3  Power up the system and      Section 7.6.3                verify devices.i  9             4  Set SCSI console             Section 7.6.4o               parameters.   9             5  Install the OpenVMS          Section 7.6.5a               operating system.a  9             6  Configure additional         Section 7.6.6h               systems.  6         7.6.1 Step 1: Meet SCSI Grounding Requirements  E               You must ensure that your electrical power distributionaF               systems meet local requirements (for example, electricalH               codes) prior to installing your VMScluster system. If yourH               configuration consists of two or more enclosures connectedF               by a common SCSI interconnect, you must also ensure thatD               the enclosures are properly grounded. Proper groundingF               is important for safety reasons and to ensure the proper3               functioning of the SCSI interconnect.e  I               Electrical work should be done by a qualified professional.t=               Section 7.7.8 includes details of the groundinge,               requirements for SCSI systems.  -         7.6.2 Step 2: Configure SCSI Node IDs   C               This section describes how to configure SCSI node and_B               device IDs. SCSI IDs must be assigned separately forB               multiple-host SCSI buses and single-host SCSI buses.  H               Figure 7-15 shows two hosts; each one is configured with aG               single-host SCSI bus and shares a multiple-host SCSI bus.   6         7-18 SCSI as a VMScluster Storage Interconnect                   E               The following sections describe how IDs are assigned ingE               this type of multiple-host SCSI configuration. For morexF               information about this topic, see VMScluster Systems for               OpenVMS.  B         7.6.2.1 Configuring Device IDs on Multiple-Host SCSI Buses  F               When configuring multiple-host SCSI buses, adhere to the               following rules:  D               o  Set each host adapter on the multiple-host bus to aI                  different ID. Start by assigning ID 7, then ID 6, and sol1                  on, using decreasing ID numbers.   E                  If a host has two multiple-host SCSI buses, allocateaC                  an ID to each SCSI adapter separately. There is no F                  requirement that you set the adapters to the same ID,F                  although using the same ID may simplify configurationI                  management. (Section 7.6.4 describes how to set host IDsiI                  for the internal adapter using SCSI console parameters.)   F               o  When assigning IDs to devices and storage controllers?                  connected to multiple-host SCSI buses, DigitaldB                  recommends starting at ID 0 (zero), assigning theI                  highest ID numbers to the disks that require the fastesta#                  I/O response time.   H               o  Devices connected to a multiple-host SCSI bus must haveI                  the same name as viewed from each host. To achieve this,                   ensure that:   G                  -  All hosts connected to a multiple-host SCSI bus are 4                     set to the same allocation class  G                  -  All host adapters connected to a multiple-host SCSI 7                     bus have the same controller lettere  @         7.6.2.2 Configuring Device IDs on Single-Host SCSI Buses  I               The following discussion applies to hosts that include bothsB               a single-host SCSI bus and a multiple-host SCSI bus.  @               In multiple-host SCSI configurations, device names>               generated by OpenVMS use the format $allocation_B               class$DKA300. You set the allocation class using the?               ALLOCLASS system parameter. OpenVMS generates thefD               controller letter (for example, A, B, C, and so forth)I               at boot time by allocating a letter to each controller. The   I                            SCSI as a VMScluster Storage Interconnect 7-19e k                 G               unit number (for example, 0, 100, 200, 300, and so forth) 1               is derived from the SCSI device ID.   I               When configuring devices on single-host SCSI buses that arerF               part of a multiple-host SCSI configuration, take care toE               ensure that the disks connected to the single-host SCSI4B               buses have unique device names. Do this by assigningD               different IDs to devices connected to single-host SCSIG               buses with the same controller letter on systems that usemH               the same allocation class. Note that the device names must>               be different, even though the bus is not shared.  I               For example, in Figure 7-15, the two disks at the bottom of G               the picture are located on SCSI bus A of two systems thataF               use the same allocation class. Therefore, they have beenD               allocated different device IDs (in this case 2 and 3).  A               For a given allocation class, SCSI device type, andsF               controller letter (in this example, "$4$DKA"), there canF               be up to 8 devices in the cluster, one for each SCSI busG               ID. To use all 8 IDs, it is necessary to configure a disksF               on one SCSI bus at the same ID as a processor on anotherF               bus. (See Section 7.7.5 for a discussion of the possible0               performance impact this can have.)  I               SCSI bus IDs can be effectively "doubled up" by configuringe@               different SCSI device types at the same SCSI ID onF               different SCSI buses. For example, device types "DK" and=               "MK" could produce "$4$DKA100" and "$4$MKA100".   6         7.6.3 Step 3: Power Up and Verify SCSI Devices  D               After connecting the SCSI cables, power up the system.D               Enter a console SHOW DEVICE command to verify that all;               devices are visible on the SCSI interconnect.   B               If there is a SCSI ID conflict, the display may omitE               devices that are present, or it may include nonexistentrB               devices. If the display is incorrect, then check theF               SCSI ID jumpers on devices, the automatic ID assignmentsC               provided by the StorageWorks shelves, and the console D               settings for host adapter and HSZ40 controller IDs. IfB               changes are made, type INIT, then SHOW DEVICE again.C               If problems persist, check the SCSI cable lengths andy               termination.  6         7-20 SCSI as a VMScluster Storage Interconnect s                 I               The following is a sample output from a console SHOW DEVICE I               command. This system has one host SCSI adapter on a private I               SCSI bus (pka0), and two additional SCSI adapters (pkb0 and 9               pkc0), each on separate, shared SCSI buses.                >>>SHOW DEVICEO             dka0.0.0.6.0               DKA0 1                       RZ26L  442DiP             dka400.4.0.6.0             DKA400                        RRD43  2893P             dkb100.1.0.11.0            DKB100                         RZ26  392AP             dkb200.2.0.11.0            DKB200                        RZ26L  442DP             dkc400.4.0.12.0            DKC400                        HSZ40   V25O             dkc401.4.0.12.0            DKC401 2                     HSZ40   V25 P             dkc500.5.0.12.0            DKC500                        HSZ40   V25P             dkc501.5.0.12.0            DKC501                        HSZ40   V25P             dkc506.5.0.12.0            DKC506                        HSZ40   V25+             dva0.0.0.0.1               DVA0pO             jkb700.7.0.11.0            JKB700 3                    OpenVMS  V62eP             jkc700.7.0.12.0            JKC700                       OpenVMS  V62O             mka300.3.0.6.0             MKA300 4                     TLZ06  0389eO             era0.0.0.2.1               ERA0                   08-00-2B-3F-3A-B9wO             pka0.7.0.6.0               PKA0 5                     SCSI Bus ID 71P             pkb0.6.0.11.0              PKB0                        SCSI Bus ID 6P             pkc0.6.0.12.0              PKC0                        SCSI Bus ID 6  B               The following list describes the device names in the                preceding example:  D               1  DK devices represent SCSI disks. Disks connected toH                  the SCSI bus controlled by adapter PKA are given deviceI                  names starting with the letters DKA. Disks on additionalwH                  buses are named according to the host adapter name in aH                  similar manner (DKB devices on adapter PKB, and so on).  G                  The next character in the device name (0 in this case)rI                  represents the device's SCSI ID. Make sure that the SCSIeG                  ID for each device is unique for the SCSI bus to whichh!                  it is connected.   F               2  The last digit in the DK device name (1 in this case)G                  represents the LUN number. The HSZ40 virtual DK devicehG                  in this example is at SCSI ID 4, LUN 1. Note that some G                  systems do not display devices that have nonzero LUNs..      I                            SCSI as a VMScluster Storage Interconnect 7-21r c  s              G               3  JK devices represent nondisk or nontape devices on theSI                  SCSI interconnect. In this example, JK devices represent C                  other processors on the SCSI interconnect that are C                  running the OpenVMS operating system. If the other F                  system is not running, these JK devices do not appearG                  in the display. In this example, the other processor'ss+                  adapters are at SCSI ID 7.a  H               4  MK devices represent SCSI tapes. The third character inH                  this device's name is A, indicating that it is attached7                  to adapter pka0, the private SCSI bus.e  B               5  PK devices represent the local SCSI adapters. TheC                  information in the rightmost column indicates this D                  adapter's SCSI ID. Make sure this is different fromG                  the IDs used by other devices and host adapters on itsa                  bus..  I                  The third character in the device name (in this example,iF                  a) is assigned by the system so that each adapter hasF                  a unique name on that system. The fourth character is                  always zero.c  F                 ________________________ Note ________________________  C                 Make sure that all host adapters attached to a SCSIbC                 interconnect have the same name; that is, the third ?                 character in the device names must be the same.a?                 OpenVMS configures the internal SCSI adapter as C                 DKA, the first KZPAA adapter as DKB, and so on. ForaC                 example, to ensure that device names are consistent A                 on a shared SCSI bus, do not connect the internalaE                 adapter in one system and a KZPAA adapter in a second A                 system to the same bus. For more information, see "                 Section 7.7.4.2.1.  F                 ______________________________________________________                6         7-22 SCSI as a VMScluster Storage Interconnect -  t              :         7.6.4 Step 4: Show and Set SCSI Console Parameters  H               When creating a SCSI VMScluster system, you need to verifyI               the settings of the console environment parameters shown inlG               Table 7-7 and, if necessary, reset their values according 1               to your configuration requirements.   D               Table 7-7 provides a brief description of SCSI consoleI               parameters. Refer to your system-specific documentation for G               complete information about setting these and other systeme               parameters.I  F                 ________________________ Note ________________________  F                 If you need to modify any parameters, first change theF                 parameter (using the appropriate console SET command),B                 and then enter a console INIT command or press the:                 Reset button to make the change effective.  F                 ______________________________________________________  3               Table 7-7 SCSI Environment Parameterso  /               Parameter             Description   H               bootdef_dev device_   Specifies the default boot device to/               name                  the system.   =               boot_osflags root_    The boot_osflags variable @               number,bootflag       contains information that isC                                     used by the operating system to C                                     determine optional aspects of a B                                     system bootstrap (for example,>                                     conversational bootstrap).  H               pk*0_disconnect       Allows the target to disconnect fromF                                     the SCSI bus while the target actsE                                     on a command. When this parameternF                                     is set to 1, the target is allowedC                                     to disconnect from the SCSI buseD                                     while processing a command. WhenI                                     the parameter is set to 0, the target-I                                     retains control of the SCSI bus while 8                                     acting on a command.  I                                                  (continued on next page)   I                            SCSI as a VMScluster Storage Interconnect 7-23h r                 ;               Table 7-7 (Cont.) SCSI Environment Parametersh  /               Parameter             Description   G               pk*0_fast             Enables SCSI adapters to perform in G                                     Fast SCSI Mode. When this parameter E                                     is set to 1, the default speed is H                                     set to Fast Mode; when the parameterG                                     is 0, the default speed is Standard )                                     Mode.   C               pk*0_host_id          Sets the SCSI device ID of hostmE                                     adapters to a value between 0 ando&                                     7.  G               scsi_poll             Enables console polling on all SCSInD                                     interconnects when the system is+                                     halted.   G               control_scsi_term     Enables and disables the terminator E                                     on the integral SCSI interconnect D                                     at the system bulkhead (for some-                                     systems).t  A               Before setting boot parameters, display the currentIE               settings of these parameters, as shown in the followings               examples:                  Examples                 1. >>>SHOW *BOOT*   ,                 boot_osflags            10,0+                 boot_reset              OFFa6                 bootdef_dev             dka200.2.0.6.0                 >>>n  I                  The first number in the boot_osflags parameter specifiesuG                  the system root. (In this example, the first number iseI                  10.) The boot_reset parameter controls the boot process.rE                  The default boot device is the device from which the A                  OpenVMS operating system is loaded. Refer to the F                  documentation for your specific system for additional%                  booting information..  6         7-24 SCSI as a VMScluster Storage Interconnect .                 D                  Note that you can identify multiple boot devices toH                  the system. By doing so, you cause the system to searchH                  for a bootable device from the list of devices that youF                  specify. The system then automatically boots from theI                  first device on which it finds bootable system software.oF                  In addition, you can override the default boot deviceE                  by specifying an alternative device name on the booto                  command line.  I                  Typically, the default boot flags suit your environment. F                  You can override the default boot flags by specifyingI                  boot flags dynamically on the boot command line with ther                  -flags option.i                 2. >>>SHOW *PK*o  )                 pka0_disconnect         1 )                 pka0_fast               1 )                 pka0_host_id            7e  D                  The pk*0_disconnect parameter determines whether orH                  not a target is allowed to disconnect from the SCSI busI                  while it acts on a command. On a multiple-host SCSI bus,tG                  the pk*0_disconnect parameter must be set to 1 so thats'                  disconnects can occur.p  C                  The pk*0_fast parameter controls whether Fast SCSI7I                  devices on a SCSI controller perform in Standard or FastsH                  Mode. When the parameter is set to 0, the default speedF                  is set to Standard Mode; when the pk*0_fast parameterI                  is set to 1, the default speed is set to Fast SCSI Mode.tE                  In this example, devices on SCSI controller pka0 aremE                  set to Fast SCSI Mode. This means that both StandardMH                  and Fast SCSI devices connected to this controller willG                  automatically perform at the appropriate speed for the C                  device (that is, in either Fast or Standard Mode).t  E                  The pk*0_host_id parameter assigns a bus node ID for E                  the specified host adapter. In this example, pka0 isn0                  assigned a SCSI device ID of 7.          I                            SCSI as a VMScluster Storage Interconnect 7-25e a  y                               3. >>>SHOW *POLL* *                 scsi_poll               ON  E                  Enables or disables polling of SCSI devices while in                   console mode.  A                  Set polling ON or OFF depending on the needs and C                  environment of your site. When polling is enabled,iD                  the output of the SHOW DEVICE is always up-to-date.H                  However, because polling can consume SCSI bus bandwidthG                  (proportional to number of unused SCSI IDs), you mightoI                  want to disable polling if one system on a multiple-host H                  SCSI bus will be in console mode for an extended period                  of time.   A                  Polling must be disabled during any hot pluggingsF                  operations. For information on hot plugging in a SCSI;                  VMScluster environment, see Section 7.7.6.n                 4. >>>SHOW *TERM*o0                 control_scsi_term       external  D                  Used on some systems (such as the AlphaStation 400)E                  to enable or disable the SCSI terminator next to the H                  external connector. Set the control_scsi_term parameterD                  to external if a cable is attached to the bulkhead.:                  Otherwise, set the parameter to internal.  :         7.6.5 Step 5: Install the OpenVMS Operating System  H               Refer to the OpenVMS Alpha or VAX upgrade and installationA               manual for information about installing the OpenVMStA               operating system. Perform the installation once fort@               each system disk in the VMScluster system. In mostG               configurations, there is a single system disk. Therefore,kC               you need to perform this step once, using any system.0  G               During the installation, when you are asked if the system C               is to be a cluster member, answer Yes. Then, completeaF               the installation according to the guidelines provided in-               VMScluster Systems for OpenVMS.n      6         7-26 SCSI as a VMScluster Storage Interconnect e  e              2         7.6.6 Step 6: Configure Additional Systems  C               Use the CLUSTER_CONFIG command procedure to configuretE               additional systems. Execute this procedure once for thelH               second host that you have configured on the SCSI bus. (See2               Section 7.7.1 for more information.)  %         7.7 Supplementary Information   D               The following sections provide supplementary technical@               detail and concepts about SCSI VMScluster systems.  :         7.7.1 Running the CLUSTER_CONFIG Command Procedure  E               You execute the CLUSTER_CONFIG.COM command procedure to D               set up and configure nodes in your VMScluster system.+E               Typically, the first computer is set up as a VMSclustereF               system during the initial OpenVMS installation procedureB               (see Section 7.6.5). The CLUSTER_CONFIG procedure isF               then used to configure additional nodes. However, if youG               originally installed OpenVMS without enabling clustering, B               the first time you run CLUSTER_CONFIG, the procedureA               converts the standalone system to a cluster system.s  I               To configure additional nodes in a SCSI VMScluster, execute D               CLUSTER_CONFIG.COM for each additional node. Table 7-8E               describes the steps to configure additional SCSI nodes.   =               Table 7-8 Steps for Installing Additional Nodes                      ProcedureD  A               1   From the first node, run the CLUSTER_CONFIG.COMnF                   procedure and select the default option [1] for ADD.  H               2   Answer Yes when CLUSTER_CONFIG.COM asks if you want to                   proceed.  I                                                  (continued on next page)I  "               ____________________E               +     In OpenVMS Version 6.2, sites that choose to boot D                     their VMScluster systems using the LANCP utilityE                     rather than DECnet use the CLUSTER_CONFIG_LAN.COMCI                     procedure.  See Section 3.5 for information about then6                     use of this alternative procedure.  I                            SCSI as a VMScluster Storage Interconnect 7-27l n  s              E               Table 7-8 (Cont.) Steps for Installing Additional Nodeso                     Proceduret  I               3   Supply the DECnet name and address of the node that you A                   are adding to the existing single-node cluster.   E               4   Confirm that this will be a node with a shared SCSI                    interconnect.   H               5   Answer No when the procedure asks if this node will be                   a satellite.  I               6   Configure the node to be a disk server if it will serve11                   disks to other cluster members.   H               7   Place the new node's system root on the default device                   offered.  G               8   Select a system root for the new node. The first node B                   uses SYS0. Take the default (SYS10 for the firstE                   additional node), or choose your own root numbering F                   scheme. You can choose from SYS1 to SYSn, where n is#                   hexadecimal FFFF.v  F               9   Select the default disk allocation class so that theH                   new node in the cluster will use the same ALLOCLASS as!                   the first node.p  @               10  Confirm whether or not there is a quorum disk.  G               11  Answer the questions about the sizes of the page file                     and swap file.  F               12  When CLUSTER_CONFIG.COM completes, boot the new nodeE                   from the new system root. For example, for SYSFF on ;                   disk DKA200, enter the following command:   '                    BOOT -FL FF,0 DKA200   G                   On the BOOT command, you can use the following flags:   -                   o  -FL indicates boot flags   .                   o  FF is the new system root  I                   o  0 means there are no special boot requirements, such +                      as conversational bootk  I               ___________________________________________________________t  A               Example 7-1 shows how to run the CLUSTER_CONFIG.COM >               procedure to set up an additional node in a SCSI               VMScluster.r  6         7-28 SCSI as a VMScluster Storage Interconnect    t              <               Example 7-1 Adding a Node to a SCSI VMScluster  +               $ @SYS$MANAGER:CLUSTER_CONFIG   8                          Cluster Configuration Procedure  O          Use CLUSTER_CONFIG.COM to set up or change a VMScluster configuration.hO          To ensure that you have the required privileges, invoke this procedure +          from the system manager's account.t  1                   Enter ? for help at any prompt.   5                           1. ADD a node to a cluster. <                           2. REMOVE a node from the cluster.G                           3. CHANGE a cluster member's characteristics.mF                           4. CREATE a duplicate system disk for CLU21.6                           5. EXIT from this procedure.  #                   Enter choice [1]:   @                   The ADD function adds a new node to a cluster.  O                   If the node being added is a voting member, EXPECTED_VOTES in P                   every cluster member's MODPARAMS.DAT must be adjusted, and the+                   cluster must be rebooted.   O             WARNING - If this cluster is running with multiple system disks anddI                       if common system files will be used, please, do not I                       proceed unless you have defined appropriate logical G                       names for cluster common files in SYLOGICALS.COM.sK                       For instructions, refer to the VMScluster Systems ford%                       OpenVMS manual.   :                             Do you want to continue [N]? y  O              If the new node is a satellite, the network databases on CLU21 arehP              updated. The network databases on all other cluster members must be              updated.c  P            For instructions, refer to the VMScluster Systems for OpenVMS manual.  9               What is the node's DECnet node name? SATURNb:               What is the node's DECnet node address? 7.77N               Is SATURN to be a clustered node with a shared SCSI bus (Y/N)? y/               Will SATURN be a satellite [Y]? NI/               Will SATURN be a boot server [Y]?A  I                                                  (continued on next page)i  I                            SCSI as a VMScluster Storage Interconnect 7-29t e  t              D               Example 7-1 (Cont.) Adding a Node to a SCSI VMScluster  P     This procedure will now ask you for the device name of SATURN's system root.J     The default device name (DISK$BIG_X5T5:) is the logical volume name of     SYS$SYSDEVICE:.   P               What is the device name for SATURN's system root [DISK$BIG_X5T5:]?D               What is the name of SATURN's system root [SYS10]? SYS22                   Creating directory tree SYS2 ...*                   System root SYS2 created  
         NOTE:iO              All nodes on the same SCSI bus must be members of the same clustereN              and must all have the same non-zero disk allocation class or eachM              will have a different name for the same disk and data corruption               will result.y  A               Enter a value for SATURN's ALLOCLASS parameter [7]:a:               Does this cluster contain a quorum disk [N]?*               Updating network database...9               Size of pagefile for SATURN [10000 blocks]?u                  .                  .                  .  E         7.7.2 Errors Reports and OPCOM Messages in Multiple-Host SCSI                Environments  I               Certain common operations, such as booting or shutting downfG               a host on a multiple-host SCSI bus, can cause other hosts_H               on the SCSI bus to experience errors. In addition, certainI               errors that are unusual in a single-host SCSI configurationiD               may occur more frequently on a multiple-host SCSI bus.  E               These errors are transient errors that OpenVMS detects,fI               reports, and recovers from without losing data or affectingaG               applications that are running. This section describes the I               conditions that generate these errors and the messages that H               are displayed on the operator console and entered into the               error log.          6         7-30 SCSI as a VMScluster Storage Interconnect o  t                       7.7.2.1 SCSI Bus Resets   F               When a host connected to a SCSI bus first starts, eitherF               by being turned on or by rebooting, it does not know theC               state of the SCSI bus and the devices on it. The ANSI C               SCSI-2 Standard provides a method called BUS RESET to F               force the bus and its devices into a known state. A hostH               typically asserts a RESET signal one or more times on eachI               of its SCSI buses when it first starts up and when it shuts I               down. While this is a normal action on the part of the host E               asserting RESET, other hosts consider this RESET signalSG               an error, because RESET requires that the hosts abort and >               restart all I/O operations that are in progress.  B               A host may also reset the bus in the midst of normalI               operation if it detects a problem that it cannot correct in I               any other way. These kinds of resets are uncommon but occur E               most frequently when something on the bus is disturbed. I               For example, an attempt to hot plug a SCSI device while the G               device is still active (see Section 7.7.6) or halting one H               of the hosts with CTRL/P can cause a condition that forces5               one or more hosts to issue a bus reset.e           7.7.2.2 SCSI Timeouts   G               When a host exchanges data with a device on the SCSI bus,nI               there are several different points where the host must waiteH               for the device or the SCSI adapter to react. In an OpenVMSF               system, the host is allowed to do other work while it isG               waiting, but a timer is started to make sure that it doescH               not wait too long. If the timer expires without a responseH               from the SCSI device or adapter, this is called a timeout.  0               There are three kinds of timeouts:  A               o  Disconnect timeout-The device accepted a command E                  from the host and disconnected from the bus while itWC                  processed the command but never reconnected to the G                  bus to finish the transaction. This error happens most H                  frequently when the bus is very busy. See Section 7.7.5D                  for more information. The disconnect timeout periodH                  varies with the device, but for most disks, it is about                  20 seconds.    I                            SCSI as a VMScluster Storage Interconnect 7-31h                   H               o  Selection timeout-The host tried to send a command to aH                  device on the SCSI bus, but the device did not respond.H                  This condition might happen if the device did not existD                  or if it were removed from the bus or powered down,C                  for example. (This failure is not more likely withoC                  a multi-initiator system; it is mentioned here forfE                  completeness.) The selection timeout period is aboutt                  0.25 seconds.  C               o  Interrupt timeout-The host expected the adapter toaF                  respond for any other reason, but it did not respond.H                  This error is usually an indication of a busy SCSI bus.I                  It is more common if you have initiator unit numbers setlF                  low (0 or 1) rather than high (6 or 7). The interrupt3                  timeout period is about 4 seconds.   B               Timeout errors are not inevitable on SCSI VMSclusterD               systems. However, they are more frequent on SCSI busesG               with heavy traffic and those with two initiators. They do F               not necessarily indicate a hardware or software problem.E               If they are logged frequently, you should consider waystH               to reduce the load on the SCSI bus (for example, adding an               additional bus).           7.7.2.3 Mount Verify  D               Mount verify is a condition declared by a host about aG               device. The host declares this condition in response to arG               number of possible transient errors, including bus resetseG               and timeouts. When a device is in the mount verify state, C               the host suspends normal I/O to it until the host canoF               determine that the correct device is there, and that theH               device is accessible. Mount verify processing then retriesE               outstanding I/Os in a way that ensures that the correctoG               data is written or read. Application programs are unawaresG               that a mount verify condition has occurred as long as them%               mount verify completes.   C               If the host cannot access the correct device within a I               certain amount of time, it declares a mount verify timeout, F               and application programs are notified that the device isE               unavailable. Manual intervention is required to restore E               a device to service after the host has declared a mount G               verify timeout. A mount verify timeout usually means that G               the error is not transient. The system manager can chooses  6         7-32 SCSI as a VMScluster Storage Interconnect    t              E               the timeout period for mount verify; the default is ones               hour.e  (         7.7.2.4 Shadow Volume Processing  D               Shadow volume processing is a process similar to mountC               verify, but it is for shadow set members. An error ontG               one member of a shadow set places the set into the volumeeG               processing state, which blocks I/O while OpenVMS attemptslC               to regain access to the member. If access is regained A               before shadow volume processing times out, then thenF               outstanding I/Os are reissued and the shadow set returnsG               to normal operation. If a timeout occurs, then the failed D               member is removed from the set. The system manager canF               select one timeout value for the system disk shadow set,H               and one for application shadow sets. The default value for*               both timeouts is 20 seconds.  F                 ________________________ Note ________________________  B                 The SCSI disconnect timeout and the default shadowC                 volume processing timeout are the same. If the SCSIrC                 bus is heavily utilized so that disconnect timeoutsd>                 may occur, it may be desirable to increase theA                 value of the shadow volume processing timeout. (A B                 recommended value is 60 seconds.) This may prevent@                 shadow set members from being expelled when they5                 experience disconnect timeout errors.   F                 ______________________________________________________  =         7.7.2.5 Expected OPCOM Messages in Multiple-Host SCSI   G               When a bus reset occurs, an OPCOM message is displayed asaF               each mounted disk enters and exits mount verification or'               shadow volume processing.S  D               When an I/O to a drive experiences a timeout error, anG               OPCOM message is displayed as that drive enters and exitsE=               mount verification or shadow volume processing.n  H               If a quorum disk on the shared SCSI bus experiences eitherI               of these errors, then additional OPCOM messages may appear, H               indicating that the connection to the quorum disk has been                lost and regained.  I                            SCSI as a VMScluster Storage Interconnect 7-33S s                           7.7.2.6 Error-Log Basics  H               In the OpenVMS system, the Error Log utility allows deviceB               drivers to save information about unusual conditionsE               that they encounter. In the past, most of these unusualsA               conditions have happened as a result of errors suchnC               as hardware failures, software failures, or transientU:               conditions (like loose cables, for example).  I               If you type the DCL command SHOW ERROR, the system displaysVE               a summary of the errors that have been logged since theC7               last time the system booted. For example:s                 $ SHOW ERROR  :               Device                           Error Count8               SALT$PKB0:                               68               $1$DKB500:                              108               PEA0:                                    18               SALT$PKA0:                               98               $1$DKA0:                                 0  B               In this case, 6 errors have been logged against hostD               SALT's SCSI port B (PKB0), 10 have been logged against+               disk $1$DKB500, and so forth.w  I               To see the details of these errors, you can use the command I               ANALYZE/ERROR/SINCE=DD-MMM-YYYY:HH:MM:SS at the DCL prompt. G               The output from this command displays a list of error-log @               entries with information similar to the following:  P   ******************************* ENTRY    2337. *******************************P    ERROR SEQUENCE 6.                               LOGGED ON:  CPU_TYPE 00000002P   DATE/TIME 29-MAY-1995 16:31:19.79                            SYS_TYPE 0000000D  *               <identification information>  -                      ERROR TYPE            03oP                                                     COMMAND TRANSMISSION FAILURE-                      SCSI ID               01eA                                                      SCSI ID = 1.e-                      SCSI LUN              00iB                                                      SCSI LUN = 0.-                      SCSI SUBLUN           00eE                                                      SCSI SUBLUN = 0. -                      PORT STATUS     00000E32vP                                                 %SYSTEM-E-RETRY, RETRY OPERATION  6         7-34 SCSI as a VMScluster Storage Interconnect e  e              &               <additional information>  H               For this discussion, the key elements are the "ERROR TYPE"G               and, in some instances, the "PORT STATUS" fields. In thisnB               example, the ERROR TYPE is "03, COMMAND TRANSMISSIONC               FAILURE", and the PORT STATUS is "00000E32, SYSTEM-E-e               RETRY".   7         7.7.2.7 Error-Log Entries in Multiple-Host SCSIt  H               The error-log entries listed in this section are likely toF               be logged in a multiple-host SCSI configuration, and youI               usually do not need to be concerned about them. You should,aG               however, examine any error-log entries for messages other 0               than those listed in this section.  4               o  ERROR TYPE 0007, BUS RESET DETECTED  H                  Occurs when the other system asserts the SCSI bus reset-                  signal. This happens when a:F  4                  o  System's power-up self-test runs  4                  o  Console INIT command is executed  ;                  o  EISA Configuration utility (ECU) is runn  D                  o  Console BOOT command is executed (several resets'                     occur in this case)   -                  o  System shutdown completes_  C                  This error causes all mounted disks to enter mountx                  verification.  <               o  ERROR TYPE 05, EXTENDED SENSE DATA RECEIVED  G                  When a SCSI bus is reset, an initiator must get "senseSE                  data" from each device. When the initiator gets thislI                  data, an "EXTENDED SENSE DATA RECEIVED" error is logged.U+                  This is expected behavior.t  <               o  ERROR TYPE 03, COMMAND TRANSMISSION FAILURE0                  PORT STATUS E32, SYSTEM-E-RETRY  D                  Occasionally, one host may send a command to a diskD                  while the disk is exchanging error information withF                  the other host. Many disks respond with a SCSI "BUSY"F                  code. The OpenVMS system responds to a SCSI BUSY codeF                  by logging this error and retrying the operation. YouH                  are most likely to see this error when the bus has beenG                  reset recently. This error does not always happen near   I                            SCSI as a VMScluster Storage Interconnect 7-35  e  o              D                  resets, but when it does, the error is expected and                  unavoidable.   (               o  ERROR TYPE 204, TIMEOUT  I                  An interrupt timeout has occurred (see Section 7.7.2.2). B                  The disk is put into mount verify when this error                  occurs.  (               o  ERROR TYPE 104, TIMEOUT  H                  A selection timeout has occurred (see Section 7.7.2.2).B                  The disk is put into mount verify when this error                  occurs.  -         7.7.3 Restrictions and Known ProblemsS  @               The current release of VMScluster software has theG               following restrictions when multiple hosts are configured #               on the same SCSI bus:o  B               1. A node's access to a disk will not fail over fromC                  a direct SCSI path to an MSCP served path. This is B                  not expected to be a significant limitation sinceF                  most of the failures that cause a SCSI disk to becomeH                  inaccessible to one node on the SCSI bus affect all theH                  nodes on the SCSI bus. Thus, when a failure occurs, theG                  served path to the disk tends to fail at the same timeb,                  that the direct path fails.  D                  Conversely, a node's access to a disk will not failE                  over from an MSCP served path to a direct SCSI path. G                  Normally, this type of failover is not a considerationrC                  because when OpenVMS discovers both a direct and a'E                  served path, it chooses the direct path permanently.iA                  It is necessary, however, to avoid situations inhD                  which the MSCP served path becomes available first,B                  and is selected by OpenVMS before the direct pathD                  becomes available. You must avoid this by observing%                  the following rules:   G                  o  A node that has a direct path to a SCSI system disk G                     must boot the disk directly from the SCSI port, not !                     over the LAN.e  6         7-36 SCSI as a VMScluster Storage Interconnect    l              E                  o  If a node is running the MSCP server, then a SCSI H                     disk must not be added to the multiple-host SCSI busF                     after the node boots. This is necessary to preventC                     the second node on the SCSI bus from seeing the C                     served path to the new disk and configuring it,tG                     thereby precluding the second node from configuringi$                     its direct path.  E               2. The SYS$DEVICE_SCAN system service (and the F$DEVICE_@                  lexical function that calls it) can be executedI                  repeatedly to obtain a list of devices on the system. IfgH                  this is done on a system with a multiple-host SCSI bus,F                  and the other system is running the MSCP server, thenF                  each device on the multiple-host SCSI bus is reported8                  twice by SYS$DEVICE_SCAN (or F$DEVICE).  I                  The reason for this is that each device on the multiple-rD                  host SCSI bus has two UCBs, one for the direct SCSII                  path, and one for the MSCP served path. (The MSCP served-#                  path is not used.)c  H                  Programs that use SYS$DEVICE_SCAN or F$DEVICE to searchF                  the IO database may need to be modified to check for,4                  and ignore, duplicate device names.  E               3. If a system on a multiple-host SCSI bus boots a diskSH                  that is served to it over the LAN, and the other systemF                  on the SCSI bus is running the MSCP server, then eachG                  device on the multiple-host SCSI bus is reported twice I                  by the DCL SHOW DEVICE command. This not known to result .                  in any other adverse effects.  F               4. Abruptly halting a system on a multiple-host SCSI busC                  (by typing CTRL/P on the console, for example) mayrE                  leave the SCSI adapter in a state that can interferetD                  with the operation of the other host on the bus. ItD                  is recommended that you either initialize, boot, orG                  continue an abruptly halted system as soon as possiblee*                  after it has been halted.  B               5. All I/O to a disk drive must be stopped while itsC                  microcode is updated. This typically requires more @                  precautions in a multiple-host environment thanB                  are needed in a single-host environment. Refer to>                  Section 7.7.6.3 for the necessary procedures.  I                            SCSI as a VMScluster Storage Interconnect 7-37w    e              D               6. The EISA Configuration Utility (ECU) causes a largeH                  number of SCSI bus resets. These resets cause the otherH                  system on the SCSI bus to pause while its I/O subsystemE                  recovers. It is suggested (though not required) thateH                  both systems on a shared SCSI bus be shut down when the                  ECU is run.  H               The current release of VMScluster software also places oneG               new restriction on the SCSI quorum disk, whether the disk-E               is located on a single-host SCSI bus or a multiple-hostoH               SCSI bus: the SCSI quorum disk must support Tagged CommandH               Queueing. This is required because of the special handlingC               that quorum I/O receives in the OpenVMS SCSI drivers.i  H               This restriction is not expected to be significant becauseG               all disks on a multiple-host SCSI bus must support TaggedrF               Command Queueing (see Section 7.7.7), and because quorum?               disks are normally not used on single-host buses.            7.7.4 Troubleshooting   F               The following sections describe troubleshooting tips forI               solving common problems in a VMScluster system using a SCSI                interconnect.i  $         7.7.4.1 Termination Problems  H               Verify that two terminators are on every SCSI interconnectI               (one at each end of the interconnect). The BA350 enclosure,iH               the DWZZA, and the KZPAA adapter have internal terminatorsC               that are not visible externally. (See Section 7.4.4.)o  @         7.7.4.2 Booting or Mounting Failures Caused by Incorrect                 Configurations  @               OpenVMS automatically detects configuration errorsG               described in this section and prevents the possibility ofII               data loss that could result from such configuration errors,lC               either by bugchecking or by refusing to mount a disk.   F               7.7.4.2.1 Bugchecks During the Bootstrap Process   ThereD               are three types of configuration error can can cause aI               bugcheck (the bugcheck code is: "VAXCLUSTER, Error detectedeG               by VMScluster software" during booting). These errors areh(               described in this section.  6         7-38 SCSI as a VMScluster Storage Interconnect                   I               When OpenVMS boots, it determines which devices are presentnI               on the SCSI bus by sending an inquiry command to every SCSI F               ID. When a device receives the inquiry, it indicates itsG               presence by returning data that indicates whether it is at'               disk, tape, or processor.   G               Some processor devices (host adapters) answer the inquiry B               without assistance from the operating system; othersH               require that the operating system be running. The adaptersC               supported in VMScluster systems require the operating C               system to be running. These adapters, with the aid ofo@               OpenVMS, pass information in their response to theG               inquiry that allows the recipient to detect the followingg#               configuration errors:c  G               o  Different controller device names on the same SCSI bust  D                  The OpenVMS device name of each adapter on the SCSIE                  bus must be identical (all named pkc0, for example),eA                  or the VMScluster software cannot coordinate therB                  host's accesses to storage (see Section 7.6.2 and                   Section 7.6.3).  F                  OpenVMS can check this automatically because it sendsI                  the controller letter in the inquiry response. A bootingSC                  system receives this response, and it compares the C                  remote controller letter with the local controller I                  letter. If a mismatch is detected, then an OPCOM message D                  is printed, and the system stops with an VAXCLUSTERF                  bugcheck to prevent the possibility of data loss. SeeC                  the description of the NOMATCH error in either the H                  Help Message utility or in Appendix A. (To use the HelpH                  Message utility for NOMATCH, enter HELP/MESSAGE NOMATCH$                  at the DCL prompt.)  :               o  Different or zero allocation class values  E                  Each host on the SCSI bus must have the same nonzero H                  disk allocation class value, or the VMScluster softwareG                  can not coordinate the host's accesses to storage (seeeF                  Section 7.6.3 and Section 7.6.2). The disk allocationB                  class value is controlled by the ALLOCLASS SYSGEN                  parameter._    I                            SCSI as a VMScluster Storage Interconnect 7-39  e                 G                  OpenVMS is able to automatically check this because itSE                  sends the ALLOCLASS value in the inquiry response. AtH                  booting system receives this response, and compares theG                  remote ALLOCLASS value with the local ALLOCLASS value. C                  If a mismatch or a zero value is detected, then an G                  OPCOM message is printed, and the system stops with aniI                  VAXCLUSTER bugcheck, in order to prevent the possibility_F                  of data loss. See the description of the ALLODIFF andI                  ALLOZERO errors in either the Help Message utility or in                   Appendix A.  '               o  Unsupported processorss  A                  Finally, there may be processors on the SCSI bus C                  that are not running OpenVMS or that do not return D                  the controller name or allocation class informationC                  needed to validate the configuration. If a booting E                  system receives an inquiry response and the response C                  does not contain the special OpenVMS configurationeE                  information, then an OPCOM message is printed and anaG                  VAXCLUSTER bugcheck occurs. See the description of theSG                  CPUNOTSUPP error in either the Help Message utility or                   in Appendix A.   @                  (If your system requires the presence of a non-D                  VMScluster processor device on a SCSI bus, refer toF                  the CPUNOTSUPP message description in either the HelpI                  Message utility or in Appendix A for instructions on the E                  use of a special SYSGEN parameter for this purpose.)   F                 ________________________ Hint ________________________  D                 The OPCOM error code that is printed for each of theB                 failures described above is preserved in R8 of theC                 VAXCLUSTER bugcheck. You can examine register R8 toRF                 quickly determine the cause of the error. For example:  %              $ ANAL/CRASH SYSDUMP.DMP                SDA> examine @r8;50O              2D462D47 49464E4F 43415453 250A0D4B  K..%STACONFIG-F-     00020430 O              4C412065 6854202C 46464944 4F4C4C41  ALLODIFF, The AL     00020440 O              6574656D 61726170 20535341 4C434F4C  LOCLASS paramete     00020450sO              20656874 20726F66 2065756C 61762072  r value for the      00020460bO              00000000 6E6F2072 6F737365 636F7270  processor on....     00020470   F                 ______________________________________________________  6         7-40 SCSI as a VMScluster Storage Interconnect                   ?               7.7.4.2.2 Mount Failures   There are two types of H               configuration error can can cause a disk to fail to mount.2               These are described in this section.  G               First, when a system boots from a disk on the shared SCSINE               bus, it may fail to mount the system disk. This happens H               if there is another system on the SCSI bus that is alreadyF               booted, and the other system is using a different deviceH               name for the system disk. (Two systems will disagree aboutH               the name of a device on the shared bus if their controllerI               names or allocation classes are misconfigured, as described0F               in the previous section.) If the system does not executeD               one of the bugchecks described in the previous sectionI               first, then the following error message is displayed on the                console:  O   %SYSINIT-E- error when mounting system device, retrying..., status = 007280B4   ;               The decoded representation of this status is:   F               VOLALRMNT,  another volume of same label already mounted  B               This error indicates that the system disk is already@               mounted in what appears to be another drive in theG               VMScluster system, so it is not mounted again. Solve this G               problem by checking the controller letters and allocationR@               class values for each node on the shared SCSI bus.  H               Second, SCSI disks on a shared SCSI bus will fail to mountE               on both systems unless the disk supports Tagged Command D               Queueing (TCQ). This is because TCQ provides a commandI               ordering guarantee that is required during VMScluster statee               transitions.  E               OpenVMS determines that another processor is present onEH               the SCSI bus during autoconfiguration, using the mechanismF               described in Section 7.7.4.2.1. The existence of anotherD               host on a SCSI bus is recorded and preserved until the               system reboots.   E               This information is used whenever an attempt is made to E               mount a non-TCQ device. If the device is on a multiple- I               host bus, the mount attempt fails and returns the following_               message:  1               %MOUNT-F-DRVERR, fatal drive error.   I                            SCSI as a VMScluster Storage Interconnect 7-41D    E              I               If the drive is intended to be mounted by multiple hosts on G               the same SCSI bus, then it must be replaced with one that                supports TCQ.S  F               Note that the first processor to boot on a multiple-hostD               SCSI bus does not receive an inquiry response from theE               other hosts because the other hosts are not yet runningOE               OpenVMS. Thus, the first system to boot is unaware thatiF               the bus has multiple hosts, and it allows non-TCQ drivesG               to be mounted. The other hosts on the SCSI bus detect theTG               first host, however, and they are prevented from mountingnF               the device. If two processors boot simultaneously, it isF               possible that they will detect each other, in which caseF               neither is allowed to mount non-TCQ drives on the shared               bus.           7.7.4.3 Grounding7  F               Having excessive ground offset voltages or exceeding theH               maximum SCSI interconnect length can cause system failuresG               or degradation in performance. See Section 7.7.8 for moreu<               information about SCSI grounding requirements.  $         7.7.4.4 Interconnect Lengths  C               Adequate signal integrity depends on strict adherence C               to SCSI bus lengths. Failure to follow the bus length B               recommendations can result in problems (for example,F               intermittent errors) that are difficult to diagnose. See@               Section 7.4.3 for information on SCSI bus lengths.  -         7.7.5 SCSI Arbitration Considerationsu  E               Only one initiator (typically, a host system) or target G               (typically, a peripheral device) can control the SCSI bus H               at any one time. In a computing environment where multipleD               targets frequently contend for access to the SCSI bus,F               you could experience throughput issues for some of theseF               targets. This section discusses control of the SCSI bus,I               how that control can affect your computing environment, and D               what you can do to achieve the most desirable results.  B               Control of the SCSI bus changes continually. When anH               initiator gives a command (such as READ) to a SCSI target,I               the target typically disconnects from the SCSI bus while itaG               acts on the command, allowing other targets or initiatorscH               to use the bus. When the target is ready to respond to the  6         7-42 SCSI as a VMScluster Storage Interconnect o  e              I               command, it must regain control of the SCSI bus. Similarly, H               when an initiator wishes to send a command to a target, it0               must gain control of the SCSI bus.  H               If multiple targets and initiators want control of the busF               simultaneously, bus ownership is determined by a processC               called arbitration, defined by the SCSI Standard. The D               default arbitration rule is simple: control of the busI               is given to the requesting initiator or target that has then"               highest unit number.  E               The following sections discuss some of the implications C               of arbitration and how you can respond to arbitrationt6               situations that affect your environment.  @         7.7.5.1 Arbitration Issues in Multiple-Disk Environments  B               When the bus is not very busy, and bus contention isA               uncommon, the simple arbitration scheme is adequate D               to perform I/O requests for all devices on the system.D               However, as initiators make more and more frequent I/OD               requests, contention for the bus becomes more and moreG               common. Consequently, targets with lower ID numbers begin H               to perform poorly because they are frequently blocked fromI               completing their I/O requests by other users of the bus (in F               particular, targets with the highest ID numbers). If theF               bus is sufficiently busy, low-numbered targets may neverG               complete their requests. This situation is most likely totH               occur on systems with more than one initiator because more;               commands can be outstanding at the same time.D  I               The OpenVMS system attempts to prevent low-numbered targetsoG               from being completely blocked by monitoring the amount of H               time an I/O request takes. If the request is not completedG               within a certain period, the OpenVMS system stops sending D               new requests until the tardy I/Os complete. While thisI               algorithm does not ensure that all targets get equal access I               to the bus, it does prevent low-numbered targets from beingr               totally blocked.            I                            SCSI as a VMScluster Storage Interconnect 7-43  I  s              <         7.7.5.2 Solutions for Resolving Arbitration Problems  H               If you find that some of your disks are not being servicedI               quickly enough during periods of heavy I/O, try some or all =               of the following, as appropriate for your site:   B               o  Assign the highest ID numbers to those disks that3                  require the fastest response time.   5               o  Spread disks across more SCSI buses.   E               o  Keep disks that need to be accessed only by a single G                  host (for example, page and swap disks) on a nonshared                   SCSI bus.  H               Another method that might provide for more equal servicingH               of lower and higher ID disks is to set the host IDs to theH               lowest numbers (0 and 1) rather than the highest. When youF               use this method, the host cannot gain control of the busG               to send new commands as long as any disk, including those E               with the lowest IDS, need the bus. Although this optionsH               is available to improve fairness under some circumstances,G               Digital considers this configuration to be less desirable ;               in most instances, for the following reasons:c  9               o  It can result in lower total throughput.,  H               o  It can result in timeout conditions if a command cannot.                  be sent within a few seconds.  F               o  It can cause physical configuration difficulties. ForH                  example, StorageWorks shelves such as the BA350 have noG                  slot to hold a disk with ID 7, but they do have a slot F                  for a disk with ID 0. If you change the host to ID 0,I                  you must remove a disk from slot 0 in the BA350, but youeI                  cannot move the disk to ID 7. If you have two hosts withuF                  IDs 0 and 1, you cannot use slot 0 or 1 in the BA350.H                  (Note, however, that you can have a disk with ID 7 in a                  BA353.)            6         7-44 SCSI as a VMScluster Storage Interconnect                   -         7.7.5.3 Arbitration and Bus Isolators   C               Any active device, such as a DWZZA, that connects busaF               segments introduces small delays as signals pass through@               the device from one segment to another. Under someA               circumstances, these delays can be another cause of E               unfair arbitration. For example, consider the following A               configuration, which could result in disk servicingf;               problems (starvation) under heavy work loads:   G               Although disk 5 has the highest ID number, there are somemG               circumstances under which disk 5 has the lowest access toeE               the bus. This can occur after one of the lower numberedeH               disks has gained control of the bus and then completed theH               operation for which control of the bus was needed. At thisG               point, disk 5 does not recognize that the bus is free andoF               might wait before trying to arbitrate for control of theG               bus. As a result, one of the lower numbered disks, having H               become aware of the free bus and then submitting a request8               for the bus, will gain control of the bus.  H               If you see this type of problem, the following suggestions/               can help you reduce its severity:n  @               o  Try to place all disks on the same bus segment.  D               o  If placing all disks on the same bus segment is notH                  possible (for example, if you have both some RZ28 disksH                  by themselves and an HSZ40), try to use a configurationF                  that has only one isolator between any pair of disks.  E               o  If your configuration requires two isolators betweena?                  a pair of disks (for example, to meet distance E                  requirements), try to balance the number of disks ono"                  each bus segment.  H               o  Follow the suggestions in Section 7.7.5.2 to reduce the2                  total traffic on the logical bus.              I                            SCSI as a VMScluster Storage Interconnect 7-45o x  l              H         7.7.6 Removal and Insertion of SCSI Devices While the VMScluster!               System is OperatingS  I               With proper procedures, certain SCSI devices can be removedSI               from or inserted onto an active SCSI bus without disruptinglC               the on-going operation of the bus. This capability iseC               referred to as hot plugging. Hot plugging can allow atF               suitably configured VMScluster system to continue to runI               while a failed component is replaced. Without hot plugging,nF               it is necessary to make the SCSI bus inactive and removeC               power from all the devices on the SCSI bus before anys<               device is removed from it or inserted onto it.  I               In a SCSI VMScluster system, hot plugging requires that allsH               devices on the bus have certain electrical characteristicsI               and be configured appropriately on the SCSI bus. SuccessfuluB               hot plugging also depends on strict adherence to theD               procedures described in this section. These proceduresE               ensure that the hot-plugged device is inactive and thato3               active bus signals are not disturbed.c  H                  Hot Plugging for SCSI Buses Behind a Storage Controller  B                 This section describes hot-plugging procedures forA                 devices that are on the same SCSI bus as the hosteE                 that is running OpenVMS. The procedures are differenthD                 for SCSI buses that are behind a storage controller,B                 such as the HSZ40. Refer to the storage controllerD                 documentation for the procedures to hot plug devices"                 that they control.  F                 ______________________________________________________  7         7.7.6.1 Terminology for Describing Hot Pluggingi  E               The terms shown in bold in this section are used in thes>               discussion of hot plugging rules and procedures.  D               o  A SCSI bus segment consists of two terminators, theE                  electrical path forming continuity between them, andUC                  possibly, some attached stubs. Bus segments may beeI                  connected together by bus isolators (for example, DWZZA)a=                  to form a logical SCSI bus or just SCSI bus.a    6         7-46 SCSI as a VMScluster Storage Interconnect    f              A               o  There are two types of connections on a segment:dF                  bussing connections, which break the path between twoH                  terminators, and stubbing connections, which disconnect'                  all or part of a stub.u  H               o  A device is active on the SCSI bus when it is assertingE                  one or more of the bus signals. A device is inactiveA:                  when it is not asserting any bus signals.  H                  The segment attached to a bus isolator is inactive whenE                  all devices on that segment, except possibly the bus (                  isolator, are inactive.  H               o  A port on a bus isolator has proper termination when itI                  is attached to a segment that is terminated at both ends_H                  and has TERMPWR in compliance with SCSI-2 requirements.  &         7.7.6.2 Rules for Hot Plugging  H               The following rules must be followed when planning for and&               performing hot plugging:  G               o  The device to be hot plugged, and all other devices onxI                  the same segment, shall meet the electrical requirements A                  described in Annex A, Section A.4, of the SCSI-3NG                  Parallel Interface (SPI) Standard, working draft X3T10LB                  /855D.[1] The SPI document places requirements onC                  the receivers and terminators on the segment where2@                  the hot plugging is being performed, and on theE                  transceivers, TERMPWR, termination, and power/ground D                  /signal sequencing, of the device that is being hot                  plugged.a  F                  All the devices in Table 7-2 meet these requirements,G                  except the DWZZA. The DWZZA's transceivers do not meetoI                  the requirements for glitch-free power on/off. The rulescE                  and procedures in this section have been adjusted to *                  compensate for this fact.    "               ____________________I               [1]   Reference to this draft standard is necessary becauseaG                     the SCSI-2 Standard does not adequately specify ther2                     requirements for hot plugging.  I                            SCSI as a VMScluster Storage Interconnect 7-47h d  s            H               o  Hot plugging shall occur only at a stubbing connection.  B                  This implies that a hot-plugged device shall makeF                  only one connection to the SCSI bus, the device shallB                  not provide termination for the SCSI bus, and theF                  device's connection shall not exceed the maximum stubI                  length, as shown in Figure 7-3. An example of a SCSI bus G                  topology showing the valid hot plugging connections isn,                  illustrated in Figure 7-16.    G               o  Precautions shall be used to ensure that electrostatic C                  discharge (ESD) does not damage devices or disrupt B                  active signals on the SCSI bus. These precautionsG                  shall be taken during the process of disconnecting and E                  connecting, as well as during the time that SCSI bus (                  conductors are exposed.  G               o  Precautions shall be used to ensure that ground offsetTB                  voltages do not pose a safety hazard and will notI                  interfere with SCSI bus signaling, especially in single-VG                  ended configurations. The procedures for measuring andeD                  eliminating ground offset voltages are described in                  Section 7.7.8.g  H               o  The device that is hot plugged shall be inactive duringH                  the disconnection and connection operations. Otherwise,1                  the SCSI bus may become hung.[1]   F                 ________________________ Note ________________________  D                 Ideally, a device will also be inactive whenever its6                 power is removed, for the same reason.  F                 ______________________________________________________  F                  The procedures for ensuring that a device is inactive2                  are described in Section 7.7.6.3.        "               ____________________A               [1]   OpenVMS will eventually detect a hung bus andrD                     reset it, but this may be temporarily disruptive  -                     to VMScluster operations.l  6         7-48 SCSI as a VMScluster Storage Interconnect s  s              H               o  A quorum disk shall not be hot plugged. This is becauseG                  there is no mechanism for stopping the I/O to a quorum G                  disk and because the replacement disk will not contain )                  the correct quorum file.   G                  The VMScluster system must be reconfigured to remove anF                  device as a quorum disk before that device is removedF                  from the bus. The procedure for accomplishing this isE                  described in VMScluster Systems for OpenVMS (Sectionr;                  8.3.3 in the OpenVMS Version 6.1 edition).u  D                  An alternate method for increasing the availabilityD                  of the quorum disk is to use an HSZ40 mirror set asB                  the quorum disk. This would allow a failed memberA                  to be replaced while maintaining the quorum diskr                  functionality.n  G               o  Disks shall be logically dismounted before removing orrI                  replacing them in a hot-plug operation. This is requiredsF                  to ensure that the disk is inactive and to ensure the.                  integrity of the file system.  G               o  The DWZZA shall be powered up when it is inserted ontonG                  an active SCSI bus. The DWZZA should remain powered up E                  at all times while it is attached to the active SCSI I                  bus. This is because the DWZZA can disrupt the operation I                  of the attached segments when it is powering up or down.   @               o  The segment attached to a bus isolator shall beI                  maintained in the inactive state whenever the other port F                  on the bus isolator is improperly terminated. This isG                  required because an improperly terminated bus isolator C                  port may pass erroneous signals to the other port.   C                  Thus, for a particular hot-plugging operation, one D                  of the segments attached to a bus isolator shall beD                  designated as the (potentially) active segment, andE                  the other shall be maintained in the inactive state,rB                  as illustrated in Figure 7-17. The procedures forE                  ensuring that a segment is inactive are described in !                  Section 7.7.6.3.m        I                            SCSI as a VMScluster Storage Interconnect 7-49t o  i              I                  Note that although a bus isolator may have more than one H                  stubbing connection and thus be capable of hot pluggingD                  on each of them, only one segment can be the activeC                  segment for any particular hot-plugging operation.h  C               o  Precautions shall be taken to ensure that the onlysC                  electrical conductor that contacts a connector pinaD                  is its mate. These precautions must be taken duringG                  the process of disconnecting and connecting as well asi?                  during the time the connector is disconnected.o  C               o  Devices shall be replaced with devices of the sameiF                  type (that is, if any member in the VMScluster systemD                  configures a SCSI ID as a "DK" or "MK" device, thenF                  that SCSI ID shall contain only "DK" or "MK" devices,G                  respectively, for as long as that VMScluster member isd                  running).  I                  Different implementations of the same device type may beoH                  substituted (for example, an RZ26L may be replaced withG                  an RZ28B). Note that the system will not recognize theoH                  change in device type until an attempt is made to mountE                  the new device. Also, note that host-based shadowing I                  continues to require that all members of a shadow set bep&                  the same device type.  I               o  SCSI IDs that are empty when a system boots shall remaineH                  empty as long as that system is running. This rule onlyI                  applies if there are multiple processors on the SCSI busoH                  and the MSCP server is loaded on any of them. (The MSCPE                  server is loaded when the system parameter MSCP_LOADt                  equals 1).r  F                  This is required to ensure that nodes on the SCSI busC                  use their direct path to the disk, rather than theoD                  served path. When the new device is configured on aI                  system (using SYSMAN IO commands), that system serves itlH                  to the second system on the shared SCSI bus. The secondG                  system automatically configures the new device via the F                  MSCP served path. Once this occurs, the second systemF                  will be unable to use its direct SCSI path to the newF                  device because failover from an MSCP served path to a5                  direct SCSI path is not implemented.A    6         7-50 SCSI as a VMScluster Storage Interconnect    r              C         7.7.6.3 Procedures for Ensuring That a Device or Segment IsI                 Inactive  G               Use the following procedures to ensure that a device or ah"               segment is inactive:  3               o  To ensure that a disk is inactive:   F                  1. Dismount the disk on all members of the VMScluster                     system.D  F                  2. Ensure that any I/O that can occur to a dismounted1                     disk is stopped, for example:   9                     -  Disable the disk as a quorum disk.   I                     -  Allocate the disk (using the DCL ALLOCATE command) I                        to block further mount or initialization attempts.   I                     -  Disable console polling by all halted hosts on theiH                        logical SCSI bus (by setting the console variableH                        SCSI_POLL to OFF, and entering the INIT command).  E                     -  Ensure that no host on the logical SCSI bus iseG                        executing power-up or initialization self-tests, I                        booting, or configuring the SCSI bus (using SYSMANe$                        IO commands).  @               o  To ensure that an HSZ40 controller is inactive:  B                  1. Dismount all of the HSZ40 virtual disks on all5                     members of the VMScluster system.   I                  2. Shut down the controller, following the procedures in D                     the HS Family of Array Controllers User's Guide.  5                  3. Power down the HSZ40, if desired.i  ;               o  To ensure that a host adapter is inactive:e  $                  1. Halt the system.  E                  2. Power down the system or set the console variableeG                     SCSI_POLL to OFF and then enter the INIT command on H                     the halted system. This ensures that the system will1                     not poll or respond to polls.n  A               o  To ensure that a segment is inactive, follow therB                  procedure described above for every device on the                  segment.   I                            SCSI as a VMScluster Storage Interconnect 7-51g t  ,              A         7.7.6.4 Procedure for Hot Plugging StorageWorks SBB Disks   <               To remove an SBB disk from an active SCSI bus:  F               1. Use an ESD grounding strap that is attached either toE                  a grounding stud or to unpainted metal on one of thefI                  cabinets in the system. Refer to the system installationh)                  procedures for guidance.   I               2. Follow the procedure in Section 7.7.6.3 to make the diskn                  inactive.  H               3. Squeeze the clips on the side of the SBB, and slide the4                  disk out of the StorageWorks shelf.  <               To insert an SBB disk onto an active SCSI bus:  F               1. Use an ESD grounding strap that is attached either toE                  a grounding stud or to unpainted metal on one of theyI                  cabinets in the system. Refer to the system installation )                  procedures for guidance.l  C               2. Ensure that the SCSI ID associated with the devicelF                  (either by jumpers or by the slot in the StorageWorks2                  shelf) conforms to the following:  B                  o  The SCSI ID is unique for the logical SCSI bus  I                  o  The SCSI ID is already configured as a "DK" device on )                     all of the following:s  G                     -  Any member of the VMScluster system that alreadys-                        has that ID configuredb  I                     -  Any OpenVMS processor on the same SCSI bus that is .                        running the MSCP server  ;               3. Slide the SBB into the StorageWorks shelf.   G               4. Configure the disk on VMScluster members, if required, *                  using SYSMAN IO commands.  1         7.7.6.5 Procedure for Hot Plugging HSZ40sl  D               To remove an HSZ40 controller from an active SCSI bus:  F               1. Use an ESD grounding strap that is attached either toE                  a grounding stud or to unpainted metal on one of the I                  cabinets in the system. Refer to the system installatione)                  procedures for guidance.   6         7-52 SCSI as a VMScluster Storage Interconnect    c              D               2. Follow the procedure in Section 7.7.6.3 to make the                   HSZ40 inactive.  B               3. The HSZ40 can be powered down, but it must remainH                  plugged in to the power distribution system to maintain                  grounding.i  F               4. Unscrew and remove the differential tri-link from the                  HSZ40.i  E               5. Protect all exposed connector pins from ESD and from C                  contacting any electrical conductor while they are                   disconnected.  D               To insert an HSZ40 controller onto an active SCSI bus:  F               1. Use an ESD grounding strap that is attached either toE                  a grounding stud or to unpainted metal on one of thecI                  cabinets in the system. Refer to the system installationrF                  procedures for guidance. Also, ensure that the groundE                  offset voltages between the HSZ40 and all components B                  that will be attached to it are within the limits,                  specified in Section 7.7.8.  E               2. Protect all exposed connector pins from ESD and fromtC                  contacting any electrical conductor while they are                   disconnected.  B               3. Power up the HSZ40 and ensure that the disk unitsD                  associated with the HSZ40 conform to the following:  F                  o  The disk units are unique for the logical SCSI bus  I                  o  The disk units are already configured as "DK" devices.%                     on the following:   G                     -  Any member of the VMScluster system that alreadyc-                        has that ID configuredp  I                     -  Any OpenVMS processor on the same SCSI bus that isd.                        running the MSCP server  A               4. Ensure that the HSZ40 will make a legal stubbing E                  connection to the active segment. (The connection is I                  legal when the tri-connector is attached directly to the E                  HSZ40 controller module, with no intervening cable.)   E               5. Attach the differential tri-link to the HSZ40, using H                  care to ensure that it is properly aligned. Tighten the                  screws.  I                            SCSI as a VMScluster Storage Interconnect 7-53i t  A              I               6. Configure the HSZ40 virtual disks on VMScluster members,e7                  as required, using SYSMAN IO commands.   8         7.7.6.6 Procedure for Hot Plugging Host Adapters  ?               To remove a host adapter from an active SCSI bus:r  F               1. Use an ESD grounding strap that is attached either toE                  a grounding stud or to unpainted metal on one of theaI                  cabinets in the system. Refer to the system installationu)                  procedures for guidance.o  F               2. Verify that the connection to be broken is a stubbingB                  connection. If not, then hot plugging must not be                  performed.   I               3. Follow the procedure in Section 7.7.6.3 to make the host "                  adapter inactive.  C               4. The system can be powered down, but it must remaintH                  plugged in to the power distribution system to maintain                  grounding.   E               5. Remove the "Y" cable from the host adapter's single- !                  ended connector.r  E               6. Protect all exposed connector pins from ESD and fromaC                  contacting any electrical conductor while they aret                  disconnected.  G               7. Do not unplug the adapter from the host's internal busq3                  while the host remains powered up.Z  E                  At this point, the adapter has disconnected from thetE                  SCSI bus. To remove the adapter from the host, poweriF                  down the host first, and then remove the adapter from)                  the host's internal bus._  ?               To insert a host adapter onto an active SCSI bus:   F               1. Use an ESD grounding strap that is attached either toE                  a grounding stud or to unpainted metal on one of the I                  cabinets in the system. Refer to the system installation F                  procedures for guidance. Also, ensure that the groundI                  offset voltages between the host and all components thatlG                  will be attached to it are within the limits specifieds"                  in Section 7.7.8.  6         7-54 SCSI as a VMScluster Storage Interconnect '  o              E               2. Protect all exposed connector pins from ESD and fromrC                  contacting any electrical conductor while they areh                  disconnected.  H               3. Ensure that the host adapter will make a legal stubbingG                  connection to the active segment (the stub length mustsH                  be within allowed limits, and the host adapter must not<                  provide termination to the active segment).  E               4. Plug the adapter into the host (if it is unplugged).c  F               5. Plug the system into the power distribution system to>                  ensure proper grounding. Power up if desired.  H               6. Attach the "Y" cable to the host adapter, ensuring that(                  it is properly aligned.  1         7.7.6.7 Procedure for Hot Plugging DWZZAsg  C               Use the following procedure to remove a DWZZA from ann               active SCSI bus:  F               1. Use an ESD grounding strap that is attached either toE                  a grounding stud or to unpainted metal on one of thevI                  cabinets in the system. Refer to the system installatione)                  procedures for guidance.e  F               2. Verify that the connection to be broken is a stubbingB                  connection. If not, then hot plugging must not be                  performed.   B               3. Do not power down the DWZZA. This can disrupt the=                  operation of the attached SCSI bus segments.   D               4. Determine which SCSI bus segment will remain activeA                  after the disconnection. Follow the procedure in_D                  Section 7.7.6.3 to make the other segment inactive.  G                  When the DWZZA is removed from the active segment, therF                  inactive segment must remain inactive until the DWZZAE                  is also removed from the inactive segment, or proper C                  termination is restored to the DWZZA port that was 6                  disconnected from the active segment.  C               5. The next step depends on the type of DWZZA and thew?                  segment that is being hot plugged, as follows:   I                            SCSI as a VMScluster Storage Interconnect 7-55                  I                  ________________________________________________________.I                  DWZZA_Type__Condition________Action_____________________c  F                  DWZZA-VA    Single-ended     Squeeze the clips on theH                              segment will     side of the SBB, and slideE                              remain active    the DWZZA-VA out of thenA                                               StorageWorks shelf.a  D                  DWZZA-VA    Differential     Unscrew and remove theH                              segment will     differential tri-link from;                              remain active    the DWZZA-VA.   G                  DWZZA-AA    Single-ended     Remove the "Y" cable from I                              segment will     the DWZZA-AA's single-ended 8                              remain active    connector.  D                  DWZZA-AA    Differential     Unscrew and remove theH                              segment will     differential tri-link fromI                  ____________remain_active____the_DWZZA-AA.______________   E               6. Protect all exposed connector pins from ESD and from C                  contacting any electrical conductor while they are                   disconnected.  8               To insert a DWZZA onto an active SCSI bus:  F               1. Use an ESD grounding strap that is attached either toE                  a grounding stud or to unpainted metal on one of thenI                  cabinets in the system. Refer to the system installationoF                  procedures for guidance. Also, ensure that the groundH                  offset voltages between the DWZZA-AA and all componentsB                  that will be attached to it are within the limits,                  specified in Section 7.7.8.  E               2. Protect all exposed connector pins from ESD and fromaC                  contacting any electrical conductor while they ares                  disconnected.  A               3. Ensure that the DWZZA will make a legal stubbing G                  connection to the active segment (the stub length must I                  be within allowed limits, and the DWZZA must not providev4                  termination to the active segment).  G               4. The DWZZA must be powered up. The SCSI segment that isyF                  being added must be attached and properly terminated.>                  All devices on this segment must be inactive.  6         7-56 SCSI as a VMScluster Storage Interconnect i                 F               5. The next step depends on the type of DWZZA, and which:                  segment is being hot plugged, as follows:  I                  ________________________________________________________cI                  DWZZA_Type__Condition________Action_____________________t  I                  DWZZA-VA    Single-ended     Slide the DWZZA-VA into theVA                              segment is       StorageWorks shelf.r&                              being hot$                              plugged  E                  DWZZA-VA    Differential     Attach the differentialeG                              segment is       tri-link to the DWZZA-VA,pG                              being hot        using care to ensure thatdE                              plugged          it is properly aligned.)A                                               Tighten the screws.a  E                  DWZZA-AA    Single-ended     Attach the "Y" cable toeI                              segment is       the DWZZA-AA, using care touH                              being hot        ensure that it is properly6                              plugged          aligned.  E                  DWZZA-AA    Differential     Attach the differential G                              segment is       tri-link to the DWZZA-VA, G                              being hot        using care to ensure thateE                              plugged          it is properly aligned.aI                  _____________________________Tighten_the_screws.________   I               6. If the newly attached segment has storage devices on it, H                  then configure them on VMScluster members, if required,*                  using SYSMAN IO commands.  I         7.7.7 OpenVMS Requirements for Devices Used on Multiple-Host SCSI                 VMScluster Systems  @               At this time, the only devices approved for use onG               multiple-host SCSI VMScluster systems are those listed in G               Table 7-2. While not specifically approved for use, otherwF               disk devices might be used in a multiple-host VMSclusterE               system when they conform to the following requirements:d  <               o  Support for concurrent multi-initiator I/O.  I               o  Proper management for the following states or conditionsd*                  on a per-initiator basis:  :                  -  Synchronous negotiated state and speed  *                  -  Width negotiated state  I                            SCSI as a VMScluster Storage Interconnect 7-57  c  e              G                  -  Contingent Allegiance and Unit Attention conditions   F               o  Tagged Command Queueing. This is needed to provide anH                  ordering guarantee used in VMScluster systems to ensureD                  that I/O has been flushed. The drive must implementG                  queuing that complies with Section 7.8.2 of the SCSI-2 0                  Standard, which says (in part):  E                     "...All commands received with a simple queue taglG                     message prior to a command received with an orderednH                     queue tag message, regardless of initiator, shall beG                     executed before that command with the ordered queueh3                     tag message." (Emphasis added.)i  0               o  Support for command disconnect.  H               o  A reselection timeout procedure compliant with Option bH                  of Section 6.1.4.2 of the SCSI-2 Standard. Furthermore,I                  the device shall implement a reselection retry algorithmtG                  that limits the amount of bus-time spent attempting to 4                  reselect a nonresponsive initiator.  I               o  Automatic read reallocation enabled (ARRE) and automaticsI                  write reallocation enabled (AWRE), (that is, drive-based G                  bad block revectoring), to prevent multiple hosts from H                  unnecessarily revectoring the same block. To avoid dataG                  corruption, it is essential that the drive comply with G                  Section 9.3.3.6 of the SCSI-2 Standard, which says (inn                  part):l  @                     "...The automatic reallocation shall then beF                     performed only if the target successfully recovers0                     the data." (Emphasis added.)  C               o  Storage devices should not supply TERMPWR. If theySF                  do, then it is necessary to apply configuration rulesF                  to ensure that there are no more than four sources of&                  TERMPWR on a segment.  D               Finally, if the device or any other device on the sameH               segment will be hot plugged, then the device must meet theC               electrical requirements described in Section 7.7.6.2.s      6         7-58 SCSI as a VMScluster Storage Interconnect                   $         7.7.8 Grounding Requirements  C               This section describes the grounding requirements forc=               electrical systems in a SCSI VMScluster system.s  E               Improper grounding can result in voltage differentials,nF               called ground offset voltages, between the enclosures inI               the configuration. Even small ground offset voltages across E               the SCSI interconnect (as shown in Step 3 in Table 7-9) H               can disrupt the configuration, and the user may experience9               performance degradation or data corruption.d  D               Table 7-9 describes important considerations to ensure               proper grounding.o  ;               Table 7-9 Steps for Ensuring Proper Groundingu                    Description  D               1  Ensure that site power distribution meets all local"                  electrical codes.  E               2  Inspect the entire site power distribution system tom                  ensure that:   =                  o  All outlets have power ground connectionsV  @                  o  A grounding prong is present on all computer*                     equipment power cables  C                  o  Power outlet neutral connections are not actuale&                     ground connections  F                  o  All grounds for the power outlets are connected to5                     the same power distribution panelv  F                  o  All devices that are connected to the same circuitC                     breaker as the computer equipment are UL or IECo                     approved  I                                                  (continued on next page)t        I                            SCSI as a VMScluster Storage Interconnect 7-59s V  l              C               Table 7-9 (Cont.) Steps for Ensuring Proper Groundingd                    Description  G               3  If you have difficulty verifying these conditions, youoE                  can use a hand-held multimeter to measure the groundrH                  offset voltage between any two cabinets. To measure theI                  voltage, connect the multimeter leads to unpainted metal G                  on each enclosure. Then, determine whether the voltageEF                  exceeds the following allowable ground offset limits:I                  ________________________________________________________Z                  SCSI Signaling ?                  Method                Maximum Allowable Offseth  4                  Single-ended          50 millivolts  5                  Differential          800 millivoltsn  H                  The multimeter method provides data for only the momentI                  it is measured. The ground offset values may change oversI                  time as additional devices are activated or plugged intohI                  the same power source. To ensure that the ground offsets.C                  remain within acceptable limits over time, DigitalfE                  recommends that you have a power survey performed byr)                  a qualified electrician.   I               4  If you are uncertain about the grounding situation or if G                  the measured offset exceeds the allowed limit, DigitaloD                  recommends that a qualified electrician correct theI                  problem. It may be necessary to install grounding cables B                  between enclosures to reduce the measured offset.  E               5  If an unacceptable offset voltage was measured and aiE                  ground cable was installed, then measure the voltage G                  again to ensure it is less than the allowed limits. If E                  not, an electrician must determine the source of the B                  ground offset voltage and reduce or eliminate it.                6         7-60 SCSI as a VMScluster Storage Interconnect      H                    I                                                                         8lI         _________________________________________________________________p  I                               VMScluster Systems That Span Multiple Sites     =               This chapter discusses multiple-site VMScluster C               configurations, with an emphasis on the new wide areauF               network ATM and DS3 communications services. It providesH               configuration guidelines and system management suggestionsH               for VMScluster systems in which multiple nodes are located>               at sites separated by relatively long distances.  F               The information in this chapter supersedes the Multiple-I               Site VMScluster Systems Addendum manual, and it supplements C               multiple-site VMScluster information in the followingc!               VMScluster manuals:g  /               o  VMScluster Systems for OpenVMSg  9               o  Guidelines for VMScluster Configurations   H               The sections that follow describe multiple-site VMSclusterI               configurations and some of the benefits you can derive fromb               them.   6         8.1 What Is a Multiple-Site VMScluster System?  F               A multiple-site VMScluster system is a VMScluster systemE               in which the member nodes are located in geographicallyeE               separate sites. When an organization has geographicallyaF               disperse sites, a multiple-site VMScluster system allowsD               the organization to realize the benefits of VMSclusterB               systems (for example, sharing data among sites whileF               managing data center operations at a single, centralized               location).  C               Figure 8-1 illustrates the concept of a multiple-site G               VMScluster system for a company with a manufacturing site D               located in Washington, D.C. and corporate headquartersF               in Philadelphia. This configuration spans a geographical;               distance of approximately 130 miles (210 km).   I                           VMScluster Systems That Span Multiple Sites 8-1c n                 E               The Fiber Distributed Data Interface (FDDI) has been indF               general use since VMS Version 5.4-3 to carry out clusterE               communications over distances of approximately 25 milese'               (approximately 40 km).[1]       0         8.1.1 ATM, DS3, and FDDI Intersite Links  H               The following link technologies between sites are approved6               for OpenVMS VAX and OpenVMS AXP systems:  1               o  Asynchronous Transfer Mode (ATM)w                 o  DS3                 o  FDDI   B               High-performance local area network (LAN) technologyG               combined with the ATM, DS3, and FDDI interconnects allowssB               you to utilize wide area network (WAN) communicationC               services in your VMScluster configuration. VMScluster.H               systems configured with the GIGAswitch crossbar switch andF               ATM, DS3, or FDDI interconnects approve the use of nodesF               located miles apart.[2] Section 8.3 describes VMSclusterI               systems and the WAN communications services in more detail.   F                 ________________________ Note ________________________  C                 To gain the benefits of disaster tolerance across a C                 multiple-site VMScluster, use the Business RecoveryUB                 Server combined with Volume Shadowing for OpenVMS.  >                 Consult your Digital Services Group or see theA                 Software Product Descriptions (SPDs) for complete <                 and up-to-date details about these products.  F                 ______________________________________________________  "               ____________________  ;               [1]   The cable route distance between sites. @               [2]   The actual distance between any two sites isD                     determined by the physical intersite cable-routeH                     distance, and not the straight-line distance between                     the sites.  7         8-2 VMScluster Systems That Span Multiple Sitesr g  t              :         8.1.2 Benefits of Multiple-Site VMScluster Systems  ?               The benefits you can realize with a multiple-sitee(               VMScluster system include:  I               ___________________________________________________________iI               Benefit__________Description_______________________________t  D               Remote           A few systems can be remotely locatedG               satellites       at a secondary site and can benefit fromsF               and nodes        centralized system management and otherF                                resources at the primary site, as shownH                                in Figure 8-2. For example, a main officeI                                data center could be linked to a warehouseSE                                or a small manufacturing site that hassG                                a few local nodes with directly attachedrD                                site-specific devices. Alternatively,E                                some engineering workstations could beDE                                installed in an office park across thegC                                city from the primary business site.   H               Data center      A single management team can manage nodesI               management       located in data centers at multiple sites.                consolidatione  G               Physical         Multiple sites can readily share devices ?               resource         such as high-capacity computers, @               sharing          tape libraries, disk archives, or0                                phototypesetters.  D               Remote           Backups can be made to archival mediaC               archiving        at any site in the cluster. A commonlF                                example would be to use disk or tape atH                                a single site to back up the data for allE                                sites in the multiple-site VMScluster.nG                                Backups of data from remote sites can be G                                made transparently (that is, without anyuI                                intervention required at the remote site).t              I                           VMScluster Systems That Span Multiple Sites 8-3t e  t          i  I               ___________________________________________________________aI               Benefit__________Description_______________________________n  E               Increased        In general, a multiple-site VMScluster F               availability     system provides all of the availabilityC                                advantages of a LAN VMScluster. (See A                                VMScluster Systems for OpenVMS forrE                                information about LANs.) Additionally, E                                by connecting multiple, geographically G                                separate sites, multiple-site VMScluster >                                configurations can increase theF                                availability of a system or elements of=                                a system in a variety of ways:d  C                                o  Logical volume/data availability- F                                   Volume shadowing or redundant arraysI                                   of independent disks (RAID) can be usedtH                                   to create logical volumes with membersD                                   at both sites. If one of the sitesF                                   becomes unavailable, data can remain>                                   available at the other site.  @                                o  Site failover-By adjusting theA                                   VOTES system parameter, you can E                                   select a preferred site to continue G                                   automatically if the other site fails E                                   or if communications with the other 0                                   site are lost.  G                                o  Disaster tolerance-When combined with H                                   the software, services, and managementE                                   procedures provided by the BusinesseF                                   Recovery Server and Volume ShadowingI                                   for OpenVMS products, you can achieve atG                                   high level of disaster tolerance. The F                                   Software Product Descriptions (SPDs)D                                   for these products provide further.                                   information.I               ___________________________________________________________               7         8-4 VMScluster Systems That Span Multiple Sitesm s  r              G         Figure 8-2 shows a VMScluster system with satellites accessible          from a remote site.s  E         Figure 8-2 Multiple-Site VMScluster Configuration with Remote                     Satellites       .         8.1.3 General Configuration Guidelines  C               The same configuration rules that apply to VMSclusterMG               systems on a LAN also apply to a multiple-site VMSclustermE               configuration that includes ATM, DS3, or FDDI intersite G               interconnects. General LAN configuration rules are statedn)               in the following documents:i  E               o  VAXcluster Software for OpenVMS VAX Software Product +                  Description (SPD 29.78.xx)   E               o  VMScluster Software for OpenVMS AXP Software Product +                  Description (SPD 42.18.xx)e  9               o  Guidelines for VMScluster Configurations   @               Some configuration guidelines are unique to multi-E               site VMSclusters, and these guidelines are described in                Section 8.3.4.  D         8.2 Using FDDI to Configure Multiple-Site VMScluster Systems  F               Since VMS Version 5.4-3, FDDI has been the most commonlyG               used means to connect two distant VMScluster sites. UsinguG               high-speed FDDI fiber-optic cables, you can connect sites F               with an intersite cable-route distance of up to 25 miles               (40 km).  =               You can connect sites using these FDDI methods:   F               o  To obtain maximum performance, use a full-duplex FDDIC                  link at 100 Mb/s both ways between GIGAswitch/FDDIpF                  bridges at each site for maximum intersite bandwidth.  H               o  To obtain maximum availability, use a dual FDDI ring atH                  100 Mb/s between dual attachment station (DAS) ports ofA                  wiring concentrators or GIGAswitch/FDDI bridges.r  I                           VMScluster Systems That Span Multiple Sites 8-5( E  n              B               o  For maximum performance and availability, use twoF                  disjoint FDDI LANs, each with dedicated host adaptersB                  and full-duplex FDDI intersite links connected to6                  GIGAswitch/FDDI bridges at each site.  H               Refer to the GIGAswitch/FDDI ATM Linecard Reference ManualB               for configuration information. Additional VMSclusterH               configuration guidelines and system management informationF               can be found in Guidelines for VMScluster ConfigurationsE               and VMScluster Systems for OpenVMS. See the Overview ofoF               OpenVMS Documentation for information about ordering the/               current version of these manuals.   I               The inherent flexibility of VMScluster systems and improvedPI               VMScluster LAN protocols also allow you to connect multipleeF               VMScluster sites using the ATM and/or DS3 communications               services.   D         8.3 Using WAN Services to Configure Multiple-Site VMScluster             Systemsl  G               This section provides an overview of the ATM and DS3 wideeG               area network (WAN) services, describes how you can bridgeeG               an FDDI interconnect to the ATM and/or DS3 communications H               services, and provides guidelines for using these services<               to configure multiple-site VMScluster systems.  D               The ATM and DS3 services provide long-distance, point-F               to-point communications that you can configure into yourI               VMScluster system to gain WAN connectivity. The ATM and DS3 G               services are available from most common telephone service )               carriers and other sources.   F                 ________________________ Note ________________________  =                 DS3 is not available in Europe and some other D                 locations. Also, ATM is a new and evolving standard,>                 and ATM services might not be available in all                 localities.i  F                 ______________________________________________________  @               ATM and DS3 services are approved for use with the)               following OpenVMS versions:   7         8-6 VMScluster Systems That Span Multiple Sites                  I               ___________________________________________________________dI               Service__Approved_Versions_of_OpenVMS______________________o  3               ATM      OpenVMS Version 6.2 or latert  I               DS3______OpenVMS_Version_6.1_or_later______________________c  =               The following sections describe the ATM and DS3 I               communications services and how to configure these services 2               in multiple-site VMScluster systems.  ,         8.3.1 The ATM Communications Service  I               The ATM communications service that uses the SONET physicalnC               layer (ATM/SONET) provides full-duplex communicationsiC               (that is, the bit rate is available simultaneously inoC               both directions as shown in Figure 8-3). ATM/SONET istD               compatible with multiple standard bit rates. The SONETI               OC-3 service at 155 Mb/s full-duplex rate is the best matchnG               to FDDI's 100 Mb/s bit rate. ATM/SONET OC-3 is a standardeF               service available in most parts of the world. In Europe,I               ATM/SONET is a high performance alternative to the older E3_               standard.   D               To transmit data, ATM frames (packets) are broken intoB               cells for transmission by the ATM service. Each cellD               has 53 bytes, of which 5 bytes are reserved for headerE               information and 48 bytes are available for data. At the H               destination of the transmission, the cells are reassembledH               into ATM frames. The use of cells permits ATM suppliers toI               multiplex and demultiplex multiple data streams efficiently.D               at differing bit rates. This conversion of frames intoC               cells and vice versa is transparent to higher layers.b  ,         8.3.2 The DS3 Communications Service  A               The DS3 communications service provides full-duplex D               communications as shown in Figure 8-4. DS3 (also knownH               as T3) provides the T3 standard bit rate of 45 Mb/s. T3 isF               the standard service available in North America and many'               other parts of the world.o          I                           VMScluster Systems That Span Multiple Sites 8-7l e  s                !         8.3.3 FDDI-to-WAN Bridges   F               You can use FDDI-to-WAN (for example, FDDI-to-ATM and/orG               FDDI-to-DS3) bridges to configure a VMScluster with nodesnH               in geographically separate sites, such as the one shown inF               Figure 8-5. In this figure, the VMScluster nodes at eachG               site communicate as though the two sites are connected by I               FDDI. The FDDI-to-WAN bridges make the existence of ATM and_9               DS3 transparent to the VMScluster software._  G               In Figure 8-5, the FDDI-to-DS3 bridges and DS3 operate asi               follows:  C               1. The local FDDI-to-DS3 bridge receives FDDI packetsr5                  addressed to nodes at the other site   F               2. The bridge converts the FDDI packets into DS3 packetsI                  and sends the packets to the other site via the DS3 link   B               3. The receiving FDDI-to-DS3 bridge converts the DS3H                  packets into FDDI packets and transmits them on an FDDI"                  ring at that site  A               Digital recommends using the GIGAswitch/FDDI systemn@               to construct FDDI-to-WAN bridges. Digital used theC               GIGAswitch/FDDI, combined with the DEFGT WAN T3/SONET F               option card, during qualification testing of the ATM andE               DS3 communications services in multiple-site VMScluster                systems.  D         8.3.4 Guidelines for Configuring ATM and DS3 in a VMScluster               System  H               When configuring a multiple-site VMScluster configuration,I               you must ensure that the intersite link's delay, bandwidth,m>               availability, and bit error rate characteristics@               meet application needs. This section describes theI               requirements and provides recommendations for meeting thoses               requirements.           7         8-8 VMScluster Systems That Span Multiple Sitesy m  f                       8.3.4.1 Requirements  H               To be a configuration approved by Digital, a multiple-site>               VMScluster must comply with the following rules:  G               Maximum intersite link     The total intersite link cable G               route distance             route distance between members F                                          of a multiple-site VMSclusterE                                          cannot exceed 150 miles (242eB                                          km). You can obtain exactH                                          distance measurements from your=                                          ATM or DS3 supplier.a  I                                          This distance restriction may beoF                                          exceeded by Business RecoveryC                                          Server configurations thatsF                                          meet Business Recovery Server=                                          configuration rules.   ?               Maximum intersite link     Average intersite link H               utilization                utilization in either directionE                                          must be less than 80% of the A                                          link's bandwidth in thatrD                                          direction for any 10-secondA                                          interval. Exceeding thistH                                          utilization is likely to resultI                                          in intolerable queuing delays ore5                                          packet loss.n  E               Intersite link             The intersite link must meet_D               specifications             the VMScluster requirements@                                          specified in Table 8-3.  F               VMScluster LAN             Apply the configuration rulesH               configuration rules        for VMScluster systems on a LANF                                          to a configuration. DocumentsG                                          describing configuration rulestI                                          are referenced in Section 8.1.3._              I                           VMScluster Systems That Span Multiple Sites 8-9  l  o                       8.3.4.2 Recommendations   >               When configuring the DS3 interconnect, apply the=               configuration guidelines for VMScluster systems C               interconnected by LANs that are stated in the cluster H               Software Product Descriptions (SPDs) and in the GuidelinesI               for VMScluster Configurations manual. VMScluster members atcG               each site can include any mix of satellites, systems, andp6               other interconnects such as CI and DSSI.  B               This section provides additional recommendations for<               configuring a multiple-site VMScluster system.  )               DS3 link capacity/protocols   I               The GIGAswitch with the WAN T3/SONET option card provides a G               full-duplex 155 Mb/s ATM/SONET link. The entire bandwidthnG               of the link is dedicated to the WAN option card. However,uG               The GIGAswitch/FDDI's internal design is based upon full-uD               duplex extensions to FDDI. Thus, the GIGAswitch/FDDI'sH               design limits the ATM/SONET link's capacity to 100 Mb/s in               each direction.a  G               The GIGAswitch with the WAN T3/SONET option card providescH               several protocol options that can be used over a DS3 link.E               Use the DS3 link in clear channel mode, which dedicatesDG               its entire bandwidth to the WAN option card. The DS3 link I               capacity varies with the protocol option selected. Protocol 1               options are described in Table 8-1:   ,               Table 8-1 DS3 Protocol Options  :               Protocol Option                Link Capacity  5               ATM[1] AAL-5[2] mode with       39 Mb/si               PLCP[3] disabled.   5               ATM AAL-5 mode with PLCP        33 Mb/se               enabled.  5               HDLC[4] mode (not currently     43 Mb/s                available).y  +               [1]Asynchronous Transfer Modec%               [2]ATM Adaptation Layer 4               [3]Physical Layer Convergence Protocol,               [4]High-Speed Datalink ControlI               ___________________________________________________________l  8         8-10 VMScluster Systems That Span Multiple Sites    s              G               For maximum link capacity, Digital recommends configuringfE               the WAN T3/SONET option card to use ATM AAL-5 mode withn               PLCP disabled.  !               Intersite bandwidtht  G               The intersite bandwidth can limit application locking and E               I/O performance (including volume shadowing or RAID set B               copy times) and the performance of the lock manager.  E               To promote reasonable response time, Digital recommends_H               that average traffic in either direction over an intersiteA               link not exceed 60% of the link's bandwidth in that F               direction for any 10-second interval. Otherwise, queuingH               delays within the FDDI-to-WAN bridges can adversely affect&               application performance.  D               Remember to account for both VMScluster communicationsB               (such as locking and I/O) and network communicationsE               (such as TCP/IP, LAT, and DECnet) when calculating link                utilization.                 Intersite delay   H               An intersite link introduces a one-way delay of up to 1 msF               per 100 miles of intersite cable route distance plus theI               delays through the FDDI-to-WAN bridges at each end. DigitalsC               recommends that you consider the effects of intersitedA               delays on application response time and throughput.   F               For example, intersite link one-way path delays have the#               following components:   F               o  Cable route one-way delays of 1 ms/100 miles (0.01 ms,                  /mile) for both ATM and DS3  D               o  FDDI-to-WAN bridge delays (approximately 0.5 ms per8                  bridge, and 2 bridges per one-way trip)  ?               Calculate the delays for a round trip as follows:e  7                                  WAN ROUND TRIP DELAY =   O            2x( N miles x  0.01 ms per mile + 2  x 0.5 ms per FDDI-WAN  bridge )m  C               An I/O write operation that is MSCP served requires al9               minimum of two round-trip packet exchanges:e  A                      WAN I/O Write Delay = 2xWAN Round Trip Delay   I                          VMScluster Systems That Span Multiple Sites 8-11e y  e                H               Thus, an I/O write over a 100-mile WAN link takes at leastE               8 ms longer than the same I/O write over a short, local                FDDI.   I               Similarly, a lock operation typically requires a round trip "               exchange of packets:  C                     WAN Lock Operation Delay = WAN Round Trip Delayr  H               An I/O operation with N locks to synchronize it incurs the)               following delay due to WAN:_  ;                             WAN Locked IO Operation Delay =n  C                    (N  x WAN Lock Operation Delay)  + WAN I/O Delayl                 Bit error ratios  I               The bit error ratio (BER) parameter is an important measurelE               of the frequency that bit errors are likely to occur on H               the intersite link. You should consider the effects of bitF               errors on application throughput and responsiveness whenH               configuring a multiple-site VMScluster. Intersite link bitG               errors can result in packets being lost and retransmitted.E               with consequent delays in application I/O response timeoD               (see Section 8.3.6). You can expect application delaysF               ranging from a few hundred milliseconds to a few seconds?               each time a bit error causes a packet to be lost.c  )               Intersite link availabilityx  G               Interruptions of intersite link service can result in the G               resources at one or more sites becoming unavailable untili;               connectivity is restored (see Section 8.3.5).                  System disks  F               Sites with nodes contributing quorum votes should have a9               local system disk or disks for those nodes.m                 System managemento  A               A large, multiple-site VMScluster requires a systemFE               management staff trained to support an environment thatnI               consists of a large number of diverse systems that are used 5               by many people performing varied tasks.o  8         8-12 VMScluster Systems That Span Multiple Sites u  d              !               Microwave DS3 linksh  I               You can provide portions of a DS3 link with microwave radioiE               equipment. The specifications in Section 8.3.6 apply tolG               any DS3 link. The BER and availability of microwave radiocF               portions of a DS3 link are affected by local weather andG               the length of the microwave portion of the link. ConsiderTF               working with a microwave consultant who is familiar withE               your local environment if you plan to use microwaves asn%               portions of a DS3 link.d  )         8.3.5 Availability Considerations   C               If the FDDI-to-WAN bridges and the link that connectsa@               multiple sites become temporarily unavailable, the+               following events could occur:f  G               o  Intersite link failures can result in the resources atuG                  one or more sites becoming unavailable until intersite *                  connectivity is restored.  D               o  Intersite link bit errors (and ATM cell losses) and+                  unavailability can affect:t  )                  -  System responsiveness   4                  -  System throughput (or bandwidth)  5                  -  Virtual circuit (VC) closure rate   @                  -  VMScluster transition and site failover time  E               Many communication service carriers offer availability- H               enhancing options, including path diversity and protectiveF               switching, that can significantly increase the intersite"               link's availability.           8.3.6 Specifications  D               This section describes the requirements for successfulH               communications and performance with the WAN communications               services.i  >               To assist you in communicating your requirements>               to a WAN service supplier, this section uses WANH               specification terminology and definitions commonly used byF               telecommunications service providers. These requirementsB               and goals are derived from a combination of BellcoreB               Communications Research specifications and a Digital7               analysis of error effects on VMSclusters._  I                          VMScluster Systems That Span Multiple Sites 8-13u e  d              @               Table 8-2 describes terminology that will help youE               understand the Bellcore and VMScluster requirements and &               goals used in Table 8-3.  H               Use the Bellcore and VMScluster requirements for ATM/SONETI               - OC3 and DS3 service error performance (quality) specified G               in Table 8-3 to help you assess the impact of the serviceiF               supplier's service quality, availability, down time, andA               service-interruption frequency goals on the system.o  F                 ________________________ Note ________________________  ?                 To ensure that the VMScluster system meets your_A                 application response-time requirements, you mightsB                 need to establish WAN requirements that exceed theE                 Bellcore and VMScluster requirements and goals statedl                 in Table 8-3.   F                 ______________________________________________________                                                    8         8-14 VMScluster Systems That Span Multiple Sites                   @         Table 8-2 Bellcore and VMScluster Requirements and Goals                   Terminology.  B   Specification    Requirements                              Goals  B   Bellcore         Bellcore specifications are the           TheseD   Communication    recommended "generic error performance    are theH   Research         requirements and objectives" documented   recommendedD                    in the Bellcore Technical Reference TR-   minimumD                    TSY-000499 TSGR: Common Requirements.     values.E                    These specifications are adopted by WAN   Bellcore H                    suppliers as their service guarantees.    calls theseH                    The FCC has also adopted them for         goals theirI                    tariffed services between common          "objectives"fC                    carriers. However, some suppliers will    in thefI                    contract to provide higher service-       TSGR: CommonnI                    quality guarantees at customer request.   RequirementsgF                    Other countries have equivalents to the   document.  :                    Bellcore specifications and parameters.  H         VMScluster In order for Digital to approve a         For optimalG                    configuration, parameters must meet       VMScluster.G                    or exceed the values shown in the         operation,o@                    VMScluster Requirement column in          allG                    Table 8-3.                                parameters C                    ________________________________________  shouldeD                    IF..._______THEN..._____________________  meet or  G                    These       VMScluster performance will   exceed the G                    values      probably be unsatisfactory    VMScluster A                    are not     because of interconnect       GoalnF                    met         errors/error recovery delays, values inG                                and VC closures that may      Table 8-3.   I                                produce VMScluster state      Note that if I                                transitions and/or site       these values G                                failover.                     are met or   F                    These       Interconnect bit error-       exceeded,A                    values      related recovery delays       then I                    are         will not significantly        interconnect G                    met or      degrade average VMScluster    bit errors D                    exceeded    throughput. VMScluster        and bitB                                response time should be       errorE                                generally satisfactory.       recoverysC                                Note that if the              delaysoC                                requirements are only being   shouldeE                                met, there may be several     not sig-fG                                application pauses per hour.  nificantly D                                [1]                           degradeD                                                              averageG                                                              VMSclustergH                                                              throughput.  H                                                 (continued on next page)  G                        VMScluster Systems That Span Multiple Sites 8-15    e  M         Table 8-3 VMScluster DS3 and SONET OC3 Error Performance Requirementsm  F                         Bellcore    Bellcore   VMScluster   VMSclusterM         Parameter       Requirement Goal       Requirement  Goal[1]     Unitso  G                                                              VMSclustermE                                                              response H                                                              time shouldI                                                              be generally C                                                              satis- E                                                              factory, E                                                              although F                                                              there mayE                                                              be brief H                                                              applicationI                                                              pauses a fewSF                                                              times perD                                                              day.[2]  A         [1]Pauses are due to a virtual circuit retransmit timeoutaC         resulting from a lost packet on one or more NISCA transportiB         virtual circuits. Each pause might last from a few hundred&         milliseconds to a few seconds.  I         [2]Application pauses may occur every hour or so (similar to what G         is described under VMScluster Requirement in Table 8-3) because +         of packet loss caused by bit error.   G         [3]Application requirements might need to be more rigorous than :         those shown in the VMScluster Requirements column.         Table Key   G        o Availability-The long-term fraction or percentage of time thatkE          a transmission channel performs as intended. Availability issF          frequently expressed in terms of unavailability or down time.E        o BER (bit error ratio)-"The BER is the ratio of the number of E          bits in error to the total number of bits transmitted during B          a measurement period, excluding all burst errored secondsB          (defined below) in the measurement period. During a burstH          errored second, neither the number of bit errors nor the number          of bits is counted." B        o BES (burst errored second)-"A burst errored second is any8          errored second containing at least 100 errors."G        o Channel-The term for a link that is used in the Bellcore TSGR:t>          Common Requirements document for a SONET or DS3 link.E        o Down time-The long-term average amount of time (for example,aG          minutes) that a transmission channel is not available during a 8          specified period of time (for example, 1 year).  D          "...unavailability or downtime of a channel begins when theC          first of 10 [or more] consecutive Severely Errored Seconds F          (SESs) occurs, and ends when the first of 10 consecutive non-          SESs occurs."  F          The unavailable time is counted from the first SES in the 10-          SES sequence.  I                                                  (continued on next page)o  8         8-16 VMScluster Systems That Span Multiple Sites TH         Table 8-3 (Cont.) VMScluster DS3 and SONET OC3 Error Performance&                           Requirements   E                         Bellcore    Bellcore  VMScluster   VMScluster K         Parameter       Requirement Goal      Requirement  Goal[1]    Unitsn  E         Errored          <1.0%      <0.4%     <1.0%     <0.028%     %dI         seconds (%                                                  ES/24dI         ES)_________________________________________________________hr___D  G         [1]Application requirements might need to be more rigorous thana:         those shown in the VMScluster Requirements column.         Table Key   F          "The time for the end of unavailable time is counted from the<          first fault-free second in the [non-SES] sequence."  A        o ES (errored second)-"An errored second is any one-secondo1          interval containing at least one error."[F        o SES (severely errored second)-"...an SES is a second in which'          the BER is greater than 10-3."   G        o Availability-The long-term fraction or percentage of time thatuE          a transmission channel performs as intended. Availability isyF          frequently expressed in terms of unavailability or down time.E        o BER (bit error ratio)-"The BER is the ratio of the number ofpE          bits in error to the total number of bits transmitted during_B          a measurement period, excluding all burst errored secondsB          (defined below) in the measurement period. During a burstH          errored second, neither the number of bit errors nor the number          of bits is counted." B        o BES (burst errored second)-"A burst errored second is any8          errored second containing at least 100 errors."G        o Channel-The term for a link that is used in the Bellcore TSGR:l>          Common Requirements document for a SONET or DS3 link.E        o Down time-The long-term average amount of time (for example,eG          minutes) that a transmission channel is not available during ai8          specified period of time (for example, 1 year).  D          "...unavailability or downtime of a channel begins when theC          first of 10 [or more] consecutive Severely Errored SecondsiF          (SESs) occurs, and ends when the first of 10 consecutive non-          SESs occurs."  F          The unavailable time is counted from the first SES in the 10-          SES sequence.  F          "The time for the end of unavailable time is counted from the<          first fault-free second in the [non-SES] sequence."A        o ES (errored second)-"An errored second is any one-secondn1          interval containing at least one error." F        o SES (severely errored second)-"...an SES is a second in which'          the BER is greater than 10-3."a  I                                                  (continued on next page)o  I                          VMScluster Systems That Span Multiple Sites 8-17t                   H         Table 8-3 (Cont.) VMScluster DS3 and SONET OC3 Error Performance&                           Requirements  C                        Bellcore    Bellcore  VMScluster  VMScluster/J         Parameter      Requirement Goal      Requirement Goal[1]     Units  D                          The ES parameter can also be expressed as a>                          count of errored seconds, as follows:  G         [1]Application requirements might need to be more rigorous than :         those shown in the VMScluster Requirements column.         Table Keym  G        o Availability-The long-term fraction or percentage of time that E          a transmission channel performs as intended. Availability is F          frequently expressed in terms of unavailability or down time.E        o BER (bit error ratio)-"The BER is the ratio of the number of E          bits in error to the total number of bits transmitted during B          a measurement period, excluding all burst errored secondsB          (defined below) in the measurement period. During a burstH          errored second, neither the number of bit errors nor the number          of bits is counted." B        o BES (burst errored second)-"A burst errored second is any8          errored second containing at least 100 errors."G        o Channel-The term for a link that is used in the Bellcore TSGR: >          Common Requirements document for a SONET or DS3 link.E        o Down time-The long-term average amount of time (for example, G          minutes) that a transmission channel is not available during an8          specified period of time (for example, 1 year).  D          "...unavailability or downtime of a channel begins when theC          first of 10 [or more] consecutive Severely Errored SecondsgF          (SESs) occurs, and ends when the first of 10 consecutive non-          SESs occurs."  F          The unavailable time is counted from the first SES in the 10-          SES sequence.  F          "The time for the end of unavailable time is counted from the<          first fault-free second in the [non-SES] sequence."A        o ES (errored second)-"An errored second is any one-second 1          interval containing at least one error." F        o SES (severely errored second)-"...an SES is a second in which'          the BER is greater than 10-3."   I                                                  (continued on next page)a  8         8-18 VMScluster Systems That Span Multiple Sites    .              H         Table 8-3 (Cont.) VMScluster DS3 and SONET OC3 Error Performance&                           Requirements  F                          Bellcore     Bellcore  VMScluster  VMSclusterM         Parameter        Requirement  Goal      Requirement Goal[1]     Units   F                          <864       <345      <864      <24         ESG                                                                     per I                                                                     24-hr J                                                                     periodD                                                                     G         [1]Application requirements might need to be more rigorous thanc:         those shown in the VMScluster Requirements column.         Table Keyi  G        o Availability-The long-term fraction or percentage of time thatwE          a transmission channel performs as intended. Availability isnF          frequently expressed in terms of unavailability or down time.E        o BER (bit error ratio)-"The BER is the ratio of the number ofiE          bits in error to the total number of bits transmitted duringvB          a measurement period, excluding all burst errored secondsB          (defined below) in the measurement period. During a burstH          errored second, neither the number of bit errors nor the number          of bits is counted."lB        o BES (burst errored second)-"A burst errored second is any8          errored second containing at least 100 errors."G        o Channel-The term for a link that is used in the Bellcore TSGR:i>          Common Requirements document for a SONET or DS3 link.E        o Down time-The long-term average amount of time (for example, G          minutes) that a transmission channel is not available during at8          specified period of time (for example, 1 year).  D          "...unavailability or downtime of a channel begins when theC          first of 10 [or more] consecutive Severely Errored SecondspF          (SESs) occurs, and ends when the first of 10 consecutive non-          SESs occurs."  F          The unavailable time is counted from the first SES in the 10-          SES sequence.  F          "The time for the end of unavailable time is counted from the<          first fault-free second in the [non-SES] sequence."A        o ES (errored second)-"An errored second is any one-secondu1          interval containing at least one error."sF        o SES (severely errored second)-"...an SES is a second in which'          the BER is greater than 10-3."   I                                                  (continued on next page)   I                          VMScluster Systems That Span Multiple Sites 8-19o n  t              H         Table 8-3 (Cont.) VMScluster DS3 and SONET OC3 Error Performance&                           Requirements  D                         Bellcore    Bellcore  VMScluster  VMSclusterK         Parameter       Requirement Goal      Requirement Goal[1]     Units   G         Burst errored     4         -          4        Bellcore    BES H         seconds                                         Goal        /day         (BES)[2]G         [1]Application requirements might need to be more rigorous than :         those shown in the VMScluster Requirements column.#         [2]Averaged over many days.          Table Keye  G        o Availability-The long-term fraction or percentage of time thatfE          a transmission channel performs as intended. Availability is_F          frequently expressed in terms of unavailability or down time.E        o BER (bit error ratio)-"The BER is the ratio of the number of E          bits in error to the total number of bits transmitted duringmB          a measurement period, excluding all burst errored secondsB          (defined below) in the measurement period. During a burstH          errored second, neither the number of bit errors nor the number          of bits is counted." B        o BES (burst errored second)-"A burst errored second is any8          errored second containing at least 100 errors."G        o Channel-The term for a link that is used in the Bellcore TSGR:c>          Common Requirements document for a SONET or DS3 link.E        o Down time-The long-term average amount of time (for example,nG          minutes) that a transmission channel is not available during a 8          specified period of time (for example, 1 year).  D          "...unavailability or downtime of a channel begins when theC          first of 10 [or more] consecutive Severely Errored Seconds.F          (SESs) occurs, and ends when the first of 10 consecutive non-          SESs occurs."  F          The unavailable time is counted from the first SES in the 10-          SES sequence.  F          "The time for the end of unavailable time is counted from the<          first fault-free second in the [non-SES] sequence."A        o ES (errored second)-"An errored second is any one-secondo1          interval containing at least one error." F        o SES (severely errored second)-"...an SES is a second in which'          the BER is greater than 10-3."i  I                                                  (continued on next page)p  8         8-20 VMScluster Systems That Span Multiple Sites e                 H         Table 8-3 (Cont.) VMScluster DS3 and SONET OC3 Error Performance&                           Requirements  D                         Bellcore    Bellcore  VMScluster  VMSclusterK         Parameter       Requirement Goal      Requirement Goal[1]     Units   K         Bit error        1x10 -9    2x10 -10  1x10 -9   6x10 -12    Errored_  H         ratio (BER)[3]                                              bitsH                                                                     /bitG         [1]Application requirements might need to be more rigorous than :         those shown in the VMScluster Requirements column.F         [3]Does not include any burst errored seconds occurring in the         measurement period.          Table Key   G        o Availability-The long-term fraction or percentage of time that E          a transmission channel performs as intended. Availability is F          frequently expressed in terms of unavailability or down time.E        o BER (bit error ratio)-"The BER is the ratio of the number of E          bits in error to the total number of bits transmitted during B          a measurement period, excluding all burst errored secondsB          (defined below) in the measurement period. During a burstH          errored second, neither the number of bit errors nor the number          of bits is counted."hB        o BES (burst errored second)-"A burst errored second is any8          errored second containing at least 100 errors."G        o Channel-The term for a link that is used in the Bellcore TSGR: >          Common Requirements document for a SONET or DS3 link.E        o Down time-The long-term average amount of time (for example, G          minutes) that a transmission channel is not available during a 8          specified period of time (for example, 1 year).  D          "...unavailability or downtime of a channel begins when theC          first of 10 [or more] consecutive Severely Errored Seconds F          (SESs) occurs, and ends when the first of 10 consecutive non-          SESs occurs."  F          The unavailable time is counted from the first SES in the 10-          SES sequence.  F          "The time for the end of unavailable time is counted from the<          first fault-free second in the [non-SES] sequence."A        o ES (errored second)-"An errored second is any one-second 1          interval containing at least one error." F        o SES (severely errored second)-"...an SES is a second in which'          the BER is greater than 10-3."   I                                                  (continued on next page)   I                          VMScluster Systems That Span Multiple Sites 8-21                    H         Table 8-3 (Cont.) VMScluster DS3 and SONET OC3 Error Performance&                           Requirements  D                         Bellcore    Bellcore  VMScluster  VMSclusterK         Parameter       Requirement Goal      Requirement Goal[1]     Units   G         DS3 channel      None        97       None      Bellcore    Min G         unavailability              @ 250               Goal        /yr *                                     miles,(                                     lin-)                                     early '                                     de- *                                     creas-'                                     ing )                                     to 24 )                                     @  25 )                                     milesa  I                                                  (continued on next page)                                                     8         8-22 VMScluster Systems That Span Multiple Sites 2  p              H         Table 8-3 (Cont.) VMScluster DS3 and SONET OC3 Error Performance&                           Requirements  D                         Bellcore    Bellcore  VMScluster  VMSclusterK         Parameter       Requirement Goal      Requirement Goal[1]     Units G         [1]Application requirements might need to be more rigorous thana:         those shown in the VMScluster Requirements column.         Table Keyi  G        o Availability-The long-term fraction or percentage of time thatxE          a transmission channel performs as intended. Availability isoF          frequently expressed in terms of unavailability or down time.E        o BER (bit error ratio)-"The BER is the ratio of the number oftE          bits in error to the total number of bits transmitted duringiB          a measurement period, excluding all burst errored secondsB          (defined below) in the measurement period. During a burstH          errored second, neither the number of bit errors nor the number          of bits is counted."oB        o BES (burst errored second)-"A burst errored second is any8          errored second containing at least 100 errors."G        o Channel-The term for a link that is used in the Bellcore TSGR:e>          Common Requirements document for a SONET or DS3 link.E        o Down time-The long-term average amount of time (for example,pG          minutes) that a transmission channel is not available during aw8          specified period of time (for example, 1 year).  D          "...unavailability or downtime of a channel begins when theC          first of 10 [or more] consecutive Severely Errored Seconds"F          (SESs) occurs, and ends when the first of 10 consecutive non-          SESs occurs."  F          The unavailable time is counted from the first SES in the 10-          SES sequence.  F          "The time for the end of unavailable time is counted from the<          first fault-free second in the [non-SES] sequence."A        o ES (errored second)-"An errored second is any one-seconde1          interval containing at least one error." F        o SES (severely errored second)-"...an SES is a second in which'          the BER is greater than 10-3."   I                                                  (continued on next page)     I                          VMScluster Systems That Span Multiple Sites 8-23_ _  r              H         Table 8-3 (Cont.) VMScluster DS3 and SONET OC3 Error Performance&                           Requirements  D                         Bellcore    Bellcore  VMScluster  VMSclusterK         Parameter       Requirement Goal      Requirement Goal[1]     Unitsn  G         SONET channel    None        105      None      Bellcore    MinyG         unavailability              @ 250               Goal        /yro*                                     miles,(                                     lin-)                                     early-'                                     de-i*                                     creas-'                                     ing )                                     to 21i)                                     @  50r)                                     milesb  I                                                  (continued on next page)_                                                    8         8-24 VMScluster Systems That Span Multiple Sites    i              H         Table 8-3 (Cont.) VMScluster DS3 and SONET OC3 Error PerformanceI                           Requirements___________________________________A                             C                         Bellcore    Bellcore  VMScluster VMSclusteraK         Parameter       Requirement Goal      Requirement Goal[1]     Units G         [1]Application requirements might need to be more rigorous thann:         those shown in the VMScluster Requirements column.         Table Keys  G        o Availability-The long-term fraction or percentage of time thatfE          a transmission channel performs as intended. Availability isaF          frequently expressed in terms of unavailability or down time.E        o BER (bit error ratio)-"The BER is the ratio of the number of1E          bits in error to the total number of bits transmitted duringtB          a measurement period, excluding all burst errored secondsB          (defined below) in the measurement period. During a burstH          errored second, neither the number of bit errors nor the number          of bits is counted."rB        o BES (burst errored second)-"A burst errored second is any8          errored second containing at least 100 errors."G        o Channel-The term for a link that is used in the Bellcore TSGR: >          Common Requirements document for a SONET or DS3 link.E        o Down time-The long-term average amount of time (for example,tG          minutes) that a transmission channel is not available during at8          specified period of time (for example, 1 year).  D          "...unavailability or downtime of a channel begins when theC          first of 10 [or more] consecutive Severely Errored SecondsqF          (SESs) occurs, and ends when the first of 10 consecutive non-          SESs occurs."  F          The unavailable time is counted from the first SES in the 10-          SES sequence.  F          "The time for the end of unavailable time is counted from the<          first fault-free second in the [non-SES] sequence."A        o ES (errored second)-"An errored second is any one-second 1          interval containing at least one error." F        o SES (severely errored second)-"...an SES is a second in which'          the BER is greater than 10-3."   I                                                  (continued on next page)     I                          VMScluster Systems That Span Multiple Sites 8-25i a  b              H         Table 8-3 (Cont.) VMScluster DS3 and SONET OC3 Error Performance&                           Requirements  eD                         Bellcore    Bellcore  VMScluster  VMSclusterK         Parameter       Requirement Goal      Requirement Goal[1]     Unitsd  J         Channel          None       None      None      1 to 2      EventsI         unavailable                                                 /year G         [1]Application requirements might need to be more rigorous than :         those shown in the VMScluster Requirements column.D         [4]The average number of channel down-time periods occurringH         during a year. This parameter is useful for specifying how often+         a channel might become unavailable.[         Table Keye  G        o Availability-The long-term fraction or percentage of time that E          a transmission channel performs as intended. Availability isbF          frequently expressed in terms of unavailability or down time.E        o BER (bit error ratio)-"The BER is the ratio of the number oftE          bits in error to the total number of bits transmitted during B          a measurement period, excluding all burst errored secondsB          (defined below) in the measurement period. During a burstH          errored second, neither the number of bit errors nor the number          of bits is counted." B        o BES (burst errored second)-"A burst errored second is any8          errored second containing at least 100 errors."G        o Channel-The term for a link that is used in the Bellcore TSGR:3>          Common Requirements document for a SONET or DS3 link.E        o Down time-The long-term average amount of time (for example, G          minutes) that a transmission channel is not available during at8          specified period of time (for example, 1 year).  D          "...unavailability or downtime of a channel begins when theC          first of 10 [or more] consecutive Severely Errored Seconds F          (SESs) occurs, and ends when the first of 10 consecutive non-          SESs occurs."  F          The unavailable time is counted from the first SES in the 10-          SES sequence.  F          "The time for the end of unavailable time is counted from the<          first fault-free second in the [non-SES] sequence."A        o ES (errored second)-"An errored second is any one-secondt1          interval containing at least one error."nF        o SES (severely errored second)-"...an SES is a second in which'          the BER is greater than 10-3."iI         _________________________________________________________________r  8         8-26 VMScluster Systems That Span Multiple Sites m  u              =         8.4 Managing VMScluster Systems Across Multiple Sitesi  E               In general, you manage a multiple-site VMScluster usingrF               the same tools and techniques that you would use for anyH               VMScluster interconnected by a LAN. The following sectionsE               describe additional considerations and recommend systemT.               management tools and techniques.  H               The following table lists system management considerations;               specific to multiple-site VMScluster systems:p                                                                      I                          VMScluster Systems That Span Multiple Sites 8-27  "  u            I               ___________________________________________________________cI               Problem____________________Possible_Solution_______________   A               Multiple-site              Assign votes so that oneTF               configurations present     preferred site has sufficientE               an increased probability   votes to maintain quorum andoE               of the following failure   to continue operation if thenC               modes:                     site-to-site communicationnC               o  VMScluster quorum loss  link fails or if the other(D                  resulting from site-    site is unavailable. Select?                  to-site communication   the site with the most E                  link failure            critical applications as theSC                                          primary site. Sites with a C               o  Site loss resulting     few noncritical systems ornC                  from power failure or   satellites probably should E                  other breakdown can     not have sufficient votes toe2                  affect all systems at   continue.                  that site  G               Users expect that the      Consider some of the following A               local resources will       options for setting user 6               either continue to be      expectations:C               available or will rapidly  o  Set management and usermB               become available after        expectations regardingA               such a failure. This          the likely effects offB               might not always be the       failures, and considerD               case.                         training remote users in  I                                             the procedures to be followed E                                             at a remote site when themG                                             system becomes unresponsive E                                             because of quorum loss or ;                                             other problems.b  G                                          o  Develop management policiesbC                                             and procedures for whatsA                                             actions will be takennB                                             to identify and handleF                                             these failure modes. TheseB                                             procedures may includeE                                             manually adjusting quorum H                                             to allow a site to continue.I               ___________________________________________________________.      8         8-28 VMScluster Systems That Span Multiple Sites    -                       8.4.1 Methods and Toolsl  E               You can use the following system management methods and.:               tools to manage both remote and local nodes:  E               o  There are two options for remote-site console accesseF                  when you use an intersite link through a DECserver in"                  reverse LAT mode.  G                  o  Use the following tools to connect remote consoles:n  +                     -  SET HOST/LAT command-  1                     -  POLYCENTER Console Manager   6                     -  VMScluster Console System (VCS)  E                     -  Business Recovery Server Operations ManagementC-                        Station (includes VCS)m  F                  o  Use a modem to dial up the remote system consoles.  H               o  An alternative to remote-site console access is to have/                  a system manager at each site.   H               o  To enable device and processor control commands to takeH                  effect across all nodes in a VMScluster system, use theI                  System Management utility (SYSMAN) that is supplied with .                  the OpenVMS operating system.           8.4.2 Shadowing Data  D               Volume Shadowing for OpenVMS allows you to shadow dataH               volumes across multiple sites. System disks can be membersG               of a volume shadowing or RAID set within a site; however,iI               use caution when configuring system disk shadow set members G               in multiple sites. This is because it may be necessary tovF               boot from a remote system disk shadow set member after aG               failure. If your system does not support FDDI booting, iti.               will not be possible to do this.  G               See the Software Product Descriptions (SPDs) for complete G               and up-to-date details about Volume Shadowing for OpenVMSn0               and StorageWorks RAID for OpenVMS.  I                          VMScluster Systems That Span Multiple Sites 8-29  a                 $         8.4.3 Monitoring Performance  I               Monitor performance for multiple-site VMScluster systems as                follows:  G               o  Monitor the virtual circuit (VC) packet-loss count andaF                  round-trip time values using the System Dump AnalyzerG                  (SDA). The procedures for doing this are documented in 0                  VMScluster Systems for OpenVMS.  E               o  Monitor the intersite link bit error ratio (BER) andrD                  packet loss using network management tools. You canB                  use tools such as POLYCENTER NetView or DECmcc toE                  access the GIGAswitch and WAN T3/SONET option card's-D                  management information and to set alarm thresholds.G                  See the GIGAswitch, WAN T3/SONET card, POLYCENTER, andn6                  DECmcc documentation, as appropriate.                                                        8         8-30 VMScluster Systems That Span Multiple Sites n  "                    I                                                                         A I         _________________________________________________________________   I                                               New OpenVMS System Messages     C               This release includes new or changed messages for thee+               following OpenVMS facilities:   9               o  ANALDISK, Analyze/Disk_Structure Utilityu  '               o  BACKUP, Backup Utilityo  #               o  DUMP, DUMP Command   (               o  IMGACT, Image Activator  "               o  LAT, LAT Facility  &               o  LIB, Library Facility  4               o  LICENSE, License Management Utility  /               o  LOADER, Executive Image Loaderi  )               o  MONITOR, Monitor Utility   %               o  MOUNT, Mount Utility   8               o  RMS, OpenVMS Record Management Services  (               o  SECSRV, Security Server  1               o  SET, SET Command and SET Utility   8               o  STACONFIG, Standalone Configure Process  3               o  SYSBOOT, System Bootstrap Facilityo  2               o  SYSMAN, System Management Utility  (               o  SYSTEM, System Services  G               This appendix alphabetically lists and describes messages C               that have been added or changed for this release. You C               can access online descriptions of these and all otheroF               OpenVMS system messages by using the online Help MessageE               utility. For information about the HELP/MESSAGE commandiI               and qualifiers, see DCL help (type HELP HELP/MESSAGE at thee  I                                           New OpenVMS System Messages A-1  c  n              H               DCL prompt) or refer to OpenVMS System Messages: Companion+               Guide for Help Message Users.n  4          ACA_ACTIVE,  SCSI ACA operations are active  -             Facility: SYSTEM, System Servicesr  F             Explanation: You attempted to execute a SCSI I/O operation@             while the SCSI device was busy performing a recovery             operation.  -             User Action: Retry the operation.   -          AECREATED,  created alias file entryt(             'dev:[directory]entry.ALIAS'  ,             Facility: BACKUP, Backup Utility  C             Explanation: The specified alias file entry was created .             during a backup restore operation.               User Action: None.  8          ALFNOMATCH,  no records matched search criteria  >             Facility: SMI, System Management Integrator/Server  H             Explanation: No records in the ALF database match the search$             criteria of the command.               User Action: None.  F          ALFWILCRDREQ,  more than one record might match - Wildcard or*             unit number of device required  7             Facility: SYSMAN, System Management Utilityn  D             Explanation: While removing records from SYSALF.DAT, theE             SYSMAN ALF component has encountered more than one record :             that matches the input from a terminal device.  B             User Action: Supply a wildcard or unit number with the             device input.   A          ALIASQUAL,  saveset was created /NOALIAS, restore /ALIAS %             qualifier will be ignoredr  ,             Facility: BACKUP, Backup Utility  B             Explanation: The backup restore operation could not beC             performed as specified because the save set was creatednD             ignoring alias entries. Therefore, there are no separateB             files in the save set to restore in place of the aliasB             directory entries. The restore operation was performed  '         A-2 New OpenVMS System Messages     l              E             by processing the alias file entries as directory entries 0             instead of as separate file entries.  H             User Action: Examine the save set used in the backup restoreD             operation to determine if it is the correct save set. IfG             not, restore the correct image and incremental save sets in F             the recommended order. If the save set is the correct one,-             no additional action is required.   F          ALLODIFF,  The ALLOCLASS parameter value for the processor onG             SCSI bus 'device-name', ID 'slot-number', is different from %             the value on this system. F             This condition creates multiple names for the same device,.             which can lead to data corruption.  =             Facility: STACONFIG, Standalone Configure Process   F             Explanation: The value of the SYSGEN disk allocation classF             parameter differs between the local node and the specified             remote node.  H             User Action: Set the ALLOCLASS parameter to the same nonzero              value on both nodes.  @          ALLOZERO,  This system and/or the processor on SCSI busH             'device-name', ID 'slot-number', has a zero ALLOCLASS value.F             This condition creates multiple names for the same device,.             which can lead to data corruption.  =             Facility: STACONFIG, Standalone Configure Process   H             Explanation: The local node, remote node, or both nodes haveC             the SYSGEN disk allocation class parameter set to zero.h  H             User Action: Set the ALLOCLASS parameter to the same nonzero              value on both nodes.  4          ARESTERR,  error restoring alias file entry)             'dev:[directory]entry.alias', C             the primary file entry was 'dev:[prim_dir]primary.file't  ,             Facility: BACKUP, Backup Utility  H             Explanation: An error occurred when the Backup utility triedH             to restore an alias file entry. The alias file entry was notE             restored. Note that in most cases the alias file entry is *             eliminated from the directory.  E             User Action: Examine the primary file, the directory, andtC             the alias entry directory to determine the cause of thenH             error. Then, based on the data in this error message and any  I                                           New OpenVMS System Messages A-3e                   F             secondary error status, correct the problem and create theB             alias file entry using the DCL command SET FILE/ENTER.  F             As a general practice, Digital recommends that you executeH             the DCL command ANALYZE/DISK after Backup restore operationsC             of all save sets have been completed and any subsequent D             error corrections have been made, for example, using SET              FILE/ENTER commands.  G          ASSIGNFAILED,  security server failed to assign a channel to a)              client reply mailbox  -             Facility: SECSRV, Security Server   B             Explanation: The security server's call to the $ASSIGNH             system service failed to assign a channel to the requestor's             mailbox.  5             User Action: Contact your system manager.O  G          AUDITFAILED,  security server failed to audit an event because #             of the following error:M  -             Facility: SECSRV, Security Serveru  G             Explanation: The security server could not perform an audit F             because of the error reported in the accompanying message.  G             User Action: Take action based on the accompanying message.i  B          BAD_DIREFBLK,  EFBLK indicates zero length directory file  >             Facility: ANALDISK, Analyze/Disk_Structure Utility  F             Explanation: The Analyze/Disk_Structure utility detected a*             directory file of zero length.  G             User Action: Do a SET FILE/NODIRECTORY on the bad directory H             file; then delete the directory file. Last, run ANALYZE/DISKG             /REPAIR to rename all the files from the bad directory into (             the SYSLOST.DIR;1 directory.  I          BAD_GSD,  an inconsistency was detected while traversing the GSTo  4             Facility: LOADER, Executive Image Loader  A             Explanation: An executive image was loaded containinguC             a global symbol that is not vectored through either ther;             SYS$BASE_IMAGE or the SYS$PUBLIC_VECTORS image.r  E             User Action: Use either /NOSYSSHR or /NOSYSLIB to correct H             the link procedure to exclude any shareable image other than1             SYS$BASE_IMAGE or SYS$PUBLIC_VECTORS.   '         A-4 New OpenVMS System Messagess e  n              E          BAD_NAMEORDER,  filename ordering incorrect in VBN 'virtual-              block-number'-"             of directory 'file-id'1             Filenames are 'file-id' and 'file-id'e  >             Facility: ANALDISK, Analyze/Disk_Structure Utility  H             Explanation: The Analyze/Disk_Structure utility detected two5             files that are out of alphabetical order.u  H             User Action: Do a SET FILE/NODIRECTORY on the directory fileE             in which the files are located; then delete the directoryaG             file. Last, run ANALYZE/DISK/REPAIR to rename all the filescD             from the bad directory into the SYSLOST.DIR;1 directory.  D          BAD_VERSORDER,  version ordering incorrect in VBN 'virtual-             block-number'""             of directory 'file-id'!             Filename is 'file-id'e?             Versions are ' version-number' and 'version-number'E  >             Facility: ANALDISK, Analyze/Disk_Structure Utility  H             Explanation: The Analyze/Disk_Structure utility detected two?             versions of a file that are out of numerical order.u  H             User Action: Do a SET FILE/NODIRECTORY on the directory fileE             in which the files are located; then delete the directorysG             file. Last, run ANALYZE/DISK/REPAIR to rename all the filesaD             from the bad directory into the SYSLOST.DIR;1 directory.  >          BADIMGOFF,  image offset not within any image section  4             Facility: LOADER, Executive Image Loader  F             Explanation: During an image load request, a relocation orH             fixup operation was attempted on an image offset that has no/             resultant address within the image.   D             User Action: Disable executive slicing by specifying theH             LDR$V_NO_SLICE option or by using the LOAD_SYS_IMAGES systemE             parameter. Correct the bad references in the source code._      I                                           New OpenVMS System Messages A-5     A              ?          BADINITD_MFD,  Root directory 000000.DIR;1 file headertA             incorrectly initialised, RVN 'relative-volume-number'   >             Facility: ANALDISK, Analyze/Disk_Structure Utility  D             Explanation: The Analyze/Disk_Structure utility detectedC             an incorrectly initialized master file directory (MFD),n             000000.DIR;1.   F             User Action: None, if you specified the /REPAIR qualifier.@             If you omitted /REPAIR, reenter the command with the             qualifier.  C          BADJOBTYPE,  an invalid job type was used to audit a login &             failure or breakin attempt  -             Facility: SECSRV, Security Serverr  B             Explanation: A request to audit a login failure in theD             security server failed because the type of job specified&             in the request is invalid.  E             User Action: Specify the job type correctly and retry the 2             call to the intrusion system services.  A          BADLOCALUSERLEN,  local user name length is out of rangei  -             Facility: SECSRV, Security Server   D             Explanation: The proxy record you want to add contains a-             local user name that is too long.t  C             User Action: Specify a user name that is valid for your D             environment. The proxy services accept 32 characters but-             currently OpenVMS allows only 12.   A          BADNODENAMELEN,  remote node name length is out of range   -             Facility: SECSRV, Security Serverl  D             Explanation: The proxy record you want to add contains a.             remote node name that is too long.  E             User Action: Specify a remote node name that is valid for F             your environment. The proxy services allow 1024 characters2             but currently OpenVMS allows only 256.  '         A-6 New OpenVMS System Messagesb                   7          BADREFCNT,  faulty reference count maintenance   4             Facility: LOADER, Executive Image Loader  E             Explanation: A call was made to the SYS$REMOVE_REF system H             service and the outstanding reference count for the image is             negative.   D             User Action: Check all references to the routines in theE             executive image to ensure that each SYS$MAKE_REF has only *             one associated SYS$REMOVE_REF.  @          BADREMUSERLEN,  remote user name length is out of range  -             Facility: SECSRV, Security ServerS  D             Explanation: The proxy record you want to add contains a.             remote user name that is too long.  B             User Action: Specify a remote user name of 32 or fewer             characters.   <          BADSECSYS,  failed to create or access SECURITY.SYS  *             Facility: MOUNT, Mount Utility  C             Explanation: The Mount utility was unable to create and H             write the SECURITY.SYS file on a volume that was initializedG             prior to OpenVMS Version 6.0, usually because the device isC             full.e  :             User Action: Try any of the following actions:  =             o  Mount the device using the /NOWRITE qualifier.g  G             o  Mount the device with /OVERRIDE=SECURITY if the securityo?                policy of the system permits this. Once the disk A                is mounted, free up approximately 10 blocks on the @                disk, and then remount the disk without using the,                /OVERRIDE=SECURITY qualifier.  H             o  Mount the device on a version of OpenVMS prior to VersionH                6.0 and free up about 10 blocks on the disk. Then remount;                the disk on the later version of the system.   +          BADWIDTH,  illegal width value 'n'u  (             Facility: DUMP, DUMP Command  >             Explanation: The specified width value is illegal.  H             User Action: Specify a legal width value of either 80 or 132!             to format the output.t  I                                           New OpenVMS System Messages A-7l i  .              A          CANTASSIGN,  Error assigning a channel to the PK device.   =             Facility: STACONFIG, Standalone Configure Processs  D             Explanation: The $ASSIGN system service did not complete             successfully.   B             User Action: Contact a Digital support representative.  7          CANTRUNACP,  attempt to run LATACP incorrectlyp  '             Facility: LAT, LAT Facility   F             Explanation: An attempt was made to run the LATACP processC             interactively. This action is prohibited because it cano-             cause LATACP to start improperly.   A             User Action: Use the LAT$STARTUP command procedure to 4             automatically start both LAT and LATACP.  >          CIADBEMPTY,  no intruders or suspects currently exist  -             Facility: SECSRV, Security Serverr  G             Explanation: A request was made to show the contents of thet:             intrusion database, and the database is empty.               User Action: None.  B          CIASHUTDOWN,  breakin detection and evasion processing is             shutting downc  -             Facility: SECSRV, Security Server   F             Explanation: The break-in detection and evasion processingB             component of the security server is shutting down upon             request.  >             User Action: None required. If you wish to restartA             the security server, issue the DCL command SET SERVER              SECURITY/START.0  E          CIASTARTINGUP,  breakin detection and evasion processing now              starting up   -             Facility: SECSRV, Security Server   F             Explanation: The break-in detection and evasion processing?             component of the security server is starting up, ast             requested.               User Action: None.  '         A-8 New OpenVMS System Messages  l  n              F          CIATERMINATED,  an error caused breakin detection and evasion#             processing to terminatel  -             Facility: SECSRV, Security Server   H             Explanation: An error occurred in the break-in detection and@             evasion processing component of the security server.  B             User Action: Contact a Digital support representative.  8          CONNDELETEONLY,  connection can only be deleted  '             Facility: LAT, LAT Facility   >             Explanation: You tried to change a virtual circuit?             characteristic. This information cannot be changed.   A             User Action: Do not attempt to change virtual circuitn             characteristics.  >          CONNECTQUEUED,  queued at service position 'position'  '             Facility: LAT, LAT Facility   E             Explanation: A LAT connection request issued to a serviceyE             with no available resources has been placed in the remotehB             node's service connection queue. When resources become@             available, the connection request will be completed.  G             User Action: Wait until the connection request is serviced.n9             To abort the queued connection, press Ctrl/Y.e  D          CONSTERROR,  security server experienced a CONSTRAINT_ERROR             exceptione  -             Facility: SECSRV, Security Server   B             Explanation: An error occurred in the security server.  B             User Action: Contact a Digital support representative.  :          CONVERT,  converting proxy database to new format  -             Facility: SECSRV, Security Servert  H             Explanation: The NETPROXY.DAT file is being converted to the;             new format; the new file name is NET$PROXY.DAT.o               User Action: None.  I                                           New OpenVMS System Messages A-9     v              I          CONVERT_SUCCESS,  conversion of proxy database to new format wasx             successful  -             Facility: SECSRV, Security Serverg  B             Explanation: The old proxy database, NETPROXY.DAT, wasC             successfully converted to the new format database nameda             NET$PROXY.DAT.               User Action: None.  G          COULDNTRESTART,  security server cannot restart because of the              following error:  -             Facility: SECSRV, Security ServerD  D             Explanation: The security server was directed to restartE             itself but the error reported in the accompanying messagem"             prevented this action.  G             User Action: Take action based on the accompanying message.m  I          COULDNTSTART,  security server cannot start functioning properlyp  -             Facility: SECSRV, Security Servert  D             Explanation: The security server failed to start for the8             reason described in an accompanying message.  G             User Action: Take action based on the accompanying message.i  E          CPUNOTSUPP,  The processor device on SCSI bus 'device-name', B             ID 'slot-number', is not supported in a multihost SCSI#             VMScluster environment. H             The processor vendor ID is 'vendor-id' and the product ID is             'product-id'.e  =             Facility: STACONFIG, Standalone Configure Processe  G             Explanation: An unsupported processor device was discoveredl             on the bus.   A             User Action: If you are operating in a multihost SCSI D             VMScluster environment, remove the specified unsupported             device.s  C             If you are not operating in a multihost SCSI VMSclusterhF             environment, specify the processor device using the SYSGEN1             parameter SCSICLUSTER_Pn=abcd, where:e  !                 n = 1, 2, 3, or 4cF                ab = The first two letters of the processor's vendor IDG                cd = The first two letters of the processor's product IDI  (         A-10 New OpenVMS System Messages e        <          CREATEPROXYDB,  attempting to create proxy database  -             Facility: SECSRV, Security Server,  H             Explanation: As requested, the security server is attempting+             to create a new proxy database.                User Action: None.  F          CRELNM_FAILED,  failed to create logical name 'name' in table             'table-name'  *             Facility: MOUNT, Mount Utility  D             Explanation: The mount operation completed successfully,H             but the Mount utility could not create the requested logicalE             name. An accompanying message explains the reason for ther             failure.  E             User Action: None required. If you wish, you can manually H             assign the logical name after the reason for the failure has             been resolved.  F          CREMBXFAILED,  security server failed to create input mailbox  -             Facility: SECSRV, Security Serverc  H             Explanation: The security server could not create a mailbox.  B             User Action: Contact a Digital support representative.  I          DASSGNFAILED,  security server could not deassign a channel to a]              client reply mailbox  -             Facility: SECSRV, Security Servert  C             Explanation: The security server could not deassign thet2             channel assigned to the reply mailbox.  B             User Action: Contact a Digital support representative.  8          DBALREADYEXISTS,  proxy database already exists  -             Facility: SECSRV, Security Server   F             Explanation: The security server cannot create a new proxy=             database because a proxy database already exists.t  D             User Action: Delete or rename the current proxy database2             before attempting to create a new one.  ,          DELENTRY,  deleted queue entry 'id'  '             Facility: LAT, LAT Facilityr  B             Explanation: The specified queue entry ID was deleted.               User Action: None.  I                                          New OpenVMS System Messages A-11e u                 6          DELETEDCONN,  deleted connection 'connect-id'  '             Facility: LAT, LAT Facilityc  =             Explanation: A delete circuit operation completedb             successfully.g               User Action: None.  H          DENIGNORED,  /DENSITY qualifier not appropriate to this device;             ignorede  *             Facility: MOUNT, Mount Utility  C             Explanation: The /DENSITY qualifier was supplied on thecC             command line for a device that does not support variousn0             densities. The qualifier is ignored.  E             User Action: Omit the /DENSITY qualifier to avoid gettingLE             this system message. Use the /MEDIA_FORMAT=[NO]COMPACTIONt8             qualifier if the device supports compaction.  G          DEVNAMLNG,  device or port or node::username length restrictedo             to 63 characters  7             Facility: SYSMAN, System Management Utility   ?             Explanation: The device name parameter specified ineA             the SYSMAN ALF ADD command exceeds 63 characters. The D             63-character restriction is determined by the field size             in SYSALF.DAT.  F             User Action: Specify a device name that is no more than 63             characters.   #          DRVERR,  fatal drive errorC  *             Facility: MOUNT, Mount Utility  D             Explanation: In a SCSI VMScluster environment, a requestH             has been made to mount a device on a shared SCSI bus and theH             device does not support SCSI-2 tagged command queuing (TCQ).  G             User Action: If you want to mount a device on a shared SCSIg-             bus, the device must support TCQ.v  (         A-12 New OpenVMS System Messages l  l              D          DUPLICATEUSER,  username already exists in the proxy record  -             Facility: SECSRV, Security Servert  G             Explanation: A request was made to add a local user name tooF             a proxy record that already contains that local user name.  D             User Action: Use the SHOW/PROXY command in the AuthorizeB             utility to see what proxy records exist for a specific:             combination of remote node name and user name.  7          DZRO_ISD,  image contains demand zero sectionsf  4             Facility: LOADER, Executive Image Loader  G             Explanation: A load request was made for an executive images9             that illegally contains demand zero sections.e  E             User Action: Correct the link procedure used to build theDC             executive image; specify the appropriate PSECT_ATTR andcE             COLLECT statements to eliminate the demand zero sections.I  7          ENTRYDELONLY,  queue entry can only be deletedd  '             Facility: LAT, LAT Facility.  B             Explanation: An attempt was made to use a SETMODE $QIOA             operation on a queue entry. You can only delete queue D             entries from the system or use SENSEMODE $QIO operations             on them.  D             User Action: Do not use SETMODE $QIO operations on queue             entries.  )          EXDEPTH,  exceeded allowed depthe  -             Facility: SYSTEM, System Servicesr  G             Explanation: Either a programming error has occurred or theCE             resource name tree does not have enough depth. This error =             can be caused by any of the following conditions:/  E             o  The operation has exceeded the maximum number (64K) ofiG                child locks that can be associated with one parent lock.   E             o  The operation has exceeded the maximum number of locks 7                you can have on one resource name (64K).e  F             o  The operation has exceeded the maximum number of parentF                generations for a lock. The maximum is fixed at 127 forE                Alpha systems. The maximum for VAX systems is computedeD                using the values for the INTSTKPAGES and DLCKEXTRASTK8                system generation parameters, as follows:  I                                          New OpenVMS System Messages A-13M y  m              >                (INTSTKPAGES*512 - DLCKEXTRASTK) / 32 = maximum  =                The maximum VAX value can range from 4 to 255.N  D             User Action: Reprogram the operation so that it does notC             exceed the maximums. If you need to increase the numberuF             of parent generations on VAX systems, you can increase the/             value of the INTSTKPAGES parameter.   <          FILFAIMAT,  file failed to match selection criteria  +             Facility: LIB, Library Facilitye  F             Explanation: No files meet the search criteria for a PRINT             or SUBMIT command.               User Action: None.  G          FREESPADRIFT,  free block count of 'n' is incorrect (RVN 'n'); $             the correct value is 'n'  >             Facility: ANALDISK, Analyze/Disk_Structure Utility  >             Explanation: The free block count for this disk is             incorrect.  A             User Action: None. The Analyze/Disk_Structure utility E             automatically corrects this error if you used the /REPAIRc8             qualifier and you have the CMKRNL privilege.  A          INCOMPDRVACP,  incompatible LATACP and LTDRIVER - LATACPc             terminatingi  '             Facility: LAT, LAT Facilityo  D             Explanation: An attempt to start LAT failed because of a7             mismatch between the LAT driver and LATACP.e  G             User Action: Locate the mismatched image and remove it from              the system.o  I          INCONOWNER,  inconsistent /OWNER_UIC option. Verify volume ownery  *             Facility: MOUNT, Mount Utility  F             Explanation: The UIC specified in the /OWNER_UIC qualifierF             is not consistent with the protection that this device has<             been mounted with on other nodes in the cluster.  G             User Action: Verify that the /OWNER_UIC option is specified &             consistently on all nodes.  (         A-14 New OpenVMS System Messages u                 C          INCONPROT,  inconsistent /PROTECTION option. Verify volumer             protection  *             Facility: MOUNT, Mount Utility  D             Explanation: The protection specified in the /PROTECTIOND             qualifier is not consistent with the protection that theG             device has been mounted with on other nodes in the cluster.h  H             User Action: Verify that the /PROTECTION option is specified&             consistently on all nodes.  G          INSUFINFO,  not enough information to produce a breakin recordS  -             Facility: SECSRV, Security Server   G             Explanation: A request to produce a break-in record did not -             contain the required information.m  H             User Action: Include at least one of the following in a callG             to request a break-in record: source terminal, source user,iF             failed user, failed password, parent user, or source node.  +          INTRUDER,  matching intruder founda  -             Facility: SECSRV, Security Servero  G             Explanation: A record matching the request was found in the              intrusion database.o  9             User Action: None. The search was successful.s  I          INVALIDDELETE,  you cannot delete the only user in a record; youE)             must delete the entire recordp  -             Facility: SECSRV, Security Server   G             Explanation: A request was made to delete an explicit local E             user from a proxy record; however, that is the only local              user in the record.   D             User Action: Remove the explicitly named local user fromC             your request to delete the entire record or add anothermB             local user to this proxy record and perform the delete             request again.  I                                          New OpenVMS System Messages A-15  l  t              F          INVALIDTERMNAME,  received invalid terminal name for intruder             /suspect  -             Facility: SECSRV, Security Server   D             Explanation: An invalid terminal name was specified in a2             request to generate a break-in record.  D             User Action: Specify a valid terminal name and retry the             request.  =          LOGRDERR,  error reading LBN 'n' to LBN 'n', RVN 'n'c  >             Facility: ANALDISK, Analyze/Disk_Structure Utility  G             Explanation: The Analyze/Disk_Structure utility detected an 1             error while trying to read from disk.a  G             User Action: Take action based on the accompanying message.t  6          LOGWRTERR,  error writing to LBN 'n', RVN 'n'  >             Facility: ANALDISK, Analyze/Disk_Structure Utility  G             Explanation: The Analyze/Disk_Structure utility detected anp4             error while trying to write to the disk.  G             User Action: Take action based on the accompanying message.i  A          LRJINCOMPVER,  incompatible LAT version with remote nodex  '             Facility: LAT, LAT Facilityo  B             Explanation: An attempt was made to run LATACP with an"             incompatible LTDRIVER.  E             User Action: Check whether an incorrect LATACP was placed @             in SYS$SYSTEM or an incorrect LTDRIVER was placed inC             SYS$LOADABLE_IMAGES. Remove the incorrect file from thes             system.   4          LRJIVMSG,  invalid message or slot received  '             Facility: LAT, LAT Facilitys  H             Explanation: An invalid LAT slot or LAT message was receivedH             from the remote node. This message indicates that a protocol7             violation occurred during a LAT connection.o  A             User Action: File a problem report against the remoteVD             LAT implementation that sent the invalid LAT slot or LAT             message.  (         A-16 New OpenVMS System Messages i  t              1          LRJREMDISABLED,  remote node is disabled:  '             Facility: LAT, LAT Facilitys  E             Explanation: A LAT $QIO connection request failed becausee9             the target node has disabled LAT connections.n  H             User Action: Enable connections on the remote node and retry             the connection.h  2          MARKUNL,  exec image is marked for unload  4             Facility: LOADER, Executive Image Loader  H             Explanation: A call was made to the LDR$UNLOAD_IMAGE routineE             to unload a removable executive image that already has anc2             outstanding unload request against it.               User Action: None.  D          MULTIPLE_ISDS,  more than one image section of a given type  4             Facility: LOADER, Executive Image Loader  F             Explanation: A load request was made for an image that wasG             not linked correctly because it contains more than one each /             of the following types of sections:                   fixup                initialization                 nonpaged code                nonpaged data                paged code                 paged datal  E             User Action: Correct the link procedure used to build theWC             executive image; specify the appropriate PSECT_ATTR andtB             COLLECT statements to ensure that each executive imageE             contains only one each of the types of information listed              above.  :          NO_PAGED_ISDS,  cannot load paged ISDs in SYSBOOT  4             Facility: LOADER, Executive Image Loader  C             Explanation: SYSBOOT failed to load the executive imagee?             because it contains either paged code or paged dataV             sections.   E             User Action: Correct the link procedure used to build the C             executive image; specify the appropriate PSECT_ATTR and E             COLLECT statements to eliminate the paged image sections.   I                                          New OpenVMS System Messages A-17  n  s              >          NO_SUCH_IMAGE,  the requested image cannot be located  4             Facility: LOADER, Executive Image Loader  A             Explanation: A load request was made for an executivesG             image that was linked against a shareable image that is not.F             loaded. The only legal shareable images for executives are2             SYS$BASE_IMAGE and SYS$PUBLIC_VECTORS.  B             User Action: Use /NOSYSSHR or /NOSYSLIB to correct theE             link procedure to exclude any shareable images other thant1             SYS$BASE_IMAGE or SYS$PUBLIC_VECTORS.a  <          NOACTLINKS,  no active LAT links to service request  '             Facility: LAT, LAT Facilityh  ?             Explanation: A LAT connection to the local node was G             attempted from the local node. The operation failed becausei;             LAT cannot communicate with the datalink layer.i  C             User Action: Ask your system manager to properly createe+             LAT$LINK and make it available.n  I          NOCMKRNL,  correcting free block count requires CMKRNL privilegee  >             Facility: ANALDISK, Analyze/Disk_Structure Utility  G             Explanation: To correct the free block count, you must have !             the CMKRNL privilege.s  D             User Action: Enable the CMKRNL privilege, then enter the8             ANALYZE/DISK_STRUCTURE/REPAIR command again.  1          NODISCON,  disconnect character disablede  '             Facility: LAT, LAT Facilitys  A             Explanation: Use of the disconnect character has beenSH             disabled in response to a SET HOST/LAT/NODISCONNECT command.  9             User Action: None. This is a Success message.i  C          NOLOGIO,  erasing old home block requires LOG_IO privilegeo  >             Facility: ANALDISK, Analyze/Disk_Structure Utility  F             Explanation: To erase an old home block, you must have the             LOG_IO privilege.p  D             User Action: Enable the LOG_IO privilege, then enter the8             ANALYZE/DISK_STRUCTURE/REPAIR command again.  (         A-18 New OpenVMS System Messages a  m              E          NOMATCH,  The processor on SCSI bus 'device-name', ID 'slot-              number',7             is attached using controller 'device-name'. F             This condition creates multiple names for the same device,.             which can lead to data corruption.  =             Facility: STACONFIG, Standalone Configure Process   G             Explanation: The local and remote nodes are attached to thei-             SCSI bus through unmatched ports.   B             User Action: Connect the nodes to the SCSI bus through*             matching ports on each system.  1          NOMOREENTRIES,  no more entries in queueA  '             Facility: LAT, LAT Facilitym  H             Explanation: There are no more entries in the LAT connection             queue.               User Action: None.  B          NOPROXYDB,  cannot find proxy database file NET$PROXY.DAT  -             Facility: SECSRV, Security Server   B             Explanation: The security server cannot find the proxy(             database file NET$PROXY.DAT.  F             User Action: If a proxy database exists, make sure that itF             is in SYS$SYSTEM or that the logical name NET$PROXY points             to it.  G             If a proxy database does not exist, create one by using theaG             DCL command RUN SYS$SYSTEM:CONVERT_PROXY to convert the old G             NETPROXY.DAT file or by issuing the CREATE/PROXY command inAE             the Authorize utility to create a new NET$PROXY.DAT file.E  G          NORDPROXYREC,  proxy record is internally inconsistent; cannoto             read it   -             Facility: SECSRV, Security Servere  ?             Explanation: A proxy record was read from the proxynB             database, but the record is not internally consistent.  E             User Action: Examine the NETPROXY.DAT database from which D             the new format NET$PROXY.DAT proxy database was created.E             Delete erroneous records and reconvert the proxy database F             using the DCL command RUN SYS$SYSTEM:CONVERT_PROXY. If theD             conversion process does not create a NET$PROXY.DAT file,5             contact a Digital support representative.x  I                                          New OpenVMS System Messages A-19                    B          NOSCANNEDINTRUDER,  no matching intruder or suspect found  -             Facility: SECSRV, Security Server   H             Explanation: No record in the intrusion database matches theH             $SCAN_INTRUSION request; the specified user is not a suspect             or intruder.               User Action: None.  D          NOSHARE,  NO_SHARE option may not be removed from 'product'  9             Facility: LICENSE, License Management Utilitye  E             Explanation: The NO_SHARE option cannot be removed from arH             PAK that was originally issued with the NO_SHARE option. TheF             NO_SHARE option can be removed with a LICENSE MODIFY/NONO_F             SHARE command only if the NO_SHARE option was added with a,             LICENSE MODIFY/NO_SHARE command.  B             User Action: If you require a PAK without the NO_SHAREH             option for a particular product, contact the software vendor.             to see if such a PAK is available.  =          NOSUCHINTRUDER,  no intruder or suspect matches your              specificationr  -             Facility: SECSRV, Security Servery  G             Explanation: The specified intruder or suspect has no entry &             in the intrusion database.               User Action: None.  0          NOSUCHNODE,  node 'node-name' not known  '             Facility: LAT, LAT Facilityo  E             Explanation: A LAT connection was attempted to an unknownd             target node.  F             User Action: Retry the connection until the specified nodeE             is known or check whether some condition on the specified F             node prohibits its network visibility. Possibly, the localF             node's service group codes do not intersect with the group/             codes of the specified remote node.   A          NOSUCHPROXY,  no proxy record matches your specification   -             Facility: SECSRV, Security Servero  C             Explanation: The requested proxy record does not exist..  F             User Action: Specify an existing proxy record or add a new             proxy record.v  (         A-20 New OpenVMS System Messages a  e              8          NOSUCHUSER,  no user matches your specification  -             Facility: SECSRV, Security Servert  F             Explanation: The user name you specified does not exist in'             the specified proxy record.   E             User Action: Specify a user name that exists in the proxys?             record or add a new user name for the proxy record.   8          NOT_UNL,  image is not unloadable or not loaded  4             Facility: LOADER, Executive Image Loader  F             Explanation: A call was made to LDR$UNLOAD_IMAGE to unloadH             an executive image that is not loaded or that was not loaded,             with the LDR$V_UNL flag bit set.  F             User Action: If you want to be able to unload an executiveG             image, be sure to set the LDR$V_UNL bit in the flags passedeC             to the LDR$LOAD_IMAGE routine when the image is loaded.dF             The LDR$V_UNL bit cannot be specified for OpenVMS-suppliedC             executive images or for images loaded using VMS$SYSTEM_s             IMAGES.DATA.  C          NOTALLSET,  authorization file NOT modified on some or alld7             members; check before rebooting any member.   7             Facility: SYSMAN, System Management Utilityo  E             Explanation: A CONFIGURATION SET CLUSTER operation to set C             either the cluster group number or the cluster password D             failed on one or more nodes of the cluster. This messageG             appears only when the environment is set to CLUSTER and not (             all the members are updated.  C             User Action: Ensure that all members of the cluster area@             updated with the new password or group number before"             rebooting any members.  *          NOTIMEOUT,  no timeout period set  7             Facility: SYSMAN, System Management UtilityX  B             Explanation: Either SYSMAN received a timeout value ofF             0-00:00:00.00 for the SET TIMEOUT command (meaning that noG             timeout value is set for cluster communication) or a SYSMANXG             SHOW TIMEOUT command was issued when there is no timeout inm             effect.L               User Action: None.  I                                          New OpenVMS System Messages A-21  l  t              6          NOTNATIVE,  image is not an OpenVMS AXP image  -             Facility: IMGACT, Image Activator   D             Explanation: The image is not an OpenVMS Alpha image. It*             might be an OpenVMS VAX image.  F             User Action: Use the DCL command ANALYZE/IMAGE to get more(             information about the image.  6          NOTVAXIMG,  image is not an OpenVMS VAX image  -             Facility: IMGACT, Image Activator   H             Explanation: The image is not an OpenVMS VAX image. It might&             be an OpenVMS Alpha image.  F             User Action: Use the DCL command ANALYZE/IMAGE to get more(             information about the image.  !          NXR,  nonexistent record   =             Facility: RMS, OpenVMS Record Management Servicesf  G             Explanation: A secondary index data record (SIDR) points to G             a nonexistent primary data record. This condition (commonly B             referred to as a dangling SIDR) can occur when a powerH             failure, system crash, or STOP/ID occurs while a process hasG             modified buckets whose write-back to disk has been deferred )             by the deferred-write option.o  ?             This condition can be detected when a $GET or $FINDsB             operation performs an exact-match keyed search using aD             secondary key. An RNF is reported in the status (STS) ofF             the RAB and NXR is returned in the associated status value             (STV) of the RAB.T  E             User Action: None. If the associated file was opened withyF             write access, RMS transparently cleans up the SIDR element2             before returning the NXR status value.  G          OBSPASSALL,  terminal set to PASSALL mode even though /PASSALLe!             qualifier is obsoleter  6             Facility: SET, SET Command and SET Utility  F             Explanation: You specified the obsolete /PASSALL qualifier*             with the SET TERMINAL command.  D             User Action: Use the /PASSTHRU qualifier to perform this             function.:  (         A-22 New OpenVMS System Messages                   9          OLDHM,  old home block found at LBN 'n', RVN 'n'I  >             Facility: ANALDISK, Analyze/Disk_Structure Utility  H             Explanation: The Analyze/Disk_Structure utility found a homeF             block that was created by a previous initialize operation.  A             User Action: None. The Analyze/Disk_Structure utilitySC             automatically erases the old home block if you used thef@             /REPAIR qualifier and you have the LOG_IO privilege.  H          OUTCOMTERMINATED,  security server's outgoing message mechanism!             failed and is exitingo  -             Facility: SECSRV, Security Serverr  C             Explanation: An error occurred in the security server'slA             communication system and the server is shutting down.   H             User Action: Issue the DCL command SET SERVER SECURITY/STARTG             to restart the security server. If this condition persists,d5             contact a Digital support representative.e  G          PAGED_GST_TOBIG,  paged global symbol fixup data exceeds table              size  4             Facility: LOADER, Executive Image Loader  F             Explanation: An executive image has more global symbols inH             the fixup data than can fit in the loader's internal tables.  B             User Action: Contact a Digital support representative.  E          PROXYACTIVE,  proxy processing is active; you must shut downa3             proxy processing to perform this action   -             Facility: SECSRV, Security Servera  H             Explanation: A request was made to start proxy processing orF             to create a proxy database but proxy processing is already             active.i  C             User Action: You must shut down proxy processing beforee/             performing either of these actions.f  6          PROXYMODIFIED,  existing proxy entry modified  -             Facility: SECSRV, Security ServerR  >             Explanation: The request to modify the proxy entry             succeeded.               User Action: None.  I                                          New OpenVMS System Messages A-23l r  g              C          PROXYNOTACTIVE,  proxy processing is not currently active;n)             please try your request latern  -             Facility: SECSRV, Security Server   F             Explanation: Proxy processing is not active because eitherC             the security server was not started or proxy processing #             halted for some reason.r  A             User Action: Check whether a new format NET$PROXY.DAToD             proxy database exists and use the DCL command SET SERVERE             SECURITY/START to start the security server if it has not,             been started.e  G             If a proxy database does not exist, create one by using theoG             DCL command RUN SYS$SYSTEM:CONVERT_PROXY to convert the oldrG             NETPROXY.DAT file or by issuing the CREATE/PROXY command in E             the Authorize utility to create a new NET$PROXY.DAT file.r  2          PROXYNOTOPEN,  cannot open proxy database  -             Facility: SECSRV, Security Server   E             Explanation: The proxy database NET$PROXY.DAT exists, but H             it cannot be opened for the reason stated in an accompanying             message.  G             User Action: Take action based on the accompanying message.e  :          PROXYSHUTDOWN,  proxy processing is shutting down  -             Facility: SECSRV, Security Serverc  C             Explanation: As requested, proxy processing is shutting              down.                User Action: None.  ;          PROXYSTARTINGUP,  proxy processing now starting up   -             Facility: SECSRV, Security ServerA  G             Explanation: As requested, proxy processing is starting up.h               User Action: None.  H          PROXYTERMINATED,  an error caused proxy processing to terminate  -             Facility: SECSRV, Security Server   B             Explanation: An error occurred in the proxy processing-             component of the security server.a  B             User Action: Contact a Digital support representative.  (         A-24 New OpenVMS System Messages i  t              C          PSB_FIXUPS,  image contains LPPSB fixups, link NATIVE_ONLY   4             Facility: LOADER, Executive Image Loader  G             Explanation: A load request was made for an executive imageo@             that contains LPPSB fixup data because it was linkedD             /NONATIVE_ONLY. Executive images must be linked /NATIVE_             ONLY.n  =             User Action: Relink the image using /NATIVE_ONLY.h  0          QIOCALLFAIL,  QIO service call failure.?             Unable to obtain inquiry data from one or more SCSIT             initiators.   =             Facility: STACONFIG, Standalone Configure ProcessT  B             Explanation: The $QIOW system service did not complete             successfully.d  B             User Action: Contact a Digital support representative.  A          QIOFAILED,  security server QIO on client mailbox failedy  -             Facility: SECSRV, Security ServerL  F             Explanation: An error has occurred in the security server.  B             User Action: Contact a Digital support representative.  3          QIOOPFAIL,  QIO service operation failure.e?             Unable to obtain inquiry data from one or more SCSIg             initiators.x  =             Facility: STACONFIG, Standalone Configure Process   D             Explanation: The operation requested by the $QIOW system2             service did not complete successfully.  B             User Action: Contact a Digital support representative.  *          RIGHTSLIM,  Rights limit exceeded  >             Facility: SMI, System Management Integrator/Server  @             Explanation: A SYSMAN user with more than 125 rights@             identifiers attempted to issue a SYSMAN command to aB             remote node. This rights limitation includes a minimumC             of three identifiers that are granted at login when the F             process rights list is created: a UIC identifier, a systemB             identifier, and at least one environmental identifier.  D             User Action: Run SYSMAN from another account with 125 orH             fewer rights identifiers or reduce the number of identifiersE             on the current account to fall within the required range.S  I                                          New OpenVMS System Messages A-25     t              E          RUNNING,  security server is already running; it will not beR             restartedr  -             Facility: SECSRV, Security Servero  G             Explanation: An attempt was made to start a security server +             but another is already running.   E             User Action: Shut down the current server before startingi             another.  A          SAMEDEVICE,  you cannot write output to the disk you are.             repairinga  >             Facility: ANALDISK, Analyze/Disk_Structure Utility  ?             Explanation: You used the /LIST, /OUTPUT, or /USAGEeD             qualifier to write output to the disk you are repairing.  G             User Action: Enter the command again, making sure that noneaC             of the files specified by the /LIST, /OUTPUT, or /USAGER8             qualifier are on the disk you are repairing.  8          SERVERNOTACTIVE,  security server is not active  -             Facility: SECSRV, Security Server   F             Explanation: A request was made of the security server but0             the server is not currently running.  @             User Action: Start the security server and retry the             request.  3          SERVERRESTART,  security server restarting   -             Facility: SECSRV, Security Server   =             Explanation: As requested, the security server iss             restarting.t               User Action: None.  7          SERVERSHUTDOWN,  security server shutting down   -             Facility: SECSRV, Security ServerA  F             Explanation: As requested, the security server is shutting             down.t  G             User Action: None required. If you wish to start a securityNB             server, use the DCL command SET SERVER SECURITY/START.  (         A-26 New OpenVMS System Messages y  r              7          SERVERSTARTINGUP,  security server starting upo  -             Facility: SECSRV, Security Server   F             Explanation: As requested, the security server is starting             up.$               User Action: None.  B          SERVERTERMINATED,  an error caused the security server to             terminateo  -             Facility: SECSRV, Security Server$  ?             Explanation: An error caused the security server tofE             perform cleanup and terminate break-in detection, evasionz-             processing, and proxy processing.   F             User Action: Use the DCL command SET SERVER SECURITY/STARTG             to restart the security server. If this condition persists, 5             contact a Digital support representative.   E          SHADOWLBS,  clearing low-order bit in SHADOWING; function not             longer supported  8             Facility: SYSBOOT, System Bootstrap Facility  B             Explanation: The low-order bit in the SYSGEN parameterE             SHADOWING was set at boot time. This bit has been cleared G             and the system was booted from the physical device named to E             VMB register 3 (R3). Unless you have migrated to phase IIo=             volume shadowing, no shadow sets will be created.                User Action: None.  >          SPF_TOBIG,  second pass fixup data exceeds table size  4             Facility: LOADER, Executive Image Loader  H             Explanation: The loader's internal tables cannot accommodateG             all of the executive image fixups that must be postponed tos-             later in the bootstrap operation.   B             User Action: Contact a Digital support representative.  I                                          New OpenVMS System Messages A-27  E  ,              D          SRVREPLYTIMEOUT,  timed out waiting for reply from security             server  -             Facility: SECSRV, Security Serverh  G             Explanation: The security server did not reply to a requestIG             within the timeout period. Most likely, the security server H             encountered an error while processing the request and had to             restart itself.r  E             User Action: Check the operator log and correct any error,C             condition that caused the security server to terminate.i?             If this problem persists, contact a Digital supports             representative.t  )          SUSPECT,  matching suspect foundy  -             Facility: SECSRV, Security Serverd  G             Explanation: A record matching the request was found in the              intrusion database.   9             User Action: None. The search was successful.   C          TAPEALLODIFFF,  The TAPE_ALLOCLASS parameter value for thee             processoraE             on SCSI bus 'device-name', ID 'slot-number', is differentt*             from the value on this system.F             This condition creates multiple names for the same device,.             which can lead to data corruption.  =             Facility: STACONFIG, Standalone Configure Process   F             Explanation: The value of the SYSGEN tape allocation classF             parameter differs between the local node and the specified             remote node.  E             User Action: Set the TAPE_ALLOCLASS parameter to the samec(             nonzero value on both nodes.  D          TAPEALLOZERF,  This system and/or the processor on SCSI busF             'device-name', ID 'slot-number', has a zero TAPE_ALLOCLASS             value.F             This condition creates multiple names for the same device,.             which can lead to data corruption.  =             Facility: STACONFIG, Standalone Configure Processc  H             Explanation: The local node, remote node, or both nodes haveC             the SYSGEN tape allocation class parameter set to zero.   E             User Action: Set the TAPE_ALLOCLASS parameter to the samed)             nonzero value for both nodes.   (         A-28 New OpenVMS System Messages                   @          TASKERROR,  security server experienced a TASKING_ERROR             exceptiono  -             Facility: SECSRV, Security Server.  B             Explanation: An error occurred in the security server.  B             User Action: Contact a Digital support representative.  E          TOOMANYELTS,  an attempt was made to 'action' 'nnnn' 'class-d:             name' elements. The maximum allowed is 'nnnn'.  .             Facility: MONITOR, Monitor Utility  H             Explanation: MONITOR attempted to display or record a numberF             of elements that exceeds the maximum allowed for the class,             of data specified by class-name.  G             When this message is seen with the DISK class, the elementsxE             being displayed or recorded are individual disks. MONITORiE             will attempt to process all the mounted disks seen by thelE             system. If that number exceeds MONITOR's internal limits,r=             the MONITOR request terminates with this message.   E             User Action: If your MONITOR request selected the /RECORDaD             option, you have reached the record limit of 909. If youB             reissue the request without the /RECORD qualifier, andD             select display and/or summary output, you can monitor as1             many as 1817 disks without recording.n  D             Because MONITOR collects information about mounted disksA             only, you can reduce the number of disks monitored byu%             dismounting unused disks.n  ?          TOOMANYUSERS,  proxy already has the maximum number ofe             associated users  -             Facility: SECSRV, Security Server   H             Explanation: A request was made to add a local user entry toG             a proxy record that already has the maximum number of locala             users.  G             User Action: Delete a local user entry to make room for theo             new one.  I                                          New OpenVMS System Messages A-29: e  e              4          UNDEFENTRY,  invalid queue entry request ID  '             Facility: LAT, LAT Facilityi  F             Explanation: The queue entry you specified does not exist.  G             User Action: Use the LATCP SHOW QUEUE_ENTRY command to listgF             all entries in the local queue. Retry the command, using a             valid queue entry.  /          UNL_PEN,  exec image unload is pendingg  4             Facility: LOADER, Executive Image Loader  F             Explanation: A call was made to LDR$UNLOAD_IMAGE to unloadH             an executive image that is in use. The image is marked to be             unloaded later.i               User Action: None.  D          VALUOVRFLOW,  value too large for 'system-parameter'; field#             width is only 'n' bytess  7             Facility: SYSMAN, System Management Utilityi  B             Explanation: A system parameter is set to a value thatF             exceeds its actual field width. With SYSGEN, you can set aG             parameter value to more than its actual field width without B             getting an error message but SYSGEN silently truncatesF             the value to fit the parameter's field width. In contrast,G             SYSMAN gives a warning and does not change the value of the C             parameter even if PARAMETER DISABLE CHECK is in effect.p  @             User Action: Set the parameter to a value within the             acceptable range.O  @          VEC_TOBIG,  symbol vector reset data exceeds table size  4             Facility: LOADER, Executive Image Loader  E             Explanation: An attempt to load an executive image faileddC             because the image's symbol vector updates for SYS$BASE_oH             IMAGE and SYS$PUBLIC_VECTORS exceed the size of the loader's             internal tables.  B             User Action: Contact a Digital support representative.  (         A-30 New OpenVMS System Messages V  n              H          VERIFY_CONVERSION,  verifying that proxy database conversion is             correctD  -             Facility: SECSRV, Security Serverl  @             Explanation: The contents of the new proxy database,D             NET$PROXY.DAT, are being compared to the contents of the-             old proxy database, NETPROXY.DAT.u               User Action: None.  5          ZEROALLOCLS,  unit has zero allocation classT  -             Facility: SYSTEM, System Servicese  H             Explanation: The physical unit cannot be added to the shadow5             set because the allocation class is zero.o  C             User Action: Make sure all the disks being used to makeaC             the shadow set are configured with an allocation class.eF             Then reenter the command to form or add to the shadow set.B             See the VMScluster Systems for OpenVMS manual for more1             information about allocation classes.T                                            I                                          New OpenVMS System Messages A-31  d                                 F      _________________________________________________________________  F                                                                  Index    9      A                                 ATM intersite link ?      _______________________________      specifications,  8-13x@      Adapters                          AUTOGEN command procedureF        add-on SCSI, 7-12                 AGEN$NO_AUTOCONFIGURE logical2        integral SCSI, 7-16                  , 3-21E        LAN communication, 4-2            AGEN$NO_SPAWN logical,  3-22 F      AGEN$NO_AUTOCONFIGURE logical       AGEN$REPORT_NO_INFORMATIONALS9         name, 3-21                          logical, 3-21O@      AGEN$NO_SPAWN logical name,         computation of SYSMWCNT;         3-22                                parameter, 3-21q;      AGEN$REPORT_NO_INFORMATIONALS       LOAD_DECNET_IMAGES A         logical name, 3-21                  pseudoparameter, 3-22 B      Allocation classes                  preventing autoconfigure,0        setting for SCSI                     3-21E          configurations,  7-5, 7-18,     preventing from running as aaD          7-19                               spawned subprocess, 3-22E      ANALYZE/DISK_STRUCTURE command      suppression of informationala:        erasing home blocks, 3-33            messages, 3-21       ANALYZE/IMAGE command,  2-3F      APPEND command,  2-3              B______________________________5      Applications                      BACKUP command @        TCP/IP, 3-35                      directory levels,  3-25D      Arbitration rules                   /[NO]ALIAS qualifier,  3-255        for control of SCSI bus,        Backup Manager ;          7-42                            description,  3-24 .           modifying the effect of,     BootingB             7-43                         cross-architecture,  6-58      ASSIGN command,  2-3        ATM communications service,         8-6         system management, 8-27        F                                                                Index-1 u                 A                                           Configurations (cont'd) =         C______________________________     SCSI interconnecth  @         C++ RTL object library, 4-17          requirements,  7-3H         Character set description           SCSI VMScluster systems, 7-1I           (charmap) file                    single-ended and differential B          components,  5-73                    SCSI signaling,  7-9F          descriptions of,  5-70 to          single-host SCSI access onE             5-77                              VMScluster system,  7-3e@         Cluster event notification          troubleshooting SCSIG           system services,  4-10              VMScluster systems,  7-38 G         CLUSTER_CONFIG.COM command          unique SCSI device IDs, 7-8 I           procedure                         using CLUSTER_CONFIG for SCSItG          setting up LAN MOP,  6-56            VMScluster systems,  7-27t5         CLUSTER_CONFIG_LAN.COM command      WANs, 8-2 5           procedure,  6-56                ControllersLC         Command files                       HSZ40 controllers, 7-15t4          LAN Control Program (LANCP)      Converters?             utility,  6-52                  using DWZZA in SCSI G         Communications services               VMScluster systems,  7-14t<          ATM,  8-6                        COPY command,  2-3?          DS3,  8-6                          /FTP qualifier, 2-7 ?         Configurations                      /RCP qualifier, 2-7tI          building SCSI VMScluster         CREATE/NAME_TABLE command,  2-3 E             systems with DWZZA            Cross-architecture booting, 1             converters,  7-14                6-58o  "          building with add on SCSII             adapters,  7-12               D______________________________   3          building with an HSZ40           Databasesi;             controller,  7-15               LAN device, 6-7 5          building with BA350/BA353          node, 6-7i:             StorageWorks enclosures,        permanent, 6-79             7-12                            volatile, 6-7e5          building with internal SCSI      Date formatdG             adapters,  7-16                 selecting for SHOW command,i2          displaying LAN,  6-27                3-296          installing SCSI VMScluster       DCL commandsG             systems,  7-17                  automatic foreign commands, 1          LAN,  6-1                            2-3t8          LAN firmware updates,  6-27        changes, 2-3@          multiple-host SCSI access on     DEASSIGN command,  2-4>             VMScluster system,  7-3       DECamds,  3-13, 3-354          SCSI concepts,  7-7              DECnet/OSIB          SCSI hardware,  7-12               full name support, 4-1<                                                routines, 4-2           Index-2                    E         DEFINE command, 2-4               DUMPSTYLE system parameter, 1         DELETE command, 2-4                  3-23          Device IDsI          configuring for SCSI,  7-19      E______________________________fF         Devices                           Error-handling requirements,1          LAN communication,  4-2             8-13 >          managing with LAN Control        Error messages,  A-1H             Program (LANCP) utility,      EXCHANGE/NETWORK command,  2-4             6-8t+         DIFFERENCES command, 2-4          FaI         Differential signaling            _______________________________ .          for SCSI,  7-9                   FDDID         Digital Availability Manager        multiple-site VMSclusterB           for Distributed Systems             configurations,  8-5C          See DECamds                      Feedback on documentation G         Digital writers                     sending comments to Digitali;          sending comments to,  iii            writers,  iii 2         DIRECTORY command, 2-4            Firmware=          /FTP qualifier,  2-7               LAN updates, 6-27t=         Disks                             Freeware disc,  2-1l4          access to SCSI storage,  7-3     Full names9          SCSI,  7-1                         support, 3-25 8          SCSI concepts,  7-7                SYSMAN, 3-25            SCSI configurationiI             requirements,  7-3            G______________________________e  >          SCSI storage interconnect,       GENCAT command,  5-23             3-9                           GroundingtC         Documentation                       SCSI requirements, 7-18vA          sending comments to Digital        troubleshooting, 7-42                writers,  iiieI         DR_UNIT_BASE system parameter,    H______________________________s  2           3-23                            HardwareF         DS3 communications service,         add-on SCSI adapters, 7-12D           8-6                               BA350/BA353 StorageWorks?          system management,  8-27             enclosures,  7-12dB         DS3 interconnect                    DWZZA converters, 7-14C          in VMScluster systems,  3-11       HSZ40 controllers, 7-15 G         DS3 intersite link                  in SCSI VMScluster systems,e2           specifications,  8-13               7-12H         Dump file off system disk,          integral SCSI adapters, 7-165           3-35                            Home blockso  9                                             erasing, 3-33e  I                                                                   Index-3u y  r                       Host-based RAIDoI          support for,  7-5                L______________________________ 8         Host-based shadowing              LANACP utilityE          support for,  7-5                  See LAN Auxiliary ControlS=         Host IDs                              Program utilityrG          configuring for SCSI,  7-18      LAN Auxiliary Control Programr=         Hosts                                (LANACP) utilitySF          in a VMScluster system,  7-1       booting cluster satellites$         Hot plugging (SCSI devices),9           7-46                                with,  3-16GC         HSC series controller failover      clearing counters, 6-44sH           ,  3-13                           deleting device information,2         HSD series controller failover        6-35F           ,  3-13                           deleting node information,2         HSJ series controller failover        6-43G           ,  3-13                           device database management,e2                                               6-28G         I                                   disabling MOP downline loadm<         _______________________________       service,  6-36I         ICONV commands                      displaying device information 5          COMPILE,  5-8                        ,  6-34tH          CONVERT,  5-15                     displaying node information,2         INITIALIZE command, 2-4               6-42F         Installation                        displaying OPCOM messages,2          configuring SCSI node IDs,           6-46A             7-18                            displaying status ands=          SCSI VMScluster systems,             counters,  6-44uF             7-17                            enabling MOP downline load<         Interconnects                         service,  6-36E          accessing SCSI storage over,       Load Trace facility, 6-47oE             7-2                             MOP downline load servicet?          ATM,  8-6                            management,  6-43rE          DS3,  3-11, 8-6                    node database management, 2          FDDI,  8-5                           6-36E          SCSI,  3-9, 7-1                    OPCOM messages displayed, 2          troubleshooting SCSI,  7-38          6-579         Internet, 3-35                      running, 6-54 9         Internet address                    servers, 6-52rG          specifying in Mail,  2-7           setting device information,f         ISA devicesr2          configuring,  4-4 to 4-7             6-29E                                             setting node information, 2                                               6-37:                                             stopping, 6-54           Index-4     G              D         LAN Control Program (LANCP)       LANs (local area networks)5           utility,  6-5                      (cont'd)sF          booting cluster satellites         displaying OPCOM messages,2             with,  3-15                       6-46A          device management,  6-8            displaying status and-=          LAN$DEVICE_DATABASE.DAT file,        counters,  6-44 F             3-15                            enabling MOP downline load<          LAN$NODE_DATABASE.DAT file,          service,  6-36E             3-15                            Ethernet controllers, 4-3 C          MOP console carrier,  6-48         ISA devices, 4-4 to 4-7 B          MOP trigger boot,  6-50            LANACP device database?          running,  6-6                        management,  6-28mI          setting up LAN MOP,  6-57          LANACP related OPCOM messagesS5          SPAWN function,  6-52                ,  6-57RI          using command files,  6-52         LAN Auxiliary Control Program   E         LANCP (Local Area Network             (LANACP) utility,  6-52AG           Control Program)                  LAN Control Program (LANCP)a  ;          See LAN Control Program              utility,  6-5aE             utility                         LANCP command files, 6-52nF         Language                            LANCP SPAWN function, 6-52F          selecting for SHOW command,        LAN firmware updates, 6-27H             3-29                            LAN MOP and DECnet MOP, 6-54E         LANs (local area networks)          Load Trace facility, 6-47 G          clearing counters,  6-44           migrating DECnet MOP to LAN 8          communication devices and            MOP,  6-55E             drivers,  4-2                   MOP console carrier, 6-48 F          databases,  6-7                    MOP downline load service,2          deleting device information,         6-54E             6-35                            MOP downline load servicel?          deleting node information,           management,  6-43rB             6-43                            MOP trigger boot, 6-50D          device management,  6-8            multiple-site VMScluster;          device names,  4-3                   systems,  8-3tE          disabling MOP downline load        node database management,m2             service,  6-36                    6-36G          displaying device information      running the LANACP utility, 2             ,  6-34                           6-54G          displaying LAN device              sample LAN MOP set up, 6-57 G             configurations,  6-27           setting device information,l2          displaying LAN device                6-29I             parameters,  6-21               setting LAN device parameters 4          displaying node information,         ,  6-9E             6-42                            setting node information,   2                                               6-37  I                                                                   Index-5i    ,              G         LANs (local area networks)        LGI_BRK_LIM system parameter,.1           (cont'd)                           3-23UA          setting up LAN MOP with          License database,  3-28eG             CLUSTER_CONFIG,  6-56         LICENSE MODIFY command,  3-28U2          stopping the LANACP utility,     LicensesG             6-54                            VMScluster client software,c2          system management                    3-11?             enhancements,  6-1            Linker utility,  4-17 D         LAT Control Program (LATCP)       Load Trace facility,  6-47<           utility,  3-28                  LOAD_DECNET_IMAGESD         LATCP (Local Area Transport         AUTOGEN pseudoparameter,2           Control Program)                    3-22  F          See LAT Control Program          Local Area Network Auxiliary<             utility                          Control Program  E         LAT software                        See LAN Auxiliary Controle=          LAT Control Program (LATCP)          Program utility   =             utility,  3-28                Local area networks   4          SET HOST/LAT command,  3-28        See LANs9             new qualifiers,  2-5          LOCALE commandsL9         Layered products                    COMPILE, 5-17p6          inclusion on distribution          LOAD, 5-20G             kit,  3-36                      SHOW CHARACTER_DEFINITIONS,e2         LC_COLLATE locale category,           5-22>           5-35                              SHOW CURRENT, 5-23=         LC_CTYPE locale category, 5-41      SHOW PUBLIC, 5-26p<         LC_MESSAGES locale category,        SHOW VALUE, 5-278           5-47                              UNLOAD, 5-21<         LC_MONETARY locale category,      Locale file formatD           5-48                              descriptions of, 5-33 to2          format variations,  5-55             5-69D          keywords,  5-49                    locale categories, 5-33,2         LC_NUMERIC locale category,           5-34             5-57I         LC_TIME locale category, 5-59     M______________________________e  .          field descriptors,  5-64         MAILC          keywords,  5-59                    MAIL$INTERNET_TRANSPORTZ@          sample locale definition,            logical name,  2-7C             5-68                            specifying addresses in C         Lexical functions                     Internet format,  2-7aH          F$CONTEXT,  2-4                  Managing multiple sites,  8-29=          F$GETQUI,  2-4                   MERGE command,  2-6i8          F$GETSYI,  2-4                   Messages,  A-1           Index-6  t  s              /         MOP downline load service         OPCOMm=          clearing counters,  6-44           messages (cont'd)sF          console carrier,  6-48                displayed during LANACP=          disabling,  6-36                        start,  6-57 H          displaying status and                 generated by LANACP, 6-46H             counters,  6-44                 OPC$V_OPR_* bit definitions,2          enabling,  6-36                      3-30I          LANACP server,  6-43               OPC$Z_MS_ENAB_TERMINALS field 5          LAN MOP,  6-54                       ,  3-31 I             coexisting with DECnet          OPC$Z_MS_TARGET_CLASSES field 5                MOP,  6-54                     ,  3-31 D          migrating DECnet MOP to LAN        OPR$V_* bit definitions,2             MOP,  6-55                        3-30H          sample setup,  6-57                overriding symbol values forH          setup with CLUSTER_CONFIG.COM        workstations in a cluster,2             ,  6-56                           3-30>          trigger boot,  6-50              OpenVMS Alpha SCSI-2  @         N                                   device support, 4-16@         _______________________________   OpenVMS cluster client;         NET$PROXY.DAT file, 3-26, 3-27       software, 3-11SD         NETPROXY.DAT file, 3-26           OpenVMS Management Station<         Networks                            description, 3-2>          Internet,  3-35                    documentation, 3-5>          LAN enhancements,  6-1             features, 3-4, 3-5
         Nodes I          deleting node information,       P______________________________m4             6-43                          Parameters>          in a VMScluster system,  7-1       setting SCSI, 7-235          setting node information,        Performance-D             6-37                            data transfer rates, 7-9  =         O                                   SCSI storage, 7-8 I         _______________________________   Performance requirements,  8-13 1         OPC$OPA0_ENABLE logical           Persona :          defining,  3-30                    assuming, 4-11:         OPC$Z_MS_ENAB_TERMINALS OPCOM       creating, 4-13:           field,  3-31                      deleting, 4-15H         OPC$Z_MS_TARGET_CLASSES OPCOM     $PERSONA_ASSUME system service3           field,  3-31                       , 4-11oH         OPCOM                             $PERSONA_CREATE system service3          defining OPC$OPA0_ENABLE,           , 4-13eH             3-30                          $PERSONA_DELETE system service3          enabling selected operator          , 4-15                classes,  3-30          messagesc  I                                                                   Index-7n f  5              $         Portable Character Set, 5-70I         Port-queue functionality, 4-17    S______________________________s4         PRINT command, 2-4                Satellites9         Protocols                           booting, 6-54sG          for using TCP/IP,  3-35            cross-architecture booting,i2         Proxy authorization files,            6-58B           3-26                              LAN MOP and DECnet MOPD          NET$PROXY.DAT,  3-26                 downline load service,2          NETPROXY.DAT,  3-26                  6-54I         PURGE command, 2-4                  migrating to LAN MOP downline   A         R                                     load service,  6-55 2         _______________________________   SCSI busC         RAID (redundant arrays of           arbitration rules, 7-42 G           independent disks),  7-3             modifying the effect of,O5          volume shadowing support,               7-43 <             3-8                             control of, 7-424         RECALL command, 2-4               SCSI disks:         Redundant arrays of                 accessing, 7-2H           independent disks                 configurations requirements,1          See RAID                             7-3 C         RENAME command, 2-4                 modes of operation, 7-8 B         Requirements                        unique device IDs, 7-8A          Bellcore Communications          SCSI interconnect,  7-1 >             Research,  8-14                 ANSI standard, 7-1C          VMScluster,  8-14                  as a VMScluster storage @         RMTDBG_SCRATCH_PAGES system           interconnect,  3-9D           parameter,  3-23                  cabling and termination,2         RTL (run-time library)                7-119          See Run-time library (RTL)         concepts, 7-7 G                                             configuration requirements,-1             routines                          7-3 G         RUN (process) command, 2-4          configurations using add onpB         Run-time library (RTL)                SCSI adapters,  7-12I           routines                          configurations using an HSZ40E?          LIB$BUILD_NODESPEC,  4-2             controller,  7-15nF          LIB$COMPARE_NODENAME,  4-2         configurations using BA350A          LIB$COMPRESS_NODENAME,  4-2          /BA353 StorageWorks ?          LIB$EXPAND_NODENAME,  4-2            enclosures,  7-12-F          LIB$FIT_NODENAME,  4-2             configurations using DWZZA?          LIB$GET_FULLNAME_OFFSET,  4-2        converters,  7-14gI          LIB$GET_HOSTNAME,  4-2             configurations using integral B          LIB$TRIM_FULLNAME,  4-2              SCSI adapters,  7-16  H                                             configuring device IDs, 7-19           Index-8A                   D         SCSI interconnect (cont'd)        SET HOST/DTE command,  2-5E          configuring SCSI node IDs,       SET HOST/LAT command,  2-5,s1             7-18                             3-28 C          configuring with CLUSTER_        SET MAGTAPE command,  2-5iD             CONFIG.COM,  7-27             SET SECURITY command,  2-5D          connected to a single host,      SET TERMINAL command,  2-5@             7-3                           SET TIME command,  2-5B          connected to multiple hosts,     SET VOLUME command,  2-53             7-3                           Shadowing <          data transfer rates,  7-9          support for, 7-5E          grounding requirements,  7-18    SHADOWING system parameter, 1          hardware configurations,            3-23a5             7-12                          Shadow setsSH          hot plugging devices with,         increased numbers supported,6             7-46                              3-6, 3-76          installation,  7-17              SHOW commandG          maximum distances,  7-10           time and date formats, 3-29EE          maximum length,  7-9             SHOW DEVICES/REBUILD_STATUSt9          number of devices supported,        command, 2-5eF             7-8                           SHOW DEVICES/SERVED command,0          performance,  7-8                   2-5G          power up and verify,  7-20       SHOW INTRUSION command,  3-27 D          show and set console             SHOW PROCESS command,  2-5E             parameters,  7-23             SHOW SECURITY command,  2-5 C          TERMPWR line,  7-11              SHOW SYSTEM command,  2-6tE          troubleshooting,  7-38           SHOW TERMINAL command,  2-6 B         SCSI tapes                        SHOW USERS command,  2-6A          no support for SCSI retension    SHUTDOWN$DECNET_MINUTES :             ,  3-13                          logical, 3-34H          support in a VMScluster          SHUTDOWN$QUEUE_MINUTES logical3             system,  3-12                    , 3-34 6         SEARCH command, 2-5               SHUTDOWN.COM:         Security Server process             logicals, 3-34@          intrusion database,  3-27        Single-ended signaling9          network proxy database,  3-27      for SCSI, 7-9t  @         Security system services, 4-8     Small Computer Systems6         Sending comments to Digital          Interface  4           writers,  iii                     See SCSIC         SET AUDIT command, 2-5            SONET OC-3 intersite linktA         SET DIRECTORY command, 2-5           specifications, 8-13 <         SET FILE command, 2-5             SORT command,  2-6=         SET HOST command                  SPAWN command,  2-6            /RLOGIN qualifier,  2-7           /TELNET qualifier,  2-7           /TN3270 qualifier,  2-7  I                                                                   Index-9, 4                 ;         SPAWN function                    System management ?          LAN Control Program (LANCP)        ATM multisite, 8-271C             utility,  6-52                  clearing counters, 6-44eH         Specifications                      deleting device information,2          ATM Intersite Link,  8-13            6-35F          DS3 Intersite Link,  8-13          deleting node information,2          T3 Intersite Link,  8-13             6-43G          WAN Intersite Link,  8-13          disabling MOP downline load <         STOP command, 2-6                     service,  6-36I         StorageWorks                        displaying device information 5          BA350/BA353 enclosures,  7-12        ,  6-34TA         SUBMIT command, 2-6                 displaying LAN device C         Subprocesses                          configurations,  6-27 A          creating with the LANCP SPAWN      displaying LAN device ?             function,  6-52                   parameters,  6-21 H         SYS$ADD_PROXY system service,       displaying node information,2           4-9                                 6-42F         SYS$CLRCLUEVT system service,       displaying OPCOM messages,2           4-10                                6-46A         SYS$DELETE_INTRUSION system         displaying status and8=           service,  4-8                       counters,  6-44 5         SYS$DELETE_PROXY system             DS3, 8-27 F           service,  4-9                     enabling MOP downline load<         SYS$DISPLAY_PROXY system              service,  6-36H           service,  4-9                     LANACP device database, 6-28I         SYS$PERSONA_ASSUME system           LAN Auxiliary Control ProgrameE           service,  4-11                      (LANACP) utility,  6-52eG         SYS$PERSONA_CREATE system           LAN Control Program (LANCP) ;           service,  4-13                      utility,  6-5eE         SYS$PERSONA_DELETE system           LANCP command files, 6-52 F           service,  4-15                    LANCP SPAWN function, 6-52>         SYS$SCAN_INTRUSION system           LAN databases, 6-7<           service,  4-8                     LAN devices, 6-8A         SYS$SETCLUEVT system service,       LAN enhancements, 6-1iF           4-10                              LAN firmware updates, 6-27I         SYS$SHOW_INTRUSION system           LAN node database management,s2           service,  4-8                       6-36E         SYS$TSTCLUEVT system service,       Load Trace facility, 6-47bC           4-10                              methods and tools, 8-29 E         SYS$VERIFY_PROXY system             MOP console carrier, 6-48nE           service,  4-9                     MOP downline load service,?         SYSMWCNT parameter                    management,  6-43dB          computation of,  3-21              MOP trigger boot, 6-50;                                             multisite, 8-27A           Index-10 e                 "         System management (cont'd)I          running the LANACP utility,      T______________________________g  ;             6-54                          T3 intersite linkuA          running the LANCP utility,          specifications, 8-13t@             6-6                           Tagged command queuing@          setting device information,        device support, 4-16>             6-29                            I/O requests, 4-16/          setting LAN device parameters    TapesiI             ,  6-9                          no support for SCSI retension 5          setting node information,            ,  3-13 6             6-37                            SCSI, 3-12>          stopping the LANACP utility,       TMSCP served, 3-12F             6-54                          TCP/IP (Transmission ControlH          WAN multisite,  8-27                Protocol/Internet Protocol)>         System Management utility           applications, 3-35=           (SYSMAN)                          DCL commands, 2-7-5          full name support,  3-25         Terminatorsn:         System messages, A-1                for SCSI, 7-115         System parameters                 Time format G          DR_UNIT_BASE,  3-23                selecting for SHOW command, 2          DUMPSTYLE,  3-23                     3-297          LGI_BRK_LIM,  3-23               TMSCP serversbE          RMTDBG_SCRATCH_PAGES,  3-23        controlled by TMSCP_LOAD,e2          SHADOWING,  3-23                     3-12F          TMSCP_SERVE_ALL,  3-23             controlled by TMSCP_SERVE_8          VCC_PTES,  3-24                      ALL,  3-12F         System services, 4-8                SCSI tapes in a VMScluster;          $ADD_PROXY,  4-9                     system,  3-12 F          $CLRCLUEVT,  4-10                TMSCP_LOAD system parameter,1          cluster event notification,         3-12 @             4-10                          TMSCP_SERVE_ALL systemB          $DELETE_INTRUSION,  4-8             parameter, 3-12, 3-23G          $DELETE_PROXY,  4-9              Transmission Control Protocol ?          $DISPLAY_PROXY,  4-9                /Internet Protocol 6          $PERSONA_ASSUME,  4-11             See TCP/IP6          $PERSONA_CREATE,  4-13           Trigger bootC          $PERSONA_DELETE,  4-15             LANCP MOP downline load           $SCAN_INTRUSION,  4-8<          security,  4-8                       service,  6-509          $SETCLUEVT,  4-10                Troubleshooting E          $SHOW_INTRUSION,  4-8              SCSI configurations, 7-38 <          $TSTCLUEVT,  4-10                TYPE command,  2-6            $VERIFY_PROXY,  4-9  I                                                                  Index-11, -                 E                                           VMScluster systems (cont'd)eF         V______________________________     SCSI storage interconnect,  1         VCC_PTES system parameter,            7-1PD           3-24                              serving SCSI tapes, 3-12H         VMScluster systems                  setting up for LAN MOP, 6-57I          ATM communications service,        shared SCSI storage concepts, 1             8-6                               7-7-G          ATM multisite system               using CLUSTER_CONFIG to set ?             management,  8-27                 up LAN MOP,  6-56O;          booting with LANCP instead of      using FDDI, 8-5OB             DECnet,  3-15                   using LANCP as booting>          client software licensing,           mechanism,  3-15G             3-11                            using the DS3 interconnect, 2          CLUSTER_CONFIG.COM,  7-27            3-11H          cross-architecture booting,        using the SCSI interconnect,1             6-58                              3-97@          DS3 communications service,        WAN multisite system?             8-6                               management,  8-27 C          DS3 system management,  8-27       warranted and migrationfC          hosts, nodes, and computers,         configurations,  3-13 :             7-1                           Volume shadowingD          HSC series controller              geometry-based shadowingF             failover,  3-13                   device recognition,  3-6=          HSD series controller              new features, 3-6 =             failover,  3-13                 RAID support, 3-8eC          HSJ series controller              shadow set numbers, 3-6 >             failover,  3-13                    guidelines, 3-7            installing SCSI,  7-17fI          LAN management enhancements,     W______________________________i  D             6-1                           WAN communications serviceC          LAN MOP coexisting with            system management, 8-27 <             DECnet MOP,  6-54             WAN intersite linkA          migrating from DECnet MOP to        specifications, 8-13e.             LAN MOP,  6-55                WANsE          multiple-site,  8-1                utilizing in a VMScluster :          SCSI configuration                   system,  8-2<             requirements,  7-3            Wide area networks4          SCSI hardware configurations,      See WANs             7-12          SCSI performance,  7-8 $          SCSI storage connected to a             single host,  7-3N"          SCSI storage connected to              multiple hosts,  7-3           Index-12 t  E              ;                                             LOCALE commands <         X______________________________        COMPILE, 5-179         XPG4 localization utilities,           LOAD, 5-20 I           5-1                                  SHOW CHARACTER_DEFINITIONSi8          character map (charmap) file,           ,  5-22A             5-70 to 5-77                       SHOW CURRENT, 5-23 @          GENCAT command,  5-2                  SHOW PUBLIC, 5-26?          ICONV commands                        SHOW VALUE, 5-27 ;             COMPILE,  5-8                      UNLOAD, 5-21_G             CONVERT,  5-15                  locale file format, 5-33 tos2                                               5-69                                                                    I                                                                  Index-13u                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        