                                             H                     ____________________________________________________5                     OpenVMS Version 6.2 Release Notes     -                     Order Number: AA-QJEFA-TE                          May 1995  H                     This manual describes changed and enhanced features;B                     upgrade and compatibility information; new andD                     existing software problems and restrictions; and;                     software and documentation corrections.               G                     Revision/Update Information:  This is a new manual.   E                     Software Version:             OpenVMS Version 6.2           1                     Digital Equipment Corporation *                     Maynard, Massachusetts                 J           ________________________________________________________________           May 1995  @           Digital Equipment Corporation makes no representationsA           that the use of its products in the manner described in B           this publication will not infringe on existing or futureB           patent rights, nor do the descriptions contained in thisB           publication imply the granting of licenses to make, use,>           or sell equipment or software in accordance with the           description.  B           Possession, use, or copying of the software described inA           this publication is authorized only pursuant to a valid D           written license from Digital or an authorized sublicensor.  B           Digital conducts its business in a manner that conservesC           the environment and protects the safety and health of its 2           employees, customers, and the community.  D            Digital Equipment Corporation 1995. All rights reserved.  ;           The following are trademarks of Digital Equipment D           Corporation: ACMS, ALL-IN-1, AlphaGeneration, AlphaServer,7           AlphaStation, AXP, BASEstar, Bookreader, CDA, A           CDD/Administrator, CDD/Repository, CI, DATATRIEVE, DEC, >           DEC @ a Glance, DEC ACA Services, DEC Ada, DEC DBMS,9           DEC Fortran, DEC GKS, DEC MAILworks, DEC Notes, >           DEC OPS5, DEC Pascal, DEC PHIGS, DEC RALLY, DEC Rdb,<           DEC Reliable Transaction Router, DEC SecurityGate,<           DEC SNA, DEC SNA Domain Gateway, DEC Test Manager,;           DEC VTX, DECADMIRE, DECamds, DECdecision, DECdtm, C           DECevent, DECforms, DECgraph, DEChub DECimage, DECintact, <           DECmessageQ, DECmigrate, DECnet, DEComni, DECplan,>           DECpresent, DECprint, DECprint Supervisor, DECquery,B           DECram, DECserver, DECset, DECslide, DECss7, DECstation,9           DECterm, DECthreads, DECtp, DECtrace, DECvoice, @           DECvoiceBuilder, DECwindows, DECwrite, DEQNA, Digital,@           DSM, EDCS, HSC, HSD, HSJ, HSZ, InfoServer, InstantSQL,@           KDA, KDM, LASTport, LN03, MAILbus, MAILWorks, MASSBUS,<           MicroVAX, MSCP, MUXserver, ObjectBroker, OpenDATA,D           OpenVMS, OpenVMS RMS, OpenVMS Volume Shadowing, PATHWORKS,A           POLYCENTER, PrintServer, Q-bus, Rdb/VMS, ReGIS, RMS-11, ?           RX, RZ, SQL Multimedia, SSU, StorageWorks, TeamLinks, D           TeamRoute, ThinWire, TK, TMSCP, TURBOchannel, UDA, ULTRIX,?           UNIBUS, VAX, VAX 4000, VAX 6000, VAX 7000, VAX 10000, D           VAX ACMS, VAX Ada, VAX APL, VAX BASIC, VAX BLISS-32 VAX C,?           VAX COBOL, VAX COBOL GENERATOR, VAX DOCUMENT VAX FMS, >           VAX MACRO, VAX Notes, VAX RMS, VAX TDMS, VAXcluster,D           VAXELN, VAXft, VAXstation, VAXuisx, VIDA, VMS, VMScluster,B           Volume Shadowing for OpenVMS, VT240, VT52, XMI, XUI, the-           DEC C++ logo, and the DIGITAL logo.        ii                3           The following are third-party trademarks:   1           Adaptec is a trademark of Adaptec, Inc.   ?           DB2 is a trademark of International Business Machines            Corporation.  >           Internet is a registered trademark of Internet, Inc.  C           Kodak is a registered trademark of Eastern Kodak Company.   E           Macintosh is a registered trademark of Apple Computer, Inc.   D           Motif, OSF, and OSF/Motif are registered trademarks of the(           Open Software Foundation, Inc.  D           MS-DOS is a registered trademark of Microsoft Corporation.  ;           NetWare is a registered trademark of Novell, Inc.   A           ORACLE is a registered trademark of Oracle Corporation.   C           POSIX is a registered certification mark of the Institute 2           of Electrical and Electronics Engineers.  ?           PostScript is a registered trademark of Adobe Systems            Incorporated.   :           SYBASE is a registered trademark of Sybase, Inc.  A           UNIX is a registered trademark in the United States and >           other countries, licensed exclusively through X/Open           Company Ltd.  ;           X/Open is a trademark of X/Open Company, Limited.   @           All other trademarks and registered trademarks are the/           property of their respective holders.   E                                                                ZK6422   /           This document is available on CD-ROM.   D           This document was prepared using VAX DOCUMENT Version 2.1.       								iii                                 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 Corporation&                  OpenVMS Documentation0                  110 Spit Brook Road, ZKO3-4/U08'                  Nashua, NH  03062-2698                   USA                 Thank you.                       iv                                 C   _________________________________________________________________   C                                                            Contents       C   Preface...................................................    xix   8   1  OpenVMS Installation, Upgrade, and Hardware Release
      Notes  <         1.1   Installation and Upgrade Information Common toC               VAX and Alpha ................................    1-1 C         1.1.1     Changes and Enhancements..................    1-1 C         1.1.1.1     Software Product Descriptions (SPDs)....    1-2 6         1.1.1.2     Using ConDIST to Update InfoServerC                     Software ...............................    1-2 C         1.1.2     Problems and Restrictions.................    1-3 C         1.1.2.1     DECnet Product Requirements.............    1-3 C         1.1.2.2     DECnet/OSI Installation Can Fail........    1-4 <         1.1.2.3     DECnet/OSI: NET$MANAGE Rights IdentifierC                     Recommended.............................    1-4 :         1.1.2.4     InfoServer Client Can Fail to Start IfC                     DECnet Is Started or Stopped............    1-5 4         1.1.2.5     POLYCENTER Software Installation;                     Utility Can Hang During Layered Product C                     Installations...........................    1-5 9         1.1.2.6     VMSINSTAL Can Fail to Update DCL Help C                     During Layered Product Installations....    1-6 3         1.2   VAX Specific Installation and Upgrade C               Information...................................    1-7 C         1.2.1     Problems and Restrictions.................    1-7 C         1.2.1.1     Upgrade Version Requirements ...........    1-7 0         1.2.1.2     Volume Shadowing Phase I NotC                     Available...............................    1-7 9         1.2.1.3     DECnet for OpenVMS VAX Extensions Not C                     Supported...............................    1-8 C         1.2.1.4     MACRO32.EXE and Standalone BACKUP.......    1-8     C                                                                   v                    <           1.2.1.5     DECpresent Dependencies for InstallingE                       on OpenVMS VAX Version 6.1..............    1-8 :           1.2.1.6     VAXstation and MicroVAX InstallationE                       Workaround..............................    1-9 7           1.3   Alpha Specific Installation and Upgrade E                 Information...................................    1-9 E           1.3.1     Changes and Enhancements..................    1-9 =           1.3.1.1     Installing or Upgrading an Alpha System E                       from a Running System...................    1-9 :           1.3.1.2     Removing the OpenVMS Alpha OperatingE                       System .................................   1-10 E           1.3.2     Problems and Restrictions.................   1-11 E           1.3.2.1     RAID Devices Naming Problem.............   1-11 E           1.3.2.2     Audio Editor in DECwindows Mail.........   1-12 E           1.3.2.3     Booting Messages .......................   1-12 E           1.3.3     Corrections...............................   1-12 E           1.3.3.1     System Directories Installation.........   1-13 E           1.4   Alpha Firmware Revisions......................   1-13 3           1.5   AlphaStation and AlphaServer Series E                 Computers.....................................   1-13 E           1.5.1     Changes and Enhancements..................   1-13 8           1.5.1.1     Console Variable Default Change onE                       AlphaServer 2100 Systems................   1-13 E           1.5.1.2     Graphics Support........................   1-14 E           1.5.2     Problems and Restrictions.................   1-14 E           1.5.2.1     Adapter Support.........................   1-14 E           1.5.2.2     Bells on AlphaStation 400 Systems.......   1-14 E           1.5.2.3     DECterm Startup.........................   1-15 E           1.5.2.4     Ethernet Wire Settings..................   1-15 E           1.5.2.5     Graphics Support........................   1-15 E           1.5.2.6     HALT/CONTINUE Restriction...............   1-17 E           1.5.2.7     KFESA Port Reinitializing Message ......   1-17 :           1.5.2.8     RX23 Disks Supported Instead of RX26E                       Disks...................................   1-17 E           1.5.2.9     SCSI Controller Restriction.............   1-17 E           1.5.2.10    Window Corruption.......................   1-18 E           1.6   Ethernet and FDDI Controllers.................   1-18 E           1.6.1     Problems and Restrictions.................   1-18 =           1.6.1.1     Multiple Controllers Configured But Not E                       All Attached to a Wire (Alpha Only).....   1-18 E           1.7   RF73 and Other RFnn DSSI Disk Devices ........   1-20              vi                   I               1.7.1     Problems and Restrictions.................   1-20 ?               1.7.1.1     RF73 and Other RFnn DSSI Disk Devices I                           and Controller Memory Errors............   1-20 9               1.8   Hardware Information: VAX 4000 Series I                     Computers (VAX Only)..........................   1-23 I               1.8.1     Changes and Enhancements..................   1-24   %         2  General User Release Notes   I               2.1   Batch and Print Queues........................    2-1 I               2.1.1     Corrections...............................    2-1 I               2.1.1.1     File Search Qualifiers..................    2-1 I               2.1.1.2     Print Job Alignment.....................    2-2 I               2.2   DCL Commands..................................    2-2 I               2.2.1     Problems and Restrictions.................    2-2 @               2.2.1.1     SET PROCESS/NOAUTO_UNSHELVE Command inI                           Cluster Environment ....................    2-2 @               2.2.1.2     SET PROCESS/SUSPEND=KERNEL/ID= CommandI                           in Cluster Environment .................    2-3 I               2.2.2     Corrections...............................    2-3 I               2.2.2.1     DELETE/QUEUE/MANAGER Command............    2-3 I               2.2.2.2     INITIALIZE/QUEUE Command................    2-3 I               2.2.2.3     PRINT/DELETE Command....................    2-4 I               2.2.2.4     PRINT/FORM Command on LAT Printers......    2-4 I               2.2.2.5     SET QUEUE/DESCRIPTION Command...........    2-4 I               2.2.2.6     SET QUEUE/NODESCRIPTION Command.........    2-4 I               2.2.2.7     SHOW SYSTEM Command.....................    2-4 I               2.2.2.8     START/QUEUE Command.....................    2-5 I               2.2.2.9     SUBMIT Command..........................    2-5 8               2.2.2.10    SUBMIT/NAME and SET ENTRY/NAMEI                           Commands................................    2-5 I               2.2.2.11    SUBMIT/NAME/USER Command................    2-6 I               2.3   DECnet Layered Product........................    2-6 I               2.3.1     Changes and Enhancements..................    2-6 7               2.3.1.1     DECnet Phase IV Superseded by I                           DECnet/OSI..............................    2-6 I               2.4   DECserver ....................................    2-7 I               2.4.1     Problems and Restrictions.................    2-7 I               2.4.1.1     Baud Rate Using LAT.....................    2-7 I               2.5   DECTPU .......................................    2-7 I               2.5.1     Problems and Restrictions.................    2-8 I               2.5.1.1     Motif Widget Context Help Built-In......    2-8 I               2.6   DECwindows Motif for OpenVMS .................    2-8     I                                                                       vii                    E           2.6.1     Changes and Enhancements..................    2-8 >           2.6.1.1     Support for DECwindows Motif Version 1.1E                       for OpenVMS.............................    2-8 9           2.6.1.2     NCSA Mosaic Browser: TCP/IP Support E                       Options.................................    2-9 E           2.7   Image Activator...............................    2-9 E           2.7.1     Changes and Enhancements .................    2-9 8           2.7.1.1     Message Returned on Attempt to Run9                       an Alpha Image on a VAX System (VAX E                       Only)...................................    2-9 E           2.8   Sort/Merge Utility............................    2-9 E           2.8.1     Changes and Enhancements..................    2-9 E           2.8.1.1     /FIELD Qualifier........................   2-10   &     3  System Management Release Notes  E           3.1   Authorize Utility (AUTHORIZE).................    3-1 E           3.1.1     Changes and Enhancements..................    3-1 7           3.1.1.1     WSQUOTA Maximum Value Is 64K Byte E                       Pages...................................    3-1 E           3.2   AUTOGEN.......................................    3-1 E           3.2.1     Changes and Enhancements .................    3-1 =           3.2.1.1     AGEN$PARAMS.REPORT: Turning Off Logging E                       (Alpha Only)............................    3-2 E           3.2.1.2     CTLPAGES Parameter Value (VAX Only).....    3-2 E           3.2.1.3     Dump File Size (VAX Only)...............    3-2 E           3.2.1.4     Retired Parameters (VAX Only)...........    3-3 E           3.2.1.5     SYSMWCNT Computations (VAX Only)........    3-3 E           3.2.1.6     WSMAX Computations (VAX Only)...........    3-4 E           3.2.2     Problems and Restrictions ................    3-4 E           3.2.2.1     Full Memory Dumps (Alpha Only)..........    3-4 E           3.3   Backup Utility ...............................    3-4 E           3.3.1     Problems and Restrictions.................    3-4 E           3.3.1.1     Image and Incremental Backups...........    3-5 =           3.3.1.2     Incremental Backups Using PATHWORKS for_E                       OpenVMS Servers.........................    3-5 4           3.3.1.3     Warning Issued on ANALYZE/DISKE                       Operation...............................    3-6aE           3.3.1.4     CD-ROM Menu System (VAX Only)...........    3-7sE           3.3.1.5     Image Backups from an RF73 Disk.........    3-7n=           3.3.1.6     Relative File Version -0 Processed LikesE                       0.......................................    3-8i           viii e  i              B               3.3.1.7     Standalone BACKUP Version 5.3 on ConsoleI                           Media (VAX Only)........................    3-8r?               3.3.1.8     Standalone BACKUP Failure on VAX 4000 I                           Model 300 and TF857 (VAX Only)..........    3-9 I               3.3.1.9     VMS$COMMON.DIR File: Restore Problems...    3-9,I               3.3.2     Corrections...............................   3-11 I               3.3.2.1     BACKUP$_ACCONFLICT Error Message........   3-11iI               3.3.2.2     Boot Block Saved Correctly (VAX Only)...   3-11hI               3.3.2.3     Incremental Restore ....................   3-12 I               3.3.2.4     Save Operation Error Message............   3-14 I               3.4   Batch and Print Queue Management .............   3-14GI               3.4.1     Problems and Restrictions.................   3-14DI               3.4.1.1     Process Rights Identifier Limits........   3-14GI               3.4.1.2     VMScluster Environment .................   3-15 I               3.4.1.3     PRINT/DELETE Command ...................   3-15EI               3.4.1.4     SUBMIT/DELETE Command ..................   3-15iI               3.4.2     Corrections...............................   3-16SI               3.4.2.1     Form Feeding in Print Symbiont..........   3-16,I               3.4.2.2     Form/Stock Mismatch.....................   3-16 I               3.4.2.3     LAT Initialization Timing...............   3-16SI               3.4.2.4     Memory Leak in Modified Symbiont........   3-17AI               3.4.2.5     STS$V_INHIB_MSG in Return Status........   3-17rI               3.5   DCL Commands..................................   3-17eI               3.5.1     Changes and Enhancements..................   3-17RI               3.5.1.1     ANALYZE/ERROR_LOG/SUMMARY Command.......   3-17nI               3.5.1.2     MOUNT/UCS_SEQUENCE Command..............   3-17 I               3.5.2     Corrections...............................   3-18 I               3.5.2.1     ANALYZE/DISK_STRUCTURE/REPAIR Command...   3-18OI               3.5.2.2     SET ACCOUNTING/NEW_FILE Command.........   3-18NI               3.6   DECdtm Services in a DECnet/OSI Network.......   3-18VI               3.6.1     Problems and Restrictions.................   3-184I               3.6.1.1     Assigning SCSNODE Values................   3-19 <               3.7   DECevent Fault Management Support (AlphaI                     Only).........................................   3-21 I               3.7.1     Problems and Restrictions.................   3-21pI               3.7.1.1     Bit-to-Text Translation Support ........   3-21 I               3.7.1.2     Ctrl/C .................................   3-21 I               3.7.1.3     Log Files Not Purged Automatically......   3-21 I               3.7.1.4     Logical File Names......................   3-21 I               3.7.1.5     Page File Quota.........................   3-22kI               3.7.1.6     Unrecognized Error Log Messages.........   3-22fI               3.8   DECnet for OpenVMS Alpha (Phase IV) ..........   3-22oI               3.8.1     Problems and Restrictions ................   3-22t    I                                                                        ixt    e              E           3.9   DECnet for OpenVMS VAX (Phase IV) ............   3-23 E           3.9.1     Changes and Enhancements..................   3-23d6           3.9.1.1     DEFQA Now Can Be Configured withE                       SYS$MANAGER:NETCONFIG.COM ..............   3-23 E           3.9.2     Problems and Restrictions.................   3-23 5           3.9.2.1     DEFTA Cannot Be Configured witheE                       SYS$MANAGER:NETCONFIG.COM...............   3-23 E           3.10  DECnet/OSI for OpenVMS VAX (Phase V)..........   3-24dE           3.10.1    Changes and Enhancements..................   3-24d6           3.10.1.1    DEFQA Now Can Be Configured withE                       SYS$MANAGER:NET$CONFIGURE.COM...........   3-24 6           3.10.1.2    DEFTA Now Can Be Configured withE                       SYS$MANAGER:NET$CONFIGURE.COM...........   3-24rE           3.11  DECwindows Motif for OpenVMS .................   3-25 E           3.11.1    Changes and Enhancements..................   3-25 6           3.11.1.1    DECwindows Motif Version 1.1 forE                       OpenVMS.................................   3-25s9           3.11.1.2    NCSA Mosaic Browser: TCP/IP Support E                       Options.................................   3-25rE           3.11.2    Problems and Restrictions.................   3-25xE           3.11.2.1    Console Broadcasts Disabled.............   3-260E           3.11.2.2    System Files Purged During Startup......   3-26e7           3.11.2.3    Virtual Data Error Message (AlphaEE                       Only)...................................   3-26 :           3.11.2.4    World Wide Support Requires RemedialE                       Kit.....................................   3-26 2           3.11.2.5    DECwindows Motif Version 1.2E                       Compatibility Problem ..................   3-27 7           3.11.2.6    DECwindows Server Height or WidthiE                       Exceeding 32767 (VAX Only)..............   3-28 ;           3.11.2.7    SET DISPLAY Used to Create WSA Pseudo E                       Workstation Devices.....................   3-29_;           3.11.2.8    DECwindows Motif Start Session Dialog ;                       Box Not Displayed After Rebooting the E                       System (VAX Only).......................   3-30 E           3.12  Help Message Utility (MSGHLP) ................   3-30 E           3.12.1    Problems and Restrictions.................   3-30 E           3.12.1.1    User-Supplied Comments Are Not Preserved   3-30 E           3.13  InfoServer MADDRIVER..........................   3-31 E           3.13.1    Problems and Restrictions.................   3-31 =           3.13.1.1    Magnetic Tapes Are Not Supported (AlphaaE                       Only)...................................   3-31a           xn .  .              I               3.14  INITIALIZE ...................................   3-31 I               3.14.1    Problems and Restrictions.................   3-31 <               3.14.1.1    Recovery of Badly Initialized RootI                           Directory (Alpha Only)..................   3-31.I               3.15  Install Utility (INSTALL).....................   3-32II               3.15.1    Changes and Enhancements .................   3-32fI               3.15.1.1    Installing Images.......................   3-32dI               3.16  License Management Facility (LMF).............   3-33 I               3.16.1    Problems and Restrictions.................   3-33 I               3.16.1.1    PAKs on Alpha and VAX Systems...........   3-33cI               3.17  Monitoring Performance History (MPH)..........   3-34.I               3.18  Monitor Utility (MONITOR).....................   3-36.I               3.18.1    Changes and Enhancements..................   3-36.I               3.18.1.1    Disk Limit Increased....................   3-36 B               3.18.1.2    Display Header Changed From "VAX/VMS" ToI                           "OpenVMS" (VAX Only)....................   3-37rI               3.19  Mount Utility (MOUNT).........................   3-37 I               3.19.1    Problems and Restrictions.................   3-37 ;               3.19.1.1    ISO 9660 Support in Mixed-Version I                           VMScluster Systems......................   3-37 I               3.19.2    Corrections...............................   3-37 A               3.19.2.1    Noncompliant ISO 9660 CD-ROMs and MOUNTuI                           (VAX Only)..............................   3-37sI               3.20  Nonpaged Pool.................................   3-38.I               3.20.1    Problems and Restrictions.................   3-38.=               3.20.1.1    Prepopulation of Nonpaged Pool (VAXnI                           Only)...................................   3-38.I               3.20.2    Corrections...............................   3-38 I               3.20.2.1    Nonpaged Pool Deallocation..............   3-38 I               3.21  OPCOM.........................................   3-39.I               3.21.1    Problems and Restrictions.................   3-39.I               3.21.1.1    OPERATOR.LOG File.......................   3-39 I               3.22  POLYCENTER Software Installation Utility .....   3-39rI               3.22.1    Problems and Restrictions.................   3-39m;               3.22.1.1    Dependency Information Is Lost OnlI                           Product Upgrade.........................   3-40SI               3.22.1.2    PRODUCT Command ........................   3-40.=               3.22.1.3    Deleting Directories Created by theaI                           POLYCENTER Software Installation Utility   3-41DI               3.22.1.4    Inaccurate Disk Space Reporting.........   3-42.=               3.22.1.5    Installing an Earlier Version of an.I                           Installed Product.......................   3-42.      I                                                                        xi  1                 E           3.22.1.6    Product Removal Restrictions............   3-43.E           3.22.2    Documentation Changes and Corrections.....   3-43.>           3.22.2.1    POLYCENTER Software Installation UtilityE                       User's Guide............................   3-43 E           3.23  POLYCENTER Striping (VAX Only)................   3-43 E           3.23.1    Changes and Enhancements..................   3-43 <           3.23.1.1    StorageWorks RAID Software for OpenVMSE                       Replaces POLYCENTER Striping............   3-43 E           3.24  RMS Journaling................................   3-44 E           3.24.1    Problems and Restrictions.................   3-44 >           3.24.1.1    Remote Access of Recovery Unit JournaledE                       Files...................................   3-44 E           3.24.1.2    VFC Format Sequential Files ............   3-44 E           3.25  Security......................................   3-44 E           3.25.1    Changes and Enhancements..................   3-44 E           3.25.1.1    Auditing Events (VAX Only)..............   3-44rE           3.25.2    Corrections...............................   3-45hE           3.25.2.1    Intrusion Services......................   3-45mE           3.26  Shared Linkage Sections ......................   3-45nE           3.26.1    Problems and Restrictions (Alpha Only)....   3-45.E           3.27  SORT32 Work Files.............................   3-46sE           3.27.1    Changes and Enhancements..................   3-46 E           3.27.1.1    Files Now Have Directory Entries........   3-46-:           3.28  StorageWorks RAID Array 110 Subsystem (VAXE                 Only).........................................   3-47.E           3.28.1    Problems and Restrictions.................   3-47.E           3.28.1.1    SHOW DEVICE Does Not Display Capacity...   3-47.7           3.28.1.2    TURBOchannel Devices: Booting NotrE                       Supported ..............................   3-47 E           3.29  System Dump Analyzer (SDA) ...................   3-47lE           3.29.1    Problems and Restrictions.................   3-48 E           3.29.1.1    EXAMINE Command (VAX Only)..............   3-48CE           3.30  System Management Utility (SYSMAN)............   3-48oE           3.30.1    Changes and Enhancements..................   3-48 E           3.30.1.1    ALF Command.............................   3-48.E           3.30.1.2    Rights Identifiers......................   3-51 ;           3.30.1.3    SHUTDOWN NODE Command Qualifiers Have E                       Changed.................................   3-52-E           3.30.2    Problems and Restrictions.................   3-52 E           3.30.2.1    /CLUSTER Qualifier .....................   3-52.;           3.30.2.2    Clusterwide DISKQUOTA Commands (Alpha.E                       Only)...................................   3-53.E           3.31  System Time...................................   3-55.         xii. .  .              I               3.31.1    Changes and Enhancements..................   3-55 B               3.31.1.1    Watch Chip - Change in Time Range (AlphaI                           Only)...................................   3-55 I               3.31.2    Problems and Restrictions.................   3-56 @               3.31.2.1    Time of Day Register (TODR): Resetting<                           System Time After January 1st (VAXI                           Only)...................................   3-56 ;               3.32  Terminal Fallback Facility (TFF) (Alpha I                     Only).........................................   3-59 I               3.33  VAX 7000 Systems (VAX Only)...................   3-61 I               3.33.1    Problems and Restrictions.................   3-61 9               3.33.1.1    Dump Off System Disk (DOSD) Not.I                           Supported...............................   3-61 I               3.34  VMScluster Systems............................   3-61.I               3.34.1    Changes and Enhancements..................   3-61 I               3.34.1.1    SCSI VMScluster Systems.................   3-61eI               3.34.1.2    Concurrency Improvements ...............   3-62 I               3.34.1.3    FDDI Clusters (Alpha Only)..............   3-62.I               3.34.2    Problems and Restrictions.................   3-62PI               3.34.2.1    KFESA/KFESB Controller Restrictions.....   3-62.A               3.34.2.2    Booting Two Computers That Share a SCSI.I                           Bus (Alpha Only)........................   3-63.8               3.34.2.3    System Startup in a VMSclusterI                           Environment (Alpha Only)................   3-63 I               3.34.3    Corrections...............................   3-64 /               3.34.3.1    REMOVE_NODE Option in.I                           SYS$SYSTEM:SHUTDOWN.COM.................   3-64 I               3.35  VMSKITBLD.COM Procedure.......................   3-641I               3.35.1    Changes and Enhancements .................   3-65t@               3.35.1.1    VMSKITBLD.COM Not Supported on OpenVMSI                           Alpha Version 6.2 (Alpha Only)..........   3-65UI               3.35.2    Documentation Changes and Corrections.....   3-65.:               3.35.2.1    OpenVMS System Manager's Manual:I                           Essentials (Alpha Only).................   3-65aI               3.36  Volume Shadowing..............................   3-65TI               3.36.1    Changes and Enhancements..................   3-65.I               3.36.1.1    Mixed-Architecture VMScluster Changes...   3-66yI               3.36.1.2    New Bugcheck: SHADZEROMBR ..............   3-66.I               3.36.1.3    Phase I Retirement (VAX Only)...........   3-67 I               3.36.1.4    Timer-Based Polling.....................   3-67-I               3.36.1.5    SCSI Shadowing Support (VAX Only) ......   3-67         I                                                                      xiii. .                 E           3.36.2    Problems and Restrictions.................   3-67.E           3.36.2.1    KDM70 Devices ..........................   3-67R8           3.36.2.2    DISMOUNT/CLUSTER Command Can CauseE                       Clusterwide Hang........................   3-68 7           3.36.2.3    RZ57 Support Restricted in Shadow E                       Sets....................................   3-68.E           3.36.3    Documentation Changes and Corrections.....   3-68.E           3.36.3.1    Volume Shadowing for OpenVMS Manual.....   3-68n        4  Programming Release Notes  E           4.1   Batch and Print Queues........................    4-1nE           4.1.1     Problems and Restrictions.................    4-1 E           4.1.1.1     Terminating Executing Batch Jobs........    4-1 E           4.1.2     Corrections...............................    4-2CE           4.1.2.1     Accessing Batch Log Files...............    4-3.E           4.1.2.2     Displaying Open Batch Jobs..............    4-3CE           4.1.2.3     $GETQUI Error Message...................    4-3 E           4.1.2.4     Log File Defaults for Batch Jobs........    4-3F9           4.1.2.5     Restarting FORTRAN Carriage ControloE                       Files...................................    4-4 2           4.1.2.6     Symbiont BADLOGIC Dump AfterE                       STOP/QUEUE/RESET and START/QUEUE........    4-437           4.1.2.7     TASK_STATUS Requests to the Queue.E                       Manager.................................    4-4ME           4.2   Debugger......................................    4-5aE           4.2.1     Changes and Enhancements..................    4-5sE           4.2.1.1     Performance Improvements................    4-5iE           4.2.1.2     VMSDEBUG.DAT File.......................    4-5uE           4.2.2     Problems and Restrictions.................    4-6RE           4.2.2.1     Behavior After Stack Corruption ........    4-6 E           4.2.2.2     CONNECT Command.........................    4-7 E           4.2.2.3     Detached Processes .....................    4-7.E           4.2.2.4     SET TASK/ACTIVE Command.................    4-7 E           4.2.2.5     SPAWN/NOWAIT Command....................    4-7 <           4.2.2.6     System Service Interception and SharedE                       Linkage Images (Alpha Only).............    4-8.E           4.2.2.7     DEBUG.EXE Image (VAX Only)..............    4-8.;           4.2.2.8     STEP/OVER Steps into Fortran Run-Time.E                       Library Routines (VAX Only).............    4-9mE           4.2.2.9     Watchpoint Support......................   4-10_9           4.2.2.10    CALL and SHOW CALLS Commands (Alpha E                       Only)...................................   4-10          xivn .  .              I               4.2.2.11    DECwindows Motif Interface..............   4-11 I               4.2.2.12    EVALUATE Command (Alpha Only)...........   4-13nI               4.2.2.13    EXAMINE LABEL[n] Command (Alpha Only)...   4-13wI               4.2.2.14    Kept Debugger...........................   4-13.>               4.2.2.15    SET BREAK/UNALIGNED_DATA Command and<                           Related System Service Call (AlphaI                           Only)...................................   4-15.?               4.2.2.16    Complex Variables in Fortran ProgramsaI                           (Alpha Only)............................   4-15T<               4.2.2.17    Concealed Rooted-Directory LogicalI                           Names...................................   4-16.I               4.2.2.18    DEPOSIT/TYPE Command with C Programs....   4-16.I               4.2.2.19    $HIBER Call ............................   4-16.I               4.2.2.20    Inlined Routines (Alpha Only)...........   4-17.>               4.2.2.21    Null Frame Procedures and SHOW CALLSI                           (Alpha Only)............................   4-17 <               4.2.2.22    SHOW BREAK and SHOW TRACE CommandsI                           (Alpha Only)............................   4-17 >               4.2.2.23    STEP/INTO Command and User ExceptionI                           Handlers (Alpha Only)...................   4-18a?               4.2.2.24    STEP/OVER Command Error with One-LineoI                           Program Loops (Alpha Only) .............   4-18.I               4.2.2.25    Translated Images (Alpha Only)..........   4-18.I               4.2.2.26    Vector Support (VAX Only)...............   4-19 I               4.2.3     Corrections...............................   4-19 I               4.2.3.1     Breakpoints (Alpha Only)................   4-19 ?               4.2.3.2     Breakpoints and Display of Source and I                           Scope...................................   4-19YI               4.2.3.3     COBOL: STEP and GO .....................   4-20 I               4.2.3.4     Communications Pane Sizing..............   4-20.I               4.2.3.5     DEBUG.EXE Image (Alpha Only)............   4-20.I               4.2.3.6     Edit Save Function......................   4-20.I               4.2.3.7     EVALUATE Command........................   4-20 @               4.2.3.8     EXAMINE Command on SCAN Tree VariablesI                           (VAX Only) .............................   4-20 I               4.2.3.9     Hebrew Command View Messages............   4-21 I               4.2.3.10    Include Files in a Text Library.........   4-21 I               4.2.3.11    Monitor View Display of Long Strings....   4-21tI               4.2.3.12    Multidimensional Arrays.................   4-21 I               4.2.3.13    PL/I Controlled Variables...............   4-21.I               4.2.3.14    Process Dump Files......................   4-21eI               4.2.3.15    Radixes for Monitored Items.............   4-212I               4.2.3.16    Records with the Same Symbol Name.......   4-22     I                                                                        xvn s  r              E           4.2.3.17    RERUN/SAVE Command......................   4-22 E           4.2.3.18    SET RADIX Command.......................   4-22 E           4.2.3.19    SET SOURCE Command (VAX Only)...........   4-22 >           4.2.3.20    User-Written System Service Calls (AlphaE                       Only)...................................   4-22 E           4.2.3.21    Watchpoint Reporting ...................   4-222E           4.2.3.22    Watchpoint Setting on Bit Fields........   4-222E           4.3   DEC C++.......................................   4-232E           4.3.1     Problems and Restrictions.................   4-233>           4.3.1.1     SYS$LIB_C.TLB Structures Need PrototypesE                       (Alpha Only)............................   4-23 E           4.4   DEC C++ Class Library.........................   4-23 E           4.4.1     Changes and Enhancements..................   4-24 E           4.4.1.1     Object Library Format...................   4-24.E           4.4.2     Corrections...............................   4-24iE           4.5   DEC C Run-Time Library .......................   4-26lE           4.5.1     Changes and Enhancements..................   4-26.:           4.5.1.1     Floating-Point Values Now Conform toE                       IEEE Standard ..........................   4-26 2           4.5.1.2     Getenv Function Now PerformsE                       Case-Insensitive Lookup.................   4-26 E           4.5.1.3     Internationalization Support ...........   4-26 9           4.5.1.4     Math Functions Conform to XPG4 (VAX.E                       Only)...................................   4-27.4           4.5.1.5     Open Routines Now Validate RMSE                       Options.................................   4-27tE           4.5.1.6     Setvbuf Function .......................   4-27h8           4.5.1.7     Sleep Function Now Returns UnsleptE                       Seconds.................................   4-28 :           4.5.1.8     Wildcards No Longer Accepted by statE                       Function................................   4-28 <           4.5.1.9     Writing to Pipes Now Conforms to POSIXE                       Standards...............................   4-28.E           4.5.2     Problems and Restrictions.................   4-28 =           4.5.2.1     SYS_ERRLIST and SYS_NERR Symbols (Alpha.E                       Only)...................................   4-29.E           4.5.2.2     DECC$SHR.EXE (VAX Only).................   4-29I8           4.5.2.3     Internationalization CompatibilityE                       Problem with DECwindows Motif...........   4-29gE           4.5.2.4     Regular Expressions.....................   4-30 <           4.5.2.5     Simultaneously Opened Files Limited toE                       256.....................................   4-30            xvi. .  .              I               4.5.3     Corrections ..............................   4-30.<               4.5.3.1     Maximum Record Size Is Now Set forI                           Stream Files ...........................   4-30.I               4.5.3.2     Undefined Record Formats ...............   4-30sI               4.5.4     Programming Tips..........................   4-30FI               4.5.4.1     RMS-11 Stream Format Files..............   4-31 ?               4.6   DECmigrate: Translated Image Support (AlphaeI                     Only).........................................   4-31eI               4.7   DECthreads....................................   4-32.I               4.7.1     Problems and Restrictions.................   4-32.I               4.7.1.1     Dynamic Image-Activation ...............   4-32iI               4.7.1.2     Exit Handler Routine ...................   4-32i?               4.7.1.3     Routines Can Terminate Process (AlphacI                           Only)...................................   4-33eI               4.8   DECTPU for DECwindows Motif...................   4-33.I               4.8.1     Problems and Restrictions.................   4-33 ?               4.8.1.1     Small Display Monitors and DECwindows I                           Motif Applications......................   4-33uI               4.9   DECwindows Motif Transport....................   4-34EI               4.9.1     Corrections...............................   4-34.I               4.9.1.1     User-Written Modifications..............   4-34lI               4.10  Delta/XDelta Debugger.........................   4-35.I               4.10.1    Changes and Enhancements..................   4-35rI               4.10.1.1    Image Activation (Alpha Only) ..........   4-353I               4.10.2    Documentation Changes and Corrections.....   4-36 I               4.10.2.1    OpenVMS Delta/XDelta Debugger Manual....   4-36 I               4.11  Device Support on OpenVMS Alpha Systems.......   4-36 I               4.11.1    Changes and Enhancements (Version 6.2)....   4-362I               4.11.1.1    Driver Compatibility for Version 6.2....   4-36iA               4.11.1.2    Improving Performance of Device Drivers I                           Written in C............................   4-37 I               4.11.1.3    PCI DMA Window Changes..................   4-38cI               4.11.1.4    Device IPL Setup for Drivers............   4-41oI               4.11.1.5    SCSI Port and Class Driver Changes......   4-41c:               4.11.1.5.1   OpenVMS Alpha SCSI Class DriverI                            Changes................................   4-41r<               4.11.1.5.2   OpenVMS Alpha SCSI Tagged CommandI                            Queuing................................   4-43 B               4.11.1.5.3   Enhanced SCSI Interface to IO$_DIAGNOSEI                            Function...............................   4-43.I               4.11.1.5.4   GKDRIVER Command Queuing Enhancement...   4-50s        I                                                                      xviil C  c              E           4.11.2    Problems and Restrictions (Version 6.2)...   4-51 =           4.11.2.1    Hardware Support for Multiple-Host SCSI E                       VMScluster Systems......................   4-51 =           4.11.2.1.1   Supported Hardware for SCSI VMScluster4E                        Systems................................   4-514=           4.11.2.1.2   Minimum SCSI Firmware Requirements for.E                        SCSI VMSclusters.......................   4-53.3           4.11.2.1.3   Firmware Revision Level 442D.E                        Requirements...........................   4-54.E           4.11.2.1.4   442D Firmware Installation Procedure...   4-54n=           4.11.2.1.5   Documentation Correction for Supported.E                        Hardware for SCSI VMScluster Systems...   4-54nE           4.11.2.2    Unsupported Ethernet ISA Bus Adapters...   4-54.E           4.11.2.3    SCSI Port and Class Drivers ............   4-55 E           4.11.2.3.1   Mounting Third-Party SCSI Disks........   4-55.=           4.11.2.3.2   Fatal Drive Errors for TZ86, TZ87, and.E                        TZ88 SCSI Tape Drives..................   4-55 E           4.11.2.3.3   Add-On SCSI Adapters...................   4-55 8           4.11.2.3.4   HSZ40 and Transportable SCSI DiskE                        Shadow-Set Members.....................   4-56 E           4.11.2.3.5   KZTSA Adapter Restriction..............   4-57.E           4.11.2.3.6   KZPSA SCSI Adapter Bus Resets..........   4-57t<           4.11.2.3.7   SCSI Disk I/O Performance Degradation6                        for KZMSA XMI and Adaptec 1742AE                        Adapters...............................   4-58yE           4.11.3    Changes and Enhancements (Version 6.1)....   4-59.E           4.11.3.1    New Device Driver Interface.............   4-59.E           4.11.3.2    Step 1 Drivers Are Obsolete.............   4-60nE           4.11.3.3    OpenVMS Alpha System-Code Debugger .....   4-60iE           4.11.4    Problems and Restrictions (Version 6.1)...   4-61.:           4.11.4.1    C Structure Member Names: Passing toE                       Nested C Macros.........................   4-61 E           4.11.4.2    OpenVMS Alpha System-Code Debugger......   4-62VE           4.12  Device Support on OpenVMS VAX Systems ........   4-63oE           4.12.1    Documentation Changes and Corrections.....   4-63 E           4.12.1.1    OpenVMS VAX Device Support Manual.......   4-632E           4.12.1.1.1   Linking a Device Driver................   4-63.7           4.12.1.1.2   Device-Register I/O Space: Usage.E                        Restrictions ..........................   4-64 :           4.12.1.2    OpenVMS VAX Device Support ReferenceE                       Manual..................................   4-64 -           4.12.1.2.1   COM$DRVDEALMEM RoutinelE                        Synchronization........................   4-64.    	     xviii. .                 I               4.12.1.2.2   CRB Data Structure ....................   4-64YI               4.12.1.2.3   SCDRP Data Structure SCSI Flags........   4-65OI               4.12.1.2.4   SPI$CONNECT Macro .....................   4-65 6               4.12.1.2.5   SPI$GET_CONNECTION_CHAR andI                            SPI$SET_CONNECTION_CHAR Macros.........   4-66 I               4.12.1.2.6   $EQULST Macro .........................   4-66 I               4.13  I/O User .....................................   4-661I               4.13.1    Problems and Restrictions.................   4-67(=               4.13.1.1    I/O Write Operations Interrupted byeI                           System Failure .........................   4-67hI               4.13.2    Documentation Changes and Corrections.....   4-68 I               4.13.2.1    OpenVMS I/O User's Reference Manual.....   4-68 I               4.14  Librarian Utility (LIBRARIAN).................   4-69 I               4.14.1    Problems and Restrictions.................   4-69 >               4.14.1.1    PGFLQUOTA Should Exceed 23000 (AlphaI                           Only)...................................   4-70 I               4.15  Linker Utility................................   4-70 I               4.15.1    Problems and Restrictions ................   4-70.@               4.15.1.1    Fixup Information Not Generated (AlphaI                           Only)...................................   4-70 >               4.15.1.2    Shareable Image Psects Pointed to byI                           Symbol Definitions (Alpha Only).........   4-71 I               4.15.2    Corrections...............................   4-716I               4.15.2.1    /DEBUG Qualifier........................   4-711I               4.15.3    Documentation Changes and Corrections.....   4-72RI               4.15.3.1    OpenVMS Linker Utility Manual...........   4-72.I               4.16  Lock Manager .................................   4-72 I               4.16.1    Changes and Enhancements..................   4-72-I               4.16.1.1    LCKMGR Spin Lock (Alpha Only)...........   4-72 I               4.17  LTDRIVER......................................   4-73 I               4.17.1    Problems and Restrictions.................   4-73 8               4.17.1.1    CANCEL SELECTIVE Cannot CancelI                           IO$_TTY_PORT Functions..................   4-73F>               4.18  MACRO-32 Compiler for OpenVMS Alpha (AlphaI                     Only).........................................   4-73 I               4.18.1    Problems and Restrictions ................   4-73EI               4.18.1.1    .ASCID Directive........................   4-73 I               4.18.1.2    .GLOBAL_LABEL Directive.................   4-74.I               4.18.1.3    Floating-Point Return Values in R0......   4-74.>               4.18.1.4    INSV Instructions Negate GranularityI                           Preservation............................   4-74.I               4.18.1.5    .JSB_ENTRY Directive....................   4-74.      I                                                                       xix  R                 7           4.18.1.6    Floating-Point and Packed-Decimal E                       Instruction Arguments...................   4-75 E           4.18.1.7    Multiple Object Files Compilation ......   4-75 E           4.18.2    Documentation Changes and Corrections.....   4-75 9           4.18.2.1    Migrating to an OpenVMS AXP System:.E                       Porting VAX MACRO Code..................   4-75 E           4.18.2.1.1   Entry Point Declarations...............   4-75 E           4.18.2.1.2   BUGx Instruction Is Not Supported......   4-76 E           4.18.2.1.3   /FLAGGING=INSTRUCTIONS Qualifier.......   4-76 >           4.18.2.1.4   TRACEBACK and DEBUG Options RestrictionE                        Removed................................   4-77 E           4.19  Mathematics (MTH$) Run-Time Library ..........   4-77 E           4.19.1    Problems and Restrictions.................   4-77 7           4.19.1.1    Linking Images to Run on PrevioussE                       OpenVMS VAX Versions (VAX Only).........   4-77A9           4.19.1.2    Compatibility Between VAX and Alpha.E                       Mathematics Libraries (Alpha Only)......   4-78 9           4.20  Migration to OpenVMS Alpha Systems (Alpha1E                 Only).........................................   4-79 E           4.20.1    Documentation Changes and Corrections.....   4-79 1           4.20.1.1    Migrating to an OpenVMS AXP.7                       System: Recompiling and RelinkingFE                       Applications............................   4-79.E           4.21  POLYCENTER Software Installation Utility .....   4-79oE           4.21.1    Problems and Restrictions.................   4-80.E           4.21.1.1    Account Removal Problem ................   4-80rE           4.21.1.2    Alphanumeric Options Not Supported......   4-80.2           4.21.1.3    Alternate File Placement NotE                       Supported...............................   4-80 E           4.21.1.4    Command Procedure Behavior..............   4-81aE           4.21.1.5    Conflict Error Reporting................   4-81HE           4.21.1.6    Error Reporting.........................   4-81)E           4.21.1.7    File Generation Restrictions............   4-81TE           4.21.1.8    File Statement Generation Limit.........   4-82 E           4.21.1.9    Information Statement Problem...........   4-82oE           4.21.1.10   Multiple Execute Remove Statements .....   4-83p3           4.21.1.11   Multiple Operating Scopes Not5E                       Supported...............................   4-83.E           4.21.1.12   Network Object Statement Problem........   4-83 E           4.21.1.13   Package Operation Constraints...........   4-83 E           4.21.1.14   Partial Kit Restrictions................   4-84 E           4.21.1.15   Rights Identifier Problem ..............   4-84            xx p  .              :               4.21.1.16   "Uses" Clause File SpecificationI                           Restriction ............................   4-84nI               4.21.2    Documentation Changes and Corrections.....   4-85.I               4.21.2.1    DCL Help: PRODUCT PACKAGE Command.......   4-85SB               4.21.2.2    POLYCENTER Software Installation UtilityI                           User's Guide............................   4-85 B               4.21.2.3    POLYCENTER Software Installation UtilityI                           Developer's Guide.......................   4-85 I               4.21.2.3.1   File Statement.........................   4-85 I               4.21.2.3.2   Scope Statement........................   4-85 I               4.22  Run-Time Libraries............................   4-86 I               4.22.1    Problems and Restrictions.................   4-86 <               4.22.1.1    Run-Time Libraries Not Included inI                           OpenVMS Alpha Systems (Alpha Only)......   4-86 I               4.23  Screen Management (SMG$) Facility.............   4-87 I               4.23.1    Changes and Enhancements..................   4-87 I               4.23.1.1    VT500 Series Terminal Support ..........   4-87 I               4.24  Security .....................................   4-89.I               4.24.1    Changes and Enhancements..................   4-894I               4.24.1.1    SYS$EXAMPLES:HASH_PASSWORD.MAR .........   4-90 A               4.25  STARLET Data Structures and Definitions for C I                     Programmers (Alpha Only)......................   4-90 I               4.26  System Services ..............................   4-92 I               4.26.1    Changes and Enhancements..................   4-93 A               4.26.1.1    $INIT_VOL Has New INIT$_HOMEBLOCKS Item I                           Code....................................   4-93.?               4.26.1.2    $LCKPAG and $LKWSET Limits Are Set by I                           WSQUOTA.................................   4-93 ?               4.26.1.3    $SNDJBC Has New SJC$_DISPLAY_USERNAME.I                           Item Code...............................   4-94 I               4.26.1.4    $SYNCH and Wait Form Services...........   4-94oI               4.26.2    Problems and Restrictions.................   4-94-I               4.26.2.1    $SNDJBC Batch Queue Limitation..........   4-94nB               4.26.2.2    $SUSPND Behaves Incorrectly in a ClusterI                           Environment ............................   4-95.<               4.26.2.3    $FORMAT_AUDIT Width Argument WorksI                           Inconsistently .........................   4-95.I               4.26.3    Documentation Changes and Corrections.....   4-95.I               4.26.3.1    $CHKPRO System Service..................   4-96 I               4.26.3.2    $TSTCLUEVT System Service...............   4-96 I               4.26.3.3    $CREATE_USER_PROFILE System Service.....   4-96.I               4.26.3.4    $GETQUI System Service..................   4-97cI               4.27  System Time Operation ........................   4-97N    I                                                                       xxi.    2              E           4.27.1    Documentation Changes and Corrections.....   4-97 E           4.27.1.1    OpenVMS Programming Concepts Manual.....   4-97 9           4.28  Translated Image Environment (TIE) (Alpha E                 Only).........................................   4-99 E           4.28.1    Problems and Restrictions.................  4-102 E           4.28.1.1    Condition Handler Restriction...........  4-102.E           4.28.1.2    Exception Handler Restrictions..........  4-102SE           4.28.1.3    Floating-Point Restrictions.............  4-102nE           4.28.1.4    Interoperability Restrictions...........  4-104d/           4.28.1.5    VAX C: Translated Program E                       Restrictions............................  4-105 E           4.29  Translated Image Support (Alpha Only).........  4-105.E           4.30  Translated Run-Time Libraries (Alpha Only)....  4-110 E           4.30.1    Problems and Restrictions.................  4-112.<           4.30.1.1    CRF$FREE_VM and CRF$GET_VM: TranslatedE                       Callers Problem ........................  4-112.8           4.31  Translated VAX C Run-Time Library (AlphaE                 Only).........................................  4-112iE           4.31.1    Problems and Restrictions.................  4-113SE           4.31.1.1    Functional Restrictions.................  4-113eE           4.31.1.2    Interoperability Restrictions...........  4-113.E           4.32  Translated VAX COBOL Programs (Alpha Only)....  4-115.E           4.32.1    Problems and Restrictions.................  4-115bE           4.33  VAX MACRO (VAX Only)..........................  4-115 E           4.33.1    Documentation Changes and Corrections ....  4-115.=           4.33.1.1    VAX MACRO and Instruction Set Reference E                       Manual..................................  4-115 E           4.33.1.1.1   .ASCIZ Macro Directive.................  4-115 E           4.33.1.1.2   General Register Addressing............  4-115 E           4.33.1.1.3   VAX Instruction CASE...................  4-116 E           4.34  X/Open Transport Interface (XTI)..............  4-116 E           4.34.1    Changes and Enhancements..................  4-116 E           4.34.2    Problems and Restrictions.................  4-118   #     A  ISA Bus Support (Alpha Only).  E           A.1   OpenVMS ISA Bus Configuration.................    A-2nE           A.2   Adding a Device...............................    A-2D9           A.2.1     Entering Interrupt Request Line (IRQ)0E                     Assignments...............................    A-3 0           A.2.2     Configuring a Device with anE                     ISA_CONFIG.DAT File.......................    A-5nE           A.2.3     Configuring an ISA Device with SYSMAN.....    A-9          xxii                   I               A.3   ISA Bus Device Driver Routines................   A-12.I               A.4   Determining an Available ISA IRQ..............   A-15.I               A.5   Troubleshooting...............................   A-17.?               A.6   System Board Resources for AlphaStation 200 I                     and 400 Series Systems........................   A-18 I               A.7   Sample ISA_CONFIG.DAT File....................   A-19   8         B  Remedial Kits Included in OpenVMS Version 6.2  A               B.1   Remedial Kits Included in OpenVMS VAX Version I                     6.2...........................................    B-1 ;               B.2   Remedial Kits Included in OpenVMS Alpha4I                     Version 6.2...................................    B-4   <         C  Remedial Kits Not Included in OpenVMS Version 6.2  =               C.1   Remedial Kits Not Included in OpenVMS VAXGI                     Version 6.2...................................    C-141               C.1.1     Local Area VMScluster KituI                         (VAXLAVC01_061)...........................    C-1 ?               C.2   Remedial Kits Not Included in OpenVMS Alpha I                     Version 6.2...................................    C-2 I               C.2.1     Trace Facility (AXPTRAC01_061)............    C-2   :         D  Layered Product Support for OpenVMS Version 6.2    
         Indexd             Examples  I               4-1       OpenVMS SCSI-2 Diagnose Buffer (S2DGB)....   4-445           Figures2  I               3-1       Transaction Group.........................   3-20M                I                                                                     xxiii2                   
     Tables  E           1-1       Error-Free Microcode Revision Levels .....   1-21m  >           1-2       Commands for Updating Microcode in CertainE                     DSSI Disk Devices.........................   1-23o  7           2-1       Formats of the /FIELD Qualifier for E                     SORT/MERGE Specification Files............   2-10   E           3-1       TFF Character Fallback Tables.............   3-60M  5           4-1       Debugger Commands Disabled in the E                     DECwindows Motif Interface................   4-11   <           4-2       Support for Translated Images on OpenVMSE                     Alpha Versions............................   4-31   E           4-3       Obsolete SPI Interface Macros.............   4-42a  :           4-4       Supported Hardware for SCSI VMSclusterE                     Systems...................................   4-512  0           4-5       Revision Level 442D FirmwareE                     Compatibility.............................   4-54   E           4-6       Supported Terminal Devices................   4-69A  >           4-7       Run-Time Libraries Not Included on OpenVMSE                     Alpha Systems.............................   4-871  E           4-8       Predefined Output Date Formats............   4-98   E           4-9       Predefined Output Time Formats............   4-99   E           4-10      Interoperability Documentation............  4-100b  E           4-11      Run-Time Library Logical Names............  4-112t  E           A-1       Available ISA IRQ Lines...................    A-7.  <           D-1       Digital Layered Products Compatible withE                     OpenVMS VAX Version 6.2...................    D-3o  <           D-2       Digital Layered Products Compatible withE                     OpenVMS Alpha Version 6.2.................   D-28p  <           D-3       Digital Layered Products Compatible withE                     OpenVMS VAX Version 6.2 After May 1995....   D-541  <           D-4       Digital Layered Products Compatible with7                     OpenVMS Alpha Version 6.2 After May E                     1995......................................   D-55        xxiv .  .                        I         _________________________________________________________________   I                                                                   Preface                Intended Audience2  F               This manual is intended for all OpenVMS operating systemI               users. Read this manual before you install, upgrade, or use12               Version 6.2 of the operating system.           Document Structure  I               This manual contains the following chapters and appendixes:H  A               o  Chapter 1 contains release notes that pertain to.H                  installing and upgrading the OpenVMS operating systems,9                  as well as hardware-related information.   D               o  Chapter 2 contains release notes that relate to the=                  general use of the OpenVMS operating system.   D               o  Chapter 3 contains release notes specific to system(                  management information.  @               o  Chapter 4 contains release notes that relate to2                  programming on an OpenVMS system.  H               o  Appendix A contains information about Industry StandardH                  Architecture (ISA) I/O bus support for Alpha platforms.  D               o  Appendix B lists remedial kits that are included in%                  OpenVMS Version 6.2.7  I               o  Appendix C describes remedial kits that are not included (                  in OpenVMS Version 6.2.  B               o  Appendix D contains tables that summarize layeredI                  product support for OpenVMS Version 6.2. The tables also.E                  identify which layered products work with DECnet/OSIg)                  synonyms and full names.   I                                                                       xxv  o  c              >           This manual contains release notes introduced in theB           current release and notes from previous OpenVMS versionsD           that still apply to the new release. Margin notes for eachC           release note indicate the version of origin (for example,            V6.1).  :           Notes from previous releases are published when:  B           o  The release note has not been documented in any otherE              manual in the OpenVMS documentation set, and the note is               still pertinent..  B           o  The release note may be pertinent in multiple-version%              OpenVMS cluster systems.7       Associated Information  B           For a list of additional documents that are available inB           support of this version of the OpenVMS operating system,9           refer to the Overview of OpenVMS Documentation..  C           The Alpha Architecture Reference Manual mentioned in this C           document is published by Digital Press under order number.           EY-L520E-DP.       Conventions.  ?           The name of the OpenVMS AXP operating system has been.A           changed to OpenVMS Alpha. Any references to OpenVMS AXPt<           or AXP are synonymous with OpenVMS Alpha or Alpha.  >           In this manual, every use of OpenVMS Alpha means theB           OpenVMS Alpha operating system, every use of OpenVMS VAX?           means the OpenVMS VAX operating system, and every use A           of OpenVMS means both the OpenVMS VAX and OpenVMS Alpha            operating systems.  D           The following conventions are used to identify information3           specific to OpenVMS Alpha or OpenVMS VAX:   @           In this manual, every use of DECwindows and DECwindows@           Motif refers to DECwindows Motif for OpenVMS software.           xxvi 8  1              E               The following conventions are also used in this manual:e  G               Ctrl/x           A sequence such as Ctrl/x indicates that.G                                you press the key labeled Ctrl while youpE                                press another key or a pointing devicel&                                button.  F               PF1 x            A sequence such as PF1 x indicates thatG                                you must first press and release the PF1MI                                key, then press and release another key orR8                                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 followingt-                                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.b  I                                o  Additional parameters, values, or other =                                   information can be entered.   D               .                Vertical ellipsis points indicate theD               .                omission of items from a code exampleG               .                or command format; the items are omittedeD                                because they are not important to the5                                topic being discussed.r  >               ( )              In command format descriptions,G                                parentheses indicate that, if you choose I                                more than one option, you must enclose then6                                choices in parentheses.          J                                                                      xxvii t  e                C           [ ]              In command format descriptions, brackets.>                            indicate optional elements. You canC                            choose one, none, or all of the options..B                            (Brackets are not optional, however, in?                            the syntax of a directory name in anr?                            OpenVMS file specification or in the A                            syntax of a substring specification in 4                            an assignment statement.)  A           { }              In command format descriptions, bracescE                            surround a required choice of options; you A                            must choose one of the options listed.r  D           boldface text    Boldface text represents the introductionD                            of a new term or the name of an argument,A                            an attribute, or a reason (user actiond5                            that triggers a callback).3  B                            Boldface text is also used to show user>                            input in Bookreader versions of the"                            manual.  ;           italic text      Italic text emphasizes importantbD                            information and indicates complete titles>                            of manuals and variables. VariablesD                            include information that varies in system?                            messages (Internal error number), in A                            command lines (/PRODUCER=name), and in D                            command parameters in text (where device-@                            name contains up to five alphanumeric'                            characters).h  B           UPPERCASE TEXT   Uppercase text indicates a command, theD                            name of a routine, the name of a file, orC                            the abbreviation for a system privilege.   C           -                A hyphen in code examples indicates that B                            additional arguments to the request are=                            provided on the line that follows.   @           numbers          All numbers in text are assumed to beE                            decimal unless otherwise noted. Nondecimal.A                            radixes-binary, octal, hexadecimal-aree0                            explicitly indicated.  
     xxviii .  .                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,9B                                syntax summaries, and references toE                                variables or identifiers introduced inC*                                an example.                                                                          H                                                                     xxix .  .                    I                                                                         1.I         _________________________________________________________________   I                 OpenVMS Installation, Upgrade, and Hardware Release Notes     ?               This chapter contains information that applies to4G               installations and upgrades of the OpenVMS VAX and OpenVMS C               Alpha operating systems. It also provides information.+               specific to certain hardware.   D               The installation and upgrade notes in this chapter are6               organized into the following categories:  F               o  Installation and upgrade notes common to both VAX and0                  Alpha systems (see Section 1.1)  C               o  Alpha specific installation and upgrade notes (see.                  Section 1.3)   A               o  VAX specific installation and upgrade notes (see                   Section 1.2)   @               Hardware and firmware notes follow the upgrade and$               installation sections.  H         1.1 Installation and Upgrade Information Common to VAX and Alpha  C               The following notes document installation and upgrade I               information common to both platforms. For more VAX specificoB               installation and upgrade notes, see Section 1.2. For?               additional Alpha specific notes, see Section 1.3.l  &         1.1.1 Changes and Enhancements  F               This section describes information related to installingE               or upgrading the OpenVMS VAX or OpenVMS Alpha operating                system.r        I                                                                       1-1m i  r      =     OpenVMS Installation, Upgrade, and Hardware Release Notes.D     1.1 Installation and Upgrade Information Common to VAX and Alpha    0     1.1.1.1 Software Product Descriptions (SPDs)  D     V6.2  Printed copies of the Software Product Descriptions (SPDs)E           are no longer provided. However, the following SPDs are nowo5           available on the OpenVMS Version 6.2 media:b  D           o  OpenVMS Operating System for VAX and Alpha, Version 6.2  2           o  OpenVMS Cluster Software, Version 6.2  :           o  DECnet for OpenVMS VAX and Alpha, Version 6.2  4           o  RMS Journaling for OpenVMS, Version 6.2  6           o  Volume Shadowing for OpenVMS, Version 6.2  8           Customers who receive the operating system andA           documentation on CD-ROM can consult the OpenVMS Versionl@           6.2 CD-ROM User's Guide for complete information about?           locating and printing the SPDs. VAX users who receive/C           their distribution kit on other media should refer to the1E           OpenVMS VAX Version 6.2 Upgrade and Installation Manual for2E           information about how to locate and access the SPD files ons           their kit.  7     1.1.1.2 Using ConDIST to Update InfoServer Software.  D     V6.1  You can use the Digital Consolidated Software DistributionC           (ConDIST) to update InfoServer software. After you log inI@           to the InfoServer system, perform the following steps:  C           1. Insert the disc containing the [INFOSERVxxx] directory D              tree in a compact disc drive attached to the InfoServer              system.  >           2. At the InfoServer> prompt, enter a command in the;              following format, where n is the drive number:s  E              o  On the InfoServer 100 or InfoServer 150 system, enterA2                 a command in the following format:  "                 UPDATE SYSTEM DKn:  E              o  On the InfoServer 1000 system, enter a command in the !                 following format:e  (                 UPDATE SYSTEM DKn: FLASH       1-2            I                 OpenVMS Installation, Upgrade, and Hardware Release NotesiH         1.1 Installation and Upgrade Information Common to VAX and Alpha    C                  These commands move the InfoServer software to the.G                  internal read/write device. The next time you boot thedF                  InfoServer system, it runs the updated software. NoteI                  that you can also boot the server from the ConDIST disc.S  '         1.1.2 Problems and Restrictionsl  E               This section contains upgrade and installation problems.D               and restrictions that are common to both VAX and Alpha                operating systems.  +         1.1.2.1 DECnet Product Requirements.  F         V6.2  On OpenVMS VAX systems, if you currently run DECnet/OSI,D               the OpenVMS VAX Version 6.2 kit detects this and givesD               you the option to retain those files. If you prefer toG               use the Phase IV code base, you have the option to do so.nF               However, you cannot use DECnet over TCP/IP if you choose               that option. f  B               On OpenVMS Alpha systems, if DECnet/OSI is currentlyH               installed, the DECnet/OSI files are automatically retainedF               during an upgrade. If you prefer to use DECnet Phase IV,(               you must do the following:  C               1. Ensure that the DECnet Phase IV option is selected D                  when you upgrade to OpenVMS Alpha Version 6.2. (YouH                  can repeat the upgrade procedure to select DECnet Phase                  IV later.)   H               2. After upgrading and booting the upgrade system, execute<                  the following command to remove DECnet/OSI:  -                  $ PRODUCT REMOVE DECNET_OSI u  C               If you want to run the DECnet/OSI for OpenVMS layeredtI               product on your OpenVMS Version 6.2 systems, you must firstdI               upgrade to Version 6.1 of DECnet/OSI for OpenVMS before you.H               can install any later versions of the product. Version 6.1F               of DECnet/OSI allows you to run DECnet applications overI               TCP/IP. Before you upgrade to Version 6.1 of DECnet/OSI for27               OpenVMS, note the following requirements:   I                                                                       1-3  -         =     OpenVMS Installation, Upgrade, and Hardware Release Notes-D     1.1 Installation and Upgrade Information Common to VAX and Alpha  /           If . . .                   Then . . .1  C           You are upgrading from     You can upgrade to Version 6.19E           OpenVMS Version 6.1,       of DECnet/OSI prior to upgrading49                                      your OpenVMS system..  B           You are upgrading from     You must upgrade your OpenVMS?           OpenVMS VAX Version 6.0    system before upgrading toi?           or                         Version 6.1 of DECnet/OSI.e           OpenVMS Alpha Version            1.5,  D           You are running DEC        You must upgrade to Version 3.2C           TCP/IP                     of the DEC TCP/IP Services forME           Services for OpenVMS,      OpenVMS product before upgradingiB                                      to Version 6.1 of DECnet/OSI.  C           You are running TCP/IP     Consult your TCP/IP vendor for A           from another vendor,       the minimum version of their E                                      product that will support DECnet.2                                      applications.,     1.1.2.2 DECnet/OSI Installation Can Fail  <     V6.1  During the installation of DECnet/OSI for OpenVMS,>           VMSINSTAL may fail with the following error message:  A           %SMI-E-INGDUPINV, Image NET$MESSAGE for product DECNET  !           already in images table   >           If you experience this behavior, issue the following/           commands and repeat the installation:g             $ SYSMAN:=$SYSMANr9           $ SYSMAN SYS_LOADABLE REMOVE DECNET NET$MESSAGEc  ;           Note that under normal circumstances you will not #           experience this behavior.   @     1.1.2.3 DECnet/OSI: NET$MANAGE Rights Identifier Recommended  >     V6.1  After installing the Decnet/OSI for OpenVMS product,A           Digital recommends that you grant the NET$MANAGE rights D           identifier to the SYSTEM account or any other account fromB           which you expect to use VMSINSTAL. Installations of someA           layered products may fail if you are running Decnet/OSIcE           and the account running the installation does not have thisn           identifier.        1-4  p  i      I                 OpenVMS Installation, Upgrade, and Hardware Release NotesIH         1.1 Installation and Upgrade Information Common to VAX and Alpha    H         1.1.2.4 InfoServer Client Can Fail to Start If DECnet Is Started                 or Stopped  D         V6.0  The InfoServer client software will fail to start on aC               system where DECnet has been started and subsequentlyhF               stopped. The following message will be found in the file*               SYS$MANAGER:ESS$STARTUP.LOG:  M               %ESS-I-NONET ESS started before DECnet.  4-MAR-1994 16:36:39.29n  B               This is caused by a problem in the startup procedure*               SYS$STARTUP:ESS$STARTUP.COM.  E               If the InfoServer client must be started at this point, I               the LASTport transport can be started with the Last Controls2               Program using the following command:                 $ MCR ESS$LASTCP               LASTCP> STARTa  H               This command will start the transport. You may now execute,               the InfoServer client startup:  -               $ @SYS$STARTUP:ESS$STARTUP DISKm  H               Because the last transport is already started, the startup$               will run successfully.  H         1.1.2.5 POLYCENTER Software Installation Utility Can Hang During-                 Layered Product Installations   G         V6.2  During a layered product installation, if another processpH               is accessing the DCL help library, the POLYCENTER SoftwareG               Installation utility will hang until it can open the fileeC               for exclusive access. When all users have exited from F               DCL help, the utility automatically resumes installationF               of the layered product. This wait condition occurs afterG               the "Portion Done: 0%..." message is displayed but before F               the percent complete indicator reaches 100%. However, noI               explicit warning message is displayed to alert the user wholG               issued the PRODUCT INSTALL command that one or more otherM3               users have the DCL help library open.O      I                                                                       1-5.           =     OpenVMS Installation, Upgrade, and Hardware Release Notes D     1.1 Installation and Upgrade Information Common to VAX and Alpha    @     1.1.2.6 VMSINSTAL Can Fail to Update DCL Help During Layered!             Product Installationsf  C     V6.0  During a layered product installation, if another processn<           is accessing DCL Help, the following events occur:  E           o  The installer sees the following message displayed once:   K              %VMSINSTAL-I-DCLHLPINUSE, Trying to update DCL HELP library.   1              Procedure will try three more times.   C              The procedure makes up to three additional attempts to ?              access DCL Help (one attempt every 1 1/2 minutes).   E           o  All user processes see the following message up to three C              times (that is, each time VMSINSTAL attempts and fails !              to access DCL Help):o  Q              Software installation procedure in progress, but DCL HELP command is M              in use. Trying to update DCL HELP library.  Please exit DCL HELP !              command temporarily.a  B           o  After three tries to update DCL Help (4 1/2 minutes),>              if DCL Help is still accessed, VMSINSTAL does the              following:   D              1. Moves the files to be updated to a working directory  B              2. Notifies the installer with the following message:  N                 %VMSINSTAL-I-NODCLHLP, DCL HELP not provided for this product.B                 Manually update HELP libraries after installation.@                 Use SYS$COMMON:[SYSHLP]<file name> for providing                 new HELP  A              3. At the completion of the installation, issues the 3                 following message to the installer:   F                 %VMSINSTAL-I-REFDCLHLP, DCL HELP could not be updated.K                 Reference SYS$UPDATE:DODCLHELP.VMI for information updating                  DCL HELP.m             1-6t           I                 OpenVMS Installation, Upgrade, and Hardware Release Notes I                     1.2 VAX Specific Installation and Upgrade Information     =         1.2 VAX Specific Installation and Upgrade Information   ?               The release notes in this section pertain only to I               installations or upgrades of OpenVMS VAX operating systems. G               See Section 1.1 for additional notes that pertain to both C               VAX and Alpha systems. For complete information about B               installing or upgrading your OpenVMS VAX Version 6.2D               operating system, refer to the OpenVMS VAX Version 6.2.               Upgrade and Installation Manual.  '         1.2.1 Problems and Restrictions   I               This section describes problems and restrictions related tos>               installing or upgrading OpenVMS VAX Version 6.2.  ,         1.2.1.1 Upgrade Version Requirements  I         V6.2  To upgrade your system to OpenVMS VAX Version 6.2, you must D               have OpenVMS VAX Version 6.0 or 6.1 already installed.  E               To perform a concurrent upgrade or rolling upgrade in auF               VAXcluster environment, all nodes in the cluster must beE               running at least OpenVMS VAX Version 5.5-2. For rollingpH               upgrades, Digital recommends that all nodes in the cluster;               run the same version of the operating system.,  A               For more information about upgrading to OpenVMS VAXaF               Version 6.2, see the OpenVMS VAX Version 6.2 Upgrade and"               Installation Manual.  6         1.2.1.2 Volume Shadowing Phase I Not Available  F         V6.2  Volume shadowing phase I (controller-based) is no longerG               available. Phase II (host-based) shadowing fully replaceslC               phase I shadowing and provides significantly enhanced                features.i  C               For more information about migrating to phase II, sees+               Volume Shadowing for OpenVMS.   F               At the beginning of an upgrade, the procedure checks theH               setting of the SHADOWING system parameter. If you have notI               migrated to phase II and the procedure detects the presenceaI               of phase I shadowing, it displays a message and asks you if,/               you want to continue the upgrade.e  I                                                                       1-7y m  i      =     OpenVMS Installation, Upgrade, and Hardware Release Notesc9     1.2 VAX Specific Installation and Upgrade Information     D           At that point, you can exit the upgrade procedure, migrateB           to phase II, and restart the upgrade from the beginning.C           If you continue the upgrade without migrating to phase IINA           shadowing, volume shadowing will not be present on youre1           system after the upgrade has completed.n  ;     1.2.1.3 DECnet for OpenVMS VAX Extensions Not Supportedt  >     V6.2  The DECnet for OpenVMS VAX Extensions product is notE           supported for OpenVMS VAX Version 6.2. The network products D           associated with DECnet for OpenVMS VAX Extensions (P.S.I.,>           WANDD, VOTS, OSAK, and FTAM) are no longer availableB           separately. If you need these products, you must migrateC           to Version 6.1 of DECnet/OSI for OpenVMS. For informationCD           about planning for and implementing DECnet/OSI for OpenVMSE           software, see the DECnet/OSI installation and configuration            manuals.  -     1.2.1.4 MACRO32.EXE and Standalone BACKUP   A     V6.2  To build standalone BACKUP onto tape, you must have the B           image MACRO32.EXE on your system disk. Do not tailor offD           the Macro libraries before building standalone BACKUP onto           tape.e  A     1.2.1.5 DECpresent Dependencies for Installing on OpenVMS VAXt             Version 6.1   D     V6.1  To run DECpresent Version 1.0A on OpenVMS VAX Version 6.1,E           you must upgrade the CDA Converter Library from Version 1.1            to Version 2.0.a  @           When installing DECpresent Version 1.0A on OpenVMS VAX@           Version 6.1, system managers can safely ignore the IVPC           failure for the CDA Converter Library Version 1.1 becauseaD           that version of the product is bundled with DECpresent but3           does not work on OpenVMS VAX Version 6.1..  A           After installing DECpresent Version 1.0A on OpenVMS VAXtE           Version 6.1, or upgrading from VMS Version 5.5-2 to Version ?           6.1 with DECpresent Version 1.0A already installed on B           the system, system managers should install CDA Converter           Library Version 2.0.         1-8            I                 OpenVMS Installation, Upgrade, and Hardware Release NotestI                     1.2 VAX Specific Installation and Upgrade Informationa    ?         1.2.1.6 VAXstation and MicroVAX Installation Workaroundl  H         V6.0  This release note applies specifically to VAXstation 4000-F               VLC, VAXstation 4000 Model 60, VAXstation 4000 Model 90,I               MicroVAX 3100 Models 30 and 40, and MicroVAX 3100 Model 80.t  @               If you halt the OpenVMS VAX Version 6.0 (or later)G               installation procedure after booting the new system disk,nI               the console will either display miscellaneous characters orUI               appear to hang. Turn the system power off and on to recovertC               the use of the console and continue the installation.u  H               Once AUTOGEN runs and the system reboots at the completionI               of the installation procedure, the console is usable again.   ?         1.3 Alpha Specific Installation and Upgrade Information6  ?               The release notes in this section pertain only to B               installations or upgrades of OpenVMS Alpha operatingH               systems. See Section 1.1 for additional notes that pertainE               to both Alpha and VAX systems. For complete information F               about installing or upgrading your OpenVMS Alpha VersionF               6.2 operating system, refer to the OpenVMS Alpha Version2               6.2 Upgrade and Installation Manual.  &         1.3.1 Changes and Enhancements  H               This section describes changes and enhancements to OpenVMS8               Alpha installation and upgrade procedures.  F         1.3.1.1 Installing or Upgrading an Alpha System from a Running                 System  G         V6.2  Beginning with OpenVMS Alpha Version 6.2 systems, you canoE               use the SYS$SYSTEM:AXPVMS$PCSI_INSTALL.COM procedure tovG               install or upgrade from a running OpenVMS Alpha system torE               another target system disk. The OpenVMS Version 6.2 NewIH               Features Manual describes this new feature in more detail.  C               Using the VMSKITBLD.COM procedure to duplicate systemvD               files from an existing system disk to another disk nowI               applies only to OpenVMS VAX systems (see the OpenVMS SystemS8               Manager's Manual: Essentials for details).  I                                                                       1-9n e  f      =     OpenVMS Installation, Upgrade, and Hardware Release Notesn;     1.3 Alpha Specific Installation and Upgrade Information     7     1.3.1.2 Removing the OpenVMS Alpha Operating Systemr  A     V6.1  Although use of the PRODUCT REMOVE command is not fullyeB           supported in OpenVMS Alpha Version 6.1 and later for theB           removal of the OpenVMS operating system, you can use theD           PRODUCT REMOVE command to remove most of the OpenVMS AlphaD           operating system from a system disk without affecting user           files on the disk.  5           Follow these steps to remove OpenVMS Alpha:R  D           1. If your system disk has multiple system-specific roots,C              boot the system and execute SYS$MANAGER:CLUSTER_CONFIGhB              to remove all roots except the one from which you are              booted.  D           2. Shut down and boot from the distribution CD-ROM or from@              a system disk other than the one from which OpenVMS>              Alpha is being removed. Execute the following DCLB              commands; substitute the device name of the disk fromD              which OpenVMS Alpha is being removed for <target-disk>,B              and the root number that you did not remove in step 1              for SYSx.  8              $ DEFINE/NOLOG PCSI$SYSDEVICE <target-disk>?              $ DEFINE/NOLOG PCSI$SPECIFIC <target-disk>:[SYSx.]uG              $ DEFINE/NOLOG PCSI$DESTINATION <target-disk>:[VMS$COMMON] )              $ PRODUCT REMOVE VMS /REMOTEE  B              If OpenVMS Alpha is not running from the distributionB              CD-ROM, you will need to be logged in to a privileged              account.   D           3. After the remove operation completes, review the targetB              disk to determine if you want to delete the followingC              files, which the PRODUCT REMOVE command cannot remove.   C              o  In <target-disk>:[SYS*.SYSEXE], where * is 0 or theoE                 hexadecimal number of any additional VMScluster roots #                 on the target disk:   "                    ALPHAVMSSYS.PAR                     MODPARAMS.DAT                    PAGEFILE.SYSt                    SWAPFILE.SYSd  5              o  In <target-disk>:[VMS$COMMON.SYSEXE]:t  "                    LMF$LICENSE.LDB       1-10    o      I                 OpenVMS Installation, Upgrade, and Hardware Release Notes I                   1.3 Alpha Specific Installation and Upgrade Information     5                        PCSI$FILE_SYSTEM.PCSI$DATABASEl3                        PCSI$PROCESSOR.PCSI$DATABASE .                        PCSI$ROOT.PCSI$DATABASE%                        RIGHTSLIST.DAT   F                 ________________________ Note ________________________  C                 Do not remove the *.PCSI$DATABASE files if you haveOB                 layered products installed on this disk, or if youF                 want to maintain a history of software installation on                 this disk.  F                 ______________________________________________________  D               4. Review the target disk for the directory structuresG                  [VMS$COMMON...] and [SYSx...], which will remain afterrE                  removing OpenVMS Alpha. You may want to remove these/                  directories.v  '         1.3.2 Problems and Restrictionsr  I               This section describes problems and restrictions related toS@               installing or upgrading OpenVMS Alpha Version 6.2.  +         1.3.2.1 RAID Devices Naming Problemt  E         V6.2  If you have RAID devices connected to StorageWorks RAIDtG               Array 210 or 230 subsystems, you might experience device-iF               naming problems when running in a cluster environment ifI               nonzero allocation classes are used. In this case, the RAIDtF               devices will be named $n$DRcu, where: n is the (nonzero)H               allocation class, c is the controller letter, and u is the               unit number.  F               If multiple nodes in the cluster have the same (nonzero)=               allocation class and these same nodes have RAIDAD               controllers, then RAID devices that are distinct mightI               be given the same name (for example, $1$DRA0). This problem.*               can lead to data corruption.  E               A new system parameter, DR_UNIT_BASE, has been added todI               provide a way for unique RAID device names to be generated. G               The RAID controller adds DR_UNIT_BASE to the unit number, B               u, before it creates the RAID device names. With DR_F               UNIT_BASE set to 0, the device name $1$DRA0 is produced;G               with the parameter set to 10, the device name $1$DRA10 isd               produced.p  I                                                                      1-11s o  I      =     OpenVMS Installation, Upgrade, and Hardware Release NotesA;     1.3 Alpha Specific Installation and Upgrade Information     D           Setting DR_UNIT_BASE to appropriate, nonoverlapping values>           on all cluster members that share the same (nonzero)E           allocation class ensures that no two RAID devices are givenp           the same name.  +     1.3.2.2 Audio Editor in DECwindows MailA  >     V6.1  The Audio Editor in DECwindows Mail is not usable onB           systems running DECwindows Motif Version 1.1 and OpenVMSA           Alpha Version 6.1 or later. The following error message:D           is displayed when you attempt to create a new mail message            with the Audio Editor:  /           Application Interface library error 0s  A           To eliminate this problem, install a kit for DECwindows %           Motif Version 1.2 or later.        1.3.2.3 Booting Messages  B     V6.1  You may see the following message on some systems during=           booting. This is simply an informational message toAB           indicate that an image was not installed as RESIDENT dueD           to insufficient code or data granularity hint region size.  H    %INSTALL-I-NONRES, installed image non-resident with other specified 
    optionsO    -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hinta	    region   >           You can either ignore this message or run AUTOGEN to&           eliminate the error message.  A           For more information about the /RESIDENT qualifier, see C           the OpenVMS System Management Utilities Reference Manual. E           For more information on installing resident images, see the (           OpenVMS Linker Utility Manual.       1.3.3 Corrections   =           This section describes corrections to OpenVMS Alpha .           installation and upgrade procedures.           1-12 r  o      I                 OpenVMS Installation, Upgrade, and Hardware Release Notes I                   1.3 Alpha Specific Installation and Upgrade Information     /         1.3.3.1 System Directories Installation   D         V6.2  During an installation of OpenVMS AXP Version 6.1, theH               following five directories were created without world read               access:a                 [VMS$COMMON]!               [VMS$COMMON.SYSEXE].               [SYS0]               [SYS0.SYSEXE]y               [SYS0.SYSCOMMON]  ?               This happened only during installation; directoryt=               protections were not changed during an upgrade.e  +               This problem has been fixed. h  $         1.4 Alpha Firmware Revisions  D               Refer to the Alpha AXP Systems Firmware Update VersionC               3.2 Release Notes Overview (Order Number AA-PW8YM-TE) D               contained on the Alpha Firmware Version 3.2 CD-ROM forE               the revision numbers of the console firmware needed forA%               each Alpha system type.s  H               The Release Notes Overview references a DOC directory thatH               contains release notes documents for each system type. TheI               release notes documents contain tables that list compatible 6               firmware and operating system versions.   9         1.5 AlphaStation and AlphaServer Series Computerst  ?               This section contains release notes that apply to 3               AlphaStation and AlphaServer systems.   &         1.5.1 Changes and Enhancements  F               This section describes graphics support on OpenVMS Alpha               systems.  C         1.5.1.1 Console Variable Default Change on AlphaServer 2100                  Systemsd  G         V6.2  Version V4.0 of the AlphaServer 2100 console now defaults G               the value of the console environment variable, bus_probe_ F               algorithm, to "new." This is the recommended setting for;               OpenVMS Version V6.2 and subsequent releases.l  I                                                                      1-13.           =     OpenVMS Installation, Upgrade, and Hardware Release Notes 5     1.5 AlphaStation and AlphaServer Series Computers     B           The "new" setting can result in a difference between theA           console controller letter assignments and the operatingr@           system controller letter assignment, especially if any@           PCI/PCI bridges are present in the system. The consoleD           environment variable, bus_probe_algorithm, can be reset toE           "old" to restore the existing controller letter assignment.l  E           After you change this environment variable, you must power-mC           cycle, or reset the system to ensure that the environmentOB           variable has taken effect. It is not possible to use theC           "new" setting for prior versions of the operating system.a       1.5.1.2 Graphics Support  E     V6.2  The following graphics support enhancements are included ini           this release:   D           o  This release supports the QVision PCI card (1280/P) for=              AlphaServer 1000, 2000, and 2100 series systems.u  E           o  This release supports the AlphaServer 1000 with embeddedS$              Cirrus system graphics.  ?              This support consists of a Cirrus CL-GD5422/24 VGAgA              controller integrated on the system motherboard withcB              supported resolutions of 800x600x256 and 640x480x256.A              (Refer to Section 1.5.2.5 for restrictions on Cirrus               system graphics.)  #     1.5.2 Problems and Restrictionsr  C           This section describes hardware problems and restrictions .           pertaining to OpenVMS Alpha systems.       1.5.2.1 Adapter Supporte  <     V6.2  If your AlphaStation 200 or 400 series computer is>           configured with multiple ZLX-E* graphics adapters (aD           multihead system), you must turn the computer off and then,           on (power-cycle) before rebooting.  -     1.5.2.2 Bells on AlphaStation 400 Systemss  C     V6.2  DECwindows now supports the bell function on AlphaStationoA           400 systems. There is no hardware support for adjustinguD           the volume. However, you can use the Bell Volume slider inC           the Keyboard Options dialog box under the Session ManagerGC           Options menu to adjust the frequency of the tone. You canIB           use the Keyclick Volume slider in the same dialog box to           adjust the duration.       1-14 ,         I                 OpenVMS Installation, Upgrade, and Hardware Release Notes I                         1.5 AlphaStation and AlphaServer Series Computersl             1.5.2.3 DECterm Startup   F         V6.2  DECterm windows might not start up properly when invokedH               using the Automatic Startup option in the Session Manager.  G               To correct this problem, set DECterm to run as a detachedy5               process by default. Follow these steps:   G               1. Click on the Applications menu in the Session Manager.   E               2. Click on the horizontal ellipsis ( ... ) next to theV                   DECterm option.  D               3. Click on the Detached option in the Run Application>                  section of the DECterm Qualifiers dialog box.  ?               4. Click on Save to make this change the default.I  I               Note: This problem is fixed in DECwindows Motif for OpenVMS I               Version 1.2-3. However, if you have saved a private profileiC               file (DECW$USER_DEFAULTS:VUE$PROFILE.VUE$DAT) from anlI               earlier version, you may still have to apply the correction %               described in this note.r  &         1.5.2.4 Ethernet Wire Settings  !         V6.2  Note the following:   E               o  Because the EWA0_MODE parameter AUTOSENSING does not B                  currently work on AlphaStation 200 and 400 seriesC                  systems, you must use one of the following console C                  commands to manually set your system to either AUIpD                  (thickwire or ThinWire) or TWISTED (twisted pair or                  10Base-T):s  &                  >>> SET EWA0_MODE AUI*                  >>> SET EWA0_MODE TWISTED  B               o  If you use the SET EWA0_MODE AUI setting, be sureE                  the specified mode matches the setting (thickwire or C                  ThinWire) for the jumper on the PCI Ethernet card.o            1.5.2.5 Graphics Support  B         V6.2  Note the following restrictions on graphics support:  F               o  ZLX-E* graphics are supported on AlphaStation 200 and)                  400 series systems only.s  8               o  No ISA graphics adapters are supported.  I                                                                      1-15  t         =     OpenVMS Installation, Upgrade, and Hardware Release Noteso5     1.5 AlphaStation and AlphaServer Series Computersn    @           o  On all AlphaStation series computers with graphics,A              be sure the console is set correctly by entering the 5              following command at the console prompt:a  %              >>> SET CONSOLE GRAPHICS   A           o  Note these restrictions on the AlphaServer 1000 witho-              embedded Cirrus system graphics:   B              -  The Cirrus CL-GD5422/24 VGA controller provides no$                 accelerated drawing.  D              -  The AlphaServer 1000 motherboard jumper that enablesB                 the Cirrus chip must be installed and all EISA busE                 graphics adapters must be removed prior to using this                  option.   B              -  Multi-head graphics support is not provided if the?                 Cirrus embedded graphics device option is used.t  D              -  The embedded Cirrus graphics support is intended forC                 limited use and may not be suitable for general uselA                 as a Motif display. DECterm text scrolling may benB                 slow and the limited display size may preclude the,                 use of certain applications.  B              -  Because the Cirrus embedded graphics controller onE                 AlphaServer 1000 supports a resolution (800x600) that C                 is different from the 1024x768 resolution supported C                 by DECwindows applications, some application screen @                 displays may extend beyond the image area of theA                 screen. The workaround for this problem is to adds>                 scroll bars to those applications by doing the                 following:  9                 1. While in a DECwindows session, add theR<                    following resource definition to the file.                    [SYSMGR]DECW$XDEFAULTS.DAT:  :                           *DXmfitToScreenPolicy: AS_NEEDED  E                 2. After editing (or creating) the resource file, endt*                    the DECwindows session.  B                 When you log back in to the system, the DECwindowsE                 applications that have long screen displays will haveT                 scroll bars.       1-16           I                 OpenVMS Installation, Upgrade, and Hardware Release Notes I                         1.5 AlphaStation and AlphaServer Series Computers'    G                  -  If the display performance is not adequate for your C                     needs, you can use optional EISA or PCI bus VGAaI                     graphics controllers instead. However, if you installtD                     optional graphics, you must disable the embeddedC                     Cirrus graphics by removing the jumper from thec                      motherboard.  )         1.5.2.6 HALT/CONTINUE Restrictionr  G         V6.2  On AlphaStation 400 series systems, use Ctrl/P to performeD               HALT/CONTINUE operations instead of pressing the ResetD               button. Pressing the Reset button resets the mouse and               keyboard.d  1         1.5.2.7 KFESA Port Reinitializing MessageS  G         V6.2  On AlphaStation 1000 series systems, if a KFESA DSSI diskoG               controller is installed, you may see several instances ofh2               the following message while booting:  +               %PAA0, Port is Reinitializing   B               You can ignore this message. If you do not want thisG               message to display, enter the console INIT command beforeA(               entering the boot command.  :         1.5.2.8 RX23 Disks Supported Instead of RX26 Disks  B         V6.2  AlphaStation 200 and 400 and AlphaServer 1000 seriesE               systems support RX23 disks but not RX26 disks. However,iE               the driver for the diskette device, DVDRIVER, currentlySF               identifies all diskette drives as RX26. As a result, theF               following command produces a display that identifies the(               diskette drive as an RX26:  #               $ SHOW DEVICE/FULL DVp  H               Note that the RX23 is capable of supporting double densityI               (DD) diskettes and high density (HD) diskettes. It does not 6               support extended density (ED) diskettes.  +         1.5.2.9 SCSI Controller Restrictiont  E         V6.2  The Adaptec 1740/1742 SCSI controller (PB2HA-SA) is notmF               supported on AlphaServer 2100 systems having more than 1E               gigabyte (GB) of memory. If the controller is connectednD               to such a system, the following message appears on the!               operator's console:   L               %PKJDRVR-E- The direct DMA window does not map all of memory. %               Port is going OFF LINE.g  I                                                                      1-17-           =     OpenVMS Installation, Upgrade, and Hardware Release Notes 5     1.5 AlphaStation and AlphaServer Series Computerss         1.5.2.10 Window Corruption  B     V6.2  On AlphaStation 200 and 400 series systems, some windowsE           will become corrupted (will not repaint correctly) after an$C           operator message is displayed. This occurs when either of *           the following conditions exists:  0           o  A window has backing store enabled.  =           o  A window is occluded by a window with SaveUndersr>              enabled. (Menus with DECwindows Motif for OpenVMS6              Version 1.2 and later enable SaveUnders.)  5           There are two workarounds for this problem:_  D           o  Shrink the corrupted window to an icon and then restore              it.  B           o  Refresh the screen by entering the following command:  %              $ MC DECW$UTILS:XREFRESHr  B           The DECwindows Motif 1.2-3 kit provides a Console WindowD           application to prevent this problem when using DECwindows.A           Refer to the DECwindows Motif Version 1.2-3 for OpenVMS A           Release Notes and Section 3.11.2.1 for more information 0           about the Console Window application.   %     1.6 Ethernet and FDDI Controllerse  =           This section contains release notes that pertain tot(           Ethernet and FDDI controllers.  #     1.6.1 Problems and Restrictions   ?           This section describes problems and restrictions thata;           pertain to certain Ethernet and FDDI controllers.b  E     1.6.1.1 Multiple Controllers Configured But Not All Attached to as             Wire (Alpha Only)n  <     V6.2  If you have multiple Ethernet and FDDI controllersE           configured on your system, and not all of them are attachedi@           to a wire, you might experience problems. Problems can>           range from not being able to access all the services<           available on the network, if you have four or more4           controllers configured, to a system crash.       1-18 p  m      I                 OpenVMS Installation, Upgrade, and Hardware Release NotesII                                         1.6 Ethernet and FDDI Controllers_    H               To avoid these problems, specify only the controllers thatF               are attached to the wire. Digital recommends that you doI               this by first editing your SYS$STARTUP:ESS$LAST_STARTUP.DATeI               data file to specify only the controllers that are attached .               and then restarting your system.  C               With certain controller configurations, if you do notoI               specify only the controllers that are attached, your system H               might crash when you issue the following command sequence:                 $ MC ESS$LASTCPr               LASTCP> STOP  A               An example of how to edit the SYS$STARTUP:ESS$LAST_ I               STARTUP.DAT file follows. The unedited file is shown first, )               followed by an edited file.s   !++aP ! This file will be used to set the appropriate LASTCP qualifiers. The followingL ! LASTCP qualifiers: ALL_CONTROLLERS, CHECKSUM, TRANSMIT_QUOTA, or SLOW_MODE5 ! can be set by using the following statement format: H ! LASTCP qualifier = 1 to enable   e.g. SLOW_MODE = 1 enables  SLOW_MODEH ! LASTCP qualifier = 0 to disable  e.g. SLOW_MODE = 0 disables SLOW_MODEN ! The remaining LASTCP qualifiers will require the appropriate value settings.% ! DEVICE          = (list-of-devices)s/ ! TIMEOUT    = n    minimum interval in secondsi0 ! CIRCUIT_MAXIMUM = n    maximum number of nodes% ! GROUP           = n    Group numberl$ ! NODE_NAME       = name   Node name? ! CONTROLLERS     = ([{controller letter,}...]) Controller list-3 ! TRANSMIT_QUOTA  = n    Number of transmit buffersc !--  ALL_CONTROLLERS = ON  G               The edited SYS$STARTUP:ESS$LAST_STARTUP.DAT file follows. >               This example assumes you have ESA, ETA, EXA, EZAE               controllers configured on your system and that only thee>               ESA controller is attached to the Ethernet wire.              I                                                                      1-19  t  i      =     OpenVMS Installation, Upgrade, and Hardware Release Notes.%     1.6 Ethernet and FDDI Controllers      !++iP ! This file will be used to set the appropriate LASTCP qualifiers. The followingL ! LASTCP qualifiers: ALL_CONTROLLERS, CHECKSUM, TRANSMIT_QUOTA, or SLOW_MODE5 ! can be set by using the following statement format: H ! LASTCP qualifier = 1 to enable   e.g. SLOW_MODE = 1 enables  SLOW_MODEH ! LASTCP qualifier = 0 to disable  e.g. SLOW_MODE = 0 disables SLOW_MODEN ! The remaining LASTCP qualifiers will require the appropriate value settings.% ! DEVICE          = (list-of-devices) / ! TIMEOUT    = n    minimum interval in seconds 0 ! CIRCUIT_MAXIMUM = n    maximum number of nodes% ! GROUP           = n    Group number $ ! NODE_NAME       = name   Node name? ! CONTROLLERS     = ([{controller letter,}...]) Controller list 3 ! TRANSMIT_QUOTA  = n    Number of transmit buffers  !--  ALL_CONTROLLERS = OFFs DEVICE = (ESA)  C              ________________________ Note ________________________p  ?              The default ESS$LAST_STARTUP.DAT file is stored ino@              SYS$COMMON:[SYS$STARTUP]. You might want to put theB              edited file in SYS$SPECIFIC:[SYS$STARTUP]. Otherwise,3              other system roots might be affected.    C              ______________________________________________________v  -     1.7 RF73 and Other RFnn DSSI Disk Devices   C           Notes in this section pertain to the RF31T, RF31T+, RF35, 2           RF35+, RF73, and RF74 DSSI disk devices.  #     1.7.1 Problems and Restrictionsa  B           This section describes a problem found in certain RF31T,@           RF31T+, RF35, RF35+, RF73, and RF74 DSSI disk devices.  @     1.7.1.1 RF73 and Other RFnn DSSI Disk Devices and Controller             Memory Errors   B           A problem exists with the microcode for earlier versionsA           of RF31T, RF31T+, RF35, RF35+, RF73, and RF74 DSSI disk.A           devices that can cause data loss. The problem can occur E           when reading data from one of these devices when the devicenC           has had a Controller Memory error (also known as an errort@           detection and correction (EDC) error). The error could       1-20 d  t      I                 OpenVMS Installation, Upgrade, and Hardware Release Notes H                                1.7 RF73 and Other RFnn DSSI Disk Devices    F               have been induced by a virtual circuit closure or faulty               hardware.a  D               Digital advises customers with any of these devices toE               check their microcode revision levels. If the microcodetA               revision levels are lower than the numbers shown in,?               Table 1-1, Digital recommends that you update thesH               microcode. The microcode for all models, except the RF31T,G               RF31T+, and RF35+, is provided on the OpenVMS Version 6.2 )               binary distribution CD-ROM.t  F               The RF_VERS utility, a utility program that displays theH               microcode revision level of the DSSI disk devices, is alsoH               provided on the CD-ROM. Instructions for using the utilityI               program and for updating the microcode are provided in thish               section.  F                 ________________________ Note ________________________  A                 If you have an RF31T, RF31T+, or RF35+ disk drive >                 with a version of microcode that is not error-?                 free (see Table 1-1), and if you have a support F                 contract, contact your Digital support representative.F                 Otherwise, contact your Digital account representative,                 or your authorized reseller.  F                 ______________________________________________________  G               The earliest supportable revision levels of the DSSI disk /               microcode are shown in Table 1-1.   <               Table 1-1 Error-Free Microcode Revision Levels  F               Device Type      Minimum Level with Error-Free Microcode  $               RF31T            T387E  $               RF31T+           T387E  $               RF35             T392D  $               RF35+            T392D  $               RF36             V427P  $               RF73             T392D  $               RF74             V427P  I                                                                      1-21p t  o      =     OpenVMS Installation, Upgrade, and Hardware Release Notesu-     1.7 RF73 and Other RFnn DSSI Disk Devicese    B           To display the microcode version level of your DSSI disk/           devices, perform the following steps:d  E           1. Log in to the SYSTEM account or another account that hasm9              the CMKRNL, DIAGNOSE, and SYSPRV privileges.r  *           2. Issue the following commands:  ?               $ SET PROCESS /PRIVILEGE=(DIAGNOSE,CMKRNL,SYSPRV) !               $ SHOW DEVICE FYA0:n  C              On VAX systems, if the SHOW DEVICE command produces an 1              error, issue the following commands:p  %               $ RUN SYS$SYSTEM:SYSGENn/                       SYSGEN>  CONN FYA0/NOADAPa"                       SYSGEN>  ^Z   E              On Alpha systems, if the SHOW DEVICE command produces anf1              error, issue the following commands:k  %               $ RUN SYS$SYSTEM:SYSMANM6                       SYSMAN> IO CONNECT FYA0: /NOADAP"                       SYSGEN>  ^Z   C           3. On VAX and Alpha systems, issue the following command:o  '               $ RUN SYS$ETC:RF_VERS.EXEs  D           The following is an example of the display produced by the           RF_VERS utility:  "            Program Name:   RF_VERS             Revision Level: V1.2s  J            NOTICE: This program does not currently support the RF72 or anyC                    HSDxx controllers. See next version for support.V  A            DSSI disks currently on this system as seen by RF_VERSo  O            Device            Node        Status            Hardware    FirmwaretN            Name              Name                          Type        Version  L            _$22$DIA7:        R4JL2I      mounted           RF73        T387AL            _$22$DIA6:        R4I0BG      mounted           RF73        T387AL            _$22$DIA8:        R4XLWE      mounted           RF73        T387AL            _$22$DIA2:        R4FCZK      mounted           RF73        T387AL            _$22$DIA3:        R4CKCG      mounted           RF73        T387AL            _$22$DIA4:        R4ZKUE      mounted           RF73        T387AL            _$22$DIA9:        R4GYYI      mounted           RF73        T387AL            _$22$DIA1:        R4XRYI      mounted           RF73        T387A       1-22 I  h      I                 OpenVMS Installation, Upgrade, and Hardware Release NotesiH                                1.7 RF73 and Other RFnn DSSI Disk Devices    I               To update the microcode in your device, use the appropriatesB               command for your device and platform from Table 1-2.  G                 _______________________ Caution _______________________   ?                 Back up the disk before updating the microcode.o  F                 ______________________________________________________  G               Table 1-2 Commands for Updating Microcode in Certain DSSIu$                         Disk Devices                 Device)               Type      Platform  Command   G               RF35      Alpha     $RUN SYS$ETC:RF35_T392F_DEC_ALPHA.EXEt  A               RF35      VAX       $RUN SYS$ETC:RF35_T392F_DEC.EXEe  G               RF36      Alpha     $RUN SYS$ETC:RF36_V427P_DEC_ALPHA.EXEi  A               RF36      VAX       $RUN SYS$ETC:RF36_V427P_DEC.EXEl  G               RF73      Alpha     $RUN SYS$ETC:RF73_T392F_DEC_ALPHA.EXEc  A               RF73      VAX       $RUN SYS$ETC:RF73_T392F_DEC.EXEt  G               RF74      Alpha     $RUN SYS$ETC:RF74_V427P_DEC_ALPHA.EXE   A               RF74      VAX       $RUN SYS$ETC:RF74_V427P_DEC.EXE   G                 _______________________ Caution _______________________   @                 Do not delete SCSI_INFO.EXE, RF_VERS.EXE, or any@                 of the files listed in Table 1-2. If these files?                 are deleted, VMSKITBLD.COM (on VAX) will not be C                 able to find them. Similarly, on Alpha systems, the C                 PRODUCT INSTALL commands in AXPVMS$PCSI_INSTALL andr2                 AXPVMS$PCSI_INSTALL_MIN will fail.  F                 ______________________________________________________  F         1.8 Hardware Information: VAX 4000 Series Computers (VAX Only)  G               This section contains notes pertaining to VAX 4000 Seriesy               Computers.  I                                                                      1-23s           =     OpenVMS Installation, Upgrade, and Hardware Release Notes B     1.8 Hardware Information: VAX 4000 Series Computers (VAX Only)    "     1.8.1 Changes and Enhancements  B     V6.1  The following notes supplement the information containedE           in OpenVMS Upgrade/Installation: VAX 4000 Series, MicroVAX, B           VAXstation, and VAXserver 32/33/34/35/36/38/3900 Series:  C           o  For certain VAX 4000 series systems with embedded DSSInA              buses, you can specify a DSSI bus number from 0 to 3l'              (rather than only 0 or 1).i  C           o  After you start the DUP Driver utility, you can change D              the DSSI node name by entering the following command at-              the PARAMS> prompt. For example:p  '              PARAMS> SET NODE <BARNEY>                                                                   1-24                         I                                                                         2iI         _________________________________________________________________u  I                                                General User Release Notesh    D               This chapter provides information for all users of theE               OpenVMS operating system. It includes information abouts3               commonly used commands and utilities.I  I               For information about new features included in this versiontH               of the software, refer to OpenVMS Version 6.2 New Features               Manual.i  "         2.1 Batch and Print Queues  H               This section contains release notes of general interest toG               most users of batch and print queue operations. Notes for I               this facility are also included in Chapter 3 and Chapter 4.z           2.1.1 Corrections   I               This section describes corrections to batch and print queuey               software.c  &         2.1.1.1 File Search Qualifiers  F         V6.2  In previous releases, a problem existed when you enteredG               a BATCH or PRINT command with one of the following search                qualifiers:r                    /BY_OWNER                  /CONFIRM                   /EXCLUDE                   /SINCEl                  /BEFORE  H               If no files met the selection criteria, an empty file listD               was sent to the Job Controller and the following error!               message was issued:   2               %SUBMIT-F-CREJOB, error creating job:               -JBC-F-MISREQPAR, missing required parameter  I                                                                       2-1p    e           General User Release Notes     2.1 Batch and Print Queues    A           With this release of OpenVMS, the Job Controller is not)?           called if there is an empty file list (that is, if noiD           files meet the selection criteria) and the following error           message is issued:  .           %SUBMIT-F-CREJOB, error creating jobC           -LIB-W-FILFAIMAT, file failed to match selection criteriaE       2.1.1.2 Print Job Alignmentp  E     V6.2  In prior releases, there was a problem aligning print jobs. A           If the end of a print job was reached during alignment, @           the job would complete normally; however, if the queue?           characteristics or the PRINT command did not have the 5           /RETAIN qualifier, the job would disappear.t  &           This problem has been fixed.       2.2 DCL Commands  D           This section contains release notes related to the DIGITAL@           Command Language (DCL) for this release of the OpenVMS           operating system.   #     2.2.1 Problems and Restrictions   9           The notes in this section describe problems andh2           restrictions pertaining to DCL commands.  :     2.2.1.1 SET PROCESS/NOAUTO_UNSHELVE Command in Cluster             Environment   @     V6.1  The command SET PROCESS/NOAUTO_UNSHELVE as implemented?           in Version 6.1 does not support operations across the B           cluster. It can be issued only for a process on the sameE           node, including as the default case, the process from whichw            the command is issued.  B           The /IDENTIFICATION=pid qualifier is supported, but onlyD           when the target process is on the same node as the process&           where the command is issued.             2-21 r  r      I                                                General User Release NotesnI                                                          2.2 DCL Commandsh    A         2.2.1.2 SET PROCESS/SUSPEND=KERNEL/ID= Command in Clusterr                 Environment   G         VAX   When you issue the SET PROCESS/SUSPEND=KERNEL/ID= commandeE         V6.0  in a cluster environment, the KERNEL keyword is ignoredeE         Alpha if the target process and the current process reside onlI         V1.5  different cluster nodes. As a result, process suspension is I               handled as if you had specified the SUPERVISOR keyword (the                default).t  A               This is caused by a problem with the $SUSPND systemlH               service, as discussed in Section 4.26.2.2. Digital expectsD               to fix this problem in a future version of the OpenVMS               operating system.            2.2.2 Correctionsn  I               The notes in this section describe software corrections for 4               problems associated with DCL commands.  ,         2.2.2.1 DELETE/QUEUE/MANAGER Command  F         V6.2  In previous versions, the following error message (whichC               was generated when the required /NAME_OF_MANAGER=nameLA               qualifier was omitted from the DELETE/QUEUE/MANAGERo>               command) displayed an incomplete qualifier name:  N %DCL-W-CONFLICT, illegal combination of command elements - check documentation \NONAME\  D               This problem has been corrected. The error message now               reads:  N %DCL-W-CONFLICT, illegal combination of command elements - check documentation \NONAME_OF_MANAGER\T  (         2.2.2.2 INITIALIZE/QUEUE Command  C         V6.2  Previously, you could specify negative values for thehH               working set qualifiers /WSDEFAULT, /WSEXTENT, and /WSQUOTA7               even though such values were meaningless.t  E               This problem has been corrected. Negative values are no G               longer accepted. If you specify a negative value, you getn               an error message.a  I                                                                       2-3i =  t           General User Release Notes     2.2 DCL Commands          2.2.2.3 PRINT/DELETE Command  A     V6.2  Previously, if you submitted a print job with the PRINTsC           /DELETE command, the file associated with a print job was ?           deleted even if the print operation was unsuccessful.m  D           This problem has been corrected. Files marked for deletion@           with the /DELETE qualifier are now deleted only if the+           print job completes successfully.R  .     2.2.2.4 PRINT/FORM Command on LAT Printers  D     V6.2  A problem existed that caused the LATSYM to crash when theE           /FORM qualifier specifying a WIDTH of 255 was used to printsD           a file containing an OSC escape sequence on a LAT printer.  *           This problem has been corrected.  )     2.2.2.5 SET QUEUE/DESCRIPTION Command   B     V6.2  In previous versions, entering the SET QUEUE/DESCRIPTIONA           command with a description string above a certain limit <           would cause the SHOW QUEUE command to display some            extraneous characters.  *           This problem has been corrected.  +     2.2.2.6 SET QUEUE/NODESCRIPTION Command   A     V6.2  In previous versions of the operating system, the queuee>           description was not deleted when the DCL command SETA           QUEUE/NODESCRIPTION was executed. This problem has beenTD           corrected, and the description is now deleted when the SET2           QUEUE/NODESCRIPTION command is executed.       2.2.2.7 SHOW SYSTEM CommandI  A     V6.2  Previously, if you entered the SHOW SYSTEM command on aoB           VAX node, the operating system was displayed as VAX/VMS.C           In a mixed-architecture VMScluster, this difference could D           cause problems for applications that parse the SHOW SYSTEM           display.  C           This problem has been corrected. The operating system for A           both OpenVMS Alpha and OpenVMS VAX is identified in the            display as OpenVMS.m       2-4o t  e      I                                                General User Release Notes I                                                          2.2 DCL Commands_    #         2.2.2.8 START/QUEUE Command   G         V6.2  In previous versions, there were problems associated witht&               the START/QUEUE command.  H               When you used the START/QUEUE/SEARCH="text string" commandH               to restart a paused print job, the print job did not startC               on the correct page (that is, the page containing the F               search text). Instead, the print job started a few linesF               before the actual page containing the text. This problem!               has been corrected.   I               When you used the START/QUEUE/BACKWARD=n command to restartiI               a queue after a paper jam and the paper was at top-of-form,gF               the print job would start with the last line of the pageE               before page n. This misalignment would continue for the E               rest of the print job. This problem has been corrected.            2.2.2.9 SUBMIT Command  F         V6.2  If a command procedure was submitted under the followingG               conditions, a problem caused a batch process to overwrite                with a log file:  I               o  A logical name for the command procedure was used in thei                   SUBMIT command.  1               o  The /NAME qualifier was omitted.   =               o  The /LOG qualifier was defaulted or omitted.e  .               This problem has been corrected.  8         2.2.2.10 SUBMIT/NAME and SET ENTRY/NAME Commands  G         V6.2  In previous versions, when you used a SUBMIT/NAME command,I               or a SET ENTRY/NAME command on a print queue, the following )               error message was returned:t  L               %JBC-I-ITMREMOVED, meaningless items were removed from request  A               This message was returned even though there were noM/               meaningless items in the command.   *               This problem has been fixed.  I                                                                       2-5_ _  N           General User Release Notes     2.2 DCL Commands    %     2.2.2.11 SUBMIT/NAME/USER Command   >     V6.2  In previous versions, the combined use of the SUBMIT@           command qualifiers /NAME and /USER caused the log file<           to be created in the wrong directory. For example:  B           o  If the following command was used to submit a commandD              file for another user, the log file would be created in:              the account specified by the /USER qualifier:  ?              $ SUBMIT SOME_WORK.COM /KEEP /NOPRINT /USER=DIMPLEs  A              In this example, the log file SOME_WORK.LOG would be @              created in the directory [DIMPLE]. This is correct.  B           o  However, if the following command-containing both theD              /USER and /NAME qualifiers-was used to submit that sameE              file, the log file would be created in the default login97              directory of the user submitting the file:   M              $ SUBMIT SOME_WORK.COM /KEEP /NOPRINT /USER=DIMPLE /NAME=BOUNCER   D              If the file was submitted from the account VOODOO, thenC              the log file BOUNCER.LOG would be created in the wrong                directory [VOODOO].  >           This problem has been corrected. The log file is now)           created in the right directory.m       2.3 DECnet Layered Product  ?           This section contains release notes pertaining to the !           DECnet layered product.S  "     2.3.1 Changes and Enhancements  @           The release notes in this section describe changes and?           enhancements to the DECnet layered product on OpenVMS            Version 6.2.  4     2.3.1.1 DECnet Phase IV Superseded by DECnet/OSI  D     V6.2  The DECnet/OSI layered product supersedes the DECnet PhaseC           IV product distributed with the OpenVMS operating system. @           DECnet Phase IV still ships with the OpenVMS operating=           system, but it will be retired in a future release.h       2-6  m  s      I                                                General User Release NotesNI                                                2.3 DECnet Layered ProductA    G               DECnet/OSI (DECnet Phase V) was first released on OpenVMS$H               in 1991. As with all previous releases of DECnet products,E               there is full backwards compatibility with the previous F               version. As such, customers can continue to use Phase IVA               network protocols and applications with DECnet/OSI.   I               The current release of DECnet/OSI provides a suite of toolsuG               for ease of upgrade and ease of use as customers make the E               transition to the new environment. Future releases will H               incorporate additional enhancements and improvements basedH               on customer feedback and needs. Some of these improvementsE               include making NCL network management easier to use and H               increasing the size of the local name space to accommodate7               larger networks with local name services.   ?               DECnet/OSI for OpenVMS on VAX and Alpha platformsuF               provides the functionality of DECnet plus support of theE               international OSI protocols. For more information aboutG;               upgrading to DECnet/OSI, see Section 1.1.2.1.$           2.4 DECserverm  C               This section contains notes pertaining to DECservers.   '         2.4.1 Problems and Restrictionsr  E               This section describes a restriction with the baud rateF               when using LAT.   #         2.4.1.1 Baud Rate Using LAT   C         V6.1  The DECserver 90TL and the DECserver 90M support port D               speeds of 57600. The DECserver 700 terminal controllerD               supports 57600, 76800, and 115200 bauds. However, whenB               the DECserver communicates with OpenVMS using LAT, aG               restriction allows LAT to report speeds only up to 57600.rE               This restriction will be addressed in a future release.c           2.5 DECTPU  D               This section contains notes pertaining to the DEC Text*               Processing Utility (DECTPU).      I                                                                       2-7                 General User Release Notes     2.5 DECTPU    #     2.5.1 Problems and Restrictions   @           The notes in this section describe DECTPU problems and           restrictions._  .     2.5.1.1 Motif Widget Context Help Built-In  C     V1.0  The following built-in, which should enter Motif context-hB           sensitive help mode, is disabled because of a problem in           the Motif toolkit:  B           SET (WIDGET_CONTEXT_HELP, widget_variable, {on|1|off|0})  B           The mouse pointer changes to a question mark, and DECTPUE           waits for you to select a widget by clicking on MB1. DECTPU D           then executes the help callback of the selected widget (orE           of its parent if the selected widget has no help callback).eB           The widget_variable is the widget within which the modalC           help interaction will occur, usually the top-level widget A           returned from the GET_INFO (SCREEN, "widget") built-in. B           The last parameter confines the question mark pointer toC           the specified widget if ON or 1, and does not confine the0           pointer if OFF or 0.  $     2.6 DECwindows Motif for OpenVMS  E           This section contains two release notes of general interestt@           pertaining to the DECwindows Motif for OpenVMS layeredC           product. All other notes for this product are included ine,           Section 3.11 and related sections.  "     2.6.1 Changes and Enhancements  ?           This section includes notes about support for the thei7           DECwindows Motif for OpenVMS layered product./  @     2.6.1.1 Support for DECwindows Motif Version 1.1 for OpenVMS  A     V6.2  OpenVMS Version 6.2 is the final version of the OpenVMSsB           operating system to support DECwindows Motif Version 1.1C           for OpenVMS. Future versions of OpenVMS will require that =           DECwindows Motif Version 1.2 or later be installed.            2-8  e  R      I                                                General User Release Notes H                                         2.6 DECwindows Motif for OpenVMS    ;         2.6.1.2 NCSA Mosaic Browser: TCP/IP Support Options   E         V6.2  DECwindows Motif Version 1.2-3 includes the NCSA Mosaic_A               web browser. The DECwindows Motif Version 1.2-3 for F               OpenVMS Release Notes state that the NCSA Mosaic browserI               requires that the TCP/IP Services for OpenVMS product (UCX)mC               be installed on your system. Note that TCP/IP supportsB               can alternatively be provided by PathWay for OpenVMS9               (Wollongong) or TCPware (Process Software).r           2.7 Image Activator   D               This section contains a release note pertaining to the               Image Activator.  &         2.7.1 Changes and Enhancements  @               This section describes an enhancement to the Image               Activator.  F         2.7.1.1 Message Returned on Attempt to Run an Alpha Image on a%                 VAX System (VAX Only)i  H         V6.2  The Image Activator has been enhanced to return this errorH               message if you attempt to run an OpenVMS Alpha image on an!               OpenVMS VAX system:e  #               $ RUN alpha_image.execA               %DCL-W-ACTIMAGE, error activating image ALPHA_IMAGErG               -CLI-E-IMGNAME, image file _$1$DKA0:[MY_DIR]ALPHA_IMAGE;1 E               -IMGACT-F-NOTVAXIMG, image is not an OpenVMS VAX image             2.8 Sort/Merge Utility  C               This section contains release notes pertaining to theo6               OpenVMS Sort/Merge utility (SORT/MERGE).  &         2.8.1 Changes and Enhancements  E               This section describes changes and enhancements to SORTd               /MERGE.     I                                                                       2-9     e           General User Release Notes     2.8 Sort/Merge Utility         2.8.1.1 /FIELD Qualifier  C     V6.2  The VALUE:n parameter has been added to the specificationl            file /FIELD qualifier:                /FIELDc  E              The VALUE:n parameter of the /FIELD qualifier allows you D              to define a constant field and assign it a value of anyB              valid Sort/Merge data type. You can use this constantD              field in specification file /KEY, /DATA, and /CONDITION              statements.  4              Table 2-1 describes the /FIELD formats.  B           Table 2-1 Formats of the /FIELD Qualifier for SORT/MERGE'                     Specification Filesd  6           Qualifier                            Default  3           /FIELD=(NAME=field-name,POSITION:n,  None.(           SIZE:n[,DIGITS:n][,data-type])  3           /FIELD=(NAME=field-name,VALUE:n,     None (           SIZE:n[,DIGITS:n][,data-type])  @           If you specify VALUE:n, do not specify POSITION:n. TheC           VALUE parameter is a constant and is not part of an inputi           record.   C           The VALUE:n parameter was previously undocumented, but itCE           is available in OpenVMS VAX releases beginning with Version B           5.1 and in OpenVMS Alpha releases beginning with Version           1.0.                           2-10 s  h                    I                                                                         3nI         _________________________________________________________________s  I                                           System Management Release Notes     F               This chapter contains information that applies to systemE               maintenance and management, performance management, and                networking.   I               For information about new features included in this version H               of the software, refer to OpenVMS Version 6.2 New Features               Manual.i  )         3.1 Authorize Utility (AUTHORIZE)   C               This section contains release notes pertaining to the                 Authorize utility.  &         3.1.1 Changes and Enhancements  B               This section notes a change to the working set quota               (WSQUOTA).  7         3.1.1.1 WSQUOTA Maximum Value Is 64K Byte Pages   I         V6.2  The working set quota (WSQUOTA) maximum value is 65536 (64K                byte) pages.  I               You may be able to set a higher value, but the maximum willa=               be enforced at the time the process is created.            3.2 AUTOGENa  H               This section contains release notes pertaining to AUTOGEN.  &         3.2.1 Changes and Enhancements  H               This section describes changes and enhancements to AUTOGEN%               on OpenVMS VAX systems.     I                                                                       3-1     l      #     System Management Release Notesa     3.2 AUTOGENt    @     3.2.1.1 AGEN$PARAMS.REPORT: Turning Off Logging (Alpha Only)  <     V6.2  The contents of MODPARAMS.DAT are evaluated as DCL=           statements, and you can make assignments to symbolsmA           with names that are not SYSGEN parameters (for example, A           "scratch" variables or conditional assignments based on @           other values). Traditionally, every such assignment isB           logged in AGEN$PARAMS.REPORT, sometimes creating a large@           file with many logging statements that do not interest           users.  :           Starting with OpenVMS Alpha Version 6.2, you canA           designate any assignments that you prefer not to log inlD           AGEN$PARAMS.REPORT by prefixing every such assignment withD           a dollar sign ($). When AUTOGEN encounters a MODPARAMS.DATB           record beginning with a $, it does not check the list ofA           known SYSGEN parameters and does not log this record to            AGEN$PARAMS.REPORT.   /     3.2.1.2 CTLPAGES Parameter Value (VAX Only)   D     V6.2  The value of the parameter CTLPAGES is now computed, basedB           on the default value and on any site-specific changes toC           LNMPHASHTBL (as well as direct modifications of the valuer           of CTLPAGES).   %     3.2.1.3 Dump File Size (VAX Only)e  C     V6.2  As in previous releases, the software dumps the system tonA           SYSDUMP.DMP if the file is present - even if the SYSGENR@           parameter SAVEDUMP is set to 1 to indicate that system2           dumps be dumped to PAGEFILE.SYS instead.  C           Previously, AUTOGEN would not compute and adjust the sizerD           of the dump file if one was present. Starting with VersionC           6.2, AUTOGEN calculates the proper size for the dump file B           if a dump file exists. If execution proceeds through theC           GENFILES phase, AUTOGEN might even enlarge the dump file.r
                  3-2i           I                                           System Management Release NotesaI                                                               3.2 AUTOGENU    -         3.2.1.4 Retired Parameters (VAX Only)   E         V6.2  AUTOGEN has a list of parameters that have been retiredoE               in this version as well as earlier versions of OpenVMS.xG               When one of them is encountered in MODPARAMS.DAT, AUTOGENiH               will make the symbol assignment and enter an informationalG               message in the report file, just as it does for "scratch"e               variables.  C               The current list of retired parameters is as follows:A                    CRDENABLE$                  IRPCOUNT, IRPCOUNTV5                  LRPCOUNT, LRPCOUNTV, LRPMIN, LRPSIZEt5                  SRPCOUNT, SRPCOUNTV, SRPMIN, SRPSIZE $                  TTY_OWNER, TTY_PROT(                  AWSMIN_SYS, AWSTIME_SYS'                  PFRATL_SYS, PFRATH_SYS %                  WSINC_SYS, WSDEC_SYS                   QUORUM   0         3.2.1.5 SYSMWCNT Computations (VAX Only)  H         V6.2  The computation of SYSMWCNT (working set for the operatingG               system, in pages) now uses the first 8192 pages of SPTREQ G               (additional system page table entries), instead of a much                smaller subset.   E               SYSMWCNT for MicroVAX systems is still capped at 10% ofdE               physical memory, but the computation no longer includesaI               the restriction of reducing by 75% the amount that exceeded                1000 pages.n  G               These two changes can be expected to increase SYSMWCNT byaE               200 to 500 pages on MicroVAX systems, and by 100 to 200 *               pages on other VAX systems.           I                                                                       3-3a           #     System Management Release Noteso     3.2 AUTOGENh    )     3.2.1.6 WSMAX Computations (VAX Only)e  D     V6.2  The computation of WSMAX is no longer linear but resemblesE           a logarithmic curve. Instead of simply computing WSMAX as aUE           quarter of physical memory, it is now computed as a quarterrD           of the first 32 MB, plus a sixteenth of the memory from 32E           to 256 MB, plus a sixty-fourth of the memory (if any) aboveA           256 MB.h  B           This is intended to assist managers of systems that hostB           large numbers of users whose working sets are not large.?           Systems whose user bases consist of a small number of E           users (or processes) that require large amounts of physicaldB           memory (for example, simulations) might need to set MIN_C           WSMAX to a value that satisfies the requirements of thoseo           processes.    #     3.2.2 Problems and Restrictionss  ;           This section describes known AUTOGEN problems ande           restrictions.m  *     3.2.2.1 Full Memory Dumps (Alpha Only)  @     V6.2  OpenVMS Alpha Version 6.2 does not perform full memory>           dumps (the system parameter DUMPSTYLE set to 0 or 2)?           on systems with over 4 gigabytes of memory. Selective B           dumps (the system parameter DUMPSTYLE set to 1 or 3) are)           supported for all memory sizes.   A           The default action by AUTOGEN is to set DUMPSTYLE to 1.U;           This is the recommended setting for all systems.         3.3 Backup Utility  >           Notes in this section pertain to the Backup utility.  #     3.3.1 Problems and Restrictionsa  D           This section describes known problems and restrictions for           the Backup utility.t       3-4b h  U      I                                           System Management Release NotessH                                                       3.3 Backup Utility    -         3.3.1.1 Image and Incremental Backupsi  D         V6.2  The first time you back up a disk, you must perform anG               image backup using the BACKUP/IMAGE/RECORD command before G               you perform regular incremental backups. The image backupiD               saves a copy of the entire disk and marks each file asI               being saved. Subsequent incremental backups assume an image H               backup has been performed and, therefore, save only new or               modified files.O  I               If an image backup was not performed first, the incremental G               backups save more files than might be necessary to ensure =               that an incremental restore will be successful.   G         3.3.1.2 Incremental Backups Using PATHWORKS for OpenVMS ServersE  D         V6.2  An incompatibility between the operating procedures ofD               the PATHWORKS for OpenVMS Macintosh server and OpenVMS?               incremental backup operations can cause BACKUP toeB               save entire disks or directory structures, including'               subdirectories and files.t  H               A recent change to fix other problems now causes Backup toI               detect whether a directory file has been modified since theVI               date indicated by the Backup Date field in the file header.hG               If a directory file has been modified, all subdirectories F               and files of that directory are saved for possible laterC               restore operations. Updating the modification date oftD               directory files is unusual for OpenVMS systems, but itE               can happen, for example, if you rename a directory filelF               from one location to another. By contrast, the PATHWORKSA               Macintosh server maintains the modification date of F               directory files for Macintosh users; that is, it updatesC               the modification date for each directory change, file *               creation, and file deletion.  F               Thus, an incremental backup of a disk where PATHWORKS isI               used to serve files to Macintosh users may result in savingsD               the entire disk or entire directories (including theirF               subdirectories and files) instead of just the user filesF               that were created or modified since the last incremental               backup operation.r  H               This incompatibility will be addressed in a future version               of OpenVMS.u  I                                                                       3-5            #     System Management Release Noteso     3.3 Backup Utility    <           For now, you can avoid needless saving of files byE           performing a dummy BACKUP/RECORD operation on all directory E           files immediately before performing the incremental backup. <           The following example illustrates this workaround:  .           $ BACKUP/RECORD/IGNORE=(INTERLOCK) -&           _$ disk:[000000...]*.DIR;* -3           _$ NLA0:DUMMY.BCK/SAVE/NOCRC/GROUP_SIZE=0            $p:           $ BACKUP/VERIFY/FAST/RECORD/IGNORE=(INTERLOCK) ->           _$ /NOASSIST/COMMENT="Incremental backup of DISK:" -1           _$ disk:[000000...]*.*;*/SINCE=BACKUP -M*           _$ tape:incr.bck/LABEL=incr/SAVE  @           In this example, the first BACKUP command performs theC           dummy backup operation and the second performs the actualUB           incremental backup. The first command updates the Backup@           Date field for all the directory files. Specifying the?           null output device [000000...] causes no saveset file @           to actually be written. Since no file information needA           be retained from this operation, the /NOCRC and /GROUP_ D           SIZE=0 qualifiers are specified to avoid CRC and XOR block           calculation.  4     3.3.1.3 Warning Issued on ANALYZE/DISK Operation  A     V6.2  An ANALYZE/DISK operation performed immediately after a B           BACKUP/IMAGE restore of a disk might result in a warning+           message similar to the following:a  C           %ANALDISK-W-ALLOCCLR, blocks incorrectly marked allocated &                   LBN 97 to 105, RVN 1  D           This can be caused by attempting to perform a BACKUP/IMAGED           restore operation where alias file entries are restored asC           separate (primary) file entries. (The primary file, whicht@           uses the same file header but allocates different data,           storage blocks, is also restored.)  =           Note that there is no BACKUP error or loss of data.l  ?           This problem will be addressed in a future version ofn           OpenVMS.         3-6i t         I                                           System Management Release NoteswH                                                       3.3 Backup Utility    -         3.3.1.4 CD-ROM Menu System (VAX Only)h  H         V6.1  Do not use the CD-ROM menu system, which displays when youF               boot the OpenVMS VAX operating system CD-ROM, to back up>               user disks. Use it to back up system disks only.  G               When you boot from the SYS1 directory on the distributionfD               CD-ROM, you are booting a writelocked system disk thatI               does not allow paging. Because of this, the system displaysv6               error messages similar to the following:  D               %SYSINIT-E, error opening page file, status = 0000025CD               %SYSINIT-E, error opening swap file, status = 0000025CN               %SYSINIT, primary PAGEFILE.SYS not found; system initialization                continuingB               %SYSINIT, no dump file - error log buffers not savedI               %SYSINIT-E, error mounting system device, status = 00000F64T  H               These messages are normal. The lack of page and swap files.               does not affect most operations.  F               If you back up large user disks, BACKUP may need to pageH               and the operation could fail. Use online BACKUP to back up               user disks.r  E               This can also occur when you use the CD-ROM menu system H               to back up large system disks on low memory systems (thoseF               with less than 32 MB of memory). If this problem occurs,=               use standalone BACKUP to back up system disks.    /         3.3.1.5 Image Backups from an RF73 Disk   E         V6.1  When performing an image backup from an RF73 disk (or asI               disk with a cluster size of 4 blocks) to an RF74 disk (or a G               disk with a cluster size of 7 blocks), the Backup utility F               does not check the file size when it is allocating spaceC               for the file being copied. Therefore, if the file hasuF               an allocation greater than the value of the CLUSTER_SIZEE               attribute established during initialization, the BackupAC               utility will allocate one more cluster size number ofGG               blocks to the allocation size even though the actual file-H               size is less than the cluster size. For example, during anF               image backup, a file that uses 6 blocks and is allocatedH               8 blocks (which displays as 6/8 on the screen if you enterD               a DIRECTORY/SIZE=ALL command) shows an increase in itsH               allocation size to 14, instead of 7, after it is copied to               the target disk.  I                                                                       3-7s    .      #     System Management Release NotesD     3.3 Backup Utility    E           As a result of this problem, the following files are copied/E           to the image system disk with a blocks used/allocation sizer           of 6/14 blocks:i  -              SYS$COMMON:[SYS$LDR]LIDRIVER.EXE -              SYS$COMMON:[SYS$LDR]LPDRIVER.EXE   D           This incorrect allocation size causes standalone BACKUP to/           fail on the booted image system disk.I  C           To correct this problem, recopy the two previously listedI@           files to the same directory after the image backup, by?           using the following command (which also specifies the #           correct allocation size):   S           $ COPY/ALLOCATION=7 SYS$COMMON:[SYS$LDR]LIDRIVER.EXE SYS$COMMON:[SYS$LDR],S           $ COPY/ALLOCATION=7 SYS$COMMON:[SYS$LDR]LPDRIVER.EXE SYS$COMMON:[SYS$LDR]   5     3.3.1.6 Relative File Version -0 Processed Like 0e  @     V6.1  The Backup utility processes relative version -0 as ifB           it were 0, saving the most recent version instead of the6           earliest version of the file for processing.  =           Digital expects to correct this problem in a futureg           release.  E     3.3.1.7 Standalone BACKUP Version 5.3 on Console Media (VAX Only)   >     V6.1  OpenVMS VAX Version 6.1 and later is available on 9-B           track magtape in three forms: magnetic tape only or withE           standalone BACKUP on either RX50 or RL02 console media. The_D           standalone BACKUP on the console media is VMS Version 5.3;B           the media is so labeled and identifies itself as VersionB           5.3 on startup. The standalone BACKUP console media haveA           not been updated for OpenVMS VAX Version 6.1 and later.   <           OpenVMS VAX Version 6.1 and later is not available?           with standalone BACKUP on RX01 or TU58 console media.oA           Installations using these console media are expected to D           have standalone BACKUP console media created from previousB           versions of the operating system. If you need standalone@           BACKUP on RX01 or TU58 media and are not in a positionB           to create your own kits before installing Version 6.1 orC           later, please contact your Digital support representative            for assistance.O       3-8  u  s      I                                           System Management Release NotesaH                                                       3.3 Backup Utility    H               After you have installed OpenVMS VAX Version 6.1 or later,H               you can build a Version 6.1 or later standalone BACKUP kitE               on a disk of your choice or on the RL02 or RX50 consolehG               media. You cannot build a Version 6.1 or later standalone D               BACKUP kit on RX01 or TU58 media. If you use either ofG               the latter, you must retain a kit built from a previously 9               installed version of the operating system. l  I         3.3.1.8 Standalone BACKUP Failure on VAX 4000 Model 300 and TF857                  (VAX Only)  sI         V6.0  If a TF857 and the VAX 4000 Model 300 are connected as partfI               of a tri-hosted DSSI configuration, standalone BACKUP failsd"               to operate properly.  F               For standalone BACKUP to work properly on VAX 4000 ModelH               300 from a TF857, it is necessary to either have the TF857H               connected to no more that one host or to disable the other=               two hosts by executing the shutdown procedure.    5         3.3.1.9 VMS$COMMON.DIR File: Restore ProblemsO  H         VAX   On an OpenVMS system disk, the file [SYSx]SYSCOMMON.DIR isI         V6.0  an alias directory of the file [000000]VMS$COMMON.DIR. ThisiH         Alpha means that both files point to the same file header. PriorI         V6.1  to OpenVMS VAX Version 5.5-2 and OpenVMS Alpha Version 1.5,GF               BACKUP did not properly restore the VMS$COMMON.DIR file.E               Although this does not affect the system disk, it mightnH               produce errors with DIGITAL Command Language (DCL) lexical               functions.  E               OpenVMS VAX Version 5.5-2 and OpenVMS Alpha Version 1.56C               corrected this problem. However, if you restore image F               backups created with an old OpenVMS version, the problem               can recur.  D               The symptoms of the problem are different depending onI               which version of the operating system you are using. If yousF               upgraded from OpenVMS VAX Version 5.5-2 or OpenVMS AlphaH               Version 1.5 to OpenVMS VAX Version 6.0 or later or OpenVMSI               Alpha Version 6.1 or later, it is unlikely that your system I               disk has this problem. However, you should confirm this and /               correct the problem if necessary.   I                                                                       3-9            #     System Management Release Notes      3.3 Backup Utility    >           To restore VMS$COMMON to its proper state, enter the           following commands:   %           $ SET DEFAULT DISK:[000000]r7           $ SET FILE/ENTER=SYSCOMMON.DIR VMS$COMMON.DIRm+           $ SET FILE/REMOVE VMS$COMMON.DIR; /           $ RENAME SYSCOMMON.DIR VMS$COMMON.DIRn  >           If you upgraded to OpenVMS Version 6.1 or later from@           OpenVMS VAX Version 5.5-2 or OpenVMS Alpha Version 1.5E           without following this procedure, your system disk could be #           affected by this problem.I  B           To determine if your system disk has this problem, enter?           a BACKUP/LIST command to display save set information @           about the files contained in the VMS$COMMON directory.           For example:                .              .              .O           [000000]VOLSET.SYS;1                             0  24-SEP-1994 19:31nO           []000000.DIR;1                                   1  24-SEP-1994 19:31eO           []SYSCOMMON.DIR;1                                2  24-SEP-1994 19:31 O           []SYSLIB.DIR;1                                  18  24-SEP-1994 19:31 O           []SYSTEST.DIR;1                                  1  24-SEP-1994 19:31pO           []SYSMAINT.DIR;1                                 1  24-SEP-1994 19:31uO           []SYSMGR.DIR;1                                   6  24-SEP-1994 19:31 O           []SYSHLP.DIR;1                                   6  24-SEP-1994 19:31iO           []EXAMPLES.DIR;1                                 1  24-SEP-1994 19:311O           []SYSUPD.DIR;1                                   4  24-SEP-1994 19:31 O           []SYSMSG.DIR;1                                   3  24-SEP-1994 19:31t              .              .              .O           []SECURITY_AUDIT.AUDIT                           2   3-FEB-1995 15:23MO           []SECURITY_AUDIT.AUDIT                          11   3-FEB-1995 15:23iO           []BACKUP.EXE;33                                273   4-FEB-1995 09:37tO           []STABACKUP.EXE;9                              486   4-FEB-1995 09:38o  D           If the display lists the files in the VMS$COMMON directoryD           as lost files (files with an empty directory specificationA           as shown in this example), your system disk is affectedrB           by this problem. Follow the procedure described above to           correct it.        3-10           I                                           System Management Release Notes,H                                                       3.3 Backup Utility             3.3.2 Correctionso  F               This section describes corrections to the OpenVMS Backup               utility (BACKUP).A  0         3.3.2.1 BACKUP$_ACCONFLICT Error Message  F         V6.2  In prior versions of BACKUP, using the /IGNORE=INTERLOCKC               qualifier would result in BACKUP reporting a BACKUP$_eH               ACCONFLICT message when a file was accessed for WRITE fromD               the local node during the initial opening of the file.F               If the file was accessed from a remote node or if it wasH               accessed for WRITE from the local node after BACKUP openedF               the file, a BACKUP$_ACCONFLICT message was not reported,I               and users would not know that they might have an inaccurate                copy of the file.   D               BACKUP now reports a BACKUP$_ACCONFLICT message if theI               file is modified while BACKUP is reading the file or if the F               file is accessed for WRITE on the local node when BACKUPH               is finished reading the file. This correction improves the'               accuracy of this message.   E               Note, however, that BACKUP is unable to detect when the G               file is being accessed for WRITE from a remote node after I               BACKUP is finished reading the file, and no message will be                displayed.  5         3.3.2.2 Boot Block Saved Correctly (VAX Only)a  E         V6.2  In previous versions of OpenVMS VAX, if an image backuppH               of an Alpha system disk was performed on a VAX system, theE               boot block was not saved correctly and the user was not F               notified that there was a problem. If the resulting save@               set was restored, the Alpha system would not boot.  E               This problem has been corrected. Now, the boot block isoD               saved correctly and, on a restore operation, the Alpha               system reboots.         I                                                                      3-11a a  p      #     System Management Release Notes      3.3 Backup Utility         3.3.2.3 Incremental Restore   B     V6.2  Previous versions of the OpenVMS Backup utility (BACKUP)E           would not restore target disk structures as expected duringrD           incremental restore operations, resulting in the following           problems:D  E           1. Some directories and their contents would be erroneouslyn?              created or restored (as opposed to deleting or notiD              creating those directories and their contents that were>              previously deleted or renamed to a new location).  @           2. In cases where a directory was renamed (moved) to aB              new location, BACKUP would not be able to detect thatD              the directory was renamed and would not save all of theD              directory's files and subdirectory contents. Thus, some@              data files could be lost during a restore operationE              because the original files would not be contained in ther"              incremental save set.  C           3. No attempts were made to restore alias or synonym file               entries.i  ?           These problems have been corrected in this version ofi           BACKUP, as follows:i  A           1. BACKUP now examines the target disk and the save-setsA              contents and more properly determines which save-set D              entries are to be ignored and which target disk entriesB              are to be deleted. Additionally, if a privilege errorB              is encountered when directories or other files are to@              be deleted from the target disk, an attempt is madeA              to change the protection of the files so they can beu              deleted.i  >           2. BACKUP now detects that a directory file has beenA              modified and saves the directory contents and all of B              its subdirectories' contents. This will allow renamed1              directories to be properly restored.O  C              ________________________ Note ________________________N  A              Note that the renaming of directories is a procedureK?              that is not recommended by Digital. Also note thatTB              changing security information for a directory changesB              its modification date. Thus, directories might appearC              to be "renamed" and their contents and subdirectories' @              contents included in incremental save sets if their       3-12 n  m      I                                           System Management Release NotestH                                                       3.3 Backup Utility    C                 file protection or security information is changed.l@                 The addition of renamed directory contents might@                 increase the size of some incremental save sets.  F                 ______________________________________________________  H                  In incremental restore operations, BACKUP processes theG                  target disk directory structure by directory levels inrG                  alphabetical order. Thus, circumstances may occur that F                  prevent BACKUP from properly restoring an incrementalG                  save set to a target disk. An example of this is whereiG                  the target disk does not have sufficient space to holdeH                  newly "renamed" directories and their contents prior toH                  deleting the original directories and their contents on!                  the target disk.c  E                  If the incremental restore fails due to insufficient C                  disk space, a possible workaround is to apply thateC                  incremental save set a second time (prior to doing E                  anything else). Often, this workaround will complete C                  successfully because the first incremental restore F                  continues and deletes directories and their contents,H                  making more space available on the target disk. AnotherI                  possible workaround is to selectively restore files froms                  the save set.  E               3. BACKUP now attempts to restore alias or synonym filesF                  entries in incremental restore operations that do notE                  specify multiple processing of alias or synonym filetC                  entries (/NOALIAS). In cases where the alias entry H                  cannot be restored properly, an error message is issuedI                  indicating the alias file entry, its primary file, and a F                  secondary status indicating the cause of the failure.  B                  If the /LOG qualifier was specified in the BACKUPF                  command, successful restoration of alias file entries7                  is indicated by a message to the user.s  C                  If there is to be a separate verify pass, (/VERIFYfF                  qualifier was specified in the BACKUP command), aliasG                  entry restoration is attempted during the verify pass.nF                  Otherwise, alias entry restoration is attempted alongF                  with the normal file restoration. The reason for thisH                  behavior is that an attempt is made to have all primaryD                  files restored prior to attempting to restore aliasD                  entries that will eventually reference those files.  I                                                                      3-13  m         #     System Management Release Notes      3.3 Backup Utility    (     3.3.2.4 Save Operation Error Message  E     V6.2  In prior versions of OpenVMS, if a user specified a versionnC           number for a disk save set on a save operation and a file C           with that version already existed, BACKUP would overwriteaC           the file, destroying the contents of the file. This couldt!           result in loss of data.z  B           BACKUP now reports the following error message if a file4           with the specified version already exists:  8           RMS-E-FEX, file already exists, not superseded             For example:  !           $ DIRECTORY LOGIN.BCK;*   $             Directory WORK$:[BACKUP]               LOGIN.BCK;1   -           $ BACKUP LOGIN.COM LOGIN.BCK;1/SAVErL           %BACKUP-F-OPENOUT, error opening WORK$:[TEST]LOGIN.BCK;1 as output:            -RMS-E-FEX, file already exists, not superseded  (     3.4 Batch and Print Queue Management  @           The following notes contain information about managing!           batch and print queues.   #     3.4.1 Problems and Restrictions   C           The following sections describe problems and restrictionsl=           pertaining to batch and print queue management. FortD           problems important to programmers, refer to Section 4.1.1.  ,     3.4.1.1 Process Rights Identifier Limits  ?     V6.2  In OpenVMS Version 6.2, processes that have more thant>           512 rights identifiers cannot perform queuing systemC           operations. When a process with more than 512 identifiersrD           attempts to submit or print jobs, or manage queues, forms,D           or characteristics, the system returns the following error           message:  9           SYSTEM-F-ARBTOOBIG, access rights block too bigY       3-14 Y  O      I                                           System Management Release NotesYH                                     3.4 Batch and Print Queue Management    &         3.4.1.2 VMScluster Environment  E         VAX   The multiple queue manager feature cannot be used untiltG         V6.0  all nodes in a VMScluster environment are running OpenVMStG         Alpha VAX Version 6.0 or later and OpenVMS Alpha Version 6.1 ore         V6.1  later.  H               In addition, once you begin using multiple queue managers,A               you cannot bring into the cluster a node running anaF               operating system version earlier than those cited above.E               Doing so can result in unexpected behavior or failures.c  $         3.4.1.3 PRINT/DELETE Command  F         VAX   Before OpenVMS VAX Version 5.5 and OpenVMS Alpha VersionG         V5.5  1.5, the queue manager allowed users to specify the PRINT D         Alpha /DELETE command for a file residing on a disk that wasH         V1.5  not mounted clusterwide, as long as the queue specified inH               the command was assigned to a node with access to the file               being printed.  E               As of OpenVMS VAX Version 5.5 and OpenVMS Alpha VersionaF               1.5, the new clusterwide queue manager process must haveI               access to the file specified with the PRINT/DELETE command. =               Otherwise, the file is printed but not deleted.o  G               This problem will be addressed in a future release of theoI               operating system. Until then, you can ensure that the PRINT E               /DELETE command deletes the specified files by mountingnI               the disks on which the files reside clusterwide. To mount a I               disk clusterwide, use the /CLUSTER qualifier with the MOUNTi               command.  G               However, if your operating environment does not allow you G               to mount a disk clusterwide, you can resolve this problem E               by running the queue manager process on a node that has G               access to the disk. You can specify the node on which the D               queue manager process runs by specifying the /ON=node-F               list qualifier with the START/QUEUE/MANAGER command. ForE               more information on this qualifier, see the OpenVMS DCL                Dictionary.6  %         3.4.1.4 SUBMIT/DELETE Command   D         VAX   The information in Section 3.4.1.3 also applies to the$         V5.5  SUBMIT/DELETE command.
         Alphap         V1.5  I                                                                      3-15     0      #     System Management Release Notesa(     3.4 Batch and Print Queue Management         3.4.2 Correctionsd  E           This section describes corrections to batch and print queuedE           features used by system managers. For batch and print queue @           corrections related to programming, see Section 4.1.2.>           For corrections of interest to the general user, see           Section 2.1.1.  *     3.4.2.1 Form Feeding in Print Symbiont  E     V6.2  In previous releases, the PRTSMB and LATSYM print symbiontsAC           would sometimes print an unwanted form feed after a print B           job. This unwanted behavior occurred under the following           conditions:n  5           o  The print job ends at the end of a page.a  C           o  A file printed with the /PASSALL qualifier ends with a               form feed.   B           The symbiont has been modified to eliminate the unwanted           form feeds.        3.4.2.2 Form/Stock Mismatchl  >     V6.2  Beginning with OpenVMS Alpha Version 1.5 and VMS VAX@           Version 5.5, a print job could unexpectedly be pendingB           due to a stock-type mismatch. The stock on the print jobB           matched the stock on the mounted form; however, a stock-:           type mismatch was reported by the queue manager.  &           This problem has been fixed.  %     3.4.2.3 LAT Initialization Timinga  B     V6.2  In OpenVMS Version 6.1, starting a LAT queue might causeB           a symbiont process crash, leaving the queue in a stoppedC           state and causing a process dump (SYS$SYSTEM:LATSYM.DMP). ?           Symbiont processes can handle many print queues. This B           problem would only occur when starting a queue created a           new symbiont process.o  &           This problem has been fixed.         3-16 r         I                                           System Management Release NotesVH                                     3.4 Batch and Print Queue Management    0         3.4.2.4 Memory Leak in Modified Symbiont  B         V6.2  In previous versions, when a modified print symbiontE               contained a combination of a user-written input routinebI               and a user-written format routine, memory leaks occurred insH               the modified print symbiont. The symbiont would eventually/               abort with the following message:i  >               %JBC-E-WRISMBMBX, error writing symbiont mailbox.               SYSTEM-W-MBFULL, mailbox is full;               -STR-F-INSVIRMEM, insufficient virtual memory   .               This problem has been corrected.  0         3.4.2.5 STS$V_INHIB_MSG in Return Status  C         V6.2  In previous versions, when a batch job exited with anPF               error status and the inhibit message flag was set in theH               return status, the error message was displayed in the job-.               completion notification message.  H               This problem has been fixed. Now, if the flag STS$V_INHIB_C               MSG is set in the return status, the error message is 5               suppressed in the notification message.            3.5 DCL Commands  B               This section contains information about DCL commands/               commonly used by system managers.   &         3.5.1 Changes and Enhancements  D               This section describes changes and enhancements to DCL8               commands commonly used by system managers.  1         3.5.1.1 ANALYZE/ERROR_LOG/SUMMARY Command   C         V6.2  The /SUMMARY qualifier is no longer supported for the (               ANALYZE/ERROR_LOG command.  *         3.5.1.2 MOUNT/UCS_SEQUENCE Command  A         V6.2  ISO 9660 volumes might contain Supplementary Volume F               Descriptors (SVDs) that specify a graphic character set.D               When selected when the volume is mounted, this graphicD               character set is used as the default character set forA               displaying the volume's directories and file names.e  I                                                                      3-170           #     System Management Release Notes      3.5 DCL Commands    D           The /UCS_SEQUENCE=(escape_sequence) qualifier to the MOUNTB           command supplies the escape sequence to select the codedC           graphic character set, which is required when mounting an .           ISO 9660 volume for one of its SVDs.  B           All ISO 9660 volumes contain a Primary Volume DescriptorC           (PVD) that uses ASCII (ISO 646-IRV) as the character set.AC           Both ISO 9660 and OpenVMS file-naming conventions use theiD           same subset of ASCII characters when displaying a volume's%           directories and file names.        3.5.2 Correctionse  C           This section describes corrections to problems associatedf=           with DCL commands commonly used by system managers.   1     3.5.2.1 ANALYZE/DISK_STRUCTURE/REPAIR Command   A     V6.2  In previous versions of OpenVMS, the following problems            existed:  A           o  If you ran ANALYZE/DISK_STRUCTURE/REPAIR on a device B              that was write-locked, the command sometimes unlocked'              the device before exiting.e  B           o  If you used STOP/IDENTIFICATION=pid to stop a processD              while it was running ANALYZE/DISK_STRUCTURE/REPAIR on a6              device, the device remained write-locked.  1           These problems have now been corrected.   +     3.5.2.2 SET ACCOUNTING/NEW_FILE Command   ?     V6.2  Previously, when all account events were disabled andlA           there were no accounting files, the SET ACCOUNTING/NEW_.9           FILE command would create two accounting files.   *           This problem has been corrected.  /     3.6 DECdtm Services in a DECnet/OSI Networka  D           This section contains notes pertaining to DECdtm services.  #     3.6.1 Problems and Restrictions   @           This section describes known problems and restrictions0           associated with using DECdtm services.       3-18           I                                           System Management Release Notes I                               3.6 DECdtm Services in a DECnet/OSI Networkm    (         3.6.1.1 Assigning SCSNODE Values  E         V6.1  Read this section if all of the following apply to you:m  /               o  You have a DECnet/OSI network.   )               o  You use DECdtm services.6  C               o  Your DECdtm transactions span different VMScluster 1                  systems or standalone computers.d  F               SCSNODE is a system parameter that defines the name of aH               computer. DECdtm transactions can fail if the same SCSNODE7               value is used for more than one computer.r  H               Make sure the same SCSNODE name is not duplicated on other1               computers by following these steps:l  A               1. Make a note of the computers that belong to yourrE                  transaction group. A transaction group is a group ofUB                  computers involved in DECdtm transactions, where:  E                  o  A computer belongs to only one transaction group.s  F                  o  Every computer in a VMScluster belongs to the same&                     transaction group.  D                  o  Computers A and B belong to the same transactionC                     group if any transaction on computer A involves                      computer B.   D                  o  Computers A and C belong to the same transactionC                     group if any transaction on computer A involvesxD                     computer B, and any transaction on computer B orC                     any node in B's VMScluster involves computer C.e  D                  Figure 3-1 shows an example of a transaction group.  G               2. For each computer in your transaction group, make sureo:                  that the SCSNODE value is different from:  @                  o  The SCSNODE values of other computers in the%                     transaction group   D                  o  DECnet synonyms of other computers in the entire                     networkf  F                  o  DECnet simple names of other computers on the same                     local root  I                                                                      3-19  _  _      #     System Management Release Notes_/     3.6 DECdtm Services in a DECnet/OSI Networkr    D           3. If the computer is part of a VMScluster, also make sure6              that the SCSNODE value is different from:  B              o  DECnet simple names of other computers in the same                 VMScluster  B              o  DECnet simple names of computers on the same local0                 root as other VMScluster members  @           For information on how to find out DECnet synonyms andC           DECnet simple names, see the DECnet/OSI DECdns Management B           manual. For information on how to find out or change the@           SCSNODE name, see the OpenVMS System Manager's Manual.  &           Figure 3-1 Transaction Group            :           Note the following in the example in Figure 3-1:  E           o  Transactions on a computer in cluster FRED involve other_@              computers in cluster FRED and a computer in cluster              BILL.  ?           o  Transactions on a computer in cluster BILL involvee$              standalone machine TOM.  >           o  No other computers in the network are involved inB              transactions with computers in clusters FRED or BILL,-              or with standalone computer TOM.   @           Therefore, the computers in the transaction group are:  *              All computers in cluster FRED*              All computers in cluster BILL              Computer TOM                  3-20 t  r      I                                           System Management Release NotesmI                        3.7 DECevent Fault Management Support (Alpha Only)s    :         3.7 DECevent Fault Management Support (Alpha Only)           V6.2  I               Beginning with OpenVMS Alpha Version 6.2, DECevent replacesoD               the Error Reporting Formatter (ERF) as the bit-to-textD               translating tool for fault management on OpenVMS AlphaG               systems. While the ERF is still available on Version 6.2, H               it will be retired in future releases of the OpenVMS Alpha               operating system.   '         3.7.1 Problems and RestrictionsC  I               This section describes problems and restrictions related toi7               using the DECevent fault management tool.   /         3.7.1.1 Bit-to-Text Translation Supportm  C         V6.2  DECevent bit-to-text translation is supported on manynI               products and devices. On other devices, as much translationuG               as possible is performed and all remaining information inn1               the event is dumped in hexadecimal.t  E               Contact your Digital support representative if you haveeD               questions about the type of DECevent support currently)               available for your devices.            3.7.1.2 Ctrl/C  @         V6.2  After pressing Ctrl/C, you must also press Return./               Otherwise, no prompt is returned.e  2         3.7.1.3 Log Files Not Purged Automatically  E         V6.2  DECevent does not automatically purge log files. Either H               purge them manually or set version limits on the files and%               directory. For example:a  3               $ SET FILE/VERSION=3 DIA_ACTIVITY.LOGm  "         3.7.1.4 Logical File Names  B         V6.2  DECevent is unable to translate as input any logicalB               defined as a search list of file names. For example:  O     $define event_log disk1:[events]event_log1.sys,disk1:[events]event_log2.sys      $dia/analyze event_log  I                                                                      3-21s e         #     System Management Release Notesa6     3.7 DECevent Fault Management Support (Alpha Only)               DECevent T1.0 FT2a?           _DIAGNOSE-FAT: Analyze - No files found ' event_log ' L           _DIAGNOSE-FAT: An error occurred while executing a command ruleset>           _DIAGNOSE-INF: No Error Messages to send in thread 1       3.7.1.5 Page File Quotaa  @     V6.2  The possibility exists that DECevent will fail with anA           access violation if the page file quota is exceeded. If C           this happens, the process terminates and you are returned E           to the system prompt. You can then reenter the last failingK           command.  +     3.7.1.6 Unrecognized Error Log Messageso  D     V6.2  The DIAGNOSE command does not recognize error log messages3           logged using the $SNDERR system service. n  +     3.8 DECnet for OpenVMS Alpha (Phase IV)o  9           The following sections describe new support andrD           restrictions that apply to DECnet for OpenVMS Alpha (PhaseD           IV). For information about using DECnet/OSI (Phase V), see'           the DECnet/OSI documentation.t  #     3.8.1 Problems and Restrictions   @     V1.5  The following restrictions apply to DECnet for OpenVMS           Alpha:  B           o  Level 1 routing is available but is supported only onA              DECnet for OpenVMS Alpha nodes acting as routers for B              a cluster alias. Routing between multiple circuits orD              having more than one routing circuit enabled at once is              not supported.   C           o  Level 2 routing is not supported on DECnet for OpenVMST              Alpha nodes.t  -           o  Some line types are unsupported.   C              DECnet for OpenVMS Alpha nodes can connect to a DECnet B              network only via Ethernet lines or FDDI lines. DECnetE              communication over CI lines is not supported. There alsot+              is no support for DDCMP lines.i  A              Because DDCMP lines are unsupported, the DCL commandp@              SET TERMINAL /PROTOCOL=DDCMP /SWITCH=DECNET also is+              unsupported on Alpha systems.         3-22 t  ,      I                                           System Management Release NotestH                                    3.9 DECnet for OpenVMS VAX (Phase IV)    -         3.9 DECnet for OpenVMS VAX (Phase IV)   =               The following sections describe new support and.F               restrictions that apply to DECnet for OpenVMS VAX (PhaseH               IV). For information about using DECnet/OSI (Phase V), see+               the DECnet/OSI documentation.L  &         3.9.1 Changes and Enhancements  C               The following section describes changes to DECnet forp%               OpenVMS VAX (Phase IV).a  0         3.9.1.1 DEFQA Now Can Be Configured with)                 SYS$MANAGER:NETCONFIG.COMo  D         V6.2  The DEC FDDIcontroller/Q-bus Controller (DEFQA) is now=               supported by DECnet for OpenVMS VAX (Phase IV).   B               The DEFQA can now be configured using the DECnet forC               OpenVMS VAX NETCONFIG.COM procedure. The NCP LINE and H               CIRCUIT name for the DEFQA is FQA-n, where n is the numberG               representing the controller; for example, line FQA-0 maps @               to device FQA0 and line FQA-1 maps to device FQB0.  D               If you previously had the following logical defined inE               SYS$MANAGER:SYCONFIG.COM in order to use this device on G               OpenVMS VAX Version 6.1, you must remove the logical fromgI               SYCONFIG.COM and deassign it before configuring the device.,I               This logical is no longer necessary to configure the DEFQA.p  (               $ DEFINE/SYSTEM FXc0 FQc0:  '         3.9.2 Problems and Restrictionso  I               The following section describes a restriction pertaining ton0               DECnet for OpenVMS VAX (Phase IV).  I         3.9.2.1 DEFTA Cannot Be Configured with SYS$MANAGER:NETCONFIG.COM   =         V6.1  DECnet for OpenVMS VAX cannot configure the DEC.=               FDDIcontroller/TURBOchannel Controller (DEFTA).c  E               To use DECnet for OpenVMS with the DEFTA on OpenVMS VAX B               Versions 6.1 and 6.2, you must define a logical nameG               before invoking the NETCONFIG.COM or STARTNET.COM command E               procedures. Use the following DCL command to define the $               required logical name:  (               $ DEFINE/SYSTEM FZc0 FCc0:  I                                                                      3-23            #     System Management Release Notese)     3.9 DECnet for OpenVMS VAX (Phase IV)i    D           In this command, c represents the controller (for example,>           FCA0). To make the definition permanent, define this3           logical name in SYS$MANAGER:SYCONFIG.COM.o  C           The NCP LINE and CIRCUIT name for the DEFTA controller is.C           FZA-n, where n is the number representing the controller;tD           for example, line FZA-0 maps to device FZA0 and line FZA-1           maps to device FZB0. e  -     3.10 DECnet/OSI for OpenVMS VAX (Phase V)r  <           The following sections contain notes that apply toD           DECnet/OSI (Phase V). For complete information about using7           DECnet/OSI, see the DECnet/OSI documentation.5  #     3.10.1 Changes and Enhancementsp  @           The following section describes changes to DECnet/OSI.  -     3.10.1.1 DEFQA Now Can Be Configured with *              SYS$MANAGER:NET$CONFIGURE.COM  @     V6.2  The DEC FDDIcontroller/Q-bus Controller (DEFQA) is now<           supported by DECnet/OSI for OpenVMS VAX (Phase V).  C           The DEFQA can be configured by DECnet/OSI for OpenVMS VAXg@           using the NET$CONFIGURE.COM procedure. For information@           on how to configure devices using DECnet/OSI, refer toC           the DECnet/OSI for OpenVMS Installation and Configurationl           manual..  @           If you previously had the following logical defined inA           SYS$MANAGER:SYCONFIG.COM in order to use this device onhC           OpenVMS VAX Version 6.1, you must remove the logical from E           SYCONFIG.COM and deassign it before configuring the device. E           This logical is no longer necessary to configure the DEFQA.   $           $ DEFINE/SYSTEM FXc0 FQc0:  -     3.10.1.2 DEFTA Now Can Be Configured withr*              SYS$MANAGER:NET$CONFIGURE.COM  C     V6.2  The DEC FDDIcontroller/TURBOchannel Controller (DEFTA) ist@           now supported by DECnet/OSI for OpenVMS VAX (Phase V).  C           The DEFTA can be configured by DECnet/OSI for OpenVMS VAXr@           using the NET$CONFIGURE.COM procedure. For information@           on how to configure devices using DECnet/OSI, refer to       3-24           I                                           System Management Release NoteslI                                 3.10 DECnet/OSI for OpenVMS VAX (Phase V)     G               the DECnet/OSI for OpenVMS Installation and Configuration                manual.d  D               If you previously had the following logical defined inE               SYS$MANAGER:SYCONFIG.COM in order to use this device ontC               OpenVMS Version 6.1, you must remove the logical from I               SYCONFIG.COM and deassign it before configuring the device.eH               This logical is no longer necessary to configure the DEFTA               using DECnet/OSI.   )               $ DEFINE/SYSTEM FZc0 FCc0:    )         3.11 DECwindows Motif for OpenVMSe  C               This section contains release notes pertaining to the ;               DECwindows Motif for OpenVMS layered product.D  '         3.11.1 Changes and Enhancements   C               This section includes notes about support for the the ;               DECwindows Motif for OpenVMS layered product.   9         3.11.1.1 DECwindows Motif Version 1.1 for OpenVMS   E         V6.2  OpenVMS Version 6.2 is the final version of the OpenVMStF               operating system to support DECwindows Motif Version 1.1G               for OpenVMS. Future versions of OpenVMS will require thatmA               DECwindows Motif Version 1.2 or later be installed.t  <         3.11.1.2 NCSA Mosaic Browser: TCP/IP Support Options  E         V6.2  DECwindows Motif Version 1.2-3 includes the NCSA Mosaic A               web browser. The DECwindows Motif Version 1.2-3 forgF               OpenVMS Release Notes state that the NCSA Mosaic browserI               requires that the TCP/IP Services for OpenVMS product (UCX)eC               be installed on your system. Note that TCP/IP support,B               can alternatively be provided by PathWay for OpenVMS9               (Wollongong) or TCPware (Process Software).a  (         3.11.2 Problems and Restrictions  I               This section describes problems and restrictions associated D               with the DECwindows Motif for OpenVMS layered product.    I                                                                      3-25m           #     System Management Release Notesc%     3.11 DECwindows Motif for OpenVMSa    (     3.11.2.1 Console Broadcasts Disabled  ;     V6.2  In Version 1.2-3, console broadcasts are disabledU;           by default by the DECwindows startup procedure onM:           nonworkstation systems as well as on workstation>           systems. To allow broadcasts to OPA0:, edit the fileA           SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM (creating it if @           it does not exist) and add the following global symbol           definition:   .           $ DECW$CONSOLE_SELECTION == "ENABLE"  E           Then, restart DECwindows by entering the following command:n  -           $ @SYS$MANAGER:DECW$STARTUP RESTART   A           On workstation systems, Digital recommends that you set B           DECW$CONSOLE_SELECTION to WINDOW instead of ENABLE. ThisA           directs console output to a Console Window application, D           which is new in DECwindows Motif V1.2-3, instead of to the1           operator window on the graphics screen.m  /     3.11.2.2 System Files Purged During Startups  E     V6.2  In Version 1.2-3, the following DECwindows files are purgede,           each time DECwindows Motif starts:  #              SYS$LIBRARY:DECW$*.EXEo*              SYS$SYSTEM:DECW$SETSHODIS.EXE  4     3.11.2.3 Virtual Data Error Message (Alpha Only)  D     V6.2  In Version 1.2-3, the following error message is displayed?           on nonworkstation OpenVMS Alpha systems during system            startup:  J           %SDA-E-NOTINPHYS, 00000024 : virtual data not in physical memory  '           You can ignore this message.    5     3.11.2.4 World Wide Support Requires Remedial Kit   >     V6.2  Before you upgrade to OpenVMS Version 6.2 on systems@           that run language variant versions of DECwindows MotifB           Version 1.2, you should first install a remedial kit for?           DECwindows Motif Version 1.2 World Wide Support. This E           patch is necessary because the internationalization supportrB           provided in OpenVMS Version 6.2 is incompatible with the2           support in DECwindows Motif Version 1.2.       3-26           I                                           System Management Release NotesaH                                        3.11 DECwindows Motif for OpenVMS    H               The name of the remedial kit is DWMV_I18N01_012 on VAX andF               DWMA_I18N01_012 on Alpha. If you install OpenVMS VersionF               6.2 from the CD-ROM, the remedial kit will be on the CD-F               ROM; otherwise you must obtain the kit from your Digital%               support representative.f  F                 ________________________ Note ________________________  <                 Systems running language variant versions ofC                 DECwindows Motif Version 1.2 should not be upgradediD                 to DECwindows Motif Version 1.2-3 until a World WideB                 Support kit becomes available for DECwindows Motif                 Version 1.2-3.  F                 ______________________________________________________  C         3.11.2.5 DECwindows Motif Version 1.2 Compatibility Problemt  G         V6.2  DECwindows Motif Version 1.2 issues the following warning D               message when it encounters compatibility problems with"               OpenVMS Version 6.2:  N         X Toolkit Warning: locale not supported by C library, locale unchanged  D               In some cases, applications can also terminate with an               ACCVIO status.  @               A new system logical name has been introduced as aI               temporary workaround to prevent this problem from occurringeF               when running DECwindows Motif Version 1.2-3. The logicalI               name definition is included in VMS$LPBEGIN-050_STARTUP.COM:e  3               $ DEFINE/SYSTEM DECW$USEXLIBXPG4 TRUEr  I               Using this system logical name enables applications to worksE               as they have in the past. However, defining the logicaleA               name has no effect on DECwindows Motif Version 1.2.t  D               Therefore, if you have upgraded to OpenVMS Version 6.2F               and are running DECwindows Motif Version 1.2 and are notE               running a language variant of DECwindows Motif, DigitalsB               recommends that you also upgrade to DECwindows Motif               Version 1.2-3.  I               Alternatively, you can work around this problem by applyingrE               a remedial kit to DECwindows Motif Version 1.2. ContactuH               your Digital support representative for the following kitsE               that add support for the DECW$USEXLIBXPG4 logical name:   I                                                                      3-27a c  n      #     System Management Release Notes %     3.11 DECwindows Motif for OpenVMSr  4                                           Kit Number  ?           Platform    For Base Product    For WorldWide Support   9           Alpha       AXPMOTF05_012       DWMA_I18N01_012e  9           VAX         VAXMOTF05 012       DWMV I18N01 012   C     3.11.2.6 DECwindows Server Height or Width Exceeding 32767 (VAX               Only)       V6.1  C           When an X application sends the display server a width or B           height greater than 32767, the application may terminate9           with a BadValue error similar to the following:   K            X error event received from server: BadValue (integer parameter t&            out of range for operation)=              Major opcode of failed request: 61 (X_ClearArea) 0              Value in failed request: 0xffff****1              Serial number of failed request: ### 8              Current serial number in output stream: ###  5           The following calls can cause this problem:                 CopyArea()i              CreateWindow ()              PutImage()l              GetImage()-              CopyPlane()              ClearArea()  @           This is due to the width and height being defined as aE           signed word by the display server when it should be defined C           as an unsigned word (CARD16) that allows for values up to            65536.  ?           To modify the default operation perform the followingt           steps:  A           1. Set the logical name DECW$CARD16_VALIDATE to TRUE ast              follows:   K               $DEFINE/TABLE=DECW$SERVER0_TABLE   DECW$CARD16_VALIDATE  TRUE   .           2. Exit the session and log back in.       3-28 w  ,      I                                           System Management Release Notes H                                        3.11 DECwindows Motif for OpenVMS    G                  Exiting the session causes the display server to reset E                  using the new value of the logical name DECW$CARD16_DE                  VALIDATE. The server will now accept values that are @                  greater then 32767 without generating an error.  H               To make this a permanent change, add the command from StepF               1 to the file SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM.  B         3.11.2.7 SET DISPLAY Used to Create WSA Pseudo Workstation                  Devices  D         V6.1  When creating WSA pseudo workstation devices using theG               SET DISPLAY command, be careful not to create WSA devices E               that are never destroyed. For example, this DCL command !               procedure is wrong:w                  $LOOP:r0                $  SET DISPLAY/CREATE/NODE=remote+                $  RUN SYS$SYSTEM:DECW$CLOCK +                $  IF $STATUS THEN GOTO DONEa                $  WAIT 0:0:5                $  GOTO LOOP                 $DONE:e  E               If the clock cannot be started for some reason, one WSArC               device will be created for each failed attempt. ThesesC               WSA devices will use up non-paged dynamic memory, andMD               eventually the process will exceed its BYTLM quota andA               enter a resource wait state (if resource waiting is ,               enabled, as it is by default).  ?               A better version of this command procedure is the                following:  0                $  SET DISPLAY/CREATE/NODE=remote                $LOOP:u+                $  RUN SYS$SYSTEM:DECW$CLOCK +                $  IF $STATUS THEN GOTO DONEe                $  WAIT 0:0:5                $  GOTO LOOPs                $DONE:e?                $  SET DISPLAY/DELETE 'F$TRNLNM("DECW$DISPLAY")'l      I                                                                      3-29  t         #     System Management Release Notes %     3.11 DECwindows Motif for OpenVMS     D           The SET DISPLAY/DELETE command deletes the WSA device that@           was created at the beginning of the command procedure;D           the logical name DECW$DISPLAY contains the name of the WSA"           device that was created.  D     3.11.2.8 DECwindows Motif Start Session Dialog Box Not Displayed2              After Rebooting the System (VAX Only)  B     V6.0  Occasionally when you reboot a system running DECwindowsB           Motif Version 1.1 software on OpenVMS VAX Version 6.0 or?           later, the Start Session dialog box does not display.   A           Usually you can work around the problem by entering the 6           following command from a privileged account:  *           $ @SYS$MANAGER:DECW$STARTUP APPS  D           To resolve the problem, order DECwindows Motif for OpenVMSD           Version 1.2-3 or the latest available version or contact aD           Digital support representative to obtain patch kit CSCPAT_:           1090 for DECwindows Motif Version 1.1 software.   &     3.12 Help Message Utility (MSGHLP)  D           This section contains release notes pertaining to the Help#           Message utility (MSGHLP).   $     3.12.1 Problems and Restrictions  E           This section describes problems and restrictions related to )           using the Help Message utility.   5     3.12.1.1 User-Supplied Comments Are Not Preserved   D     VAX   Currently, user-supplied comments or additions to Digital-C     V6.0  supplied .MSGHLP$DATA files will not be preserved throughpD     Alpha the next upgrade. However, your own .MSGHLP$DATA files are#     V1.0  not affected by upgrades.   B           Note that you can reuse .MSGHLP files to insert your own?           messages into future Digital-supplied database files. A           Depending on the content of future databases, you might E           also be able to reuse some .MSGHLP files to add comments to            existing messages.       3-30    i      I                                           System Management Release NoteseI                                                 3.13 InfoServer MADDRIVERo    !         3.13 InfoServer MADDRIVERs  G               This section contains a note pertaining to the InfoServern               MADDRIVER.  (         3.13.1 Problems and Restrictions  E               The following section describes an InfoServer MADDRIVER                restriction.  >         3.13.1.1 Magnetic Tapes Are Not Supported (Alpha Only)  G         V6.2  OpenVMS Alpha Version 6.2 does not support magnetic tapesAG               served by the InfoServer. A remedial kit will be suppliedr:               in the near future to support this function.  G                 _______________________ Caution _______________________   F                 Until you can install the remedial kit, do not attemptD                 to load the existing MADDRIVER. Using it could cause&                 your system to crash.   F                 ______________________________________________________           3.14 INITIALIZEE  D               This section describes notes pertaining to INITIALIZE.  (         3.14.1 Problems and Restrictions  D               The following section describes an INITIALIZE problem.  D         3.14.1.1 Recovery of Badly Initialized Root Directory (Alpha                  Only)  H         V6.1  In the Software Developer Toolkit (SDK) version of OpenVMSG               Alpha Version 6.1, INITIALIZE did not initialize the rootoC               directory of a volume, 000000.dir correctly. This badpE               initialization could cause the directory entry for thiseI               file to be deleted, and also prevent you from being able toe%               set ACLs on 000000.dir.   I                                                                      3-31I h         #     System Management Release Notes      3.14 INITIALIZEe    @           To tell whether you have a disk that has suffered fromE           this, use the ANALYZE/DISK_STRUCTURE command on the disk. A D           new warning message has been added to flag this condition:  K           %ANALDISK-W-BADINITD_MFD, Root directory 000000.DIR;1 file headerF(           incorrectly initialized, RVN 1  A           Use the ANALYZE/DISK_STRUCTURE/REPAIR command to repaire"           this bad initialization.  A           If the directory entry for 000000.dir has been deleted, B           then use ANALYZE/DISK_STRUCTURE/REPAIR to repair this asC           well. You will receive the following warning from ANALYZE C           /DISK_STRUCTURE if this directory entry has been deleted:e  O     %ANALDISK-W-LOSTHEADER, file (4,4,1) 000000.DIR;1 not found in a directory    "     3.15 Install Utility (INSTALL)  ?           This section contains release notes pertaining to thef$           Install utility (INSTALL).  #     3.15.1 Changes and Enhancementso  5           This section describes a change to INSTALL.F       3.15.1.1 Installing Images  <     V6.2  The REPLACE option for the OpenVMS Install utility=           (INSTALL) has been changed to modify the known fileE(           database in an atomic fashion.  @           In the past, REPLACE was equivalent to DELETE followedC           by ADD. Consequently, there was a short time during whichRA           neither the new nor the old image was in the known fileiC           database. When activating protected or privileged images, A           this could result in failed image activations. Also, if C           the new image could not be installed, it was possible for E           neither the old nor the new image to be installed after ther           failure.  +           These problems are now corrected.a  B           With the change, REPLACE operations for images installed>           with the /SHARED qualifier might require more global>           sections or global pages than in the past. Also, theD           names of global sections have been changed to avoid namingE           conflicts. The global sections can be displayed with one of !           the following commands:        3-32 E  Z      I                                           System Management Release NotescI                                            3.15 Install Utility (INSTALL)t    $               $ INSTALL LIST /GLOBAL                 or  /               $ INSTALL LIST image-name /GLOBALe  .         3.16 License Management Facility (LMF)  A               This section contains information about the LicenseC(               Management Facility (LMF).  (         3.16.1 Problems and Restrictions  D               This section describes a restriction pertaining to the0               License Management Facility (LMF).  .         3.16.1.1 PAKs on Alpha and VAX Systems  @         VAX   Availability Product Authorization Keys (PAKs) areB         V6.0  available for OpenVMS Alpha. An OpenVMS Alpha PAK isH         Alpha identified by the keyword ALPHA in the PAK's option field.         V1.0B               PAKs having the ALPHA option will be loaded and usedD               only on Alpha systems. However, they can safely resideF               in a license database (LDB) shared by both VAX and Alpha               systems.  B               Availability PAKs for VAX systems (availability PAKsG               without the ALPHA option) will not load on Alpha systems.PF               Only those availability PAKs containing the ALPHA option)               will load on Alpha systems.   I               Other PAK types, such as activity (also known as concurrent E               or n-user) and personal use (identified by the RESERVE_ @               UNITS option), work on both VAX and Alpha systems.  G                 _______________________ Caution _______________________e  E                 By default, all Alpha availability PAKs look disablede>                 to a system running OpenVMS VAX Version 6.0 orE                 earlier. Never use the DELETE/STATUS=DISABLED command @                 from a system running OpenVMS VAX Version 6.0 orB                 earlier on an LDB that contains Alpha PAKs. If you3                 do, all Alpha PAKs will be deleted.   F                 ______________________________________________________  H               See the OpenVMS License Management Utility Manual for more*               information about using LMF.  I                                                                      3-33e           #     System Management Release Notese-     3.17 Monitoring Performance History (MPH)u    -     3.17 Monitoring Performance History (MPH)h  C     V6.2  Digital invites you to participate in the Digital Productr@           Performance (DPP) program, which monitors and verifiesA           in-field performance of Digital systems at customer and ?           Digital sites. This program provides Digital service,fB           manufacturing, and design engineering organizations with?           accurate information about the performance of Digitalg?           products. Digital's goal is to provide customers with 6           improved reliability on all Digital systems.  A           To ensure the high quality of its products, Digital hasE>           developed a system monitoring tool called MonitoringA           Performance History (MPH). MPH resides on participants'uE           systems with negligible impact on system performance and no $           impact on system security.  C           MPH collects error log entries, crash dump summaries, and.A           configuration information from monitored systems. EverysA           week the information is sent to the DPP group using thecE           selected transport mechanism, which can include DSNLink and &           Internet mail, among others.  >           DPP analyzes the collected information and generatesE           reports that are distributed to engineering, manufacturing,g9           and services groups. These groups evaluate this @           information in an effort to improve system reliabilityC           and availability. All collected information is classified8D           as Digital Confidential and is held for internal use only.  A           The MPH process, with the exception of installation, is;B           fully automated. MPH runs as a background task utilizingB           negligible system resources. The disk space required forE           the collected data and the application is approximately 300a           blocks per system.  =           MPH is a voluntary program that requires no special -           maintenance agreement with Digital.   '           MPH Kit Location on the Media   A           The MPH kit and installation guide are in the following..           OpenVMS Version 6.2 media locations:  0           o  Volume 3 of the magnetic tape media  '           o  Volume 2 of the TK50 mediar  0           o  Directory [MPH] of the CD-ROM media       3-34 l  n      I                                           System Management Release Notes I                                 3.17 Monitoring Performance History (MPH)                    Installing MPH  I               You install MPH by using VMSINSTAL. The installation manualnH               is in the MPH kit and can be extracted in either text form!               or POSTSCRIPT form.   G               o  To extract the installation manual in text form, enter '                  the following command:   O             $ BACKUP/SELECT=MPH_VMS_INSTALL_GUIDE.TXT MPH_VMS011.A /SAVE [].TXTA  I               o  To extract the information in POSTSCRIPT form, enter the #                  following command:e  M             $ BACKUP/SELECT=MPH_VMS_INSTALL_GUIDE.PS MPH_VMS011.A /SAVE [].PSf                 Stopping MPH  F               You can stop MPH on your systems at any time by entering               this command:e  -               $ @SYS$MANAGER:MPH$SHUTDOWN.COMu                 Deinstalling MPH  I               You can deinstall MPH at any time by entering this command:i  -               $ @SYS$MANAGER:MPH$DEINSTAL.COMg  @               New Features in Version 1.1 of the OpenVMS MPH Kit  G               The following new features are included in Version 1.1 of "               the OpenVMS MPH kit:  C               o  MPH now offers you the opportunity to upgrade yourt'                  existing installation.   E               o  Error log data can be collected on a weekly or daily                   basis.   I               o  Customer questions asked during the installation processsI                  have been updated to retrieve more accurate information.   C               o  Internet users can now use an Internet gateway, if                   required.  F               o  MPH now performs space management to ensure it has noE                  impact on your system, regardless of error log size.w  E               o  The MPH directory is no longer required to be a top- !                  level directory.t  F               o  MPH invokes the Crash Log tool (CRL) if the Crash LogG                  Utility Extractor (CLUE) is not running on the system.a  I                                                                      3-35u i  g      #     System Management Release Notes -     3.17 Monitoring Performance History (MPH)     B           o  Several new safeguards and warning messages have been%              introduced; for example:l  D              -  The system manager is notified if there are problems                 with DSNLink.a  C              -  The system manager is notified if the initial errorCE                 log is too large or if daily changes to the error log                  are large.  A           o  After installation on a cluster, monitored nodes cane@              be added or deleted by executing MPH$AREA:MPH$EDIT_              NODES.COM.   !           For more information...t  B           For additional information about MPH or the DPP program,           send mail to:f  )             mph_admin@dppsys.enet.dec.com   D           Include the keyword INFO anywhere in the subject header of;           your message to expedite routing of your request.E  =           Digital looks forward to your participation in thisn9           mutually beneficial program. Thank you for your            cooperation.  "     3.18 Monitor Utility (MONITOR)  <           The following notes pertain to the Monitor utility           (MONITOR).  #     3.18.1 Changes and Enhancementsp  @           This section describes changes to the Monitor utility.  !     3.18.1.1 Disk Limit Increased   C     V6.2  The limit on the number of disks that can be monitored on A           OpenVMS Version 6.2 has been raised from 799 to 909 for D           record output and from 799 to 1817 for display and summary>           outputs. If you are monitoring a remote node running>           OpenVMS Version 6.2 from a system running an earlier;           version of OpenVMS, the old limit of 799 applies.        3-36 s  i      I                                           System Management Release Notes I                                            3.18 Monitor Utility (MONITOR)     H         3.18.1.2 Display Header Changed From "VAX/VMS" To "OpenVMS" (VAX                  Only)  H         V6.2  The text in the first heading line for MONITOR display andH               summary output has been changed slightly. The heading lineI               "VAX/VMS Monitor Utility" used in previous VAX versions nowcE               reads "OpenVMS Monitor Utility" to match OpenVMS Alpha.eG               This change is a reflection of the functional equivalenceu+               of MONITOR on both platforms.   B               Any software that parses this line of the display orE               summary output of the MONITOR utility should be changed G               accordingly. This change does not affect MONITOR's binarys%               recording file output.    "         3.19 Mount Utility (MOUNT)  G               The following notes pertain to the Mount utility (MOUNT).Y  (         3.19.1 Problems and Restrictions  6               This note describes a MOUNT restriction.  E         3.19.1.1 ISO 9660 Support in Mixed-Version VMScluster SystemsI  G         V6.1  On OpenVMS systems, do not specify the /CLUSTER qualifier F               when mounting ISO 9660 formatted CD-ROMs in a VMSclusterH               system with nodes that are running versions of OpenVMS VAXG               prior to Version 6.0. If you attempt to mount an ISO 9660 G               CD-ROM on an OpenVMS node without ISO 9660 support, which E               is likely in a mixed-version environment, the operationeD               will fail. However, the failure will take an excessiveI               amount of time to complete, due to the slow access time for                the CD-ROM media.e           3.19.2 Corrections  C               This section describes software corrections to MOUNT.   C         3.19.2.1 Noncompliant ISO 9660 CD-ROMs and MOUNT (VAX Only)   A         V6.2  Previously, on OpenVMS VAX systems, support was not B               provided for mounting noncompliant ISO 9660 CD-ROMs.  I                                                                      3-37o M  f      #     System Management Release Notese     3.19 Mount Utility (MOUNT)    :           If users had noncompliant media and were running@           applications in a mixed-architecture VMScluster systemD           (OpenVMS Alpha Version 6.1 with either OpenVMS VAX Version@           6.0 or OpenVMS VAX Version 6.1), they could experienceB           problems. This was an issue for PATHWORKS users who wereE           using noncompliant ISO 9660 CD-ROMs in a mixed-architecture            VMScluster system.  +           This problem has been corrected. t       3.20 Nonpaged Pool  D           This section contains release notes pertaining to nonpaged           pool.S  $     3.20.1 Problems and Restrictions  C           This section describes software problems and restrictionss#           related to nonpaged pool.d  6     3.20.1.1 Prepopulation of Nonpaged Pool (VAX Only)  A     V6.2  Feedback from some sites suggests that prepopulation ofaA           the nonpaged pool lookaside lists can cause problems insC           some environments. For OpenVMS VAX Version 6.2 the SYSGENdA           parameter VMS7 is temporarily being used as a switch to !           turn off prepopulation.   E           If you experience any problems that you believe are related 9           to nonpaged pool prepopulation, set VMS7 to 1. .       3.20.2 Corrections  A           This section describes software corrections relating tor           nonpaged pool.  '     3.20.2.1 Nonpaged Pool Deallocationt  <     V6.2  In previous versions of OpenVMS, a problem existed@           that reduced the amount of free nonpaged pool and that:           occasionally caused the system to hang or crash.  D           If you exceed the version limit for a file, and the oldestC           version of the file is a file alias, then the file system            does the following:p  ?           1. Creates a directory entry for the new file versiono       3-38 _  _      I                                           System Management Release Notes I                                                        3.20 Nonpaged Pool     C               2. Removes the directory entry for the old file alias_  H               Each time this happens, a small amount of nonpaged pool is+               allocated to the file system.I  B               Previously, the file system failed to deallocate theD               nonpaged pool at the end of the operation. If the fileH               system performed this operation many times, the system ranH               out of nonpaged pool, causing the system to hang or crash.  .               This problem has been corrected.           3.21 OPCOM  E               The release notes in this section pertain to OPCOM, theT-               operator communication manager.u  (         3.21.1 Problems and Restrictions  I               The release notes in this section describe restrictions you 3               need to be aware of when using OPCOM.   "         3.21.1.1 OPERATOR.LOG File  D         V6.2  The size of and access to the OPERATOR.LOG file (or toE               the file pointed to by the logical OPC$LOGFILE_NAME) issH               limited by the size and access of the disk device on whichF               it resides. If the disk device does not have enough roomH               to write to the log file or if access to the device in anyH               other way is restricted, records might be missing from the               log file.E  5         3.22 POLYCENTER Software Installation Utilityt  A               The notes in this section pertain to the POLYCENTERtB               Software Installation utility. Also see Section 4.21B               for notes about this utility that are of interest to               programmers.  (         3.22.1 Problems and Restrictions  H               Notes in this section pertain to problems and restrictionsE               with using the POLYCENTER Software Installation utilitycD               to install, remove, and reconfigure software products.F               Problems and restrictions of interest to programmers are*               described in Section 4.21.1.  I                                                                      3-39S s  l      #     System Management Release Notesg1     3.22 POLYCENTER Software Installation Utility     >     3.22.1.1 Dependency Information Is Lost On Product Upgrade  ?     V6.2  When a software product is upgraded to a new version,r@           information about other products that are dependent on@           it is incorrectly removed from the POLYCENTER Software?           Installation utility database. Consider this example:   0           1. Product A Version 2.1 is installed.  A           2. Product B Version 1.0, which requires Version 2.0 or /              higher of product A, is installed.   >           3. Product A is upgraded to Version 2.2, causing theC              dependency of Product B on Product A to be erroneouslyd&              erased from the database.  E           To restore the dependency information, you must reconfigurepB           all products that are dependent on the upgraded product.C           Reconfiguration of an installed product requires that itsp<           software product kit be accessible to the utility.  @           For example, to restore the dependency information forC           Product B, shown in the above sequence, place Product B's C           software kit online and reconfigure Product B as shown inL&           the following code sequence:  B           $ PRODUCT SHOW PRODUCT A/FULL     ! A is referenced by BA           $ PRODUCT INSTALL A/VERSION=2.2/SOURCE=disk:[directory] D           $ PRODUCT SHOW PRODUCT A/FULL     ! no dependency is shown9           $ PRODUCT RECONFIGURE B/SOURCE=disk:[directory]cB           $ PRODUCT SHOW PRODUCT A/FULL     ! A is referenced by B  =           Digital expects to correct this problem in a futured           release.       3.22.1.2 PRODUCT Command  B           There are several problems with the DCL command PRODUCT:  >     V6.2  o  If the /SOURCE qualifier is not specified and theA              logical name PCSI$SOURCE is not defined, the PRODUCTsE              command does not use the default device and directory as C              documented; instead, a message reports an error in thec              device name.b  @              To avoid this problem, use the /SOURCE qualifier orE              define the logical name PCSI$SOURCE as the source devicehD              and directory for these PRODUCT subcommands: CONFIGURE,E              COPY, EXTRACT RELEASE_NOTES, FIND, INSTALL, RECONFIGURE,l"              and REGISTER PRODUCT.       3-40 y  ,      I                                           System Management Release NotesaH                            3.22 POLYCENTER Software Installation Utility    D               o  Commands such as PRODUCT FIND and PRODUCT SHOW thatF                  can display more than a screen of data do not supportG                  the /OUTPUT qualifier. As a result, displayed text canM'                  scroll off the screen.l  B         V6.1  o  The /DIRECTORY and /DEVICE qualifiers do not workB                  correctly on the PRODUCT SHOW OBJECT command. TheD                  utility either ignores them or provides output that/                  does not match the qualifiers.   I               o  The PRODUCT command can cause indexed and relative fileshG                  to be truncated during a package or install operation.mD                  To determine if a particular file is susceptible toG                  being truncated, use the DIRECTORY/SIZE=ALL command tosF                  examine the file. If the two sizes are the same, yourE                  file will not exhibit this problem. If the two sizesoI                  are not the same, perform the following SET FILE commandw/                  prior to a package or install:r  <                  $ SET FILE/END_OF_FILE file-in-question.dat  E                  This command should be issued only for an indexed oraH                  relative file, since the end-of-file (EOF) attribute is1                  meaningful for sequential files.s  C               Digital expects to correct all of these problems in aa               future release.   H         3.22.1.3 Deleting Directories Created by the POLYCENTER Software%                  Installation Utilityc  F         V6.1  If a directory is created as part of a product installedI               using the POLYCENTER Software Installation utility and thataI               directory is deleted manually, a reinstallation of the samerE               product will fail. The POLYCENTER Software InstallationmE               utility determines from its database that the directory I               should be there, so it does not issue the command to createhI               it. When the utility tries to reinstall the file, it fails.   E               Digital recommends that you not manually delete objectsoG               that were created by the POLYCENTER Software Installatione               utility.      I                                                                      3-41i           #     System Management Release Notesm1     3.22 POLYCENTER Software Installation Utilityt    ,     3.22.1.4 Inaccurate Disk Space Reporting  @     V6.1  The POLYCENTER Software Installation utility estimates@           the amount of disk space required for an installation.B           Sometimes this number is inaccurate, and an installationD           may fail due to lack of disk space even though the utility2           reports that there is enough disk space.  B           The utility also fails to check for enabled disk quotas.  ?           Digital expects to correct these problems in a future            release.  B     3.22.1.5 Installing an Earlier Version of an Installed Product  B     V6.1  If you attempt to install an earlier version (one with aD           lower version number) of an installed product, the utility@           displays a sequence of questions. The questions do notE           display the correct defaults; if you take the defaults, the C           utility attempts to install both versions. This causes an )           error similar to the following:   O           %PCSI-E-FAILCONF, failed to resolve conflicting requirements for files:           [000000]DEC-VAXVMS-XYZ-V0105--1.PCSI$DESCRIPTIONO           Terminating is strongly recommended.  Do you want to terminate? [YES]m  D           The following example shows how to answer the questions to'           install the version you want:L  7           1. The system displays the following message:T  O      %PCSI-E-CONREMHV, confirm removal of higher version of DEC AXPVMS XYZ V2.0g2              Do you want to take this action? [NO]  C              If you want the lower version, answer YES. If you want +              the higher version, answer NO.e  7           2. The system displays the following message:   +              Do you want to continue? [YES]   C              If you want the lower version, answer YES. If you want +              the higher version, answer NO.          3-42 M  G      I                                           System Management Release NotesMH                            3.22 POLYCENTER Software Installation Utility    -         3.22.1.6 Product Removal Restrictions   >         V6.1  Removing a product using the POLYCENTER SoftwareE               Installation utility results in the removal of accountsdB               created for that product. This happens regardless ofE               whether the SYSUAF.DAT file is shared by another systemr               disk.   E               The same problem exists with rights identifiers and the "               file RIGHTSLIST.DAT.  C               Digital expects to correct these problems in a futureM               release.  4         3.22.2 Documentation Changes and Corrections  @               This section describes changes to documentation ofA               the POLYCENTER Software Installation utility. Other F               documentation corrections of interest to programmers are*               described in Section 4.21.2.  F         3.22.2.1 POLYCENTER Software Installation Utility User's Guide  F         V6.2  Information formerly included in the POLYCENTER SoftwareD               Installation Utility User's Guide has been revised andD               incorporated into the OpenVMS System Manager's Manual:               Essentials.i  +         3.23 POLYCENTER Striping (VAX Only)   C               This section contains release notes pertaining to theD*               POLYCENTER Striping product.  '         3.23.1 Changes and Enhancements   C               This section describes the replacement for POLYCENTER                Striping.   @         3.23.1.1 StorageWorks RAID Software for OpenVMS Replaces$                  POLYCENTER Striping  E         V6.2  With OpenVMS Version 6.2, POLYCENTER VAX Striping is noiD               longer supported. The supported replacement product isB               StorageWorks RAID Software for OpenVMS. The StripingE               functionality in StorageWorks RAID Software for OpenVMSeE               is available to POLYCENTER VAX Striping customers at norH               charge. Please contact your Digital support representative1               for details of the migration plan. f  I                                                                      3-43     h      #     System Management Release Notesi     3.24 RMS Journaling.         3.24 RMS Journalingh  D           The following notes pertain to RMS Journaling for OpenVMS.  $     3.24.1 Problems and Restrictions  E           The following notes describe restrictions to RMS Journalingo           for OpenVMS.  ;     3.24.1.1 Remote Access of Recovery Unit Journaled Filesd  C     V6.1  Nodes that host recovery unit journaled files that are to.C           be accessed remotely from other nodes in the network mustoD           define SYS$NODE to be a Phase IV style node name. The node@           name specified by SYS$NODE must be known to any remoteE           node attempting to access the recovery unit journaled files C           on the host node, and must be sufficiently unique for the A           remote node to use this node name to establish a DECnete&           connection to the host node.  (     3.24.1.2 VFC Format Sequential Files  ?     VAX   You cannot update variable fixed-length control (VFC)hC     V5.0  sequential files when using before-image or recovery unitiD     Alpha journaling. The VFC sequential file format is indicated byD     V1.0  the symbolic value FAB$C_VFC in the FAB$B_RFM field of the           FAB.  @           Digital expects to remove this restriction in a future0           release of RMS Journaling for OpenVMS.       3.25 Securitya  B           This section contains release notes pertaining to system           security.   #     3.25.1 Changes and Enhancementst  B           This section contains changes and enhancements to system           security.O  '     3.25.1.1 Auditing Events (VAX Only)e  ?     V6.2  In previous versions of OpenVMS VAX, ill-formed audit ;           requests were recorded through the FATAL BUGCHECKt?           mechanism; that is, the system crashed when the auditSA           server detected an audit request that was not specifiedy           correctly.       3-44    h      I                                           System Management Release Notes I                                                             3.25 Securityi    F               A second method of handling ill-formed audit requests isG               now available on OpenVMS VAX. (This method was previouslymE               available on OpenVMS Alpha.) Instead of using the FATALvF               BUGCHECK mechanism, messages that describe what happened1               are recorded in the audit log file.   H               Both OpenVMS VAX and OpenVMS Alpha provide the auditing of4               ill-formed audit requests by default.            3.25.2 Corrections  G               This section describes software corrections pertaining toV               system security.  #         3.25.2.1 Intrusion Serviceso  H         V6.2  The checking of privileges for intrusion services has beenG               changed. Previously, the wrong privilege bit (SYSPRV) wass/               being checked on intrusion calls.   H               This problem has been corrected. The correct privilege bit(               (SECURITY) is now checked.  $         3.26 Shared Linkage Sections  F               This section contains notes pertaining to shared linkage               sections.   5         3.26.1 Problems and Restrictions (Alpha Only)   D         V6.1  If you want to use an alternate version of any libraryF               installed with shareable linkage, it is essential to useI               alternate (noninstalled) versions of all the libraries that I               call that library. The libraries that can be installed withmG               shared linkage are LIBOTS, LIBRTL, CMA$TIS_SHR, DPML$SHR,a               and DECC$SHR.e  7               The dependencies are in the order listed.o  4               For example, if you issue the command:  9               $ DEFINE DPML$SHR SYS$LIBRARY:DPML$SHR.EXE;p  3               then you must also issue the command:o  5               $ DEFINE LIBOTS SYS$LIBRARY:LIBOTS.EXE;   E               Failure to redefine all calling libraries may result in !               access violations.    I                                                                      3-45  n  a      #     System Management Release Notes      3.27 SORT32 Work Files         3.27 SORT32 Work Files  B           This section contains release notes pertaining to SORT32           work files.l  #     3.27.1 Changes and Enhancementso  A           This section describes SORT32 changes and enhancements.f  -     3.27.1.1 Files Now Have Directory Entriesl  >     V6.2  Starting with OpenVMS Version 6.1, SORT32 work filesB           were implemented as RMS temporary files to fix a problemE           wherein SORT32 work files remained if a sort was terminatedo?           abnormally. RMS temporary files do not have directory ;           entries and are automatically deleted by RMS upon @           file closure. Thus, if the SORT32 image was terminated8           abnormally, the work files were still deleted.  <           Unfortunately, this implementation caused a systemD           management restriction in that, without a directory entry,A           no access control information is available for the work A           files. Therefore, work files could be created only in a -           directory owned by the SORT32 user.r  >           Typically, for large sorts, the system manager wouldC           designate a large shared temporary disk area using accessnC           control mechanisms so that the general user would require A           only small disk quotas. The large work files, which are @           deleted at the end of the sort, would be placed in theA           temporary area. Without a directory entry, these access D           control mechanisms cannot be used and the work file cannot+           be created in the temporary area.u  D           Work files are now created as regular files with directoryB           entries. Reverting to the previous behavior and allowing<           the management freedom for work file placement wasA           considered more important than the occasional work file C           that was not deleted under abnormal conditions. Users canm@           manually delete any work files left after a sort image            terminates abnormally.  <           Infrequently, SORT32 might not be able to find the<           designated directory for the work file due to some=           unforeseen reason, such as a user error or hardwareeB           malfunction. In this case, SORT32 will attempt to createC           the work file as an RMS temporary file, possibly allowingiB           the sort to complete successfully. This is a convenience       3-46           I                                           System Management Release Notes I                                                    3.27 SORT32 Work Files     F               feature and was retained for compatibility with previous@               versions of SORT32. Alternatively, the creation ofD               SORT32 work files as RMS temporary files can be forcedG               by specifying a nonexistent directory for the location of                the work files.N  =         3.28 StorageWorks RAID Array 110 Subsystem (VAX Only)n  H               This section contains notes pertaining to the StorageWorks'               RAID Array 110 Subsystem.n  (         3.28.1 Problems and Restrictions  I               This section describes known problems and restrictions with 8               the StorageWorks RAID Array 110 Subsystem.  6         3.28.1.1 SHOW DEVICE Does Not Display Capacity  H         V6.1  On some VAX systems, the capacity of the StorageWorks RAIDF               Array 110 Subsystem is not displayed after you enter the(               following console command:                 >>> SHOW DEVICEo  F               Instead, the capacity displays as "...". (This is due toH               the current settings for spin up time in the EEPROM of the5               StorageWorks RAID Array 110 Subsystem.)   A               If you reenter the SHOW DEVICE command, the correcttF               capacity will be displayed. This will be corrected in an=               update to the DEC RAID OpenVMS VAX Utility Kit.f  <         3.28.1.2 TURBOchannel Devices: Booting Not Supported  @         V6.1  VAX workstations running the OpenVMS VAX operatingC               system do not provide support for system booting fromDE               a TURBOchannel device. You cannot, therefore, boot from D               a StorageWorks RAID Array 110 Subsystem connected to a)               TURBOchannel-SCSI adapter. o  '         3.29 System Dump Analyzer (SDA)E  E               The following notes pertain to the System Dump Analyzerf               (SDA).  I                                                                      3-47     .      #     System Management Release Notesr#     3.29 System Dump Analyzer (SDA)n    $     3.29.1 Problems and Restrictions  D           This section describes known System Dump Analyzer problems           and restrictions.s  '     3.29.1.1 EXAMINE Command (VAX Only)a       VAXaD     V6.0  If you make a mistake specifying a virtual address for the  A           EXAMINE command and you are examining global page table E           entries, your system may crash with a bugcheck. This occursi6           rarely and only when you use ANALYZE/SYSTEM.  +     3.30 System Management Utility (SYSMAN)O  ?           This section contains release notes pertaining to theR5           OpenVMS System Management utility (SYSMAN).   #     3.30.1 Changes and Enhancements   @           This section describes changes and enhancements to the5           OpenVMS System Management utility (SYSMAN).i       3.30.1.1 ALF Command  ?     V6.2  OpenVMS Version 6.2 includes changes to the following            SYSMAN ALF commands:             o  ADD             o  REMOVEe             o  SHOWs  :           The following are explanations of these changes:             ALF_ADD   =           When you create ALF records for proxy accounts, the B           <device-name> parameter can be as long as 63 characters.           For example:  G           SYSMAN> ALF ADD VMS:.ZKO.VMSORG.SYSMAN.CLIENT1::SYSTEM FOOBAR   D           In this command, VMS:.ZKO.VMSORG.SYSMAN.CLIENT1::SYSTEM is<           the value for the <device-name> command parameter.             ALF_REMOVE       3-48           I                                           System Management Release NotestI                                   3.30 System Management Utility (SYSMAN)t    H               Due to changes in the SHOW command, you can now use REMOVEH               commands to remove more than one ALF record at a time. For               example:  %               SYSMAN> ALF REMOVE TTA*t  G               This command removes all matching records that start with-E               the string TTA, but it does not remove any records that G               start with the string <nodename>$TTA, where <nodename> isFE               the system's SCSNODE name. To remove those records, you 5               must use one of the following commands:b  0               SYSMAN> ALF REMOVE <nodename>$TTA*  &               SYSMAN> ALF REMOVE *TTA*  G               Note that the latter command removes all matching records C               that contain the string TTA in the device name field. C               Similarly, the following command removes all matching H               records that have device names ending with the string TTA:  %               SYSMAN> ALF REMOVE *TTAL  G               If you omit either of the wildcard characters and enter aaG               REMOVE command, SYSMAN attempts to match the given device E               name exactly. If more than one record matches the giventE               criteria, SYSMAN returns an error message. For example,aE               the following command causes SYSMAN to match any recordt+               starting with <nodename>$TTA:   $               SYSMAN> ALF REMOVE TTA  @               This command produces the following error message:  I               %SYSMAN-E-ALFWILCRDREQ, more than one record might match - l9               Wildcard or unit number of device required.r  F                 ________________________ Note ________________________  D                 This message is new for OpenVMS Version 6.2. DigitalC                 recommends that you use caution when issuing REMOVE D                 commands from Version 6.1 or lower SYSMAN clients to.                 Version 6.2 or higher systems.  F                 ______________________________________________________  I                                                                      3-49.           #     System Management Release Notesn+     3.30 System Management Utility (SYSMAN)t    A           For example, the following command issued from a systembB           running OpenVMS Version 6.1 or lower to a system runningD           OpenVMS Version 6.2 produces no error messages and deletes,           all records that match FOOBAR$TTA:  N      SYSMAN> SET ENVIRONMENT/NODE=FOOBAR     ! FOOBAR runs OpenVMS Version 6.20      %SYSMAN-I-ENV, current command environment:%              Individual nodes: FOOBARe;              Username SYSTEM will be used on nonlocal nodes-P      SYSMAN> ALF REMOVE TTA                  ! Does not produce an error message      SYSMAN>  ?           Note that if the same command is issued from a systems@           running OpenVMS Version 6.1 or lower to another system?           running OpenVMS Version 6.1 or lower, it produces theE"           following error message:  9           %SYSMAN-I-NODERR,  error returned from node FOOt?           -SMI-E-ALFNOMATCH, no records matched search criterian  C           This is due to incorrect processing of wildcards prior to            OpenVMS Version 6.2.             ALF_SHOW  E           The SHOW command now works as documented whether or not you @           use wildcards. However, there are certain restrictions?           in wildcard matching of ALF records. For example, the B           following command displays only those records that start           with the string TTA:             SYSMAN> ALF SHOW TTA*i  D           However, the following command displays only those records4           that start with the string <nodename>$TTA:             SYSMAN> ALF SHOW TTA  E           Similarly, the following command displays records that havet'           device names ending with TTA:              SYSMAN> ALF SHOW *TTAa  D           If you want to display all records that contain the string4           TTA, you must enter the following command:              SYSMAN> ALF SHOW *TTA*       3-50 a  x      I                                           System Management Release Notes.I                                   3.30 System Management Utility (SYSMAN)s    #         3.30.1.2 Rights Identifiers   I         V6.2  In OpenVMS Version 6.0, a problem occurred for SYSMAN usersoH               having large numbers of rights identifiers associated withI               their accounts, causing the SMIserver to fail under certaino               conditions.   A               In OpenVMS Version 6.1, a temporary restriction was C               implemented to limit the number of rights identifiers E               that SYSMAN users could hold. SYSMAN users were limited C               to 60 rights identifiers per account. This limitationyE               was a total of all process, system, image, and extendedhF               rights. If a SYSMAN user running with more that 60 totalF               rights identifiers attempted to invoke a SYSMAN command,1               the following message was returned:   L               SMI-E-RIGHTSLIM, Temporary restriction:  rights limit exceeded  H               In OpenVMS Version 6.2, this limitation has been modified.H               The new upper limit for identifiers that a SYSMAN user who@               is attempting a remote connection can hold is 125.  F               If a SYSMAN user running with more than 125 total rightsH               attempts to issue a SYSMAN command to a remote node withinB               a cluster, the following error message is displayed:  5               SMI-E-RIGHTSLIM, Rights limit exceeded.i  F               Note that this rights limitation includes a minimum of 3H               identifiers that are granted during login when the process%               rights list is created:u  !               o  A UIC identifiero  $               o  A system identifier  G               o  Depending upon the environment in which the process is A                  operating, at least one environmental identifier   <               Users who want to run SYSMAN must have either:  @               o  A separate account with no more than 125 rights  F               o  Enough identifiers removed from their current accountD                  so that the total number of rights falls within the"                  appropriate range  G               A system manager usually performs account modification ory               creation.   I                                                                      3-51  o  n      #     System Management Release NotesC+     3.30 System Management Utility (SYSMAN)     :     3.30.1.3 SHUTDOWN NODE Command Qualifiers Have Changed  <     V6.2  The former /INVOKE_SHUTDOWN and /NOINVOKE_SHUTDOWN@           qualifiers have been changed to /INVOKE_SYSHUTDOWN and           /NOINVOKE_SYSHUTDOWN.   >           The qualifier /INVOKE_SYSHUTDOWN is the new default.9           Previously, /NOINVOKE_SHUTDOWN was the default.i  $     3.30.2 Problems and Restrictions  <           The following sections describe known problems andB           restrictions that apply to the System Management utility           (SYSMAN).        3.30.2.1 /CLUSTER QualifierC  C     VAX   When the system management environment is set clusterwide D     V6.0  with the /CLUSTER qualifier, entering the following SYSMAN*     Alpha command sometimes causes a hang:     V1.5,           SYSMAN> DO SHOW DEVICE device-name  D           This hang is caused by a communication failure between theD           process spawned by the DO command and the remote SMISERVER;           process on one of the Alpha nodes in the cluster..  @           To work around this problem, press Ctrl/C to return toA           the SYSMAN> prompt. Delete the remote SMISERVER process D           on the node that did not respond. You can then restart the7           SMISERVER process with the following command:   )           $ @SYS$SYSTEM:STARTUP SMISERVERh  @           If the DO SHOW DEVICE device-name command hangs on the=           next attempt, press Ctrl/C to return to the SYSMAN>gB           prompt. Delete and then restart the SMISERVER process on@           the unresponsive node. Log in to the node that stopped>           responding, and enter the DO SHOW DEVICE device-name           command.  D           Digital expects to fix this problem in a future release of-           the OpenVMS Alpha operating system.t         3-52           I                                           System Management Release NotestI                                   3.30 System Management Utility (SYSMAN)i    <         3.30.2.2 Clusterwide DISKQUOTA Commands (Alpha Only)  D         V1.5  Normally, SYSMAN DISKQUOTA commands for disks that areG               mounted clusterwide can be performed with the environmenteH               set to a single node. The clusterwide operation is done at               the XQP level.  F               If the environment is set clusterwide using the /CLUSTERD               qualifier, the following message is displayed, and the=               operation still finishes correctly clusterwide:a  O       %SMI-S-DQCLUS, device is mounted clusterwide, CLUSTER environment ignored   G               However, until further notice, when you use the followingmD               DISKQUOTA commands for clusterwide operation, you mustI               first set the environment clusterwide by using the /CLUSTER                qualifier:  ,               o  DISKQUOTA ENABLE/DEV=device  -               o  DISKQUOTA DISABLE/DEV=deviceP  I               If these commands are performed with the environment set to G               a single node, the disk quota for the clusterwide-mounted ?               device is enabled or disabled for that node only.c  H               The following example shows the correct usage and behaviorE               of the DISKQUOTA ENABLE and DISKQUOTA DISABLE commands:   %               SYSMAN> SET ENV/CLUSTER79               %SYSMAN-I-ENV, current command environment:s2                       Clusterwide on local clusterJ                       Username TESTUSER     will be used on nonlocal nodes                    I                                                                      3-532 t  i      #     System Management Release Notesl+     3.30 System Management Utility (SYSMAN)r    (       SYSMAN> DO SHOW DEV TEST01$DKA100:8       %SYSMAN-I-OUTPUT, command execution on node TEST02L       Device                Device       Error  Volume       Free  Trans MntL        Name                 Status       Count   Label      Blocks Count CntN       TEST01$DKA100:        Mounted          0  TESTVOL       832395     1   48       %SYSMAN-I-OUTPUT, command execution on node TEST03M       Device                Device        Error  Volume       Free  Trans MntnM        Name                 Status        Count  Label       Blocks Count Cnt O       TEST01$DKA100:        Mounted          0  TESTVOL        832395     1   4 8       %SYSMAN-I-OUTPUT, command execution on node TEST04M       Device                Device        Error  Volume       Free  Trans MntyM        Name                 Status        Count  Label       Blocks Count Cnt O       TEST01$DKA100:        Mounted          0  TESTVOL        832395     1   4 8       %SYSMAN-I-OUTPUT, command execution on node TEST01M       Device                Device        Error  Volume       Free  Trans Mnt M        Name                 Status        Count  Label       Blocks Count CnteO       TEST01$DKA100:        Mounted          0  TESTVOL        832395     1   4a1       SYSMAN> DISKQUOTA SHOW */DEV=TEST01$DKA100:g7       %SYSMAN-I-NODERR, error returned from node TEST02a@       -SYSTEM-F-QFNOTACT, disk quotas not enabled on this volume7       %SYSMAN-I-NODERR, error returned from node TEST03h@       -SYSTEM-F-QFNOTACT, disk quotas not enabled on this volume7       %SYSMAN-I-NODERR, error returned from node TEST04 @       -SYSTEM-F-QFNOTACT, disk quotas not enabled on this volume7       %SYSMAN-I-NODERR, error returned from node TEST01c@       -SYSTEM-F-QFNOTACT, disk quotas not enabled on this volume1       SYSMAN> DISKQUOTA ENABLE/DEV=TEST01$DKA100:t1       SYSMAN> DISKQUOTA SHOW */DEV=TEST01$DKA100: O       %SMI-S-DQCLUS, device is mounted clusterwide, CLUSTER environment ignored H       %SYSMAN-I-QUOTA, disk quota statistics on device TEST01$DKA100: --       Node TEST02 N            UIC                  Usage        Permanent Quota   Overdraft LimitB       [0,0]                     0            1000              100B       [VMS,TESTUSER]            25           1000              100                           3-54 e  t      I                                           System Management Release NotesnI                                   3.30 System Management Utility (SYSMAN)a    6           SYSMAN> DISKQUOTA DISABLE/DEV=TEST01$DKA100:5           SYSMAN> DISKQUOTA SHOW */DEV=TEST01$DKA100: ;           %SYSMAN-I-NODERR, error returned from node TEST02WD           -SYSTEM-F-QFNOTACT, disk quotas not enabled on this volume;           %SYSMAN-I-NODERR, error returned from node TEST03kD           -SYSTEM-F-QFNOTACT, disk quotas not enabled on this volume;           %SYSMAN-I-NODERR, error returned from node TEST04 D           -SYSTEM-F-QFNOTACT, disk quotas not enabled on this volume;           %SYSMAN-I-NODERR, error returned from node TEST01 D           -SYSTEM-F-QFNOTACT, disk quotas not enabled on this volume           SYSMAN>            3.31 System Time  C               This section contains notes pertaining to setting the                system time.  '         3.31.1 Changes and Enhancements   =               This note describes a change to the Watch Chip.   ?         3.31.1.1 Watch Chip - Change in Time Range (Alpha Only)   C         V1.0  Alpha systems maintain their system time during power D               failures and system down time with a watch chip (BBW).E               This chip replaces the time-of-day register (TODR) usedoE               on VAX systems. The BBW chip allows a range of only oneoE               century, placing a greater constraint on the dates thatlE               can be accepted by the $SETIME service and SET TIME DCLsI               commands. What used to be a wider date range on VAX systemsdB               is now limited to the century between 1957 and 2056.  G               In addition, a set of sanity checks has been added to theSD               system boot routines to validate the format of the BBWH               and the values put into it by previous system boots. TheseE               checks recognize out-of-bounds values. When the time is D               known to be earlier than the last time modification orE               greater than 5 years in the future, you are prompted toyC               enter the time at the console prompt. Such situationsaE               may occur when an Alpha computer, after running anotherlC               operating system such as OSF/1, is rebooted using thek.               OpenVMS Alpha operating system.   I                                                                      3-55     h      #     System Management Release Notesg     3.31 System Time    $     3.31.2 Problems and Restrictions  @           This section describes known problems and restrictions-           related to setting the system time.   E     3.31.2.1 Time of Day Register (TODR): Resetting System Time Aftera#              January 1st (VAX Only)n  C     V6.1  The following restriction applies to all past and present "           versions of OpenVMS VAX.  @           The Time of Day Register (TODR), which the system usesB           to maintain system time, has a limit of approximately 15C           months. If you do not reset the system time after Januarye2           1st, the following problems might occur:  ;           o  The first time in a new year that you reboot aNC              VAXcluster system or a node in the system, one or moreA0              nodes display any of the following:  9              -  A system time that is a year in the past.   ;              -  A system time that is a year in the future, ?                 which might cause passwords to expire and other                  difficulties.y  @              -  A system time that is correct, but a SHOW SYSTEMC                 command indicates that the system has been up sinceA&                 sometime in the 1800s.  @           o  Even if you have corrected an incorrect system timeC              when you boot the system, one or more of the following #              problems might remain:e  C              -  A SHOW SYSTEM command displays an incorrect up timeT,                 such as a date in the 1800s.  E              -  The error log report (ERRLOG) shows errors for a yeare                 in the future.  @              -  Batch jobs are waiting for a year in the future.  A              -  Files have a creation or modification date in thea                 future.e       3-56           I                                           System Management Release Notes,I                                                          3.31 System Timev    I               OpenVMS maintains system time across reboots using the TODR*F               register in the OpenVMS VAX system CPU. Because the TODRI               has a range of approximately 15 months, the system actuallydF               maintains system time by combining the TODR value with aH               base time recorded in the base system image (SYS$LOADABLE_C               IMAGES:SYS.EXE). The base time is defined as follows:r  -               01-JAN-CURRENT_YEAR 00:00:00.00A  G               Because all TODRs ordinarily have the same base, multipleoE               CPUs can boot off the same system disk, and you can useRC               multiple system disks on one CPU; in either case, then-               system sets the time correctly.   @               When a SET TIME command is issued (with or without=               specifying a time), OpenVMS does the following:   B               1. Writes the current time to the system image file.  F               2. Resets the TODR as an offset within the current year.  C               In a VAXcluster system, the TODR is reset only on the_E               node on which the SET TIME command was issued. However, F               multiple systems might share the system image. This doesI               not normally cause a problem, except after the first day of                a new year.t  F                 ________________________ Note ________________________  >                 The system issues the SET TIME command when itB                 boots and as a part of the normal SHUTDOWN command                 procedure.  F                 ______________________________________________________  F               By December, each node has a very large offset stored inG               the TODR (from the base time of 1-JAN of that year). WheneI               the time advances to a new year, the system image still hasr?               the old year and the TODR values are still large.   G               After January 1st, if a SET TIME command is issued on any E               node (or any node is shut down using SHUTDOWN.COM), theu                following happens:  4               1. The new year becomes the base year.  9               2. The system resets the TODR on that node.c  F               3. The other nodes still have a large value in the TODR.  I                                                                      3-57            #     System Management Release Notese     3.31 System Time    D           After these three events occur, if a node that has a largeB           TODR crashes and rejoins the cluster, its system time isD           initially in the next year (applying the large TODR to theA           new year). This system time is recorded as the system'seE           boot time. When the node joins the cluster, its time is setsB           to the correct value, but the boot time remains one yearA           in the future. Certain forms of the SHOW SYSTEM commandhB           compare current time to boot time; in this circumstance,0           SHOW SYSTEM displays incorrect values.  C           If a system disk is used at different times by different, @           unclustered CPUs or if different system disks are used>           at different times on the same CPU, the system mightD           incorrectly set the time to a year in the future or a yearD           in the past, depending on how the CPU's TODR and the value<           recorded on the system disk become unsynchronized:  B           o  Sharing a system disk across multiple CPUs pushes the"              time into the future.  E           o  Using multiple disks on one CPU pushes the time into the               past.             Action:n  C           Between January 1 and April 1, reset the system time. UsemC           either of the following methods, depending on whether youSD           have a nonclustered node or a node in a VAXcluster system:             Type of Node Action   >           Nonclustered  Use the SET TIME command; for example:9           node          $ SET TIME 05-JUN-1994:12:00:00 1s  C            Node in a     Use the following SYSMAN commands to resettB            VAXcluster    the time on all the nodes in a VAXcluster-            system        system; for example:S  0                          $ RUN SYS$SYSTEM:SYSMAN8                          SYSMAN> SET ENVIRONMENT/CLUSTERF                          SYSMAN> SET PROFILE/PRIVILEGE=(LOG_IO,SYSLCK)?                          SYSMAN> CONFIGURATION SET TIME 05-JUN-o(                          1994:12:00:00 1  &                           SYSMAN> EXIT  E           [1]You do not need to specify a time. If you do not specifydD           a time, SET TIME updates the system time using the time in           the TODR.        3-58 I  R      I                                           System Management Release Notes I                                                          3.31 System Timen      F               Either method shown in the table resets the TODR and theG               base time in the system image with the values for the newD               year.i  F                 ________________________ Note ________________________  ?                 If you are running the Digital Distributed TimeYC                 Service (DECdts) on your system, you must use it to                  set the time.   F                 ______________________________________________________  :         3.32 Terminal Fallback Facility (TFF) (Alpha Only)           V1.0  F               The Terminal Fallback facility (TFF) includes a fallbackH               driver (SYS$FBDRIVER.EXE), a shareable image (TFFSHR.EXE),I               a terminal fallback utility (TFU.EXE), and a fallback tableM'               library (TFF$MASTER.DAT).   F                 ________________________ Note ________________________  C                 TFFSHR has been removed from IMAGELIB because it isKD                 not a documented, user-callable interface. The imageA                 is still available in the SYS$LIBRARY: directory.   F                 ______________________________________________________  I                                                                      3-59     l      #     System Management Release Notes 6     3.32 Terminal Fallback Facility (TFF) (Alpha Only)    C           o  To start TFF, invoke the TFF startup command procedure 0              located in SYS$MANAGER, as follows:  -              $ @SYS$MANAGER:TFF$SYSTARTUP.COMl  5           o  To enable fallback or to change fallbackoB              characteristics, invoke the Terminal Fallback utility              (TFU), as follows:   !              $ RUN SYS$SYSTEM:TFUb              TFU>   B           o  To enable default fallback to the terminal, issue the#              following DCL command:n  $              $ SET TERMINAL/FALLBACK  ?           OpenVMS Alpha TFF differs from OpenVMS VAX TFF in ther           following ways:S  ?           o  On Alpha systems, the TFF fallback driver is named ?              SYS$FBDRIVER.EXE. On VAX systems, the TFF fallbackc*              driver is named FBDRIVER.EXE.  @     V6.1  o  On Alpha systems, TFF is capable of handling 16-bitA              character fallback. The OpenVMS Alpha fallback tableY?              library (TFF$MASTER.DAT) contains four more 16-bitr=              character tables than the VAX library. Table 3-1h/              describes these additional tables.O  1           Table 3-1 TFF Character Fallback Tables   -           Table Name       Base   Descriptionr  =           BIG5_HANYU       BIG5   BIG5 for CNS 11643 (SICGCC) 2                                   terminal/printer  =           HANYU_BIG5       CNS    CNS 11643 (SICGCC) for BIG5 2                                   terminal/printer  @           HANYU_TELEX      CNS    CNS 11643 for MITAC TELEX-CODE*                                   terminal  <           HANGUL DS        KS     KS for DOOSAN 200 terminal  D              These tables are used mainly by the Asian region. Also,C              the table format was changed due to the support of 16-e$              bit character fallback.       3-60 w         I                                           System Management Release NotesaI                        3.32 Terminal Fallback Facility (TFF) (Alpha Only)     B         V1.0  o  On Alpha systems, the TFU command SHOW STATISTICSA                  does not display the size of the fallback driver $                  (SYS$FBDRIVER.EXE).  4               RT terminals are not supported by TFF.  H               For more information about the Terminal Fallback facility,E               refer to the OpenVMS Terminal Fallback Utility Manual.    (         3.33 VAX 7000 Systems (VAX Only)  H               This section contains release notes pertaining to VAX 7000               systems.  (         3.33.1 Problems and Restrictions  >               This section describes problems and restrictions.               experienced on VAX 7000 systems.  :         3.33.1.1 Dump Off System Disk (DOSD) Not Supported  H         V6.2  Dump Off System Disk (DOSD) functionality is not supported?               on VAX 7000 systems. Contact your Digital supporteD               representative for a remedial kit that will enable use;               of Dump Off System Disk on VAX 7000 systems. s           3.34 VMScluster Systems   F               The following sections contain information pertaining to!               VMScluster systems.e  '         3.34.1 Changes and EnhancementsM  E               This section contains notes about changes to VMSclusterT               systems.  (         3.34.1.1 SCSI VMScluster Systems  C         V6.2  Starting with OpenVMS Version 6.2, VMScluster systems A               support the Small Computer Systems Interface (SCSI)AD               as a storage interconnect. See the OpenVMS Version 6.2D               New Features Manual for a description of this feature,?               including configuration information, installation F               information, and a description of any known restrictions               and problems.   I                                                                      3-61T o  n      #     System Management Release Notes      3.34 VMScluster Systemso    %     3.34.1.2 Concurrency Improvementsm  A     V6.1  OpenVMS Version 6.1 and later provides an improved file B           system. This improved file system is also available as a:           special release known as the XQP+ for PATHWORKS.  B           One of the features provided by the improved file systemE           is improved concurrency, which allows multiple processes toL4           create files on a single disk in parallel.  D           In a VMScluster system, do not enable improved concurrencyE           unless all nodes are running the improved file system. EachuC           node in the cluster must be running one of the following:b  /           o  OpenVMS Alpha Version 6.1 or latere  -           o  OpenVMS VAX Version 6.1 or laterT             o  XQP+ for PATHWORKSo  @           If you are running the improved file system on all theC           nodes in your VMScluster, turn on improved concurrency byS;           setting the static XQPCTL2 system parameter to 1.E  '     3.34.1.3 FDDI Clusters (Alpha Only)i  A     V6.1  Beginning with OpenVMS Alpha Version 6.1, you no longerY>           have to set system parameter PE3 to 1 to enable FDDIA           clustering. In fact, system parameter PE3 should not be )           set to any value other than 0. e  $     3.34.2 Problems and Restrictions  E           This section describes problems and restrictions pertaininga            to VMScluster systems.  0     3.34.2.1 KFESA/KFESB Controller Restrictions  >     V6.2  There are restrictions in the use of the KFESA/KFESB@           EISA DSSI controllers in systems that are members of aA           VMScluster system. This configuration will be supported B           only after a specific update is applied to your systems.@           This update may be present on your OpenVMS V6.2 CD-ROM5           distribution kit in the following location:A  !           [KFESX]KFESX_UPDATE.BCKT  A           To apply this update, restore the save set to a scratch B           directory and follow the instructions in the READ-ME.1ST           file.E       3-62 i  q      I                                           System Management Release Notes I                                                   3.34 VMScluster Systems     C               If this update save set is not present on your CD-ROM C               distribution kit, please contact your Digital support E               representative and ask for the TIMA kit associated withn$               the KFESA/KFESB issue.  I         3.34.2.2 Booting Two Computers That Share a SCSI Bus (Alpha Only)   E         V6.2  When you simultaneously boot two computers that share a D               SCSI bus, one of them might bugcheck early in the boot1               process with the following message:n  N               ** Code=00000215: MACHINECHK, Machine check while in kernel mode  I               However, the system that bugchecks will reboot immediately. I               Since the two systems are no longer booting simultaneously, I               the boot will succeed and the cluster will continue with noa               ill effects.  G               This problem is most common with AlphaServer 2100 systems G               that have more than one shared SCSI bus, but it can occureI               on other shared SCSI bus configurations. Digital expects toa<               fix this software problem in a future release.  G               To avoid this problem, wait a few seconds between issuingr?               boot commands to two systems sharing a SCSI bus. -  H         3.34.2.3 System Startup in a VMScluster Environment (Alpha Only)  C         V6.2  In a VMScluster environment, under some circumstancesuB               the system startup procedure may fail to write a newC               copy of the ALPHAVMSSYS.PAR file. If this occurs, theoI               console output from the boot sequence reports the following1               messages:   B               %SYSGEN-E-CREPARFIL, unable to create parameter file?               -RMS-E-FLK, file currently locked by another user   A               This error creates an operational problem only when E               changing SYSGEN parameters using a conversational boot.kI               For a normal, nonconversational boot, this error message iseI               purely cosmetic because the parameter file has not changed.aE               If a conversational boot is used, and SYSGEN parametersiH               are changed at boot time, these changed parameters will beI               correctly used for the current boot of the system. However, H               since the boot procedure does not successfully write a new  I                                                                      3-63f o  g      #     System Management Release Notesf     3.34 VMScluster Systemsy    C           copy of the parameter file, these changed parameters will *           not be used in subsequent boots.  @           To permanently change SYSGEN parameters that have been@           changed by a conversational boot, run SYSGEN after theA           system has completed booting, and execute the followingt           commands:              SYSGEN> USE ACTIVE            SYSGEN> WRITE CURRENT        3.34.3 Corrections  C           This section describes corrections that affect VMScluster            systems.  :     3.34.3.1 REMOVE_NODE Option in SYS$SYSTEM:SHUTDOWN.COM  D     V6.2  The REMOVE_NODE option in SYS$SYSTEM:SHUTDOWN.COM has beenD           corrected to reduce cluster expected votes to a value that?           maintains quorum after the node shuts down. Quorum is B           maintained as long as at least one voting member remains           in the cluster.f  C           With this change to REMOVE_NODE you can now shut down anysD           number of nodes in an OpenVMS cluster without encounteringA           quorum loss. The benefit of this change is greatest for            two-node clusters.  D           Digital strongly recommends that all nodes in a VMSclusterB           environment have the SYSGEN parameter EXPECTED_VOTES setB           to the largest number of votes attainable in the cluster           configuration.  D           This feature is provided only by the REMOVE_NODE option inE           SHUTDOWN.COM. Nodes that leave a cluster for other reasons, =           such as power failure, can still cause quorum loss.h  B           To learn more about the impact of removing a node, referD           to the OpenVMS System Manager's Manual: Essentials and the0           VMScluster Systems for OpenVMS manual.        3.35 VMSKITBLD.COM Procedure  E           This section contains notes pertaining to the VMSKITBLD.COMo           procedure.       3-64 a  s      I                                           System Management Release Notes I                                              3.35 VMSKITBLD.COM Procedurem    '         3.35.1 Changes and Enhancements   @               This section describes a change in support for the&               VMSKITBLD.COM procedure.  I         3.35.1.1 VMSKITBLD.COM Not Supported on OpenVMS Alpha Version 6.2t                  (Alpha Only)X  C         V6.2  Using the VMSKITBLD.COM procedure to duplicate systemhD               files from an existing system disk to another disk nowI               applies only to OpenVMS VAX systems (see the OpenVMS Systemy8               Manager's Manual: Essentials for details).  G               Beginning with OpenVMS Alpha Version 6.2 systems, you can_E               use the SYS$SYSTEM:AXPVMS$PCSI_INSTALL.COM procedure toaG               install or upgrade from a running OpenVMS Alpha system tomE               another target system disk. The OpenVMS Version 6.2 New_H               Features Manual describes this new feature in more detail.                 4         3.35.2 Documentation Changes and Corrections  I               This section describes a documentation correction regardingw*               the VMSKITBLD.COM procedure.  I         3.35.2.1 OpenVMS System Manager's Manual: Essentials (Alpha Only)e  H         V6.2  Section 2.5 of OpenVMS System Manager's Manual: EssentialsC               incorrectly indicates that VMSKITBLD.COM is availablelE               on both OpenVMS VAX and OpenVMS Alpha systems. In fact, I               OpenVMS Alpha Version 6.2 no longer supports VMSKITBLD.COM.                         3.36 Volume Shadowingn  @               The following sections pertain to volume shadowing               software.   '         3.36.1 Changes and Enhancementse  @               This section describes changes to volume shadowing               software.l  I                                                                      3-65     n      #     System Management Release Notese     3.36 Volume Shadowing     2     3.36.1.1 Mixed-Architecture VMScluster Changes  =     V6.2  Volume Shadowing for OpenVMS contains the followinge           changes:  <           o  Enabling of minimerge functionality in a mixed->              architecture VMScluster environment that includes,              OpenVMS Alpha Version 6.1 nodes  D           o  Support for geometry-based shadowing device recognitionE              that allows devices, such as the RZ28 and RZ28B, to work #              in the same shadow sets  6           o  Software improvements that provide betterA              interoperability for a mixed-architecture VMSclustere              environment  D           These changes are also available in a remedial kit that isB           distributed through Digital Customer Services worldwide.B           This kit applies to OpenVMS VAX Versions 5.5-2 and laterE           and OpenVMS Alpha Version 6.1. For more information, pleaseo6           contact your Digital support representative.  &     3.36.1.2 New Bugcheck: SHADZEROMBR  ?     V6.2  A synchronization problem which resulted in a virtualo@           unit having zero members formerly caused ACCVIO systemB           failures in Volume Shadowing for OpenVMS. Because having@           zero members is an illegal state for a mounted virtualB           unit, Volume Shadowing crashed the node in an attempt to"           maintain data integrity.  B           Version 6.2 of OpenVMS provides a new shadowing bugcheck=           called SHADZEROMBR. If this bugcheck occurs, pleaseeA           document and report what events occurred on other nodesSA           in the VMScluster environment that also have the shadowUB           set mounted. For example, if Node A and Node B share theD           same shadow set, report any problems that occurred on NodeD           A before Node B failed with a SHADZEROMBR error. This willE           help OpenVMS Engineering determine what caused the failure.f  C           To continue operation, reboot the failed node and remounte           the shadow sets.         3-66    -      I                                           System Management Release NoteseI                                                     3.36 Volume Shadowingy    .         3.36.1.3 Phase I Retirement (VAX Only)  E         V6.2  Starting with OpenVMS Version 6.2, the Volume ShadowingeE               for OpenVMS product supports only phase II (host-based) C               shadowing. Phase I (controller-based) shadowing is no H               longer available. Phase II provides significantly enhancedB               data availability and supports a much wider range of:               configurations, disk controllers, and disks.  F               Any VAX nodes that still use phase I must be migrated toE               phase II in order to access shadowed data from an AlphabB               node on the cluster. For information about migratingE               from phase I shadowing to phase II, refer to the Volumef,               Shadowing for OpenVMS manual.   $         3.36.1.4 Timer-Based Polling  B         V6.2  Shadowing now uses a timer to adhere more accuratelyC               to the number of seconds specified by the SHADOW_MBR_aE               TMO parameter. For directly connected SCSI devices thatTE               have been powered down or do not answer to polling, theoG               elapsed time before a device is removed from a shadow set_G               can still approach 1 minute. In all other situations, the I               elapsed time will closely approximate the number of secondsi8               specified by the SHADOW_MBR_TMO parameter.  2         3.36.1.5 SCSI Shadowing Support (VAX Only)  I         V6.2  Volume Shadowing for OpenVMS Version 6.2 no longer supportsAF               shadowing operations for locally connected SCSI disks on8               the VAX 3000 and VAX 4000 series systems.   (         3.36.2 Problems and Restrictions  F               The following sections describe known problems and other<               considerations pertaining to volume shadowing.           3.36.2.1 KDM70 Devices  I         V6.1  Volume Shadowing for OpenVMS (phase II) requires that KDM70 F               disk controllers run a minimum of Version 3.0 microcode.  I                                                                      3-67S D  E      #     System Management Release Notes      3.36 Volume ShadowingF    @     3.36.2.2 DISMOUNT/CLUSTER Command Can Cause Clusterwide Hang  A     V6.1  When you issue the DISMOUNT/CLUSTER command to a shadowc@           set, it can sometimes cause a clusterwide hang. If youB           experience this problem, use the DISMOUNT/SYSTEM command>           for every node in the VMScluster. You can enter thisD           command once for every node in the VMScluster by using theC           SYSMAN DO command in combination with the DISMOUNT/SYSTEMr           command.  E           For more information about using the SYSMAN DO command, seeI.           the OpenVMS System Manager's Manual.  3     3.36.2.3 RZ57 Support Restricted in Shadow Sets   ?     V6.1  OpenVMS systems support the RZ57 disk drive only with B           device revision level D01 and microcode revision 6000 or           higher.   ;           Disks that meet these conditions can be shadowed.e  0     3.36.3 Documentation Changes and Corrections  D           This section contains a correction to the volume shadowing           documentation.  0     3.36.3.1 Volume Shadowing for OpenVMS Manual  A     V6.1  The first bullet in Section 3.1 of the Volume ShadowinglB           for OpenVMS manual incorrectly indicates that only Alpha>           systems support per-disk volume shadowing licensing.E           Starting with Version 6.1, OpenVMS VAX systems also supportV           per-disk licensing.r                             3-68                         I                                                                         4OI         _________________________________________________________________   I                                                 Programming Release Notes     H               This chapter provides release notes about both application8               and system programming on OpenVMS systems.  E               For information about new programming features included1E               in OpenVMS Version 6.2, see the OpenVMS Version 6.2 News               Features Manual.  "         4.1 Batch and Print Queues  I               This section contains release notes pertaining to batch anda               print queues.e  '         4.1.1 Problems and Restrictions   I               This section describes problems and restrictions pertaininghI               to batch and print queues. For problems important to systemu/               managers, refer to Section 3.4.1.n  0         4.1.1.1 Terminating Executing Batch Jobs  F         V6.2  Under the following conditions, the DELETE/ENTRY command8               might fail to stop an executing batch job:  :               o  The batch job is a DCL command procedure.  C               o  There is an ON ERROR CONTINUE command (or SET NOONe7                  command) within the command procedure.   E               The DELETE/ENTRY command causes the job to terminate inlC               phases. A delete_process AST routine is given in usertE               mode, supervisor mode, and then executive mode. BecausebF               there is a small delay between each mode, it is possibleI               that, in a batch job, a user-mode image might terminate andVG               the command procedure might continue to execute until the1E               supervisor-mode delete_process AST routine is executed.y  I                                                                       4-1e    w           Programming Release Notes      4.1 Batch and Print Queues    A           The return status of the SYNCHRONIZE command is assumedaD           to contain the termination status of the target batch job.B           In addition, command procedures would normally execute aE           command such as $ON ERROR THEN CONTINUE or $SET NOON beforeiD           issuing the SYNCHRONIZE command. If a DELETE/ENTRY commandA           is issued to the job executing the SYNCHRONIZE command,eC           the JBC$_JOBABORT is interpreted as being the terminationPD           status of the target batch job rather than a return status@           of the SYNCHRONIZE command. The command procedure thenE           continues to execute for a short period with this incorrecteD           assumption and performs an operation such as requeuing theD           target batch job or incorrectly reporting a failure of the           target batch job.   D           This problem has been fixed for the SYNCHRONIZE command byE           detecting this situation and waiting in an exit handler forPD           longer than the delay between the user and supervisor mode           termination delay.  ?           Any other images that would report the job completionlC           status obtained by the SJC$_SYNCHRONIZE_JOB function codeeC           of the $SNDJBC system service as the return status of thebB           program should implement logic similar to the following:  $           1. Declare an exit handler  @           2. In the exit handler, implement the following logic:  .              IF (exit status is JBC$_JOBABORT)              THEN                    Wait 10 seconds              ENDIF       4.1.2 Correctionsy  ?           This section describes corrections to batch and printrA           queue features used by programmers. For batch and print =           queue corrections related to system management, see C           Section 3.4.2. For corrections of interest to the general "           user, see Section 2.1.1.               4-2     f      I                                                 Programming Release NoteskI                                                4.1 Batch and Print Queuesa    )         4.1.2.1 Accessing Batch Log Files   C         V6.2  In previous versions of OpenVMS, when a batch job wasaF               submitted without the /NAME qualifier, the log file nameG               was not maintained. The log file was created when the jobiH               executed, but the log file name specification could not beI               accessed with the SYS$GETQUI system service or the F$GETQUI                lexical.  .               This problem has been corrected.  *         4.1.2.2 Displaying Open Batch Jobs  D         V6.2  Beginning with OpenVMS VAX Version 5.5, open jobs wereA               displayed when $GETQUI(display_entry) was used in a @               wildcard search because the undefined jobs (JOB$K_;               UNDEFINED) were being considered for display.   F               This problem has been corrected. Open jobs are no longerI               displayed when $GETQUI(display_entry) is used in a wildcarde               search.   %         4.1.2.3 $GETQUI Error Messagei  D         V6.2  Previously, when the $GETQUI service was called from aI               nonbatch process with the DISPLAY_JOB function and THIS_JOBeF               flag, a JOBQUEDIS error was returned even when the queueD               manager was running. This inappropriate error was alsoG               returned when a process was spawned from a batch process.   I               This problem has been fixed and the appropriate error (JBC-o+               E-NOSUCHJOB) is now returned.   0         4.1.2.4 Log File Defaults for Batch Jobs  A         V6.2  In previous versions, if a JOBNAME included invalida?               characters in a file specification and any of therG               components of the log file name were drawn from defaults,sD               the batch job failed with the following error message:  9               %RMS-F-SYN, file specification syntax errorh  G               This problem occurred when the $SNDJBC system service wasiI               used with both the SJC$_LOG_SPECIFICATION and the SJC$_JOB_sF               NAME item codes. If the log file name was not a completeF               file specification, defaults were applied incorrectly to               create one.e  D               This problem has been corrected, and the job no longer               fails.  I                                                                       4-3                 Programming Release Notesh     4.1 Batch and Print Queues    5     4.1.2.5 Restarting FORTRAN Carriage Control Filest  >     V6.2  In previous versions, when a paused or stopped queue@           printing a FORTRAN carriage control file was restarted@           with the /TOP_OF_FILE qualifier, extraneous formattingA           characters were sent to the printer device. Usually, an 4           extra line feed was output to the printer.  E           This problem has been fixed, and the /TOP_OF_FILE qualifier4=           can be used when restarting queues printing FORTRAN !           carriage control files.M  =     4.1.2.6 Symbiont BADLOGIC Dump After STOP/QUEUE/RESET ande             START/QUEUEt  E     V6.2  In previous versions of OpenVMS, a STOP/QUEUE/RESET command C           that was followed quickly by a START/QUEUE command caused 8           the print symbiont to produce a BADLOGIC dump.  C           A workaround for this problem stated that you should waitMA           at least 1 minute between entering STOP/QUEUE/RESET ando           START/QUEUE commands.   E           This problem has been corrected. You no longer need to waita,           between entering the two commands.  5     4.1.2.7 TASK_STATUS Requests to the Queue Manager   B     V6.2  In previous versions, when a symbiont sent a TASK_STATUSE           request to the queue manager and there were no active jobs,O>           the request was rejected with the following message:  2           Message from user QUEUE_MANAGE on CRATERK           %QMAN-I-INVSMBMSG, invalid data in message from symbiont on queue            TEST is being ignored   C           However, device status can change when no jobs are activeM@           (for example, SMBMSG$V_STALLED or SMBMSG$V_UNAVAILABLE<           conditions are not tied to a job). Therefore, thisB           situation has been corrected. Now, when a symbiont sendsE           a TASK_STATUS request to the queue manager and there are noe/           active jobs, the request is accepted.3           4-4O r  d      I                                                 Programming Release NotesdI                                                              4.2 Debugger.             4.2 Debugger  C               This section contains release notes pertaining to the(               OpenVMS Debugger.n  I               Unless specified otherwise, the release notes apply to bothaG               the character-cell and DECwindows Motif interfaces of the                debugger.t  &         4.2.1 Changes and Enhancements  H               This section describes changes and enhancements in OpenVMS#               Debugger Version 6.2.   (         4.2.1.1 Performance Improvements  F         V6.2  Performance improvements have been made in the following               areas:  ?               o  Previously, in the DECwindows Motif interface,.F                  lengthy examines resulted in performance degradation.G                  Performance has now been considerably improved througheC                  optimized text output routines. In addition, a newtE                  message view pop-up menu command named CLEAR COMMAND.H                  WINDOW (which entirely clears the command window of itsH                  current contents) has been added to restore performance&                  after lengthy output.  E               o  The previous performance degradation in the debuggerhG                  startup and in the SET MODULE, SET SCOPE, DECLARE, andu9                  SHOW SYMBOL commands has been corrected.   E               o  On OpenVMS Alpha systems, previously the STEP/RETURNo@                  command was very slow. Performance has now been(                  considerably enhanced.   !         4.2.1.2 VMSDEBUG.DAT File   H         V6.2  This note pertains only to the DECwindows Motif interface.  D               When you have installed the OpenVMS Debugger, be awareH               that the VMSDEBUG.DAT file has been revised, and check forE               the existence of an old file named VMSDEBUG.DAT in youroG               directory. If you do not have a VMSDEBUG.DAT file in youroE               login directory when you run the debugger, the debuggeraC               will start up with the full complement of definitions A               found in the system copy of this file, DECW$SYSTEM_ E               DEFAULTS:VMSDEBUG.DAT. There is nothing more for you to                do.a  I                                                                       4-5  i  r           Programming Release NotesV     4.2 Debugger    B           If you do have an old copy of VMSDEBUG.DAT in your login?           directory, the debugger will use whatever definitionsrB           are in it. Because some changes have occurred, there may?           be some minor visual differences, particularly in therB           definitions of fonts. If you have made customizations toB           your GUI and then saved the customizations from the menuD           function, the current design replaces the new VMSDEBUG.DATC           with an older format in your SYS$LOGIN directory, and yourB           will lose the additional features of the latest version.D           It is therefore recommended that you take advantage of theE           latest version of the VMSDEBUG.DAT file by doing one of the            following:  D           -  Delete your old SYS$LOGIN:VMSDEBUG.DAT, thus defaulting               to the system copy.  @           -  Copy the DECW$SYSTEM_DEFAULTS:VMSDEBUG.DAT file andE              carefully merge the changes with your SYS$LOGIN version.e  #     4.2.2 Problems and Restrictionsr  <           This section describes known debugger problems and           restrictions.t  +     4.2.2.1 Behavior After Stack Corruption   >     V6.2  The debugger allocates a certain amount of memory atB           startup and shares the stack with the user's program. IfE           a user process exception results in exhaustion of resourcesdC           or corruption of the stack, the debugger may be incapable D           of regaining control, and the debug session may terminate.  C           You may be able to work around this problem by trying oneP           of the following:   D           o  Change your source code, temporarily or permanently, toC              reduce resource consumption or lessen the use of stackd              space             o  Increase quotas  B           o  Specify a larger stack size when linking your program  E           Be aware of this potential behavior after the occurrence ofmE           stack corruption messages or warnings about continuing from D           a severe error. In either case, the integrity of the debug'           session cannot be guaranteed.e       4-6  d  d      I                                                 Programming Release NotesgI                                                              4.2 Debuggerm             4.2.2.2 CONNECT CommandM  @         V6.2  You cannot use the CONNECT command to connect to aE               subprocess of a process running under debugger control.t  B               To work around this restriction, use the SET PROCESS1               command to connect to subprocesses.T  "         4.2.2.3 Detached Processes  B         V6.2  You cannot use the DECwindows Motif interface to theA               debugger to debug detached processes, such as printrE               symbionts, which run without a Command Line Interpretere               (CLI).  G               The debugger's DECwindows Motif interface requires eitheraE               the two-process or multiprocess debugger configurations F               so that the main debugger image can communicate with theG               debugger's UI image. These debuggers require you to start G               the program you are debugging from the CLI; the debuggersoG               themselves are created through a call to LIB$SPAWN, whichn               requires a CLI.   I               If you want to debug a detached process that runs without a0H               CLI, use the character-cell (screen mode) interface to the&               single-process debugger.  '         4.2.2.4 SET TASK/ACTIVE Command.  D         V6.2  The debugger command SET TASK/ACTIVE does not work for               DECthreads.y  I               Instead, you can use the following effective substitutes onD               DECthreads:   A               o  For query-type actions, use the SET TASK/VISIBLEE                  command.   I               o  To gain control to step through a particular thread, usei4                  strategic placement of breakpoints.  $         4.2.2.5 SPAWN/NOWAIT Command  G         V6.2  If your application attempts to spawn a subprocess from aeF               process running under debugger control and the following3               conditions apply, the debugger hangs:e  D               o  You started the spawned subprocess with a RUN/DEBUG                  command  )               o  The Nowait flag is clear   I                                                                       4-7t                Programming Release Notesi     4.2 Debugger    C           This occurs because the wait direction causes the currentc>           debug process to hibernate until the spawned process@           completes. The spawned process never completes becauseE           the debug kernel image spawned with your spawned subprocessoB           waits indefinitely for communication from the debug mainC           image. The debug main image cannot communicate due to thes           wait direction.   C           To work around this restriction, do one of the following:g  >           o  Start the spawned subprocess with the RUN/NODEBUG<              command and then issue the SET PROCESS command.  !           o  Set the Nowait flag.   A     4.2.2.6 System Service Interception and Shared Linkage Images_             (Alpha Only)  =     V6.2  On OpenVMS Alpha systems, anything that uses system C           service interception (SSI), like the debugger or the heaphC           analyzer (HA), is unable to intercept system service call B           images activated by shared linkage. The image activator,C           therefore, avoids shared linkage for images linked or runOB           with /DEBUG, and instead activates private image copies.  A           This has performance implications for user applications E           under debugger or HA control, as images activated by shared            linkage run faster.   &     4.2.2.7 DEBUG.EXE Image (VAX Only)  A     V6.1  On OpenVMS VAX systems, you cannot debug an image named @           DEBUG.EXE. This name is used internally for the kernelB           portion of the debugger. To work around this problem, do           the following:  ,           $ DEFINE LIB$DEBUG SYS$SHARE:DEBUG  B           Optionally, you can rename your image to something other           than DEBUG.EXE.        4-8            I                                                 Programming Release NotesRI                                                              4.2 Debuggerm    F         4.2.2.8 STEP/OVER Steps into Fortran Run-Time Library Routines                 (VAX Only)  H         V6.1  On OpenVMS VAX systems, if you are debugging a DEC Fortran@               program, and the debugger encounters a Fortran I/OF               operation such as READ, WRITE, or PRINT, you will noticeH               that the Fortran compiler calls a Fortran Run-Time LibraryE               routine to complete the I/O operation. When you issue a G               STEP command at the call to the RTL routine, the debugger F               steps into, rather than over, the routine and issues the               following error:  D               %DEBUG-W-NOSCRLIN, no source line for address nnnnnnnn  B               The problem occurs because the debugger steps acrossI               routines by searching for a RET instruction to be executed,oE               and, in this case, the Fortran compiler is deallocatingHD               temporary strings from the stack in a nonstandard way,0               without explicit RET instructions.  C               To recover from the error message, issue several STEPJD               commands to return the session to the expected line ofE               code. To prevent recurrence of the problem, modify yourHE               program to include a temporary variable that stores theuE               results of the function prior to the I/O statement. Forr               example:  %                   CHARACTER*23 c1, c2jN                   c1 = c2()                   ! c1 is the temporary variable C                   WRITE (*) c1                   END ,                   CHARACTER*23 FUNCTION c2()0                   c2 = 'ABCDEFGHIJKLMNOPQRSTUVW'                   RETURN                   END               I                                                                       4-9j c  l           Programming Release Notest     4.2 Debugger         4.2.2.9 Watchpoint Support  >     VAX   The following are problems and restrictions with the-     V6.0  debugger's support for watchpoints:o	     Alpha =     V1.0  o  Watchpoints set on variables whose addresses aret@              in global sections do not work. Attempting to set aE              watchpoint on a location in a global section will results,              in a %DEBUG-E-BADWATCH message.  B           o  If a watched location changes during a system service>              routine, you will be notified, as usual, that theA              watchpoint occurred. However the stack will show one B              or more debugger frames on top of the frame or frames              for your program.  @              To work around this problem, enter one or more STEP:              /RETURN commands to get back to your program.  6     4.2.2.10 CALL and SHOW CALLS Commands (Alpha Only)  >     V1.5  On OpenVMS Alpha systems, the following CALL command;           problems and restrictions appear in this release:a  D           o  You cannot pass floating-point parameters by value in a              CALL command.  A           o  After you issue a SHOW CALLS command, the output maytD              include system call frames in addition to the user callD              frames associated with your program. System call frames3              appear in the following circumstances:o  (              -  When an exception occurs  7              -  When an asynchronous system trap occursi  8              -  When a watchpoint occurs in system space  B              The display of system call frames does not indicate a              problem.            4-10 N  I      I                                                 Programming Release NotesoI                                                              4.2 Debuggerl    +         4.2.2.11 DECwindows Motif Interfacee  H         V1.5  The following problems or restrictions are specific to the)               DECwindows Motif interface:a  D               o  Occasionally, if you are debugging a UI applicationH                  and you have many debugger windows overlapping the userH                  program's windows, the X server will abruptly terminate"                  the user program.  C                  To avoid this problem, refrain from overlapping orb@                  covering windows belonging to the user program.  E               o  If you are stopped at a breakpoint in a routine thatsG                  has control of the mouse pointer by a PointerGrab or a >                  KeyboardGrab, you will hang your workstation.  F                  To work around this problem, debug your program usingH                  two workstations. For more information, see the OpenVMS!                  Debugger Manual.i  H               o  Occasionally, if you are using DECwindows Motif VersionB                  1.1 and are scrolling or clicking on items in theI                  Register View, the following message is displayed in theeH                  DECterm from which you initiated the debugging session:  E                  X Toolkit Warning: Not all children have same parentp(                     in XUnmanageChildren  2                  This error can be safely ignored.  G               o  Table 4-1 lists debugger commands that are disabled ingG                  the DECwindows Motif interface. The debugger issues aneH                  error message if you try to enter any of these disabledE                  commands at the command prompt, or when the debugger E                  executes a command procedure containing any of thesee                  commands.  D               Table 4-1 Debugger Commands Disabled in the DECwindows'                         Motif Interface.  4               ATTACH                          SELECT  C               CANCEL MODE                     (SET, SHOW) ABORT_KEYn  =               CANCEL WINDOW                   (SET, SHOW) KEYb  I                                                  (continued on next page)   I                                                                      4-11  h  w           Programming Release Notesc     4.2 Debugger    =           Table 4-1 (Cont.) Debugger Commands Disabled in the 6                             DECwindows Motif Interface  =           DEFINE/KEY                      (SET, SHOW) MARGINS   =           DELETE/KEY                      SET MODE [NO]KEYPADh  =           DISPLAY                         SET MODE [NO]SCREEN   =           EXAMINE/SOURCE                  SET MODE [NO]SCROLL   A           EXPAND                          SET OUTPUT [NO]TERMINAL   >           EXTRACT                         (SET, SHOW) TERMINAL  <           HELP                            (SET, SHOW) WINDOW  @           MOVE                            (SHOW, CANCEL) DISPLAY  5           SAVE                            SHOW SELECTm             SCROLL  B           o  DECwindows Motif does not provide for specialized key?              support (such as Ctrl/Y), but the DECwindows MotifaD              interface provides alternative means of executing these6              functions (for example, the STOP button).  @           o  Commands related to character-cell terminal displayD              apply only to the command interface. These commands are8              disabled in the DECwindows Motif interface.  A           o  If you have not installed a DECwindows Motif licensee@              (DW-MOTIF) on the node from which you are using theB              debugger, the debugger's GUI fails with the following              error messages:  0         %NONAME-W-NOMSG, Message number 00000000M         -DEBUG-F-FATALSTATUS, a fatal condition was detected by the debugger.tO         %DEBUG-F-INITERR, an error has occurred during debugger initialization, (         unable to continue this session.  ?              To return to DCL level after this failure, enter asC              Ctrl/C or Ctrl/Y key sequence. To correct the problem, E              install a DECwindows Motif license or use the character-m@              cell interface by defining DBG$DECW$DISPLAY to " ".  @           o  The DECwindows Motif interface to the debugger doesB              not use a DECterm. Therefore, commands that require aD              DECterm are disabled in the DECwindows Motif interface.>              The exception is the EDIT command, which is still              available.        4-12 e  o      I                                                 Programming Release NoteslI                                                              4.2 Debugger     F               o  Occasionally, the DECwindows Motif interface does notI                  accept properly formatted Fortran commands. For example, D                  if you select the fragment "qdata( :ilen)" from theG                  program statement "read(qdata( :ilen),100)ivalue" with F                  the mouse and paste it into an EXAMINE command at theC                  DBG> prompt, the debugger issues an error message:n  '             DBG>  EXAMINE qdata( :ilen)DO             DEBUG-E-MISOPEMIS, misplaced operator or missing operand at 'end ofn             expression'   C                  To work around this problem, reenter your command:h  ,                  DBG>  EXAMINE qdata(1:ilen)  .         4.2.2.12 EVALUATE Command (Alpha Only)  C         V1.5  On OpenVMS Alpha systems, when you issue the EVALUATEhG               command for an integer, the debugger truncates the returnr5               value if it is larger than a longword. t  6         4.2.2.13 EXAMINE LABEL[n] Command (Alpha Only)  E         V1.5  On OpenVMS Alpha systems, a command in the form EXAMINEAF               LABEL[n] or EXAMINE LABEL(n), where LABEL is a label forC               a code location and n is an integer, causes an access I               violation error. In this case, the debugger does not handle                the error.  H               Note that this problem does not occur when the label marks@               the start of data storage, as in a MACRO program.            4.2.2.14 Kept Debugger  H         V1.5  The following problems or restrictions are specific to the               Kept Debugger:  B               o  If a previous debugger process has not completelyE                  stopped, you may see the following error at debuggera                  startup:   <                  %DEBUG-E-INTERR, internal debugger error in9                     DBGMRPC\DBG$WAIT_FOR_EVENT got an ACKs  I                                                                      4-13t                Programming Release NotesD     4.2 Debugger    E              To fix this problem, exit the debugger. Then use the DCLVE              command SHOW PROCESS/SUBPROCESS to check if any debugger B              subprocesses exist. If so, you can stop them by usingE              the DCL command STOP. You should then be able to restart.C              the debugger without seeing the error described above.o  ?           o  Ctrl/Y-DEBUG is not supported in the Kept Debuggere              configuration.   @           o  Running a sequence of many large programs may causeC              the debugger to fail because it has run out of memory, 5              global sections, or some other resource.o  C              To fix this problem, exit the debugger and restart the               debugging session.g  @           o  Many commands are disabled when there is no runningC              program. This includes commands that might be expectedfA              to work, such as SET STEP and SET PROMPT/SUFFIX. ThepB              disabled command may cause DBG$INIT files to generateD              %DEBUG-W-NOPROGRAM messages. These commands are enabled2              once a RUN command has been executed.  B           o  The prompt may change when a RUN command is executed.E              It will change back to its former state once the programb              has completed.   @           o  If you are using the DECwindows Motif interface (asC              opposed to character-cell screen mode), and you try to D              run a program that does not exist, or misspell the nameA              of a program that does exist, you may not notice theg1              following error messages displaying:   4              %DCL-W-ACTIMAGE, error activating image2              -CLI-E-IMAGEFNF, image file not found  =              The reason is that DECwindows Motif displays thei?              messages in the DECterm window, rather than in theuC              Command View. Therefore, it is not always obvious thato#              an error has occurred.e  <              To avoid this problem, make sure the "Select an@              application to run" box in the File Selection popup1              contains a valid file specification.   E           o  The %DEBUG-I-INITIAL is not displayed after execution of E              the RERUN/SAVE command. The absence of this message does @              not adversely affect the execution of this command.       4-14    u      I                                                 Programming Release Notes I                                                              4.2 Debuggere    F               o  The Kept Debugger shares I/O channels with the parentB                  process when it is run by a SPAWN/NOWAIT command.B                  Therefore, you must press the Return key twice onB                  the DECterm from which the debugger was run after@                  the debugger version number has appeared in the%                  Communications Pane.   E                  Optionally, you can execute the Kept Debugger in theo"                  following manner:  (                   $ DEFINE DBG$INPUT NL:/                   $ SPAWN/NOWAIT RUN DEBUG/KEEP   I               o  If you issue the RERUN command while your file (that is,hH                  the image you wish to rerun) is locked by another user,<                  the debugger returns the following message:  B                  %DEBUG-E-NORERUNPGM, There is no program to RERUN  D                  This situation might occur, for example, if anotherE                  user has changed the protection on the file. To workaE                  around this problem, have your system manager change D                  the protection. Then, issue a RUN command and reset                  breakpoints.   D         4.2.2.15 SET BREAK/UNALIGNED_DATA Command and Related System*                  Service Call (Alpha Only)  D         V1.5  On OpenVMS Alpha systems, the SET BREAK/UNALIGNED_DATAC               command calls the SYS$START_ALIGN_FAULT_REPORT systempG               service routine. Do not issue this command if the programwF               you are debugging includes a call to the same SYS$START_I               ALIGN_FAULT_REPORT routine. If you issue the command beforeuF               the program call, the program call fails. If the programH               call occurs before you issue the command, unaligned breaks               are not set. N  C         4.2.2.16 Complex Variables in Fortran Programs (Alpha Only)   D         V1.0  On OpenVMS Alpha systems, the debugger cannot evaluateE               expressions that contain complex variables. (Currently,2F               DEC Fortran is the only supported language that providesF               complex variables.) To work around this problem, examineI               the complex variable and then evaluate the expression usingt  I                                                                      4-15d n  e           Programming Release Notes      4.2 Debugger    A           the real and imaginary parts of the expression obtainede$           from the EXAMINE command.   5     4.2.2.17 Concealed Rooted-Directory Logical Namese  ?     V1.0  If you use a rooted-directory logical name to specifyX@           the location of a source file when compiling a program?           with the /DEBUG qualifier, make sure that the rooted-tC           directory logical name is concealed. You must include theoA           /TRANSLATION_ATTRIB=CONCEALED qualifier in your logicalE&           name definition, as follows:  L           DEFINE /TRANSLATION_ATTRIB=CONCEALED root_dir_log_name disk:[dir.]  @           If the rooted-directory logical name is not concealed,A           and you move the source file to another directory after E           compilation, you cannot use the debugger SET SOURCE commandP9           to specify the new location of the source file.   1     4.2.2.18 DEPOSIT/TYPE Command with C Programss  E     V1.0  When debugging a C program, you cannot use the DEPOSIT/TYPEdE           command if the type specified is a mixed or lowercase name. B           For example, suppose the program has a function like the           following:                 xyzzy_type foo ()t               {h                 xyzzy_type     z;                z = get_z ();                return (z);                }  A           If you try to enter the following command, the debuggereE           issues a message that it cannot find the type "xyzzy_type":   5           DBG> DEPOSIT/TYPE=(xyzzy_type) z="whatever"b       4.2.2.19 $HIBER Call  C     V1.0  In the following cases, a user application remains in HIBt           (hibernate) state:  ;           o  If a program, running under the two-process or @              multiprocess debugger, issues a $WAKE call followed?              by a $HIBER call, the user application hibernates.   C           o  If you step inside or interrupt RTL or system services C              routines that make use of $WAKE or $HIBER, for example E              Lib$wait or sys$schdwk, the user application hibernates.        4-16 c  e      I                                                 Programming Release NotesoI                                                              4.2 DebuggerH    G               o  When an application includes the LCK$M_DEQALL modifier D                  in a $DEQ system service call, this modifier breaksH                  communication links between the portion of the debuggerG                  in the user process (the kernel) and the debugger main H                  process. The result is that the user's process stays in'                  hibernate (HIB) state.r  E                  To work around this problem, debug these applicationpD                  programs using the limited one-process mode, ratherE                  than the default or the multiprocess mode. To set up ?                  one-process mode, issue the following command:   .                      $ DEFINE DBG$PROCESS NONE  .         4.2.2.20 Inlined Routines (Alpha Only)  E         V1.0  On OpenVMS Alpha systems, the debugger does not support I               attempts to debug inlined routines. If you attempt to debug D               an inlined routine, the debugger issues a message thatE               it cannot access the routine, as shown in the followingo               example:  B               %DEBUG-E-ACCESSR, no read access to address 00000000  H               To work around this problem, compile your program with the%               /NOOPTIMIZE qualifier.    B         4.2.2.21 Null Frame Procedures and SHOW CALLS (Alpha Only)  D         V1.0  On OpenVMS Alpha systems, there is a problem with nullH               frame procedures that prevents the SHOW CALLS display fromH               including their frames. For more information on null frame<               procedures, see the OpenVMS Calling Standard.   @         4.2.2.22 SHOW BREAK and SHOW TRACE Commands (Alpha Only)  A         V1.0  On OpenVMS Alpha systems, SHOW BREAK and SHOW TRACErF               commands do not display individual instructions when theD               break or trace is on a particular class of instruction<               (such as SET BREAK/CALL or SET BREAK/RETURN).   I                                                                      4-17  i  e           Programming Release Notes      4.2 Debugger    A     4.2.2.23 STEP/INTO Command and User Exception Handlers (Alphao              Only)  C     V1.0  On OpenVMS Alpha systems, when execution is stopped at an C           exception break, STEP/INTO does not transfer control to a D           user exception handler. To work around this problem, set a%           breakpoint on the handler. O  @     4.2.2.24 STEP/OVER Command Error with One-Line Program Loops              (Alpha Only)   @     V1.0  On OpenVMS Alpha systems, when you issue the STEP/OVERD           command at a program loop that is coded on a single sourceB           line, and that source line also contains a routine call,?           the debugger steps into the called routine instead ofgE           stepping to the next source line. In the following example,e>           if you issue the STEP/OVER command when execution isE           stopped at the FOR loop, the debugger steps into the squarekD           routine instead of stepping to the j assignment statement:  '           for (i=0;i<10;i++) square(i);i           j=6;  =           To work around this problem, either set a temporary ?           breakpoint on the line following the FOR loop (in theV?           previous example, j=6), or move the routine call to am$           separate line, as follows:             for (i=0;i<10;i++)              square(i);   +     4.2.2.25 Translated Images (Alpha Only)u  A     V1.0  On OpenVMS Alpha systems, the debugger does not supportnB           attempts to debug translated images. If you must debug aC           translated image, use the Delta/XDelta Debugger. For morebD           information on this debugger, see the OpenVMS Delta/XDelta           Debugger Manual. c       4-18    u      I                                                 Programming Release Notes I                                                              4.2 Debugger     *         4.2.2.26 Vector Support (VAX Only)  D         V5.4  On OpenVMS VAX systems, the following are problems andE               restrictions with the debugger's support for vectorized                programs:   G               o  When the programming language is BLISS, COBOL, or RPG, H                  you must specify a type qualifier to deposit into %VMR.                  For example:E  7                  DEPOSIT/QUADWORD %VMR = %HEX 0FFFFFFFFt  H               o  When the programming language is PL/I, COBOL, or DIBOL,F                  the command EXAMINE %VMR displays %VMR as an array ofE                  bits instead of as a hexadecimal quadword. Enter thelH                  command EXAMINE/HEX/QUADWORD %VMR to obtain the default:                  behavior for other programming languages.  F               o  When the vector mode is synchronized (that is, if youH                  have entered the command SET VECTOR_MODE SYNCHRONIZED),I                  the debugger suspends execution twice at any breakpoints @                  that were set on vector instructions. To resumeD                  execution from such breakpoints, you must enter the+                  GO or STEP command twice.             4.2.3 Corrections   I               This section describes corrections to problems that existedW.               in OpenVMS Debugger Version 6.1.  (         4.2.3.1 Breakpoints (Alpha Only)  D         V6.2  On OpenVMS Alpha systems, a problem that caused missed.               breakpoints has been corrected.   ;         4.2.3.2 Breakpoints and Display of Source and Scopee  H         V6.2  Previously, in the DECwindows Motif interface, the displayB               of the source and scope after a breakpoint event wasG               sometimes incorrect. This problem has been corrected, and E               the scope and source are now kept current and correctly                displayed.  I                                                                      4-19l i  t           Programming Release Notesa     4.2 Debugger         4.2.3.3 COBOL: STEP and GO  @     V6.2  Previously, in COBOL programs, a STEP and GO sometimesC           resulted in %DEBUG-E-ERROR_BLOCK and %DEBUG-I-SS_INT_END.g*           This problem has been corrected.  &     4.2.3.4 Communications Pane Sizing  ?     V6.2  Previously, in the DECwindows Motif interface, if yourC           decreased the size of the Communications Pane so that thesE           prompt was occluded, the message area was not automaticallyl@           scrolled to display the prompt, and you had to use theC           vertical scroll bar to scroll the view so that the promptu6           reappeared. This problem has been corrected.  (     4.2.3.5 DEBUG.EXE Image (Alpha Only)  =     V6.2  Previously, on OpenVMS Alpha as well as OpenVMS VAXd?           systems, you could not debug an image named DEBUG.EXE ?           (a name used internally for the kernel portion of theeE           debugger). This problem has been corrected on OpenVMS Alpha            systems.         4.2.3.6 Edit Save Function  A     V6.2  Previously, in the DECwindows Motif interface, the EdityC           Save function sometimes wrote a corrupt output file. Thise%           problem has been corrected.t       4.2.3.7 EVALUATE Command  >     V6.2  In previous releases, the debugger would generate an@           OPTNOTALLOW error when the Pascal IN operator was usedD           on a packed array in an EVALUATE command. This problem has           been corrected.D  =     4.2.3.8 EXAMINE Command on SCAN Tree Variables (VAX Only)e  ?     V6.2  In previous versions of OpenVMS VAX, an ACCVIO statusoC           resulted from attempts to use the EXAMINE command on SCANG;           tree variables. This problem has been corrected.         4-20           I                                                 Programming Release NotesoI                                                              4.2 Debuggeru    ,         4.2.3.9 Hebrew Command View Messages  G         V6.2  Previously, for the DECwindows Motif interface (V1.2), inpG               the Hebrew version, command view messages were compressedMB               into a single line. This problem has been corrected.  0         4.2.3.10 Include Files in a Text Library  I         V6.2  Previously, when the debugger accessed an include file kept H               inside a text library, it prevented user applications fromF               updating/replacing the include file by means of the text7               library. This problem has been corrected.1  5         4.2.3.11 Monitor View Display of Long Stringso  H         V6.2  Previously, in the DECwindows Motif interface, the MonitorH               View failed to display long strings. This problem has beenF               corrected so that the debugger now truncates the displayH               of long strings in the Monitor View at 256 characters, and9               reports this with an informational message.   (         4.2.3.12 Multidimensional Arrays  F         V6.2  In previous releases, sometimes the debugger incorrectlyB               examined nonzero-based multidimensional arrays. This)               problem has been corrected.P  *         4.2.3.13 PL/I Controlled Variables  F         V6.2  In previous releases, the debugger generated an internalI               error on attempts to examine PL/I controlled variables thatg;               were arrays. This problem has been corrected.   #         4.2.3.14 Process Dump Filese  G         V6.2  Previously, the debugger could not analyze a process dumpcG               file if the dump described an exception where the programaE               counter (PC) was zero. This problem has been corrected.t  ,         4.2.3.15 Radixes for Monitored Items  D         V6.2  Previously, if you attempted to typecast or change theB               radix for a monitored item (for example, a task in aD               multitasking program) where deposit operations did notF               make sense, the debugger did not issue an error message.H               Instead, it tried to complete the operation and then froze;               the display. This problem has been corrected.   I                                                                      4-21     n           Programming Release Notes      4.2 Debugger    .     4.2.3.16 Records with the Same Symbol Name  D     V6.2  Previously, when more than one record used the same symbolA           name, an examine sometimes provided information for therC           wrong record, even if fully scoped. This problem has beene           corrected.       4.2.3.17 RERUN/SAVE Commandt  >     V6.2  In previous releases, 'EVENT=' type breakpoints wereB           not saved during execution of a RERUN/SAVE command. This%           problem has been corrected.F       4.2.3.18 SET RADIX Command  C     V6.2  When you use the SET RADIX command, the radix you specifysC           now correctly persists across runs, reruns, set language,d"           set image, and so forth.  *     4.2.3.19 SET SOURCE Command (VAX Only)  A     V6.2  In Version 6.1 of the OpenVMS VAX debugger, the default >           behavior of the SET SOURCE command was inadvertentlyB           changed to SET SOURCE/LATEST. The default setting of theC           SET SOURCE command has been restored to SET SOURCE/EXACT, D           as it was in OpenVMS VAX Version 6.0 and previous versions           of the debugger.    ;     4.2.3.20 User-Written System Service Calls (Alpha Only)   E     V6.2  On OpenVMS Alpha systems, a problem involving stepping over B           CHM* and "misdirected" user-written system service calls           has been corrected.   !     4.2.3.21 Watchpoint Reportinga  B     V6.2  In previous releases, the debugger did not always report7           watchpoints. This problem has been corrected.   -     4.2.3.22 Watchpoint Setting on Bit Fieldsh  B     V6.2  In previous releases, in the DECwindows Motif interface,C           the debugger sometimes failed to set watchpoints on a bit 1           field. This problem has been corrected.p       4-22 h         I                                                 Programming Release Notes I                                                               4.3 DEC C++s             4.3 DEC C++l  H               The following sections contain release notes pertaining to               DEC C++.  '         4.3.1 Problems and Restrictionsl  ?               This section describes known DEC C++ problems and                restrictions.   E         4.3.1.1 SYS$LIB_C.TLB Structures Need Prototypes (Alpha Only)   G         V6.1  DEC C++ users who include header files from SYS$LIB_C.TLBaH               may receive compiler errors. Many of the structures withinG               SYS$LIB_C.TLB contain pointers to other structures. TheseoI               pointers are defined using the tag name of the structure totI               which it points. In C, if you declare something using a tagAI               name, it is not necessary to predefine it. DEC C++ requires E               that the name be predefined. If the header file you are G               including contains any pointers to structures, it will ben@               necessary to create structure prototypes for them.  F               As an example, the inclusion of a header file (header.h)+               that contained the following:   (               typedef struct  _structa {+                   struct _structb    *ptr1;r+                   struct _structc    *ptr2;a               } STRUCTA;  F               would require the following structure prototypes defined6               before the #include for the header file:                 struct  _structb;                struct  _structc;p  "               #include <header.h>   !         4.4 DEC C++ Class Libraryu  G               This section contains release notes pertaining to the DECa                C++ class library.  I                                                                      4-23                 Programming Release Notes      4.4 DEC C++ Class Libraryl    "     4.4.1 Changes and Enhancements  B           This section describes enhancements to the DEC C++ class           library.  !     4.4.1.1 Object Library Formate  ?     V6.2  The DEC C++ class library has always been provided inn?           shareable image format. Starting with OpenVMS VersionEC           6.2, the DEC C++ class library is also provided in objectaE           library format. Please refer to the OpenVMS Version 6.2 NewIE           Features Manual for details about linking using this objecto           library.       4.4.2 CorrectionsB  B     V6.2  The following problems that existed in the DEC C++ class=           library in OpenVMS Version 6.1 have been corrected:t  A           o  An access violation is no longer generated when youru>              application writes into an uninitialized ostream_E              withassign. Instead, the written text is simply ignored.o  >           o  The class library image supplied with OpenVMS VAX@              Version 6.1 and with the ECO for DEC C/C++ Run-Time>              Components for VAX/VMS (AACRTVAXE02060 or CSCPAT_D              1150012) incorrectly defined the size of a strstreambufE              to be several bytes larger than the defined header file.p@              So if your application declared a strstreambuf, theD              strstreambuf constructor and several other strstreambuf>              functions would write into the memory beyond thatC              allocated for your strstreambuf. The consequences were)              unpredictable.9  E           o  An access violation no longer occurs when a null pointeri@              is passed to the insertion operator (<<) within the              ostream class.o  >           o  The dynamic expansion of strstream and ostrstreamC              buffers has been corrected on OpenVMS VAX. Previously,tC              when data was inserted that overflowed the buffer, therB              expansion of the buffer could fail even if memory wasB              available. This resulted in the buffer contents being              truncated.        4-24           I                                                 Programming Release Notes I                                                 4.4 DEC C++ Class Library     F               o  A file-positioning problem for bidirectional fstreamsD                  has been corrected. Previously, if your applicationH                  switched from reading an fstream to writing an fstream,C                  with or without an intervening seek operation, the H                  necessary synchronization of the external file positionF                  with the get pointer was often skipped. This resultedH                  in the written data being placed incorrectly within the                  file.  C               o  The real() function within the stopwatch class wasoG                  incorrectly returning the CPU time. Now it returns the *                  clock time as documented.  F               o  The >> operator within the istrstream class now worksE                  correctly when the conversion base format is hex and H                  hexadecimal values are read that begin with "0" but are(                  not prefixed with "0x."  B               o  The flush() function within the ostream class wasB                  incorrectly calling overflow(). Now flush() calls&                  sync() as documented.  C               o  The ignore() function within the istream class nowiI                  works correctly. Previously it would ignore two and onlym                   two characters.  D               o  The input functions within the stdiostream class no3                  longer skip every other character.t  D               o  The sync_with_stdio() function within the ios classG                  no longer causes subsequent istream operations to skipa'                  every other character.   A               o  The SYS$OUTPUT and SYS$ERROR files are no longerSC                  opened during the initialization of cout and cerr, F                  respectively. Previously this behavior resulted in anF                  empty file being created when SYS$OUTPUT or SYS$ERRORG                  was defined to be a file and the application generated                   no output.   G               o  The showpoint flag within the ios class now forces the /                  decimal point to be displayed.       I                                                                      4-25e u  n           Programming Release Noteso     4.5 DEC C Run-Time Library         4.5 DEC C Run-Time Library  D           The following sections contain release notes pertaining to+           the DEC C Run-Time Library (RTL).R  "     4.5.1 Changes and Enhancements  B           This section describes changes and enhancements to DEC C           RTL software./  >     4.5.1.1 Floating-Point Values Now Conform to IEEE Standard  =     V6.2  The ecvt, fcvt, and gcvt functions were modified tou>           represent the following values specified in the IEEE1           Standard for floating-point arithmetic:   )           Value            Representationf             Quiet NaN        NaNQe             Signaling NaN    NaNSt  #           +Infinity        Infinityt  $           -Infinity        -Infinity  D           The sign associated with each of these values is stored inD           the sign parameter of ecvt, fcvt, and gcvt. Also note thatD           in IEEE Floating Point, a value of zero can be positive or1           negative, as set by the sign parameter.=  @     4.5.1.2 Getenv Function Now Performs Case-Insensitive Lookup  =     V6.2  The function getenv was enhanced to perform a case- @           insensitive lookup if the case-sensitive lookup fails.D           In most instances, logical names are defined in uppercase.@           The getenv function now can find logicals that include(           lowercase letters in the name.  (     4.5.1.3 Internationalization Support  C     V6.2  The DEC C RTL has added capabilities to allow application @           developers to create international software. The DEC CC           RTL obtains information about a language and a culture by 5           reading this information from locale files.6  A           If you are using these DEC C RTL capabilities, you musth?           install a separate kit to provide these files to your C           system. The save set, VMSI18N062, is provided on the same '           media as OpenVMS Version 6.2.i       4-26    R      I                                                 Programming Release Notes H                                               4.5 DEC C Run-Time Library    C               To install this save set, follow the standard OpenVMS E               installation procedures using this save set name as theMH               name of the kit. There are four categories of locales thatG               you can select to install. You may select as many localesa=               as you need by answering the following prompts:   5                  Do you want European and US support?n-                  Do you want Chinese support?v.                  Do you want Japanese support?,                  Do you want Korean support?  F               This kit also has an Installation Verification ProcedureC               that Digital recommends you run to verify the correctk&               installation of the kit.  9         4.5.1.4 Math Functions Conform to XPG4 (VAX Only)   B         V6.2  The following changes have been made to DEC C RTL inF               OpenVMS VAX Version 6.2 so that the behavior now matches,               that on OpenVMS Alpha systems.  F               o  The behavior of the log, log10, and pow functions nowE                  conforms to the behavior specified by XPG4. As such, E                  log and log10 of zero return -HUGE_VAL and set errnoiH                  to ERANGE; pow of zero with a negative exponent returnsI                  -HUGE_VAL and sets errno to EDOM; and pow of zero with an,                  zero exponent returns 1.0.   6         4.5.1.5 Open Routines Now Validate RMS Options  C         V6.2  The open, fopen, and creat functions no longer ignore C               invalid RMS options. If an unrecognized RMS option is.F               passed as a parameter to these functions, a return valueC               of -1 is returned and errno is set to EINVAL (InvalidB               argument).            4.5.1.6 Setvbuf Function  C         V6.2  The setvbuf function has been changed to give it more H               functionality and make it more compatible with the setvbuf2               function on other operating systems.  F               Prior to this release, if the buffer argument to setvbufA               was NULL, setvbuf would reset the buffer to the onetB               allocated by the DEC C RTL when the file was opened.E               Starting with Version 6.2, if a NULL buffer argument is.D               passed and the size argument is larger than the buffer  I                                                                      4-27  e  E           Programming Release Notesr     4.5 DEC C Run-Time Library    @           allocated by the RTL when the file was opened, setvbufA           allocates a buffer equal to the specified size and uses "           that as the file buffer.  6     4.5.1.7 Sleep Function Now Returns Unslept Seconds  A     V6.2  The return value of the sleep function has been changedcB           to be in line with the System V Interface Definition andC           the X/Open Portability Guide, Release 4. The return value A           is the number of seconds that it prematurely awoke, duenA           to the delivery of a signal or a call from the sys$wake C           function. A return value of zero is returned when a sleep D           call waits the entire time period. Prior to these changes,E           the sleep function returned the number of seconds that were            originally requested.s  9     4.5.1.8 Wildcards No Longer Accepted by stat Function   D     V6.2  The stat function no longer accepts wildcard characters asD           part of the file specification. If a wildcard character isB           found, stat returns -1 and sets errno to ENOENT (No such           file or directory).t  <     4.5.1.9 Writing to Pipes Now Conforms to POSIX Standards  D     V6.2  The DEC C RTL now properly deals with EOF when reading andD           writing to pipes. The correct behavior is described in theC           IEEE standard P1003.1-1988, Section 6.4.1.2, which stateslC           that an EOF is written to a pipe only when no writers arer@           left. Previously, the DEC C RTL wrote an EOF to a pipe,           every time a writer closed a pipe.  E           The DEC C RTL no longer incorrectly writes an EOF to a pipepC           when the user issues a write of zero bytes. The correctedoB           behavior now conforms to the IEEE Standard P1003.1-1988,D           Section 6.4.1.2, which states that writing zero bytes to a           file has no effect.l  #     4.5.2 Problems and Restrictionse  E           This section describes DEC C RTL problems and restrictions.i             4-28           I                                                 Programming Release NotesoH                                               4.5 DEC C Run-Time Library    =         4.5.2.1 SYS_ERRLIST and SYS_NERR Symbols (Alpha Only)d  I         V6.2  The symbols SYS_ERRLIST and SYS_NERR have been removed from F               object library SYS$LIBRARY:STARLET.OLB. If you see theseH               symbols being undefined during a link operation, read fileI               SYS$LIBRARY:DECC$SYS_ERRLIST.COM for instructions on how toe$               resolve this problem.   '         4.5.2.2 DECC$SHR.EXE (VAX Only)   E         V6.2  A new package of internationalization routines has been B               added to the DEC C RTL (see Section 4.5.1.3) and theA               transfer vector has been extended, necessitating anvI               increase in the minor ident (GSMATCH) of the image. Because I               of this, programs using the DEC C RTL (DECC$SHR.EXE) linkedrF               on OpenVMS VAX Version 6.2 systems will not run on prior'               versions of OpenVMS VAX.    ?         4.5.2.3 Internationalization Compatibility Problem withe                  DECwindows Motif  @         V6.2  Applications that call the Xlib locale routines inG               DECwindows Motif Version 1.2-3 using the method describedeF               in Section 4.18.5.3 of the DECwindows Motif Version 1.2-F               3 for OpenVMS Release Notes will continue to function onF               OpenVMS Version 6.2. However, because the locale supportE               in Xlib is not compatible with the support in the DEC CeD               Run-Time Library (DECC$SHR.EXE), Xlib does not use theF               locale environment provided by the C library. Therefore,E               setting the locale in the C library does not affect the E               behavior of DECwindows Motif, although it does affect CnG               library routines such as strcoll(). Setting the locale inrH               Xlib changes the behavior of DECwindows Motif but does not(               affect C library routines.  @               Applications that call the Xlib locale routines inE               DECwindows Motif Version 1.2 using the method describedaG               in the DECwindows Motif Version 1.2-3 for OpenVMS ReleasefF               Notes, Section 4.17.6.3, do not run correctly on OpenVMSI               Version 6.2 unless you install the DECwindows Motif Version I               1.2 remedial kit appropriate for your system (see the tablesH               in Section 3.11.2.5). With the remedial kit installed, theG               Xlib locale routines work normally, but Xlib does not usei?               the locale environment provided by the C library.n  I                                                                      4-29e t              Programming Release Notes      4.5 DEC C Run-Time Library    E           Digital expects to correct this problem in a future releasee           of DECwindows Motif.       4.5.2.4 Regular Expressionse  E     V6.2  Regular expressions in the source string passed to decc$to_rB           vms do not work properly. Operations result in either anE           ACCVIO status return or a return value of 0 indicating that &           no files match the wildcard.  6     4.5.2.5 Simultaneously Opened Files Limited to 256  D     V6.2  DEC C RTL limits the number of simultaneously opened files           to 256.        4.5.3 Correctionsl  >           This section describes corrections to the DEC C RTL.  ;     4.5.3.1 Maximum Record Size Is Now Set for Stream FilesL  C     V6.2  DEC C RTL no longer ignores the Maximum Record Size (mrs)rE           value when it is provided by the caller. Previously, streamvB           files would always be created with a maximum record sizeD           of 32767, regardless of the specified mrs value. Note thatE           the DEC C RTL does not validate the integer used as the mrs E           value. Application developers should not use values greater 4           than 32767 to specify record sizes to RMS.  $     4.5.3.2 Undefined Record Formats  D     V6.2  The I/O system now properly inherits a record attribute ofC           none when a previous version of the file had an undefinedsA           record format. Previously, the newly created file would @           be created with carriage return record attributes. TheC           functions fopen, open, and creat have also been correctedcC           to allow the RMS option "rat=none" to override the record 9           attributes of the previous version of the file.        4.5.4 Programming Tips  B           This section contains helpful programming tips for DEC C           RTL users.         4-30    u      I                                                 Programming Release NotesrH                                               4.5 DEC C Run-Time Library    *         4.5.4.1 RMS-11 Stream Format Files  G         V6.1  RMS defines an RMS-11 stream format file that corresponds C               to the value of FAB$C_STM for the record format. ThissG               format definition causes the RMS record operation SYS$GETcD               to remove leading null bytes from each record. BecauseF               DEC C RTL processes this file type in record mode, it isE               not a suitable file format for binary data unless it is H               explicitly opened with "ctx=stm" to cause the raw bytes of0               data from the file to be returned.  =         4.6 DECmigrate: Translated Image Support (Alpha Only).           V6.1  H               DECmigrate Version 1.1A runs on OpenVMS Alpha Version 6.1.F               The images it translates require this version or a laterI               version to execute. Translated images are generally forwardvE               compatible but not backward compatible; that is, imageseE               translated with DECmigrate Version 1.1A can run only on H               OpenVMS Alpha Version 6.1 or later while images translatedB               with DECmigrate Version 1.0 can run on OpenVMS AlphaF               Version 1.0 and later. Table 4-2 correlates the versionsE               of OpenVMS Alpha systems with the different versions of +               DECmigrate that support them.   F               Table 4-2 Support for Translated Images on OpenVMS Alpha                          Versions                 DECmigrate               Version Used               to TranslateH               Images         OpenVMS Alpha Support for Translated ImagesH                                                          Version 6.1 and<                              Version 1.0   Version 1.5 later  <               Version 1.0    Yes           Yes           Yes  <               Version 1.1    No            Yes           Yes  <               Version 1.1A   No            No            Yes        I                                                                      4-31X r  o           Programming Release Notess     4.7 DECthreads         4.7 DECthreads  D           The following sections contain release notes pertaining to           DECthreads.s  D           See the Guide to DECthreads for detailed information about$           using DECthreads software.  #     4.7.1 Problems and Restrictionse  >           This section describes known DECthreads problems and           restrictions.   $     4.7.1.1 Dynamic Image-Activation  D     V6.2  Applications that use thread-safe run-time libraries mightA           not be able to use LIB$FIND_IMAGE_SYMBOL to dynamicallyiD           activate DECthreads or products that depend on DECthreads.  D           Certain run-time libraries use conditional synchronizationC           mechanisms. These mechanisms typically are enabled during B           image initialization when the run-time library is loadedE           only if the process is multithreaded. If the process is not 9           multithreaded, the synchronization is disabled.   D           If a single-threaded application attempts to use LIB$FIND_@           IMAGE_SYMBOL to activate an image that would cause theB           process to become multithreaded, a LIB$_REENTRANCY error3           occurs and the application is terminated.m  <           This termination ensures that threads can never beB           present when run-time libraries are not using the proper           synchronization.  @           To work around this problem, link the image that calls0           LIB$FIND_IMAGE_SYMBOL against CMA$RTL.        4.7.1.2 Exit Handler Routine  <     V6.1  If you try to abort a program that uses DECthreads@           functions in an exit handler routine by using a Ctrl/YB           sequence followed by the DCL EXIT command (or almost anyE           DCL command), the program may hang indefinitely in the exitn           handler routine.  D           One instance of this problem occurs when you type a Ctrl/YE           sequence to interrupt a multithreaded program in the middleoD           of a C RTL I/O function. The problem is with the operatingB           system, not with your program code or the C RTL code. To       4-32 e  i      I                                                 Programming Release NoteshI                                                            4.7 DECthreadsT    F               release your program from the exit handler routine, typeG               another Ctrl/Y sequence followed by the DCL STOP command.p  I               Digital expects to correct this problem in a future releaset.               of the OpenVMS operating system.  ;         4.7.1.3 Routines Can Terminate Process (Alpha Only)   H         V1.0  The DECthreads routines cma_thread_exit_error, cma_thread_H               exit_normal, and pthread_exit should terminate the callingH               thread only. However, these routines erroneously cause theF               process to terminate when they are called in the initial               thread.   C               This problem will be corrected in a future version of                OpenVMS Alpha.    '         4.8 DECTPU for DECwindows Motifs  H               The following sections contain release notes pertaining to*               DECTPU for DECwindows Motif.  '         4.8.1 Problems and Restrictions   I               This section describes DECTPU for DECwindows Motif problemsa               and restrictions.   H         4.8.1.1 Small Display Monitors and DECwindows Motif Applications  C         V6.0  When running DECwindows Motif DECTPU on small displaynG               monitors, the main window can be less than fully visible.a  <               To correct this condition, follow these steps:  F               1. Add the following resources to your DECTPU X resource                  file:  B                  Tpu.Tpu$MainWindow.X:                           0B                  Tpu.Tpu$MainWindow.Y:                           0C                  Tpu.Tpu$Mainwindow.Rows:                        21 C                  Tpu*condensedFont:                              on B                  Tpu*fontSetSelection:                           1  H               2. Copy the resource file from SYS$LIBRARY:EVE.DAT and add$                  the previous lines.  B               3. Use logical name TPU$DEFAULTS to point at the new                  resource file.b  I                                                                      4-33u e  i           Programming Release Notesm#     4.8 DECTPU for DECwindows Motift    C              The following example invokes the EVE DECwindows Motif0@              user interface using the X resource file named eve_A              small_window.dat in your login directory to edit the               file LOGIN.COM.  A              $ DEFINE TPU$DEFAULTS SYS$LOGIN:EVE_SMALL_WINDOW.DAT-2              $ EDIT/TPU/INTER=DECWINDOWS LOGIN.COM  "     4.9 DECwindows Motif Transport  D           The following sections contain release notes pertaining to)           the DECwindows Motif Transport.        4.9.1 Correctionst  D           This section describes corrections to the DECwindows Motif           Transport.  &     4.9.1.1 User-Written Modifications  E     VAX   The DECwindows Motif Transport has been modified to correct A     V6.0  previous disconnect problems. Under certain conditions,p@     Alpha pending ASTs could be sent after the Transport cleanupB     V6.1  process had begun. As a result, the AST could attempt toE           access data that had already been deallocated, which caused .           access violations or system crashes.  ;           Queuing the CLOSE_AND_DEALLOCATE_AST AST from the B           DECW$$TCPIP_CLOSE routine is an incomplete solution. The?           CLOSE_AND_DEALLOCATE_AST AST is queued to the current B           operation mode (EXEC), and this AST could be sent before!           pending USER mode ASTs.f  @           The Transport Function Table (XTFT) data structure hasD           been modified and a new common routine has been added. TheC           XTFT data structure has been increased by one longword togE           provide an additional routine entry, XTFT$A_DISCONNECT. TheO6           new common routine is DECW$XPORT_DISCONNECT.  B           If you have written your own DECwindows Motif Transport,D           you can implement these modifications, based on the Sample@           Transport implementation Digital recommends in the VMS&           DECwindows Transport Manual.       4-34 e  n      I                                                 Programming Release NotesLI                                            4.9 DECwindows Motif Transport     F                 ________________________ Note ________________________  F                 You must recompile any user-written specific transport5                 that uses the XTFT$C_LENGTH constant.   F                 ______________________________________________________  H               o  Create a new routine to remove the cleanup instructionsF                  from the CLOSE_AND_DEALLOCATE_AST AST. Store this newE                  routine address in the XTFT data structure at offsetaB                  XTFT$A_DISCONNECT. The XTFT is initialized in theD                  DECW$TRANSPORT_INIT routine. This new routine takes%                  the IXTCC parameter..  G               o  From DECW$$TCPIP_CLOSE, queue CLOSE_AND_DEALLOCATE_ASTw$                  as a USER mode AST.  A               o  Inside CLOSE_AND_DEALLOCATE_AST, call the CommonhA                  Transport routine DECW$XPORT_DISCONNECT, passingcD                  an IXTCC parameter. DECW$XPORT_DISCONNECT will callB                  the routine stored in XTFT[XTFT$A_DISCONNECT]. ByF                  dispatching the disconnect routine through the CommonI                  Transport layer, the process will change to EXEC mode as 8                  required to deallocate data structures.  "         4.10 Delta/XDelta Debugger  H               The following sections contain release notes pertaining to(               the Delta/XDelta debugger.  '         4.10.1 Changes and Enhancementse  C               This section describes changes or enhancements to thea               software.   .         4.10.1.1 Image Activation (Alpha Only)  H         V6.1  Because of enhancements to the OpenVMS Debugger, the imageE               activator on OpenVMS Alpha systems has been modified totE               automatically activate SYS$SHARE:SYS$SSISHR.EXE when an.H               image is debugged using the RUN/DEBUG command or is linked)               using the /DEBUG qualifier.g  I                                                                      4-35                Programming Release Notes      4.10 Delta/XDelta Debugger    5           If the Delta/XDelta debugger is being used,rA           SYS$SHARE:SYS$SSISHR.EXE may be automatically activated >           for you. The presence of this image should not alter<           your program's correctness, but if your program isC           sensitive to virtual address layout or if for some reason D           SYS$SHARE:SYS$SSISHR.EXE is not installed properly on yourB           system, you may want to bypass its automatic activation.  5           To keep the image activator from activatingcC           SYS$SHARE:SYS$SSISHR.EXE for you, define the logical nametE           SSI$AUTO_ACTIVATE to be "OFF" before running the program to )           be debugged with Delta/XDelta. e  0     4.10.2 Documentation Changes and Corrections  @           This section describes corrections to the Delta/XDelta           documentation.  1     4.10.2.1 OpenVMS Delta/XDelta Debugger Manualh  ?     V1.5  The base register default offset for OpenVMS Alpha isAE           10000(16), not 100000(16), as documented in the descriptiong1           of the ;X (Load Base Register) command.R  0     4.11 Device Support on OpenVMS Alpha Systems  D           The following sections contain release notes pertaining to'           OpenVMS Alpha device drivers.   1     4.11.1 Changes and Enhancements (Version 6.2)   A           This section describes OpenVMS Alpha Version 6.2 device *           support changes or enhancements.  1     4.11.1.1 Driver Compatibility for Version 6.2   @     V6.2  Most OpenVMS Alpha Version 6.1 device drivers will run>           on OpenVMS Alpha Version 6.2 without recompiling andC           relinking. However, you must make source code changes andoB           recompile and relink the following OpenVMS Alpha Version           6.1 device drivers:   C           o  OpenVMS Alpha device drivers written for PCI, EISA, or @              ISA devices that perform direct memory access (DMA)  =           o  OpenVMS Alpha SCSI port and class device driverst       4-36 o         I                                                 Programming Release Notes I                              4.11 Device Support on OpenVMS Alpha Systems     F               For more information about the OpenVMS Alpha Version 6.2H               changes required for device drivers written for PCI, EISA,I               or ISA devices that perform direct memory access (DMA), see H               Section 4.11.1.3. For more information about OpenVMS Alpha@               SCSI port and class drivers, see Section 4.11.1.5.  >               For details about ISA device configurations, see               Appendix A.t  E         4.11.1.2 Improving Performance of Device Drivers Written in Ca  @         V6.2  Additional pragmas have been added to the C header@               files that define the following data structures in(               SYS$LIBRARY:SYS$LIB_C.TLB:  -               ACB           AST Control Blockf  4               BOD           Buffer Object Descriptor  3               CCDB          Class Driver Data Blocki  7               CDRP          Class Driver Request Packete  (               CPU           CPU Database  >               CRAMH         CSR Register Access Mailbox Header  -               DDB           Device Data Blockn  1               DDT           Driver Dispatch Table   1               DPT           Driver Prologue Table   3               FDT           Function Decision Table   E               FDT_CONTEXT   Function Decision Table Contect Structure.  &               FKB           Fork Block  6               FT_UCB        Pseudo Terminal Driver UCB  @               HW_CRAM       Hardware CSR Register Access Mailbox  6               INTSTK        Interrupt Stack Structures  >               IRPE          Interrupt Request Packet Extension  0               KPB           Kernel Process Block  :               LTRM_UCB      Logical Terminal UCB Extension  1               PCB           Process Control Block   *               PHD           Process Header    I                                                                      4-37  r  i       Programming Release Notess0     4.11 Device Support on OpenVMS Alpha Systems  (           PTE           Page Table Entry  $           SB            System Block  6           SCDRP         SCSI Class Driver Reset Packet  2           SPDT          SCSI Port Descriptor Table  *           TAST          Terminal AST Block  @           TPD_UCB       Terminal Port Driver Dependent Extension  )           TQE           Timer Queue EntryT  +           TTY_UCB       Terminal Driver UCB   =           The compiler generates more efficient code when your<           reference the members of these structures. To takeC           advantage of this enhancement and improve the performancewC           of your OpenVMS Alpha device driver that is written in C,o            recompile your driver.  #     4.11.1.3 PCI DMA Window Changesu  E     V6.2  This release note should be read by anyone writing a drivert)           for a PCI, EISA, or ISA device.i  ?           PCI bus implementations on Alpha platforms define twoaD           ways for PCI devices to access main memory: scatter/gatherE           memory access and physical memory access. In scatter/gatheriB           memory access, the PCI address generated by a PCI deviceD           is translated to a main memory address by a scatter/gatherD           table. In physical memory access the PCI address generatedC           by a PCI device is translated to a main memory address by E           the addition of a constant. Scatter/gather memory access is E           called scatter/gather DMA. Physical memory access is calledl#           physical (or direct) DMA..  9           Each memory access technique has advantages and @           disadvantages. Scatter/gather DMA allows access to allD           system memory, but it is more complex to program. PhysicalB           DMA is easier to program, but it may limit the amount of,           main memory that can be addressed.  >           Alpha PCI platforms implement scatter/gather DMA andB           physical DMA through DMA address windows on the PCI bus.A           A PCI DMA address window is an address range on the PCI D           bus through which PCI devices (and EISA/ISA devices behindD           the PCI/EISA bridge or PCI/ISA bridge) access main memory.A           The Alpha platforms that support PCI buses (AlphaServerr?           2000, AlphaServer 2100, AlphaServer 1000, AlphaServer,D           400, AlphaServer 8200, AlphaServer 8400, AlphaStation 200,@           AlphaStation 250) provide a minimum of two DMA address?           windows on the PCI bus. A DMA address window can be a        4-38 A  a      I                                                 Programming Release Notes I                              4.11 Device Support on OpenVMS Alpha Systems     F               physical DMA window, where a PCI bus address is a linearF               function of a system memory address, or a scatter/gatherH               DMA window, where a PCI bus address undergoes a page table@               translation before becoming a main memory address.  I               Alpha platforms that support PCI buses have both a physical6D               DMA window and a scatter/gather DMA window. In OpenVMSA               Alpha Version 6.2, the scatter/gather DMA window is E               based at PCI address 0 and extends to a maximum address D               of 3FFFFFFF (the actual size of the scatter/gather DMAF               window is a function of the amount of physical memory inE               the system). In OpenVMS Alpha Version 6.2, the physical F               DMA window is typically based at a PCI address above the(               scatter/gather DMA window.  C               To allow drivers to find the base of the physical DMA G               window in a platform independent manner, two new function H               codes have been added to the bus support routine IOC$NODE_H               DATA. The basic definition of the IOC$NODE_DATA routine is               as follows:   O            int ioc$node_data (CRB  *crb, int  function_code, void *user_buffer)a                 Inputs:a  E               crb              Address of CRB. IOC$NODE_DATA uses the H                                crb$l_node field and the vec$ps_adp fieldE                                to find the data structures associatediG                                with the I/O bus to which this device is )                                connected.   B               function_code    From [lib.lis]iocdef.sdl. SpecifiesF                                information to be returned by IOC$NODE_$                                DATA.  F               user_buffer      Address of caller's buffer. On success,G                                the requested information is returned in 3                                the caller's buffer.                  Outputs:  F               SS$_NORMAL       Normal successful completion. RequestedF                                information is returned in the caller's&                                buffer.  :               SS$_ILLIOFUN     Unrecognized function code.  I                                                                      4-39r u  e           Programming Release Notese0     4.11 Device Support on OpenVMS Alpha Systems      A           SS$_BADPARAM     Bad parameter. Usually this means that >                            crb$l_node contains an invalid slotA                            number. Check that the driver has been ;                            loaded with the /node qualifier.O  ?           When called with function code IOC$K_DIRECT_DMA_BASE, C           the IOC$NODE_DATA routine returns the base address of the D           physical DMA window. The base address is returned as a 64-C           bit value in anticipation of future 64-bit I/O buses. For7E           this reason, the caller of the IOC$NODE_DATA routine shouldlA           make sure the user_buffer argument points to a quadword B           cell when using the IOC$K_DIRECT_DMA_BASE function code.  C           When called with function code IOC$K_DIRECT_DMA_SIZE, thegD           IOC$NODE_DATA routine returns the size of the physical DMAD           window, expressed in megabytes. The size of the direct DMA/           window is returned as a 32-bit value.e  9           Using the physical DMA window for device DMA isH>           straightforward. Once you have found the base of theB           physical DMA window using the IOC$NODE_DATA routine, youC           must adjust the DMA address that you assign to the devicevC           by adding the physical DMA window base to the main memoryDB           DMA buffer address. For example, on a typical system theB           physical DMA window is based at the PCI address 40000000B           and extends to 7FFFFFFF. PCI addresses in the range fromB           40000000 to 7FFFFFFF are passed to main memory addressesA           0 to 3FFFFFFF. This means that if you have a DMA bufferDD           at main memory address 0, the PCI device would access thisD           buffer at PCI address 40000000. The correspondence of main@           memory address and PCI DMA addresses is derived by the           following formula:  P   PCI DMA address = (main memory buffer address) + (base of physical DMA window)  C           The main reason for locating the PCI DMA windows this way A           is to support bit-limited ISA devices. In OpenVMS Alpha A           Version 6.1, bit-limited ISA bus masters cannot use the B           scatter/gather DMA window because ISA bus masters do notB           have enough address bits to generate an address above 16E           MB. For this reason, the Scatter/Gather window was moved toLE           PCI address 0. The scatter/gather table is now managed such C           that EISA and ISA devices that perform DMA in the scatter >           /gather window always get bus addresses below 16 MB.       4-40           I                                                 Programming Release NotesrI                              4.11 Device Support on OpenVMS Alpha SystemsD    F               Note that the size of the physical DMA window limits theG               amount of physical memory that can be addressed by a PCI, H               EISA, or ISA device. In the physical DMA window, it is notE               possible for an I/O device to address more than 1 GB ofGG               physical memory. For this reason, on large memory systemseD               you may want to code your driver to perform DMA in theG               scatter/gather window. To perform scatter/gather DMA, userI               the standard counted resource management routines described.C               in the OpenVMS AXP Device Support: Developer's Guide.o  -         4.11.1.4 Device IPL Setup for Driverso  F         V6.2  Alpha hardware platforms that support PCI, EISA, and ISAD               buses deliver I/O device interrupts at different IPLs,E               either 20 or 21. The IPL at which device interrupts aredB               delivered can change if you move the device from oneB               platform to another. This is a problem if the driverG               declares its device IPL to be 20, and then that driver islG               executed on a machine that delivers I/O device interruptsn               at IPL 21.  I               The simplest solution to this problem is for PCI, EISA, andsH               ISA device drivers to use IPL 21. This will work correctlyG               on platforms that deliver I/O device interrupts at IPL 20 H               and on platforms that deliver I/O device interrupts at IPL               21.a  F               A future release of OpenVMS Alpha may provide a platformG               independent mechanism for drivers to determine the devicew               IPL dynamically.  3         4.11.1.5 SCSI Port and Class Driver Changese  F         V6.2  The following sections describe changes to OpenVMS Alpha1               SCSI class and port device drivers.n  @               4.11.1.5.1 OpenVMS Alpha SCSI Class Driver Changes  D         V6.2  Some SCSI-2 port interface (SPI) macros that supportedE               OpenVMS Alpha SCSI class device drivers for Version 6.1_H               have been changed for OpenVMS Alpha Version 6.2. Table 4-3G               lists the obsolete Version 6.1 macros and the Version 6.2a1               macros that have similar functions._    I                                                                      4-41h l  u           Programming Release Notes 0     4.11 Device Support on OpenVMS Alpha Systems    D           Note that many of the Version 6.2 SPI macros use differentA           names, and most of them require new arguments. For this B           reason, do not replace each reference to an obsolete SPIE           macro without taking into account the OpenVMS Alpha VersionC            6.2 interface changes.  A           You can obtain the new SPI$ interface macro definitionss@           by extracting them from SYS$LIBRARY:LIB.MLB, using the           following command:  P           $ LIBRARY/EXTRACT=SPI$*/OUTPUT=SPI$DEFINITIONS.MAR SYS$LIBRARY:LIB.MLB  1           Table 4-3 Obsolete SPI Interface MacrosT  C           Obsolete V6.1 Macro             Similar Version 6.2 Macro   8           SPI$MAP_BUFFER                  SPI$BUFFER_MAP  :           SPI$UNMAP_BUFFER                SPI$BUFFER_UNMAP  :           SPI$SEND_COMMAND                SPI$SEND_COMMAND  A           SPI$SET_CONNECTION_CHAR         SPI$CONNECTION_CHAR_SETp  A           SPI$GET_CONNECTION_CHAR         SPI$CONNECTION_CHAR_GET0  <           SPI$RESET                       SPI$RESET_SCSI_BUS  ;           SPI$ABORT_COMMAND               SPI$ABORT_COMMAND   8           SPI$DISCONNECT                  SPI$DISCONNECT  >           SPI$ALLOCATE_COMMAND_BUFFER     SPI$CMD_BUFFER_ALLOC  @           SPI$DEALLOCATE_COMMAND_BUFFER   SPI$CMD_BUFFER_DEALLOC  +           SPI$RESERVED1                   -A  +           SPI$RESERVED2                   -   5           SPI$CONNECT                     SPI$CONNECT   :           SPI$FREEZE_QUEUE                SPI$QUEUE_FREEZE  =           SPI$TQE_WAIT                    Use EXE$KP_TQE_WAIT   ;           SPI$RELEASE_QUEUE               SPI$QUEUE_RELEASEr  9           SPI$FLUSH_QUEUE                 SPI$QUEUE_FLUSH   :           -                               SPI$RESET_DEVICE       4-42           I                                                 Programming Release NotestI                              4.11 Device Support on OpenVMS Alpha Systems     B               4.11.1.5.2 OpenVMS Alpha SCSI Tagged Command Queuing  H         V6.2  For OpenVMS Alpha Version 6.2, the OpenVMS Alpha SCSI portE               device driver interface has been changed to support the H               tagged command queuing architecture of the SCSI-2 standard=               as described in specification ANSI X3.131-1994.t  I               4.11.1.5.3 Enhanced SCSI Interface to IO$_DIAGNOSE Functiona  B         V6.2  The $QIO IO$_DIAGNOSE function has been enhanced forC               the following SCSI class drivers: GKDRIVER, DKDRIVER,DE               and MKDRIVER. The function now allows for the return ofsG               autosense data into a user-specified buffer. In addition,tE               a new data structure, called the S2DGB (SCSI-2 DiagnosedG               Buffer), has been placed in STARLET to facilitate the useo+               of the IO$_DIAGNOSE function.n  B               The new $QIO IO$_DIAGNOSE parameters are as follows:                 Parameter Use   *               P1        S2DGB base address  $               P2        S2DGB length  0               P3        Reserved, should be zero  0               P4        Reserved, should be zero  0               P5        Reserved, should be zero  0               P6        Reserved, should be zero  A               Example 4-1 shows the only S2DGB format that can bee               accepted.l  F               Note that this structure is upwardly compatible with theC               existing structure used by the IO$_DIAGNOSE function.E  C               The correct length of the structure is defined by theME               constant S2DGB$K_XCDB32_LENGTH (value: 60-decimal). The G               addresses in this structure are 32-bit virtual addresses.r9               The fields in the structure are as follows:                  S2DGB$L_OPCODE  E               This field should contain S2DGB$K_OP_XCDB32 (value: 1).V  I                                                                      4-43, S              Programming Release Notesf0     4.11 Device Support on OpenVMS Alpha Systems    <           Example 4-1 OpenVMS SCSI-2 Diagnose Buffer (S2DGB)  B                +-------------------------------------------------+F                |              S2DGB$L_OPCODE                     | :00B                +-------------------------------------------------+F                |              S2DGB$L_FLAGS                      | :04B                +-------------------------------------------------+F                |              S2DGB$L_32CDBADDR                  | :08B                +-------------------------------------------------+F                |              S2DGB$L_32CDBLEN                   | :0CB                +-------------------------------------------------+F                |              S2DGB$L_32DATADDR                  | :10B                +-------------------------------------------------+F                |              S2DGB$L_32DATLEN                   | :14B                +-------------------------------------------------+F                |              S2DGB$L_32PADCNT                   | :18B                +-------------------------------------------------+F                |              S2DGB$L_32PHSTMO                   | :1CB                +-------------------------------------------------+F                |              S2DGB$L_32DSCTMO                   | :20B                +-------------------------------------------------+F                |              S2DGB$L_32SENSEADDR                | :24B                +-------------------------------------------------+F                |              S2DGB$L_32SENSELEN                 | :28B                +-------------------------------------------------+F                |                                                 | :2CB                +--                                             --+F                |              Reserved                           | :30B                +--                                             --+F                |              Should Be Zero                     | :34B                +--                                             --+F                |                                                 | :38B                +-------------------------------------------------+             S2DGB$L_FLAGS   ?           This field should contain the bit fields shown in thenC           following table. Note that these bit definitions start athD           bit 0 and omit no bits. This is required for compatibility3           with the existing IO$_DIAGNOSE interface.2               4-44 u  b      I                                                 Programming Release Notes I                              4.11 Device Support on OpenVMS Alpha Systems     A               S2DGB$V_READ            This bit should be 1 if theeD                                       operation being performed is aH                                       read. If the operation is a write,;                                       this bit should be 0.   A               S2DGB$V_DISCPRIV        This bit should contain the F                                       DiscPriv bit value to be used inI                                       the IDENTIFY message sent with thislI                                       operation. If S2DGB$V_TAGGED_REQ islI                                       1, then this bit should be ignored. G                                       Note that this bit may be ignored 4                                       by some ports.  I               S2DGB$V_SYNCHRONOUS     This bit is ignored since its value G                                       is beyond the control of the userl8                                       in SCSI-2 drivers.  C               S2DGB$V_OBSOLETE1       This bit is ignored. Formerly E                                       it represented the disabling ofhC                                       command retries, which is nowbD                                       beyond the control of the user8                                       in SCSI-2 drivers.  G               S2DGB$V_TAGGED_REQ      When this bit is 1, the operationvG                                       will be processed as using tagged E                                       command queuing and S2DGB$V_TAG D                                       should define the tag value toF                                       be used. When this bit is 0, theI                                       operation will be processed without H                                       benefit of tagged command queuing.F                                       Ports that do not support taggedI                                       command queuing always behave as if I                                       this bit is 0. Note that some portslG                                       simulate untagged operation using F                                       appropriately tagged operations.                    I                                                                      4-45t s              Programming Release Notes30     4.11 Device Support on OpenVMS Alpha Systems      B           S2DGB$V_TAG             If S2DGB$V_TAGGED_REQ is 1, thenA                                   this 3-bit field should containaE                                   one of the following coded constantt)                                   values:.  B                                      S2DGB$K_SIMPLE indicates thatC                                      the command is to be sent withn:                                      the SIMPLE queue tag.C                                      S2DGB$K_ORDERED indicates that C                                      the command is to be sent witht;                                      the ORDERED queue tag.fC                                      S2DGB$K_EXPRESS indicates thateC                                      the command is to be sent withbA                                      the HEAD OF QUEUE queue tag. @                                      If S2DGB$V_TAGGED_REQ is 0,@                                      then this field is ignored.>                                      Ports that do not supportB                                      tagged command queuing alwaysE                                      ignore the S2DGB$V_TAG field andDB                                      send all commands as untaggedD                                      operations. Note that automaticE                                      contingent allegiance processing B                                      is not accessible through the;                                      IO$_DIAGNOSE function.i                                             4-46           I                                                 Programming Release Notes.I                              4.11 Device Support on OpenVMS Alpha Systems3      B               S2DGB$V_AUTOSENSE       When this bit is 1, S2DGB$L_H                                       32SENSEADDR and S2DGB$L_32SENSELENI                                       should contain a valid sense buffer D                                       address and length. If a CHECKE                                       CONDITION or COMMAND TERMINATEDOG                                       status is returned, REQUEST SENSE I                                       data will be returned in the buffer D                                       defined by S2DGB$L_32SENSEADDRG                                       and S2DGB$L_32SENSELEN. When thissG                                       bit is 0, the buffer described bysF                                       S2DGB$L_32SENSEADDR and S2DGB$L_E                                       32SENSELEN is ignored and sense C                                       data will be returned only ifTE                                       the CDB defines a REQUEST SENSEs.                                       command.  I                                       When S2DGB$V_AUTOSENSE is zero, thelF                                       class driver saves the autosenseH                                       data in pool and returns it to theE                                       next IO$_DIAGNOSE, if that IO$_ G                                       DIAGNOSE has a REQUEST SENSE CDB.a  E                                       All other bits in S2DGB$L_FLAGSm5                                       should be zero.                  S2DGB$L_32CDBADDRe  I               This field should contain the 32-bit virtual address of theFG               SCSI Command Data Block (CDB) to be sent to the target byn*               this IO$_DIAGNOSE operation.                 S2DGB$L_32CDBLEN  B               This field should contain the number of bytes in theD               SCSI Command Data Block (CDB) to be sent to the targetF               by this IO$_DIAGNOSE operation. (Legal values: 2 to 248.G               However, some ports may restrict CDBs to smaller lengths. +               Recommended values: 2 to 16.)n                 S2DGB$L_32DATADDRp  E               This field should contain the 32-bit virtual address oftD               the DATAIN or DATAOUT buffer to be used with this SCSII               operation. If the CDB being sent to the target does not usetI               a DATAIN or DATAOUT buffer, then this field should be zero.G  I                                                                      4-47  n  m           Programming Release Notes 0     4.11 Device Support on OpenVMS Alpha Systems               S2DGB$L_32DATLEN  E           This field should contain the number of bytes in the DATAIN B           or DATAOUT buffer associated with this operation. If the?           CDB being sent to the target does not use a DATAIN or @           DATAOUT buffer, then this field should be zero. (Legal>           values: 0 to UCB$L_MAXBCNT. Recommended values: 0 toC           65,536. All ports are required to support at least 65,536D           byte data transfers.)              S2DGB$L_32PADCNT  C           This field should contain the number of padding DATAIN oreB           DATAOUT bytes required by this operation. (Legal values:B           0 to the maximum number of bytes in a disk block on this<           system minus one. Current legal values: 0 to 511.)             S2DGB$L_32PHSTMO  B           This field should contain the number of seconds that theA           port driver should wait for a phase transition to occurv?           or for delivery of an expected interrupt. If S2DGB$V_E?           TAGGED_REQ is 1 or this field contains a 0 or 1, thentB           the current phase transition timeout setting will not be8           changed. (Legal values: 0 to 300 {5 minutes}.)             S2DGB$L_32DSCTMO  B           This field should contain the number of seconds that the@           port driver should wait for a disconnected transaction@           to reconnect. If S2DGB$V_TAGGED_REQ is 1 or this field@           contains a 0 or 1, then the current disconnect timeoutA           setting will not be changed. (Legal values: 0 to 65,535            {about 18 hours}.)             S2DGB$L_32SENSEADDR   C           If S2DGB$V_AUTOSENSE is 1, then this field should contain C           the 32-bit virtual address of the sense buffer to be usedLA           by this SCSI operation. If S2DGB$V_AUTOSENSE is 0, thisl            field will be ignored.             S2DGB$L_32SENSELEN  C           If S2DGB$V_AUTOSENSE is 1, then this field should contain A           the number of bytes in the sense buffer associated with @           this operation. (Legal values: 0 to 255. Note: a valueC           of 0 instructs the class driver to discard any sense data1B           received. Recommended value: 18. Some ports may restrictC           the number of sense bytes to 18.) If S2DGB$V_AUTOSENSE isl(           0, this field will be ignored.       4-48           I                                                 Programming Release NoteshI                              4.11 Device Support on OpenVMS Alpha Systemsa    G               If all parameters are valid, the class driver will invoke H               the necessary port functions to send the CDB, transfer theH               data, and return, save or discard sense data as defined byI               the input S2DGB. Upon completion, the return IOSB will haves#               the following format:t  K                +----------------------------+-----------------------------+ O                |      byte count <15:0>     |       port VMS status       | :00nK                +-------------+--------------+-----------------------------+iO                | SCSI status |     zero     |      byte count <31:16>     | :04 K                +-------------+--------------+-----------------------------+T  G               The DKDRIVER, GKDRIVER, and MKDRIVER class drivers, whichMH               implement other QIO functions, might intermix other taggedE               requests with IO$_DIAGNOSE requests. The order in which B               requests are sent generally match the order in whichH               requests are presented to the driver. An exception to thisD               ordering occurs when the driver receives REQUEST SENSED               for which autosense data previously has been recoveredF               and stored. In this case, the IO$_DIAGNOSE will completeD               immediately and no command will be sent to the target.  G               The DKDRIVER, GKDRIVER, and MKDRIVER class drivers permitUH               only one IO$_DIAGNOSE operation to be active (in the startI               I/O routine) at given time, except as described in the nextVF               paragraph. However, applications must single thread IO$_H               DIAGNOSE requests in order to properly detect the presenceH               of sense data and send the required REQUEST SENSE command.H               This is consistent with the VAX IO$_DIAGNOSE behavior. ForH               example, if three reads are issued with no waiting and theG               first read gets a CHECK CONDITION, the sense data will be C               discarded by the target when the second read arrives.   F               The DKDRIVER, GKDRIVER, and MKDRIVER drivers permit moreH               than one IO$_DIAGNOSE operation to be active (in the startC               I/O routine) only when all active operations have the F               S2DGB$V_AUTOSENSE flag equal to 1. Upon encountering theG               first IO$_DIAGNOSE with S2DGB$V_AUTOSENSE equal to 0, the G               class driver will apply the restrictions described in the !               previous paragraph.e          I                                                                      4-49n c  f           Programming Release Notesc0     4.11 Device Support on OpenVMS Alpha Systems    9           4.11.1.5.4 GKDRIVER Command Queuing Enhancement   ?     V6.2  The GKDRIVER device driver supports the additional IO @           function code IO$_SETCHAR, which allows an applicationB           to request that a connection be characterized as tagged-E           command-queuing capable. By default, GKDRIVER characterizes $           connections as nonqueuing.  B           To implement the IO$_SETCHAR function, do the following:  D           1. Call IO$_SETCHAR with the P1 parameter equal to zero or              one.   >           2. If the caller passes a P1 value of zero, then theD              connection characteristics will be set so as to disable              queuing behavior.  =           3. If the caller passes a value of one and the portr@              supports tagged command queuing, then SPI$V_CC_CMDQD              will be set to one to indicate queuing. Also, SPI$V_CC_D              SCSI_2 (indicating SCSI-2 characteristics) is set. NoteE              that callers are responsible for requesting queuing onlysA              to those devices that have hardware queuing support.   B           4. If the caller passes a value of one and the port doesE              not support queuing, then the connection characteristics$E              shall continue to reflect nonqueuing characteristics andvE              success shall be returned, thereby allowing the caller's A              application to run transparently on both queuing and "              nonqueuing platforms.  C              ________________________ Note ________________________G  <              If the connection is characterized as a queuingC              connection, then disconnect status may not be changed, ?              and disconnects will be enabled by default. If the-A              connection does not support queuing, then connection A              characteristics may be modified (using IO$_DIAGNOSE)-B              to either enable or disable disconnects as the caller#              requests in the S2DGB.+  C              ______________________________________________________            4-50 2  L      I                                                 Programming Release Notes-I                              4.11 Device Support on OpenVMS Alpha Systems     6         4.11.2 Problems and Restrictions (Version 6.2)  D               This section describes known problems and restrictionsB               related to OpenVMS Alpha Version 6.2 device support.  C         4.11.2.1 Hardware Support for Multiple-Host SCSI VMScluster                   Systems  E         V6.2  This note describes supported hardware requirements for H               multiple-host SCSI VMScluster systems, and it explains howE               to determine if your hardware and firmware meet minimum #               version requirements.   G               4.11.2.1.1 Supported Hardware for SCSI VMScluster Systems-  H         V6.2  Table 4-4 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 4-4 or a subsequent version).   F               Table 4-4 Supported Hardware for SCSI VMScluster Systems  5                                               Minimum 5                                               Version G                                               or H/W        How to FinduH               Component    Supported Item     Revision      Your Version  C               Hosts       AlphaServer 400     See           Console H                           4/xxx               footnote[1]   SHOW VERSIONC                                                             commands  1                           AlphaServer 1000    See 9                           4/xxx               footnote[1]a  1                           AlphaServer 2000    Seeu9                           4/xxx               footnote[1]G  1                           AlphaServer 2100    See 9                           4/xxx               footnote[1]e?               [1]The minimum revision ofthis component for SCSI F               VMScluster configurations is the version included in theD               Version 3.2 Firmware Kit, on the May, 1995 CD-ROM. TheE               revision number is listed in the Firmware Release Notest:               Overview that accompanies that Firmware Kit.  I                                                  (continued on next page)s  I                                                                      4-51t e  e           Programming Release Notes 0     4.11 Device Support on OpenVMS Alpha Systems    J           Table 4-4 (Cont.) Supported Hardware for SCSI VMScluster Systems  1                                           Minimume1                                           VersionoC                                           or H/W        How to Find D           Component   Supported Item      Revision      Your Version  -                       AlphaStation 200    See 5                       4/xxx               footnote[1]   -                       AlphaStation 250    See.5                       4/xxx               footnote[1]g  -                       AlphaStation 400    See 5                       4/xxx               footnote[1]   ?           Disks       RZ26                N/A[2]        Console C                                                         SHOW DEVICE ?                                                         command$  .                       RZ26L               442D  .                       RZ28                442D  .                       RZ28B               0006  .                       RZ29B               0006  ?           Controller  HSZ40               2.5           ConsoleoC                                                         SHOW DEVICEt?                                                         commands  <           [1]The minimum revision of this component for SCSIB           VMScluster configurations is the version included in the@           Version 3.2 Firmware Kit, on the May, 1995 CD-ROM. TheA           revision number is listed in the Firmware Release Notes 6           Overview that accompanies that Firmware Kit.  :           [2]The version information for this component is@           incorrectly listed in Table 7-2 in the OpenVMS Version>           6.2 New Features Manual as 392A. There is no version)           requirement for this component.   E                                              (continued on next page)V       4-52 s         I                                                 Programming Release Notes I                              4.11 Device Support on OpenVMS Alpha Systems     F               Table 4-4 (Cont.) Supported Hardware for SCSI VMScluster'                                 Systems   5                                               Minimum 5                                               VersionwG                                               or H/W        How to Find H               Component   Supported Item      Revision      Your Version  C               Bus         DWZZA-AA            E01           Examine C               Isolators                                     product C                                                             sticker   1                           DWZZA-VA            F01   1               Adapters[3] Integral system     N/Ae!                           adapter '                           KZPAA (PCI to                            SCSI)t  D               [3]You can configure other types of SCSI adapters in a=               system for single-host access to local storage.     D               4.11.2.1.2 Minimum SCSI Firmware Requirements for SCSI               VMSclusters   I         V6.2  If your system contains RZ26L or RZ28 disks, their firmware G               revision level must be at or above 442D for use in a SCSI                VMScluster.   F                 ___________________ Important Note ___________________  E                 Only certain RZ26L and RZ28 firmware revisions can beiF                 safely upgraded to firmware revision level 442D. ReferE                 to Section 4.11.2.1.3, to determine if your disks are.D                 capable of being upgraded to firmware revision levelD                 442D. If your disk is capable of supporting firmwareD                 revision level 442D, use the RZTOOLS Utility that isD                 described in Section 4.11.2.1.4 to update the disk's                 firmware.   F                 ______________________________________________________    I                                                                      4-53                 Programming Release NotesS0     4.11 Device Support on OpenVMS Alpha Systems    >           4.11.2.1.3 Firmware Revision Level 442D Requirements  E     V6.2  Only the following combinations of disk drives and firmware >           revision levels are capable of being upgraded safely@           to firmware revision level 442D. Performing the updateC           procedure on any other combination can permanently damage            the disk.   E           Table_4-5_Revision_Level_442D_Firmware_Compatibility_______a             DiskE           Drive_____Firmware_Revision___Disk_Filename________________U  :           RZ26L     440C                RZ26L_442D_DEC.FUP  E           RZ28______441C_or_D41C________RZ28_442D_DEC2104.FUP________l  9           4.11.2.1.4 442D Firmware Installation Proceduree  A     V6.2  If you determine that your disk requires revision leveltD           442D firmware, and it is capable of being upgraded safely,B           use the following procedure to update the firmware. (SeeD           Table 4-5 for the filename of the disk you are upgrading.)  H           $ MCR SYS$ETC:RZTOOLS_ALPHA DKB500 /LOAD=SYS$ETC:disk filename!             Read in 262144 bytes.D&             Current FW version - X440C%             Upgrading to       - DEC0               Loading code  ......0             New code has been sent to the drive.  D           4.11.2.1.5 Documentation Correction for Supported Hardware%           for SCSI VMScluster Systemst  ?     V6.2  The version information for RZ26 disks is incorrectlycE           listed in Table 7-2 in the OpenVMS Version 6.2 New Featurese?           Manual as 392A. The information in Section 4.11.2.1.1t:           supersedes this information. There is no version)           requirement for this component.   2     4.11.2.2 Unsupported Ethernet ISA Bus Adapters  ?     V6.2  OpenVMS Alpha Version 6.2 does not support the DE203, E           DE204, and DE205 Digital Ethernet ISA bus adapters. SupporthA           for these devices will be available in the next releaseND           of the operating system. A driver update kit that supportsB           these devices can be obtained by contacting your Digital!           support representative.e       4-54 v         I                                                 Programming Release NotessI                              4.11 Device Support on OpenVMS Alpha SystemsO    ,         4.11.2.3 SCSI Port and Class Drivers  F         V6.2  The following sections describe OpenVMS Alpha SCSI class2               and port device driver restrictions.  8               4.11.2.3.1 Mounting Third-Party SCSI Disks  D         V6.2  Users of the Digital RZ25M, Imperial MegaRAM MG-SCSI2,I               Seagate ST31200N, and ST31250N disks as well as other disks D               not qualified by Digital may see errors logged againstH               these disks when they are mounted for the first time afterI               booting in OpenVMS Alpha V6.2. Although these disks mountedmF               error-free in OpenVMS Alpha Version 6.1, users might seeF               1 to 11 errors in OpenVMS Alpha Version 6.2 on the first               mount.  E               The errors logged against these disks do not indicate a C               real problem. They occur because a 10-byte mode sensetF               command is now issued to a disk instead of a 6-byte modeD               sense. This approach will allow OpenVMS to work with aG               wider variety of third-party and other previously untrieds               disks.  A               Digital is working with the parties responsible fornH               maintaining the disk's firmware to correct this condition.  I               4.11.2.3.2 Fatal Drive Errors for TZ86, TZ87, and TZ88 SCSI                Tape Drivesb  F         V6.2  When initializing a TZ86, TZ87, or TZ88 SCSI tape drive,H               a fatal drive error may occur. If the fatal drive error isG               accompanied by an error log entry of type "Extended SenseeE               Data Received" and its associated sense data is labeledTI               "Recovered Error, Error Log Overflow," contact your Digital21               support representative for a patch.e  -               4.11.2.3.3 Add-On SCSI Adaptersr  F         V6.2  OpenVMS Alpha 6.2 supports various add-on SCSI adapters.C               Digital's AlphaGeneration platforms typically supportcA               one or more integral SCSI adapters, with the optionnC               of installing additional add-on SCSI adapters. Due to G               differences in device-naming conventions used between thegH               Alpha console and OpenVMS, the OpenVMS device name may not6               match the name displayed by the console.  I                                                                      4-55a p  m           Programming Release Notesl0     4.11 Device Support on OpenVMS Alpha Systems    @           For example, the console designation for a SCSI deviceC           on the integral SCSI adapter may be DKA100. However, whenU@           two additional add-on SCSI adapters are added, the "A"D           designation becomes "C"; and DKA100 appears as DKC100 when           OpenVMS is running.   A           Note that although the console and OpenVMS device names E           may be different, the unique specification of a device name-E           from the console to the device name under OpenVMS will staynC           consistent, as long as add-on SCSI adapters are not added-           or removed.-  A           4.11.2.3.4 HSZ40 and Transportable SCSI Disk Shadow-Sete           Members   @     V6.2  An HSZ40 Raid-Array Controller provides the capability@           of an OpenVMS initialized SCSI disk (that is, one with@           a Files-11 ODS-2 format on it), to be moved between anB           OpenVMS controlled SCSI bus and an HSZ40 controlled SCSIE           bus, without reinitializing the disk and losing data. DisksEB           that contain this functionality are called transportable           disks.  D           A SCSI disk initialized by the HSZ40 and then subsequentlyC           initialized by OpenVMS is called a nontransportable disk, ?           and cannot be moved to an OpenVMS controlled SCSI busi           without losing data.  E           OpenVMS Volume Shadowing requires that a SCSI disk supportsaE           the SCSI commands READ_LONG/WRITE_LONG. These SCSI commands.B           in conjunction with OpenVMS Volume Shadowing are used to?           handle certain classes of errors as seen under normal B           volume shadowing operations. SCSI disks that support the?           READ_LONG/WRITE_LONG capability while connected to anrD           OpenVMS controlled SCSI bus, lose this capability when theE           transportable disks are moved to the SCSI bus controlled byi           an HSZ40.   D           The lack of READ_LONG/WRITE_LONG capability is detected at8           shadow-set MOUNT time, by the following error:  F           MOUN$_DEVNOFE, device does not support FORCED ERROR handling  >           To correct this problem, specify the MOUNT qualifier=           /OVERRIDE=NO_FORCED_ERROR at shadow-set MOUNT time.n       4-56           I                                                 Programming Release NoteslI                              4.11 Device Support on OpenVMS Alpha Systemsv    I               Note that specifying this MOUNT qualifier may cause shadow- F               set member SCSI disks to be removed from a shadow set ifF               certain error conditions arise that cannot be corrected.  G               Digital recommends that HSZ40 nontransportable SCSI disksvF               be used to contain shadow-set members that support READ_H               LONG/WRITE_LONG functionality, and offer benefits providedA               by the level of RAID chosen at initialization time.G  2               4.11.2.3.5 KZTSA Adapter Restriction  G         V6.2  When using wide SCSI devices, a hardware restriction with:F               the KZTSA TURBOchannel to the SCSI adapter is present in4               certain revisions of the KZTSA option.  C               When installing a KZTSA option, you must follow thesec               guidelines:b  E               1. Version A10_1 or later of the KZTSA firmware must be                   used.  F               2. If the KZTSA option revision is "J" or less, then theE                  WIDE parameter must be disabled for each wide device 3                  using the KZTSA DEVPARAMS utility.s  I               3. If the KZTSA option revision is "K" or greater, then thelF                  WIDE parameter may be kept enabled (default) for each                  device.  A                  For instructions about using the KZTSA DEVPARAMSq9                  utility, refer to the KZTSA Users Guide.s  F                 ________________________ Note ________________________  B                 These guidelines pertain only to wide SCSI devices>                 used on the KZTSA. Narrow SCSI devices are notE                 affected. Narrow SCSI devices may have all parameters_"                 enabled (default).  F                 ______________________________________________________                     I                                                                      4-57  a  .           Programming Release Notess0     4.11 Device Support on OpenVMS Alpha Systems  ,     4.11.2.3.6 KZPSA SCSI Adapter Bus Resets  @     V6.2  On PCI-based AlphaServer systems with heavy I/O rates,B           KZPSA SCSI adapters may occasionally reset the SCSI bus.@           These bus reset events, which may appear in the systemE           error log, indicate that a recoverable SCSI bus failure hasmC           occurred. They do not require field service notification.o  E           The following display shows partial DIAGNOSE example outpute5           containing bus reset error log information.n  I                   VMS SCSI Error Type  5. Extended Sense Data from Device2#                                   .H#                                   .I;                   SCSI Status          x02  Check Conditionn#                                   .i#                                   .hK                                        Power On, Reset, or Bus Device Reseti/                                        Occurred   B           Digital expects to fix this problem in a future release.  D           4.11.2.3.7 SCSI Disk I/O Performance Degradation for KZMSA(           XMI and Adaptec 1742A Adapters  @     V6.2  As a result of the SCSI-2 Tagged Command Queuing (TCQ);           support in OpenVMS Alpha Version 6.2, Digital hasi>           determined that customers with KZMSA XMI to SCSI andE           Adaptec 1742A adapters might experience a 20% SCSI disk I/O D           performance degradation because TCQ is not implemented forD           these adapters. The performance degradation is in the areaB           of increased CPU cost per I/O. Customers running at lessB           than maximum CPU utilization under OpenVMS Alpha Version@           6.1 might not experience any degradation under OpenVMS           Alpha Version 6.2.  A           Digital does not expect this situation to significantly C           affect DEC 7000 customers planning to upgrade to DEC 8000 B           Family systems using KZMSA adapters because the speed ofE           those processors should offset the performance degradation.tB           However, DEC 7000 customers who upgrade to OpenVMS AlphaC           Version 6.2 will experience the SCSI I/O disk performance            degradation.  =           Digital expects that this will significantly affectt@           existing DEC 2000 Model 300 systems customers that use)           the Adaptec 1742A SCSI adapter.a       4-58 r  n      I                                                 Programming Release Notes.I                              4.11 Device Support on OpenVMS Alpha Systemst    5         4.11.3 Changes and Enhancements (Version 6.1).  E               This section describes OpenVMS Alpha Version 6.1 deviceaB               support changes or enhancements, which also apply to               Version 6.2.  ,         4.11.3.1 New Device Driver Interface  E         V6.1  Starting with Version 6.1, OpenVMS Alpha supports user-rF               written device drivers and a new device driver interfaceF               known as the Step 2 driver interface, which replaces theI               temporary Step 1 driver interface provided in OpenVMS Alpha H               Versions 1.0 and 1.5. The Step 2 driver interface providesF               support for writing device drivers in C or another high-F               level language and that can conform to the OpenVMS AlphaH               calling standard. An example device driver written in C is5               provided in the SYS$EXAMPLES directory.   F               The following Alpha device support manuals are available,               for OpenVMS Alpha Version 6.1:  I               o  Creating an OpenVMS AXP Step 2 Device Driver from a Step                    1 Device Driver  F                  This manual describes how to convert an OpenVMS AlphaB                  Step 1 device driver, written in VAX MACRO, to anD                  OpenVMS Alpha Step 2 device driver, also written in                  VAX MACRO.   E               o  Creating an OpenVMS AXP Step 2 Device Driver from an *                  OpenVMS VAX Device Driver  D                  This manual describes how to convert an OpenVMS VAXI                  device driver, written in VAX MACRO, to an OpenVMS AlphaaA                  Step 2 device driver, also written in VAX MACRO.e  >               o  OpenVMS AXP Device Support: Developer's Guide  D                  This manual describes how to write an OpenVMS Alpha8                  device driver in a high-level language.  6               o  OpenVMS AXP Device Support: Reference  E                  This manual provides reference material for creating2H                  OpenVMS Alpha device drivers, and describes the macros,E                  system routines, and entry points used in converting G                  OpenVMS VAX and Step 1 OpenVMS Alpha device drivers tog5                  Step 2 OpenVMS Alpha device drivers.1  I                                                                      4-59. u  r           Programming Release Notes 0     4.11 Device Support on OpenVMS Alpha Systems    (     4.11.3.2 Step 1 Drivers Are Obsolete  B     V6.1  OpenVMS Alpha Version 6.1 does not support Step 1 driverB           interfaces, and source changes are required to convert aD           Step 1 driver to a Step 2 driver. For detailed informationB           about how to convert a Step 1 driver to a Step 2 driver,?           see Creating an OpenVMS AXP Step 2 Device Driver fromc@           a Step 1 Device Driver and OpenVMS AXP Device Support:           Reference.  B           If you attempt to load a Step 1 driver that was compiledA           and linked on any previous version of the OpenVMS Alpha B           operating system, the System Management utility (SYSMAN)B           will issue the following warning message, and the driver           will not be loaded:n  N       $ mcr sysman io connect mya0/noadapter/driver=$users:[jones]mydriver_v157       %SYSMAN-I-NODERR, error returned from node BEAMME A       -SYSTEM-W-SYSVERDIF, system version mismatch; please relinkr  E           If you attempt to relink a Step 1 driver object module thataC           was compiled on any previous version of the OpenVMS Alpha_B           operating system, the linker will issue warning messagesD           about undefined symbols for any references to the obsoleteB           Step 1 support routines. The resultant image file is not           loadable.   A           If you attempt to recompile a Step 1 driver module, theeD           MACRO-32 Compiler will issue many compilation warnings and3           errors, including the following messages:n  N    %AMAC-E-GENERROR, (1) generated ERROR: 0 DPTAB must declare driver STEP=2 ;  M    %AMAC-E-GENERROR, (1) generated ERROR: 0 FUNCTAB is an obsolete macro used_    by STEP=1 drivers;_  ,           No object module will be produced.  /     4.11.3.3 OpenVMS Alpha System-Code Debugger   >     V6.1  OpenVMS Alpha Version 6.1 supports a new programming@           tool that can be used to debug nonpageable system code<           and device drivers running at any IPL. The OpenVMS=           Alpha System-Code Debugger lets you use the OpenVMS B           Debugger interface to observe and manipulate system code'           interactively as it executes.h       4-60           I                                                 Programming Release Notes I                              4.11 Device Support on OpenVMS Alpha Systems     C               For more information about how to use the system-code_G               debugger, see the OpenVMS AXP Device Support: Developer'sPD               Guide. Before using the system-code debugger, note theE               problems and limitations described in Section 4.11.4.2.   6         4.11.4 Problems and Restrictions (Version 6.1)  D               This section describes known problems and restrictionsC               related to OpenVMS Alpha Version 6.1 and later deviceS               support.  E         4.11.4.1 C Structure Member Names: Passing to Nested C MacrosT  B         V6.1  The file SYS$LIBRARY:SYS$LIB_C.TLB is a library of CF               header files that define structures corresponding to theE               structures defined for MACRO-32 in SYS$LIBRARY:LIB.MLB. G               These C structure definitions also include simple macros,nD               which allow the use of the same field names in driversG               written in C as those used in drivers written in MACRO-32                and BLISS.  C               A compile-time error results if both of the following                occur:  I               o  You pass one of these simple macro names for a structure ;                  member as part of a parameter to a C macros  B               o  This macro passes this parameter to another macro  F               You can avoid this problem by using one of the following               methods:  D               o  "Flattening" the macro definition (by expanding the                  nested macros)s  F               o  Using C inline functions to replace the nested macros9                  while maintaining the desired modularityn  F               o  Introducing additional temporary storage in the outerG                  macro to avoid passing the input arguments directly toe"                  the nested macros        I                                                                      4-61  t  s           Programming Release Notes 0     4.11 Device Support on OpenVMS Alpha Systems    /     4.11.4.2 OpenVMS Alpha System-Code DebuggerD  B     V6.1  The OpenVMS Alpha System-Code Debugger has the following#           problems and limitations:N  ;           o  The CALL command is not currently implemented.   @           o  If you use the SET WATCH command, it uses nonstaticB              watchpoints. Because nonstatic watchpoints are slowerC              than static watchpoints, their use is not recommended.   @           o  With the OpenVMS Debugger, if you use the SET BREAKD              /EXCEPTION command, when the program hits an exception,E              the user could fix the problem and continue the program. C              With the system-code debugger, the SET BREAK/EXCEPTIONu=              command catches the problem later (just before ao@              bugcheck). Therefore, it is not possible to fix theD              problem and proceed. The GO command will let the system/              bugcheck and write the crash dump.   :           o  Setting breakpoints at IF statements in the CD              programming language does not always work. For example,>              if you have code like the following and you set aC              breakpoint at the first line, the system-code debugger @              may or may not hit the breakpoint (depending on the              condition):                if (x).              {                      ....               } elseo              {                        ...              }  D              To avoid this problem, you can set two breakpoints, oneD              in the THEN clause and one in the ELSE clause, or set aD              breakpoint before the IF statement and then single-step.              until you reach the IF statement.  B           o  When using the SET MODULE command on some images with?              the system-code debugger, you may receive an errorr.              message similar to the following:  K              %DEBUG-E-INVPD, procedure descriptor at 00028840 is not valid.        4-62 d  c      I                                                 Programming Release NotestI                              4.11 Device Support on OpenVMS Alpha Systemsh    H                  This procedure descriptor is either in the init sectionG                  for the image or in a paged-out image section. You can G                  determine this by searching for the above value in thedD                  MAP file for the image to which the module belongs.  G                  If the value is not within the init image section or a H                  pageable section, file a Problem Report and provide theF                  error message along with the MAP file for the image.   2         4.12 Device Support on OpenVMS VAX Systems  H               The following sections contain release notes pertaining to)               OpenVMS VAX device support.n  4         4.12.1 Documentation Changes and Corrections  B               This section describes corrections to device support               documentation.  2         4.12.1.1 OpenVMS VAX Device Support Manual  H         V6.1  The following sections describe corrections to the OpenVMS(               VAX Device Support Manual.  0               4.12.1.1.1 Linking a Device Driver  B         V6.1  Chapter 12 of the OpenVMS VAX Device Support Manual,F               Version 6.0, describes how to assemble, link, and load aG               device driver. In Step 3 of the procedure for preparing aaF               driver for loading into the operating system, append theG               following text to the end of the procedure (following theaH               paragraph that begins: "The resulting image must . . . "):  I               To produce an image with a symbol table compatible with theSI               System Dump Analyzer (SDA), you must link again; this time,ED               using the UNIVERSAL=* option statement (to include allG               global symbols and to ensure proper state of the REL bitsoF               in the object records). Relink as shown in the following               example:            I                                                                      4-63  t  l           Programming Release Notesn.     4.12 Device Support on OpenVMS VAX Systems    5           $ LINK /NOEXECUTABLE/NOTRACEBACK/NOSYSSHR - (           _$     /SYMBOLS=MYDRIVER.EXE,-)           _$     /SHARE=DUMMY_FILE_NAME,-M5           _$     /NOMAP,MYDRIVER1.OBJ,MYDRIVER2.OBJ,-E$           _$     SYS.STB/SELECTIVE,-!           _$     SYS$INPUT/OPTIONe           _$     BASE=0t           _$     UNIVERSAL=*  @           For more information about the Linker, see the OpenVMS            Linker Utility Manual.  B           4.12.1.1.2 Device-Register I/O Space: Usage Restrictions  E     V6.1  Chapter 5 of the OpenVMS VAX Device Support Manual, Version E           6.0, describes device driver coding and the restrictions on E           the use of device-register I/O space. The third sentence of E           the fifth bulleted paragraph in Section 5.2 states that the B           instructions that refer to UNIBUS adapter registers mustC           use longword context. This is the wrong bus. The sentenceA           should read:  B              "Instructions that refer to MASSBUS adapter registers,              must use the longword context."  8     4.12.1.2 OpenVMS VAX Device Support Reference Manual  D     V6.1  The following sections describe corrections to the OpenVMS.           VAX Device Support Reference Manual.  ;           4.12.1.2.1 COM$DRVDEALMEM Routine Synchronizationt  ?     V6.1  Chapter 3 of the OpenVMS VAX Device Support Referenceo@           Manual, Version 6.0, contains a section describing the!           COM$DRVDEALMEM routine.T  D           At the end of the paragraph under Synchronization, add the           following sentence:   B           "If called at IPL$_SYNCH or higher, the routine executes           the fork process."  
                  4-64 S  i      I                                                 Programming Release NoteshH                               4.12 Device Support on OpenVMS VAX Systems         %         4.12.1.2.2 CRB Data Structurer  ?         V6.1  Chapter 1, Section 1.7, of the OpenVMS VAX DeviceiF               Support Reference Manual, Version 6.0, contains Table 1-I               8 describing the CRB data structure fields. The descriptionsD               in the table for the CRB$L_INTD field is confusing andI               needs clarification. Replace the first two sentences in the 0               CRB$L_INTD description as follows:  &               Field Name   Description  I               CRB$L_INTD   Portion of the interrupt transfer vector block D                            that stores executable code, driver entryH                            points, and I/O adapter information. This 10-F                            longword area is overlaid with the contentsF                            of the interrupt transfer vector block thatH                            starts at VEC$L_INTD (offset 16) as describedH                            in Section 1.7.1. It contains pointers to the)                            driver's . . .m  8               4.12.1.2.3 SCDRP Data Structure SCSI Flags  C         V6.1  Chapter 1 of the OpenVMS VAX Device Support ReferenceaD               Manual, Version 6.0, contains a section describing the.               SCDRP data structure SCSI flags.  A               In the SCDRP$L_SCSI_FLAGS field description for bit :               SCDRP$V_LOCK, make the following correction:  #                  Change:SCDRP$VLOCK   $                  To:    SCDRP$V_LOCK  *               4.12.1.2.4 SPI$CONNECT Macro  C         V6.1  Chapter 2 of the OpenVMS VAX Device Support Reference D               Manual, Version 6.0, contains a section describing the                SPI$CONNECT macro.  <               In the table listing the required inputs, add:  *                  R4    Address of the SPDT  I               In the values returned in R3, the SPDT$M_CMDQ bit was addedCH               to the port capability mask (SPDT$L_PORT_FLAGS). When set,I               SPDT$M_CMDQ indicates that the port driver supports command7               queuing I/O.  I                                                                      4-65i e  t           Programming Release Notes .     4.12 Device Support on OpenVMS VAX Systems    A           In the return values table listing R3 and the mask bitsh#           (after SPDT$M_LUNS), add:V  6              SPDT$M_CMDQ  Supports command queuing I/O  D           4.12.1.2.5 SPI$GET_CONNECTION_CHAR and SPI$SET_CONNECTION_           CHAR Macross  ?     V6.1  Chapter 2 of the OpenVMS VAX Device Support Referencel?           Manual, Version 6.0, contains sections describing theME           SPI$GET_CONNECTION_CHAR and SPI$SET_CONNECTION_CHAR macros.sB           Appended to the macro characteristics buffer is longword!           #12 for SCSI-2 support.   A           At the end of the characteristics buffer table in these A           macro descriptions, add the longword #12 information asg           follows:  E              12     SCSI-2 device characteristic status bits. Bits of 9                     this longword are defined as follows:   %                     Bit   Description   A                     0     When set, (SCDT$V_SCSI_2) indicates the A                           device connection is SCSI-2 conformant.s  ?                     1     When set, (SCDT$V_CMDQ) indicates therE                           device connection supports command queuing.r  "           4.12.1.2.6 $EQULST Macro  ?     V6.1  Chapter 2 of the OpenVMS VAX Device Support Referencer@           Manual, Version 6.0, contains a section describing the           $EQULST macro.  B           In the parameter description for symbol,value insert the'           phrase in decimal as follows:   A           " . . . and value specifies in decimal the value of ther           symbol." h       4.13 I/O Users  C           The following sections contain release notes pertinent tou           the I/O user.d       4-66 a  h      I                                                 Programming Release Notes H                                                            4.13 I/O User    (         4.13.1 Problems and Restrictions  B               This section describes known problems with I/O write               operations.   C         4.13.1.1 I/O Write Operations Interrupted by System FailureA  I         V6.0  The OpenVMS operating system ensures that when an I/O write H               operation returns a successful completion status, the data5               is available on the disk or tape media.t  E               OpenVMS guarantees atomicity for single-block I/O writenI               operations to DIGITAL Storage Architecture (DSA) drives.[1]SH               However, if a system failure occurs while a multiple blockG               I/O write operation is in progress, the OpenVMS operating H               system does not guarantee the successful completion of theI               I/O write. When a failure interrupts a write operation, the F               data can be left in any one of the following conditions:  F               o  The new data is written completely to the disk blocksG                  on the media, but a completion status was not returnedD$                  before the failure.  G               o  The new data is partially written to the media so that H                  some of the disk blocks involved in the I/O contain theE                  data from the in-progress I/O write and other blocks I                  contain the data that was present prior to the I/O write I                  operation. Note that blocks updated with new data can be >                  interspersed with blocks containing old data.  I               o  The new data was never written to any of the disk blocks                   on the media.  F               Individual blocks can contain either all new data or allE               old data; a block is not partially updated when dealinga               with DSA devices.e  "               ____________________E               [1]   Single block atomicity may not be guaranteed with I                     SCSI devices.  This includes the new HSZ and HSJ SCSItF                     adapters that extend SCSI disk connectivity to theG                     HSC family of devices.  An OpenVMS operating system E                     makes no distinction between the SCSI-adapted DSA 4                     devices and actual SCSI devices.  I                                                                      4-67                 Programming Release Notesy     4.13 I/O User0    C           To guarantee that an I/O write operation either completesoA           successfully, or (in the event of failure) is redone orsD           rolled back as if it were never started, applications mustA           be supplemented by additional techniques to ensure datavE           correctness and recovery. For example, using RMS JournalingkA           for OpenVMS or database or file journaling and recoveryoA           techniques allows applications to automatically recover.            from failures such as:  A           o  Permanent loss of the path between a CPU data buffer1A              containing the data being written and the disk beingo>              written to during a multiple block I/O operation.B              Communication path loss can occur due to node failureC              or a failure of node-to-node communications. Note thatR@              transient failures are automatically recovered fromD              during mount verification without requiring any further!              recovery techniques.6  B           o  Failure of a CPU (such as a system crash, halt, powerB              failure) during a multiple block I/O write operation.  )           o  Mistaken deletion of a file.S  @           o  OpenVMS RMS incomplete bucket write operation to an              indexed file.  @           o  Cancellation of an in-progress multiple block write              operation.   9           Note that Volume Shadowing for OpenVMS promotesrB           availability by providing access to data in the presence@           of media deterioration, communication path failure, orA           controller or device failure. However, volume shadowingeE           should not be mistaken for a journaling product that tracksf.           changes to files for data integrity.  0     4.13.2 Documentation Changes and Corrections  >           This section describes changes to I/O documentation.  0     4.13.2.1 OpenVMS I/O User's Reference Manual  D     V6.1  The following section should appear in the Terminal Driver=           chapter of the OpenVMS I/O User's Reference Manual..       4-68 u  M      I                                                 Programming Release NotesSH                                                            4.13 I/O User    (               Terminal Devices Supported  D               Table 4-6 lists the supported terminal devices for theD               Digital 2100 Server Model A500/600 MP and the DEC 2000               Model 300.  ,         Table 4-6 Supported Terminal Devices  M                                                                 International !                            NumberrE         Terminal           of        Output    Split            Modem G         Interface          Lines   __________  Speed   Bus      Control +                                    Silo DMAa  D         Digital 2100       2       No    No    No      None     Full         Server         Model A500/600MP  D         Digital 2100       4, 8    Yes   No    No      EISA     Full         Server         Model A500         /600MP[1]t  D         DEC 2000 Model     2       No    No    No      None     Full         300r  D         DEC 2000 Model     4, 8    Yes   No    No      EISA     Full         300[1]  F         [1] Optional multiplex serial DIGIboard PC/X[TM] adapter card.F         You can daisy chain up to 4 boards in one system, resulting in         16, 32, or 64 ports.  *         4.14 Librarian Utility (LIBRARIAN)  H               The following sections contain release notes pertaining to0               the Librarian utility (LIBRARIAN).  (         4.14.1 Problems and Restrictions  A               This section describes known LIBRARIAN problems andu               restrictions.     I                                                                      4-69y p  e           Programming Release Notes &     4.14 Librarian Utility (LIBRARIAN)    7     4.14.1.1 PGFLQUOTA Should Exceed 23000 (Alpha Only)w  C     V1.5  The OpenVMS Alpha LIBRARIAN sometimes does not inform you ?           of errors during compression, data reduction, or dataEB           expansion operations. This problem occurs if the account@           or process in which the LIBRARIAN is running has a lowC           PGFLQUOTA process quota. Operation failure is not readily/D           apparent because the $PUTMSG system service always returnsE           a status of SS$_NORMAL, even when the system service fails. A           However, when a failure occurs, the LIBRARIAN returns am$           status other than success.  @           To work around this problem, run the compression, dataC           reduction, or data expansion operation in an account withxD           a PGFLQUOTA process quota greater than 23000. In addition,E           ensure that your command procedures check the return status $           from the LIBRARY command.        4.15 Linker Utility   D           The following sections contain release notes pertaining to4           the OpenVMS Alpha Linker utility (linker).  $     4.15.1 Problems and Restrictions  :           This section describes known linker problems and           restrictions.   9     4.15.1.1 Fixup Information Not Generated (Alpha Only)a  B     V1.0  The linker has been modified so that a new error messageE           informs you at link time that global symbols from shareablesD           images are being placed into byte- or word-sized fields byD           the linker. (Word- and byte-sized stores of global symbolsA           do not generate fixup information. Fixup information isrD           required when linking against shareable images.) When thisB           situation occurs, an error message is printed, and image"           production is inhibited.  =           The following example shows this new error message:r  J     %LINK-E-NOFIXSYM, unable to perform WORD fixup for symbol TPU$_OPTIONSO             in psect $PLIT$ in module TEST_MODULE file USER:[ACCOUNT]TEST.OLB;1s       4-70 e  o      I                                                 Programming Release NotesoI                                                       4.15 Linker Utilityo    F               To work around this restriction, move the symbolic valueG               into the desired location at run time rather than at link G               time. For example, in MACRO, rather than performing .WORDhH               TPU$_OPTIONS, use the instruction MOVW #TPU$_OPTIONS,dest.               H         4.15.1.2 Shareable Image Psects Pointed to by Symbol Definitions                  (Alpha Only)s  A         V1.0  The linker cannot overlay program sections that are C               referenced by symbol definitions with shareable imagelB               program sections of the same name. Symbol definitionC               records that contain the index of an overlaid program F               section are generated by the C compiler when the relaxedI               ref-def extern model is used (the default). Shareable imageaD               program sections are created when you link a shareableC               image and use the PSECT keyword in your SYMBOL_VECTORe               option.o  A               If the linker detects this condition, it issues the                following error:  J         %LINK-E-SHRSYMFND, shareable image psect <name> was pointed to by          a symbol definition 0         %LINK-E-NOIMGFIL, image file not created  I               The link continues, but no image is created. To work aroundtC               this restriction, change the symbol vector keyword totB               DATA, or recompile your C program with the qualifier               /EXTERN=COMMON.            4.15.2 Corrections  ?               This section describes corrections to the linker.   !         4.15.2.1 /DEBUG Qualifier   C         V6.2  Prior to the last release, the linker was modified to H               avoid multiple relocations and fixups to the same locationF               from occurring during the processing of overlaid programF               sections. A problem has since been reported about "lost"D               relocations and fixups to shareable images when linked)               using the /DEBUG qualifier.   I                                                                      4-71U i  M           Programming Release Notes-     4.15 Linker Utility     D           The problem was caused by the linker erroneously canceling;           deferred relocations or fixups to the image whilenE           processing debug records to generate the Debug Symbol Table D           (DST). Since the debug context is a separate address spaceB           from the image proper, a write to a virtual address fromE           the debug space was removing relocations or fixups from ther4           image located at the same virtual address.  *           This problem has been corrected.  0     4.15.3 Documentation Changes and Corrections  E           This section describes corrections to linker documentation.   *     4.15.3.1 OpenVMS Linker Utility Manual  A     V1.5  The OpenVMS Linker Utility Manual incorrectly describes.B           /NONATIVE_ONLY to be the default behavior of the linker.  @           The /NATIVE_ONLY qualifier to the LINK command directsD           the linker not to pass along the procedure signature blockC           (PSB) information, created by the compilers, in the image E           it is creating. This is the default behavior of the linker. :           For more information, refer to Section 4.20.1.1.       4.16 Lock Managere  D           The following sections contain release notes pertaining to           the lock manager.m  #     4.16.1 Changes and Enhancements   ?           This section describes changes or enhancements to the            software.t  *     4.16.1.1 LCKMGR Spin Lock (Alpha Only)  >     V6.1  The synchronization for the OpenVMS lock manager has@           changed with this release of OpenVMS Alpha. A new spin?           lock with a name of LCKMGR is now used to synchronize ?           the OpenVMS lock manager for standalone OpenVMS Alpha A           machines. Alpha systems running as part of a VMScluster D           still synchronize with the SCS (IOLOCK8) spin lock. Use ofD           the LCKMGR spin lock in a VMScluster system will correctly!           lock the SCS spin lock.   C           This change has no impact for users of the system service 6           interfaces of $ENQ[W], $DEQ, and $GETLKI[W].       4-72           I                                                 Programming Release Notes H                                                        4.16 Lock Manager    G               If you have code that currently accesses OpenVMS internaliI               lock manager data structures such as LKBs or RSBs, you williH               need to modify your software to correctly synchronize withI               the lock manager by using the LCKMGR spin lock. This change 4               does not affect OpenVMS VAX software.            4.17 LTDRIVER   H               The following sections contain release notes pertaining to               the LTDRIVER.   (         4.17.1 Problems and Restrictions  @               This section describes known LTDRIVER problems and               restrictions.   F         4.17.1.1 CANCEL SELECTIVE Cannot Cancel IO$_TTY_PORT Functions  H         V6.1  In prior releases, LTDRIVER did not set the "extended DDT"I               bit; therefore, the POSIX function CANCEL SELECTIVE did not H               work with LTDRIVER. This has been fixed, but a restriction               remains.  B               Although this fix allows $QIO reads and writes to beD               selectively canceled, any $QIO done to the port driverF               (that is, with the IO$_TTY_PORT function modifier-like aI               LAT connect $QIO) cannot be canceled with CANCEL SELECTIVE. I               This problem will be addressed in a future OpenVMS release.m  =         4.18 MACRO-32 Compiler for OpenVMS Alpha (Alpha Only)s  F               The following sections contain information pertaining to$               the MACRO-32 Compiler.  (         4.18.1 Problems and Restrictions  I               This section describes problems and restrictions pertainingE9               to the MACRO-32 Compiler for OpenVMS Alpha.e  !         4.18.1.1 .ASCID Directivel  I         V6.2  The length of the argument to a .ASCID directive is limited E               to 996 characters when using the OpenVMS Alpha MACRO-32 C               Compiler. No such restriction exists in the VAX MACRO1               Assembler.  H               This newly discovered difference will remain a restriction               of the compiler.  I                                                                      4-73d c  h           Programming Release Notes 9     4.18 MACRO-32 Compiler for OpenVMS Alpha (Alpha Only)     $     4.18.1.2 .GLOBAL_LABEL Directive  A     V6.2  Labels declared with the .GLOBAL_LABEL directive can be D           used as the newpc argument in calls to the $UNWIND (UnwindE           Call Stack) System Service because it allows the address of !           the label to be stored.   ;           However, there is no provision in the compiler tooB           automatically adjust the stack pointer at such labels to@           remove arguments passed on the stack or compensate forB           stack alignment. If the call stack is unwound back to anB           alternate PC in the calling routine, the stack may stillD           contain arguments and alignment bytes, and any stack-based@           references that expect this adjustment to the caller'sD           original stack depth (which happened automatically on VAX)           will be incorrect.  @           Code that contains labels declared with this directiveA           that are to be used as alternate PC targets for $UNWIND E           must be examined carefully to ensure correct behavior, with B           particular emphasis on any references based on the stack           pointer.  /     4.18.1.3 Floating-Point Return Values in R0p  C     V6.1  A MACRO program that calls out to a routine and expects asB           floating-point return value in R0 may require a "jacket">           between the call and the called routines to move the>           returned value from floating-point register 0 to R0.  >     4.18.1.4 INSV Instructions Negate Granularity Preservation  ?     V6.1  INSV instructions do not generate code that correctlye@           preserves granularity when granularity preservation is           turned on.  !     4.18.1.5 .JSB_ENTRY Directive   @     V6.1  For procedures declared with the .JSB_ENTRY directive,D           the MACRO-32 Compiler automatically generates a null frameD           procedure descriptor, independent of debug or optimizationD           qualifiers. The null frame procedure descriptor allows for8           debugging of problems with the linkage itself.  E           Because no new context is set up by a null frame procedure, C           a side effect is that there is no guarantee of completelyt=           accurate debugger information about such proceduresI@           in response to SHOW CALLS and SHOW STACK commands. ForC           example, the line number in the called null procedure (toe       4-74           I                                                 Programming Release Notes I                     4.18 MACRO-32 Compiler for OpenVMS Alpha (Alpha Only)     H               which a JSB is done) may be reported as the line number inA               the calling procedure from which the JSB is issued.   H         4.18.1.6 Floating-Point and Packed-Decimal Instruction Arguments  D         V1.5  Because packed-decimal instructions and floating-pointD               instructions are implemented by means of macros, thereE               is one restriction on the format of the arguments. In adH               macro invocation, an initial circumflex (^) is interpretedF               to mean that the parameter is a string and the character@               immediately following the circumflex is the stringG               delimiter. Because of this, you cannot use arguments thatlI               begin with an operand type specification, such as ^x20(SP). H               Note that immediate mode arguments, such as #^XFF, can useI               an operand type specification because the circumflex is notp$               the initial character.  2         4.18.1.7 Multiple Object Files Compilation  D         V1.5  The MACRO-32 Compiler does not support the creation ofH               separate object files from multiple source files specifiedH               in one command. It does support the creation of one objectG               file from multiple source files specified in one command.l  4         4.18.2 Documentation Changes and Corrections  G               This section describes changes in the MACRO-32 compiler'sb               documentation.  F         4.18.2.1 Migrating to an OpenVMS AXP System: Porting VAX MACRO                  Code   A               The following sections contain information that waseI               included in the OpenVMS Alpha Version 6.1 Bookreader updateaF               of Migrating to an OpenVMS AXP System: Porting VAX MACROG               Code, but which has not yet been published in the printed $               version of the manual.  1               4.18.2.1.1 Entry Point Declarations,  I         V6.1  Any code label that is a possible target of a CALLS, CALLG, I               JSB, BSBW, or BSBB instruction must be declared as an entrymG               point. In addition, any code label must be declared as an F               entry point using a .JSB_ENTRY or .JSB32_ENTRY directive               if:   G               o  The label can be the target of a global (cross-module)y-                  JMP, BRB, or BRW instruction   I                                                                      4-75t l  o           Programming Release Notesd9     4.18 MACRO-32 Compiler for OpenVMS Alpha (Alpha Only)r    C           o  The label can be the target of an indeterminate branch E              (such as BRB @(R10)), where the address of the label hasdD              been stored in R10, even if the reference and the label'              are within the same modulel  @           o  The address of the label is stored in a register orA              memory location, even if it is never accessed by the               current module   ?           The OpenVMS calling standard for Alpha computers does B           not provide a way to access indeterminate code addresses>           directly. All such accesses are accomplished using aC           procedure descriptor to describe the routine and the code0D           address. When a code label address is stored, the compiler?           does not know if that address will be referenced only A           by the current module, or whether it may be accessed by C           another MACRO module or another module written in anotherO@           language. Whenever the MACRO-32 compiler stores a codeE           address, it always stores the procedure descriptor for that C           address so that other code can access it correctly. For a B           procedure descriptor address to exist, the label must be%           declared as an entry point.   C           Likewise, when a stored address is used as a destination,0B           the compiler does not know where that address came from,E           so it always assumes that the stored address is the address D           of a procedure descriptor and uses that descriptor to pass!           control to the routine.t  6           4.18.2.1.2 BUGx Instruction Is Not Supported  @     V1.5  The BUGx instruction is not supported by the compiler.B           This instruction was inadvertently omitted from the listD           of unsupported instructions in Migrating to an OpenVMS AXP)           System: Porting VAX MACRO Code.m  5           4.18.2.1.3 /FLAGGING=INSTRUCTIONS Qualifiers  D     V1.5  When /FLAGGING=INSTRUCTIONS is enabled, absolute addressesA           detected by the compiler are flagged. For example, MOVLyD           R0, 200 compiles correctly (updating memory location 200),A           but the desired absolute address may be different on anl@           Alpha computer. As a result, the informational message@           CHKABSADR is reported. This does not also apply to the?           instruction MxPR, as stated in the description of thec9           /FLAGGING=INSTRUCTIONS qualifier in Appendix A.R       4-76 h  a      I                                                 Programming Release Notes I                     4.18 MACRO-32 Compiler for OpenVMS Alpha (Alpha Only)     E               If you do not want these information messages reported,e=               specify the /NOFLAGGING=INSTRUCTIONS qualifier.t  H               4.18.2.1.4 TRACEBACK and DEBUG Options Restriction Removed  F         V1.5  The restriction that pertained to the qualifiers /DEBUG,F               /DISABLE, and /ENABLE and to the directives .DISABLE andE               .ENABLE, which is documented in Appendixes A and B, hasu               been removed.e  E               Contrary to the documentation, you can initially enable I               the TRACEBACK and DEBUG options with the /ENABLE qualifier.iH               You can then turn the options off and on with the .DISABLED               and .ENABLE directives for whichever code sections youC               want. However, if the /DEBUG qualifier is used in the F               command line, it overrides /ENABLE=(DEBUG,TRACEBACK) andI               /DISABLE=(DEBUG,TRACEBACK), regardless of their position on                 the command line.   0         4.19 Mathematics (MTH$) Run-Time Library  H               The following sections contain release notes pertaining to6               the Run-Time Mathematics Library (MTH$).  (         4.19.1 Problems and Restrictions  <               This section describes known MTH$ problems and               restrictions.c  G         4.19.1.1 Linking Images to Run on Previous OpenVMS VAX Versionsm                  (VAX Only)S  F         V6.1  This version of OpenVMS VAX provides updated versions ofG               the Mathematics Run-Time Library (RTL) images MTHRTL.EXE,-I               UVMTHRTL.EXE, and VMTHRTL.EXE that contain new entry pointsnH               in support of DEC Fortran Version 6.0. (UVMTHRTL.EXE is anG               alternate form of MTHRTL.EXE; references to MTHRTL.EXE invC               the following paragraphs also apply to UVMTHRTL.EXE.)t  >               Due to the large number of entry points added toG               MTHRTL.EXE, that image's transfer vector was extended andtI               its global section match identifier incremented. This meanseF               that images linked against the new version of MTHRTL.EXED               will not run on a system running a previous version ofD               OpenVMS VAX, unless that system has also installed DEC  I                                                                      4-77                 Programming Release Notes ,     4.19 Mathematics (MTH$) Run-Time Library    E           Fortran Version 6.0. In addition, images linked against thenE           new MTHRTL.EXE cannot be translated to run on OpenVMS Alphae           using DECmigrate.i  D           To link an image so that it will run on a previous version@           of OpenVMS VAX, create a directory that contains saved@           copies of the .EXE and .OLB files from the SYS$LIBRARY@           directory of the earliest version you wish to support,B           and define the logical name SYS$LIBRARY to point to thatD           directory before linking. Because OpenVMS VAX also definesD           a system logical name MTHRTL to refer to either MTHRTL.EXEC           or UVMTHRTL.EXE, you must also define MTHRTL as a logicaliB           name in the process or job table to point to the copy in5           the directory of older images. For example:c  5           $ DEFINE/USER SYS$LIBRARY disk:[OLD_SYSLIB]55           $ DEFINE/USER MTHRTL SYS$LIBRARY:MTHRTL.EXEs           $ LINK ...  C           Images to be translated using DECmigrate should be linkedoD           against the SYS$LIBRARY files of OpenVMS VAX Version 5.5-2           or earlier.   <     4.19.1.2 Compatibility Between VAX and Alpha Mathematics#              Libraries (Alpha Only)i  C     V1.0  Mathematical applications using the standard OpenVMS calla>           interface to the OpenVMS Run-Time Mathematics (MTH$)>           Library need not change their calls to MTH$ routines@           when migrating to an Alpha system. Jacket routines mapB           MTH$ routines to their math$ counterparts in the Digital@           Portable Mathematics Library (DPML) for OpenVMS Alpha.A           However, there is no support in the DPML for calls madedA           to JSB entry points and vector routines. Note that DPMLpC           routines are different from those in the OpenVMS Run-TimeaD           Mathematics (MTH$) Library. You should expect to see smallC           differences in the precision of the mathematical results.e  @           If one of your goals is to maintain compatibility with>           future libraries and to create portable mathematical@           applications, Digital recommends that you use the DPMLD           routines available through the high-level language of yourA           choice (for example, DEC Fortran and DEC C) rather thanVD           using the call interface. Significantly higher performanceD           and accuracy are also available to you with DPML routines.       4-78           I                                                 Programming Release NotesoH                                 4.19 Mathematics (MTH$) Run-Time Library    E               See the Digital Portable Mathematics Library manual fora+               more information about DPML. n  <         4.20 Migration to OpenVMS Alpha Systems (Alpha Only)  E               The following sections contain release notes pertaining D               to migration from OpenVMS VAX systems to OpenVMS Alpha               systems.  4         4.20.1 Documentation Changes and Corrections  =               This section describes corrections to migrationiD               documentation. Also see Section 4.18.2 for correctionsF               to Migrating to an OpenVMS AXP System: Porting VAX MACRO               Code.   D         4.20.1.1 Migrating to an OpenVMS AXP System: Recompiling and'                  Relinking Applicationsr  A         V1.5  Migrating to an OpenVMS AXP System: Recompiling and E               Relinking Applications incorrectly describes /NONATIVE_ <               ONLY to be the default behavior of the linker.  D               The /NATIVE_ONLY qualifier to the LINK command directsH               the linker not to pass along the procedure signature blockG               (PSB) information, created by the compilers, in the imageOI               it is creating. This is the default behavior of the linker.r  H               PSB information is necessary if the image you are creatingD               in the link operation calls translated VAX images (butC               not if translated VAX images call it). To include PSBaE               information in the image, you must compile the originalcF               program sources with the appropriate compiler switch (asF               indicated by the compiler documentation) and specify theC               /NONATIVE qualifier when linking the program's object F               modules. The image activator uses the PSB information inE               the image to create jacket routines, which allow native ?               Alpha images to work with translated VAX images.    5         4.21 POLYCENTER Software Installation Utility   A               The notes in this section pertain to the POLYCENTERhF               Software Installation utility. Also see Section 3.22 forE               notes about this utility that are of interest to system                managers.c  I                                                                      4-79  C  S           Programming Release Notesm1     4.21 POLYCENTER Software Installation Utility     $     4.21.1 Problems and Restrictions  @           This section describes known problems and restrictionsD           with using the POLYCENTER Software Installation utility toE           create software kits. Problems and restrictions of interests=           to system managers are described in Section 3.22.1.t  $     4.21.1.1 Account Removal Problem  9     V6.1  Removing a product with the POLYCENTER SoftwareeA           Installation utility results in the removal of accounts A           specified by account statements. The utility should not A           do this in all cases because the file SYSUAF.DAT may be C           clusterwide or local to a single system disk or groups ofw           system disks.   B           If you install software on a particular system disk, anyB           account statements create the necessary accounts. If youB           install the software on a second system disk that sharesB           the same SYSUAF.DAT file, the account already exists and&           does not need to be created.  ?           When you remove a product, the utility always removes$@           the account, regardless of whether the SYSUAF.DAT file+           is shared by another system disk.b  <           The same problem exists with the rights identifier0           statement and the file RIGHTSLIST.DAT.  ?           Digital expects to correct these problems in a futuret           release.  /     4.21.1.2 Alphanumeric Options Not Supportedk  =     V6.1  You cannot allow installers to specify alphanumerict=           configuration choices using the POLYCENTER Softwarem@           Installation utility. The option statement allows only(           Boolean configuration choices.  =           Digital expects to correct this problem in a future            release.  3     4.21.1.3 Alternate File Placement Not Supported   C     V6.1  You cannot specify an alternate location for some of youroB           product files using the POLYCENTER Software Installation           utility.  =           Digital expects to correct this problem in a future            release.       4-80 o  n      I                                                 Programming Release NotestH                            4.21 POLYCENTER Software Installation Utility    +         4.21.1.4 Command Procedure Behaviorc  I         V6.1  The following product description file (PDF) statements usesH               command procedures to perform the creation and deletion of               managed objects:                 o  account                 o  network objectr  "               o  rights identifier  G               In a future version, the POLYCENTER Software Installation1A               utility may create and delete these managed objects E               directly without the use of command procedures. If thisrF               is the case, these statements will continue to function,I               but the command procedures may not be maintained or shipped 2               with future versions of the utility.  )         4.21.1.5 Conflict Error Reportinge  H         V6.1  Some error messages indicating managed object conflicts do0               not identify the related products.            4.21.1.6 Error Reporting  I         V6.1  When packaging a kit, you may receive many different errorsnD               (for example, wrong keywords or missing directives) inH               your product description file (PDF). In several cases, theI               utility error messages do not contain enough information to 1               determine the problem with the PDF.o  A               Digital expects to correct this problem in a futurew               release.  -         4.21.1.7 File Generation Restrictionsc  G         V6.1  The generation option to the file statement does not worki1               correctly under some circumstances.a                 For example:                 -- PDF #1:2               product DEC VAXVMS TEST1 V1.0 full ;2               file [SYSMGR]TEST.EXE generation 1 ;               end product ;                  -- PDF #2:2               product DEC VAXVMS TEST2 V1.0 full ;2               file [SYSMGR]TEST.EXE generation 2 ;               end product ;c  I                                                                      4-81r    e           Programming Release Notes 1     4.21 POLYCENTER Software Installation Utilityh    B           Installing TEST1 then TEST2 works correctly. However, ifB           you remove TEST2, generation one of the TEST.EXE file isB           not reinstalled and the utility displays a message about1           replacement material being unavailable.   A           One workaround is to have TEST2 use the execute installi>           statement to execute a procedure that saves previousD           versions of TEST.EXE. A corresponding execute remove could           restore it.   B           Another related problem is that you can remove TEST1 andB           then TEST2, but only in that order. The previous example?           shows removing TEST2 first which is the logical orderS:           (since it is the reverse order of installation).  E           Note that if you install TEST2 then TEST1, the installation ?           of TEST1 generates an error message about replacement ?           material being unavailable. The utility should give aOE           better error message that indicates that a newer generatione9           of the file is already installed on the system..  ?           Digital expects to correct these problems in a futuret           release.  ,     4.21.1.8 File Statement Generation Limit  D     V6.1  The maximum value allowed for the generation option on theB           file statement is 4294967295 (2**32-1). If you specify aE           larger number, the POLYCENTER Software Installation utility >           incorrectly uses the overflow value without warning.  =           Digital expects to correct this problem in a future            release.  *     4.21.1.9 Information Statement Problem  D     V6.1  Product Description File (PDF) information statements thatB           you want to display to the user during the configurationE           phase are not displayed if the user enters Yes (the defaulth,           answer) to the following question:  D           Do you want all the default values for this product? [YES]  =           Digital expects to correct this problem in a futuree           release.       4-82 a  g      I                                                 Programming Release Notes H                            4.21 POLYCENTER Software Installation Utility    4         4.21.1.10 Multiple Execute Remove Statements  H         V6.1  There is a problem with the execute remove statement whereD               only the first one executes during a remove operation.D               However, all of the execute install statements execute*               during an install operation.  A               Digital expects to correct this problem in a futurel               release.  9         4.21.1.11 Multiple Operating Scopes Not Supportede  E         V6.1  Multiple operating scopes are not supported and may nots6               work correctly in certain circumstances.  2         4.21.1.12 Network Object Statement Problem  H         V6.1  The command procedure that creates network objects for theE               network object statement asks the product developer foriE               the network object number. This is information that theiH               installer, not the product developer, has access to. Also,E               the utility does not provide a way for the installer to %               enter this information.   /         4.21.1.13 Package Operation Constraintst  G         V6.1  A typical task when creating software kits is to create a F               sequential kit by performing a package operation. If youG               use the same directory for the source and destination foruH               your package operation, you can create problems for futureD               install operations that use the directory as a source.  C               If both a sequential kit (with file type .PCSI) and auE               product description file for a reference kit (with filelC               type .PCSI$DESCRIPTION) are in the same directory, aniF               install operation that points to that source area alwaysG               opens the file with file type .PCSI$DESCRIPTION. This can D               cause errors locating product material if it is not inG               the same place. There is no way to specify the sequentialAH               kit for the installation when a reference kit for the same!               product is present.   E               To avoid this problem, use separate directories for theo@               source and destination of your package operations.  I                                                                      4-83N A  N           Programming Release Notes 1     4.21 POLYCENTER Software Installation Utilityc    &     4.21.1.14 Partial Kit Restrictions  ;     V6.1  Kits of type partial do work correctly under manyBC           circumstances. Digital recommends that you avoid creatingAC           partial kits with this version of the POLYCENTER SoftwareeD           Installation utility because of the following problems and           restrictions:   @           o  The utility does not require that a full kit of the0              product has already been installed.  E           o  If a full product kit is not found, the utility attemptsrE              to attach the partial kit to the operating system as itsr              parent.  ?           o  When removing a partial kit that has the operating ?              system as its parent, the utility also removes thei>              operating system without displaying any messages.  E           If possible, use patch or mandatory update kit types rathern           than partial kits.  ?           Digital expects to correct these problems in a future            release.  '     4.21.1.15 Rights Identifier Problemn  =     V6.1  Refer to Section 4.21.1.1 for a description of this            problem.  :     4.21.1.16 "Uses" Clause File Specification Restriction  ?     V6.1  You cannot specify the same file in the "uses" clause @           of two separate execute statements in the same product.           description file (PDF), for example:  *           product DEC AXPVMS MYSTUFF full;                ...E                execute install "@doit thisway" uses [000000]doit.com;nE                execute install "@doit thatway" uses [000000]doit.com;i                ...           end product;  4           The file is deleted before the second use.  =           Digital expects to correct this problem in a future            release.       4-84 t  e      I                                                 Programming Release NoteseH                            4.21 POLYCENTER Software Installation Utility    4         4.21.2 Documentation Changes and Corrections  =               This section describes changes in the utility'so               documentation.  2         4.21.2.1 DCL Help: PRODUCT PACKAGE Command  F         V6.2  The POLYCENTER Software Installation Utility Developer'sD               Guide has not been updated for the OpenVMS Version 6.2I               release, but the description of the PRODUCT PACKAGE commandaC               and its qualifiers has been significantly enhanced in D               online Help. Enter the HELP PRODUCT PACKAGE command at@               the DCL prompt to view this updated documentation.  F         4.21.2.2 POLYCENTER Software Installation Utility User's Guide  F         V6.2  Information formerly included in the POLYCENTER SoftwareD               Installation Utility User's Guide has been revised andD               incorporated into the OpenVMS System Manager's Manual:               Essentials.t  E         4.21.2.3 POLYCENTER Software Installation Utility Developer's                   Guide  @               The following sections describe corrections to theI               POLYCENTER Software Installation Utility Developer's Guide.I  '               4.21.2.3.1 File StatementE  I         V6.2  In the POLYCENTER Software Installation Utility Developer'ssC               Guide, the file statement is described in the ProductsG               Description Language (PDL) reference section. Replace therB               description of the [no]generation option as follows:  '               [no]generation generation H               Specifies the generation number of the file as an unsignedD               integer from 0 to 4294967295. Using the [no]generationH               clause is equivalent to specifying a value of 0; both meanE               the file has no explicit generation number. The defaulteD               for the file statement is [no]generation. Refer to the@               Description section for the meaning of this value.                   I                                                                      4-85t M              Programming Release Notes 1     4.21 POLYCENTER Software Installation Utilityc       4.21.2.3.2 Scope Statement  E     V6.1  In the POLYCENTER Software Installation Utility Developer'sl@           Guide, the scope statement is described in the Product=           Description Language (PDL) reference section and in <           Appendix B. The following notes apply to the scope           statement:  A           o  Bootstrap Scope should be used for products that use ?              device drivers, especially those drivers that must @              be read by the primitive file system. Because files>              in Bootstrap Scope are read by the primitive fileA              system, they are read when not synchronized with the C              file system on other cluster members that might access >              the same disk. Therefore, those files must retain@              stable positions as long as the disk is in use fromB              any system and must not be manipulated by online disk@              defragmentation operations, even those that use the               MOVEFILE primitive.  A           o  Product Scope is the default scope for most objects;S>              therefore, it is generally unnecessary to specify              Product Scope.   C           o  Operating Scope is not implemented for this version of :              the POLYCENTER Software Installation utility.       4.22 Run-Time LibrariesO  D           The following sections contain release notes pertaining to           run-time libraries.A  $     4.22.1 Problems and Restrictions  D           This section describes known run-time library problems and           restrictions.   E     4.22.1.1 Run-Time Libraries Not Included in OpenVMS Alpha Systems               (Alpha Only)e  E     V1.5  The run-time libraries listed in Table 4-7 are not includedi+           in this version of OpenVMS Alpha.            4-86 a  a      I                                                 Programming Release NoteshI                                                   4.22 Run-Time Librariesl    H               Table 4-7 Run-Time Libraries Not Included on OpenVMS AlphaI               __________Systems__________________________________________t  D               DBGSSISHR        DEBUG item, replaced by SYS$SSISHR on,                                OpenVMS Alpha  6               DNS$RTL          No DNS in OpenVMS Alpha  6               DNS$SHARE        No DNS in OpenVMS Alpha  A               VBLAS1RTL        No support for VAX vector programse  I               VMTHRTL__________No_support_for_VAX_vector_programs________   D               Most run-time libraries that were available in OpenVMSH               VAX Version 5.5-2 are available in this version of OpenVMSI               Alpha. The OpenVMS VAX Version 5.5-2 libraries that are notLG               available are either not being ported to OpenVMS Alpha or ?               are planned for a later release of OpenVMS Alpha.l  B               For example, the vector math libraries VBLAS1RTL andF               VMTHRTL are not available in OpenVMS Alpha because thereF               is no support on OpenVMS Alpha for programs that use the'               VAX vector instructions.    .         4.23 Screen Management (SMG$) Facility  H               The following sections contain release notes pertaining to4               the Screen Management (SMG$) Facility.  '         4.23.1 Changes and Enhancementst  D               This section describes changes and enhancements to the               software.   .         4.23.1.1 VT500 Series Terminal Support  F         V6.2  The Screen Management (SMG$) Facility implements supportI               for VT500 series terminals through the use of a third grouphE               of characteristics. The following specific changes wereu=               made to SMG$ to support VT500 series terminals.f  &               New Boolean Capabilities  E               Two new Boolean capabilities have been added for use ass                TERMTABLE entries:  I                                                                      4-87h e  s           Programming Release Notesl*     4.23 Screen Management (SMG$) Facility                           Used+           OpenVMS Name  by SMG  Description   A           ANSI_COLOR    N       If set, terminal conforms to ANSIr;                                 color programming standardsg  D           DEC_CRT_5     N       If set, terminal conforms to DIGITAL6                                 VT500 family standards  "           Changes to SMG$ Routines  D           The following SMG$ routines have been changed as described2           below to support VT500 series terminals:  A           SMG$GET_KEYBOARD_ATTRIBUTES  The following new symbolicnC           name provides access to VT500 series keyboard information @           table values through the keyboard-info-table argument.  =               SMG$L_DEV_DEPEND3    Specific characteristics 3r.                                    (longword).  C           SMG$GET_PASTEBOARD_ATTRIBUTES  The following new symbolictC           name provides access to VT500 series pasteboard attributea<           values through the pasteboard-info-table argument.  =               SMG$L_DEVDEPEND3     Specific characteristics 3 .                                    (longword).  D           SMG$SET_TERM_CHARACTERISTICS  Three new optional argumentsB           change terminal characteristics and retrieve the current>           terminal characteristics for VT500 series terminals.;           The three arguments are on-characteristics3, off- 5           characteristics3, and old-characteristics3.D             The new syntax is:  4           SMG$SET_TERM_CHARACTERISTICS pasteboard-id;               [,on-characteristics1] [,on-characteristics2]u=               [,off-characteristics1] [,off-characteristics2]t=               [,old-characteristics1] [,old-characteristics2]E<               [,on-characteristics3] [,off-characteristics3]%               [,old-characteristics3]   9           The three new arguments are defined as follows:r       4-88    t      I                                                 Programming Release NotesnI                                    4.23 Screen Management (SMG$) Facilitye    !               on-characteristics31               mask_longword !               longword (unsigned)                read only                by reference  H               Bit mask that specifies the terminal characteristics to beG               set from $TT3DEF. The on-characteristics3 argument is the I               address of an unsigned longword that contains the bit mask.   "               off-characteristics3               mask_longword !               longword (unsigned)s               read onlyf               by reference  H               Bit mask that specifies the terminal characteristics to beF               reset from $TT3DEF. The off-characteristics3 argument isG               the address of an unsigned longword that contains the bito               mask.o  "               old-characteristics3               mask_longword !               longword (unsigned)                read only                by reference  I               Retrieves the current terminal characteristics in the third H               group. The old-characteristics3 argument is the address of>               an unsigned longword that contains the bit mask.           4.24 Security   H               The following sections contain release notes pertaining to               security.   '         4.24.1 Changes and Enhancements   C               This section describes changes or enhancements to thei               software.                 I                                                                      4-89                 Programming Release Notesp     4.24 Securityt    +     4.24.1.1 SYS$EXAMPLES:HASH_PASSWORD.MARe  B     V6.1  Two changes were made to the site-specific password hashC           algorithm example code in SYS$EXAMPLES:HASH_PASSWORD.MAR. >           Sites using this file as a basis for a site-specificA           password hash algorithm must recompile and relink theirtB           SYS$HASH_PASSWORD executive loadable images based on the           new template.p  ?           If you modified the Digital-supplied preamble code inS@           the example, note the functional changes listed below.B           As before, site-specific algorithm dispatching generally7           replaces a "NOP" instruction in the template.l  D           o  The value of UAF$C_PREFERRED_ALGORITHM has been changedC              from 3 to 127. The new value will remain constant fromt>              now on. Existing binary images that reference theB              preferred algorithm using the old value will continueE              to function, but will need to be recompiled and relinked A              if the preferred algorithm were ever to change. WitheA              this change, such images will have to recompile onlya              once.  >           o  User-mode probing of the formal parameters is nowE              conditionally assembled based on the PROTECT conditional E              assembly prefix. If the service is being assembled as an E              exec-mode service, PROBEs are still used. Otherwise, the B              system condition handler EXE$SIGTORET is used to turnE              user-mode signals into their corresponding return statuseC              values. This change corrects a problem seen when usingoB              $HASH_PASSWORD with static watchpoints in the OpenVMS              Debugger.  B     4.25 STARLET Data Structures and Definitions for C Programmers          (Alpha Only)        V1.0  E           OpenVMS Alpha Version 1.0 includes a new file, SYS$STARLET_eD           C.TLB, that contains all the .H files that provide STARLET=           functionality equivalent to STARLETSD.TLB. The files>           SYS$STARLET_C.TLB, together with DECC$RTLDEF.TLB nowE           shipping with the DEC C Compiler, replaces VAXCDEF.TLB that E           previously shipped with the VAX C Compiler. DECC$RTLDEF.TLBsA           contains all the .H files that support the compiler and            RTL, such as STDIO.H.        4-90 t  l      I                                                 Programming Release NotesrI  STARLET   Data Structures and Definitions for C Programmers (Alpha Only)o    C               The following differences may require source changes:1                 o  RMS structuresl  F                  Previously, the RMS structures FAB, NAM, RAB, XABALL,G                  and so forth, were defined in the appropriate .H filesoC                  as "struct RAB {...", for example. The .H files to E                  be supplied in OpenVMS Alpha Version 1.0 will define.E                  them as "struct rabdef {...". To compensate for thislH                  difference, lines of the form "#define RAB rabdef" haveD                  been added. However, there is one situation where aE                  source change is required because of this change. IfiH                  you have a private structure that contains a pointer toF                  one of these structures and your private structure isI                  defined (but not used) before the RMS structure has been I                  defined, you will receive compile-time errors similar tof                  the following:   O       %CC-E-PASNOTMEM, In this statement, "rab$b_rac" is not a member of "rab".C  D                  This error can be avoided by reordering your sourceE                  file so that the RMS structure is defined before the C                  private structure. Typically, this involves moving .                  around "#include" statements.  6               o  LIB (privileged interface) structures  C                  Historically, three structures from LIB (NFBDEF.H,cG                  FATDEF.H, and FCHDEF.H) have been made available as .HoG                  files. These files were shipped as .H files in OpenVMSrG                  Alpha Version 1.0 and 1.5 (not in the new SYS$STARLET_ H                  C.TLB). In OpenVMS Alpha Version 6.1, the file SYS$LIB_F                  C.TLB, containing all LIB structures and definitions,E                  has been added. These three .H files are now part ofeG                  that .TLB and are no longer shipped separately. SourcerE                  changes may be required, as no attempt has been maderG                  to preserve any existing anomalies in these files. TheoG                  structures and definitions from LIB are for privilegedeE                  interfaces only and are therefore subject to change.h  <               o  Use of "variant_struct" and "variant_union"  D                  In the new .H files, "variant_struct" and "variant_@                  union" are always used, whereas previously someE                  structures used "struct" and "union". Therefore, the F                  intermediate structure names cannot be specified when;                  referencing fields within data structures.f  I                                                                      4-91r l  t           Programming Release NotesrO     4.25 STARLET Data Structures and Definitions for C Programmers (Alpha Only)t    2              For example, the following statement:  P         AlignFaultItem.PC[0] = DataPtr->afr$r_pc_data_overlay.afr$q_fault_pc[0];                becomes:   ?              AlignFaultItem.PC[0] = DataPtr->afr$q_fault_pc[0];              o  Member alignmentt  @              Each of the .H files in SYS$STARLET_C.TLB saves and>              restores the state of "#pragma member_alignment".             o  Conventions  =              The .H files in SYS$STARLET_C.TLB adhere to some :              conventions that were only partly followed inA              VAXCDEF.TLB. All constants (#defines) have uppercaseiA              names. All identifiers (routines, structure members,rA              and so forth) have lowercase names. Where there is a E              difference from VAXCDEF.TLB, the old symbol name is alsoeD              included for compatibility, but users are encouraged to(              follow the new conventions.  <           o  Use of Librarian utility to access the .H files  B              During installation of OpenVMS Alpha Version 1.0, theA              contents of SYS$STARLET_C.TLB are not extracted intoh?              the separate .H files. The DEC C Compiler accesses B              these files from within SYS$STARLET_C.TLB, regardlessD              of the format of the #include statement. If you want toE              inspect an individual .H file, you can use the Librarian 2              utility, as in the following example:  O        $ LIBRARY /EXTRACT=AFRDEF /OUTPUT=AFRDEF.H SYS$LIBRARY:SYS$STARLET_C.TLB   >           o  Additional .H files included in SYS$STARLET_C.TLB  =              In addition to the .H files derived from STARLETE>              sources, SYS$STARLET_C.TLB includes .H files that;              provide support for DECthreads, such as CMA.H.        4.26 System Services  D           The following sections contain release notes pertaining to           system services.  B           All system services are documented in the OpenVMS System$           Services Reference Manual.       4-92 r  n      I                                                 Programming Release NotesEH                                                     4.26 System Services    '         4.26.1 Changes and Enhancements   H               The sections that follow describe changes and enhancements%               to the system services.   =         4.26.1.1 $INIT_VOL Has New INIT$_HOMEBLOCKS Item Code   E         V6.2  The INIT$_HOMEBLOCKS item code for the $INIT_VOL systemnI               service has been added to retain backward compatibility and5I               to allow container file systems to make optimal use of diskg               space.  C               The INIT$_HOMEBLOCKS item code can have the followingl               values:h  +               o  INIT$K_HOMEBLOCKS_GEOMETRYe  B                  Causes the volume homeblocks to be placed on diskE                  depending on the reported geometry of the disk. This G                  is the behavior that occurred prior to OpenVMS Version.                  6.2.I  (               o  INIT$K_HOMEBLOCKS_FIXED  C                  Causes the volume homeblocks to be placed at fixed H                  offsets on the disk regardless of geometry. This is theI                  new default. It provides for disks that report different I                  geometries, depending on the type of controller to which:&                  the disk is attached.  -               o  INIT$K_HOMEBLOCKS_CONTIGUOUSc  G                  Causes the volume homeblocks to be placed contiguously E                  at the start of the disk. This allows container filerF                  systems to maximize the amount of contiguous space onG                  the disk when used with the INIT$_INDEX_BEGINNING itemr                  code.  >         4.26.1.2 $LCKPAG and $LKWSET Limits Are Set by WSQUOTA  G         V6.2  The value set for WSQUOTA limits the number of pages thataC               the system services $LCKPAG and $LKWSET can lock. ThefA               maximum value of WSQUOTA is 65536 (64K byte) pages.F    I                                                                      4-93c S              Programming Release Notes      4.26 System Services    <     4.26.1.3 $SNDJBC Has New SJC$_DISPLAY_USERNAME Item Code  D     V6.2  The SJC$_DISPLAY_USERNAME item code for the $SNDJBC systemC           service has been added to make it easier for applications B           such as servers to submit print jobs for users. The itemC           code has been available since OpenVMS VAX Version 5.5 and D           OpenVMS Alpha Version 1.5 but has not been documented. The>           item code is supported for these and later versions.  B           The SJC$_DISPLAY_USERNAME item code allows you to changeC           the user name string without changing the requester's ARB A           (security access rights block). This item is useful for A           server applications that submit print jobs on behalf ofoD           users. It will modify the user name used in separator pageB           output. It also specifies the user name string placed inD           the audit record when the symbiont does an access check onB           the input file. The access check will use the ARB of theB           requester, not the ARB of the user specified by the user4           name string. CMKRNL privilege is required.  *     4.26.1.4 $SYNCH and Wait Form Services  >     V6.2  For OpenVMS Version 6.2, the $SYNCH service has beenB           modified to eliminate a problem that can cause a process@           to remain in event flag wait state after a service hasC           completed. The problem is a race condition that can occuroC           when the same event flag is concurrently used by multiple.?           execution threads within the process. For this change A           to be effective, the caller must provide a status block A           (usually an IOSB). This change also applies to the wait E           form services, such as $QIOW, which call $SYNCH implicitly.   $     4.26.2 Problems and Restrictions  E           This section describes known problems and restrictions withp           system services.  +     4.26.2.1 $SNDJBC Batch Queue Limitation.  E     VAX   OpenVMS Version 6.0 allows multiple queue managers. If youroD     V6.0  system uses this feature to run batch queues on a separateE     Alpha queue manager from output queues, certain checks that would D     V6.1  otherwise be performed for the SJC$_LOG_QUEUE item code of7           the $SNDJBC system service are not performed.e         4-94           I                                                 Programming Release Notes H                                                     4.26 System Services    G               When batch and print queues are managed by the same queueeH               manager, the queue manager checks to ensure that the queueF               specified with the SJC$_LOG_QUEUE is an output queue andH               that the user has access to the output queue. These checksF               are not made if the batch queue specified by the $SNDJBCE               service and the output queue specified by the SJC$_LOG_ F               QUEUE item code are managed by different queue managers.  H               If you explicitly specify an output queue for the log fileH               when submitting a batch job, be sure the queue you specifyH               with the SJC$_LOG_QUEUE is an output queue and not a batchF               queue. Also, be sure that you have access to the printer               queue.  E         4.26.2.2 $SUSPND Behaves Incorrectly in a Cluster Environment   F         VAX   When the $SUSPND system service is called and the targetE         V6.0  process is on a different cluster node than that of the B         Alpha process calling the $SUSPND service, the kernel modeG         V1.5  suspend flag (bit 0) is ignored. As a result, any suspend 6               is treated as a supervisor-mode suspend.  F               Digital expects to fix this problem in a future release.  B         4.26.2.3 $FORMAT_AUDIT Width Argument Works Inconsistently  I         VAX   The width argument to the $FORMAT_AUDIT system service does G         V5.0  not work consistently. In most cases, if you specify both I         Alpha the width argument and the full format style (NSA$C_FORMAT_ D         V1.0  STYLE_FULL), $FORMAT_AUDIT ignores the width argument.  H               The minimum width is 80 columns; lower values do not limitG               the width to less than 80. If you specify a width greaterfH               than 80 columns, most lines are not joined to use the full               width.  9               In general, avoid using the width argument.   4         4.26.3 Documentation Changes and Corrections  H               The notes in this section describe changes and corrections>               to the OpenVMS System Services Reference Manual.    I                                                                      4-95c                Programming Release Notes      4.26 System Services    #     4.26.3.1 $CHKPRO System Service   D     V6.2  The following is a documentation correction to the $CHKPROC           system service description; it replaces the CHP$_ACL item            description:             CHP$_ACL  B           The buffer, specified by BUFADR and BUFLEN, contains oneB           or more ACEs. The length of each ACE is contained in theB           first byte of the ACE. If the specified buffer length isE           greater than the sum of the ACE lengths, the byte followingf?           the last ACE must be zero (that is, the buffer can be -           terminated with a zero-length ACE).w  @           The format of an ACE depends on the ACE type, which isD           the second byte of the ACE. The $FORMAT_ACL system service1           describes each ACE type and its format.e  C           You can specify the CHP$_ACL item multiple times to point A           to multiple segments of an access control list, up to a E           maximum of 20 segments. Segments are processed in the orderw           specified.  &     4.26.3.2 $TSTCLUEVT System Service  B     V6.2  Add the following information to the Description sectionA           for the $TSTCLUEVT system service in the OpenVMS Systemd.           Services Reference Manual: GETQUI-Z:  @              The $TSTCLUEVT system service allows an applicationC              to test itself and must be issued from within the samelE              process as the application being tested. $TSTCLUEVT doesa7              not affect other processes in the cluster.r  0     4.26.3.3 $CREATE_USER_PROFILE System Service  C     V6.1  The following corrections apply to the description of the C           $CREATE_USER_PROFILE system service in the OpenVMS System $           Services Reference Manual:  @           o  The usrpro argument is passed by descriptor, not by              reference.c  E           o  The usrprolen argument has read/write access, not write-S              only access.   ?           o  The description of the CHP$_ADDRIGHTS item code ish2              incorrect. It should read as follows:       4-96 P  W      I                                                 Programming Release Notes H                                                     4.26 System Services                      CHP$_ADDRIGHTSeH                  A rights list segment containing additional identifiersE                  to be appended to the set of identifiers held by the B                  user. A rights list segment is a list of quadword?                  identifier/attributes pairs, each containing a G                  longword identifier value, followed by a longword mask E                  identifying the attributes of the holder. The buflen D                  argument should be set to the total size, in bytes,G                  of the rights list segment. The bufadr argument pointshE                  to a descriptor that points to the first byte in the D                  rights list segment (that is, the first byte of the)                  first identifier value).R  @                  This item code can be repeated to add up to 256B                  additional rights list segments. If more than 256C                  identifiers are granted to the user, $CREATE_USER_$-                  PROFILE returns SS$_INSFMEM.e  '         4.26.3.4 $GETQUI System Servicea  C         V6.1  The context argument to the $GETQUI system service isnC               documented incorrectly in the OpenVMS System ServicesS               Reference Manual..  C               The documentation says the context argument has read-(F               only access and is passed by value. In fact, the contextD               argument has modify access and is passed by reference.  "         4.27 System Time Operation  H               The following sections contain release notes pertaining to(               the system time operation.  4         4.27.1 Documentation Changes and Corrections  B               This section includes new documentation information.  4         4.27.1.1 OpenVMS Programming Concepts Manual  A         V6.1  The following information should be included in the I               "System Time Operations" chapter of the OpenVMS Programmingm               Concepts Manual.  B               The Date/Time Manipulation option provides date/time?               spelling support for four new languages. Users or1H               application programmers can select the desired language byH               defining the logical name SYS$LANGUAGES. The new languages8               and their equivalent names are as follows:  I                                                                      4-97d    n           Programming Release Notes      4.27 System Time Operation  E           ___________________________________________________________oE           Language___________________Equivalent_Name_________________v  *           Chinese (simplified        Hanzi           character)  *           Chinese (traditional       Hanyu           character)  +           Korean                     Hangul   E           Thai_______________________Thai____________________________   %           Defining Date/Time Spellinge  <           To define the spelling for Hanzi and Hanyu, defineA           SYS$LANGUAGES as shown below, prior to invoking LIB$DT_o           STARTUP.COM:  -           $ DEFINE SYS$LANGUAGES HANZI, HANYUm'           $ @SYS$MANAGER:LIB$DT_STARTUP   #           Predefined Output Formats   B           Tables 4-8 and 4-9 list the new predefined date and timeB           format logical names, their formats, and examples of the/           output generated using those formats.a  2           Table 4-8 Predefined Output Date Formats  5           Logical Name      Format            Examplec  ?                    The contents of this table cannot display in)&                    monospaced formats.    C              ________________________ Note ________________________   @              LIB$DATE_FORMAT_042 and LIB$DATE_FORMAT_043 support/              the DEC Hanzi coded character set.   @              LIB$DATE_FORMAT_044 and LIB$DATE_FORMAT_045 support/              the DEC Hanyu coded character set.b  @              LIB$DATE_FORMAT_046 and LIB$DATE_FORMAT_047 support0              the DEC Hangul coded character set.  C              ______________________________________________________m       4-98           I                                                 Programming Release NotescH                                               4.27 System Time Operation    6               Table 4-9 Predefined Output Time Formats  ;               Logical Name      Format              Example   C                        The contents of this table cannot display in +                         monospaced formats.u    F                 ________________________ Note ________________________  @                 LIB$TIME_FORMAT_021 supports the DEC Hanzi coded                 character set.  @                 LIB$TIME_FORMAT_022 supports the DEC Hanyu coded                 character set.  A                 LIB$TIME_FORMAT_023 supports the DEC Hangul coded.                 character set.  F                 ______________________________________________________  H               Thus, to select a particular format for a date or time, orG               both, you can define the LIB$DT_FORMAT logical name using %               the following logicals:f  I               o  LIB$DATE_FORMAT_nnn, where nnn can range from 001 to 047   I               o  LIB$TIME_FORMAT_nnn, where nnn can range from 001 to 023a  <         4.28 Translated Image Environment (TIE) (Alpha Only)           V1.5  E               Image translation is one means of migrating all or partoC               of a VAX application to OpenVMS Alpha. The DECmigrateiA               for OpenVMS AXP VAX Environment Software Translator,E               utility (VEST) creates a translated image by convertingWE               a VAX executable or shareable image into a functionallybI               equivalent Alpha image. VEST is a component of the optionalc9               layered product DECmigrate for OpenVMS AXP.   @               When a translated image runs on OpenVMS Alpha, theA               Translated Image Environment (TIE) provides the VAX E               environment required for the image to execute properly. D               The TIE consists of the shareable images TIE$SHARE andH               TIE$EMULAT_TV, which perform VAX complex instructions. For  I                                                                      4-99i l              Programming Release Notes 8     4.28 Translated Image Environment (TIE) (Alpha Only)    E           information on the role of image translation in a migration ?           strategy, see the manuals Migrating to an OpenVMS AXP C           System: Planning for Migration and DECmigrate for OpenVMS )           AXP Systems Translating Images..  9           The following subsections discuss these topics:c  B           o  Interoperability between native and translated images  &           o  Running translated images  (           o  TIE statistics and feedback  ?           Interoperability Between Native and Translated Imagese  A     V1.0  The TIE works together with other components of OpenVMS 9           Alpha to enable native and translated images to @           interoperate, that is, to call one another. If you areA           developing applications or run-time libraries that rely D           on interoperability, you need to follow certain procedures@           when compiling, linking, or translating. See the first?           restriction described in Section 4.28.1.4. Table 4-10S?           provides pointers to documentation that describes thee           procedures.w  3           Table 4-10 Interoperability Documentationr  .           Goal                       Reference  <           Ensuring interoperability  Migrating to an OpenVMS@           between native and         AXP System: Recompiling and;           translated images          Relinking Applicationso  ?                                      DECmigrate for OpenVMS AXP ?                                      Systems Translating Images   ?           Coordinating native        DECmigrate for OpenVMS AXP6?           and translated run-time    Systems Translating Images            librariesh  #           Running Translated Images   @     V1.0  Use the DCL RUN command to run a translated image. For           example:             $ RUN FOO_TV.EXE  	     4-100  f  n      I                                                 Programming Release Notes I                      4.28 Translated Image Environment (TIE) (Alpha Only)C    C               Note that the translated image does not run correctlycF               unless OpenVMS Alpha includes the appropriate translatedI               shareable images and run-time libraries. When you translate H               an image, VEST requires the image information files (IIFs-C               file type .IIF) corresponding to whichever images andSH               libraries that the input image refers to. These .IIF filesE               enable VEST to create a translated image that correctlyAG               refers to the translated versions of the shareable images5D               and libraries. An image information file used at imageG               translation must exactly correspond to the version of theoI               translated shareable image or run-time library available onA               OpenVMS Alpha.  A               OpenVMS Alpha includes a set of translated run-time F               libraries and a matching set of image information files,D               which are listed in Section 4.29. Check these lists toI               determine if they include the libraries or shareable imagesME               referred to by images you want to translate and run. IfdG               OpenVMS Alpha does not include the required shared imagesYF               or libraries, refer to the manual DECmigrate for OpenVMSG               AXP Systems Translating Images. This manual describes how 8               to create and use image information files.  E               When a translated library has been replaced by a nativefD               version of the library, you need to define accordinglyE               any logical names that point to it-that is, you need toh)               redefine image_TV to image.   )               TIE Statistics and Feedbackh  E         V1.0  In addition to the TIE's run-time support function, TIEhD               statistics and feedback can help to improve translated                image performance:  B               o  The TIE can display statistics about the run-timeA                  execution of translated images. These statistics B                  describe the image's use of TIE resources and the-                  interactions between images.i  F               o  The TIE can record information about VAX entry pointsA                  discovered while interpreting VAX code. When you D                  retranslate the image, VEST uses the information to2                  find and translate more VAX code.    I                                                                     4-101$ C  m           Programming Release Notes 8     4.28 Translated Image Environment (TIE) (Alpha Only)    C           The manual DECmigrate for OpenVMS AXP Systems Translating$D           Images describes these features in detail and explains howC           to define the logical names that enable and disable theire           use.  $     4.28.1 Problems and Restrictions  E           This section describes known problems and restrictions withe           the TIE.  *     4.28.1.1 Condition Handler Restriction  C     V1.5  There is a permanent restriction on the type of condition =           handler that can be established for both native and @           translated images. A native routine cannot establish aD           translated condition handler, nor can a translated routine>           establish a native condition handler. If a native orB           translated image violates this restriction, the run-time$           results are unpredictable.  +     4.28.1.2 Exception Handler Restrictionsu  E     V1.5  The following exception handler restrictions are permanent:p  E           o  Translated images with exception handlers that depend oni@              receiving the correct program status longword (PSL)=              might not function properly. When exceptions arep@              reported, the Alpha program status (PS) is reportedE              in the signal array instead because there is no VAX PSL.S  B           o  Translated images with exception handlers that dependE              on modifying the PSL in the signal array do not function.E              properly. The modified PSL is not propagated back to then              faulting code.$  (     4.28.1.3 Floating-Point Restrictions  B     V1.5  The following floating-point restrictions are permanent:  A           o  In some cases, floating-point instructions operatingoD              on the same data generate a trap on an Alpha system butB              not on a VAX system. Specifically, VAX floating-pointA              instructions on OpenVMS Alpha generate traps for the.B              "dirty zeros" that VAX hardware can handle correctly.=              "Dirty zeros" are floating-point values that aretB              alternate encodings for zero. To retain compatibility@              with translated code that performs operations usingC              dirty zeros, the TIE includes a condition handler thatAD              corrects the dirty zeros and retries the floating-point  	     4-102l r  l      I                                                 Programming Release Notes I                      4.28 Translated Image Environment (TIE) (Alpha Only)h    E                  operation. However, the handler succeeds only if theiG                  qualifier /PRESERVE=FLOAT_EXCEPTIONS was used when the &                  image was translated.  F                  Images that were not translated with /PRESERVE=FLOAT_I                  EXCEPTIONS and that perform an operation on a dirty zero F                  incur an HPARITH exception with a summary status thatI                  has bit 1 set. If your translated application incurs one G                  of these exceptions, retranslate with /PRESERVE=FLOAT_ E                  EXCEPTIONS. VAX dirty zeros commonly result from not G                  initializing floating data to 0. In this case, changesBI                  to source code may be necessary to port to OpenVMS AlphaA6                  an application that uses dirty zeros.  D               o  Alpha D53 floating point (D_floating point as a 53-E                  bit fraction instead of a 56-bit fraction) is VAX D_ F                  floating converted to G_floating representation. ThisH                  conversion leads to the following problem. Consider the*                  VAX instruction sequence:                     MOVD    (SP),R2!                  MOVD    R2,-(SP)m  G                  VEST translates these VAX instructions into Alpha code $                  like the following:  9                  LDD     F2,0(R14)       ! Pickup D floatnL                  CVTDG   F2,F2           ! Convert to Canonical G Form with 3                                          ! roundingwM                  CVTGD   F2,F17          ! Convert back to D Form for storing ;                  STD     F17,-8(R14)     ! Store the resultM  C                  At run time, the VEST-generated code uses roundingnB                  to obtain the most accurate G_floating value whenG                  converting the D56 floating point to G canonical form.TF                  In some cases, the conversion to G canonical form mayI                  round up the D_floating value to create an exponent thatnH                  cannot be represented in D_floating. When this happens,I                  the CVTGD operation incurs an HPARITH trap with floatingn0                  overflow as the summary reason.  G                  If a translated image incurs this problem at run time,lD                  it needs to be retranslated with the VEST qualifier6                  /FLOAT=D56_FLOAT to execute properly.    I                                                                     4-1036 P  W           Programming Release Notes 8     4.28 Translated Image Environment (TIE) (Alpha Only)    *     4.28.1.4 Interoperability Restrictions  ;     V1.5  Note the following interoperability restrictions:   ?           o  A native routine that either calls or is called by >              a translated image must be compiled with the /TIE<              qualifier and be linked with the /NONATIVE_ONLYD              qualifier. Checking for interoperability between nativeB              and translated images occurs at run time. If the /TIEB              and /NONATIVE_ONLY qualifiers are not used to compile@              and link the native routine, an error occurs at run>              time when the the native routine and a translatedD              image attempt to interoperate. If such an error occurs,C              recompile and relink the native routine appropriately.h  B           o  An access violation can occur at run time if a nativeB              routine that was not compiled with the /TIE qualifier@              makes an indirect call to a translated routine. TheC              indirect call is made through a variable that containsSA              the translated routine's address. When this happens,6B              there is no autojacketing code in place to assist the@              native-to-translated call. The native code attempts=              to use the routine address as a native procedureaE              descriptor. The code address of a native procedure is at D              offset PDSC$L_ENTRY, whose value is 8, from the base ofE              the procedure descriptor. Because the translated routineeD              address is treated as a procedure descriptor, the valueA              at offset 8 from that address is used as the code toh?              call. This usually results in an access violation.a  D              If you are encountering this problem, use a debugger to!              check the following:e  >              o  Check that R27 points into a translated image.  E              o  Check that bits <31:2> of 8(R27) equal bits <31:2> ofnD                 the access violation address. (All bits are not usedA                 because Alpha instructions are longword aligned.)i  :              o  Check that R26 points into a native image.  A              o  Check that -4(R26) is a JSR R26,(26) instruction.l  @              If all these checks prove to be true, recompile the=              native routine with the /TIE qualifier to enablea'              autojacketing at run time.   	     4-104            I                                                 Programming Release NotesSI                      4.28 Translated Image Environment (TIE) (Alpha Only)_    7         4.28.1.5 VAX C: Translated Program Restrictionsv  E         V1.5  The following translated VAX C program restrictions arei               permanent:  A               o  If a program uses the VAX C RTL routine brk() to G                  release dynamic memory (that is, a break address lower_G                  than the current break address is requested), the nexteD                  attempt by TIE to use a complex instruction routineD                  may result in a fatal memory access violation. ThisD                  may happen because the complex instruction routinesE                  are in a separate image, TIE$EMULAT_TV.EXE, which isdF                  dynamically activated by LIB$FIND_IMAGE_SYMBOL on theI                  first use of one of the routines. Depending on when this E                  occurs and the address passed to the brk() call thataI                  releases memory, the memory into which TIE$EMULAT_TV.EXEt0                  is loaded may also be released.  B                  To avoid this problem, never use brk() to releaseH                  memory, or be sure to execute a complex VAX instructionG                  before getting the break address that is later used tooH                  release memory. Using brk() to allocate memory is fine.  E               o  A translated VAX C program that uses vfork() and anyuF                  executive function may hang at run time. If the childD                  process of the VAX C program aborts erroneously, itD                  may hang waiting for a mailbox I/O to be completed.D                  One workaround is to prevent the child process from                  aborting.  2         4.29 Translated Image Support (Alpha Only)  H         V6.1  At the beginning of the OpenVMS Alpha program, translationI               support was provided to remove impediments for users moving                to Alpha due to:  8               o  Lack of full language support initially  @               o  Unavailability of source code for recompilation  H               o  Difficulty of recompiling code that depended heavily on9                  certain features of the VAX architecture   I                                                                     4-105  h  c           Programming Release NotesF.     4.29 Translated Image Support (Alpha Only)    @           For languages whose VAX versions are undergoing active?           development, native Alpha versions are now available.aA           The Translated Image Environment is being maintained to C           support those language features that were available as ofw3           the release of OpenVMS VAX Version 5.5-2.n  B           Similarly, translation is supported for images whose useA           of system services and run-time library entry points issA           restricted to those that existed on OpenVMS VAX Version            5.5-2.  C           In cases where more recent VAX layered products have beenaA           installed, it may be necessary to take minor additionaln@           steps if application needs require rebuilding an imageA           suitable for translation. For instance, with DECwindows D           Motif Version 1.2 or Version 1.2-3 for OpenVMS VAX, images@           must be built with the OSF Motif Version 1.1.3 library@           or the DECwindows XUI library rather than with the OSFE           Motif Version 1.2.2 or Version 1.2.3 library in order to be #           suitable for translation.o  C           Similarly, for those using recent versions of DEC FortrancA           for VAX, an additional qualifier is required to compileg=           Fortran programs that are suitable for translation.X  <           For further information, see the release notes for"           particular VAX products.  D           As a safety measure for situations where future rebuildingC           and retranslation of OpenVMS VAX images is likely, it mayeB           be preferable to save copies of the relevant OpenVMS VAXD           Version 5.5-2 shareable images in a separate VAX directoryA           and link new versions of VAX applications against thosenC           images. Using that technique the resulting images will be E           compatible with newer OpenVMS VAX shareable images (picking E           up any OpenVMS enhancements of existing features), and willaE           also be properly built for translation to OpenVMS Alpha (byr<           not requiring newer versions of shareable images).  B           The following sections list the translated images, image=           information files, and other related files that areo&           provided with OpenVMS Alpha.  B           OpenVMS Alpha contains no translated message images. All/           message images have been made native.   	     4-106m i         I                                                 Programming Release NotesnI                                4.29 Translated Image Support (Alpha Only)e    /               Translated Images in SYS$LIBRARY:l  #                  BASRTL2_D53_TV.EXE #                  BASRTL2_D56_TV.EXE "                  BASRTL_D56_TV.EXE&                  BASRTL_TV_SUPPORT.EXE$                  BLAS1RTL_D53_TV.EXE$                  BLAS1RTL_D56_TV.EXE"                  COBRTL_D56_TV.EXE"                  DBLRTL_D56_TV.EXE                  EDTSHR_TV.EXE                  FORRTL2_TV.EXE "                  FORRTL_D56_TV.EXE#                  LIBRTL2_D56_TV.EXEn"                  LIBRTL_D56_TV.EXE"                  MTHRTL_D53_TV.EXE"                  MTHRTL_D56_TV.EXE"                  PASRTL_D56_TV.EXE"                  PLIRTL_D56_TV.EXE                  RPGRTL_TV.EXE                  SCNRTL_TV.EXE                  TECOSHR_TV.EXEO"                  TIE$EMULAT_TV.EXE$                  UVMTHRTL_D53_TV.EXE$                  UVMTHRTL_D56_TV.EXE$                  VAXCRTLG_D56_TV.EXE#                  VAXCRTL_D56_TV.EXEC                  VMSRTL_TV.EXE  .               Translated Images in SYS$SYSTEM:  !                  DBLMSGMGR_TV.EXE                   EDF_TV.EXE                   EDT_TV.EXEa                  MONITOR_TV.EXEr                  TECO32_TV.EXE  0               Translated RTL Images in IMAGELIB:  #                  BASRTL2_D53_TV.EXEd"                  BASRTL_D56_TV.EXE$                  BLAS1RTL_D53_TV.EXE"                  COBRTL_D56_TV.EXE"                  DBLRTL_D56_TV.EXE                  FORRTL2_TV.EXE "                  FORRTL_D56_TV.EXE  I                                                                     4-107m o  i           Programming Release Notesl.     4.29 Translated Image Support (Alpha Only)                  LIBRTL_D56_TV.EXE              PLIRTL_D56_TV.EXE              RPGRTL_TV.EXE              SCNRTL_TV.EXE  C           Note that most of the translated RTLs are provided in D56 B           format rather than D53 format; some are provided in both?           formats. Where both formats are provided, the default D           format is D53. See Section 4.30 for more information about,           the translated run-time libraries.  1           Image Information Files in SYS$LIBRARY:                 ACLEDTSHR.IIF              BASRTL2.IIF              BASRTL.IIFo              BLAS1RTL.IIFO              COBRTL.IIF               CONVSHR.IIF              CRFSHR.IIFo              DBLRTL.IIFt              DCXSHR.IIFo              DISMNTSHR.IIF              DTKSHR.IIFa              EDTSHR.IIFv              ENCRYPSHR.IIF              EPC$SHR.IIF              FDLSHR.IIF               FORRTL.IIF               FORRTL2.IIF              INIT$SHR.IIF               LBRSHR.IIFe              LIBRTL.IIFt              LIBRTL2.IIF              MAILSHR.IIF              MOUNTSHR.IIFr              MTHRTL.IIF               NCSSHR.IIFb              P1_SPACE.IIFn              PASRTL.IIFg              PLIRTL.IIF               PPLRTL.IIFl!              PTD$SERVICES_SHR.IIF               RPGRTL.IIFo              S0_SPACE.IIFs  	     4-108            I                                                 Programming Release NotescI                                4.29 Translated Image Support (Alpha Only)b                      SCNRTL.IIF                   SCRSHR.IIFe                  SECURESHR.IIF                  SMBSRVSHR.IIF                  SMGSHR.IIFo                  SORTSHR.IIF                  SPISHR.IIF                   TECOSHR.IIF                  TPUSHR.IIF                   UVMTHRTL.IIF                   VAXCRTL.IIF                  VAXCRTLG.IIFm                  VMSRTL.IIF   .               System Logical Names Definitions  ?               The following system logical names are defined toi4               facilitate the translated environment:  )                  ACLEDTSHR_TV = ACLEDTSHR #                  CDDSHR_TV = CDDSHRi%                  CONVSHR_TV = CONVSHRb#                  CRFSHR_TV = CRFSHRt#                  DCXSHR_TV = DCXSHR1)                  DISMNTSHR_TV = DISMNTSHR #                  DTKSHR_TV = DTKSHRh)                  ENCRYPSHR_TV = ENCRYPSHRt%                  EPC$SHR_TV = EPC_SHR #                  FDLSHR_TV = FDLSHRv'                  INIT$SHR_TV = INIT$SHRr#                  LBRSHR_TV = LBRSHR %                  MAILSHR_TV = MAILSHR '                  MOUNTSHR_TV = MOUNTSHRr#                  NCSSHR_TV = NCSSHR #                  PPLRTL_TV = PPLRTL 7                  PTD$SERVICES_SHR_TV = PTD$SERVICES_SHRH#                  SCRSHR_TV = SCRSHR 0                  SECURESHR_TV = SECURESHR_JACKET)                  SMBSRVSHR_TV = SMBSRVSHRt#                  SMGSHR_TV = SMGSHR %                  SORTSHR_TV = SORTSHRr#                  SPISHR_TV = SPISHR #                  TPUSHR_TV = TPUSHRc    I                                                                     4-109                 Programming Release Notesu.     4.29 Translated Image Support (Alpha Only)  &              BASRTL_TV = BASRTL_D56_TV(              BASRTL2_TV = BASRTL2_D53_TV*              BLAS1RTL_TV = BLAS1RTL_D53_TV&              COBRTL_TV = COBRTL_D56_TV&              DBLRTL_TV = DBLRTL_D56_TV&              FORRTL_TV = FORRTL_D56_TV&              LIBRTL_TV = LIBRTL_D56_TV(              LIBRTL2_TV = LIBRTL2_D56_TV&              MTHRTL_TV = MTHRTL_D53_TV&              PASRTL_TV = PASRTL_D56_TV&              PLIRTL_TV = PLIRTL_D56_TV(              VAXCRTL_TV = VAXCRTL_D56_TV*              VAXCRTLG_TV = VAXCRTLG_D56_TV  %              DBLMSGMGR = DBLMSGMGR_TVV              EDTSHR_TV = EDTSHR               TECO32 = TECO32_TVA!              TECOSHR = TECOSHR_TV               VMSRTL = VMSRTL_TVt                 DBLRTLMSG = DBL$MSG              PASMSG = PAS$MSGr              PLIMSG = PLI$MSG               RPGMSG = RPG$MSGh              SCNMSG = SCN$MSG                VAXCMSG = DECC$MSG   3     4.30 Translated Run-Time Libraries (Alpha Only)        V1.0  E           As part of the OpenVMS Alpha kit, Digital provides a set of (           translated run-time libraries.  D           Some of the routines in the VAX run-time libraries use theC           VAX D_floating data type for double-precision arithmetic.t  B           In the translated versions of these libraries, the Alpha@           D56 D_floating data type is used by default (where theB           VAX run-time library used D_floating). This provides theB           full precision of the 56-bit mantissa in VAX D_floating,E           yielding consistency of results at a cost in execution-timei           performance.      	     4-110  s  t      I                                                 Programming Release NoteseI                           4.30 Translated Run-Time Libraries (Alpha Only)X    @               For a handful of performance-critical math-relatedI               libraries, Digital also supplies versions of the translated G               run-time libraries that use the Alpha D53 D_floating dataoH               type for double-precision operations. For these libraries,I               the D53 forms are the default. The D53 forms provide betterrD               performance by sacrificing the low-order three bits of(               precision in the mantissa.  I               The following translated libraries are provided in D56 forms               only:                  o  BASRTLP                 o  COBRTL                  o  DBLRTL                  o  FORRTLV                 o  LIBRTLc                 o  LIBRTL2                 o  PASRTL                  o  PLIRTL                  o  VAXCRTL                 o  VAXCRTLG   I               The following translated libraries are provided in both D56 )               and D53 (the default) form:F                 o  BASRTL2                 o  BLAS1RTL                  o  MTHRTL(                 o  UVMTHRTL   >               Accessing the D56 Form of the Run-Time Libraries  H         V1.0  When you use the run-time libraries, the following happens               by default:h  B               o  For BASRTL2, translated BASIC images that use MATI                  functions on double-precision data invoke BASIC run-time =                  library routines that use the D53 data type.c  B               o  For BLAS1RTL, translated images that invoke BLAS$I                  functions with double-precision floating-point arguments 9                  get routines that use the D53 data type.   I                                                                     4-111  b  e           Programming Release Notes 3     4.30 Translated Run-Time Libraries (Alpha Only)     C           o  For MTHRTL, translated images that invoke MTH$ double--E              precision floating-point functions get routines that use               the D53 data type.l  C           o  For all others, the Alpha D56 floating-point data typee               is used by default.  B           Some users might need the full precision of D56 floating?           point. However, using the D56 routines imposes a very <           significant performance penalty. To access the D56@           routines, redefine the run-time library's logical nameC           to the D56 form, as shown in Table 4-11. The logical namehA           can be defined on a per-process or systemwide basis, asc$           appropriate for your site.  3           Table 4-11 Run-Time Library Logical Namesh  1           Library       Logical Name     D56 Name   7           BASRTL2       BASRTL2_TV       BASRTL2_D56_TV   8           BLAS1RTL      BLAS1RTL_TV      BLAS1RTL_D56_TV  6           MTHRTL        MTHRTL_TV        MTHRTL_D56_TV  $     4.30.1 Problems and Restrictions  @           The following note describes a problem with translated           callers.  C     4.30.1.1 CRF$FREE_VM and CRF$GET_VM: Translated Callers Problema  C     V1.0  Translated callers to CRF$FREE_VM and CRF$GET_VM will not.E           work properly. The translated callers are expecting VAX JSBaD           semantics, but instead, Alpha JSB semantics are present in&           the native code (naturally).  E           To work around this problem, the translated callers need tod#           use CALL instead of JSB.    7     4.31 Translated VAX C Run-Time Library (Alpha Only)b  D           The following sections contain release notes pertaining to0           the translated VAX C run-time library.  	     4-112o t  v      I                                                 Programming Release Notes I                       4.31 Translated VAX C Run-Time Library (Alpha Only)     (         4.31.1 Problems and Restrictions  I               This section describes known problems and restrictions withpH               the OpenVMS Alpha translated VAX C Run-Time Library (VAX C               RTL).3  (         4.31.1.1 Functional Restrictions  E         V1.0  The translated VAX C RTL is a translated version of thetA               OpenVMS VAX Version 5.4 VAX C RTL. All problems andtC               restrictions present in that release of the VAX C RTL H               exist unchanged in the translated VAX C RTL. The followingF               items are known restrictions in the functionality of the#               translated VAX C RTL:a  F               o  The fmod( ) function does not produce correct results                  for D_FLOAT.e  D               o  D_FLOAT programs that use the SIGFPE signal may notA                  catch all floating-point exceptions. TranslatingrE                  the program using /FLOAT=D56_FLOAT fixes most SIGFPEc                  problems.  F               o  The sbrk( ) function returns an address that does not:                  match the value returned from SYS$EXPREG.  H               o  D_FLOAT programs that use the HUGE_VAL constant or callH                  the math functions (which may return HUGE_VAL) may failB                  unless they are translated with /FLOAT=D56_FLOAT.  I               o  Under certain circumstances, some math functions (eitheroD                  D_FLOAT or G_FLOAT) may generate a high-performanceF                  arithmetic trap exception instead of setting errno to                   ERANGE or EDOM.  .         4.31.1.2 Interoperability Restrictions  H         V1.0  The following restrictions apply when the translated VAX C:               RTL interoperates with the native DEC C RTL:  H               o  The longjmp function cannot be used to transfer control                  from:  <                  -  A native routine to a translated routine  <                  -  A translated routine to a native routine  I                                                                     4-113e m  .           Programming Release Notesn7     4.31 Translated VAX C Run-Time Library (Alpha Only)e    B           o  Memory allocated by malloc, calloc, and so forth mustC              be freed in the same context. That is, if a translatedrB              routine allocates memory, the free call must occur inD              a translated routine. Allocating memory in a translatedB              routine and freeing it in a native routine results inE              corruption of the heap. Likewise, allocating memory in a C              native routine and freeing that memory in a translatedv,              routine also corrupts the heap.  D           o  Signal handlers established by the signal (and related)B              functions in translated routines are not invoked whenE              the signal is raised. Only native signal handlers can beh.              used to catch UNIX style signals.  B           o  The signals SIGEMT, SIGTRAP, SIGIOT and SIGFPE cannotB              be caught if those signals are raised by a translated              image.   A           o  The exec function can be used only to invoke similargB              images. That is, an exec function invoked in a native?              image cannot execute a translated image. Likewise,lB              an exec function invoked in a translated image cannot$              execute a native image.  A           o  An access violation occurs if vfork is executed in a E              native image to establish the context for a later system E              call and the system call is then invoked in a translated               image.h  @           o  File pointers and file descriptors cannot be shared<              between native and translated images. An accessA              violation or file corruption is likely to occur if a D              file is opened in a translated image and a native imageC              attempts to read or write using that file pointer. The E              same results occur if a file is opened in a native imageuC              and a translated image attempts to read or write usinge              that file pointer.a  C           Programs that perform any of these restricted actions mayiC           receive access violations or other exceptions. No testingiB           is performed to detect and prevent restricted operations            from being performed.       	     4-114l           I                                                 Programming Release NoteseI                           4.32 Translated VAX COBOL Programs (Alpha Only).    7         4.32 Translated VAX COBOL Programs (Alpha Only)            V1.5  G               The OpenVMS Alpha operating system supports the execution D               of translated VAX COBOL programs compiled with the VAX@               COBOL Version 5.0 compiler (or earlier compilers).  (         4.32.1 Problems and Restrictions  G         V1.5  Programs compiled with the VAX COBOL Version 5.1 compiler F               are not supported by the OpenVMS Alpha operating system.  !         4.33 VAX MACRO (VAX Only)h  H               The following sections contain release notes pertaining to               VAX MACRO.  4         4.33.1 Documentation Changes and Corrections  A               This section describes corrections to the VAX MACROl               documentation.  ?         4.33.1.1 VAX MACRO and Instruction Set Reference Manualv  @         V6.1  The following sections describe corrections to the=               VAX MACRO and Instruction Set Reference Manual.m  /               4.33.1.1.1 .ASCIZ Macro Directive   F         V6.1  Chapter 6 of the VAX MACRO and Instruction Set ReferenceG               Manual, Version 6.0 describes the .ASCIZ macro directive. G               In the example that illustrates the .ASCIZ directive, the22               following line of code is incorrect:  O                     .ASCIZ /A/<KEY>(FF\TEXT)/B/       ; 3 characters in string, D                                                   ;  4 bytes of data  "               Change this code to:  E                     .ASCIZ /A/<FF>/B/        ; 3 characters in string                    I                                                                     4-115n            Programming Release Notes      4.33 VAX MACRO (VAX Only)   *     4.33.1.1.2 General Register Addressing  B     V6.1  Chapter 8 of the VAX MACRO and Instruction Set Reference<           Manual, Version 6.0 describes the general registerE           addressing notations for the Macro assembler. In Table 8-5, D           the assembler notation for "Register deferred" (addressing-           mode 6) in Macro code is listed as:                 Rn.             Change to:                (Rn)   )           4.33.1.1.3 VAX Instruction CASE   B     V6.1  Chapter 9 of the VAX MACRO and Instruction Set Reference@           Manual, Version 6.0 describes the VAX instruction set.B           Where the description of the CASE instruction references>           symbol disp1[0] twice in the first note, the symbolsA           erroneously use the digit 1 (one) instead of the letter            "l".  1           Change both occurrences of disp1[0] to:                 displ[0]   )     4.34 X/Open Transport Interface (XTI)   A           The notes in this section describe the X/Open Transporto           Interface (XTI).  #     4.34.1 Changes and Enhancementsg  E     V6.2  OpenVMS Version 6.2 supports the X/Open Transport InterfacePB           (XTI) programming interface. The implementation conformsE           with the XPG4 X/Open CAE XO/CAE/91/600 (ISBN 1 872630 29 4) 9           X/Open Transport Interface (XTI) specification.v             Supported Transports  D           OpenVMS Version 6.2 supports the DECnet for OpenVMS (PhaseC           IV) and TCP/IP transports. See Section 4.34.2 for supportr           restrictions.   C           The transport names used in the t_open routine are 'dnet'RE           for DECnet for OpenVMS, and either 'ip/udp' or 'ip/tcp' forB           TCP/IP.   >           Other transports are available with other networking>           layered products. Consult individual layered productB           documentation for information about OpenVMS XTI support.  	     4-116     C      I                                                 Programming Release NotesTI                                     4.34 X/Open Transport Interface (XTI)L                   Architecture  H               XTI is supported by front end and back end code. Front endF               code provides access to the standard interface routines.E               Back end code provides the interface from the front end 8               code to the selected networking transport.  8               The supporting image files are as follows:  F                  XTI front end code           SYS$SHARE:XTI$XTILIB.EXE  E                  TCP/IP XTI back end code     SYS$SHARE:XTI$IPSHR.EXEI  G                  DECnet for OpenVMS XTI back  SYS$SHARE:XTI$DNETSHR.EXE                   end code   ?                  XTI C programming include    SYS$LIBRARY:XTI.H                   file   "               Linking Requirements  F               After compiling an XTI program, no additional qualifiers0               are required for linking with XTI.                 DocumentationR  D               Documentation about XTI is not included in the OpenVMSG               Version 6.2 release. You can order documentation directlydD               from X/Open Company Limited. If you have access to theI               Internet, you can get more information about X/Open CompanyHD               Limited (including their publications) by browsing the               following URL:  (                  http://www.xopen.co.uk/  @               You can also contact X/Open Company Limited at the"               following locations:                  o  USA: East Coast  '                  X/Open Company Limited )                  3141 Fairview Park Drive                   Falls Church                   VA 22042-4501                  U.S.A.M'                  Tel: +1 (703) 876 0044N'                  Fax: +1 (703) 876 0050T    I                                                                     4-117             Programming Release Notes )     4.34 X/Open Transport Interface (XTI)              o  USA: West Coast  #              X/Open Company LimitedG               1010 El Camino Real              Suite 380!              Menlo Park, CA 94025               U.S.A.U#              Tel: +1 (415) 323 7992 #              Fax: +1 (415) 323 8204              o  United Kingdom:  #              X/Open Company Limiteda              Apex PlazaO              Forbury Road_              Reading              Berks RG1 1AX              U.K. !              Tel: +44 1734 508311 !              Fax: +44 1734 500110_             o  Japan:_  #              X/Open Company Limited_$              Karufuru-Kanda Bldg, 9F!              1-2-1 Kanda Suda-choL              Chiyoda-KuV              Tokyo 101              Japan!              Tel: +81 3 3251 8321V!              Fax: +81 3 3251 83765  $     4.34.2 Problems and Restrictions  E     V6.2  The following restrictions apply to the OpenVMS Version 6.2M           XTI:  C           o  Nonblocking I/O is unsupported for DECnet for OpenVMS.   E              DECnet for OpenVMS (Phase IV) does not fit the model for D              nonblocking I/O. Attempts to open or switch an XTI fileB              descriptor to nonblocking I/O (O_NONBLOCK) will fail.  =           o  Connectionless I/O is unsupported for DECnet for0              OpenVMS.b  D              DECnet for OpenVMS (Phase IV) does not fit the model ofD              connectionless I/O. Therefore, only connection-oriented'              connections are supported.i    	     4-118i l  a      I                                                 Programming Release NotestI                                     4.34 X/Open Transport Interface (XTI)   .               o  Disabled ASTs cause problems.  A                  The XTI back end code uses ASTs for asynchronousvD                  delivery of events from the transports. If ASTs areI                  disabled (sys$setast(0)), the XTI back end code will notmD                  operate correctly until the ASTs are enabled again.  H               o  XTI file descriptors are not compatible with C Run-Time*                  Library file descriptors.  C               In addition, the 't_info' structure returned from theiD               t_open function reports any additional implementation-I               specific restrictions for the given transport. (See the XTIhF               documentation for information about the t_open command.)                                                                  I                                                                     4-119g e  w                    I                                                                         ArI         _________________________________________________________________   I                                              ISA Bus Support (Alpha Only)     D               Alpha platforms with Peripheral Component InterconnectD               (PCI) and Industry Standard Architecture (ISA) I/O busG               support use industry standard bus components to implementoI               the ISA bus interface. For this reason, the Alpha platforms5C               provide the same limited set of bus resources for ISA E               options that are available on a PC. These bus resources D               are IRQ lines, DMA channels, I/O ports, and ISA memory               buffers.  F               To allocate the bus resources to the various ISA devicesD               that require them, some kind of resource management isG               required. On ISA machines, the console provides an ISACFG C               command that allows a user to enter ISA configuration A               data into the system NVRAM. ISA bus support and bus G               configuration routines then extract the ISA configuration @               data from the console NVRAM. The console NVRAM ISAB               configuration data is referred to as the console ISA"               configuration table.  I               The console ISA configuration table contains resource usage G               information for each of the ISA devices in the system. An I               additional mechanism interprets the table entries and loadstG               the correct drivers for the devices that are present. The-G               OpenVMS SYS$MANAGER:ISA_CONFIG.DAT file stores driver andsI               device name information. A user can edit this file to entersE               ISA bus configuration information as well as driver and F               device names. OpenVMS ISA bus configuration routines useH               the console ISA configuration table as a source of ISA busH               resource usage and use the ISA_CONFIG.DAT file as a sourceF               of driver loading information, which includes driver and               device names.e          I                                                                       A-1A L  V            ISA Bus Support (Alpha Only)      E           This chapter describes ISA device configuration on machinesTD           that support ISA as an I/O bus, and it contains proceduresD           for configuring an ISA device. It also provides an example@           SYS$MANAGER:ISA_CONFIG.DAT file. For information about?           configuring ISA cards on an EISA bus, see OpenVMS AXPn,           Device Support: Developer's Guide.  %     A.1 OpenVMS ISA Bus ConfigurationA  A           The basic strategy for ISA bus configuration in OpenVMSs>           is to configure the devices found in the console ISAC           configuration table, and then configure the devices founds%           in the ISA_CONFIG.DAT file.a  ?           During booting, the I/O bus mapping routine INI$IOMAPw?           probes the console ISA configuration table and copiesr<           bus configuration information from the console ISA=           configuration table to the ISA ADP/Busarray. DuringeD           autoconfiguration, IOGEN$ISA_CONFIG walks the ADP/Busarray;           and configures the devices found in the Busarray.s=           IOGEN$ISA_CONFIG then opens file ISA_CONFIG.DAT andt3           configures the devices found in the file.l       A.2 Adding a Device   A           A machine fresh from the factory contains a console ISAoB           configuration table with entries for all of the built-inE           devices (keyboard, mouse, com1, com2, lpt1, and floppy) and E           entries for any factory installed ISA options. Each consoleT?           ISA configuration table entry lists the bus resourcese>           consumed by that device, as well as a 16 byte HANDLE?           (an ASCII character string), that is used to identify B           the device. OpenVMS will configure all factory installed>           and built-in devices using data from the console ISAD           configuration table. OpenVMS uses the HANDLE field of eachE           console ISA configuration table entry to associate a device/           and a driver.t  B           To configure an add-in ISA option device, you must first=           enter the IRQ used by the device in the console ISAh<           configuration table as described in Section A.2.1.  C              ________________________ Note ________________________e  =              This step is done prior to booting the operating @              system, so that the console knows that a particular       A-2d c  a      I                                              ISA Bus Support (Alpha Only)AI                                                       A.2 Adding a Devicei    E                 IRQ is in use by an ISA device. This will prevent the C                 console from assigning this IRQ to a PCI device. If E                 you do not perform this step, the system might becomeeD                 unresponsive ("hang") because two devices are trying$                 to use the same IRQ.  F                 ______________________________________________________  H               After you boot the operating system, you can load a driver3               for an ISA device in one of two ways:   *               o  Using ISA_CONFIG.DAT file                 o  Using SYSMAN.  F               See Section A.2.2 and Section A.2.3 for more information*               about both of these methods.  ?         A.2.1 Entering Interrupt Request Line (IRQ) Assignmentss  B               As mentioned in Section A.2, before you add optionalG               devices to an ISA bus, you must enter the IRQ used by thedE               device in the console ISA configuration table using the I               ISACFG command as described in this section. For additional H               information about the ISACFG command, see the AlphaStationD               400 Series User Information manual. The SRM console onD               your Alpha system assigns interrupt vectors to the PCID               devices plugged into the PCI option slots. The consoleB               automatically assigns an available interrupt requestF               line (IRQ) to each PCI device based on the configurationE               information stored by the console configuration utility                with the system.  G               To avoid a conflict where an IRQ that you want to use for I               an ISA device is already reserved for a PCI device, use the F               console configuration utility to reserve the IRQ for theH               ISA device. As noted in Section A.2, these conflicts mightI               cause the system to become unresponsive because two devicesd-               are trying to use the same IRQ.t  D               The commands you enter at the console prompt (>>>) are'               similar to the following:   E               >>> isacfg -mk -etyp 1 -enadev 1 -dev 0 -slot x -irq0 yh               >>> init  -               Note the following conventions:   I               o  x is the ISA option slot into which you insert the card.l  I                                                                       A-3o a  r            ISA Bus Support (Alpha Only)     A.2 Adding a Devicec    A              For more information about ISA option slots, see thee1              NODE=x description in Section A.2.2.   A           o  y is the IRQ that you are reserving for your device.e  %           Note the following as well:v  D           o  To verify that your command correctly reserved the IRQ,)              enter the following command:t                >>> isacfg -all  A              The system will display the entire data structure of A              ISA configuration information stored in the console, 1              including the IRQ you just reserved..  >           o  If you made an error, you can enter the following.              command to cancel the assignment:  *              >>> isacfg -rm -dev 0 -slot x  A           o  If you are using your system as a Universal Platform E              booting the OSF/1 operating system, you may have already C              made an entry using the console configuration utility.i@              You do not need to enter the information again. (IfD              you do, the system will display a message informing youB              that the slot is already reserved for an existing ISA              device.)   C              If you want to override the existing information entere#              the following command:d  E              >>> isacfg -mod -slot x -dev 0 -etyp 1 -enadev 1 -irq0 y   ,              Note the following conventions:  B              o  x is the ISA option slot into which you insert the                 card.   4              o  y is the IRQ assigned to the device.  B              Note that this specific command does not affect otherD              configuration information values stored for the device;;              the command modifies only the IRQ information.        A-4n e  a      I                                              ISA Bus Support (Alpha Only) I                                                       A.2 Adding a Device     >         A.2.2 Configuring a Device with an ISA_CONFIG.DAT File  H               If you are using the ISA_CONFIG.DAT file to configure yourI               device, you must first copy SYS$MANAGER:ISA_CONFIG.TEMPLATE 5               to SYS$SPECIFIC:[SYSMGR]ISA_CONFIG.DAT.   E               Then edit the ISA_CONFIG.DAT file to specify the device G               name, driver name, and other ISA bus resource usage (suchgF               as DMA channels, I/O ports, and memory buffers) for yourH               device. (This is analogous to editing config.sys on a PC.)G               You must enter the IRQ for your device in ISA_CONFIG.DAT, H               even though you already entered the IRQ in the console ISAB               configuration table (as described in Section A.2.1).  G               The main advantage of using ISA_CONFIG.DAT for add-in ISA G               option configurations is that the device is automatically I               configured. There is no need to write an ICBM or to use the F               SYSMAN IO CONNECT command, even for devices that OpenVMS               does not support.e  C               The ISA_CONFIG.TEMPLATE file is shipped in the systemtH               manager's directory with examples of configuration entriesF               for many ISA cards. The file is shipped with all entriesG               commented out. An example entry from the SYS$MANAGER:ISA_ 1               CONFIG.TEMPLATE file is as follows:E  J ;       Example 1: To indicate that the DE202 Card is plugged into slot 1,L ;       using IRQ 5, I/O ports 300-30F, and memory buffer D0000-DFFFF, enterD ;       the following into this SYS$SPECIFIC:[SYSMGR]ISA_CONFIG.DAT. ;  [ERA0]1/& NAME=ER2                 ; device name& DRIVER=SYS$ERDRIVER3     ; driver name9 NODE=14                  ; plugged into ISA Option slot 1p0 IRQ=55                   ; device is using irq 53 PORT=(300:f)6            ; 16 bytes starting at 300o6 MEM=(D0000:10000)7       ; 64 Kbytes starting at D0000A USER_PARAM = thinwire8   ; optional user parameter.  Available to'O                                  ; driver via IOC$NODE_DATA call using functionaC                                    code of IOC$K_ISA_USER_PARAM=18.i  G               1  The opening bracket indicates that the following linesMI                  contain ISA configuration information. This is basically I                  an entry delimiter. The text between the brackets is not #                  used for anything.X  I                                                                       A-5n n  n            ISA Bus Support (Alpha Only)     A.2 Adding a Device     E           2  The NAME=xx field allows specification of a standard twoiB              letter VMS device name. This two-letter string, alongB              with a controller letter and a unit number, is passed@              to the driver loading service as a standard OpenVMSE              device name. The two-letter device string is also copied$B              directly to the busarray$q_hw_id field in the ISA busE              array entry specified by the NODE field. This will cause E              the SYSMAN IO SHOW BUS command to display this device asf9              "Unknown ISA," instead of not displaying it.   C           3  The DRIVER=drivername specifies the driver that should B              be loaded for this device. This name is limited to 16?              ASCII characters, not including the implicit .EXE.e  A           4  The NODE=x field is used by OpenVMS to keep track ofd@              where ISA configuration information is being storedC              in the operating system data structures. Note that anyoB              correspondence with the actual location of the deviceB              in a physical bus slot is not needed. However, if youA              are configuring more than one ISA device in the ISA_OA              CONFIG.DAT file, you must use unique node numbers to D              avoid confusing the OpenVMS ISA bus configuration code.D              It might be helpful to label the ISA option slots 1, 2,D              3, 4 with a permanent felt-tip marker starting with theA              slot on the bottom (assuming an upright AlphaStation(D              400 Series system). Then use these slot numbers for theC              NODE=x portion of the ISA_CONFIG.DAT entries. When you B              enter the IRQ for your device at the console with theB              ISACFG command, the slot number that you specify mustA              match the node number specified in the entry for the2/              device in the ISA_CONFIG.DAT file.1  A           5  The IRQ=x field tells OpenVMS ISA configuration codei?              which IRQ is being used by the device. OpenVMS ISA A              configuration code derives the interrupt vector that A              will be used by the driver interrupt service routine7              from the ISA IRQ.  B              Even though you specified the IRQ at the console with?              the ISACFG command, you also must specify it here.1  E              On AlphaStation 200 and 400 Series systems, the built-in E              devices use many of the available ISA IRQ lines as shown               in Table A-1.       A-6  t  t      I                                              ISA Bus Support (Alpha Only) I                                                       A.2 Adding a DeviceO    /               Table A-1 Available ISA IRQ Lines)                 IRQ       Device  (               0         TIMER (built-in)  &               1         KBD (built-in)  )               2         Dual 8259 cascade.  '               3         COM2 (built-in)p  '               4         COM1 (built-in)S  <               5         Available for PCI or ISA option slot  )               6         FLOPPY (built-in)T  '               7         LPT1 (built-in)   B               8         Interval timer (not used on these systems)  B               9         SOUND (built in device on AlphaStation 200F                         only), available for PCI or ISA option slot on(                         AlphaStation 400  <               10        Available for PCI or ISA option slot  2               11        PCI NCR810 SCSI (built-in)  (               12        MOUSE (built-in)  F               13        DMA buffer chaining (not available outside PCI$                         /ISA bridge)  <               14        Available for PCI or ISA option slot  <               15        Available for PCI or ISA option slot  G                  Note that only IRQs 5, 9, 10, 14, and 15 are availabled>                  for add-in devices on AlphaStation 400 SeriesF                  systems. Only IRQs 5, 10, 14, and 15 are available onE                  AlphaStation 200 Series systems because the built-in D                  sound card uses IRQ 9. These are the only IRQ linesC                  available for all of the PCI and ISA option slots.   E                  You must be careful not to specify an IRQ that is in H                  use by another device because there is currently no IRQF                  sharing in OpenVMS. Only one driver interrupt serviceF                  routine can be connected to an IRQ. If you mistakenlyI                  overload an IRQ, only one driver (the one that is loaded >                  last) will ever get interrupts from that IRQ.  I                                                                       A-7                  ISA Bus Support (Alpha Only)     A.2 Adding a Device     A           6  The PORT=(x:y) field allows specification of the I/O E              port usage of the option. Up to 9 I/O port ranges can be               listed:  N        ;   PORT=(aa:b,cc:d,...)    ; where aa and cc are the ISA I/O port baseO        ;                           ; addresses for the device, and b,d indicatetH        ;                           ; the number of bytes to be reserved.L        ;                           ; Up to 9 separate I/O port ranges can be/        ;                           ; specified.a  D              If a driver needs to know which I/O ports its device isD              using, the driver can call the IOC$NODE_DATA routine toC              get the I/O port information. See Section A.3 for moreg9              information about the IOC$NODE_DATA routine.   @           7  The MEM=(x:y) field allows specification of the ISAB              memory buffers used by the ISA device. Up to 4 memory&              buffers can be specified:  O      ;   MEM=(ee:f,gg:h,...)     ; where ee and gg indicate the base ISA memory O      ;                           ; address for the device's on-card buffer, andpP      ;                           ; f,h indicate the size of the buffer in bytes.J      ;                           ; Up to 4 different memory buffer address;      ;                           ; ranges can be specified.   E           8  The USER_PARAM= field allows the user to create a stringhD              (72 bytes maximum) that is then available to the driverB              by way of the IOC$NODE_DATA routine. This is intended?              to be a general mechanism for passing user defined %              information to a driver.   D              This particular example did not specifiy a DMA channel,@              because this ISA card does not use DMA channels. To6              specify a DMA channel, use the following:  O           DMA=(j,k,...)                   ; where j and k are values (0-7) that O                                           ; specify which channel(s) of the DMAAN                                           ; controller this device is using to>                                           ; relay information.  B              You may specify up to 4 DMA channels for your device.  C           After you have edited the ISA_CONFIG.DAT file, reboot thetB           machine. Your device should be automatically configured,*           and the driver should be loaded.       A-8     n      I                                              ISA Bus Support (Alpha Only)nI                                                       A.2 Adding a Devicee    3         A.2.3 Configuring an ISA Device with SYSMANo  E               To manually configure your ISA device, you can also use E               the System Management (SYSMAN) utility instead of using H               ISA_CONFIG.DAT file. The following example shows how to toH               configure your device using the SYSMAN IO CONNECT command:  E               To use the SYSMAN utility, enter the following command:h                 $ MCR SYSMAN  C               At the SYSMAN> prompt, enter the following IO CONNECTl               command:  H               SYSMAN> IO CONNECT devname /ADAPTER=x /DRIVER=drivername -7               /NODE=slot /CSR=baseaddress /VECTOR=irq*4l  H               The arguments and qualifiers to the IO CONNECT command are               as follows:,                 devnameDD               Specifies the OpenVMS device name of your device. ThisG               should be specified as a standard OpenVMS device name-a 2 I               letter device code, a controller letter, and a unit number.r                 /ADAPTER=xF               Specifies the OpenVMS software adapter number of the ISAF               bus. Before you enter the IO CONNECT command, you shouldC               display the I/O adapters that are known to OpenVMS byR-               entering the following command:   !               SYSMAN> IO SHOW BUSi  H               The I/O adapter numbers are the "TR#" from the IO SHOW BUSH               DISPLAY command. The following example shows sample outputH               from the SYSMAN IO SHOW BUS command on an AlphaStation 400               Series system:  !               SYSMAN> io show bus   @               %SYSMAN-I-OUTPUT, command execution on node JIMMYJ        I                                                                       A-9  i               ISA Bus Support (Alpha Only)     A.2 Adding a Devicei    D           _Bus__________Node_TR#__Name____________Base CSR__________C             PCI           48   2    PCI/SCSI       FFFFFFFF822DC000sG                 XBUS          0    4    Mouse          FFFFFFFF820DC000 G                 XBUS          1    4    Keyboard       FFFFFFFF820DC000 G                 XBUS          2    4    Serial Port    FFFFFFFF820DC000 G                 XBUS          3    4    Serial Port    FFFFFFFF820DC000AG                 XBUS          4    4    Parallel Port  FFFFFFFF820DC000eG                 XBUS          5    4    Floppy         FFFFFFFF820DC000oE               ISA           1    3    Lance NI Adapt FFFFFFFF820DC000IE               ISA           2    3    Sound Adapter  FFFFFFFF820DC000o           SYSMAN>   C           In this display, you can see that the ISA bus adapter has @           TR# 3. Because you are plugging a device in to the ISAE           bus, you should specify /ADAPTER=3 in the SYSMAN IO CONNECTtD           command. This will cause your driver data structures to be6           associated with the ISA bus data structures.  C           Note that if your system has no devices plugged in to therC           ISA bus, then there will be nothing displayed for the ISAtE           bus when you issue the SYSMAN IO SHOW BUS command. You willeB           not see any entries for ISA bus devices. This is a knownD           deficiency in the SYSMAN IO SHOW BUS command. However, youD           will always see the XBUS devices in the SYSMAN IO SHOW BUSB           display. The TR# for the ISA bus will always be one lessE           than the TR# for the XBUS. For the AlphaStation 200 and 400 D           Series systems, the ISA adapter number will be 3, as shown"           in the previous example.             /DRIVER=drivernameD           The DRIVER=drivername qualifier specifies the file name of*           the driver that is to be loaded.             /NODE=slotA           The /NODE=slot qualifier identifies the OpenVMS ISA bus >           array entry that will be used to store configurationD           information about your ISA device. Note that this need notD           have any correspondence with the physical ISA slot cutoutsD           on the back of the machine. It is necessary, however, thatA           you do not configure more than one device into the sameoC           slot. In the previous example SYSMAN IO SHOW BUS display,vD           slots 1 and 2 are used by the Lance NI Adapt and the SoundA           Adapter. You must not use either of these slot numbers. D           It is also necessary that the slot argument match the slot@           number that you specified when you entered the console       A-10 e  y      I                                              ISA Bus Support (Alpha Only)>I                                                       A.2 Adding a Deviceu    F               ISACFG command to reserve the IRQ. As mentioned earlier,F               it is suggested that you label the ISA bus slots and useF               those slot numbers in the console ISACFG command, in theI               ISA_CONFIG.DAT file (if you decide to configure your device F               using this file), and in the /NODE=slot qualifier in theH               SYSMAN IO CONNECT command (if you decide to configure your               device this way).c                 /CSR=baseaddressE               The driver loading service that is called by the SYSMANu>               IO CONNECT command requires the /CSR=baseaddressD               input qualifier. The driver loading service copies theD               baseaddress from the /CSR=baseaddress qualifier to theG               IDB$Q_CSR field in the IDB. The Base CSR in the SYSMAN IOaG               SHOW BUS display for the XBUS devices is the base virtualhC               address of ISA I/O space. The base address of ISA I/OiF               space is generally a useful value for ISA device driversG               and should be the value specified in the /CSR=baseaddressc               argument.h  B               Note that if you code your driver using the IOC$MAP_C               IO routine to map your device register space, you may @               not need the baseaddress from the /CSR=baseaddressE               qualifier. However, you still must supply something for G               the /CSR=baseaddress qualifier, because it is required byeE               the driver loading service. If you are using IOC$MAP_IOCG               and you are not depending on any base address value beingpI               passed to you by the driver loading service, you should sayS'               /CSR=0 for this argument.                  /VECTOR=irq*4iI               The /VECTOR=irq*4 qualifier specifies to the driver loading B               service the software interrupt vector in use by yourH               device. Your driver interrupt service routine is connectedG               to the software interrupt vector and will be invoked when G               your device generates a hardware interrupt. The irq valuenF               in this qualifier must be the same as the IRQ value thatG               you specified when you entered the console ISACFG commandf%               to reserve the ISA irq.n            I                                                                      A-11  d               ISA Bus Support (Alpha Only)&     A.3 ISA Bus Device Driver Routines    &     A.3 ISA Bus Device Driver Routines  A           This section describes how to use the IOC$NODE_DATA andnE           IOC$NODE_FUNCTION routines for a device driver using an ISAu           bus.  E           The bus support routine IOC$NODE_DATA is called by a driver A           to get bus slot/platform-specific information. The usesAD           and capabilities of this routine vary from bus to bus. TheD           bus support routine IOC$NODE_FUNCTION is called to performB           bus slot-specific actions on behalf of a driver, such as-           enabling interrupts for a bus slot.C  D           This section contains the prototypes for the IOC$NODE_DATAD           and IOC$NODE_FUNCTION routines. For more information aboutC           using these routines, see the OpenVMS AXP Device Support:c           Reference manual.)  @           The formats of the IOC$NODE_DATA and IOC$NODE_FUNCTION"           routines are as follows:  N           int ioc$node_data (CRB  *crb, int  function_code, void *user_buffer)  ?           int ioc$node_function (CRB  *crb, int  function_code)   B           Both of these routines use the CRB$L_NODE field from theE           CRB to find the ADP and ISA bus array entry for the device. C           The supported function codes for IOC$NODE_DATA on the ISAl           bus are as follows:e  ;           IOC$K_EISA_IRQ          Return IRQ used by device   C           IOC$K_EISA_DMA_CHAN     Return DMA channel used by device   A           IOC$K_EISA_MEM_CONFIG   Return memory buffer(s) used byO(                                   device  C           IOC$K_EISA_IO_PORT      Return I/O port(s) used by device   A           On the ISA bus, IOC$NODE_DATA uses the CRB$L_NODE field B           from the CRB to find the ADP and the ISA bus array entryD           for the device. The ISA bus array entry contains a pointer@           to a data structure called an ISA_CFG_DATA (defined by?           isacfgdef.h from sys$lib_c.tlb) to find the requested C           information. The contents of the ISA_CFG_DATA are derived C           from two places. If you are configuring your device using >           the ISA_CONFIG.DAT file, the information returned byB           IOC$NODE_DATA is derived from the entry that you made inE           ISA_CONFIG.DAT for your device. If you are configuring your B           device using the SYSMAN IO CONNECT command, there should       A-12 D         I                                              ISA Bus Support (Alpha Only)iI                                        A.3 ISA Bus Device Driver Routinest    F               not be an entry in the ISA_CONFIG.DAT file. In this caseG               the information returned by IOC$NODE_DATA is derived from H               the entry for your device in the console ISA configurationG               table, which you created when you used the console ISACFG 9               command to reserve the IRQ for your device.c  G               When calling IOC$NODE_DATA, you must supply a user buffer D               large enough to contain the information. The data sizeD               returned for each of the previously mentioned function"               codes is as follows:                                                                      I                                                                      A-13a h  o            ISA Bus Support (Alpha Only)&     A.3 ISA Bus Device Driver Routines      ?           IOC$K_EISA_IRQ          The IRQ used by the device is ;                                   returned as a 32 bit int.   A           IOC$K_EISA_DMA_CHAN     The DMA channel number assigned >                                   to the device is returned as@                                   a 32 bit int. If more than oneB                                   DMA channel is specified in ISA_>                                   CONFIG.DAT, then each one isA                                   returned as an int (an array ofaD                                   ints should be declared to receive3                                   the information).u  ?           IOC$K_EISA_MEM_CONFIG   The memory buffer used by thea@                                   device is returned in an arrayA                                   of two consecutive 32 bit ints. B                                   The first array element contains@                                   the ISA bus base memory buffer?                                   address, and the second array D                                   element contains the memory bufferC                                   size (in bytes). If more than one D                                   memory buffer is specified in ISA_B                                   CONFIG.DAT, each one is returnedA                                   in an array of ints. You shouldeB                                   declare an array of ints that isB                                   big enough to contain all of theC                                   memory buffer information used by .                                   your device.  B           IOC$K_EISA_IO_PORT      The I/O port information used byB                                   the device is returned as 32 bitB                                   integers. The low 16 bits of theE                                   32 bit integer contain the base I/OlE                                   port, and the upper 16 bits containCE                                   the number of consecutive I/O ports1A                                   from the base I/O port. If morep@                                   than one I/O port is specified@                                   in ISA_CONFIG.DAT, each one is?                                   returned as a 32 bit int. YousA                                   should declare an array of intsrD                                   large enough to contain all of theC                                   I/O port information used by yourn)                                   device.I         A-14    s      I                                              ISA Bus Support (Alpha Only)nI                                        A.3 ISA Bus Device Driver RoutinesQ    G               The supported function codes for IOC$NODE_FUNCTION on theg!               ISA bus as follows:   G               IOC$K_ENABLE_INTR       Enables hardware device interrupt H                                       in the ISA interrupt control logic  H               IOC$K_DISABLE_INTR      Disables hardware device interruptH                                       in the ISA interrupt control logic  C               IOC$NODE_FUNCTION also uses the CRB$L_NODE field fromtE               the CRB to find the ADP and ISA bus array entry for therB               device. IOC$NODE_FUNCTION then finds the IRQ used byF               the device and either enables (if called with the IOC$K_H               ENABLE_INTR function code) or disables (if called with theH               IOC$K_DISABLE_INTR function code) the IRQ line used by the               device.   ,         A.4 Determining an Available ISA IRQ  E               To determine which IRQs are available for use by an ISA3F               device, you must check a few things. The console utilityG               will have IRQs reserved for system board devices, for ISA I               Option slot devices that have been entered by the user, andb;               for any PCI Options that have been installed.;  F               The file SYS$MANAGER:ISA_CONFIG.DAT may contain resourceF               information for ISA option devices that the console does               not know about.   D               In an AlphaStation 200 Series, the only available IRQsF               for ISA and PCI Option devices are 5, 10, 14, 15. In theG               AlphaStation 400 Series, the Audio option is not present,hF               so the available IRQ list is 5, 9, 10, 14, 15. Note thatH               thare are more option slots available than there are IRQs.  G               To determine if any of these IRQs are already consumed by G               devices previously installed in the system (either at thetE               factory or by the user), you can follow this procedure:i  H               1. Issue the console command ISACFG -ALL. This will outputI                  a list of all the ISA devices (and their resources) that H                  the console knows about, including system board devicesG                  and any option slot devices that the user has entered. I                  Search the output from this command to see if any of the H                  IRQs from the available list are consumed by previously#                  installed devices.   I                                                                      A-15n Y               ISA Bus Support (Alpha Only)(     A.4 Determining an Available ISA IRQ    D           2. PCI Option slot devices report their interrupts throughD              ISA IRQs also. The console is responsible for assigningA              these IRQs. It does so in a linear fashion, startingnB              with the lowest numbered IRQ that is not specified asB              reserved in the console ISA configuration table. EachB              consecutive PCI slot is assigned the lowest availableA              IRQ until all PCI options are assigned or we run outrD              of IRQs. If there are no ISA Option slot device entriesD              in the console ISA configuration table, the PCI OptionsE              would be assigned IRQs in order from the available list.iB              If there is an entry for an ISA option slot device inB              the table, specifying IRQ 9, then any PCI Option slotE              devices would be assigned IRQs from the list 5,10,14,15. /              (Audio is a good example of this.)   @              Use the console SHOW CONFIG command to list all theA              PCI devices. Note that the Intel SIO Bridge does notdD              require an interrupt, and that the NCR 53C810 SCSI chipD              is hardwired to IRQ 11. Any other PCI devices that show@              up will consume IRQs from the available list in the)              manner previously described.B  6           3. Boot the system and look through the file>              SYS$MANAGER:ISA_CONFIG.DAT for valid entries (notB              commented out). They will be specifying an IRQ. (NoteA              that there should already be an entry reserving thisTA              IRQ in the console ISA configuration table if properiC              procedure is followed). If you find an IRQ listed that B              is not already specified in the console data, make an@              entry using the console ISACFG command as described%              earlier in this chapter.   B              Any remaining IRQs are available for use by a new ISAC              Option card. Please note that you must reserve the IRQdD              using the console to ensure that an IRQ is reserved for              your device.                        A-16 /  I      I                                              ISA Bus Support (Alpha Only)FI                                                       A.5 TroubleshootingF             A.5 TroubleshootingB  C               This section contains information that might help you D               to solve some common problems that you might encounterD               while configuring your ISA device. If you have troubleD               adding a new device to the system, you can check a fewD               things. More than likely, the device you are trying toG               add is conflicting with an existing device's ISA Resource E               assignments. For possible resource conflicts, check theuG               output from the console's ISACFG -ALL command and comparetH               with the contents of your SYS$MANAGER:ISA_CONFIG.DAT file.  I               Possible types of conflicts and suggested solutions include                the following:                 ISA IRQ conflicts F               As mentioned in Section A.4, on AlphaStation 200 and 400G               Series systems there are more option slots than there areh               IRQs.A  :               ISA I/O port, DMA channel, and memory buffer               conflictsiA               Choose a new resource for your board, or adjust thed@               existing boards resource so that the needed one is               available.  &               Slot numbering conflictsG               ISA does not have slot numbers. OpenVMS requires some waytC               to keep track of devices in the ISA bus and uses slotlE               number as a convenient method. If there are slot numberED               conflicts in the ISA_CONFIG.DAT file, the OpenVMS codeI               will overwrite the first driver's resource information with=F               the last driver's information and fail to load the first               driver.   @               You must also ensure that there are no slot numberG               conflicts between the console data and the ISA_CONFIG.DATe               data.   H               Valid ISA slot numbers for the AlphaStation Series 200/400!               are 1, 2, 3, and 4.n  I               If you made changes to your SYS$MANAGER:ISA_CONFIG.DAT filexF               and can no longer boot, you should boot conversationallyA               using the following command. (Remember to re-enablesE               autoconfiguration after the problem has been resolved.)h  I                                                                      A-17e r  t            ISA Bus Support (Alpha Only)     A.5 Troubleshooting     +           >>> boot -flags 0,1 <boot_device>   ,           SYSBOOT> SET NOAUTOCONFIGURATION 1           SYSBOOT> CONTINUE   D           This will boot OpenVMS without configuring any of your I/OC           devices. You can then edit the SYS$MANAGER:ISA_CONFIG.DATe'           file to correct any problems.   C           If you made changes to the console data and are preventedoD           from booting, use the console ISACFG command to remove the            changes that you made.  B     A.6 System Board Resources for AlphaStation 200 and 400 Series         Systems   D           System board resources for AlphaStation 200 and 400 Series!           systems are as follows:c  )           COM1:     IRQ=4, I/O port=3F8:8T  )           COM2:     IRQ=3, I/O port=2F8:8   )           LPT1:     IRQ=7, I/O Port=378:8e  5           FDC:      IRQ=6, I/O port=3F0:8, DMA chan=2=  )           Mouse:    IRQ=C, I/O port=60,64D  )           Keyboard: IRQ=1, I/O port=60,64   "           TOY       I/O port=70,71           Clock:  )           PCI       IRQ=B, I/O port=26,27d           NCR810           SCSI:d  B           Sound:    (This is a system board device on AlphaStation$                     200 Series only)                          IRQ=9,t-                        I/O Ports=388:4,530:8, %                        DMA chan=(0,1)o             Timer     IRQ=0            /Counter:i       A-18 d  I                                              ISA Bus Support (Alpha Only)hI    A.6 System Board Resources for AlphaStation 200 and 400 Series Systems                  INTEL F               SIO PCI      IRQ=2 (Cascade IRQ for the dual 8259 on the'               /ISA         bridge chip)u?               Bridge       IRQ=D (used for DMA Buffer Chaining,n9               inter-       unconnnected on these systems) I               rupt         IRQ=8 (used for interval timer, unconnected oni)               logic:       these systems)i  C                            DMA=4 (used by the DMA controller as thed(                            cascade line)  &         A.7 Sample ISA_CONFIG.DAT File  H               This section contains a sample ISA_CONFIG.DAT file that is/               similar to the file you can edit.v                 ; 1               ;       I S A _ C O N F I G . D A Th               ; P               ;       This file informs the OpenVMS Alpha operating system which;               ;       devices are connected to the ISA bus.                ;s=               ;       Note: Do NOT make changes in this file. L               ;       To add option devices to this file you must first copyJ               ;       this template file (SYS$MANAGER:ISA_CONFIG.TEMPLATE)P               ;       to SYS$SYSROOT:[SYSMGR]ISA_CONFIG.DAT.  Then edit the fileH               ;       SYS$SYSROOT:[SYSMGR]ISA_CONFIG.DAT to add devices.               ; (               ;   Contents of this file:(               ;   ----------------------A               ;       o Description of configuration command sets                ;iM               ;       o Example configuration command sets for supported ISA O$               ;         option cards               ;tL               ;       o System board resources for AlphaStation 200 and 400 &               ;         series systems               ;                ;e               ; 0               ;   Conventions used in this file:0               ;   ------------------------------K               ;       o Characters following a semi-colon (;) are comments.                ;tE               ;       o All numbers must be specified in hexadecimal.w  I                                                                      A-19b e        ISA Bus Support (Alpha Only)"     A.7 Sample ISA_CONFIG.DAT File             ;hJ           ;       o You must separate records in the file by using square K           ;         brackets around each ISA device that is specified (for c%           ;         example, [xyzn]).l           ;u'           ;       o Spaces are ignored.A           ; 6           ;       o Note the following about keywords:           ;nM           ;         - Keywords can be in any order, *except* in the following O           ;           instance: the NAME keyword must precede the NODE keyword IP           ;           or the SYSMAN IO SHOW BUS command will not include the ISA-           ;           devices in the display.            ;B;           ;         - Each keyword must be on its own line.h           ; P           ;         - All keywords required for a device must be included before4           ;           the next record [xyzn] begins.           ;o8           ;   Description of Configuration Command Sets:8           ;   ------------------------------------------           ; M           ;       Specify the following information for each ISA device. NoteiK           ;       that the NAME, DRIVER, NODE, and IRQ fields are required.d           ; J           ;       Note that fields that are not used must be omitted. For N           ;       example, if the device does not use a DMA channel, you must )           ;       omit the DMA parameter.            ;pL           ;       NAME=xx                 ; where xx is the 2-letter device K           ;                               ; code, (for example: ER for the e2           ;                               ; DE202)           ;EL           ;       DRIVER=driver_name      ; The name of the driver stored in@           ;                               ; SYS$LOADABLE_IMAGES.N           ;                               ; For example: SYS$ERDRIVER for the L           ;                               ; DE202, and SYS$IRDRIVER for the D           ;                               ; Proteon Token Ring card.           ; J           ;       IRQ=i                   ; where i is a value (0-F) that O           ;                               ; specifies which ISA IRQ the device  F           ;                               ; uses to report interrupts.           ; K           ;       NODE=n                  ; where n is the ISA option slot  N           ;                               ; number the device is plugged into.           ; O           ;       DMA=(j,k,...)           ; where j and k are values (0-7) that O           ;                               ; specify which channel(s) of the DMAv         A-20 sI                                              ISA Bus Support (Alpha Only) I                                            A.7 Sample ISA_CONFIG.DAT File   P               ;                               ; controller this device is using E               ;                               ; to relay information.s/               ;                               ; G               ;                               ; Note the comma between  N               ;                               ; indicators and the parenthesesE               ;                               ; that indicates a listi>               ;                               ; of parameters./               ;                               ;hL               ;                               ; Up to 4 DMA channels can be :               ;                               ; specified.               ;rO               ;       PORT=(aa:b,cc:d,...)    ; where aa and cc are the ISA I/O L               ;                               ; port base addresses for the H               ;                               ; device, and b,d indicateI               ;                               ; the number of bytes to be O               ;                               ; reserved. Up to 9 separate I/O  M               ;                               ; port ranges can be specified.n               ; M               ;       MEM=(ee:f,gg:h,...)     ; where ee and gg indicate the TP               ;                               ; base ISA memory address for the L               ;                               ; device's on-card buffer, andM               ;                               ; f,h indicate the size of the s@               ;                               ; buffer in bytes.P               ;                               ; Up to 4 different memory buffer P               ;                               ; address ranges can be specified.               ; M               ;       FLAGS = n               ; Currently, bit 1 is the only C<               ;                               ; flag in use.M               ;                               ; It indicates that the device  L               ;                               ; beging configured is a SCSI K               ;                               ; adapter. Therefore, if the  O               ;                               ; adapter is a SCSI  device, set  C               ;                               ; this bit to 1. This L               ;                               ; will allow IOGEN$SCSI_CONFIGM               ;                               ; (which probes for devices on  L               ;                               ; the SCSI bus) to locate the 8               ;                               ; devices.               ;iL               ;       USER_PARAM = text       ; This parameter is dedicated O               ;                               ; solely for driver writer use.  cN               :                               ; A pointer to a copy of text isN               ;                               ; passed back in the user_bufferI               ;                               ; parameter from a call to  O               ;                               ; IOC$NODE_DATA using a function EL               ;                               ; code of IOC$K_ISA_USER_PARAMO               ;                               ; (note that the text is limited  <               ;                               ; to 72 chars)               ;                ;                ; [               ;       ************************** IMPORTANT ********************************                ; M               ;       o For all of the following examples, be sure to verify nH               ;         that the switches and jumpers on the card being K               ;         inserted are set to match the specified parameters iN               ;         BEFORE you remove the comment characters (;) from this               ;         file.t  I                                                                      A-21         ISA Bus Support (Alpha Only)"     A.7 Sample ISA_CONFIG.DAT File             ;SN           ;       o Be sure that there are no conflicting resource assignmentsK           ;         between devices (including the built-in devices on the tC           :         system board and the PCI option slot device IRQe!           ;         assignments.)o           ; F           ;       o Be sure to copy SYS$MANAGER:ISA_CONFIG.TEMPLATE toM           ;         SYS$SYSROOT:[SYSMGR]ISA_CONFIG.DAT before making changes.            ;sN           ;         A list of resources assigned to system boards follows the            ;         examples.            ;aO           ;       *************************************************************            ;a           ; O           ;   Example Configuration Command Sets for Supported ISA Option Cards O           ;   -----------------------------------------------------------------            ;bG           ;       Following are examples of configuration command sets  M           ;       necessary to automatically configure option cards that are u.           ;       not shipped with the system.           ;IM           ;       Example 1: To indicate that the DE202 Card is plugged into  L           ;       slot 1, using IRQ 5, I/O ports 300-30F, and memory buffer B           ;       D0000-DFFFF, enter the following into this file:           ;o           ;       [ERA0]           ;       NAME=ER %           ;       DRIVER=SYS$ERDRIVERaJ           ;       NODE=1                  ; plugged into ISA Option slot 1           ;       IRQ=5QD           ;       PORT=(300:f)            ; 16 bytes starting at 300F           ;       MEM=(D0000:10000)       ; 64Kbytes starting at D0000N           ;       USER_PARAM = thinwire   ; optional user parameter is passed C           ;                               ; directly back to driver            ;IN           ;       Example 2: To configure the DigiBoard PC/8 card, remove the J           ;       comment characters (;)  from the following. (Be sure to J           ;       verify that the switches are set to match the indicated F           :       resources, or change the resource lists to match theG           ;       switches.)  Note that SYS$YSDRIVER expects the Mastern=           ;       Status register address to be listed first.d           ;1           ;       [TTA0]           ;       NAME=TTi%           ;       DRIVER=SYS$YSDRIVER          A-22    m      I                                              ISA Bus Support (Alpha Only) I                                            A.7 Sample ISA_CONFIG.DAT File                  ;       IRQ=5lL             ;       NODE=2                  ; plugged into ISA Option slot 2P             ;       PORT=(390:8,398:8,3a0:8,3a8:8,3b0:8,3b8:8,3c0:8,3c8:8,3d0:8)
             ; O             ;       Note that this configures only a single port on the card.  lM             ;       The remaining 7 ports each need to be connected manually o0             ;       using the following command:
             ;tL             ;       $ MCR SYSMAN IO CONNECT/NOADAP/DRIVER=SYS$YSDRIVER TTAx:0             ;       ; where x is the unit number
             ;d
             ;uN             ;       Example 3: To configure a Microsoft Sound card, remove theN             ;       comment characters (;) from the following.  These commandsL             ;       specify the card in ISA Bus Option slot 3, running with N             ;       IRQ 9, using DMA channels 0 and 1, and I/O Port addresses $             ;       388-38B,530-537.
             ;t             ;       [AUA0]             ;        NAME=AU             ;        NODE=3 )             ;        DRIVER=SYS$MSBDRIVERI             ;        IRQ=9             ;        DMA=(0,1)'             ;        PORT=(388:4,530:8) 
             ;t
             ; M             ;       Example 4: To configure the Proteon Token Ring card usingiJ             ;       IRQ A, DMA channel 7, I/O Ports A20-A3F, STP media andL             ;       speed of 16 Mbits remove the comment characters from the'             ;       following commands.t
             ;A             ;       [IRA0]             ;        NAME=IR             ;        NODE=4o(             ;        DRIVER=SYS$IRDRIVER             ;        IRQ=A             ;        DMA=7"             ;        PORT=(A20:20)(             ;        USER_PARAM="STP,16"
             ;a
             ;sK             ;   System Board Resources for AlphaStation 200 and 400 Series               ;   SystemsrO             ;   ---------------------------------------------------------------r    I                                                                      A-23                  ISA Bus Support (Alpha Only)"     A.7 Sample ISA_CONFIG.DAT File               ;l           ;    COM1:(           ;        IRQ=4, I/O port=3F8:8           ;s           ;    COM2:(           ;        IRQ=3, I/O port=2F8:8           ;I           ;    LPT1:(           ;        IRQ=7, I/O Port=378:8           ;            ;    FDC: 4           ;        IRQ=6, I/O port=3F0:8, DMA chan=2           ;t           ;    Mouse:a(           ;        IRQ=C, I/O port=60,64           ;            ;    Keyboard:(           ;        IRQ=1, I/O port=60,64           ;u           ;    TOY Clock:t!           ;        I/O port=70,71I           ;e           ;    PCI NCR810 SCSI: (           ;        IRQ=B, I/O port=26,27           ;s           ; P           ;    Sound: (This is a system board device on AlphaStation 200 Series E           ;        only) IRQ=9, I/O Ports=388:4,530:8, DMA chan=(0,1)h           ;v           ;    Timer/Counter:n           ;        IRQ=0           ;e8           ;    INTEL SIO PCI/ISA Bridge interrupt logic:K           ;        IRQ=2 (Cascade IRQ for the dual 8259 on the bridge chip) N           ;        IRQ=D (used for DMA Buffer Chaining, unconnnected on these "           ;               systems)P           ;        IRQ=8 (used for interval timer, unconnected on these systems)I           ;        DMA=4 (used by the DMA controller as the cascade line)i           ;                    A-24 .  u                    I                                                                         B I         _________________________________________________________________   I                             Remedial Kits Included in OpenVMS Version 6.2     D               This appendix lists remedial kits that are included inF               OpenVMS Version 6.2. Appendix C describes other remedialI               kits that are not included in Version 6.2, but that will be ,               available in a future release.  C               Digital updates existing kits and creates new kits asrD               necessary. Contact your Digital support representativeA               for the latest information about new remedial kits.R  G               The following sections list the remedial kits included in:H               Version 6.2 of the OpenVMS VAX and OpenVMS Alpha operatingH               systems. For some older kits that were originally assignedC               a CSCPAT number, that number is shown in parentheses.I  I               Kit names are constructed from the following information in                this order:   6               o  Platform name: VAX or AXP (for Alpha)  H               o  Facility name, abbreviated to 4 characters if necessary  E               o  Number of the kit for this facility for this versionm                 o  Version number   H               For example, VAXBACK02_061 is the second remedial kit thatG               has been created for the Backup utility in Version 6.1 ofD               OpenVMS VAX.  =         B.1 Remedial Kits Included in OpenVMS VAX Version 6.2   H               The following remedial kits are included in Version 6.2 of/               the OpenVMS VAX operating system:                     VAXACRT01_061                  VAXACRT02_061                  VAXAUDI01_061                  VAXAUDI03_061                  VAXBACK02_060  I                                                                       B-1t f         1     Remedial Kits Included in OpenVMS Version 6.2 9     B.1 Remedial Kits Included in OpenVMS VAX Version 6.2                   VAXBACK02_061              VAXBACK03_U2055              VAXBACK4_U2055               VAXBOOT01_061              VAXCDU01_060s              VAXCDU01_U2055               VAXCLIU01_061              VAXCLIU02_U2055              VAXCMAR01_061              VAXCOPY01_061              VAXCXXL01_061              VAXDDTM01_U2055              VAXDDTM02_061              VAXDEBU02_061              VAXDECW01_060              VAXDECW02_060              VAXDECW11_U2055              VAXDUP01_060e              VAXDWXT01_061              VAXF11C02_061              VAXF11X03_061              VAXINIT03_061              VAXLAT02_U2055               VAXLMF01_061t              VAXLOAD01_061              VAXLOGI04_061              VAXMAIL02_060              VAXMAIL03_061              VAXMAIL05_061              VAXMAIL06_U2055              VAXMONT01_061              VAXMOTF03_011              VAXMOUN01_061              VAXNETA01_061              VAXPHV_02_061              VAXPHV_03_060              VAXPHV_09_U2055              VAXQMAN03_061              VAXRMS01_061-              VAXSCSI02_061              VAXSCSI03_061              VAXSHAD02_060              VAXSORT01_061         B-2     b      I                             Remedial Kits Included in OpenVMS Version 6.2 I                     B.1 Remedial Kits Included in OpenVMS VAX Version 6.2                       VAXSYS01_061                   VAXSYS02_061                   VAXSYS04_061n                  VAXSYS09_U2055                   VAXSYS10_U2055h                  VAXSYS12_U2055r                  VAXSYS12_061,                  VAXSYS13_061                   VAXSYSL01_061                   VAXSYSL01_2H455                   VAXSYSL09_U1055                   VAXSYSL11_U1055                   VAXSYSL17_U2055                   VAXTTDR09_U2055                  VAXVERI02_061                                                              I                                                                       B-3            1     Remedial Kits Included in OpenVMS Version 6.2 ;     B.2 Remedial Kits Included in OpenVMS Alpha Version 6.2     ;     B.2 Remedial Kits Included in OpenVMS Alpha Version 6.2e  D           The following remedial kits are included in Version 6.2 of-           the OpenVMS Alpha operating system:i                AXPACRT03_061              AXPACRT04_061              AXPAMAC02_U1061              AXPBOOT03_U1061              AXPBOOT04_U1061              AXPCMAR01_U1061              AXPCMAR01_061              AXPCOB01_U1061d              AXPCOPY01_061              AXPCXXL01_061              AXPDEBU02_061              AXPDPLI01_061              AXPDRIV07_061              AXPDRIV08_061              AXPDWXT01_015              AXPDWXT01_061              AXPF11C02_061              AXPINIT01_061              AXPLAN03_061-              AXPLAN04_061               AXPLAT01_061               AXPLAT03_061f              AXPLINK02_061              AXPLOGI01_061              AXPMTAA01_061              AXPOPDR01_015              AXPOPDR04_061              AXPQMAN01_015              AXPQMAN03_061              AXPSCSI01_061              AXPSHAD04_061              AXPSORT01_061              AXPSYS07_061               AXPSYS10_061               AXPSYS11_061I              AXPTTDR01_061              AXPTTDR02_015              AXPVERI02_061           B-4                          I                                                                         C I         _________________________________________________________________   I                         Remedial Kits Not Included in OpenVMS Version 6.2     I               This appendix describes remedial kits that are not included H               in OpenVMS Version 6.2. Appendix B lists all remedial kitsG               that are included in Version 6.2 of the OpenVMS operating-               system.   C               Digital updates existing kits and creates new kits as D               necessary. Contact your Digital support representativeA               for the latest information about new remedial kits.S  I               Kit names are constructed from the following information in                this order:s  6               o  Platform name: VAX or AXP (for Alpha)  H               o  Facility name, abbreviated to 4 characters if necessary  E               o  Number of the kit for this facility for this version                  o  Version number   H               For example, AXPTRAC01_061 is the first remedial kit to beF               created for the Trace facility in Version 6.1 of OpenVMS               Alpha.  A         C.1 Remedial Kits Not Included in OpenVMS VAX Version 6.2   D               The following sections describe remedial kits that areF               not included in Version 6.2 of the OpenVMS VAX operatingD               system. These kits will likely be included in the next.               release of the operating system.  7         C.1.1 Local Area VMScluster Kit (VAXLAVC01_061)   F               When this remedial kit is applied, nodes in a Local AreaH               VMScluster environment no longer invoke a CLUEXIT bugcheckF               in mixed Ethernet/FDDI environments where hello messagesH               are being produced (that is, in outdated bridge firmware).                 I                                                                       C-1            5     Remedial Kits Not Included in OpenVMS Version 6.2s?     C.2 Remedial Kits Not Included in OpenVMS Alpha Version 6.2e    ?     C.2 Remedial Kits Not Included in OpenVMS Alpha Version 6.2   @           The following sections describe remedial kits that areD           not included in Version 6.2 of the OpenVMS Alpha operating@           system. These kits will likely be included in the next*           release of the operating system.  (     C.2.1 Trace Facility (AXPTRAC01_061)  A           This kit corrects a problem where traceback information C           reported after a program failure was either incomplete or            incorrect.                                                                         C-2                          I                                                                         DeI         _________________________________________________________________p  I                           Layered Product Support for OpenVMS Version 6.2     B               This appendix provides preliminary information aboutG               layered products that are compatible with OpenVMS Version                6.2.  H               Tables in this appendix list layered products that supportC               or will soon support OpenVMS Version 6.2. The maximumeC               version of the operating system on which each layered I               product has been qualified is shown in the Operating System D               Support (Qualified) column. Most layered products thatE               supported OpenVMS Version 6.1 will also support OpenVMS                Version 6.2.  H               The tables also indicate the DECnet environments supportedI               by each layered product. Support categories are abbreviatedOH               in the tables as Ph. IV (DECnet Phase IV), Syn (DECnet/OSI:               synonyms), and Full (DECnet/OSI full names).  E               Most layered products that worked in an OpenVMS Version F               6.1 environment running DECnet for OpenVMS (DECnet PhaseF               IV) will also work in an OpenVMS Version 6.2 environmentH               running DECnet for OpenVMS. Many of these layered productsB               will also work in a DECnet/OSI synonyms environment.  I               Regardless of the DECnet environment, the following layered E               products require these new versions for installation one"               OpenVMS Version 6.2:  ;               o  DEC X.500 Directory Services, Version 2.0A *                  (Administration Facility)  I               o  DEC X.500 Directory Services, Version 2.0A (Starter Kit)   D               o  DEC X.500 Directory Services, Version 2.0A (Server)  8               o  DECdfs for OpenVMS Systems, Version 2.1  F               o  POLYCENTER Capacity Planner for OpenVMS, Version 3.0A  D               o  StorageWorks RAID Software for OpenVMS, Version 2.2  I                                                                       D-1            3     Layered Product Support for OpenVMS Version 6.2       B           Table D-1 lists layered products compatible with OpenVMSA           VAX Version 6.2 that will be available at the same timetD           as or shortly following the release of OpenVMS VAX Version           6.2.  B           Table D-2 lists layered products compatible with OpenVMS>           Alpha Version 6.2 that will be available at the sameC           time as or shortly following the release of OpenVMS Alpha-           Version 6.2.  B           Table D-3 lists layered products compatible with OpenVMS@           VAX Version 6.2 that are planned for release after May           1995.m  B           Table D-4 lists layered products compatible with OpenVMSB           Alpha Version 6.2 that are planned for release after May           1995.   A           Information in these tables is continually evolving andIB           is subject to change. As additional results from ongoingC           qualification tests become available, updated information B           will be included on the OpenVMS Software Product Library=           kits (CD-ROM consolidations). Digital now regularlyoE           compiles an OpenVMS Layered Product Public Rollout Schedule0>           for both VAX and Alpha systems. For the most currentD           information about OpenVMS layered products, please contact.           your Digital support representative.                                         D-2            I                           Layered Product Support for OpenVMS Version 6.2g      F         Table D-1 Digital Layered Products Compatible with OpenVMS VAXI         __________Version_6.2____________________________________________w  6                                              OperatingG                                              System      DECnet SupportwI         Product and Version                  Support    _________________tI         _____________________________________(Qualified)Ph._IV_Syn___FullT  G         ACMS Desktop, V2.0                   6.1        Yes    Yes   No   G         ACMS Desktop/Japanese, V2.0          6.1        Yes    Yes   NoB  H         ACMS for OpenVMS (Development),      6.1        Yes    N/A   N/A         V4.0  H         ACMS for OpenVMS (Remote), V4.0      6.1        Yes    N/A   N/A  H         ACMS for OpenVMS (Run-Time), V4.0    6.1        Yes    N/A   N/A  G         ALL-IN-1 DESKtop Server for VMS,     6.1        Yes    Yes   No          V1.2  G         ALL-IN-1 Integrated Office System    6.1        Yes    Yes   No $         Server for VMS (MUPA), V3.0B  G         ALL-IN-1 Integrated Office System    6.1        Yes    Yes   No #         Server for VMS (MUPA), V3.1   G         ALL-IN-1 IOS TeamLinks Connection    6.1        Yes    Yes   No #         V2.1 for OpenVMS VAX, V3.0C   G         ALL-IN-1 IOS TeamLinks Connection    6.1        Yes    Yes   Nos"         V2.1 for OpenVMS VAX, V3.1  G         ALL-IN-1 Office Server Options for   6.1        Yes    Yes   No *         OpenVMS AXP and OpenVMS VAX, V3.0B  G         ALL-IN-1 Office Server Options for   6.1        Yes    Yes   No )         OpenVMS AXP and OpenVMS VAX, V3.1   G         ALL-IN-1 Personal Assistant for      6.1        Yes    Yes   No          OpenVMS, V1.1U  G         ALL-IN-1/ Franais Integrated        6.1        Yes    Yes   No )         Office System Server for OpenVMS, 
         V3.0B   G         ALL-IN-1/ Franais Integrated        6.1        Yes    Yes   No )         Office System Server for OpenVMS,h         V3.1  I                                                  (continued on next page)3  I                                                                       D-3a t         3     Layered Product Support for OpenVMS Version 6.2       >     Table D-1 (Cont.) Digital Layered Products Compatible withE     __________________OpenVMS_VAX_Version_6.2________________________   2                                          OperatingD                                          System       DECnet SupportE     Product and Version                  Support    _________________uE     _____________________________________(Qualified)Ph._IV_Syn___Full   C     ALL-IN-1/British Integrated Office   6.1        Yes    Yes   No-$     System Server for OpenVMS, V3.0B  C     ALL-IN-1/Dansk Integrated Office     6.1        Yes    Yes   No $     System Server for OpenVMS, V3.0B  C     ALL-IN-1/Dansk Integrated Office     6.1        Yes    Yes   No #     System Server for OpenVMS, V3.1   C     ALL-IN-1/Dansk Office Server         6.1        Yes    Yes   No8$     Options for OpenVMS AXP and VAX,	     V3.0B   C     ALL-IN-1/Dansk Office Server         6.1        Yes    Yes   No $     Options for OpenVMS AXP and VAX,     V3.1  C     ALL-IN-1/Deutsch Integrated Office   6.1        Yes    Yes   Not$     System Server for OpenVMS, V3.0B  C     ALL-IN-1/Deutsch Integrated Office   6.1        Yes    Yes   No #     System Server for OpenVMS, V3.1   C     ALL-IN-1/Deutsch Office Server       6.1        Yes    Yes   No $     Options for OpenVMS AXP and VAX,	     V3.0Bs  C     ALL-IN-1/Deutsch Office Server       6.1        Yes    Yes   No $     Options for OpenVMS AXP and VAX,     V3.1  C     ALL-IN-1/Espaol Integrated Office   6.1        Yes    Yes   No $     System Server for OpenVMS, V3.0B  C     ALL-IN-1/Espaol Integrated Office   6.1        Yes    Yes   Nor#     System Server for OpenVMS, V3.1(  C     ALL-IN-1/Espaol Office Server       6.1        Yes    Yes   NoI$     Options for OpenVMS AXP and VAX,	     V3.0Bo  E                                              (continued on next page)s       D-4r    e      I                           Layered Product Support for OpenVMS Version 6.2o      B         Table D-1 (Cont.) Digital Layered Products Compatible withI         __________________OpenVMS_VAX_Version_6.2________________________   6                                              OperatingG                                              System      DECnet SupportiI         Product and Version                  Support    _________________iI         _____________________________________(Qualified)Ph._IV_Syn___FullA  G         ALL-IN-1/Espaol Office Server       6.1        Yes    Yes   Nod(         Options for OpenVMS AXP and VAX,         V3.1  G         ALL-IN-1/Franais Office Server      6.1        Yes    Yes   No (         Options for OpenVMS AXP and VAX,
         V3.0Bu  G         ALL-IN-1/Franais Office Server      6.1        Yes    Yes   Noa(         Options for OpenVMS AXP and VAX,         V3.1  G         ALL-IN-1/Hebrew Integrated Office    6.1        Yes    Yes   Not'         System Server for OpenVMS, V3.0g  G         ALL-IN-1/Italiano Integrated Office  6.1        Yes    Yes   No (         System Server for OpenVMS, V3.0B  G         ALL-IN-1/Italiano Integrated Office  6.1        Yes    Yes   Not'         System Server for OpenVMS, V3.1   G         ALL-IN-1/Italiano Office Server      6.1        Yes    Yes   No (         Options for OpenVMS AXP and VAX,
         V3.0Br  G         ALL-IN-1/Italiano Office Server      6.1        Yes    Yes   Not(         Options for OpenVMS AXP and VAX,         V3.1  G         ALL-IN-1/Japanese (English           6.1        Yes    Yes   No          Secondary), V3.0Br  G         ALL-IN-1/Japanese Integrated Office  6.1        Yes    Yes   No (         System Server for OpenVMS, V3.0B  G         ALL-IN-1/Nederlands Integrated       6.1        Yes    Yes   No )         Office System Server for OpenVMS,A
         V3.0Bt  I                                                  (continued on next page)   I                                                                       D-5X K  0      3     Layered Product Support for OpenVMS Version 6.2       >     Table D-1 (Cont.) Digital Layered Products Compatible withE     __________________OpenVMS_VAX_Version_6.2________________________   2                                          OperatingD                                          System       DECnet SupportE     Product and Version                  Support    _________________ E     _____________________________________(Qualified)Ph._IV_Syn___Full1  C     ALL-IN-1/Nederlands Integrated       6.1        Yes    Yes   NoV%     Office System Server for OpenVMS,0     V3.1  C     ALL-IN-1/Nederlands Office Server    6.1        Yes    Yes   No2$     Options for OpenVMS AXP and VAX,	     V3.0BV  C     ALL-IN-1/Nederlands Office Server    6.1        Yes    Yes   No $     Options for OpenVMS AXP and VAX,     V3.1  C     ALL-IN-1/Norsk Integrated Office     6.1        Yes    Yes   No $     System Server for OpenVMS, V3.0B  C     ALL-IN-1/Norsk Integrated Office     6.1        Yes    Yes   No #     System Server for OpenVMS, V3.1X  C     ALL-IN-1/Norsk Office Server         6.1        Yes    Yes   No $     Options for OpenVMS AXP and VAX,	     V3.0B0  C     ALL-IN-1/Norsk Office Server         6.1        Yes    Yes   No $     Options for OpenVMS AXP and VAX,     V3.1  C     ALL-IN-1/Portuges Integrated        6.1        Yes    Yes   NoC%     Office System Server for OpenVMS, 	     V3.0BV  C     ALL-IN-1/Portuges Integrated        6.1        Yes    Yes   Noe%     Office System Server for OpenVMS,      V3.1  C     ALL-IN-1/Portuges Office Server     6.1        Yes    Yes   No $     Options for OpenVMS AXP and VAX,	     V3.0B   E                                              (continued on next page)0       D-6            I                           Layered Product Support for OpenVMS Version 6.21      B         Table D-1 (Cont.) Digital Layered Products Compatible withI         __________________OpenVMS_VAX_Version_6.2________________________   6                                              OperatingG                                              System      DECnet Support I         Product and Version                  Support    _________________ I         _____________________________________(Qualified)Ph._IV_Syn___Fulle  G         ALL-IN-1/Portuges Office Server     6.1        Yes    Yes   Noi(         Options for OpenVMS AXP and VAX,         V3.1  G         ALL-IN-1/Suomi Integrated Office     6.1        Yes    Yes   Nok(         System Server for OpenVMS, V3.0B  G         ALL-IN-1/Suomi Integrated Office     6.1        Yes    Yes   No '         System Server for OpenVMS, V3.1M  G         ALL-IN-1/Suomi Office Server         6.1        Yes    Yes   No (         Options for OpenVMS AXP and VAX,
         V3.0B   G         ALL-IN-1/Suomi Office Server         6.1        Yes    Yes   No1(         Options for OpenVMS AXP and VAX,         V3.1  G         ALL-IN-1/Svenska Integrated Office   6.1        Yes    Yes   NoA(         System Server for OpenVMS, V3.0B  G         ALL-IN-1/Svenska Integrated Office   6.1        Yes    Yes   No0'         System Server for OpenVMS, V3.1   G         ALL-IN-1/Svenska Office Server       6.1        Yes    Yes   No1(         Options for OpenVMS AXP and VAX,
         V3.0B   G         ALL-IN-1/Svenska Office Server       6.1        Yes    Yes   NoN(         Options for OpenVMS AXP and VAX,         V3.1  G         BASEstar Classic for OpenVMS VAX     6.1        Yes    Yes   No          (Development), V3.3A  G         BASEstar Classic for OpenVMS VAX     6.1        Yes    Yes   No          (Development), V3.4   G         BASEstar Classic for OpenVMS VAX     6.1        Yes    Yes   No          (Run-Time), V3.3  I                                                  (continued on next page)_  I                                                                       D-7o n  d      3     Layered Product Support for OpenVMS Version 6.2       >     Table D-1 (Cont.) Digital Layered Products Compatible withE     __________________OpenVMS_VAX_Version_6.2________________________a  2                                          OperatingD                                          System       DECnet SupportE     Product and Version                  Support    _________________ E     _____________________________________(Qualified)Ph._IV_Syn___Fulln  C     BASEstar Classic for OpenVMS VAX     6.1        Yes    Yes   Nof     (Run-Time), V3.4  D     BASEstar Open Client for OpenVMS     6.1        N/A    N/A   N/A     VAX, V2.0A  D     BASEstar Open Server for OpenVMS     6.1        N/A    N/A   N/A     VAX (Development), V2.0A  D     BASEstar Open Server for OpenVMS     6.1        N/A    N/A   N/A     VAX (Run-Time), V2.0A   C     CDD/Administrator for OpenVMS        6.1        Yes    No    No      Systems, V1.2   C     CDD/Administrator for OpenVMS        6.1        Yes    Yes   No      Systems, V1.3   C     CDD/Repository/Japanese for OpenVMS  6.1        Yes    No    No 
     VAX, V5.1b  C     Consolidated DEChub Firmware Kit,    6.1        Yes    No    Not     V3.1  7     DEC @a Glance for VMS (Client Run-   6.1        Yesy     Time Option), V1.0  7     DEC @a Glance for VMS (Development   6.1        Yes      Option), V1.0S  7     DEC @a Glance for VMS (Server Run-   6.1        Yese     Time Option), V1.0  C     DEC Ada for OpenVMS VAX Systems,     6.1        Yes    Yes   Nok	     V3.0A   C     DEC Ada for OpenVMS VAX Systems,     6.2        Yes    Yes   No      V3.2  C     DEC Ada Professional Development     6.1        Yes    Yes   No.#     Option for OpenVMS VAX Systems, 	     V3.0A   E                                              (continued on next page)K       D-8l d         I                           Layered Product Support for OpenVMS Version 6.2       B         Table D-1 (Cont.) Digital Layered Products Compatible withI         __________________OpenVMS_VAX_Version_6.2________________________   6                                              OperatingG                                              System      DECnet Support I         Product and Version                  Support    _________________AI         _____________________________________(Qualified)Ph._IV_Syn___Fullo  G         DEC Ada Professional Development     6.2        Yes    Yes   No '         Option for OpenVMS VAX Systems,          V3.2  H         DEC C for OpenVMS VAX Systems, V4.0  6.2        N/A    N/A   N/A  H         DEC C for OpenVMS VAX Systems, V5.0  6.2        N/A    N/A   N/A  H         DEC C++ for OpenVMS VAX (Compiler),  6.1        N/A    N/A   N/A         V1.2  H         DEC C++ for OpenVMS VAX (Compiler),  6.2        N/A    N/A   N/A         V5.0  H         DEC C++ for OpenVMS VAX (VAX         6.1        N/A    N/A   N/A         Debugger), V1.2M  H         DEC C++ for OpenVMS VAX (VAX         6.2        N/A    N/A   N/A         Debugger), V5.0p  H         DEC C/C++ Run-Time Components for    6.1        N/A    N/A   N/A         OpenVMS VAX, V1.2e  H         DEC C/C++ Run-Time Components for    6.2        N/A    N/A   N/A         OpenVMS VAX, V5.0a  H         DEC C/Japanese for OpenVMS VAX,      6.1        N/A    N/A   N/A         V4.0  G         DEC Code Management System (CMS)     6.1        Yes    No    No %         for OpenVMS VAX Systems, V3.6a  G         DEC Code Management System (CMS)     6.2        Yes    No    No %         for OpenVMS VAX Systems, V3.7   G         DEC COMMserver for OpenVMS, V2.0     6.1        Yes    No    No(  G         DEC COMMserver for OpenVMS, V3.0     6.1        Yes    No    No   G         DEC Computer Integrated Telephony    6.1        Yes    No    No &         Application Interface for VMS,
         V3.0An  I                                                  (continued on next page)e  I                                                                       D-9            3     Layered Product Support for OpenVMS Version 6.2       >     Table D-1 (Cont.) Digital Layered Products Compatible withE     __________________OpenVMS_VAX_Version_6.2________________________i  2                                          OperatingD                                          System       DECnet SupportE     Product and Version                  Support    _________________iE     _____________________________________(Qualified)Ph._IV_Syn___Fully  7     DEC Data Distributor for OpenVMS     6.1        Yes 
     VAX, V6.1t  D     DEC DATATRIEVE for OpenVMS VAX,      6.1        Yes    Yes   Yes     V7.0  C     DEC DATATRIEVE/Hangul for OpenVMS    6.1        Yes    Yes   Nor
     VAX, V6.1   C     DEC DATATRIEVE/Japanese for OpenVMS  6.1        Yes    Yes   No 
     VAX, V6.1   C     DEC DB Integrator Gateway for DBMS   6.1        Yes    Yes   Nol     for OpenVMS VAX, V1.0s  7     DEC DB Integrator Gateway for DSM,   6.1        Yesl	     V1.0Bb  7     DEC DB Integrator Gateway for EDA    6.1        Yes      /SQL, V3.1  7     DEC DB Integrator V1.0B for OpenVMS  6.1        Yes      VAX (Development), V4.0i  7     DEC DB Integrator V1.0B for OpenVMS  6.1        Yesb     VAX (Interactive), V4.0e  7     DEC DB Integrator V1.0B for OpenVMS  6.1        Yes      VAX (Run-Time), V4.0  7     DEC DBA Workcenter for OpenVMS VAX,  6.1        YesV     V1.0  D     DEC Distributed Queuing Service for  6.2        Yes    Yes   Yes     OpenVMS, V1.3a  D     DEC Fortran for OpenVMS Systems,     6.2        Yes    Yes   Yes     V6.3  D     DEC GKS for OpenVMS, V6.0            6.1        Yes    Yes   Yes  D     DEC GKS for OpenVMS, V6.1            6.1        Yes    Yes   Yes  E                                              (continued on next page)t       D-10 e  a      I                           Layered Product Support for OpenVMS Version 6.2P      B         Table D-1 (Cont.) Digital Layered Products Compatible withI         __________________OpenVMS_VAX_Version_6.2________________________0  6                                              OperatingG                                              System      DECnet SupportaI         Product and Version                  Support    _________________ I         _____________________________________(Qualified)Ph._IV_Syn___Fullc  H         DEC GKS for OpenVMS (Run-Time),      6.1        Yes    Yes   Yes         V6.0  H         DEC GKS for OpenVMS (Run-Time),      6.1        Yes    Yes   Yes         V6.1  G         DEC Language-Sensitive Editor        6.1        Yes    No    No )         /Source Code Analyzer for OpenVMS          VAX, V4.2w  G         DEC Language-Sensitive Editor        6.2        Yes    No    Not)         /Source Code Analyzer for OpenVMS_         VAX, V4.3V  G         DEC MAILworks/Japanese for OpenVMS,  6.1        Yes    Yes   No          V1.2  G         DEC Module Management System (MMS)   6.1        Yes    No    No %         for OpenVMS VAX Systems, V2.7)  G         DEC Module Management System (MMS)   6.2        Yes    No    NoS%         for OpenVMS VAX Systems, V3.0N  H         DEC OPS5 for OpenVMS, V4.0A          6.1        Yes    Yes   Yes  H         DEC OPS5/Japanese for OpenVMS,       6.1        Yes    Yes   Yes
         V4.0A   H         DEC Optical Storage Desktop          6.1        N/A    N/A   N/A)         Software (OSDS) for OpenVMS, V3.2B  H         DEC Optical Storage Desktop          6.1        N/A    N/A   N/A)         Software (OSDS) for OpenVMS, V3.3   H         DEC Optical Storage Management       6.1        N/A    N/A   N/A)         Software (OSMS) for OpenVMS, V3.2   H         DEC Optical Storage Management       6.1        N/A    N/A   N/A)         Software (OSMS) for OpenVMS, V3.31  H         DEC Pascal for OpenVMS, V5.1         6.1        Yes    Yes   Yes  I                                                  (continued on next page)   I                                                                      D-11  -  1      3     Layered Product Support for OpenVMS Version 6.2       >     Table D-1 (Cont.) Digital Layered Products Compatible withE     __________________OpenVMS_VAX_Version_6.2________________________   2                                          OperatingD                                          System       DECnet SupportE     Product and Version                  Support    _________________ E     _____________________________________(Qualified)Ph._IV_Syn___Full   C     DEC Performance and Coverage         6.1        Yes    No    No %     Analyzer for OpenVMS VAX Systems,      V4.2  C     DEC Performance and Coverage         6.2        Yes    No    No_%     Analyzer for OpenVMS VAX Systems,_     V4.3  D     DEC PHIGS for OpenVMS VAX, V3.0      6.1        Yes    Yes   Yes  D     DEC PHIGS for OpenVMS VAX, V3.1      6.2        Yes    N/A   N/A  D     DEC PHIGS for OpenVMS VAX (Run-      6.1        Yes    Yes   Yes     Time), V3.0_  D     DEC PHIGS for OpenVMS VAX (Run-      6.2        Yes    N/A   N/A     Time), V3.1   D     DEC PHIGS/Japanese for VMS (Run-     6.1        Yes    Yes   Yes     Time), V3.0A  D     DEC PHIGS/Japanese for VMS VAX,      6.1        Yes    Yes   Yes	     V3.0A   C     DEC Rdb/Hangul for OpenVMS/Hangul    6.1        Yes    Yes   Noy     VAX (Multi-Version), V6.0   C     DEC Rdb/Hangul for OpenVMS/Hangul    6.1        Yes    Yes   No      VAX (Standard), V6.0  C     DEC Rdb/Hanyu for OpenVMS/Hanyu VAX  6.1        Yes    Yes   No      (Multi-Version), V6.0   C     DEC Rdb/Hanyu for OpenVMS/Hanyu VAX  6.1        Yes    Yes   Nog     (Standard), V6.0  C     DEC Rdb/Hanzi for OpenVMS/Hanzi VAX  6.1        Yes    Yes   NoN     (Multi-Version), V6.0e  C     DEC Rdb/Hanzi for OpenVMS/Hanzi VAX  6.1        Yes    Yes   No      (Standard), V6.0  E                                              (continued on next page)X       D-12    0      I                           Layered Product Support for OpenVMS Version 6.2p      B         Table D-1 (Cont.) Digital Layered Products Compatible withI         __________________OpenVMS_VAX_Version_6.2________________________B  6                                              OperatingG                                              System      DECnet SupportI         Product and Version                  Support    _________________ I         _____________________________________(Qualified)Ph._IV_Syn___Fullo  G         DEC Rdb/Japanese for OpenVMS VAX     6.1        Yes    Yes   No          (Interactive), V6.0p  G         DEC Rdb/Japanese for OpenVMS VAX     6.1        Yes    Yes   Nos         (Run-Time), V6.0  G         DEC Rdb/Japanese for OpenVMS         6.1        Yes    Yes   No )         /Japanese VAX (Full Development),a         V6.0  G         DEC SecurityGate for OpenVMS, V1.1A  6.1        Yes    No    Nor  G         DEC SERdb for Security-Enhanced      6.1        Yes    Yes   No_         VMS, V6.0_  G         DEC SNA 3270 Application Services    6.1        Yes    Yes   Nof         (Development), V1.1e  G         DEC SNA 3270 Application Services    6.1        Yes    Yes   No          (Run-Time), V1.1  G         DEC SNA Domain Gateway, V2.0         6.1        Yes    Yes   NoX  G         DEC SoftPC for OpenVMS, V4.0         6.1        Yes    No    No6  H         DEC TCP/IP Services for OpenVMS,     6.1        N/A    N/A   N/A         V3.3  H         DEC TCP/IP/Japanese Services for     6.1        N/A    N/A   N/A         OpenVMS/Japanese, V3.2  G         DEC Test Manager for OpenVMS VAX     6.1        Yes    No    NoN         Systems, V3.5e  G         DEC Test Manager for OpenVMS VAX     6.2        Yes    No    No          Systems, V3.6   G         DEC VOICEmail for OpenVMS VAX,       6.1        Yes    No    NoS
         V1.3A   G         DEC VTX Version OpenVMS VAX, V6.2    6.1        Yes    No    No3  H         DEC X.500 Directory Administration   6.1        N/A    Yes   Yes&         Facility for OpenVMS VAX, V2.0  I                                                  (continued on next page)   I                                                                      D-13n r  d      3     Layered Product Support for OpenVMS Version 6.2       >     Table D-1 (Cont.) Digital Layered Products Compatible withE     __________________OpenVMS_VAX_Version_6.2________________________   2                                          OperatingD                                          System       DECnet SupportE     Product and Version                  Support    _________________ E     _____________________________________(Qualified)Ph._IV_Syn___Fulli  D     DEC X.500 Directory Administration   6.2        N/A    Yes   Yes#     Facility for OpenVMS VAX, V2.0A   D     DEC X.500 Directory Server for       6.1        N/A    Yes   Yes     OpenVMS VAX, V2.0   D     DEC X.500 Directory Server for       6.2        N/A    Yes   Yes     OpenVMS VAX, V2.0A  D     DEC X.500 Directory Service Starter  6.1        N/A    Yes   Yes     Kit for OpenVMS VAX, V2.0   D     DEC X.500 Directory Service Starter  6.2        N/A    Yes   Yes     Kit for OpenVMS VAX, V2.0A  C     DEC/EDI for OpenVMS VAX, V2.0        6.1        Yes    Yes   Noi  C     DEC/EDI for OpenVMS VAX, V2.1        6.2        Yes    Yes   Noi  D     DECADMIRE, V2.1A                     6.1        N/A    N/A   N/A  D     DECADMIRE w/Hebrew Support for ACMS  6.1        N/A    N/A   N/A%     /COBOL/DECforms for OpenVMS, V1.2   D     DECADMIRE w/Hebrew Support for       6.1        N/A    N/A   N/A$     COBOL/DECforms for OpenVMS, V1.2  D     DECADMIRE/Japanese for OpenVMS,      6.1        N/A    N/A   N/A     V2.0  C     DECdfs for OpenVMS Systems, V2.0     6.2        Yes    Yes   NoN  C     DECdfs for OpenVMS Systems, V2.1     6.2        Yes    Yes   No   D     DECforms for OpenVMS VAX             6.1        N/A    N/A   N/A     (Development), V2.0   D     DECforms for OpenVMS VAX             6.1        N/A    N/A   N/A     (Development), V2.1   D     DECforms for OpenVMS VAX (Run-       6.1        N/A    N/A   N/A     Time), V2.0L  D     DECforms for OpenVMS VAX (Run-       6.1        N/A    N/A   N/A     Time), V2.1X  E                                              (continued on next page)o       D-14    e      I                           Layered Product Support for OpenVMS Version 6.2o      B         Table D-1 (Cont.) Digital Layered Products Compatible withI         __________________OpenVMS_VAX_Version_6.2_________________________  6                                              OperatingG                                              System      DECnet SupporteI         Product and Version                  Support    _________________tI         _____________________________________(Qualified)Ph._IV_Syn___Fullf  H         DECforms/Hangul for OpenVMS VAX      6.1        N/A    N/A   N/A         (Development), V2.0   H         DECforms/Hangul for OpenVMS VAX      6.1        N/A    N/A   N/A         (Run-Time), V2.0  H         DECforms/Hanyu for OpenVMS VAX       6.1        N/A    N/A   N/A         (Development), V2.0i  H         DECforms/Hanyu for OpenVMS VAX       6.1        N/A    N/A   N/A         (Run-Time), V2.0  H         DECforms/Hanzi for OpenVMS VAX       6.1        N/A    N/A   N/A         (Development), V2.00  H         DECforms/Hanzi for OpenVMS VAX       6.1        N/A    N/A   N/A         (Run-Time), V2.0  H         DECforms/Japanese, V2.0              6.1        N/A    N/A   N/A  H         DECforms/Japanese (Run-Time), V2.0   6.1        N/A    N/A   N/A  H         DECimage Application Services for    6.1        N/A    N/A   N/A         VMS, V3.2e  ;         DECimage Express, V2.2A              6.1        Yes   ;         DECimage Express, V2.3               6.1        YesX  G         DECintact, V2.1                      6.1        Yes    No    No6  G         DECintact (Remote), V2.1             6.1        Yes    No    No   G         DECintact (Run-Time), V2.1           6.1        Yes    No    Nos  G         DECmessageQ for OpenVMS VAX, V2.1B   6.1        Yes    No    NoS  G         DECmessageQ for OpenVMS VAX, V3.0    6.2        Yes    Yes   No   G         DECnet SNA 3270 Data Stream          6.1        Yes    Yes   No *         Programming Interface for OpenVMS,
         V1.4A   G         DECnet SNA 3270 Terminal Emulator    6.1        Yes    Yes   No          for OpenVMS, V1.5A  I                                                  (continued on next page)   I                                                                      D-15_ _  _      3     Layered Product Support for OpenVMS Version 6.2       >     Table D-1 (Cont.) Digital Layered Products Compatible withE     __________________OpenVMS_VAX_Version_6.2________________________o  2                                          OperatingD                                          System       DECnet SupportE     Product and Version                  Support    _________________ E     _____________________________________(Qualified)Ph._IV_Syn___Full   C     DECnet SNA 3270 Terminal Emulator    6.1        Yes    No    NoV%     /Japanese for VMS/Japanese, V1.5A   C     DECnet SNA APPC/LU6.2 Programming    6.1        Yes    Yes   No1      Interface for OpenVMS, V2.2A  C     DECnet SNA Application Programming   6.1        Yes    Yes   No       Interface for OpenVMS, V2.3A  C     DECnet SNA Data Transfer Facility    6.1        Yes    Yes   No      (Server), V3.1A.  C     DECnet SNA Data Transfer Facility    6.1        Yes    Yes   NoN     (Utilities), V3.1A  C     DECnet SNA Gateway for Channel       6.1        Yes    Yes   No      Transport, V2.1A  C     DECnet SNA Gateway for Synchronous   6.1        Yes    Yes   No      Transport, V1.2A  C     DECnet SNA Remote Job Entry for      6.1        Yes    Yes   Noc     OpenVMS, V1.4A  C     DECnet SNA Remote Job Entry          6.1        Yes    Yes   No       /Japanese for OpenVMS, V1.4A  C     DECnet SNA VMS Printer Emulator,     6.1        Yes    Yes   No 	     V1.2A   C     DECnet SNA VMS Printer Emulator      6.1        Yes    No    No      /Japanese, V1.2A  D     DECnet/OSI Version for OpenVMS VAX,  6.1        N/A    Yes   Yes     V6.1  D     DECnet/OSI Version for OpenVMS VAX,  6.2        N/A    Yes   Yes     V6.2  D     DEComni for OpenVMS VAX, V2.1        6.1        N/A    N/A   N/A  D     DECosap for OpenVMS VAX, V2.0B       6.1        N/A    N/A   N/A  E                                              (continued on next page)        D-16           I                           Layered Product Support for OpenVMS Version 6.2e      B         Table D-1 (Cont.) Digital Layered Products Compatible withI         __________________OpenVMS_VAX_Version_6.2________________________l  6                                              OperatingG                                              System      DECnet SupportXI         Product and Version                  Support    _________________2I         _____________________________________(Qualified)Ph._IV_Syn___Full2  G         DECprint Supervisor (DCPS) for       6.1        Yes    No    No1         OpenVMS, V1.1A  G         DECprint Supervisor (DCPS) for       6.1        Yes    No    No/         OpenVMS, V1.2   G         DECprint Supervisor/Japanese for     6.1        Yes    No    No          OpenVMS, V1.1,  H         DECram for OpenVMS, V2.1             6.2        N/A    N/A   N/A  G         DECset for OpenVMS VAX Systems,      6.1        Yes    No    Noo
         V11.2   G         DECset for OpenVMS VAX Systems,      6.2        Yes    No    NoC
         V12.0   H         DECvoice Software, V2.3              6.1        N/A    N/A   N/A  H         DECvoiceBuilder Software for         6.1        N/A    N/A   N/A(         OpenVMS (Administration and Run-         Time), V1.1A  H         DECvoiceBuilder Software for         6.1        N/A    N/A   N/A)         OpenVMS (Edit and Record Studio),N
         V1.1A   H         DECwatchdog/Autopilot, V2.1          6.1        No     N/A   N/A  G         DECwindows DECnet SNA 3270 Terminal  6.1        Yes    Yes   No6#         Emulator for OpenVMS, V2.0A   G         DECwindows DECnet SNA 3270 Terminal  6.1        Yes    No    Nop&         Emulator/Japanese for OpenVMS,
         V2.0A   H         DECwindows Motif for OpenVMS, V1.2-3 6.2        Yes    Yes   Yes           H         DECwindows Motif OpenVMS User        6.1        Yes    Yes   Yes         Interface/Cesky, V1.2p  I                                                  (continued on next page)a  I                                                                      D-17_ i         3     Layered Product Support for OpenVMS Version 6.2       >     Table D-1 (Cont.) Digital Layered Products Compatible withE     __________________OpenVMS_VAX_Version_6.2_________________________  2                                          OperatingD                                          System       DECnet SupportE     Product and Version                  Support    _________________eE     _____________________________________(Qualified)Ph._IV_Syn___Full1  D     DECwindows Motif OpenVMS User        6.1        Yes    Yes   Yes     Interface/Deutsch, V1.2   D     DECwindows Motif OpenVMS User        6.1        Yes    Yes   Yes     Interface/Espaol, V1.2   D     DECwindows Motif OpenVMS User        6.1        Yes    Yes   Yes     Interface/Franais, V1.2  D     DECwindows Motif OpenVMS User        6.1        Yes    Yes   Yes     Interface/Italiano, V1.2  D     DECwindows Motif OpenVMS User        6.1        Yes    Yes   Yes     Interface/Magyar, V1.2  D     DECwindows Motif OpenVMS User        6.1        Yes    Yes   Yes     Interface/Polski, V1.2  D     DECwindows Motif OpenVMS User        6.1        Yes    Yes   Yes     Interface/Russkij, V1.21  D     DECwindows Motif OpenVMS User        6.1        Yes    Yes   Yes     Interface/Slovenski, V1.2E  D     DECwindows Motif OpenVMS User        6.1        Yes    Yes   Yes     Interface/Svenska, V1.2V  D     DECwindows Motif/Hangul for          6.1        Yes    Yes   Yes     OpenVMS, V1.2   D     DECwindows Motif/Hanyu for OpenVMS,  6.1        Yes    Yes   Yes     V1.2  D     DECwindows Motif/Hanzi for OpenVMS,  6.1        Yes    Yes   Yes     V1.2  C     DECwindows Motif/Japanese for        6.1        Yes    Yes   Noi     OpenVMS, V1.2s  D     DECwindows Motif/Thai for OpenVMS,   6.1        Yes    Yes   Yes     V1.2  C     DECwindows/Hebrew for OpenVMS, V1.2  6.1        Yes    Yes   No   E                                              (continued on next page)        D-18 n  e      I                           Layered Product Support for OpenVMS Version 6.2_      B         Table D-1 (Cont.) Digital Layered Products Compatible withI         __________________OpenVMS_VAX_Version_6.2________________________E  6                                              OperatingG                                              System      DECnet Support I         Product and Version                  Support    _________________AI         _____________________________________(Qualified)Ph._IV_Syn___FullN  H         DECwrite for OpenVMS VAX, V3.0       6.1        N/A    N/A   N/A  H         DECwrite/British for OpenVMS VAX,    6.1        N/A    N/A   N/A         V3.0  H         DECwrite/Deutsch for VMS, V3.0       6.1        N/A    N/A   N/A  H         DECwrite/Franais for VMS, V3.0      6.1        N/A    N/A   N/A  H         Digital Extended Math Library for    6.1        N/A    N/A   N/A$         OpenVMS (Development), V2.0A  H         Digital Extended Math Library for    6.1        N/A    N/A   N/A!         OpenVMS (Run-Time), V2.0AY  0         Distributed Computing Environment    6.2(         (DCE) for OpenVMS (Development),         V1.3  0         Distributed Computing Environment    6.2*         (DCE) for OpenVMS (Run-Time), V1.3  G         DSM Version for OpenVMS VAX          6.1        Yes    No    Noa         Systems, V6.3D  G         DSM Version for OpenVMS VAX          6.1        Yes    No    No          Systems, V6.4t  G         EDCS II (Client), V2.2               6.1        Yes    No    No   G         EDCS II (Server), V2.2               6.1        Yes    No    No   H         IEX-VMS-Driver, V4.4                 6.1        N/A    N/A   N/A  ;         InfoServer Software, V3.2            6.1        Yes   H         KAP for DEC C for OpenVMS VAX, V1.1  6.1        N/A    N/A   N/A  H         KAP for DEC Fortran for OpenVMS      6.1        N/A    N/A   N/A         VAX, V1.1h  H         MAILbus 400 Application Program      6.1        Yes    N/A   N/A#         Interface for OpenVMS, V1.4   I                                                  (continued on next page)p  I                                                                      D-19     _      3     Layered Product Support for OpenVMS Version 6.2l      >     Table D-1 (Cont.) Digital Layered Products Compatible withE     __________________OpenVMS_VAX_Version_6.2________________________r  2                                          OperatingD                                          System       DECnet SupportE     Product and Version                  Support    _________________oE     _____________________________________(Qualified)Ph._IV_Syn___Fullo  D     MAILbus 400 Message Transfer Agent   6.1        Yes    N/A   N/A     for OpenVMS, V1.4n  C     MAILbus 400/Message Router Gateway,  6.1        No     Yes   No      V1.1  C     MAILWorks for OpenVMS, V1.3A         6.1        Yes    Yes   NoA  C     MEP VT for DEC SNA 3270 Application  6.1        Yes    Yes   Nos     Services, V3.0  D     MicroVAX/DRQ3B Device Driver, V1.4   6.1        N/A    N/A   N/A  C     MUXserver 320/380/90 Remote          6.2        Yes    No    No1     Terminal Server, V2.0   D     NAS Base Server 200 for OpenVMS VAX  6.2        N/A    N/A   N/A     Systems, V6.0N  D     NAS Client 150 for OpenVMS VAX       6.2        N/A    N/A   N/A     Workstations, V6.0  D     NAS Client 250 for OpenVMS VAX       6.2        N/A    N/A   N/A     Workstations, V6.0  D     NAS Production Server 400 for        6.2        N/A    N/A   N/A     OpenVMS VAX Systems, V6.0   D     NAS Server 300 for OpenVMS VAX       6.2        N/A    N/A   N/A     Systems, V6.0a  C     ObjectBroker for OpenVMS             6.2        Yes    No    Noc     (Development), V2.5A  C     ObjectBroker for OpenVMS (Run-       6.2        Yes    No    Noa     Time), V2.5A  C     OpenVMS SNA, V2.2                    6.1        Yes    Yes   No   D     OpenVMS VAX Operating System, V6.1   6.1        Yes    Yes   Yes  D     OpenVMS VAX Operating System, V6.2   6.2        Yes    Yes   Yes  ,     OpenVMS/Hangul VAX Operating         6.1     System, V6.1  E                                              (continued on next page)        D-20 /  a      I                           Layered Product Support for OpenVMS Version 6.2p      B         Table D-1 (Cont.) Digital Layered Products Compatible withI         __________________OpenVMS_VAX_Version_6.2________________________   6                                              OperatingG                                              System      DECnet Support1I         Product and Version                  Support    _________________ I         _____________________________________(Qualified)Ph._IV_Syn___FullA  0         OpenVMS/Hanyu VAX Operating System,  6.1         V6.1  0         OpenVMS/Hanzi VAX Operating System,  6.1         V6.1  0         OpenVMS/Japanese VAX Operating       6.1         System, V6.1  0         OpenVMS/Thai VAX Operating System,   6.1         V6.1  G         Oracle CDD/Repository for OpenVMS    6.1        Yes    Yes   NoE         Systems, V5.4p  G         Oracle CODASYL DBMS (Development),   6.2        Yes    Yes   NoJ
         V6.0As  G         Oracle CODASYL DBMS (Development),   6.2        Yes    Yes   No          V6.1  G         Oracle CODASYL DBMS (Run-Time),      6.2        Yes    Yes   No.
         V6.0AE  G         Oracle CODASYL DBMS (Run-Time),      6.2        Yes    Yes   Not         V6.1  H         Oracle Expert, V2.1A                 6.1        N/A    N/A   N/A  H         Oracle Graphical Schema Editor       6.1        N/A    N/A   N/A%         (GSE) for Rdb, OpenVMS, V2.1At  H         Oracle InstantSQL for Rdb, V2.1A     6.1        N/A    N/A   N/A  H         Oracle RALLY, V4.0A                  6.1        Yes    Yes   Yes  H         Oracle RALLY, V4.1                   6.1        Yes    Yes   Yes  H         Oracle RALLY (Development), V4.0A    6.1        Yes    Yes   Yes  H         Oracle RALLY (Development), V4.1     6.1        Yes    Yes   Yes  G         Oracle RALLY (MOTIF), V4.0A          6.1        Yes    No    No   H         Oracle RALLY (MOTIF), V4.1           6.1        Yes    Yes   Yes  I                                                  (continued on next page)   I                                                                      D-21_ _    3     Layered Product Support for OpenVMS Version 6.2       >     Table D-1 (Cont.) Digital Layered Products Compatible withE     __________________OpenVMS_VAX_Version_6.2________________________   2                                          OperatingD                                          System       DECnet SupportE     Product and Version                  Support    _________________YE     _____________________________________(Qualified)Ph._IV_Syn___Fullv  7     Oracle Rdb, V5.1A                    6.1        YesM  C     Oracle Rdb, V6.0                     6.1        Yes    Yes   No   C     Oracle Rdb, V6.0A                    6.1        Yes    Yes   No   >     Oracle Rdb, V6.1                     6.1        Yes    Yes  C     Oracle Rdb, V6.1                     6.1        Yes    Yes   No   7     Oracle Rdb (Interactive), V5.1A      6.1        Yes   7     Oracle Rdb (Run-Time), V5.1A         6.1        Yes   >     Oracle TRACE, V2.1A                  6.1        Yes    Yes  C     PATHWORKS for OpenVMS (Macintosh),   6.2        Yes    Yes   No      V1.3  C     PATHWORKS for OpenVMS (NetWare),     6.1        Yes    Yes   Nor	     V1.0Cs  C     PATHWORKS for VMS, V5.0C             6.1        Yes    Yes   NoV  D     POLYCENTER Accounting Chargeback     6.1        Yes    Yes   Yes     for OpenVMS, V2.1S  7     POLYCENTER Capacity Planner, V3.0    6.1        Yese  D     POLYCENTER Console Manager, V1.5A    6.1        N/A    N/A   N/A  D     POLYCENTER Console Manager, V1.6     6.2        N/A    N/A   N/A  C     POLYCENTER Extended LAN Manager for  6.1        Yes    Yes   No      OpenVMS VAX, V1.4(  C     POLYCENTER Fault Diagnostic          6.1        Yes    Yes   No      Package, V1.4c  D     POLYCENTER File Optimizer, V2.0      6.1        Yes    N/A   N/A  D     POLYCENTER File Optimizer, V2.1      6.2        Yes    N/A   N/A  C     POLYCENTER Framework, V1.4           6.1        Yes    Yes   No   C     POLYCENTER Framework Developer's     6.1        Yes    Yes   No      Toolkit, V1.4   E                                              (continued on next page)_       D-22           I                           Layered Product Support for OpenVMS Version 6.2f      B         Table D-1 (Cont.) Digital Layered Products Compatible withI         __________________OpenVMS_VAX_Version_6.2________________________   6                                              OperatingG                                              System      DECnet SupportvI         Product and Version                  Support    _________________ I         _____________________________________(Qualified)Ph._IV_Syn___Fulle  G         POLYCENTER Framework Historian       6.1        Yes    Yes   No          Option, V1.4  G         POLYCENTER Framework Notification    6.1        Yes    Yes   No0         Option, V1.4  H         POLYCENTER HSM, V1.0A                6.1        Yes    N/A   N/A  H         POLYCENTER HSM, V1.1                 6.1        Yes    N/A   N/A  H         POLYCENTER Media Library Manager     6.1        Yes    Yes   Yes         for OpenVMS VAX, V1.12  G         POLYCENTER Network Manager 200,      6.1        Yes    Yes   No          V1.4  G         POLYCENTER Network Manager 400,      6.1        Yes    Yes   No          V2.4  G         POLYCENTER Network Statistics        6.1        Yes    Yes   No          Option, V1.4  G         POLYCENTER Network Topology Option,  6.1        Yes    Yes   Non         V1.4  H         POLYCENTER Performance Advisor for   6.1        Yes    Yes   Yes         OpenVMS, V2.1s  H         POLYCENTER Performance Data          6.1        Yes    Yes   Yes#         Collector for OpenVMS, V2.1   G         POLYCENTER Saveset Manager for       6.1        Yes    No    No          OpenVMS, V1.0A  G         POLYCENTER Saveset Manager for       6.1        Yes    No    No          OpenVMS, V1.1n  G         POLYCENTER Scheduler OpenVMS, V2.1B  6.1        Yes    Yes   No   G         POLYCENTER Scheduler OpenVMS         6.1        Yes    Yes   No          (Agent), V2.1B  G         POLYCENTER Scheduler OpenVMS         6.1        Yes    Yes   Nop         (Client), V2.1B_  I                                                  (continued on next page)   I                                                                      D-23c n  e      3     Layered Product Support for OpenVMS Version 6.2_      >     Table D-1 (Cont.) Digital Layered Products Compatible withE     __________________OpenVMS_VAX_Version_6.2________________________   2                                          OperatingD                                          System       DECnet SupportE     Product and Version                  Support    _________________ E     _____________________________________(Qualified)Ph._IV_Syn___Fullt  C     POLYCENTER Scheduler OpenVMS         6.1        Yes    Yes   No.     (Server), V2.1Bt  C     POLYCENTER Scheduler/Japanese for    6.1        Yes    No    No.     OpenVMS VAX, V2.1t  C     POLYCENTER Security Compliance       6.1        Yes    Yes   NoA     Manager for OpenVMS, V2.3A  D     POLYCENTER Security Intrusion        6.2        Yes    Yes   Yes     Detector for VMS, V1.2  C     POLYCENTER Security Reporting        6.1        Yes    Yes   NoA     Facility for OpenVMS, V2.1  D     POLYCENTER Sequential Media File     6.1        Yes    N/A   N/A      System for OpenVMS VAX, V1.0  D     POLYCENTER Sequential Media File     6.1        Yes    N/A   N/A      System for OpenVMS VAX, V1.1  C     POLYCENTER Software Distribution,    6.1        Yes    Yes   No      V3.0  D     POLYCENTER Striping for OpenVMS      6.1        N/A    N/A   N/A
     VAX, V2.1s  C     POLYCENTER System Census for         6.1        Yes    Yes   No #     OpenVMS VAX and ULTRIX (Agent),p     V1.3  C     POLYCENTER System Census             6.1        Yes    Yes   No      for OpenVMS VAX and ULTRIX     (Consolidator), V1.3  C     POLYCENTER System Census for         6.1        Yes    Yes   NoM&     OpenVMS VAX and ULTRIX (GUI), V1.3  C     POLYCENTER System Watchdog Agent     6.1        Yes    Yes   No_     for OpenVMS, V2.2_  E                                              (continued on next page)        D-24           I                           Layered Product Support for OpenVMS Version 6.2c      B         Table D-1 (Cont.) Digital Layered Products Compatible withI         __________________OpenVMS_VAX_Version_6.2________________________E  6                                              OperatingG                                              System      DECnet Support I         Product and Version                  Support    _________________SI         _____________________________________(Qualified)Ph._IV_Syn___Full.  G         POLYCENTER System Watchdog           6.1        Yes    Yes   NoN&         Consolidator for OpenVMS, V2.2  H         POSIX for OpenVMS, V2.0              6.2        Yes    Yes   Yes  0         PrintServer Software, V5.1           6.1  0         PrintServer Software (Base), V5.1    6.1  0         PrintServer Software (Client), V5.1  6.1  0         PrintServer Software (DECprint       6.1         Supervisor), V5.1n  G         Reliable Transaction Router for      6.2        Yes    Yes   Noe#         OpenVMS VAX (Client), V2.2B   G         Reliable Transaction Router for      6.2        Yes    Yes   No #         OpenVMS VAX (Client), V2.2C   G         Reliable Transaction Router for      6.2        Yes    Yes   Nor#         OpenVMS VAX (Server), V2.2C   H         RMS Journaling for OpenVMS VAX,      6.2        Yes    Yes   Yes         V6.2  G         Storage Library System for OpenVMS,  6.1        Yes    No    No          V2.5  G         Storage Library System for OpenVMS   6.1        Yes    No    No          (ACS), V2.5t  G         Storage Library System for OpenVMS   6.1        Yes    No    No,         (Client), V2.5  G         StorageWorks Desktop Backup          6.1        Yes    No    No %         /Archiver Backup Server, V2.0   G         StorageWorks Desktop Backup          6.2        Yes    No    NoM&         /Archiver Backup Server, V2.0B  H         Storageworks RAID Software for       6.2        N/A    N/A   N/A         OpenVMS, V1.0_  I                                                  (continued on next page)   I                                                                      D-25n e  o      3     Layered Product Support for OpenVMS Version 6.2_      >     Table D-1 (Cont.) Digital Layered Products Compatible withE     __________________OpenVMS_VAX_Version_6.2________________________e  2                                          OperatingD                                          System       DECnet SupportE     Product and Version                  Support    _________________ E     _____________________________________(Qualified)Ph._IV_Syn___Full   D     Storageworks RAID Software for       6.1        N/A    N/A   N/A     OpenVMS, V2.1U  D     Storageworks RAID Software for       6.2        N/A    N/A   N/A     OpenVMS, V2.2O  C     TeamRoute for ALL-IN-1 OpenVMS VAX,  6.1        Yes    Yes   No1     V1.2  C     TeamRoute for ALL-IN-1 OpenVMS VAX,  6.1        Yes    Yes   Non     V1.3  7     TeamRoute for ALL-IN-1/Japanese for  6.1        Yes1     OpenVMS VAX, V1.1A  7     TeamRoute for OpenVMS, V1.0          6.1        Yese  7     TeamRoute/Dansk for ALL-IN-1, V1.1   6.1        Yes/  7     TeamRoute/Deutsch for ALL-IN-1,      6.1        Yes6     V1.1  7     TeamRoute/Espaol for ALL-IN-1,      6.1        Yesf     V1.0  7     TeamRoute/Franais for ALL-IN-1,     6.1        Yesw     V1.1  7     TeamRoute/Italiano for ALL-IN-1,     6.1        Yes2     V1.1  7     TeamRoute/Japanese for OpenVMS,      6.1        YesN     V1.0  7     TeamRoute/Nederlands for ALL-IN-1,   6.1        Yes1     V1.1  7     TeamRoute/Norsk for ALL-IN-1, V1.1   6.1        YesM  7     TeamRoute/Suomi for ALL-IN-1, V1.1   6.1        Yes   7     TeamRoute/Svenska for ALL-IN-1,      6.1        Yes-     V1.1  E                                              (continued on next page)s       D-26           I                           Layered Product Support for OpenVMS Version 6.2_      B         Table D-1 (Cont.) Digital Layered Products Compatible withI         __________________OpenVMS_VAX_Version_6.2________________________   6                                              OperatingG                                              System      DECnet Support_I         Product and Version                  Support    _________________iI         _____________________________________(Qualified)Ph._IV_Syn___Fulli  G         VAX 2780/3780 Protocol Emulator,     6.1        Yes    Yes   No          V1.8  H         VAX BASIC, V3.7                      6.1        Yes    Yes   Yes  H         VAX COBOL for OpenVMS VAX, V5.2      6.1        Yes    Yes   Yes  H         VAX COBOL/Japanese for OpenVMS VAX,  6.1        Yes    Yes   Yes         V5.2  H         VAX Distributed Name Service, V1.1A  6.1        Yes    Yes   Yes  H         VAX FMS, V2.4                        6.1        N/A    N/A   N/A  H         VAX FMS (Run-Time), V2.4             6.1        N/A    N/A   N/A  H         VAX FMS/Japanese, V2.4               6.1        Yes    Yes   Yes  H         VAX FMS/Japanese (Run-Time), V2.4    6.1        Yes    Yes   Yes  G         VAX Message Router (Base System),    6.1        Yes    Yes   NoM
         V3.3A6  G         VAX Message Router (Programmer's     6.1        Yes    Yes   Non         Kit), V3.3  G         VAX Message Router (VMSmail          6.1        Yes    Yes   No          Gateway), V3.3A   G         VAX Message Router X.400 Gateway,    6.1        No     Yes   No          V2.3  G         VAX Message Router/P Gateway, V1.3   6.1        Yes    Yes   NoE  G         VAX Message Router/S Gateway, V1.3   6.1        Yes    Yes   NoE  H         VAX TDMS, V1.9A                      6.1        N/A    N/A   N/A  H         VAX TDMS (Run-Time), V1.9A           6.1        N/A    N/A   N/A  0         VAX-11/RSX, V2.5                     6.1  H         VAXcluster Software for OpenVMS      6.2        Yes    Yes   Yes         VAX, V6.2   H         Volume Shadowing for OpenVMS VAX,    6.2        Yes    Yes   YesI         V6.2_____________________________________________________________a  I                                                                      D-27_ _  _      3     Layered Product Support for OpenVMS Version 6.2       D     Table D-2 Digital Layered Products Compatible with OpenVMS AlphaE     __________Version_6.2_____________________________________________  2                                          OperatingD                                          System       DECnet SupportE     Product and Version                  Support    _________________sE     _____________________________________(Qualified)Ph._IV_Syn___Fullo  C     ACMS Desktop, V2.0                   6.1        Yes    Yes   NoT  ,     ACMS Desktop/Japanese, V2.0          6.1  D     ACMS for OpenVMS AXP (Development),  6.1        Yes    N/A   N/A     V4.0  D     ACMS for OpenVMS AXP (Remote), V4.0  6.1        Yes    N/A   N/A  D     ACMS for OpenVMS AXP (Run-Time),     6.1        Yes    N/A   N/A     V4.0  C     ALL-IN-1 Office Server Options for   6.1        Yes    Yes   Nol     OpenVMS AXP, V3.1X  C     ALL-IN-1 Teamlinks Connection        6.1        Yes    Yes   Nol!     Package for OpenVMS AXP, V2.1   C     ALL-IN-1 Teamlinks Connection        6.1        Yes    Yes   Nor!     Package for OpenVMS AXP, V2.5   C     ALL-IN-1/Dansk Office Server         6.1        Yes    Yes   Noe$     Options for OpenVMS AXP and VAX,     V3.1  C     ALL-IN-1/Deutsch Office Server       6.1        Yes    Yes   Noe%     Options for Open VMS AXP and VAX,A     V3.1  C     ALL-IN-1/Espaol Office Server       6.1        Yes    Yes   Noe$     Options for OpenVMS AXP and VAX,     V3.1  C     ALL-IN-1/Franais Office Server      6.1        Yes    Yes   No6$     Options for OpenVMS AXP and VAX,     V3.1  C     ALL-IN-1/Italiano Office Server      6.1        Yes    Yes   No/$     Options for OpenVMS AXP and VAX,     V3.1  E                                              (continued on next page)e       D-28           I                           Layered Product Support for OpenVMS Version 6.2.      B         Table D-2 (Cont.) Digital Layered Products Compatible withI         __________________OpenVMS_Alpha_Version_6.2_______________________  6                                              OperatingG                                              System      DECnet SupportrI         Product and Version                  Support    __________________I         _____________________________________(Qualified)Ph._IV_Syn___Fulll  0         ALL-IN-1/Japanese Office Server      6.1(         Options for OpenVMS AXP and VAX,         V3.1  G         ALL-IN-1/Nederlands Office Server    6.1        Yes    Yes   No6(         Options for OpenVMS AXP and VAX,         V3.1  G         ALL-IN-1/Norsk Office Server         6.1        Yes    Yes   Non(         Options for OpenVMS AXP and VAX,         V3.1  G         ALL-IN-1/Portuges Office Server     6.1        Yes    Yes   NoN(         Options for OpenVMS AXP and VAX,         V3.1  G         ALL-IN-1/Suomi Office Server         6.1        Yes    Yes   NoS(         Options for OpenVMS AXP and VAX,         V3.1  G         ALL-IN-1/Svenska Office Server       6.1        Yes    Yes   No (         Options for OpenVMS AXP and VAX,         V3.1  0         AssetWORKS for OpenVMS AXP (Agent),  6.2         V1.0  0         AssetWORKS for OpenVMS AXP           6.2         (Server), V1.0  G         BASEstar Classic for OpenVMS AXP     6.1        Yes    Yes   No          (Development), V3.3   G         BASEstar Classic for OpenVMS AXP     6.1        Yes    Yes   No          (Run-Time), V3.3  A         BASEstar Graphics Enabler for        6.1        Yes    Noe'         OpenVMS AXP (Development), V2.0   A         BASEstar Graphics Enabler for        6.1        Yes    No $         OpenVMS AXP (Run-Time), V2.0  I                                                  (continued on next page)I  I                                                                      D-29            3     Layered Product Support for OpenVMS Version 6.2       >     Table D-2 (Cont.) Digital Layered Products Compatible withE     __________________OpenVMS_Alpha_Version_6.2______________________C  2                                          OperatingD                                          System       DECnet SupportE     Product and Version                  Support    _________________ E     _____________________________________(Qualified)Ph._IV_Syn___Full   D     BASEstar Open Server for OpenVMS     6.1        N/A    N/A   N/A     AXP (Client), V2.0  D     BASEstar Open Server for OpenVMS     6.1        N/A    N/A   N/A     AXP (Development), V2.0   D     BASEstar Open Server for OpenVMS     6.1        N/A    N/A   N/A     AXP (Run-Time), V2.0  C     DEC Ada for OpenVMS Alpha Systems,   6.1        Yes    Yes   No6	     V3.0Ae  C     DEC Ada for OpenVMS Alpha Systems,   6.2        Yes    Yes   NoY     V3.2  C     DEC Ada for Professional             6.2        Yes    Yes   Noe"     Development Option for OpenVMS     AXP Systems, V3.2e  ,     DEC Availability Manager for         6.1     Distributed Systems, V6.1M  ,     DEC BASIC for OpenVMS AXP, V1.0      6.1  D     DEC BASIC for OpenVMS AXP, V1.1      6.2        N/A    Yes   Yes  D     DEC C for OpenVMS AXP Systems,       6.1        N/A    N/A   N/A	     V1.3As  D     DEC C for OpenVMS AXP Systems, V4.0  6.1        N/A    N/A   N/A  D     DEC C for OpenVMS AXP Systems, V4.1  6.1        N/A    N/A   N/A  D     DEC C for OpenVMS AXP Systems, V5.0  6.2        N/A    N/A   N/A  D     DEC C++ for OpenVMS AXP Systems,     6.1        N/A    N/A   N/A	     V1.3AA  D     DEC C++ for OpenVMS AXP Systems,     6.2        N/A    N/A   N/A     V5.0  C     DEC COBOL for OpenVMS Alpha          6.1        Yes    No    No      Systems, V2.0   E                                              (continued on next page)        D-30 N         I                           Layered Product Support for OpenVMS Version 6.2Y      B         Table D-2 (Cont.) Digital Layered Products Compatible withI         __________________OpenVMS_Alpha_Version_6.2______________________.  6                                              OperatingG                                              System      DECnet SupportaI         Product and Version                  Support    _________________nI         _____________________________________(Qualified)Ph._IV_Syn___Fulln  G         DEC COBOL for OpenVMS Alpha          6.2        Yes    No    No          Systems, V2.1i  G         DEC COBOL for OpenVMS Alpha          6.2        Yes    No    Nov         Systems, V2.2e  0         DEC COBOL/Japanese for OpenVMS AXP   6.1         Systems, V2.0_  0         DEC COBOL/Japanese for OpenVMS AXP   6.1         Systems, V2.1F  G         DEC Code Management System (CMS)     6.1        Yes    No    No %         for OpenVMS AXP Systems, V3.6t  G         DEC Code Management System (CMS)     6.2        Yes    No    NoT%         for OpenVMS AXP Systems, V3.7   G         DEC Data Distributor Version for     6.1        Yes    Yes   No          OpenVMS AXP, V6.0   G         DEC DATATRIEVE for OpenVMS AXP       6.1        Yes    Yes   Noo         Systems, V6.1B  H         DEC DATATRIEVE for OpenVMS AXP       6.1        Yes    Yes   Yes         Systems, V7.0O  G         DEC DATATRIEVE/Japanese for OpenVMS  6.1        Yes    Yes   No4         AXP Systems, V6.1o  G         DEC DB Integrator for OpenVMS AXP,   6.1        Yes    No    No          V1.0  ;         DEC DB Integrator for OpenVMS AXP,   6.1        Yes 
         V1.0B   ;         DEC DB Integrator for OpenVMS AXP,   6.1        YesY         V3.1  0         DEC DB Integrator Gateway for        6.1'         Custom Drivers for OpenVMS AXP,          V3.0  I                                                  (continued on next page)   I                                                                      D-31r r         3     Layered Product Support for OpenVMS Version 6.2       >     Table D-2 (Cont.) Digital Layered Products Compatible withE     __________________OpenVMS_Alpha_Version_6.2______________________   2                                          OperatingD                                          System       DECnet SupportE     Product and Version                  Support    _________________nE     _____________________________________(Qualified)Ph._IV_Syn___Full   ,     DEC DB Integrator Gateway for        6.1#     Custom Drivers for OpenVMS AXP,_	     V3.0B   ,     DEC DB Integrator Gateway for        6.1#     Custom Drivers for OpenVMS AXP,n	     V3.0Cs  ,     DEC DB Integrator Gateway for DB2    6.1     for OpenVMS AXP, V3.0   ,     DEC DB Integrator Gateway for DB2    6.1     for OpenVMS AXP, V3.0B  ,     DEC DB Integrator Gateway for DB2    6.1     for OpenVMS AXP, V3.1   C     DEC DB Integrator Gateway for DBMS   6.1        Yes    Yes   Not     for OpenVMS AXP, V1.0r  7     DEC DB Integrator Gateway for DSM,   6.1        Yes 	     V1.0B   7     DEC DB Integrator Gateway for EDA    6.1        Yes      /SQL, V3.1  ,     DEC DB Integrator Gateway for        6.1!     ORACLE for OpenVMS AXP, V3.0BN  ,     DEC DB Integrator Gateway for        6.1      ORACLE for OpenVMS AXP, V3.1  ,     DEC DB Integrator Gateway for RMS    6.1     for OpenVMS AXP, V3.0r  ,     DEC DB Integrator Gateway for RMS    6.1     for OpenVMS AXP, V3.0B  ,     DEC DB Integrator Gateway for RMS    6.1     for OpenVMS AXP, V3.0C  E                                              (continued on next page)e       D-32           I                           Layered Product Support for OpenVMS Version 6.2u      B         Table D-2 (Cont.) Digital Layered Products Compatible withI         __________________OpenVMS_Alpha_Version_6.2______________________T  6                                              OperatingG                                              System      DECnet SupporteI         Product and Version                  Support    _________________XI         _____________________________________(Qualified)Ph._IV_Syn___Full   0         DEC DB Integrator Gateway for        6.1'         Sequelink for OpenVMS AXP, V3.1d  0         DEC DB Integrator Gateway for        6.1%         SYBASE for OpenVMS AXP, V1.0B   0         DEC DB Integrator Gateway for        6.1$         SYBASE for OpenVMS AXP, V3.1  0         DEC Distributed Computing Services   6.1         for OpenVMS, V1.0   H         DEC Distributed Queueing Service     6.2        Yes    Yes   Yes         for OpenVMS AXP, V1.3_  H         DEC FMS for OpenVMS AXP              6.2        N/A    N/A   N/A         (Development), V2.4   H         DEC FMS for OpenVMS AXP (Run-Time),  6.2        N/A    N/A   N/A         V2.4  H         DEC FMS/Hangul for OpenVMS AXP       6.1        N/A    N/A   N/A         (Development), V2.4l  H         DEC FMS/Hangul for OpenVMS AXP       6.1        N/A    N/A   N/A         (Run-Time), V2.4  H         DEC FMS/Hebrew for OpenVMS AXP       6.1        N/A    N/A   N/A         (Development), V2.4r  H         DEC FMS/Hebrew for OpenVMS AXP       6.1        N/A    N/A   N/A         (Run-Time), V2.4  H         DEC FMS/Japanese for OpenVMS AXP     6.1        N/A    N/A   N/A         (Development), V2.4e  H         DEC FMS/Japanese for OpenVMS AXP     6.1        N/A    N/A   N/A         (Run-Time), V2.4  H         DEC Fortran for OpenVMS Systems,     6.1        Yes    Yes   Yes         V6.2  I                                                  (continued on next page)c  I                                                                      D-33) 2         3     Layered Product Support for OpenVMS Version 6.2       >     Table D-2 (Cont.) Digital Layered Products Compatible withE     __________________OpenVMS_Alpha_Version_6.2______________________i  2                                          OperatingD                                          System       DECnet SupportE     Product and Version                  Support    _________________WE     _____________________________________(Qualified)Ph._IV_Syn___Fulli  D     DEC Fortran for OpenVMS Systems,     6.2        Yes    Yes   Yes     V6.3  D     DEC Fortran-90 for OpenVMS Systems,  6.2        Yes    Yes   Yes     V2.0  D     DEC GKS for OpenVMS AXP Systems      6.1        Yes    Yes   Yes     (Development), V5.3   D     DEC GKS for OpenVMS AXP Systems      6.1        Yes    Yes   Yes     (Development), V6.0   D     DEC GKS for OpenVMS AXP Systems      6.1        Yes    Yes   Yes     (Run-Time), V5.3  D     DEC GKS for OpenVMS AXP Systems      6.1        Yes    Yes   Yes     (Run-Time), V6.0  ,     DEC GKS/Japanese for OpenVMS AXP     6.1     (Development), V5.2A  D     DEC GKS/Japanese for OpenVMS AXP     6.1        Yes    Yes   Yes     (Development), V5.3n  ,     DEC GKS/Japanese for OpenVMS AXP     6.1     (Run-Time), V5.2A_  D     DEC GKS/Japanese for OpenVMS AXP     6.1        Yes    Yes   Yes     (Run-Time), V5.3  C     DEC Language Sensitive Editor        6.1        Yes    No    NoM%     /Source Code Analyzer for OpenVMSa     Systems, V4.2   C     DEC Language Sensitive Editor        6.2        Yes    No    NoO%     /Source Code Analyzer for OpenVMS1     Systems, V4.3e  C     DEC MAILWorks for OpenVMS, V1.3A     6.1        Yes    Yes   No3  C     DEC Module Management System (MMS)   6.1        Yes    No    NoM!     for OpenVMS AXP Systems, V2.7p  E                                              (continued on next page)        D-34    e      I                           Layered Product Support for OpenVMS Version 6.2e      B         Table D-2 (Cont.) Digital Layered Products Compatible withI         __________________OpenVMS_Alpha_Version_6.2______________________t  6                                              OperatingG                                              System      DECnet SupportmI         Product and Version                  Support    _________________/I         _____________________________________(Qualified)Ph._IV_Syn___FullN  G         DEC Module Management System (MMS)   6.2        Yes    No    No %         for OpenVMS AXP Systems, V3.0   0         DEC Notes for OpenVMS AXP Systems,   6.1         V2.5  H         DEC Open3D for OpenVMS AXP, V2.3     6.1        Yes    Yes   Yes  H         DEC Open3D for OpenVMS AXP, V2.4     6.1        Yes    Yes   Yes  H         DEC Open3D for OpenVMS AXP, V2.5     6.1        Yes    Yes   Yes  H         DEC Open3D for OpenVMS AXP, V2.6     6.2        Yes    Yes   Yes  H         DEC OPS5 for OpenVMS, V4.0A          6.1        Yes    Yes   Yes  H         DEC OPS5/Japanese for OpenVMS AXP,   6.1        Yes    Yes   Yes
         V4.0A_  H         DEC Optical Storage Desktop          6.1        N/A    N/A   N/A(         Software (OSDS) for OpenVMS AXP,         V3.2  H         DEC Optical Storage Management       6.1        N/A    N/A   N/A(         Software (OSMS) for OpenVMS AXP,         V3.2  H         DEC OSDS-Optical Storage Desktop     6.1        N/A    N/A   N/A&         Software for OpenVMS AXP, V3.2  H         DEC Pascal for OpenVMS AXP Systems,  6.1        Yes    Yes   Yes         V5.2  H         DEC Pascal for OpenVMS AXP Systems,  6.1        Yes    Yes   Yes         V5.3  G         DEC Performance and Coverage         6.1        Yes    No    Noa'         Analyzer (PCA) for OpenVMS AXP,          V4.2  G         DEC Performance and Coverage         6.2        Yes    No    No '         Analyzer (PCA) for OpenVMS AXP,          V4.3  I                                                  (continued on next page)   I                                                                      D-35t (  m      3     Layered Product Support for OpenVMS Version 6.2       >     Table D-2 (Cont.) Digital Layered Products Compatible withE     __________________OpenVMS_Alpha_Version_6.2______________________3  2                                          OperatingD                                          System       DECnet SupportE     Product and Version                  Support    _________________AE     _____________________________________(Qualified)Ph._IV_Syn___Full   ,     DEC PHIGS for OpenVMS AXP Systems    6.1     (Development), V2.5A  D     DEC PHIGS for OpenVMS AXP Systems    6.1        Yes    Yes   Yes     (Development), V2.6O  D     DEC PHIGS for OpenVMS AXP Systems    6.1        Yes    Yes   Yes     (Development), V3.0_  D     DEC PHIGS for OpenVMS AXP Systems    6.1        Yes    Yes   Yes     (Development), V3.0B  D     DEC PHIGS for OpenVMS AXP Systems    6.2        Yes    Yes   Yes     (Development), V3.1   ,     DEC PHIGS for OpenVMS AXP Systems    6.1     (Run-Time), V2.5A.  D     DEC PHIGS for OpenVMS AXP Systems    6.1        Yes    Yes   Yes     (Run-Time), V2.6  D     DEC PHIGS for OpenVMS AXP Systems    6.1        Yes    Yes   Yes     (Run-Time), V3.0  D     DEC PHIGS for OpenVMS AXP Systems    6.1        Yes    Yes   Yes     (Run-Time), V3.0B_  D     DEC PHIGS for OpenVMS AXP Systems    6.2        Yes    Yes   Yes     (Run-Time), V3.1  D     DEC PHIGS/Japanese for OpenVMS AXP   6.1        Yes    Yes   Yes     (Development), V2.5)  D     DEC PHIGS/Japanese for OpenVMS AXP   6.1        Yes    Yes   Yes     (Run-Time), V2.5  C     DEC Rdb/Hangul for OpenVMS/Hangul    6.1        Yes    Yes   No 
     AXP, V6.0N  C     DEC Rdb/Hanyu for OpenVMS/Hanyu      6.1        Yes    Yes   No 
     AXP, V6.0   E                                              (continued on next page)        D-36 N         I                           Layered Product Support for OpenVMS Version 6.21      B         Table D-2 (Cont.) Digital Layered Products Compatible withI         __________________OpenVMS_Alpha_Version_6.2______________________   6                                              OperatingG                                              System      DECnet SupportPI         Product and Version                  Support    _________________ I         _____________________________________(Qualified)Ph._IV_Syn___Full-  0         DEC Rdb/Japanese for OpenVMS AXP,    6.1         V6.0  G         DEC SNA 3270 Application Services    6.1        Yes    Yes   NoS         (Development), V1.1Y  G         DEC SNA 3270 Application Services    6.1        Yes    Yes   No          (Run-Time), V1.1  H         DEC SoftWindows/SoftPC for OpenVMS,  6.1               Yes   Yes         V5.0  0         DEC TCP/IP Services for OpenVMS      6.1         AXP, V3.1.  0         DEC TCP/IP Services for OpenVMS      6.1         AXP, V3.2p  0         DEC TCP/IP Services for OpenVMS      6.1         AXP, V3.3   0         DEC TCP/IP Services/Japanese for     6.1         OpenVMS AXP, V3.0S  0         DEC TCP/IP Services/Japanese for     6.1         OpenVMS AXP, V3.1t  0         DEC TCP/IP Services/Japanese for     6.1         OpenVMS AXP, V3.2)  0         DEC Test Manager for OpenVMS AXP     6.1         Systems, V3.5   G         DEC Test Manager for OpenVMS AXP     6.2        Yes    No    Nor         Systems, V3.66  H         DEC X.25 Client for OpenVMS AXP      6.2        Yes    N/A   N/A         Systems, V1.1N  H         DEC X.500 Directory Services         6.1        N/A    Yes   Yes'         (Administration Facility), V1.3   I                                                  (continued on next page)   I                                                                      D-37O c  e      3     Layered Product Support for OpenVMS Version 6.2o      >     Table D-2 (Cont.) Digital Layered Products Compatible withE     __________________OpenVMS_Alpha_Version_6.2______________________   2                                          OperatingD                                          System       DECnet SupportE     Product and Version                  Support    _________________cE     _____________________________________(Qualified)Ph._IV_Syn___Full,  D     DEC X.500 Directory Services         6.1        N/A    Yes   Yes#     (Administration Facility), V2.0   D     DEC X.500 Directory Services         6.2        N/A    Yes   Yes$     (Administration Facility), V2.0A  D     DEC X.500 Directory Services         6.1        N/A    Yes   Yes     (Server), V1.3  D     DEC X.500 Directory Services         6.1        N/A    Yes   Yes     (Server), V2.0  D     DEC X.500 Directory Services         6.2        N/A    Yes   Yes     (Server), V2.0A   D     DEC X.500 Directory Services         6.1        N/A    Yes   Yes     (Starter Kit), V1.3e  D     DEC X.500 Directory Services         6.1        N/A    Yes   Yes     (Starter Kit), V2.0C  D     DEC X.500 Directory Services         6.2        N/A    Yes   Yes     (Starter Kit), V2.0A  C     DEC/EDI for OpenVMS AXP, V2.0        6.1        Yes    Yes   Nop  C     DEC/EDI for OpenVMS AXP, V2.1        6.2        Yes    Yes   Nou  D     DECADMIRE for OpenVMS AXP, V2.0A     6.1        N/A    N/A   N/A  D     DECADMIRE for OpenVMS AXP, V2.1A     6.2        N/A    N/A   N/A  D     DECADMIRE/Japanese for OpenVMS,      6.1        N/A    N/A   N/A     V2.0  C     DECdfs for OpenVMS Systems, V2.0     6.1        Yes    Yes   No   D     DECdfs for OpenVMS Systems, V2.1     6.2        Yes    Yes   Yes  D     DECdocument for OpenVMS AXP          6.2        N/A    N/A   N/A     Systems, V2.3   D     DECforms /Hangul for OpenVMS AXP     6.1        N/A    N/A   N/A     (Development), V1.4C  E                                              (continued on next page)v       D-38 g  f      I                           Layered Product Support for OpenVMS Version 6.2V      B         Table D-2 (Cont.) Digital Layered Products Compatible withI         __________________OpenVMS_Alpha_Version_6.2______________________A  6                                              OperatingG                                              System      DECnet Support.I         Product and Version                  Support    _________________6I         _____________________________________(Qualified)Ph._IV_Syn___Full   H         DECforms /Hangul for OpenVMS AXP     6.1        N/A    N/A   N/A         (Run-Time), V1.4AN  H         DECforms /Hangul for OpenVMS AXP     6.1        N/A    N/A   N/A         (Run-Time), V1.4C   H         DECforms /Hanyu for OpenVMS AXP      6.1        N/A    N/A   N/A         (Development), V1.4C  H         DECforms /Hanyu for OpenVMS AXP      6.1        N/A    N/A   N/A         (Run-Time), V1.4A   H         DECforms /Hanyu for OpenVMS AXP      6.1        N/A    N/A   N/A         (Run-Time), V1.4C_  H         DECforms /Japanese for OpenVMS AXP   6.1        N/A    N/A   N/A         (Run-Time), V1.4  H         DECforms /Thai for OpenVMS AXP       6.1        N/A    N/A   N/A         (Run-Time), V1.4A_  0         DECforms for OpenVMS AXP             6.2         (Development), V1.4C  H         DECforms for OpenVMS AXP             6.2        N/A    N/A   N/A         (Development), V1.4D  H         DECforms for OpenVMS AXP             6.2        N/A    N/A   N/A         (Development), V2.1   0         DECforms for OpenVMS AXP (Run-       6.2         Time), V1.4C  H         DECforms for OpenVMS AXP (Run-       6.2        N/A    N/A   N/A         Time), V1.4D  H         DECforms for OpenVMS AXP (Run-       6.2        N/A    N/A   N/A         Time), V2.1   0         DECmessageQ for OpenVMS AXP (Run-    6.1         Time), V2.0B  I                                                  (continued on next page)f  I                                                                      D-39  A  E      3     Layered Product Support for OpenVMS Version 6.2       >     Table D-2 (Cont.) Digital Layered Products Compatible withE     __________________OpenVMS_Alpha_Version_6.2______________________E  2                                          OperatingD                                          System       DECnet SupportE     Product and Version                  Support    _________________oE     _____________________________________(Qualified)Ph._IV_Syn___FullI  C     DECmessageQ for OpenVMS AXP (Run-    6.1        Yes    No    NoE     Time), V2.0C  C     DECmessageQ for OpenVMS AXP (Run-    6.2        Yes    Yes   No      Time), V3.0   ,     DECmessageQ for OpenVMS AXP Systems  6.1     (Development), V2.0B  C     DECmessageQ for OpenVMS AXP Systems  6.1        Yes    No    Nor     (Development), V2.0C  C     DECmessageQ for OpenVMS AXP Systems  6.2        Yes    Yes   Noi     (Development), V3.0a  D     DECmigrate for OpenVMS AXP Systems,  6.1        N/A    N/A   N/A     V1.1  D     DECmigrate for OpenVMS AXP Systems,  6.2        N/A    N/A   N/A	     V1.1A   ,     DECnet for OpenVMS AXP, V5.7         6.1  D     DECnet for OpenVMS AXP, V5.8         6.1        Yes    Yes   Yes  ,     DECnet for OpenVMS AXP, V6.1         6.1  D     DECnet for OpenVMS AXP, V6.1         6.1        N/A    Yes   Yes  D     DECnet for OpenVMS AXP, V6.2         6.2        N/A    Yes   Yes  C     DECnet SNA 3270 Data Stream          6.1        Yes    Yes   No &     Programming Interface for OpenVMS,     V1.4  ,     DECnet SNA 3270 Data Stream          6.1%     Programming Interface for OpenVMS      /Japanese, V1.4   C     DECnet SNA 3270 Terminal Emulator    6.1        Yes    Yes   No      for OpenVMS, V1.5a  C     DECnet SNA 3270 Terminal Emulator    6.1        Yes    No    No       /Japanese for OpenVMS, V1.5A  E                                              (continued on next page)D       D-40           I                           Layered Product Support for OpenVMS Version 6.2O      B         Table D-2 (Cont.) Digital Layered Products Compatible withI         __________________OpenVMS_Alpha_Version_6.2______________________   6                                              OperatingG                                              System      DECnet SupporteI         Product and Version                  Support    _________________ I         _____________________________________(Qualified)Ph._IV_Syn___Full   G         DECnet SNA APPC/LU6.2 Programming    6.1        Yes    Yes   No #         Interface for OpenVMS, V2.2a  G         DECnet SNA Application Programming   6.1        Yes    Yes   Nos#         Interface for OpenVMS, V2.3   G         DECnet SNA Data Transfer Facility    6.1        Yes    Yes   No "         for OpenVMS (Server), V3.1  G         DECnet SNA Data Transfer Facility    6.1        Yes    Yes   No_#         for OpenVMS (Utility), V3.1_  0         DECnet SNA DTF/Japanese for OpenVMS  6.1         (Utilities), V3.1   0         DECnet SNA DTF/Japanese for OpenVMS  6.1         AXP (Server), V3.1  G         DECnet SNA Gateway for Channel       6.1        Yes    Yes   No          Transport, V2.1a  G         DECnet SNA Gateway for Synchronous   6.1        Yes    Yes   No          Transport, V1.2   G         DECnet SNA Printer Emulator for      6.1        Yes    Yes   Noi         OpenVMS, V1.2   0         DECnet SNA Printer Emulator          6.1(         /Japanese for OpenVMS AXP, V1.2A  G         DECnet SNA Remote Job Entry for      6.1        Yes    Yes   NoE         OpenVMS, V1.4R  G         DECnet SNA Remote Job Entry          6.1        Yes    Yes   Nog$         /Japanese for OpenVMS, V1.4A  0         DECnet/OSI for OpenVMS Alpha AXP,    6.1         V5.7  H         DECnet/OSI for OpenVMS Alpha AXP,    6.1        Yes    Yes   Yes         V5.8  I                                                  (continued on next page)D  I                                                                      D-41     N      3     Layered Product Support for OpenVMS Version 6.2e      >     Table D-2 (Cont.) Digital Layered Products Compatible withE     __________________OpenVMS_Alpha_Version_6.2______________________/  2                                          OperatingD                                          System       DECnet SupportE     Product and Version                  Support    _________________nE     _____________________________________(Qualified)Ph._IV_Syn___Full   ,     DECnet/OSI for OpenVMS Alpha AXP,    6.1     V6.1  D     DECnet/OSI for OpenVMS Alpha AXP,    6.1        N/A    Yes   Yes     V6.1  D     DECnet/OSI for OpenVMS Alpha AXP,    6.2        N/A    Yes   Yes     V6.2  D     DEComni API, V2.2                    6.1        N/A    N/A   N/A  ,     DEComni MMS, V2.2                    6.1  D     DECosap/AP for OpenVMS AXP, V2.0     6.1        N/A    N/A   N/A  D     DECosap/H1 for OpenVMS AXP, V2.0     6.1        N/A    N/A   N/A  C     DECprint Supervisor for OpenVMS      6.1        Yes    No    No 
     AXP, V1.1   C     DECprint Supervisor for OpenVMS      6.1        Yes    No    No      AXP, V1.1A  C     DECprint Supervisor for OpenVMS      6.2        Yes    No    No 
     AXP, V1.2t  ,     DECprint Supervisor/Japanese for     6.1     OpenVMS, V1.0   ,     DECprint Supervisor/Japanese for     6.1     OpenVMS, V1.1X  D     DECram for OpenVMS, V2.1             6.2        N/A    N/A   N/A  ,     DECserver Network Access Software,   6.1     V1.3  C     DECset for OpenVMS AXP Systems,      6.1        Yes    No    No 	     V11.2D  ,     DECset for OpenVMS AXP Systems,      6.2	     V12.0   C     DECwindows DECnet SNA 3270 Terminal  6.1        Yes    Yes   No/     Emulator for OpenVMS, V2.0  E                                              (continued on next page)        D-42 s  Y      I                           Layered Product Support for OpenVMS Version 6.2e      B         Table D-2 (Cont.) Digital Layered Products Compatible withI         __________________OpenVMS_Alpha_Version_6.2______________________   6                                              OperatingG                                              System      DECnet Support I         Product and Version                  Support    _________________oI         _____________________________________(Qualified)Ph._IV_Syn___Full   G         DECwindows DECnet SNA 3270 Terminal  6.1        Yes    No    No &         Emulator for OpenVMS/Japanese,
         V2.0A   H         DECwindows Motif for OpenVMS AXP,    6.2        Yes    Yes   Yes         V1.2  H         DECwindows Motif for OpenVMS AXP,    6.2        Yes    Yes   Yes         V1.2-3  H         DECwindows Motif OpenVMS User        6.1        Yes    Yes   Yes         Interface/Cesky, V1.1A  H         DECwindows Motif OpenVMS User        6.1        Yes    Yes   Yes         Interface/Cesky, V1.2_  0         DECwindows Motif OpenVMS User        6.1         Interface/Deutsch, V1.1   H         DECwindows Motif OpenVMS User        6.1        Yes    Yes   Yes         Interface/Deutsch, V1.2   0         DECwindows Motif OpenVMS User        6.1         Interface/Espaol, V1.1Y  H         DECwindows Motif OpenVMS User        6.1        Yes    Yes   Yes         Interface/Espaol, V1.2r  0         DECwindows Motif OpenVMS User        6.1          Interface/Franais, V1.1  H         DECwindows Motif OpenVMS User        6.1        Yes    Yes   Yes          Interface/Franais, V1.2  0         DECwindows Motif OpenVMS User        6.1          Interface/Italiano, V1.1  H         DECwindows Motif OpenVMS User        6.1        Yes    Yes   Yes          Interface/Italiano, V1.2  0         DECwindows Motif OpenVMS User        6.1         Interface/Magyar, V1.1A1  I                                                  (continued on next page)3  I                                                                      D-43A           3     Layered Product Support for OpenVMS Version 6.2O      >     Table D-2 (Cont.) Digital Layered Products Compatible withE     __________________OpenVMS_Alpha_Version_6.2______________________   2                                          OperatingD                                          System       DECnet SupportE     Product and Version                  Support    _________________ E     _____________________________________(Qualified)Ph._IV_Syn___Full   D     DECwindows Motif OpenVMS User        6.1        Yes    Yes   Yes     Interface/Magyar, V1.2  ,     DECwindows Motif OpenVMS User        6.1     Interface/Polski, V1.1  D     DECwindows Motif OpenVMS User        6.1        Yes    Yes   Yes     Interface/Polski, V1.2  ,     DECwindows Motif OpenVMS User        6.1     Interface/Russkij, V1.1A  D     DECwindows Motif OpenVMS User        6.1        Yes    Yes   Yes     Interface/Russkij, V1.2   ,     DECwindows Motif OpenVMS User        6.1     Interface/Slovensky, V1.1A  D     DECwindows Motif OpenVMS User        6.1        Yes    Yes   Yes     Interface/Slovensky, V1.2   ,     DECwindows Motif OpenVMS User        6.1     Interface/Svenska, V1.1   D     DECwindows Motif OpenVMS User        6.1        Yes    Yes   Yes     Interface/Svenska, V1.2   D     DECwindows Motif/Hangul for OpenVMS  6.1        Yes    Yes   Yes
     AXP, V1.2.  D     DECwindows Motif/Hanyu for OpenVMS   6.1        Yes    Yes   Yes
     AXP, V1.2p  D     DECwindows Motif/Hanzi for OpenVMS   6.1        Yes    Yes   Yes
     AXP, V1.2   ,     DECwindows Motif/Hebrew for OpenVMS  6.1
     AXP, V1.1   C     DECwindows Motif/Hebrew for OpenVMS  6.1        Yes    Yes   No 
     AXP, V1.2e  E                                              (continued on next page)t       D-44    e      I                           Layered Product Support for OpenVMS Version 6.26      B         Table D-2 (Cont.) Digital Layered Products Compatible withI         __________________OpenVMS_Alpha_Version_6.2______________________   6                                              OperatingG                                              System      DECnet SupportAI         Product and Version                  Support    _________________lI         _____________________________________(Qualified)Ph._IV_Syn___FullE  0         DECwindows Motif/Japanese for        6.1         OpenVMS AXP, V1.2   H         DECwindows Motif/Thai for OpenVMS    6.1        Yes    Yes   Yes         AXP, V1.2   H         DECwrite for OpenVMS AXP, V3.0       6.1        N/A    N/A   N/A  H         DECwrite/Deutsch for OpenVMS AXP,    6.1        N/A    N/A   N/A         V3.0  H         DECwrite/Franais for OpenVMS AXP,   6.1        N/A    N/A   N/A         V3.0  0         Digital Distributed Computing        6.2         Environment (DCE), V1.3   ;         Digital Extended Math Library for    6.1        N/A '         OpenVMS AXP (Development), V2.7_  ;         Digital Extended Math Library for    6.2        N/A-'         OpenVMS AXP (Development), V2.8A  ;         Digital Extended Math Library for    6.1        N/Ar$         OpenVMS AXP (Run-Time), V2.7  ;         Digital Extended Math Library for    6.2        N/An$         OpenVMS AXP (Run-Time), V2.8  H         Digital NAS Base Server 200 for      6.1        N/A    N/A   N/A!         OpenVMS AXP Systems, V5.0   H         Digital NAS Base Server 200 for      6.1        N/A    N/A   N/A"         OpenVMS AXP Systems, V5.0A  H         Digital NAS Base Server 200 for      6.1        N/A    N/A   N/A!         OpenVMS AXP Systems, V6.0   H         Digital NAS Client 150 for OpenVMS   6.1        N/A    N/A   N/A         AXP Systems, V5.1r  H         Digital NAS Client 150 for OpenVMS   6.1        N/A    N/A   N/A         AXP Systems, V5.26  I                                                  (continued on next page)   I                                                                      D-456           3     Layered Product Support for OpenVMS Version 6.2.      >     Table D-2 (Cont.) Digital Layered Products Compatible withE     __________________OpenVMS_Alpha_Version_6.2______________________   2                                          OperatingD                                          System       DECnet SupportE     Product and Version                  Support    _________________ E     _____________________________________(Qualified)Ph._IV_Syn___FullM  D     Digital NAS Client 150 for OpenVMS   6.1        N/A    N/A   N/A     AXP Systems, V6.0_  D     Digital NAS Client 250 for OpenVMS   6.1        N/A    N/A   N/A     AXP Workstations, V5.0  D     Digital NAS Client 250 for OpenVMS   6.1        N/A    N/A   N/A     AXP Workstations, V6.0  D     Digital NAS Production Server 400    6.1        N/A    N/A   N/A!     for OpenVMS AXP Systems, V5.0e  D     Digital NAS Production Server 400    6.1        N/A    N/A   N/A!     for OpenVMS AXP Systems, V6.0r  D     Digital NAS Server 300 for OpenVMS   6.1        N/A    N/A   N/A     AXP Systems, V5.0   D     Digital NAS Server 300 for OpenVMS   6.1        N/A    N/A   N/A     AXP Systems, V6.0   ,     DSM for OpenVMS AXP Systems, V6.3A   6.1  C     DSM for OpenVMS AXP Systems, V6.3B   6.1        Yes    No    No   C     DSM for OpenVMS AXP Systems, V6.3C   6.1        Yes    No    No   C     DSM for OpenVMS AXP Systems, V6.3D   6.2        Yes    No    No6  ,     DSM/Japanese for OpenVMS AXP         6.1     Systems, V6.2C  ,     DSM/Japanese for OpenVMS AXP         6.1     Systems, V6.3t  ,     International Lexicons for OpenVMS   6.1!     AXP (American Business), V1.1Y  ,     International Lexicons for OpenVMS   6.1      AXP (American English), V1.1  ,     International Lexicons for OpenVMS   6.1      AXP (American Medical), V1.1  E                                              (continued on next page)A       D-46 E  M      I                           Layered Product Support for OpenVMS Version 6.2e      B         Table D-2 (Cont.) Digital Layered Products Compatible withI         __________________OpenVMS_Alpha_Version_6.2______________________O  6                                              OperatingG                                              System      DECnet SupportyI         Product and Version                  Support    _________________NI         _____________________________________(Qualified)Ph._IV_Syn___Full   0         International Lexicons for OpenVMS   6.1#         AXP (British English), V1.1e  0         International Lexicons for OpenVMS   6.1         AXP (Danish), V1.1  0         International Lexicons for OpenVMS   6.1         AXP (Dutch), V1.1_  0         International Lexicons for OpenVMS   6.1         AXP (French), V1.1  0         International Lexicons for OpenVMS   6.1         AXP (German), V1.1  0         International Lexicons for OpenVMS   6.1         AXP (Italian), V1.16  0         International Lexicons for OpenVMS   6.1         AXP (Norwegian), V1.1   0         International Lexicons for OpenVMS   6.1         AXP (Portuguese), V1.1  0         International Lexicons for OpenVMS   6.1         AXP (Spanish), V1.1A  0         International Lexicons for OpenVMS   6.1         AXP (Swedish), V1.1   H         KAP for DEC C for OpenVMS AXP, V1.6  6.1        N/A    N/A   N/A  H         KAP for DEC C for OpenVMS AXP,       6.2        N/A    N/A   N/A
         V1.6A   H         KAP for DEC Fortran for OpenVMS,     6.2        N/A    N/A   N/A         V2.1  0         MACRO-64 Assembler for OpenVMS AXP   6.1         Systems, V1.1N  0         MAILbus 400 Application Program      6.1#         Interface for OpenVMS, V1.4   I                                                  (continued on next page)V  I                                                                      D-47O V  A      3     Layered Product Support for OpenVMS Version 6.2p      >     Table D-2 (Cont.) Digital Layered Products Compatible withE     __________________OpenVMS_Alpha_Version_6.2______________________r  2                                          OperatingD                                          System       DECnet SupportE     Product and Version                  Support    _________________ E     _____________________________________(Qualified)Ph._IV_Syn___Fulle  ,     MAILbus 400 Message Transfer Agent   6.1     for OpenVMS, V1.4   C     MUXserver 320/380/90 Remote          6.2        Yes    No    No      Terminal Server, V2.0   C     ObjectBroker for OpenVMS AXP         6.1        Yes    No    No      (Development), V2.5A  C     ObjectBroker for OpenVMS AXP (Run-   6.1        Yes    No    No      Time), V2.5A  C     Oracle CDD/Administrator for         6.1        Yes    No    No      OpenVMS Systems, V1.2   C     Oracle CDD/Repository for OpenVMS    6.1        Yes    No    Non     Systems, V5.3d  C     Oracle CDD/Repository for OpenVMS    6.1        Yes    No    No_     Systems, V6.1_  C     Oracle CODASYL DBMS (Development),   6.2        Yes    Yes   NoM	     V6.0A   C     Oracle CODASYL DBMS (Development),   6.2        Yes    Yes   No      V6.1  C     Oracle CODASYL DBMS (Run-Time),      6.2        Yes    Yes   Noa	     V6.0An  C     Oracle CODASYL DBMS (Run-Time),      6.2        Yes    Yes   Nop     V6.1  D     Oracle Expert for Rdb, V2.1A         6.1        N/A    N/A   N/A  D     Oracle Expert for Rdb, V3.0          6.1        N/A    N/A   N/A  D     Oracle Graphical Schema Editor for   6.1        N/A    N/A   N/A     Rdb, OpenVMS, V2.1A1  D     Oracle InstantSQL for Rdb, V2.1A     6.1        N/A    N/A   N/A  ,     Oracle RALLY, V4.0                   6.1  ,     Oracle RALLY, V4.0A                  6.1  E                                              (continued on next page)        D-48  I                           Layered Product Support for OpenVMS Version 6.2E    B         Table D-2 (Cont.) Digital Layered Products Compatible withI         __________________OpenVMS_Alpha_Version_6.2______________________m  6                                              OperatingG                                              System      DECnet SupportJI         Product and Version                  Support    _________________ I         _____________________________________(Qualified)Ph._IV_Syn___Full   0         Oracle RALLY (Development), V4.0     6.1  0         Oracle RALLY (Development), V4.0A    6.1  G         Oracle RALLY (MOTIF), V4.0           6.1        Yes    No    No   G         Oracle RALLY (MOTIF), V4.0A          6.1        Yes    No    No   0         Oracle RALLY (Run-Time), V4.0        6.1  0         Oracle RALLY (Run-Time), V4.0A       6.1  0         Oracle Rdb (Multiversion), V5.1A     6.1  G         Oracle Rdb (Multiversion), V6.0      6.1        Yes    Yes   No   G         Oracle Rdb (Multiversion), V6.0A     6.2        Yes    Yes   No   G         Oracle Rdb (Multiversion), V6.1      6.2        Yes    Yes   No_  0         Oracle Rdb (Standard), V5.1A         6.1  G         Oracle Rdb (Standard), V6.0          6.1        Yes    Yes   Noc  G         Oracle Rdb (Standard), V6.0A         6.2        Yes    Yes   No   G         Oracle Rdb (Standard), V6.1          6.2        Yes    Yes   Not  B         Oracle TRACE for OpenVMS, V2.1A      6.1        Yes    Yes  0         OSI Application Developer's Toolkit  6.1         for OpenVMS AXP, V2.2   G         PATHWORKS for OpenVMS, V5.0A         6.1        Yes    Yes   NoA  G         PATHWORKS for OpenVMS, V5.0B         6.1        Yes    Yes   Not  G         PATHWORKS for OpenVMS, V5.0C         6.2        Yes    Yes   NoE  G         PATHWORKS for OpenVMS (Macintosh),   6.2        Yes    Yes   Non         V1.3  G         PATHWORKS for OpenVMS (Netware),     6.2        Yes    Yes   No 
         V1.0Cr  0         PL/I for OpenVMS AXP Systems, V4.0   6.2  H         POLYCENTER Accounting Chargeback     6.1        Yes    Yes   Yes         for OpenVMS, V2.1   I                                                  (continued on next page)o  I                                                                      D-49  E  t      3     Layered Product Support for OpenVMS Version 6.2       >     Table D-2 (Cont.) Digital Layered Products Compatible withE     __________________OpenVMS_Alpha_Version_6.2______________________a  2                                          OperatingD                                          System       DECnet SupportE     Product and Version                  Support    _________________ E     _____________________________________(Qualified)Ph._IV_Syn___Fullo  C     POLYCENTER Archive/Backup for        6.1        Yes    No    No      OpenVMS, V2.4A  C     POLYCENTER Archive/Backup for        6.2        Yes    No    No      OpenVMS, V2.5B  D     POLYCENTER Capacity Planner for      6.1        Yes    N/A   N/A     OpenVMS, V2.1   D     POLYCENTER Capacity Planner for      6.1        Yes    N/A   N/A     OpenVMS, V2.1A  D     POLYCENTER Capacity Planner for      6.1        Yes    N/A   N/A     OpenVMS, V3.0   D     POLYCENTER Capacity Planner for      6.1        Yes    N/A   N/A     OpenVMS, V3.0A  D     POLYCENTER Console Manager for       6.1        N/A    N/A   N/A     OpenVMS, V1.1   D     POLYCENTER Console Manager for       6.1        N/A    N/A   N/A     OpenVMS, V1.5   C     POLYCENTER File Optimizer for        6.2        Yes    No    No      OpenVMS, V2.0N  D     POLYCENTER File Optimizer for        6.2        N/A    N/A   N/A     OpenVMS, V2.1S  D     POLYCENTER Hierarchical Storage      6.1        Yes    N/A   N/A      Management for OpenVMS, V1.0  D     POLYCENTER Hierarchical Storage      6.1        Yes    N/A   N/A!     Management for OpenVMS, V1.0A   D     POLYCENTER Hierarchical Storage      6.2        Yes    N/A   N/A      Management for OpenVMS, V1.1  ,     POLYCENTER Installation for          6.1     OpenVMS, V1.0   E                                              (continued on next page)        D-50 r  c      I                           Layered Product Support for OpenVMS Version 6.2       B         Table D-2 (Cont.) Digital Layered Products Compatible withI         __________________OpenVMS_Alpha_Version_6.2______________________e  6                                              OperatingG                                              System      DECnet Support2I         Product and Version                  Support    _________________MI         _____________________________________(Qualified)Ph._IV_Syn___Fullm  0         POLYCENTER Installation for          6.2         OpenVMS, V1.1_  H         POLYCENTER Performance Advisor for   6.1        Yes    Yes   Yes         OpenVMS, V2.1   H         POLYCENTER Performance Data          6.1        Yes    Yes   Yes#         Collector for OpenVMS, V2.1_  0         POLYCENTER Save Set Manager for      6.2         OpenVMS, V1.1_  H         POLYCENTER Scheduler for OpenVMS,    6.1        Yes    Yes   Yes
         V2.1B   H         POLYCENTER Scheduler for OpenVMS     6.1        Yes    Yes   Yes         (Agent), V2.1B  G         POLYCENTER Security Compliance       6.1        Yes    Yes   NoS"         Manager for OpenVMS, V2.3A  0         POLYCENTER Security Intrusion        6.1&         Detector for OpenVMS AXP, V1.2  H         POLYCENTER Sequential Media          6.2        N/A    N/A   N/A)         Filesystem for OpenVMS VAX/Alpha,n         V1.1  G         POLYCENTER Software Distribution,    6.1        Yes    Yes   Noc         V3.0  G         POLYCENTER Software Distribution,    6.2        Yes    Yes   NoY         V3.1  G         POLYCENTER System Census Agent for   6.1        Yes    Yes   No          OpenVMS, V1.3o  G         POLYCENTER System Census             6.1        Yes    Yes   NoY&         Consolidator for OpenVMS, V1.3  G         POLYCENTER System Census GUI for     6.1        Yes    Yes   Nor         OpenVMS, V1.3   I                                                  (continued on next page)e  I                                                                      D-51     e      3     Layered Product Support for OpenVMS Version 6.2e      >     Table D-2 (Cont.) Digital Layered Products Compatible withE     __________________OpenVMS_Alpha_Version_6.2______________________/  2                                          OperatingD                                          System       DECnet SupportE     Product and Version                  Support    _________________eE     _____________________________________(Qualified)Ph._IV_Syn___Full   C     POLYCENTER System Watchdog (Agent),  6.2        Yes    Yes   No_     V2.2  C     POLYCENTER System Watchdog           6.2        Yes    Yes   No      (Consolidator), V2.2  D     POSIX for OpenVMS AXP, V2.0          6.2        Yes    Yes   Yes  C     PrintServer Software, V5.0           6.2        Yes    No    No_  C     PrintServer Software, V5.0B          6.2        Yes    No    Noo  C     PrintServer/Japanese Software for    6.2        Yes    No    No/     OpenVMS, V5.0   C     Reliable Transaction Router for      6.2        Yes    Yes   No      OpenVMS AXP (Client), V2.2B   C     Reliable Transaction Router for      6.2        Yes    Yes   NoE     OpenVMS AXP (Client), V2.2C   C     Reliable Transaction Router for      6.2        Yes    Yes   No &     OpenVMS AXP (Full Function), V2.2B  C     Reliable Transaction Router for      6.2        Yes    Yes   No1&     OpenVMS AXP (Full Function), V2.2C  D     RMS Journaling for OpenVMS AXP,      6.1        N/A    N/A   N/A     V6.1  D     RMS Journaling for OpenVMS AXP,      6.2        N/A    N/A   N/A     V6.2  D     SSU (Session Support Utility) for    6.1        Yes    Yes   Yes     OpenVMS Systems, V2.0v  C     Storage Library System (SLS) for     6.1        Yes    No    No      OpenVMS AXP (ACS), V2.4A  C     Storage Library System (SLS) for     6.2        Yes    No    No      OpenVMS AXP (ACS), V2.5B  C     Storage Library System (SLS) for     6.1        Yes    No    No $     OpenVMS AXP (Development), V2.4A  E                                              (continued on next page)1       D-52 Y         I                           Layered Product Support for OpenVMS Version 6.2n      B         Table D-2 (Cont.) Digital Layered Products Compatible withI         __________________OpenVMS_Alpha_Version_6.2______________________i  6                                              OperatingG                                              System      DECnet Support I         Product and Version                  Support    _________________ I         _____________________________________(Qualified)Ph._IV_Syn___Full   G         Storage Library System (SLS) for     6.2        Yes    No    No_(         OpenVMS AXP (Development), V2.5B  G         Storage Library System (SLS) for     6.1        Yes    No    No #         OpenVMS AXP (Remote), V2.4A   G         Storage Library System (SLS) for     6.2        Yes    No    Noi#         OpenVMS AXP (Remote), V2.5B   G         StorageWorks Desktop Backup          6.1        Yes    No    No '         /Archiver for OpenVMS AXP, V2.0   G         StorageWorks Desktop Backup          6.2        Yes    No    No (         /Archiver for OpenVMS AXP, V2.0B  0         StorageWorks RAID Software for       6.1         OpenVMS, V2.0d  0         StorageWorks RAID Software for       6.1         OpenVMS, V2.1V  H         StorageWorks RAID Software for       6.2        N/A    N/A   N/A         OpenVMS, V2.2e  0         TeamRoute for ALL-IN-1 OpenVMS AXP,  6.2         V1.3  0         Terminal Server Manager, V2.1        6.1  0         VMScluster Software for OpenVMS      6.1         AXP, V6.1n  H         Volume Shadowing for OpenVMS AXP,    6.1        N/A    N/A   N/A         V6.1  H         Volume Shadowing for OpenVMS AXP,    6.2        N/A    N/A   N/A         V6.2  0         X.25 for OpenVMS AXP Systems, V1.0   6.2  I         X.25_for_OpenVMS_AXP_Systems,_V1.0A__6.2________No_____Yes___Yes_/  I                                                                      D-53e 1  3     Layered Product Support for OpenVMS Version 6.2X  B     Table D-3 Digital Layered Products Compatible with OpenVMS VAXE     __________Version_6.2_After_May_1995_____________________________   ,                                     SoftwareD                                     Library           DECnet SupportE     Product and Version             Availability    _________________ E     ________________________________________________Ph._IV_Syn___Fulla  C     ALL-IN-1 Integrated Office      Dec 95-May 96   N/A    Yes   No_!     System Server for VMS (MUPA),      V3.2  C     ALL-IN-1 Office Server Options  Dec 95-May 96   N/A    Yes   No      for OpenVMS AXP and OpenVMS 
     VAX, V3.2   D     DEC C for OpenVMS VAX Systems,  Dec 95-May 96   N/A    N/A   N/A     V5.1  D     DEC Pascal for OpenVMS, V5.4    Sep 95-Nov 95   Yes    Yes   Yes  D     DEC TCP/IP Services for         Sep 95-Nov 95   N/A    N/A   N/A     OpenVMS, V4.0V  C     DEC VTX Version OpenVMS VAX,    Dec 95-May 96   Yes    No    Noi     V7.0  C     DEC/EDI for OpenVMS VAX, V2.1A  Sep 95-Nov 95   Yes    Yes   Nos  D     DECnet/OSI Version for OpenVMS  Dec 95-May 96   N/A    Yes   Yes
     VAX, V7.0   D     DECwrite for OpenVMS VAX, V3.1  Sep 95-Nov 95   N/A    N/A   N/A  C     DSM Version for OpenVMS VAX     Sep 95-Nov 95   Yes    No    Noi     Systems, V7.00  D     NAS Base Server 200 for         Sep 95-Nov 95   N/A    N/A   N/A     OpenVMS VAX Systems, V7.0e  D     NAS Client 150 for OpenVMS VAX  Sep 95-Nov 95   N/A    N/A   N/A     Workstations, V7.0  D     NAS Client 250 for OpenVMS VAX  Sep 95-Nov 95   N/A    N/A   N/A     Workstations, V7.0  D     NAS Production Server 400 for   Sep 95-Nov 95   N/A    N/A   N/A     OpenVMS VAX Systems, V7.06  D     NAS Server 300 for OpenVMS VAX  Sep 95-Nov 95   N/A    N/A   N/A     Systems, V7.0.  C     OpenDATA Manager for OpenVMS,   Sep 95-Nov 95   No     No    No      V1.2  >     PATHWORKS for VMS, V5.0D        Dec 95-May 96   Yes    Yes  >     PATHWORKS for VMS, V6.0         Jan 97-Apr 97   Yes    Yes  E                                              (continued on next page)        D-54    C     POLYCENTER Saveset Manager for  Dec 95-May 96   Yes    No    Noe     OpenVMS, V1.2   7     POLYCENTER Capacity Planner,    Sep 95-Nov 95   Yesr	     V3.0Ar  C     POLYCENTER Scheduler OpenVMS,   Dec 95-May 96   Yes    Yes   Noe     V3.0  C     POLYCENTER Scheduler OpenVMS    Dec 95-May 96   Yes    Yes   No_     (Agent), V3.0_  C     POLYCENTER Scheduler OpenVMS    Dec 95-May 96   Yes    Yes   No      (Client), V3.0  C     POLYCENTER Scheduler OpenVMS    Dec 95-May 96   Yes    Yes   No      (Server), V3.0  C     Reliable Transaction Router     Sep 95-Nov 95   Yes    Yes   No_"     for OpenVMS VAX (Client), V3.2  C     Reliable Transaction Router     Sep 95-Nov 95   Yes    Yes   Nog"     for OpenVMS VAX (Server), V3.2  C     StorageWorks Desktop Backup     Sep 95- Nov 95  Yes    No    Noe!     /Archiver Backup Server, V2.11  D     VAX COBOL for OpenVMS VAX,      Sep 95-Nov 95   Yes    Yes   Yes     V5.3  C                                                                D-55S 6I                           Layered Product Support for OpenVMS Version 6.2S  H         Table D-4 Digital Layered Products Compatible with OpenVMS AlphaI         __________Version_6.2_After_May_1995_____________________________o  0                                         SoftwareG                                         Library          DECnet SupporthI         Product and Version             Availability    _________________SI         ________________________________________________Ph._IV_Syn___Full/  5         ACMS/Japanese for OpenVMS,      Sep 95-Nov 95          V4.0  H         DEC C for OpenVMS AXP Systems,  Dec 95-May 96   Yes    Yes   Yes         V5.1  G         DEC COBOL for OpenVMS Alpha     Dec 95-May 96   Yes    No    NoS         Systems, V2.3t  G         DEC Data Distributor Version    Sep 95-Nov 95   Yes    Yes   Noe         for OpenVMS AXP, V6.1   H         DEC GKS for OpenVMS AXP         Sep 95-Nov 95   Yes    Yes   Yes#         Systems (Development), V6.1   H         DEC GKS for OpenVMS AXP         Sep 95-Nov 95   Yes    Yes   Yes          Systems (Run-Time), V6.1  H         DEC Optical Storage Desktop     Sep 95-Nov 95   N/A    N/A   N/A#         Software (OSDS) for OpenVMS_         AXP, V3.3r  H         DEC Optical Storage Management  Sep 95-Nov 95   N/A    N/A   N/A#         Software (OSMS) for OpenVMSn         AXP, V3.3d  H         DEC Pascal for OpenVMS AXP      Sep 95-Nov 95   Yes    Yes   Yes         Systems, V5.4_  H         DEC PHIGS for OpenVMS AXP       Sep 95-Nov 95   Yes    Yes   Yes#         Systems (Development), V3.2   H         DEC PHIGS for OpenVMS AXP       Sep 95-Nov 95   Yes    Yes   Yes          Systems (Run-Time), V3.2  G         DEC/EDI for OpenVMS AXP, V2.1A  Sep 95-Nov 95   Yes    Yes   NoV  H         DECnet for OpenVMS AXP, V6.3    Sep 95-Nov 95   N/A    Yes   Yes  H         DECnet/OSI for OpenVMS Alpha    Sep 95-Nov 95   N/A    Yes   Yes         AXP, V6.3   5         DECprint Supervisor for XEROX   Sep 95-Nov 95p         for OpenVMS AXP, V1.0 F                                               (continued on next page)       D-56 NN       Table D-4 (Cont.) Digital Layered Products Compatible with OpenVMS AlphaG       __________Version_6.2_After_May_1995_____________________________,  0                                         SoftwareG                                         Library          DECnet Support I         Product and Version             Availability    _________________ I         ________________________________________________Ph._IV_Syn___FullA  H         DECwrite for OpenVMS AXP, V3.1  Sep 95-Nov 95   N/A    N/A   N/A  5         Digital Cartridge Server        Sep 95-Nov 95          Component for VMS, V3.01  H         Digital NAS Base Server 200     Sep 95-Nov 95   N/A    N/A   N/AE         for OpenVMS AXP Systems, V7.0                                0  H         Digital NAS Client 150 for      Sep 95-Nov 95   N/A    N/A   N/A!         OpenVMS AXP Systems, V7.0   H         Digital NAS Client 250 for      Sep 95-Nov 95   N/A    N/A   N/A&         OpenVMS AXP Workstations, V7.0  H         Digital NAS Production Server   Sep 95-Nov 95   N/A    N/A   N/A$         400 for OpenVMS AXP Systems,         V7.0  H         Digital NAS Server 300 for      Sep 95-Nov 95   N/A    N/A   N/A!         OpenVMS AXP Systems, V7.0J  H         ObjectBroker for OpenVMS AXP    Sep 95-Nov 95   Yes    No    Yes         (Development), V2.5B  H         ObjectBroker for OpenVMS AXP    Sep 95-Nov 95   Yes    No    Yes         (Run-Time), V2.5B   G         POLYCENTER Archive/Backup for   Sep 95-Nov 95   Yes    No    NoI         OpenVMS, V1.0   H         POLYCENTER Console Manager for  Sep 95-Nov 95   N/A    N/A   N/A         OpenVMS, V1.6   H         POLYCENTER Security Compliance  Sep 95-Nov 95   Yes    Yes   Yes!         Manager for OpenVMS, V3.0   G         Reliable Transaction Router     Sep 95-Nov 95   Yes    Yes   Noi&         for OpenVMS AXP (Client), V3.2  G         Reliable Transaction Router     Sep 95-Nov 95   Yes    Yes   NoN         for OpenVMS AXP (Fullv         Function), V3.2   G         Storage Library System (SLS)    Sep 95-Nov 95   Yes    No    No &         for OpenVMS AXP (Development),         V1.0  H         StorageWorks Array Controller   Sep 95-Nov 95   N/A    N/A   N/A"         Facility for OpenVMS, V1.0  H                                                                     D-57 A  f                            F      _________________________________________________________________  F                                                                  Index      ;      A                                 ALPHAVMSSYS.PAR file.B      _______________________________     VMScluster system startup9      Account removal problem                problem, 3-63A7        with POLYCENTER Software        .ASCIZ directive @          Installation utility,  4-80     Macro assembler,  4-115:      AGEN$PARAMS.REPORT                Audio Editor,  1-12.        managing (Alpha only), 3-2      AUTOGENA      Alpha                               changes and enhancements D        firmware revisions, 1-13             computing SYSMWCNT,  3-3A      AlphaServer 1000 systems               computing WSMAX,  3-4 D        graphics restrictions, 1-16          CTLPAGES parameter,  3-2A        graphics support, 1-14               dump file sizes,  3-2.D      AlphaServer 2100 systems               retired parameters,  3-3B        change in console variable,       problems and restrictionsC          1-13                               full memory dumps,  3-4       AlphaStation 1000F        KFESA Port is Reinitializing    B______________________________5          message,  1-17                BACKUP commandfF      AlphaStation series computers       failure on VAX 4000 Model 300:        enabling graphics, 1-16              and TF857, 3-9>        graphics support, 1-14          Backup utility (BACKUP)4        problems and restrictions         correctionsD           adapter support, 1-14             BACKUP$_ACCONFLICT error=           DECterm startup, 1-15                messages, 3-11,?           disk support, 1-17                incremental restore ?           Ethernet wire settings,              operations, 3-12e@             1-15                            save operation error=           graphics support, 1-15               messages, 3-14AB           halting the system, 1-17          saving the boot block,3           SCSI controllers, 1-17               3-11OB           window corruption, 1-18        problems and restrictionsE        system board resources, A-18         blocks incorrectly marked/F                                                allocated warnings, 3-6  F                                                                Index-1 O  E              =     Backup utility (BACKUP)            Batch and print queuesrA       problems and restrictions         problems and restrictions 3          (cont'd)                          (cont'd)1B          incremental backups,  3-5         terminating batch jobs,1          incremental backups using            4-1oE             PATHWORKS, 3-5              VMScluster environment,  3-15 1       relative file versions,  3-8     Batch jobs D       restrictions,  3-4                specifying printer queue for9       saving and restoring alias           log file, 4-94_>          directories, 3-9              Before-image journaling:     BACKUP utility (BACKUP)             restriction,  3-44A       system disk backup,  3-7         BLAS$ functions invoked by B     BASIC                                translated images,  4-111C       translated images,  4-111        BLAS1RTL translated library,s.     Batch and print queues               4-111.       corrections                      BootingC          aligning print jobs,  2-2      TURBOchannel devices,  3-47Y9          displaying open jobs,  4-3    Booting the systems@          file search qualifiers,        spurious messages,  1-12-             2-1                        Branch_@          form feeding,  3-16            target of indeterminate,/          $GETQUI error message,            4-75S             4-3VF          LAT initialization timing,    C______________________________?             3-16                       C structure member names B          log files,  4-3                passing restriction,  4-61@          maintaining log file names,   CANCEL SELECTIVE functionC            4-3                          improved use with LTDRIVER, /          modified symbionts,  3-17         4-73 >          START/QUEUE/TOP_OF_FILE       CASE instruction, 4-1168             command, 4-4               CHKABSADR messageC          stock-type mismatch,  3-16     suppressing during MACRO-32 <          suppressing error messages,       compilation, 4-76?             3-17                       CI lines unsupported forsD          symbiont BADLOGIC dumps,        DECnet communication,  3-225             4-4                        Circumflex (^) >          TASK_STATUS message,  4-4      use restriction,  4-75C       problems and restrictions        /CLUSTER qualifier (SYSMAN), -          PRINT/DELETE command,           3-52 D             3-15                       COBOL programs support, 4-115=          process rights identifier,    COM$DRVDEALMEM routine >             3-14                        synchronization,  4-64          SUBMIT/DELETE command,_             3-15       Index-2                    6         Concurrency                       DCL commands@          improved in VMScluster             corrections (cont'd)F             systems,  3-62                     SET QUEUE/NODESCRIPTION>         Console variable                         command,  2-4G          default change on AlphaServer         SHOW SYSTEM command, 2-4dG             2100 systems,  1-13                START/QUEUE command, 2-5 B         Controller-based volume                SUBMIT command, 2-5G           shadowing                            SUBMIT/NAME command, 2-5 H          See Volume shadowing                  SUBMIT/NAME/USER command,4         CRB$L_INTD field                         2-62          interrupt vector,  4-64          DCL HelpC         $CREATE_USER_PROFILE system         affected during layeredCC           service,  4-96                      product installation, 6                                               1-5, 1-6<         D______________________________   DDCMP lines,  3-22=         DATA keyword                      DEBUG option,  4-77aA          workaround for linker overlay    /DEBUG qualifier,  4-77X2             restriction,  4-71            DebuggerD         Data loss                           changes and enhancementsE          RF73 and RFnn controller              VMSDEBUG.DAT file, 4-5 7                                             correctionsY@             memory errors,  1-20               breakpoints, 4-19F         Date/time formats, 4-97                COBOL STEP and GO, 4-20H         DCL commands                           Communications Pane size,5          changes and enhancements                4-20tC             ANALYZE/ERROR_LOG/SUMMARY          DEBUG.EXE name, 4-20pG                command,  3-17                  Edit Save function, 4-20nE             MOUNT/UCS_SEQUENCE command         EVALUATE command, 4-20eD                ,  3-17                         EXAMINE command, 4-20B          corrections                           Hebrew command view@             ANALYZE/DISK_STRUCTURE               messages,  4-21A                /REPAIR command,  3-18          lengthy output and B             DELETE/QUEUE/MANAGER                 performance,  4-5A                command,  2-3                   Monitor View, 4-21 G             INITIALIZE/QUEUE command,          multidimensional arrays, 5                2-3                               4-21e?             PRINT/DELETE command,  2-4         performance, 4-5 I             PRINT/FORM command,  2-4           PL/I controlled variables, 5             SET ACCOUNTING/NEW_FILE              4-21 G                command,  3-18                  process dump files, 4-21m<             SET ENTRY/NAME command,            radixes, 4-21G                2-5                             records with same symbol <             SET QUEUE/DESCRIPTION                name,  4-22E                command,  2-4                   reporting watchpoints,r  5                                                  4-22   I                                                                   Index-3     t              /     Debugger                           Debugger A       corrections (cont'd)              problems and restrictionsP3          RERUN/SAVE command,  4-22         (cont'd)eD          SCAN tree variables,  4-20        SHOW CALLS command,  4-10D          SET RADIX command,  4-22          SHOW TRACE command,  4-17E          SET SOURCE command,  4-22         SPAWN/NOWAIT command,  4-7rC          STEP/RET,  4-5                    stack corruption, effect 5          system service calls,                of, 4-65C             4-22                           STEP/INTO command,  4-18 C          updating include files in         STEP/OVER command,  4-9,e2             a text library, 4-21              4-189          watchpoints on bit fields,        system servicel?             4-22                              interception, 4-8_C       problems and restrictions            translated images,  4-18a@          CALL command,  4-10               using SET TASK/ACTIVEE          complex variables,  4-15             command for DECthreads,_1          CONNECT command,  4-7                4-7_@          DEBUG.EXE name,  4-8              vector support,  4-19D          DECwindows Motif,  4-11           watchpoint support,  4-10?          DECwindows Motif license      DEC 2000 Model 300, 4-69/0             requirements, 4-12         DEC C RTLA          Delta/XDelta and               changes and enhancements, /             translated images,             4-26rB             4-18                        problems and restrictions,/          DEPOSIT/TYPE command,             4-28 >             4-16                           DECC$SHR.EXE,  4-29.          detached processes,  4-7      DEC C++B          EVALUATE command,  4-13        class library corrections,5          EXAMINE LABEL command,            4-23, 4-24/C             4-13                        class library enhancements, /          $HIBER calls,  4-16               4-24o2          inlined routines,  4-17       DEC Fortran3          Kept Debugger,  4-13           See Fortran B          memory resources,  4-6        DEC Text Processing Utility1          null frame procedures,          (DECTPU)NB             4-17                        DECwindows Motif interfaceB          quotas,  4-6                      small display monitors,2          rooted-directory logical             4-339             names, 4-16                DECC$SHR.EXE, 4-2966          SET BREAK/UNALIGNED_DATA      DECdtm services@             command, 4-15               in a DECnet/OSI network,/          shared linkage images,            3-181A             4-8                         problems and restrictionss@          SHOW BREAK command,  4-17         SCSNODE values,  3-19       Index-4                    =         DECdtm services (cont'd)          DECthreads (cont'd)YA          transaction group                  .H file support, 4-92p0             example,  3-20                DECTPUC         DECevent, 3-21                      See DEC Text ProcessingS5          problems and restrictions            UtilityO>             device support,  3-21         DECTPU SET built-insH             page file quotas,  3-22         WIDGET_CONTEXT_HELP keyword,1             purging log files,  3-21          2-8T9             unrecognized error log        DECwindows mail >                messages,  3-22              Audio Editor, 1-12:             using Ctrl/C,  3-21           DECwindows MotifD             using logical file names,       changes and enhancementsA                3-21                            system files, 3-26B?         DECmigrate                          creating WSA pseudoSH          See also Translated Image            workstation devices,  3-29I             Environment (TIE) and           height and width restrictions 5             Translated image support          ,  3-28 E          support for translated images      problems and restrictionsaG             ,  4-31                            console broadcasts, 3-26.I          VEST,  4-99                           virtual data error message 8         DECnet                                   ,  3-26F          DECnet/OSI supersedes DECnet       starting the Start Session?             Phase IV,  2-6                    dialog box,  3-30_D         DECnet for OpenVMS Alpha            support by OpenVMS, 3-25C          restrictions,  3-22                TCP/IP support for NCSA C         DECnet for OpenVMS VAX (Phase         Mosaic browser,  3-25 D           IV),  3-23                        Version 1.2 restrictionsE         DECnet for OpenVMS VAX                 compatibility problemsiI           Extensions,  1-8                       with OpenVMS V6.2,  3-27 G         DECnet/OSI for OpenVMS VAX             World Wide Support, 3-26 D           (Phase V),  3-24                DECwindows Motif Transport;         DECpresent                          modifying, 4-34nF          installation dependencies        DECwindows Motif Version 1.18             with OpenVMS VAX,  1-8           for OpenVMSC         DECserver 700 terminal              support by OpenVMS, 2-8v:           controller                      DEFQA controllerH          LAT restriction,  2-7              NETCONFIG.COM support, 3-23,2         DECthreads                            3-24A          dynamic image-activation         DEFTA controller,  3-23YG             problem,  4-32                  NETCONFIG.COM support, 3-24 C          erroneous thread terminations    Delta/XDelta debugger and)B             ,  4-33                          image activator, 4-35&          exit handler routine problem,             4-32  I                                                                   Index-5e 5  v              @     Device driver coding               Documentation corrections1       MASSBUS adapters,  4-64            (cont'd) D     Device support                      OpenVMS I/O User's Reference7       debugging device drivers,            Manual, 4-68eE          4-60                           OpenVMS Linker Utility Manualf1       Step 2 driver interface,             , 4-72 D          4-36                           OpenVMS Programming Concepts7       user-written drivers,  4-36          Manual, 4-97rB       writing drivers in C,  4-36       OpenVMS VAX Device SupportA       writing drivers in Macro-32,         Reference Manual, 4-64F;          4-36                           POLYCENTER Software ?     Devices                                Installation Utility B       configuring with ISA_                Developer's Guide, 4-85E          CONFIG.DAT file, A-5,          VAX MACRO and Instruction SetMB          A-9                               Reference Manual, 4-115=     Digital 2100 Server Model A500     DPML (Digital Portable =        /600MP, 4-69                      Mathematics Library)2C     Digital Portable Mathematics        mathematical operations notk:        Library                             supported, 4-781       See DPML                         Dump filesn=     Digital Product Performance         See System dump files0C        program, 3-34                   Dump Off System Disk (DOSD),m-     Digital writers                      3-61P9       sending comments to,  iii        DUP Driver utility,@     /DISABLE qualifier,  4-77           using on VAX 4000 series:     Disks                                  computers, 1-24       RF73 and RFnn (          controller memory errors,     EF             1-20                       _______________________________>       RX23,  1-17                      /ENABLE qualifier, 4-773       RX26,  1-17                      Entry pointss>     DISMOUNT/CLUSTER command            when to declare,  4-754       volume shadowing restriction,    $EQULST macro;          3-68                           symbol value,  4-66T@     Documentation                      Error Reporting Formatter5       sending comments to Digital        (ERF),  3-21 ;          writers, iii                  Ethernet controllers >     Documentation corrections           problems with multiple<       Migrating to an OpenVMS AXP          controllers, 1-187          System: Recompiling and       Extended DDT bit @          Relinking Applications,        problem corrected,  4-73
          4-79 #       OpenVMS Delta/XDelta Debugger_          Manual, 4-36_       Index-6_ _  _                I         F______________________________   G______________________________   E         Fault management tools, 3-21      General register addressing_<         FDDI clusters                       assembler, 4-115G          restriction removed,  3-62       $GETQUI system service,  4-97wE         FDDI controllers                  Global symbols table,  4-63MB          problems with multiple           Granularity preservationE             controllers,  1-18              lost with INSV code, 4-74p2         FDDI to Q-bus controller          Graphics>          NETCONFIG.COM support,  3-23,      Cirrus graphics onG             3-24                              AlphaServer 1000 systems,,2         FDDI to TURBOchannel                  1-14H           controller                        Cirrus graphics restrictionsA          NETCONFIG.COM support,  3-24         on AlphaServer 1000i<         FDDI to TURBOchannel                  systems,  1-16D           controller (DEFTA),  3-23         enabling on AlphaStationE         Feedback on documentation             series computers,  1-16s$          sending comments to DigitalI             writers,  iii                 H______________________________A2         Firmware revisions                .H filesE          Alpha,  1-13                       from SYS$STARLET_C.TLB to9G         /FLAGGING=INSTRUCTIONS                support DECthreads,  4-92pD           qualifier,  4-77                  provided by SYS$STARLET_:         Floating-point return values          C.TLB,  4-928          requirement for "jacket",        Hash algorithmB             4-74                            security changes, 4-90G         $FORMAT_AUDIT system service      Help Message utility (MSGHLP) H          width argument,  4-95              restriction on user-supplied>         Fortran                               additions,  3-30          Mathematics RTLE             interoperability              Host-based volume shadowing @             restrictions,  4-77             See Volume shadowing          qualifier needed forAI             translated image support,     I______________________________              4-106d>                                           I/O write operations9         FTAM                                failure, 4-67uH          DECnet for OpenVMS VAX           IIFs (image information files)4             Extensions,  1-8                 , 4-100I                                             provided with Alpha software, :                                               4-106, 4-1089                                           Image Activator E                                             automatic activation with =                                               debugger,  4-35pE                                             new message returned, 2-9l  I                                                                   Index-7g    A              ;     Image information files            ISA bus, A-1 to A-24k=       See IIFs                          adding a device,  A-2 D     InfoServer                          configuration strategy,  A-2;       MADDRIVER restriction,  3-31      configuring devicesnE       updating software from               using ISA_CONFIG.DAT file, 1          ConDIST, 1-2                         A-5 =     InfoServer client software             using SYSMAN,  A-9-E       failure to start,  1-5            determining IRQ availability,o/     Initialization                         A-15 A       problem with recovery of root     entering IRQ assignments, .          directory, 3-31                   A-3>     Install utility (INSTALL)           troubleshooting,  A-17E       installing images change,         using device driver routines, /          3-32                              A-12g:     Installation and upgrade           ISA_CONFIG.DAT file5        information                      sample,  A-19cC       Alpha only,  1-9                  using to configure devices,V3     Installation and upgrade               A-5, A-9 /        restrictions                    ISO 9660t4       DECnet/OSI problems and           restrictionsD          restrictions, 1-3                 using /CLUSTER qualifier,2       DECpresent dependencies,  1-8           3-37#       layered product installations F          and DCL Help, 1-6             J______________________________  6       VAXstation and MicroVAX          Jacket routinesD          system hangs,  1-9             for mapping MTH$ routines toB     Installing and upgrading               DPML counterparts, 4-78       problems and restrictionsf(          DECnet/OSI versions,  1-4     KF     INSV instruction                   _______________________________,       impact on granularity,  4-74     KFESA>     Internal lock manager access        Port is Reinitializing8        code                                message, 1-17"       required modification,  4-73F     Interoperability,  4-79            L______________________________7       between native and translated    Layered products E          images, 4-100                  compatible with OpenVMS Alpha <     Interrupt Request Line                 Version 6.2, D-28E       See IRQ                           compatible with OpenVMS Alpha @     IRQ                                    Version 6.2 after May5       determining availability,            1995, D-55rC          A-15                           compatible with OpenVMS VAX ;       entering assignments,  A-3           Version 6.2, D-3                Index-8                    6         Layered products (cont'd)         Lock managerD          compatible with OpenVMS VAX        synchronization changes,2             Version 6.2 after May             4-721             1995,  D-54                   Logging E          installations with POLYCENTER      turning off (Alpha only), 1             Software Installation             3-2_7             Utility,  1-5                 Logical names E          installations with VMSINSTAL,      run-time libraries, 4-112lC             1-6                             systemwide definitions, 3          versions supported for               4-109 E             OpenVMS Version 6.2,  D-1     LTDRIVER restriction,  4-73 *         LCKMGR                            J          spin lock for standalone         M_______________________________9             OpenVMS Alpha systems,        Macro directive,9             4-72                            .ASCIZ, 4-115o;         LIB$FIND_IMAGE_SYMBOL routine,    MACRO-32 Compiler B           4-105                             .ASCID directive, 4-73B          potential DECthreads problem,      /FLAGGING=INSTRUCTIONS=             4-32                              function,  4-76 D         Librarian utility (LIBRARIAN)       .GLOBAL_LABEL directive,2          error reporting problem and          4-749             workaround,  4-70               problem, 4-73 >          operation failure,  4-70           restrictions, 4-735         License Management Facility       MACRO32.EXEaI           (LMF)                             required by standalone BACKUP 4          for Alpha systems,  3-33             ,  1-83          restrictions,  3-33              MADDRIVER =         Linker utility, 4-70, 4-72,         restriction, 3-31 :           4-79                            MASSBUS adapters?          /DEBUG qualifier corrections,      I/O registers, 4-64 ?             4-71                          MAT functions used byaE          linking translated images,          translated BASIC images, 2             4-79                             4-111C          linking with MTHRTL,  4-77       Mathematical applications ;          new error message,  4-70           migrating, 4-78w?          workaround for restricted use    Mathematics libraries H             of global symbols,  4-71        VAX and Alpha compatibility,2         Linking device driver images,         4-78F           4-63                            MicroVAX installation system7         LMF (License Management              hangs, 1-9r           Facility)           See License Management              Facility      I                                                                   Index-9                    F     Migrating to an OpenVMS AXP        N______________________________'        System: Recompiling and         -D        Relinking Applications,         /NATIVE_ONLY qualifier, 4-72,-        documentation corrections,        4-79 :        4-79                            NCSA Mosaic browserE     Mixed-version cluster               TCP/IP support options,  3-25/4       restriction for using            NETCONFIG.COME          multiple queue managers,       support for DEFQA controller, 5          3-15                              3-23, 3-24 E     MODPARAMS.DAT                       support for DEFTA controller,e/       logging statements (Alpha            3-24 4          only), 3-2                    Nonpaged pool3     Monitor utility (MONITOR)           corrections >       display change on VAX,  3-37         deallocation,  3-38A       monitoring remote disks           problems and restrictionsG?          new limit,  3-36                  prepopulation,  3-38i;     Monitoring Performance History     Null frame procedure 3        (MPH)                             descriptor4E       See MPH                           potential problem to debuggerX1     MOUNT command,  3-37                   , 4-74       Mount utility (MOUNT),  3-37F       correction to noncompliant       O______________________________,          ISO 9660 CD-ROMs, 3-37        OPCOMA     MPH (Monitoring Performance         problems and restrictions.C        History), 3-34                      OPERATOR.LOG file,  3-39E@     MSGHLP (Help Message utility)      OpenVMS Alpha System-Code8       See Help Message utility           Debugger,  4-607     MTH$ RTL,  4-78                     problems,  4-62 <       double-precision floating-       OpenVMS Alpha systems@          point functions invoked by     installation and upgrade@          translated images, 4-111          correction for system<       executable image restrictions        directories, 1-13D          , 4-77                         POLYCENTER enhancement,  1-9D       translated,  4-111                RAID device-naming problems,/     Multiple queue managers                1-11aE       checks not performed for          removing the operating system,1          SJC$_LOG_QUEUE item code,         , 1-10tD          4-94                          OpenVMS Delta/XDelta Debugger>       restriction,  3-15                 Manual, documentation;                                          corrections,  4-36          Index-10 o  n              =         OpenVMS I/O User's Reference      POLYCENTER Software A           Manual, documentation              Installation utility 5           corrections,  4-68                 (cont'd),B         OpenVMS Linker Utility Manual,      file generation number?           documentation corrections,          limitation,  4-82 B           4-72                              file generations, 4-81I         OpenVMS Programming Concepts        file statement documentation, 2           Manual, documentation               4-85E           corrections,  4-97                handling managed objects,r2         OpenVMS VAX systems                   4-81G          standalone BACKUP requirement      information statement, 4-822E             ,  1-8                          network object statement, 2          version requirements for             4-83H             upgrades,  1-7                  option statement limitation,2          volume shadowing restriction,        4-80I             1-7                             package operation constraintso5         OSAK                                  ,  4-83 >          DECnet for OpenVMS VAX             partial kits, 4-84E             Extensions,  1-8                PRODUCT command problems, 2                                               3-40H         P______________________________     PRODUCT command restriction,2                                               3-40.         P.S.I., 1-8                           @         Package operation constraints       product installation@          with POLYCENTER Software             restriction,  3-42C             Installation utility,  4-83     PRODUCT PACKAGE commandiB         Per-disk licensing                    documentation,  4-85C          volume shadowing,  3-68            removing products, 3-43 C         PGFLQUOTA                           restriction in deletingf@          problems,  4-70                      directories,  3-41F         POLYCENTER Software                 rights identifier problem,2           Installation utility                4-84I          account removal problem,           scope statement documentationT5             4-80                              ,  4-85o?          alternate file placement           scope support, 4-83oA             restriction,  4-80              upgrade problem, 3-40fF          contention problem with DCL        "uses" clause restriction,2             Help,  1-5                        4-84=          disk space reporting,  3-42      POLYCENTER SoftwareEA          documentation corrections,          Installation Utility >             4-85                             Developer's Guide=          error message shortcoming,         corrections, 4-85C=             4-81                          POLYCENTER Stripings=          error reporting,  4-81             replacement, 3-43 !          execute statement,  4-83   I                                                                  Index-11                    =     Port driver $QIO                   Remedial kits (cont'd)e@       restriction,  4-73                not included for OpenVMSA     Port is Reinitializing message         Alpha Version 6.2, C-2 D        , 1-17                           not included for OpenVMS VAX;     /PRESERVE=FLOAT_EXCEPTIONS             Version 6.2, C-1 3       translation qualifier needed     Restrictionst:          for TIE condition handler,     KFESA/KFESB,  3-62E          4-103                          on passing C structure membern6     PRINT command                          names, 4-61:       /DELETE qualifier,  3-15         RF73 and RFnn disksA     Printing files, requirements,       controller memory errors, /        3-15                                1-20r0     Procedure descriptor,  4-76        RF73 disk>     PRODUCT command restrictions,       image backups of,  3-7@        3-40                            Rights identifier problem@     PRODUCT REMOVE command              with POLYCENTER SoftwareE       files not removed with,  1-10        Installation utility, 4-84D5       removing the operating system    RMS Journaling @          , 1-10                         remotely accessed files,/     Program abort hang                     3-44y:       DECthreads,  4-32                 restriction,  3-445     PSECT keyword                      Root directoryc@       component of linker overlay       incorrectly initialized,/          restriction, 4-71                 3-31 ;                                        Rounding problem and 3     Q______________________________      workaroundSD     Queue managers,  3-15               in translated images,  4-103=       checks not performed for         Run-time library (RTL)R1          SJC$_LOG_QUEUE item code,       routines ?          4-94                           accessing the D56 form,_0                                            4-1117     R______________________________     MTH$ RTL,  4-78tD     RAID devices                        not included in Alpha,  4-86A       naming problem,  1-11            Running translated images, .     Recovery unit journaling             4-100B       restriction,  3-44                defining logical names for@     Register deferred                      translated libraries,0       notation,  4-115                     4-1017     Remedial kits                      RX23 disks, 1-17t7       included for OpenVMS Alpha       RX26 disks, 1-17n7          Version 6.2, B-4              RZ57 disk drivestA       included for OpenVMS VAX          volume shadowing support,r/          Version 6.2, B-1                  3-68/       Index-12                   @         S______________________________   $SNDJBC system serviceE                                             SJC$_LOG_QUEUE item code,a2         Screen Management (SMG$)              4-94G           Facility                        Software Product Descriptions 8          VT500 series terminal support       (SPDs), 1-20             ,  4-87                       SORT32D         SCSI bus                            changes and enhancements?          booting two systems,  3-63            work files, 3-46 B         SCSI controllers                  Sort/Merge utility (SORT4          restrictions on AlphaServer         /MERGE)I             2100 systems,  1-17             /FIELD qualifier enhancement,l2         SCSI disks                            2-10-          VAX shadowing support,  3-67     SPI E         SCSI-2 port interface (SPI),        See SCSI-2 port interfaceC;           4-41                            SPI$CONNECT macrotG         SCSI-2 status                       R3 return with SPDT$M_CMDQ,T2          getting characteristics,             4-65:             4-66                            R4 input, 4-65G         Security changes                  SPI$GET_CONNECTION_CHAR macro H          hash algorithm,  4-90              characteristics buffer, 4-66A          SYS$HASH_PASSWORD,  4-90         Standalone BACKUP,  3-8rH          UAF$C_PREFERRED_ALGORITHM,         reliance on MACRO32.EXE, 1-8E             4-90                          STARLET data structures andr8          user-mode probing of the            definitionsC             formal parameters,  4-90        for C programmers, 4-90aG         Sending comments to Digital       Step 1 drivers not supported,s1           writers,  iii                      4-60eE         SET PROCESS/NOAUTO_UNSHELVE       StorageWorks RAID Array 110 6           command,  2-2                      SubsystemE         SET PROCESS/SUSPEND=KERNEL/ID=      problems and restrictions B           command,  2-3                        SHOW DEVICE console?         Shadowing                                command,  3-47 E          See Volume Shadowing             StorageWorks RAID Array 210 6         SHADZEROMBR error, 3-66              Subsystem@         Shared linkage sections             naming problem, 1-11E          restriction,  3-45               StorageWorks RAID Array 230 6         SHOW DEVICE console command          Subsystem@          StorageWorks RAID Array 110        naming problem, 1-11H             Subsystem,  3-47              StorageWorks RAID Software for:         SHUTDOWN NODE command, 3-52          OpenVMS, 3-438         SJC$_LOG_QUEUE item code          SUBMIT commandC          check not performed with           /DELETE qualifier, 3-15 #             multiple queue manager,              4-94  I                                                                  Index-13                    @     $SUSPND system service,  2-3       System Management utility:       cluster problem,  4-95             (SYSMAN) (cont'd)B     SYS$HASH_PASSWORD                   rights identifier changes,/       need to recompile and relink,        3-51oE          4-90                           SHUTDOWN NODE command changesf1     SYS$STARLET_C.TLB                      , 3-52 8       adherence to conventions,        System monitoring/          4-92                           See MPHi8       functional equivalency to        System parameters6          STARLETSD.TLB, 4-90            XQPCTL2,  3-626       impact on use of "variant_       System security3          struct" and "variant_          correctionssA          union", 4-91                      auditing events,  3-44tD       potential impact on LIB              intrusion services,  3-456          structures, 4-91              System services@       potential impact on RMS           changes and enhancements@          structures, 4-91                  INIT$_HOMEBLOCKS item8       providing .H files,  4-92               code, 4-93@     SYS$SYSTEM:SHUTDOWN.COM                $LCKPAG limits,  4-93@       REMOVE_NODE option correction        $LKWSET limits,  4-93E          , 3-64                            SJC$_DISPLAY_USERNAME items8     SYSMAN                                    code, 4-948       See System Management utility        $SYNCH,  4-94C     System board resources              $CREATE_USER_PROFILE,  4-961A       for AlphaStation series           documentation changes anda6          computers, A-18                   corrections9     System Dump Analyzer (SDA)             $CHKPRO,  4-96t<        utility                             $TSTCLUEVT,  4-96D       possible system failure,          $FORMAT_AUDIT problem,  4-956          3-48                           $GETQUI,  4-97;     System dump files                   restrictions,  4-95E5       Dump Off System Disk (DOSD),      $SUSPND,  2-3nE          3-61                              problem calling in cluster ?       limitation,  3-4                        environment, 4-95 2     System Management utility          System timeD        (SYSMAN)                         resetting after January 1st,/       ALF command changes,  3-48           3-56 @       /CLUSTER qualifier problem,      Systemwide logical names,.          3-52                            4-109D       clusterwide DISKQUOTA command    SYS_ERRLIST symbol undefined,-          requirement, 3-53               4-29        DISKQUOTA commands,  3-531        problems and restrictions,
          3-52M       Index-14 i  a              C         SYS_NERR symbol undefined,        Translated image support, 8           4-29                               4-31, 4-105E                                             See also Translated Imagee?         T______________________________       Environment (TIE)   I         Terminal Fallback facility          additional qualifier requiredTA           (TFF),  3-59                        for FORTRAN,  4-106o9          restrictions,  3-61                linking, 4-79 F         TF857 backup failure on VAX         need for additional steps,3           4000 Model 300,  3-9                4-106 C         TFF                               Translated VAX C Run-Time ;          See Terminal Fallback               Library, 4-113TD             facility                        functional restrictions,3                                               4-113_I         TIE                                 interoperability restrictionse6          See Translated Image                 ,  4-1135             Environment                   TranslationA?         TIE$EMULAT_TV.EXE image, 4-105      BASIC images, 4-111C8         TIE$SHARE shareable image,          BLAS$, 4-111E           4-99                              callers to CRF$FREE_VM or @         Time                                  CRF$GET_VM,  4-112C          resetting after January 1st,       executable files, 4-106 9             3-56                            images, 4-106,9         /TRACEBACK option, 4-77             MTHRTL, 4-111tE         Transaction group                   run-time libraries, 4-110 >          definition,  3-19                TURBOchannel devices9         Translated VAX COBOL programs       booting, 3-478           support,  4-115-I         Translated Image Environment      U______________________________tC           (TIE),  4-99, 4-106             UAF$C_PREFERRED_ALGORITHMp?          access violation workaround,       value changed, 4-904;             4-104                         User-mode probing F          interoperability between           conditional assembly, 4-90C             native and translated         "Uses" clause restriction D             images,  4-100                  with POLYCENTER SoftwareI          restrictions,  4-102                 Installation utility,  4-84o#          running translated images,rI             4-100                         V______________________________t:          statistics and feedback,         "variant_struct"H             4-101                           impact of SYS$STARLET_C.TLB,2          system logical names,  4-109         4-919          using /TIE qualifier to          "variant_union" H             enable autojacketing,           impact of SYS$STARLET_C.TLB,2             4-104                             4-91  I                                                                  Index-15s :  c              7     VAX 4000 series computers          Volume shadowingOE       Model 300 backup failure,         ACCVIO system failures,  3-66 ?          3-9                            controller-based,  3-67eC       using the DUP Driver utility,     device recognition changes, /          1-24                              3-66 A     VAX 7000 systems                    documentation corrections D       Dump Off System Disk (DOSD)          per-disk licensing,  3-689          not supported, 3-61            host-based,  3-67 A     VAX Environment Software            interoperability changes,-/        Translator utility (VEST)           3-66t@       See VEST                          minimerge changes,  3-66A     VAX Instruction                     phase I retirement,  3-67 ;       CASE,  4-116                      restrictions,  3-673D     VAXCDEF.TLB                            DISMOUNT/CLUSTER command,2       replaced by new files,  4-90            3-68B     VAXstation installation                recommended version forA       system hangs,  1-9                      KDM70 devices, 3-67 ;     VEST,  4-99                         RZ57 support,  3-68 C       See also DECmigrate,              SHADZEROMBR bugcheck,  3-66 B          Translated Image               timer-based polling,  3-67?          Environment (TIE), and         VAX/SCSI support,  3-67 +          Translated image support      VOTSE>                                         DECnet for OpenVMS VAX:     VMScluster systems,  3-61              Extensions, 1-8=       booting two systems that         VT500 series terminals B          share a SCSI bus, 3-63         baud rates supported,  2-7@       concurrency improvements,         Screen Management (SMG$)E          3-62                              Facility support for, 4-87e       EXPECTED_VOTES SYSGENrF          parameter, 3-64               W______________________________,       FDDI clusters,  3-62             WANDD>       KFESA/KFESB restrictions,         DECnet for OpenVMS VAX:          3-62                              Extensions, 1-8A       restriction for using            Watch chip (BBW) change ind:          multiple queue managers,        time range,  3-55A          3-15                          WSQUOTA maximum value, 3-1        SCSI clusters,  3-61(       system startup problem with      XF          ALPHAVMSSYS.PAR file, 3-63    _______________________________A     VMSINSTAL command procedure        X/Open Transport Interface 6       with layered product               (XTI),  4-116E          installations, 1-6            XQPCTL2 system parameter, 3-62r     VMSKITBLD.COM !       OpenVMS Alpha change,  1-9, 
          3-65o       Index-16                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        