                                         ?                    The OpenVMS Frequently Asked Questions (FAQ)                             ABSTRACT   J                    This document contains answers to many common questionsG                    on the OpenVMS operating system, and covers OpenVMS, A                    and OpenVMS running on Itanium, Alpha, and VAX                     hardware.  H                    While this document is available in multiple formats,H                    the text-format version is far and away generally the,                    easiest format to search.        =                    Revision/Update Information   OpenVMS V8.3   H                    Revision/Update Information:  Revision Date/July 2006                                          FAQ                                 J           ________________________________________________________________             Contents  J                 __________________________________________________________J                 PREFACE                                                  i  J                 __________________________________________________________J                 OPENVMS FREQUENTLY ASKED QUESTIONS (FAQ)               iii  J           ________________________________________________________________J           CHAPTER 1  INTRODUCTION                                      1-1  J                 __________________________________________________________J                 1.1   WHAT CORE OPENVMS URLS DO YOU NEED TO KNOW?      1-1  J                 __________________________________________________________J                 1.2   WHAT ARE THE OPENVMS USENET NEWSGROUPS?          1-2>                 1.2.1     What is the scope of the comp.os.vmsJ                           newsgroup?                                   1-2;                 1.2.2     What newsgroups carry VMS-related J                           information?                                 1-2J                 1.2.3     What newsgroup archives are available?       1-3J                 1.2.4     What is the INFO-VAX mailing list?           1-3F                 1.2.4.1      How do I subscribe to or unsubscribe from+                              INFO-VAX?, 1-4   J                 __________________________________________________________J                 1.3   WHAT IS [N]ETIQUETTE?                            1-5  J                 __________________________________________________________J                 1.4   WHAT OPENVMS USER GROUP(S) ARE AVAILABLE?        1-8  J                 __________________________________________________________J                 1.5   OPENVMS SUPPORT, QUESTIONS AND COMMENTS?         1-9A                 1.5.1     Corporate contacts for OpenVMS Business J                           Issues?                                      1-9J                 1.5.2     OpenVMS Ambassadors?                        1-10B                 1.5.3     Contact for OpenVMS Marketing Issues andJ                           Questions?                                  1-10<                 1.5.4     Contact URLs for OpenVMS TechnicalJ                           Issues?                                     1-10      J                                                                        iii                                   Contents         J           ________________________________________________________________J           CHAPTER 2  GENERAL INFORMATION                               2-1  J                 __________________________________________________________J                 2.1   WHAT IS OPENVMS? WHAT IS ITS HISTORY?            2-1  J                 __________________________________________________________<                 2.2   WHAT IS THE DIFFERENCE BETWEEN VMS ANDJ                       OPENVMS?                                         2-3  J                 __________________________________________________________J                 2.3   WHAT'S IN A NAME? TERMINOLOGY AND PRODUCTS?      2-4J                 2.3.1     How do I port from VMS to OpenVMS?           2-4  J                 __________________________________________________________J                 2.4   WHICH IS BETTER, OPENVMS OR UNIX?                2-4  J                 __________________________________________________________>                 2.5   IS HP CONTINUING FUNDING AND SUPPORT FORJ                       OPENVMS?                                         2-5  J                 __________________________________________________________J                 2.6   WHAT OPENVMS DISTRIBUTION KITS ARE AVAILABLE?    2-6B                 2.6.1     Where can I download OpenVMS and LayeredJ                           Product Kits?                                2-8  J                 __________________________________________________________J                 2.7   IN WHAT LANGUAGE IS OPENVMS WRITTEN?             2-9  J                 __________________________________________________________J                 2.8   OBTAINING AND TRANSFERING OPENVMS LICENSES?      2-9=                 2.8.1     Questions asked by Hobbyist OpenVMS J                           licensees?                                  2-10E                 2.8.1.1      Vendors offering Hobbyist Licenses, 2-11 J                 2.8.2     OpenVMS Educational and CSLG licenses?      2-11>                 2.8.3     What developer and partner licensingJ                           programs are available?                     2-12@                 2.8.4     How do I obtain or transfer an OpenVMSJ                           license?                                    2-12  J                 __________________________________________________________<                 2.9   DOES OPENVMS SUPPORT THE EURO CURRENCYJ                       SYMBOL?                                         2-12  J                 __________________________________________________________F                 2.10  OPENVMS PORTS? ITANIUM? PORTS TO IA-32, EM64T ORJ                       AMD64 SYSTEMS?                                  2-13                      iv                                    Contents         J                 __________________________________________________________>                 2.11  ARE THERE ANY NETWORK-ACCESSIBLE OPENVMSJ                       SYSTEMS?                                        2-16  J                 __________________________________________________________J                 2.12  WHAT VERSION OF OPENVMS DO I NEED?              2-18  J                 __________________________________________________________J                 2.13  HOW CAN I SUBMIT OPENVMS FREEWARE?              2-19  J                 __________________________________________________________J                 2.14  PORTING APPLICATIONS TO OPENVMS?                2-20  J                 __________________________________________________________F                 2.15  WHAT RESOURCES ARE AVAILABLE TO OPENVMS SOFTWAREJ                       DEVELOPERS?                                     2-21  J                 __________________________________________________________E                 2.16  MEMORY MANAGEMENT, RESOURCE MANAGEMENT, PROCESS J                       SCHEDULING, ETC?                                2-22  J                 __________________________________________________________J                 2.17  BASIC UNITS OF MEASUREMENT?                     2-23J                 2.17.1    How many bytes are in a disk block?         2-23J                 2.17.2    How many bytes are in a memory page?        2-25@                 2.17.3    How do I convert? Disk Blocks? KB, MB,J                           GB, TB?                                     2-25  J           ________________________________________________________________J           CHAPTER 3  DOCUMENTATION                                     3-1  J                 __________________________________________________________?                 3.1   WHERE CAN I FIND ONLINE COPIES OF OPENVMS J                       MANUALS?                                         3-1  J                 __________________________________________________________>                 3.2   WHAT ONLINE INFORMATION AND WEBSITES AREJ                       AVAILABLE?                                       3-2  J                 __________________________________________________________H                 3.3   HOW DO I EXTRACT THE CONTENTS OF A HELP TOPIC TO AJ                       TEXT FILE?                                       3-5  J                 __________________________________________________________;                 3.4   DOES OPENVMS MARKETING HAVE AN E-MAIL J                       ADDRESS?                                         3-5  J                                                                          v                                   Contents         J                 __________________________________________________________?                 3.5   WHERE CAN I LEARN ABOUT OPENVMS EXECUTIVE J                       INTERNALS?                                       3-5  J                 __________________________________________________________I                 3.6   WHERE CAN NEW USERS FIND TUTORIAL INFORMATION ABOUT J                       OPENVMS?                                         3-6J                 3.6.1     Tutorial Websites?                           3-6J                 3.6.2     Books and Tutorials?                         3-8  J                 __________________________________________________________?                 3.7   WHAT OPENVMS MAILING LISTS AND FORUMS ARE J                       AVAILABLE?                                      3-10  J                 __________________________________________________________D                 3.8   WHAT IS THIS ASK THE WIZARD WEBSITE I'VE HEARDJ                       ABOUT?                                          3-12  J                 __________________________________________________________D                 3.9   WHERE CAN I FIND THE LATEST C RUN-TIME LIBRARYJ                       MANUALS?                                        3-13  J           ________________________________________________________________J           CHAPTER 4  TIME AND TIMEKEEPING                              4-1  J                 __________________________________________________________=                 4.1   A BRIEF HISTORY OF OPENVMS TIMEKEEPING, J                       PLEASE?                                          4-17                 4.1.1     Details of the OpenVMS system J                           time-keeping?                                4-3F                 4.1.1.1      VAX hardware time-keeping details..., 4-3,                 4.1.1.1.1     TOY clock, 4-31                 4.1.1.1.2     EXE$GQ_SYSTIME, 4-3 2                 4.1.1.1.3     EXE$GQ_TODCBASE, 4-3.                 4.1.1.1.4     EXE$GL_TODR, 4-4H                 4.1.1.2      Alpha hardware time-keeping details..., 4-5G                 4.1.1.2.1     Battery-Backed Watch (BB_WATCH) Chip, 4-5 1                 4.1.1.2.2     EXE$GQ_SYSTIME, 4-6 7                 4.1.1.2.3     EXE$GQ_SAVED_HWCLOCK, 4-6 I                 4.1.1.3      Why does VAX need a SET TIME at least once a '                              year?, 4-7 >                 4.1.2     How does OpenVMS VAX maintain systemJ                           time?                                        4-7                      vi                                    Contents         J                 __________________________________________________________J                 4.2   KEEPING THE OPENVMS SYSTEM TIME SYNCHRONIZED?    4-9  J                 __________________________________________________________J                 4.3   EXTERNAL TIME-BASE HARDWARE?                    4-11<                 4.3.1     Why do my cluster batch jobs startJ                           early?                                      4-11J                 4.3.2     Why does my OpenVMS system time drift?      4-12<                 4.3.3     Resetting the system time into theJ                           past?                                       4-13<                 4.3.4     How can I drift the OpenVMS systemJ                           time?                                       4-13A                 4.3.5     How can I configure TCP/IP Services NTP J                           as a time provider?                         4-14  J                 __________________________________________________________H                 4.4   MANAGING TIMEZONES, TIMEKEEPING, UTC, AND DAYLIGHTJ                       SAVING TIME?                                    4-16B                 4.4.1     Creating, Updating and Managing TimezoneJ                           Definitions?                                4-19H                 4.4.1.1      Customizing or Updating your TDF (Timezone)+                              Setting?, 4-20 >                 4.4.1.2      US Daylight Time Changes Starting.                              1-Mar-2007?, 4-22<                 4.4.2     Timezones and Time-related LogicalJ                           Names?                                      4-22=                 4.4.3     How to troubleshoot TDF problems on J                           OpenVMS?                                    4-23  J                 __________________________________________________________G                 4.5   WHY DOES THE SET TIME COMMAND FAIL? HELP MANAGING J                       DTSS?                                           4-25  J                 __________________________________________________________D                 4.6   SETTING TIME ON ALPHASERVER ES47, ES80, GS1280J                       CONSOLE?                                        4-27  J                 __________________________________________________________F                 4.7   UTC VS GMT VS VS UT1/UT1/UT2 TDF? WHAT ARE THESEJ                       ACRONYMS?                                       4-29  J                 __________________________________________________________J                 4.8   USING W32TIME OR AN SNTP AS A TIME PROVIDER?    4-31  J                                                                        vii                                   Contents         J           ________________________________________________________________J           CHAPTER 5  SYSTEM MANAGEMENT INFORMATION                     5-1  J                 __________________________________________________________J                 5.1   WHAT IS AN INSTALLED IMAGE?                      5-1  J                 __________________________________________________________J                 5.2   ARE THERE ANY KNOWN VIRUSES FOR OPENVMS?         5-2  J                 __________________________________________________________J                 5.3   SOURCES OF OPENVMS SECURITY INFORMATION?         5-4  J                 __________________________________________________________J                 5.4   HOW DO I MOUNT AN ISO-9660 CD ON OPENVMS?        5-4  J                 __________________________________________________________J                 5.5   HOW DO I EXTRACT THE CONTENTS OF A PCSI KIT?     5-6  J                 __________________________________________________________J                 5.6   EMERGENCY (CONVERSATIONAL) SYSTEM STARTUP?       5-7C                 5.6.1     I've forgotten the SYSTEM password - what J                           can I do?                                   5-11A                 5.6.2     My product licenses have expired - what J                           can I do?                                   5-11  J                 __________________________________________________________A                 5.7   HOW DO I CHANGE THE NODE NAME OF AN OPENVMS J                       SYSTEM?                                         5-12  J                 __________________________________________________________C                 5.8   WHY DOESN'T OPENVMS SEE THE NEW MEMORY I JUST J                       ADDED?                                          5-14  J                 __________________________________________________________>                 5.9   HOW DO I CHANGE THE TEXT IN A USER'S UICJ                       IDENTIFIER?                                     5-15  J                 __________________________________________________________J                 5.10  WHAT ARE THE OPENVMS VERSION UPGRADE PATHS?     5-16J                 5.10.1    OpenVMS Alpha Upgrade (or Update) Paths     5-16J                 5.10.2    OpenVMS I64 Upgrade Paths                   5-19J                 5.10.3    OpenVMS VAX Release Upgrade Paths           5-20J                 5.10.4    OpenVMS Cluster Rolling Upgrade Paths       5-21J                 5.10.5    OpenVMS VAX Manual Organization             5-22=                 5.10.6    OpenVMS Product Version and Support J                           Information                                 5-227                 5.10.7    OpenVMS Alpha and I64 Upgrade J                           Terminology                                 5-23                      viii                                    Contents         J                 __________________________________________________________E                 5.11  WHY DO I HAVE A NEGATIVE NUMBER IN THE PAGEFILE J                       RESERVABLE PAGES?                               5-25  J                 __________________________________________________________H                 5.12  DO I HAVE TO UPDATE LAYERED PRODUCTS WHEN UPDATINGJ                       OPENVMS?                                        5-26  J                 __________________________________________________________J                 5.13  HOW DO I CHANGE THE VOLUME LABEL OF A DISK?     5-27  J                 __________________________________________________________J                 5.14  HOW CAN I SET UP A SHARED DIRECTORY?            5-27  J                 __________________________________________________________=                 5.15  WHY DO I GET EXTRA BLANK PAGES ON MY HP J                       PRINTER?                                        5-29  J                 __________________________________________________________?                 5.16  DRIVERS AND CONFIGURATION OF NEW GRAPHICS J                       CONTROLLERS?                                    5-29J                 5.16.1    The ELSA GLoria Synergy                     5-29J                 5.16.2    PowerStorm 300, PowerStorm 350              5-31J                 5.16.3    PowerStorm 3D30, PowerStorm 4D20            5-31J                 5.16.4    Radeon 7500                                 5-32  J                 __________________________________________________________C                 5.17  HOW CAN I ACQUIRE OPENVMS PATCHES, FIXES, AND J                       ECOS?                                           5-32  J                 __________________________________________________________J                 5.18  HOW DO I MOVE THE QUEUE MANAGER DATABASE?       5-33  J                 __________________________________________________________H                 5.19  HOW DO I DELETE AN UNDELETABLE/UNSTOPPABLE (RWAST)J                       PROCESS?                                        5-34  J                 __________________________________________________________J                 5.20  HOW DO I RESET THE ERROR COUNT(S)?              5-35  J                 __________________________________________________________B                 5.21  HOW DO I FIND OUT IF THE TAPE DRIVE SUPPORTSJ                       COMPRESSION?                                    5-37  J                 __________________________________________________________F                 5.22  CAN I COPY SYSUAF TO ANOTHER VERSION? TO VAX? TOJ                       ALPHA?                                          5-37  J                                                                         ix                                   Contents         J                 __________________________________________________________J                 5.23  HOW DO I DELETE (TIMEOUT) IDLE PROCESSES?       5-40  J                 __________________________________________________________C                 5.24  DO I NEED A PAK FOR THE DECEVENT (HP ANALYZE) J                       TOOL?                                           5-40  J                 __________________________________________________________;                 5.25  INITIALIZE ACCVIO AND ANSI TAPE LABEL J                       SUPPORT?                                        5-41  J                 __________________________________________________________J                 5.26  HOW DO I RECOVER FROM INSVIRMEM ERRORS?         5-41  J                 __________________________________________________________C                 5.27  HOW CAN I PREVENT A SERIAL TERMINAL LINE FROM J                       INITIATING A LOGIN?                             5-42  J                 __________________________________________________________=                 5.28  HOW DOES PCSI USE THE IMAGE BUILD_IDENT J                       FIELD?                                          5-42  J                 __________________________________________________________C                 5.29  HOW CAN I TELL WHAT SOFTWARE (AND VERSION) IS J                       INSTALLED?                                      5-44  J                 __________________________________________________________@                 5.30  WHAT FILE CHECKSUM TOOLS ARE AVAILABLE FORJ                       OPENVMS?                                        5-45  J                 __________________________________________________________@                 5.31  WHAT (AND WHERE) IS THE OPENVMS MANAGEMENTJ                       STATION?                                        5-46  J                 __________________________________________________________A                 5.32  HOW TO DETERMINE CURRENT DISK FRAGMENTATION J                       LEVEL?                                          5-46  J                 __________________________________________________________<                 5.33  SYSBOOT-I-FILENOTLOC, UNABLE TO LOCATEJ                       SYS$CPU_ROUTINES?                               5-47  J                 __________________________________________________________G                 5.34  HOW CAN I CUSTOMIZE THE DCPS DEVICE CONTROL FOR A J                       NEW PRINTER?                                    5-47                      x                                   Contents         J                 __________________________________________________________J                 5.35  WHY DO $GETDEV MOUNTCNT AND SHOW DEVICE MOUNT COUNTSJ                       DIFFER?                                         5-49  J                 __________________________________________________________<                 5.36  WHAT SOFTWARE IS NEEDED FOR POSTSCRIPTJ                       PRINTERS?                                       5-49  J                 __________________________________________________________B                 5.37  HOW DO I REMOVE A PCSI-INSTALLED PATCH (ECO)J                       KIT?                                            5-49  J                 __________________________________________________________>                 5.38  SYSINIT-E, ERROR MOUNTING SYSTEM DEVICE,J                       STATUS=0072832C                                 5-50  J                 __________________________________________________________J                 5.39  RESOLVING LICENSE PAK PROBLEMS?                 5-50  J                 __________________________________________________________J                 5.40  CHANGING THE OPENVMS VERSION NUMBER?            5-52  J                 __________________________________________________________@                 5.41  HOW TO PREVENT USERS FROM CHOOSING OBVIOUSJ                       PASSWORDS?                                      5-53  J                 __________________________________________________________<                 5.42  PLEASE HELP ME WITH THE OPENVMS BACKUPJ                       UTILITY?                                        5-55J                 5.42.1    Why isn't BACKUP/SINCE=BACKUP working?      5-55F                 5.42.1.1     Why has OpenVMS gone through the agony of/                              this change?, 5-55 A                 5.42.1.2     Can you get the old BACKUP behaviour (                              back?, 5-559                 5.42.2    What can I do to improve BACKUP J                           performance?                                5-56J                 5.42.3    Why is BACKUP not working as expected?      5-57J                 5.42.4    How do I fix a corrupt BACKUP saveset?      5-59>                 5.42.5    How do I write a BACKUP saveset to aJ                           remote tape?                                5-60<                 5.42.6    How to perform a DoD security diskJ                           erasure?                                    5-61J                 5.42.7    How to enable telnet virtual terminals?     5-63J                 5.42.7.1     Volume Shadowing MiniCopy vs MiniMerge?, 5-64.                 5.42.7.1.1    Mini-Copy?, 5-64/                 5.42.7.1.2    Mini-Merge?, 5-65   J                                                                         xi                                   Contents         J                 __________________________________________________________J                 5.43  PLEASE EXPLAIN DELETE/ERASE AND FILE LOCKS?     5-66  J                 __________________________________________________________J                 5.44  MANAGING FILE VERSIONS?                         5-66  J                 __________________________________________________________J                 5.45  HOST-BASED VOLUME SHADOWING AND RAID?           5-67  J           ________________________________________________________________J           CHAPTER 6  INFORMATION ON MAIL                               6-1  J                 __________________________________________________________I                 6.1   MAIL KEEPS SAYING I HAVE NEW MESSAGES, BUT I DON'T. J                       WHAT DO I DO?                                    6-1  J                 __________________________________________________________>                 6.2   HOW DO I SEND OR READ ATTACHMENTS IN VMSJ                       MAIL?                                            6-1  J                 __________________________________________________________J                 6.3   HOW CAN I BLOCK SMTP MAIL RELAY SPAM?            6-3  J           ________________________________________________________________J           CHAPTER 7  INFORMATION ON UTILITIES                          7-1  J                 __________________________________________________________J                 7.1   HOW DO I PLAY AN AUDIO CD ON MY WORKSTATION?     7-1  J                 __________________________________________________________J                 7.2   HOW DO I ACCESS A MICROSOFT WINDOWS FLOPPY DISK FROMJ                       OPENVMS?                                         7-2  J                 __________________________________________________________C                 7.3   HOW DO I PLAY SOUND FILES ON AN ALPHASTATION? J                       DECSOUND DOESN'T WORK.                           7-3  J                 __________________________________________________________J                 7.4   HOW DO I READ IBM EBCDIC TAPES ON OPENVMS?       7-3  J                 __________________________________________________________J                 7.5   HOW CAN I PATCH AN OPENVMS ALPHA IMAGE?          7-4                        xii                                   Contents         J           ________________________________________________________________J           CHAPTER 8  DCL DETAILS                                       8-1  J                 __________________________________________________________J                 8.1   DCL SYMBOLS AND OPENVMS LOGICAL NAMES?           8-1  J                 __________________________________________________________J                 8.2   HOW DO I RUN A PROGRAM WITH ARGUMENTS?           8-3  J                 __________________________________________________________J                 8.3   HOW CAN I CLEAR THE SCREEN IN DCL?               8-5  J                 __________________________________________________________A                 8.4   USING REPLY/LOG FROM DCL? DISABLING CONSOLE J                       OPCOMS?                                          8-5  J                 __________________________________________________________J                 8.5   HOW DO I GENERATE A RANDOM NUMBER IN DCL?        8-6  J                 __________________________________________________________J                 8.6   WHAT DOES THE MCR COMMAND DO?                    8-7  J                 __________________________________________________________J                 8.7   HOW DO I CHANGE THE OPENVMS SYSTEM PROMPT?       8-7  J                 __________________________________________________________E                 8.8   CAN I DO DECNET TASK-TO-TASK COMMUNICATION WITH J                       DCL?                                             8-8  J                 __________________________________________________________:                 8.9   HOW CAN I GET THE WIDTH SETTING OF AJ                       TERMINAL?                                        8-9  J                 __________________________________________________________J                 8.10  WHY DOESN'T DCL SYMBOL SUBSTITUTION WORK?        8-9  J                 __________________________________________________________J                 8.11  HOW CAN I SUBSTITUTE SYMBOLS IN A PIPE?         8-10  J                 __________________________________________________________>                 8.12  USE OF RUN/DETACH, LOGINOUT, AND LOGICALJ                       NAMES?                                          8-10  J                 __________________________________________________________A                 8.13  HOW TO USE ESCAPE AND CONTROL CHARACTERS IN J                       DCL?                                            8-11  J                                                                       xiii                                   Contents         J           ________________________________________________________________J           CHAPTER 9  FILES                                             9-1  J                 __________________________________________________________J                 9.1   HOW CAN I UNDELETE A FILE?                       9-1  J                 __________________________________________________________F                 9.2   WHY DOES SHOW QUOTA GIVE A DIFFERENT ANSWER THANJ                       DIR/SIZE?                                        9-1  J                 __________________________________________________________J                 9.3   HOW DO I MAKE SURE THAT MY DATA IS SAFELY WRITTEN TOJ                       DISK?                                            9-2  J                 __________________________________________________________D                 9.4   WHAT ARE THE LIMITS ON FILE SPECIFICATIONS ANDJ                       DIRECTORIES?                                     9-3  J                 __________________________________________________________F                 9.5   WHAT IS THE LARGEST DISK VOLUME SIZE OPENVMS CANJ                       ACCESS?                                          9-4  J                 __________________________________________________________G                 9.6   WHAT IS THE MAXIMUM FILE SIZE, AND THE RMS RECORD J                       SIZE LIMIT?                                      9-7  J                 __________________________________________________________B                 9.7   HOW DO I WRITE CD-RECORDABLE OR DVD MEDIA ONJ                       OPENVMS?                                         9-8J                 9.7.1     CD and DVD notation, terminology?           9-116                 9.7.2     Use of RRD42 and other olderJ                           (embossed-media) CD drives?                 9-13A                 9.7.3     Creating Bootable OpenVMS I64 CD or DVD J                           Media? SYS$SETBOOT?                         9-14  J                 __________________________________________________________<                 9.8   WHAT I/O TRANSFER SIZE LIMITS EXIST INJ                       OPENVMS?                                        9-15  J                 __________________________________________________________C                 9.9   CAN I USE ODBC TO CONNECT TO OPENVMS DATABASE J                       FILES?                                          9-15  J                 __________________________________________________________J                 9.10  IF MY DISKS ARE SHOWN AS VIOC COMPATIBLE, AM I USINGJ                       XFC?                                            9-16                      xiv    y                              Contentse        J                 __________________________________________________________7                 9.11  RMS SEQUENTIAL FILES AND PLATFORMnJ                       PORTABILITY?                                    9-16  J                 __________________________________________________________J                 9.12  HOW TO READ LOCKED FILES?                       9-17  J           ________________________________________________________________J           CHAPTER 10  OPENVMS PROGRAMMING INFORMATION                 10-1  J                 __________________________________________________________G                 10.1  MODULAR PROGRAMMING, FACILITY PREFIXES AND SYMBOL_J                       NAMING?                                         10-1  J                 __________________________________________________________9                 10.2  CAN I HAVE A SOURCE CODE EXAMPLE OF J                       CALLING...?                                     10-2  J                 __________________________________________________________A                 10.3  HOW DO I GET THE ARGUMENTS FROM THE COMMAND J                       LINE?                                           10-4  J                 __________________________________________________________A                 10.4  HOW DO I GET A FORMATTED ERROR MESSAGE IN A J                       VARIABLE?                                       10-5  J                 __________________________________________________________J                 10.5  HOW DO I LINK AGAINST SYS$SYSTEM:SYS.STB ON AN ALPHAJ                       SYSTEM?                                         10-5  J                 __________________________________________________________=                 10.6  HOW DO I DO A SET DEFAULT FROM INSIDE AUJ                       PROGRAM?                                        10-5  J                 __________________________________________________________F                 10.7  HOW DO I TURN MY FORTRAN COMMON INTO A SHAREABLEJ                       IMAGE ON ALPHA?                                 10-6  J                 __________________________________________________________D                 10.8  HOW DO I CONVERT BETWEEN IEEE AND VAX FLOATINGJ                       DATA?                                           10-6  J                 __________________________________________________________B                 10.9  HOW DO I GET THE ARGUMENT COUNT IN A FORTRANJ                       ROUTINE?                                        10-7  J                                                                         xv                                   Contents         J                 __________________________________________________________C                 10.10 HOW DO I GET A UNIQUE SYSTEM ID FOR LICENSING_J                       PURPOSES?                                       10-7  J                 __________________________________________________________F                 10.11 WHAT IS AN EXECUTABLE, SHAREABLE, SYSTEM OR UWSSJ                       IMAGE?                                          10-8  J                 __________________________________________________________J                 10.12 HOW DO I DO A FILE COPY FROM A PROGRAM?        10-10  J                 __________________________________________________________J                 10.13 WHAT IS A DESCRIPTOR?                          10-10  J                 __________________________________________________________=                 10.14 HOW DO I CREATE A PROCESS UNDER ANOTHER_J                       USERNAME?                                      10-12  J                 __________________________________________________________G                 10.15 WHY DO LIB$SPAWN, LIB$SET_SYMBOL FAIL IN DETACHEDGJ                       PROCESSES?                                     10-13  J                 __________________________________________________________E                 10.16 WHERE CAN I OBTAIN BLISS, AND THE LIBRARIES ANDOJ                       SUPPORTING FILES?                              10-14  J                 __________________________________________________________J                 10.17 HOW CAN I OPEN A FILE FOR SHARED ACCESS?       10-16  J                 __________________________________________________________A                 10.18 HOW CAN I HAVE COMMON SOURCES FOR MESSAGES,_J                       CONSTANTS?                                     10-16  J                 __________________________________________________________D                 10.19 HOW DO I ACTIVATE THE OPENVMS DEBUGGER FROM ANJ                       APPLICATION?                                   10-17  J                 __________________________________________________________J                 10.20 DEALING WITH ENDIAN-NESS?                      10-17  J                 __________________________________________________________J                 10.21 HOW TO RESOLVE LINK-I-DATMISCH ERRORS?         10-18  J                 __________________________________________________________:                 10.22 HP C AND OTHER OPENVMS C PROGRAMMINGJ                       CONSIDERATIONS?                                10-18J                 10.22.1   Other common C issues                      10-22J                 10.22.2   Other common C++ issues                    10-24                      xvi T  I                              Contents         J                 __________________________________________________________J                 10.23 STATUS OF PROGRAMMING TOOLS ON OPENVMS VAX?    10-26  J                 __________________________________________________________?                 10.24 CHOOSING A VERSION NUMBER FOR APPLICATION J                       CODE?                                          10-27  J                 __________________________________________________________J                 10.25 SELECTING A PROCESS DUMP DIRECTORY?            10-28  J                 __________________________________________________________J                 10.26 ACCESS TO ITANIUM ASSEMBLER?                   10-29  J                 __________________________________________________________J                 10.27 KERNEL-MODE CODING RESTRICTIONS?               10-29  J                 __________________________________________________________J                 10.28 DECODING AN ACCESS VIOLATION (ACCVIO) ERROR?   10-30  J                 __________________________________________________________J                 10.29 GENERATING AN AUTODIN-II CRC32?                10-32  J                 __________________________________________________________J                 10.30 ENABLING BUILT-IN TRACING?                     10-32  J           ________________________________________________________________J           CHAPTER 11  DECWINDOWS                                      11-1  J                 __________________________________________________________G                 11.1  HOW DO I LET SOMEONE ELSE DISPLAY SOMETHING ON MY3J                       WORKSTATION?                                    11-1  J                 __________________________________________________________:                 11.2  HOW DO I CREATE A DISPLAY ON ANOTHERJ                       WORKSTATION?                                    11-3  J                 __________________________________________________________J                 11.3  HOW CAN I GET THE INFORMATION FROM SHOW DISPLAY INTOJ                       A SYMBOL?                                       11-3  J                 __________________________________________________________J                 11.4  HOW DO I GET A LOG OF A DECTERM SESSION?        11-4  J                 __________________________________________________________J                 11.5  WHY IS DECWINDOWS MOTIF NOT STARTING?           11-4  J                                                                       xvii                                   Contents         J                 __________________________________________________________J                 11.6  HOW DO I SET THE TITLE ON A DECTERM WINDOW?     11-6  J                 __________________________________________________________H                 11.7  HOW DO I CUSTOMIZE DECWINDOWS, INCLUDING THE LOGINJ                       SCREEN?                                         11-77                 11.7.1    How do I customize DECwindows J                           keymapping?                                11-10@                 11.7.2    Why does the DELETE key delete forwardJ                           instead of backward?                       11-10  J                 __________________________________________________________J                 11.8  WHY DOESN'T XTAPPADDINPUT()  WORK ON OPENVMS?  11-12  J                 __________________________________________________________H                 11.9  WHY DO THE KEYBOARD ARROW KEYS MOVE THE DECWINDOWSJ                       CURSOR?                                        11-13  J                 __________________________________________________________J                 11.10 WHY DOES HALF MY DECWINDOWS DISPLAY BLANK?     11-13  J                 __________________________________________________________H                 11.11 %DECW-W-NODEVICE, NO GRAPHICS DEVICE FOUND ON THISJ                       SYSTEM?                                        11-14  J                 __________________________________________________________J                 11.12 HOW CAN I RESET THE WARNING BELL VOLUME?       11-16  J                 __________________________________________________________J                 11.13 HOW CAN I ALTER THE DECWINDOWS CDE BACKDROP?   11-17  J                 __________________________________________________________<                 11.14 HOW CAN I ENABLE THE DECWINDOWS TCP/IPJ                       TRANSPORT                                      11-17  J                 __________________________________________________________E                 11.15 CAN I USE DECWINDOWS 1.2-* ON OPENVMS V7.3-2 OR J                       LATER?                                         11-17  J                 __________________________________________________________J                 11.16 HOW TO ADD FONTS INTO DECWINDOWS?              11-18                          xviii L  D                              Contentsp        J           ________________________________________________________________J           CHAPTER 12  MISCELLANEOUS INFORMATION                       12-1  J                 __________________________________________________________H                 12.1  WHERE CAN I FIND INFORMATION ON ESCAPE AND CONTROLJ                       SEQUENCES?                                      12-1  J                 __________________________________________________________F                 12.2  DOES DECPRINT (DCPS) WORK WITH THE LRA0 PARALLELJ                       PORT?                                           12-3  J                 __________________________________________________________A                 12.3  HOW DO I CHECK FOR FREE SPACE ON A (BACKUP)_J                       TAPE?                                           12-3  J                 __________________________________________________________J                 12.4  CORRECTLY USING LICENSE PAKS AND LMF?           12-4  J           ________________________________________________________________J           CHAPTER 13  FINDING AND USING SOFTWARE                      13-1  J                 __________________________________________________________F                 13.1  WHERE CAN I FIND FREEWARE/SHAREWARE/SOFTWARE FORJ                       OPENVMS?                                        13-1  J                 __________________________________________________________J                 13.2  WHERE CAN I FIND UNIX TOOLS FOR OPENVMS?       13-15J                 13.2.1    C system and library routines              13-15J                 13.2.2    X Windows utilities and routines           13-16J                 13.2.3    TCP/IP Tools and Utilities for OpenVMS?    13-16J                 13.2.4    The vi text editor                         13-17J                 13.2.5    The Emacs Text Editor                      13-17J                 13.2.6    GNV: Various GNU tools                     13-170                 13.2.6.1     GCC compiler, 13-18  J                 __________________________________________________________J                 13.3  WHAT IS THE STATUS OF PL/I ON OPENVMS?         13-19  J                 __________________________________________________________J                 13.4  WHERE CAN I GET THE MOZILLA WEB BROWSER?       13-19  J                 __________________________________________________________J                 13.5  WHERE CAN I GET JAVA FOR OPENVMS?              13-20  J                 __________________________________________________________J                 13.6  OBTAINING USER INPUT IN DCL CGI SCRIPT?        13-21  J                                                                        xix E                                 Contents         J                 __________________________________________________________A                 13.7  HOW CAN A BATCH JOB GET ITS OWN BATCH ENTRY J                       NUMBER?                                        13-22  J                 __________________________________________________________J                 13.8  HOW DO I CONVERT TO NEW CMS OR DTM LIBRARIES?  13-22  J                 __________________________________________________________J                 13.9  WHERE CAN I GET PERL FOR OPENVMS?              13-23  J                 __________________________________________________________F                 13.10 OBTAINING THE DECMIGRATE (AEST OR VEST, AND TIE)J                       TRANSLATOR?                                    13-25  J                 __________________________________________________________F                 13.11 WHERE CAN I GET ZIP, UNZIP, SELF-EXTRACTING ZIP,J                       ETC?                                           13-26  J                 __________________________________________________________J                 13.12 ARE VAX HARDWARE EMULATORS AVAILABLE?          13-27  J           ________________________________________________________________J           CHAPTER 14  HARDWARE INFORMATION                            14-1  J                 __________________________________________________________H                 14.1  WHAT ARE THE OPENVMS DIFFERENCES AMONG VAX, ALPHA,J                       AND IA-64?                                      14-1  J                 __________________________________________________________I                 14.2  SEEKING PERFORMANCE INFORMATION FOR ALPHA (AND VAX).J                       SYSTEMS?                                        14-3  J                 __________________________________________________________J                 14.3  CONSOLE COMMANDS, SERIAL LINES, AND CONTROLS?   14-3B                 14.3.1    What commands are available in the AlphaJ                           SRM console?                                14-4J                 14.3.2    What does SRM mean? What is PALcode?        14-4@                 14.3.3    Alpha COM ports and VAX console serialJ                           line information?                           14-5J                 14.3.3.1     Which terminal device name is assigned to the-                              COM ports?, 14-5 D                 14.3.3.2     Which serial port is the console on the1                              MicroVAX 3100?, 14-5EG                 14.3.3.3     How can I set up an alternate console on a .                              VAXstation?, 14-6                      xx_ _  _                              Contents         J                 14.3.3.4     Please explain the back panel of the MicroVAX%                              II, 14-6 <                 14.3.4    What are Alpha console environmentJ                           variables?                                  14-8J                 14.3.5    What are the boot control flag values?      14-9I                 14.3.5.1     What are the I64 IPB boot flag values?, 14-9o=                 14.3.5.2     What are the Alpha APB boot flage+                              values?, 14-10 J                 14.3.5.3     What are the VAX VMB boot flag values?, 14-12?                 14.3.6    How do I boot an AlphaStation withoutlJ                           monitor or keyboard?                       14-15;                 14.3.7    Downloading and using SRM console J                           Firmware?                                  14-16I                 14.3.7.1     Where can I get updated console firmware for 2                              Alpha systems?, 14-16I                 14.3.7.2     How do I reload SRM firmware on a half-flash_1                              Alpha system?, 14-17 J                 14.3.7.3     How do I switch between AlphaBIOS/ARC and SRM-                              consoles?, 14-18 J                 14.3.8    Console Management Options                 14-21J                 14.3.9    Why do my EFI Boot Aliases Fail?           14-22A                 14.3.10   Can OpenVMS access the EFI console Boot J                           Aliases?                                   14-22;                 14.3.11   Downloading and using EFI Console_J                           Firmware?                                  14-22  J                 __________________________________________________________J                 14.4  WHAT PLATFORMS WILL OPENVMS OPERATE ON?        14-24J                 14.4.1    on the Alpha Multia?                       14-26J                 14.4.2    on AlphaPC 164LX? AlphaPC 164SX?           14-28B                 14.4.2.1     on the NoName AXPpci33 system?, 14-28J                 14.4.3    on the Alpha XL series?                    14-29@                 14.4.4    OpenVMS on the Personal Workstation -aJ                           and -au series?                            14-29H                 14.4.4.1     OpenVMS on the Whitebox Windows-Only series*                              Alpha?, 14-31G                 14.4.4.2     OpenVMS and Personal Workstation ATA (IDE) .                              bootstrap?, 14-32J                 14.4.5    On the Intel Itanium IA-64 platform?       14-32:                 14.4.5.1     Where can I get Intel Itanium0                              information?, 14-33      J                                                                        xxi T  E                              Contents         J                 __________________________________________________________F                 14.5  WHAT IS THE LEAST EXPENSIVE SYSTEM THAT WILL RUNJ                       OPENVMS?                                       14-34  J                 __________________________________________________________?                 14.6  WHERE CAN I GET MORE INFORMATION ON ALPHA J                       SYSTEMS?                                       14-35  J                 __________________________________________________________J                 14.7  DESCRIBE ALPHA INSTRUCTION EMULATION AND INSTRUCTIONJ                       SUBSETS?                                       14-36  J                 __________________________________________________________J                 14.8  SO HOW DO I OPEN UP THE DEC 3000 CHASSIS?      14-38  J                 __________________________________________________________J                 14.9  WHAT IS BYTE SWIZZLING?                        14-38  J                 __________________________________________________________B                 14.10 WHAT IS THE LAYOUT OF THE VAX FLOATING POINTJ                       FORMAT?                                        14-40  J                 __________________________________________________________J                 14.11 WHERE CAN I FIND MORE INFO ABOUT VAX SYSTEMS?  14-41  J                 __________________________________________________________D                 14.12 WHERE CAN I FIND INFORMATION ON NETBSD FOR VAXJ                       SYSTEMS?                                       14-41  J                 __________________________________________________________E                 14.13 WHAT SYSTEM DISK SIZE LIMIT ON THE MICROVAX AND J                       VAXSTATION 3100?                               14-41  J                 __________________________________________________________J                 14.14 WHAT ARE THE VAX PROCESSOR (CPU) CODES?        14-43  J                 __________________________________________________________C                 14.15 WHERE CAN I GET SOFTWARE AND HARDWARE SUPPORTEJ                       INFORMATION?                                   14-44  J                 __________________________________________________________G                 14.16 WHERE CAN I GET HARDWARE SELF-MAINTENANCE SUPPORTFJ                       ASSISTANCE?                                    14-45  J                 __________________________________________________________D                 14.17 WHY DOES MY SYSTEM HALT WHEN I POWER-CYCLE THEJ                       CONSOLE TERMINAL?                              14-45                      xxii_ _  _                              Contents_        J                 __________________________________________________________I                 14.18 CAN I REUSE OLD KEYBOARDS, MICE AND MONITORS WITH A J                       PC?                                            14-46  J                 __________________________________________________________C                 14.19 WHICH VIDEO MONITOR WORKS WITH WHICH GRAPHICS_J                       CONTROLLER?                                    14-48  J                 __________________________________________________________<                 14.20 WHERE CAN I GET INFORMATION ON STORAGEJ                       HARDWARE?                                      14-49  J                 __________________________________________________________=                 14.21 WHY DOES MY LK401 KEYBOARD UNEXPECTEDLYNJ                       AUTOREPEAT?                                    14-50  J                 __________________________________________________________I                 14.22 PROBLEM - MY LK411 SENDS THE WRONG KEYCODES OR SOME J                       KEYS ARE DEAD                                  14-51  J                 __________________________________________________________B                 14.23 WHICH DE500 VARIANT WORKS WITH WHICH OPENVMSJ                       VERSION?                                       14-51  J                 __________________________________________________________B                 14.24 HOW DO I SET THE SPEED AND DUPLEX ON OPENVMSJ                       I64?                                           14-53  J                 __________________________________________________________0                 14.25 THIRD-PARTY OR UNSUPPORTEDJ                       DISK/TAPE/CONTROLLERS/SCSI/WIDGETS?            14-539                 14.25.1   Lists of third-party widgets onRJ                           OpenVMS?                                   14-56A                 14.25.2   Are the 2X-KZPCA-AA and SN-KZPCA-AA LVDTJ                           Ultra2 SCSI?                               14-57J                 14.25.3   Resolving DRVERR fatal device error?       14-57  J                 __________________________________________________________J                 14.26 LOOKING FOR CONNECTOR WIRING PIN-OUTS?         14-57  J                 __________________________________________________________=                 14.27 WHAT CONNECTORS AND WIRING ADAPTERS ARE J                       AVAILABLE?                                     14-60  J                 __________________________________________________________J                 14.28 WHAT IS FLOW CONTROL AND HOW DOES IT WORK?     14-63  J                                                                      xxiii    6                              ContentsU        J                 __________________________________________________________J                 14.29 CD AND DVD DEVICE REQUIREMENTS?                14-64  J                 __________________________________________________________@                 14.30 OFFICE-FRIENDLY (QUIETER) INTEGRITY RX2620J                       SERIES?                                        14-66  J                 __________________________________________________________@                 14.31 KVM SWITCHES FOR ALPHASERVER AND INTEGRITYJ                       SERVERS?                                       14-67  J           ________________________________________________________________J           CHAPTER 15  INFORMATION ON NETWORKS AND CLUSTERS            15-1  J                 __________________________________________________________J                 15.1  HOW TO CONNECT OPENVMS TO A MODEM?              15-1  J                 __________________________________________________________J                 15.2  OPENVMS AND IP NETWORKING?                      15-1J                 15.2.1    How to connect OpenVMS to the Internet?     15-1J                 15.2.2    Connecting to an IP Printer?                15-2C                 15.2.3    How do I connect a PostScript printer via_J                           TCP/IP?                                     15-3<                 15.2.4    How do I set a default IP route orJ                           gateway on OpenVMS?                         15-4?                 15.2.5    How can I set up reverse telnet (like J                           reverse LAT)?                               15-4C                 15.2.6    Why can't I use PPP and RAS to connect to J                           OpenVMS Alpha?                              15-4  J                 __________________________________________________________J                 15.3  OPENVMS AND DECNET NETWORKING?                  15-5J                 15.3.1    Can DECnet-Plus operate over IP?            15-5>                 15.3.2    What does "failure on back translateJ                           address request" mean?                      15-5J                 15.3.3    Performing SET HOST/MOP in DECnet-Plus?     15-6>                 15.3.4    How to flush the DECnet-Plus sessionJ                           cache?                                      15-6                                xxivA S                                 Contents         J                 __________________________________________________________;                 15.4  HOW TO DETERMINE THE NETWORK HARDWARE_J                       ADDRESS?                                        15-7B                 15.4.1    How do I reset the LAN (DECnet-Plus NCL)J                           error counters?                             15-9A                 15.4.2    How do I install DECnet Phase IV on VMSNJ                           7.1?                                        15-9  J                 __________________________________________________________B                 15.5  HOW CAN I SEND (RADIO) PAGES FROM MY OPENVMSJ                       SYSTEM?                                        15-11  J                 __________________________________________________________J                 15.6  OPENVMS, CLUSTERS, VOLUME SHADOWING?           15-11A                 15.6.1    OpenVMS Cluster Communications ProtocolNJ                           Details?                                   15-12D                 15.6.1.1     OpenVMS Cluster (SCS) over DECnet? Over'                              IP?, 15-12 B                 15.6.1.2     Configuring Cluster SCS for path load.                              balancing?, 15-139                 15.6.1.2.1    Cluster Terminology?, 15-13 D                 15.6.1.2.2    Cluster Communications Control?, 15-14F                 15.6.1.2.3    Cluster Communications Control Tools and/                               Utilities?, 15-15 J                 15.6.2    Cluster System Parameter Settings?         15-16I                 15.6.2.1     What is the correct value for EXPECTED_VOTESD4                              in a VMScluster?, 15-16H                 15.6.2.1.1    Why no shadowing for a Quorum Disk?, 15-19D                 15.6.2.2     Explain disk (or tape) allocation class-                              settings?, 15-19_E                 15.6.2.2.1    How to configure allocation classes and 5                               Multi-Path SCSI?, 15-20_<                 15.6.3    Tell me about SET HOST/DUP and SETJ                           HOST/HSC                                   15-21J                 15.6.4    How do I rename a DSSI disk (or tape?)     15-23?                 15.6.5    Where can I get Fibre Channel Storage J                           (SAN) information?                         15-24B                 15.6.6    Which files must be shared in an OpenVMSJ                           Cluster?                                   15-24J                 15.6.7    How can I split up an OpenVMS Cluster?     15-25J                 15.6.8    Details on Volume Shadowing?               15-27E                 15.6.8.1     Does volume shadowing require a non-zero_7                              allocation classes?, 15-27   J                                                                        xxv A  ?                              Contents         J           ________________________________________________________________           INDEX   J           ________________________________________________________________           TABLES  J                 1-1   Core Websites                                    1-1  J                 1-2   INFO-VAX Mail Server Commands                    1-4  J                 2-1   OpenVMS Alpha Media Kits                         2-6  J                 2-2   OpenVMS I64 Order Numbers                        2-7  J                 2-3   OpenVMS I64 Media Suffix                         2-7  J                 2-4   OpenVMS Source Listings Kits                     2-8  J                 2-5   OpenVMS Alpha Version Rule-Of-Thumb             2-18  J                 3-1   OpenVMS Websites                                 3-2  J                 3-2   OpenVMS Tutorial and Documentation Websites      3-6  J                 3-3   DP Books                                         3-8  J                 3-4   OpenVMS Mailing Lists                           3-10  J                 3-5   OpenVMS Discussion Forums                       3-11  J                 5-1   PCSI Generation Number                          5-44  J                 11-1  X Windows Display Commands                      11-1  J                 14-1  I64 Conversational Bootstrap Flags             14-10  J                 14-2  Alpha Conversational Bootstrap Flags           14-11  J                 14-3  VAX Conversational Bootstrap Flags             14-12  J                 14-4  DE500 Speed and Duplex Settings                14-52  J                 14-5  DEC MMJ Pin-out                                14-57  J                 14-6  PC DB9 Pin-out                                 14-59  J                 14-7  MicroVAX DB9 Pin-out                           14-59  J                 14-8  DECconnect MMJ Connectors and Adapters         14-61  J                 15-1  Cluster Common Shared Files                    15-24                      xxvi  8                     J           ________________________________________________________________             Prefaced                                                                                    J                                                                          i                       J           ________________________________________________________________  2           OpenVMS Frequently Asked Questions (FAQ)    G                    This is the OpenVMS Frequently Asked Questions (FAQ) F                    posting for the comp.os.vms and comp.sys.dec usenet                    newsgroups.  ?                                Suggestions and Updates Welcome!T  ?                       Please send your suggestions for changes, F                       additions, or corrections directly to FAQ Editor1                       (hoff{atsign}hp{period}com)   =                                  No Support Questions, PleaseI  C                       Please do not send technical questions to the F                       FAQ Editor (hoff{atsign}hp{period}com) . The FAQD                       Editor (hoff{atsign}hp{period}com) is not in aB                       position to answer general questions, nor toE                       provide general product support. Rather, please G                       post your questions to the appropriate newsgroup,_F                       or please contact your preferred hardware and/or@                       software support organization(s) directly.  B                       Your understanding in this matter is greatly"                       appreciated.  B                    If you believe any particular discussion worthyB                    of inclusion in a future edition of the FAQ andG                    particularly once you have or know both the question I                    and the answer, please then send the entire discussion_J                    along to the FAQ Editor (hoff{atsign}hp{period}com) for'                    potential inclusion..  J                    Do note that the FAQ Editor (hoff{atsign}hp{period}com)F                    takes URL link continuity seriously, and strives toD                    maintain current links. This is, however, a largeD                    task, and it is only becoming more difficult. URLA                    link continuity is also something that you can D                    assist with, of course. If you should find a deadE                    link or a stale URL pointer, please notify the FAQ C                    Editor (hoff{atsign}hp{period}com) . If you have C                    or can find the current, correct or updated URL,AA                    of course, that greatly assists the FAQ Editor   J                                                                        iii _  _          ;                    OpenVMS Frequently Asked Questions (FAQ)         F                    (hoff{atsign}hp{period}com) in maintaining the most(                    current set of links.                      Thank you!   =                                 Post to Newsgroups With Care!   @                       Please consider reading Section 1.3 before=                       posting to the comp.os.vms or any other_G                       newsgroups. (What you post can come back to hauntN                       you.)   '           _____________________________            Contributors  E                    Many people have contributed to this FAQ, directly C                    and/or indirectly. In many cases, part or all of F                    an answer included in the FAQ has been adapted fromE                    one or more postings from the comp.os.vms or other J                    newsgroup-this though individual citations and specificE                    quotations are generally not included in this FAQ. H                    (The FAQ Editor (hoff{atsign}hp{period}com) wishes toF                    thank to all of those folks who post answers to theH                    newsgroups, and that have contributed to the contentsC                    of and to the general improvements of this FAQ.)   H                    The following is an incomplete list of the folks thatJ                    have contributed directly or indirectly to the contentsJ                    of the OpenVMS FAQ. Additions, corrections, and updatesF                    to this list of contributors and to the contents ofD                    the FAQ itself are welcome, and all omissions andH                    misspellings are unintentional. Thanks to each of theG                    contributors here, and to all of the folks that haveEA                    participated in the FAQ and in the newsgroups.   D                    Jim Agnew, Paul Anderson, Jason Armistead, ZoltanC                    Arpadffy, John AtoZ, Bailey, Gary Barclay, (The)BE                    Beav, Jeremy Begg, Colin Blake, Fabrice Blanquart, F                    Ken Blaylock, Kenneth Block, Bol, Craig Berry, MarkH                    Berryman, Jim Becker, Verell Boaen, Bol, Jim Brankin,H                    Richard Brodie, Colin Butcher, Robert Alan Byer, JeffC                    Campbell, Scott Campbell, Antonio Carlini, Keith_F                    Cayemberg, Ken Chaney, Cristy, John Croll, David J.I                    Dachtera, Robert Deininger, Dale Dellutri, Leo Demers,_G                    Sue Denham, Thomas Dickey, Eric Dittman, Mike Duffy,AJ                    Jim Dunham, Eric, Glenn Everhart, Ken Fairfield, Yaacov                      iv     1          ;                    OpenVMS Frequently Asked Questions (FAQ)_        C                    Fenster, Gunther Froehlin, Harry Garonzik, Derek F                    Garson, John Gillings, Andy Goldstein, Clair Grant,G                    Hunter Goatley, Ruth Goldenberg, Vance Haemmerle, Ki_J                    Suk Hahn, SHarris, Rich Hearn, Fletcher Hearns, PhillipI                    Helbig, Hein van den Heuvel, Stephen Hoffman, Eberhard_J                    Heuser-Hofmann, Sue Holt, Mark Hopkins, Horn, Jaf, LeifG                    Jansson, Kevin Jenkins, Don R. Jones, Henry Juengst,_C                    inazu_k, Geoff Kingsmill, Fred Kleinsorge, FelixRI                    Kreisel, Veli Korkko, Ruslan R. Laishev, Peter "EPLAN" F                    Langstoeger, Norm Lastovica, p_lee, Jerry Leichter,C                    Richard Levitte, Tom Linden, Steve Lionel, Denis H                    Maillard, Kerry Main, John E. Malmberg, David Mathog,H                    Dale Miller, Ian Miller, Dick Munroe, Patrick Moreau,J                    Morrison, otis, George Pagliarulo, Keith Parris, Plass,F                    pvhp, David Rabahy, Stan Rabinowitz, Mike Raspuzzi,E                    Steve Reece, Neil Rieck, Ian Ring, Aaron Sakovich,IE                    Warren Sander, Mark Schafer, Brian Schenkenberger, E                    Atlant Schmidt, Wayne Sewell, Steven Shamlian, Sue_F                    Skonetski, Scott Snadow, Sue Sommer, Scott Squires,I                    stfp, Dave Sweeney, Mike Thompson, Arne Vajhj, Martin_H                    Vorlnder, Peter Weaver, William Webb, Williams, Paul(                    Winalski, Uwe Zinser.  D                    Again, any omission from this list and any errorsE                    or misspellings are entirely unintentional. Please G                    notify the FAQ Editor (hoff{atsign}hp{period}com) of_D                    any omissions, corrections, or updates that mightD                    be needed within this list. And thanks to each ofG                    these individuals for their assistance and for theirID                    contributions, and particularly for sharing their                    expertise._  D           __________________________________________________________(           FAQ Archives and FAQ Locations  J                    The OpenVMS FAQ is archived in (at least) the following                    locations:   7                    o  http://www.hp.com/go/openvms/faq/_  @                    o  ftp://rtfm.mit.edu/pub/usenet/comp.os.vms/  '                    o  news:comp.answers   '                    o  news:news.answers   *                    o  http://www.faqs.org/  J                                                                          v               ;                    OpenVMS Frequently Asked Questions (FAQ)         ,                    o  http://www.google.com/  9                    o  http://eisner.decus.org/vms/faq.htm   0                    o  http://www.hoffmanlabs.org  G                    Other internet FAQs are generally available in these                     locations:   )                    o  news://comp.answers_  )                    o  news://news.answers   4                    o  ftp://rtfm.mit.edu/pub/usenet/  *                    o  http://www.faqs.org/  ,                    o  http://www.google.com/  D           __________________________________________________________5           FAQ File Formats and Production Information   C                    This FAQ is available in ASCII text, Postscript, F                    Bookreader, and HTML, and potentially in other fileJ                    formats. Certain formats, such as the Adobe Acrobat PDFF                    conversion from the Postscript format, are providedC                    downstream from the FAQ text formatting, and areL5                    provided and maintained by others.   I                    As the HTML-format FAQ is not a single monolithic (anddI                    accordingly large) HTML file, it is the most difficult1B                    format to search using the most common standardF                    (platform-local) tools. Accordingly, the FAQ EditorF                    (hoff{atsign}hp{period}com) recommends downloading,A                    using and searching the ASCII text FAQ format.R  D                    The OpenVMS FAQ is maintained in DECdocument SDMLH                    format and all FAQ maintenance and the primary outputC                    file format conversions are performed on OpenVMS G                    systems. For information on the DECdocument product,_5                    please contact Touch Technologies.1                          viW I  A          ;                    OpenVMS Frequently Asked Questions (FAQ)_      D           __________________________________________________________6           Old FAQ Section Notations Available in Index  I                    For the folks that are familiar with older editions of_H                    this FAQ and specifically for those folks looking forH                    the older section name keywords, please see the indexH                    entries located under FAQ Sections (Old). These olderE                    section names include the prefixes DCL, DECW, DOC,_I                    FILES, MISC, MGMT, INTRO, SOFT, VMS, etc., followed by1&                    the section number.  D           __________________________________________________________           The Fine Print  F                    Corrections and suggestions are welcome. Should youJ                    believe you can provide better stewardship of this FAQ,G                    or should you have strong feelings over the content, H                    structure, organization or implementation of the FAQ,D                    do realize you may be offered the editorship. TheF                    editor maintains this document as a free service to)                    the OpenVMS community._  C                    While the information contained here is believedAG                    correct, the use of any and all information acquired_D                    from this document is entirely at the risk of theD                    user(s). If your system should crash or your dataF                    should become corrupted or the answer(s) found hereJ                    should be found erroneous, that is solely your risk and'                    your responsibility.H  B                    Though the editor of this FAQ is an employee ofE                    Hewlett-Packard Company (HP), this posting and the_F                    information contained within this FAQ are is not anH                    official statement of HP, nor a commitment by HP. AllG                    information, comments or opinions included, cited or_G                    otherwise referenced here may or may not reflect theIH                    stated opinions of HP, of the editor, or of any other                    entity.  J                    All trademarks, registered trademarks, servicemarks andJ                    registered servicemarks used or referenced here are theF                    properties of their respective owner(s) or holders.D                    Please route any corrections, requests or relatedH                    updates to the FAQ Editor (hoff{atsign}hp{period}com)  J                                                                        vii M             ;                    OpenVMS Frequently Asked Questions (FAQ)         J                    The redistribution, reposting and/or the web-serving ofH                    complete and unaltered copies of this FAQ document isD                    permitted. Other uses only with prior permission.  ;                    The master copy of this FAQ is posted at   6                    o  http://www.hp.com/go/openvms/faq  F                    Translations of this FAQ into various languages mayD                    be available, please contact the maintainer(s) ofE                    any translated document for assistance or feedbackOF                    involving the particular translated edition of this                    FAQ._                                                                                  viii9                         J                    _______________________________________________________             1        Introduction       D           __________________________________________________________:           1.1  What core OpenVMS URLs do you need to know?  D                    If you have no other OpenVMS URLs bookmarked, youC                    will want to be familiar with the URLs listed in                     Table 1-1:   J           ________________________________________________________________"           Table 1-1  Core Websites  J           ________________________________________________________________J           URL_______Contents______________________________________________  B           Core OpenVMS Information, including roadmaps and release           schedules   1                     http://www.hp.com/go/openvms/_  8           OpenVMS and Core Layered Product Documentation  5                     http://www.hp.com/go/openvms/doc/   G           Core OpenVMS Support Search Engine URLs, the ITRC support and C           discussion forums, and the ITRC FTP-accessable Patch Area   D                     http://www2.itrc.hp.com/service/james/CPQhome.doI                     (formerly the NLSA Natural Language Search Assistant, '                     and formerly AskQ.),  +                     http://www.itrc.hp.com/   :                     ftp://ftp.itrc.hp.com/openvms_patches/             The OpenVMS Freeware  :                     http://www.hp.com/go/openvms/freeware/  .           The OpenVMS Hobbyist License Program  3                     http://www.openvmshobbyist.org/_  J                                                                        1-1                                   Introduction_      J           ________________________________________________________________*           Table 1-1 (Cont.)  Core Websites  J           ________________________________________________________________J           URL_______Contents______________________________________________  G                     http://h71000.www7.hp.com/openvms/license_software_ J           __________programs/index.html___________________________________  D           __________________________________________________________6           1.2  What are the OpenVMS Usenet Newsgroups?  H                    There are a huge number of newsgroups available, someE                    of which discuss topics of interest to folks using D                    OpenVMS operating system. Key among these are theF                    comp.os.vms newsgroup and the vmsnet.* heirarchy of                    newsgroups.  '           _____________________________ @           1.2.1  What is the scope of the comp.os.vms newsgroup?  E                    The comp.os.vms newsgroup is the primary newsgroup-H                    for discussion of the HP OpenVMS operating system andI                    the computer systems on which it runs. Questions about3J                    layered products which run on OpenVMS are also welcome,I                    though many of them (in particular, language compilers J                    and database systems) have more specific newsgroups. IfJ                    a question has some relationship to OpenVMS, it belongs#                    in comp.os.vms/.o  '           _____________________________a?           1.2.2  What newsgroups carry VMS-related information?4  F                    The vmsnet.* hierarchy is operated by the EncompassF                    users group (formerly known as DECUS), and containsH                    various newsgroups of interest, including vmsnet.misc$                    and vmsnet.alpha.  I                    Sprechen Sie Deutsch? Besuchen Sie bitte den newsgroup "                    de.comp.os.vms.  I                    The comp.sys.dec newsgroup carries general discussions F                    about various HP computer systems, and specificallyB                    systems that were acquired by HP as part of theF                    acquisition of Compaq, systems which had previouslyH                    been acquired by Compaq as part of the acquisition of;                    Digital Equipment Corporation (DIGITAL).l                      1-2                                   Introduction3        J                    Also of interest are resources and conferencing systemsH                    including Encompasserve (formerly known as DECUServe)7                    and Ken Farmer's OpenVMS.Org forums:   0                    o  telnet://eisner.decus.org/  -                    o  http://www.openvms.org/B  '           _____________________________ 7           1.2.3  What newsgroup archives are available?3  >                    Extensive archives of INFO-VAX mailings andI                    comp.os.vms postings are archived and available at SRI_H                    International: http://mvb.saic.com/freeware/info-vax/  I                    Google also has extensive newsgroup archives available1                    at?  ,                    o  http://www.google.com/  '           _____________________________ 3           1.2.4  What is the INFO-VAX mailing list?a  F                    INFO-VAX is a mailing list which is bidirectionallyJ                    gatewayed to the comp.os.vms newsgroup. This means thatJ                    postings to comp.os.vms get automatically sent to INFO-I                    VAX subscribers and messages sent to the INFO-VAX listn:                    are automatically posted to comp.os.vms  E                    INFO-VAX can be a useful way to participate in the G                    newsgroup if you can't access the newsgroup directly G                    through a newsreader. Note that INFO-VAX is a closed5F                    mailing list, which means that only subscribers mayI                    post to it. Please see Section 1.2.4.1 for information F                    on how to subscribe, and how you can subscribe suchF                    that you can post from multiple addresses but stillA                    receive no more than one copy of the mailings.T  E                    Please remember that propogation delays can and do J                    vary, meaning that mailings and postings may be delayedC                    or even lost. It is quite possible that postingsIG                    may not be delivered for several days, and that some B                    postings will appear out of the expected order.  D                    For details on the available archives, please see!                    Section 1.2.3.   J                                                                        1-3                                   Introduction_      '           _____________________________DF           1.2.4.1  How do I subscribe to or unsubscribe from INFO-VAX?  E                    The address for subscription requests is Info-VAX- E                    Request[at]Mvb.Saic.Com. Subscription requests are D                    handled automatically by a mail server. This mailE                    server ignores the subject line and processes each 4                    line of the message as a command.  H                    The syntax for subscribing and unsubscribing, as wellF                    as setting various parameters on your subscription,                    is:  J           ________________________________________________________________2           Table 1-2  INFO-VAX Mail Server Commands  J                    _______________________________________________________J                    Command____________________Description_________________  I                    HELP                       Acquire information on mail 4                                               server  F                    SUBSCRIBE INFO-VAX         Join to the mailing list  D                    UNSUBSCRIBE INFO-VAX       Leave the mailing list  E                    SET INFO-VAX DIGEST        Select periodic omnibus_I                                               mail messages from the mailOJ                                               server, rather than multipleJ                                               individual messages for each6                                               posting.  G                    SET INFO-VAX NODIGEST      Separate mail delivery ofIA                                               each message posted   H                    SET INFO-VAX NOMAIL        Establish an email addressI                                               for posting, though not for >                                               receiving, mail.  H                    SET INFO-VAX MAIL          Establish an email addressF                                               for both posting and forE                                               receiving mail from theTJ           ____________________________________mailing_list._______________  A                    The mail server is not case-sensitive; case is_E                    irrelevant. Settings and policies can be retrievedH>                    from the mail server, typically using HELP.  J                    The INFO-VAX moderator can be contacted directly at the?                    email address Mark.Berryman[at]Mvb.Saic.Com.O                      1-4                                   Introduction       D           __________________________________________________________$           1.3  What is [n]etiquette?  D                    Before posting or emailing a question, please useE                    the available local resources, such as the OpenVMS_G                    manuals, the HELP, and the resources and information4I                    in and referenced by this FAQ. Please use these first. F                    Also please specifically read the release notes andH                    (if appropriate) the cover letter for the product youH                    are using. (The release notes are generally placed inI                    SYS$HELP:.) Quite often, these simple steps will allow J                    you to quickly find the answer to your own question-andG                    more quickly than waiting for a response to question D                    posted to a newsgroup, too. These steps will saveF                    you time, and will also help ensure you have a goodF                    reputation with the folks that might be included toF                    answer one of your future questions, a question notI                    covered in these resources. Put another way, if you do G                    not want your questions to be ignored in the future-PG                    and please remember that the folks in the newsgroups F                    do not have to answer your questions-you won't wantG                    to "annoy the natives" by asking a question that has_E                    already been answered far more times more than you E                    might have realized, or a question whose answer is_A                    readily available had you made a small effort.2  >                    When posting, please consider the following                    suggestions:   F                    o  There is no particularly reliable way to recall,H                       erase, delete, or otherwise hide a message once itF                       is emailed or once posted. Once your message hasG                       reached an external email server or multiple newseI                       servers, the entire text is effectively a permanent_E                       fixture of the network. And using the available F                       search engines, a fixture that is easy to locateH                       and to correlate. (Do not assume that all tools orF                       archives will honor the do-not-cache attributes,J                       either-postings marked as such can be among the most<                       interesting ones to cache, after all.)  I                       For details on some of the many available archives, /                       please see Section 1.2.3._    J                                                                        1-5 O  N                              Introduction         H                    o  Include a valid e-mail address in the text of yourF                       posting or in a "signature" appended to the end.F                       Reply-to addresses in headers often get garbled.H                       Anonymous addresses can also simply be ignored, asI                       fake addresses are regularly used by folks that are5H                       "trolling" and by folks that are spamming. (ThoughE                       to avoid spam-harvesting of your email address,iD                       consider adding characters or a field into theJ                       address-but remember to include details around whichJ                       characters or fields should be removed or altered ifA                       you decide to be particularly clever here.)   D                    o  If you are submitting a question, please be asG                       specific as you can. Include relevant information G                       such as processor type, product versions (OpenVMS I                       and layered products that apply), error message(s), D                       DCL command(s) used, and a short, reproducibleC                       example of problems. Say what you've tried so H                       far, so that effort isn't duplicated. Keep in mindG                       that there's not yet a telepathy protocol for the5H                       Internet. (The more detailed your description, theJ                       better that people can help you with your question.)  G                    o  If responding to a posting, include in your reply J                       only as much of the original posting as is necessaryI                       to establish context. As a guideline, consider that_E                       if you've included more text than you've added, F                       you've possibly included too much. Never include?                       signatures and other irrelevant material.   D                    o  Please be polite. If the question isn't wordedE                       the way you think is correct or doesn't include C                       the information you want, try to imagine what F                       the problem might be if viewed from the poster'sC                       perspective. Requests for additional detailedFD                       information are often better sent through mail:                       rather than posted to the newsgroup.  A                    o  If you have a problem with HP (or any other,C                       vendor's) product, please use the appropriate C                       support channel. Do not assume that newsgroup I                       postings will get read, will be responded to by the J                       appropriate developers, or will be later followed up                       upon.6                      1-6 S  f                              Introductionb        H                    o  If you are posting from a web browser, news readerG                       or if you are posting via email sent to INFO-VAX, I                       please turn off MIME, vcard, attachments, and other D                       mechanisms that assume anyone reading the postH                       has the corresponding capability-use the text-onlyI                       option of your web browser, news reader, or mailer.iE                       Usenet is traditionally a text-only medium, andfG                       many comp.os.vms participants will use tools thataJ                       have this support disabled, or that do not have thisI                       support. If the message uses MIME or attachments or H                       such, the text of your message will be buried in aG                       large pile of gibberish, and some tools will send J                       multiple copies of the text within a single posting.  H                    o  If you find that the postings of a particular userE                       are uninteresting, annoying, or off-topic, most I                       newsreaders include a filter or killfile mechanism, B                       and many mail clients have similar filteringE                       capabilities. Please do not "flame"-to email or G                       to post vitriol - any individual that might annoylF                       you, please enable and filter all of that user'sG                       postings. Posting of vitriol and of "flames" willoI                       eventually come back to haunt you; netizens and the J                       net itself have a very large and a very long memory.G                       Similarly, readers that decide that your postings_F                       are not worthy of reading will similarly tend toH                       filter or to killfile all of your postings. Please0                       play nice, in other words.  B                    Before posting your question to the comp.os.vmsJ                    newsgroup or sending your message to the INFO-VAX list,J                    also please take the time to review available etiquetteF                    information, such as that included in the following                    documents:   4                    widftp://rtfm.mit.edu/pub/usenet/6                       news.answers/usenet/primer/part1  4                    widftp://rtfm.mit.edu/pub/usenet/3                       news.answers/usenet/faq/part1   4                    widftp://rtfm.mit.edu/pub/usenet/>                       news.answers/usenet/emily-postnews/part1  J                                                                        1-7                                   Introduction         4                    widftp://rtfm.mit.edu/pub/usenet/=                       news.answers/usenet/writing-style/part1   4                    widftp://rtfm.mit.edu/pub/usenet/=                       news.answers/usenet/posting-rules/part1o  B                    This information will document the etiquette ofJ                    newsgroups, as well as providing you with the knowledgeH                    the vast amount of newsgroup-related information thatG                    is readily available to you, and where to find it...   1                                              Note   A                       Please do not post security holes or system                        crashers  F                       Rather, please report these problems directly toE                       HP. Why? So that HP has a chance to resolve and F                       distribute a fix before other customer sites can"                       be affected.  A                       Most folks in the newsgroups are honest and_>                       deserve to know about potential securityA                       problems, but a few folks can and will make C                       nefarious use of this same information. Other ?                       sites will hopefully return the courtesy,_=                       and will not post information that will ?                       potentially compromise your site and yourt+                       computer environment.   D           __________________________________________________________8           1.4  What OpenVMS user group(s) are available?  C                    Encompass, the Enterprise Computing Association,eF                    is a user group comprised of information technologyG                    professionals that are interested in the Enterprise-hC                    oriented products, services, and technologies ofnE                    Compaq and of the former DIGITAL. Encompass offersoI                    newsletters, the Encompass website, and offers variousTF                    gatherings and related services, including symposia9                    events and local users group meetings.t  I                    Encompass is a descendent of the organization known aspG                    DECUS, the Digital Equipment Computer Users Society.g                      1-8    p                              Introductionr        F                    For more information on Encompass, please visit the&                    Encompass web site:  1                    o  http://www.encompassus.org/   F                    The organization comprised of customers of Hewlett-J                    Packard Company (HP) that is probably most analogous to9                    the Encompass organization is Interex:   -                    o  http://www.interex.org/s  B                    Like Encompass, Interex offers various servicesF                    and events of interest to folks that presently workG                    with and/or that wish to learn about HP products andoI                    offerings. Please see the Interex website for details.   D           __________________________________________________________7           1.5  OpenVMS Support, Questions and Comments?i  F                    The following section includes contacts for OpenVMSG                    Feedback, and information on how to obtain technicale'                    support information.L  '           _____________________________ @           1.5.1  Corporate contacts for OpenVMS Business Issues?  J                    The HP corporate contact for OpenVMS business issues isI                    Ann McQuaid, the HP General Manager directly in charge D                    of OpenVMS and OpenVMS Engineering, while featureF                    requests and other related matters should be routedE                    to MaryJane Vazquez, the OpenVMS Business Manager.t  H                    Ann and MaryJane will quite obviously respond best toJ                    cogently-worded OpenVMS corporate-level business issuesE                    or requests. With all due respect to all involved, H                    neither Ann nor MaryJane are appropriate contacts forF                    technical support matters nor for technical supportJ                    requests, nor for any other non-corporate-related, non-J                    business-related issues-these questions are best routedG                    to the local or regional customer support center; to @                    the support, technical and engineering teams.  H                    To reach Ann or MaryJane via electronic mail, place aH                    dot between the first and the surname, and append the*                    expected HP.COM domain.  J                                                                        1-9 r  }                              Introduction       '           _____________________________ %           1.5.2  OpenVMS Ambassadors?e  G                    The OpenVMS Ambassadors are senior HP engineers withoH                    advanced technical knowledge and advanced training inI                    OpenVMS, with detailed knowledge of current and futurenH                    OpenVMS releases and product plans, and with contactsE                    directly with the HP and ISV hardware and softwaretC                    engineering organizations developing OpenVMS andcJ                    OpenVMS hardware platforms, as well as layered productsG                    and tools. Further, Ambassadors are experienced withlB                    integrating HP OpenVMS and application-specificB                    products and ISV applications to solve specific)                    business requirements.   F                    OpenVMS Ambassadors are based throughout the world.  F                    Your HP sales representative or HP reseller will beG                    able connect you with your local OpenVMS Ambassador.r  '           _____________________________rD           1.5.3  Contact for OpenVMS Marketing Issues and Questions?  *                    Please see Section 3.4.  '           _____________________________ ;           1.5.4  Contact URLs for OpenVMS Technical Issues?.  E                    For formal technical issues and technical support,sH                    please contact your software support organization, orH                    your local HP Customer Support Center or HP Reseller.B                    In North America, you can call 1-800-HP-INVENT.  =                    For informal (free) support resources, see 9                    the newsgroups including comp.os.vms ( >                    news://comp.os.vms/  comp.os.vms ), see the<                    ITRC discussion forums, the James supportC                    database search engine (search assistant tool) (tC                    http://www2.itrc.hp.com/service/james/CPQhome.do E                    ), and see sections of this document including the,H                    platform support information in Section 14.4, sourcesE                    of software and hardware support in Section 14.15,mE                    information on third-party devices and unsupportedRI                    hardware in Section 14.25, and the many other sectionso$                    of this document.                      1-10     d                              Introduction         J                    Please remember to review and to bookmark the following                     support URLs:  3                    o  http://www.hp.com/go/openvms/a  F                    o  http://www2.itrc.hp.com/service/james/CPQhome.do  E                    o  http://www.hp.com/go/openvms/wizard/ (reference >                       only; use ITRC forums for new questions)  <                    o  ftp://ftp.itrc.hp.com/openvms_patches/                                                                  J                                                                       1-11    e                    J                    _______________________________________________________  &           2        General Information      D           __________________________________________________________4           2.1  What is OpenVMS? What is its history?  J                    OpenVMS, originally called VMS (Virtual Memory System),H                    was first conceived in 1976 as a new operating systemC                    for the then-new, 32-bit, virtual memory line ofsC                    computers, eventually named VAX (Virtual Addresse                    eXtension).  J                    The first VAX model, the 11/780, was code-named "Star",D                    hence the code name for the VMS operating system,F                    "Starlet", a name that remains to this day the nameD                    for the system library files (STARLET.OLB, etc.).  H                    VMS version X0.5 was the first released to customers,J                    in support of the hardware beta test of the VAX-11/780,G                    in 1977. VAX/VMS Version V1.0 shipped in 1978, along 7                    with the first revenue-ship 11/780s.w  >                    OpenVMS was designed entirely within HP andC                    specifically within the former Digital EquipmentFH                    Corporation (DIGITAL). Two of the principal designersI                    were Dave Cutler and Dick Hustvedt, though with a wide G                    variety of other contributors. OpenVMS was conceivedOD                    as a 32-bit, virtual memory successor to the RSX-C                    11M operating system for the PDP-11. Many of the D                    original designers and programmers of OpenVMS hadG                    worked previously on RSX-11M, and many concepts from 8                    RSX-11M were carried over to OpenVMS.  I                    OpenVMS VAX is a 32-bit, multitasking, multiprocessingF;                    virtual memory operating system. Current A                    implementations run on VAX systems from HP andoC                    other vendors, as well as on hardware emulators;fF                    for additional information on emulators, please see$                    Section 13.12 and    J                                                                        2-1 r             &                    General Information        J                    OpenVMS Alpha is a 64-bit multitasking, multiprocessing;                    virtual memory operating system. CurrentsJ                    implementations run on Alpha systems from HP, and other                    vendors.t  B                    OpenVMS has also been ported to the Intel IA-64A                    architecture, and specifically to HP Integrity G                    systems using microprocessors from the Intel ItaniumeF                    Processor Family. This implementation of OpenVMS isI                    officially known as "HP OpenVMS for Integrity Servers"oF                    and more commonly as "OpenVMS I64", and it operatesC                    in the native Itanium IA-64 architecture and 64-sD                    bit environment. OpenVMS I64 provides support forJ                    applications requiring 32- or 64-bit virtual addressingI                    capabilities entirely within the native 64-bit Itanium J                    execution environment. (For details on this and related;                    terminology, please see Section 14.4.5.)   G                    For more details on OpenVMS and its features, please D                    read the OpenVMS Software Product Description at:  9                    o  http://h18000.www1.hp.com/info/spd/o  H                       OpenVMS typically uses SPD 25.01.xx, SPD 41.87.xx,'                       and SPD 82.35.xx.N  D                    Additional information on the general features ofJ                    various OpenVMS releases, release dates, as well as theJ                    development project code names of specific releases, is                     available at:  G                    o  http://www.openvms.compaq.com/openvms/os/openvms- *                       release-history.html  H                    Additional historical information-as well as picturesH                    and a variety of other trivia-is available in the VAX)                    20th anniversary book:n  L                    o  http://www.openvms.compaq.com/openvms/20th/vmsbook.pdf  J                    For information on the FreeVMS project, and on hobbyistC                    and educational versions of OpenVMS, please see:e  K                    o  http://www.systella.fr/~bertrand/FreeVMS/indexGB.html   :                    o  http://en.wikipedia.org/wiki/FreeVMS  5                    o  http://www.openvmshobbyist.org/r                      2-2               &                    General Information        0                    o  http://www.openvmsedu.com/  H                    Also please see the related software licensing topicsF                    Section 2.8.4, Section 2.8.1, and Section 2.15, andI                    (for developers working on commercial applications for *                    OpenVMS) Section 2.8.3.  D           __________________________________________________________>           2.2  What is the difference between VMS and OpenVMS?  G                    VMS and OpenVMS are two names for the same operatingiF                    system. Originally, the operating system was calledF                    VAX-11/VMS; it changed to VAX/VMS at around VAX/VMSH                    V2.0. When the VMS operating system was ported to theG                    Alpha platform, it was renamed OpenVMS, for both VAX G                    and Alpha (and for the Itanium Processor Family), inuJ                    part to signify the high degree of support for industryH                    standards such as POSIX, which provides many features#                    of UNIX systems.   D                    For those versions with POSIX, an OpenVMS licenseE                    allows you to install and run POSIX for OpenVMS atlF                    no additional charge; all you need is the media andG                    documentation which can be found on the ConsolidatedoJ                    Distribution and On-Line Documentation CD-ROMs. SupportH                    for the POSIX package on more recent OpenVMS releasesI                    is not available, various parts of POSIX such as callsfG                    from the API are being integrated more directly into E                    OpenVMS. For more information on POSIX for VMS see !                    question SOFT2   E                    What became confusing is that the OpenVMS name wasiD                    introduced first for OpenVMS AXP V1.0 causing theF                    widespread misimpression that OpenVMS was for AlphaF                    AXP only, while "regular VMS" was for VAX. In fact,D                    the official name of the VAX operating system wasJ                    changed as of V5.5, though the name did not start to be;                    actually used in the product until V6.0.             J                                                                        2-3 _  _          &                    General Information      D           __________________________________________________________:           2.3  What's in a Name? Terminology and Products?  H                    The proper names for OpenVMS on the various platformsI                    are "OpenVMS VAX", "OpenVMS Alpha", and "OpenVMS I64".oH                    Use of "OpenVMS AXP" and of "VAX/VMS" are deprecated.  F                    The VAX and Alpha terms are largely interchangeablyB                    used as the names of platforms, of processor orH                    microprocessor implementations, and of the respective+                    computing architectures./  G                    Somewhat confusing to long-time OpenVMS users, IntelAJ                    IA-32, IA-64, and EM64T, and AMD AMD64 are the names ofG                    various computing architectures and of architecturalnC                    extensions. Only. These are not the names of any 9                    implementations, nor of any platforms.n  J                    Intel Itanium is the name of a family of microprocessorF                    implementations of the Intel IA-64 architecture, asF                    Intel Pentium and Xeon are the names of families ofD                    microprocessor implementations of Intel IA-32 and9                    (potentially) of the EM64T extensions.   G                    I64 is the generic name for the various HP Integrity J                    platforms supported by HP OpenVMS for Integrity ServersJ                    (and more commonly as "OpenVMS I64"); for the platformsD                    supported by OpenVMS I64. (For additional related;                    terminology, please see Section 14.4.5.)_  '           _____________________________ 3           2.3.1  How do I port from VMS to OpenVMS?h  @                    You already did. Wasn't that easy? Please see+                    Section 2.2 for details.   D           __________________________________________________________0           2.4  Which is better, OpenVMS or UNIX?  H                    This question comes up periodically, usually asked byI                    new subscribers and new posters who are long-time UNIXeE                    or Linux users. Sometimes, the question is ignored E                    totally; other times, it leads to a long series ofnG                    repetitive messages that convince no one and usuallyuJ                    carry little if any new information. Please do everyoneJ                    a favor and avoid re-starting this perpetual, fruitless                    debate.                      2-4 h             &                    General Information        G                    That said, OpenVMS and the better implementations ofpE                    UNIX are all fine operating systems, each with its D                    strengths and weaknesses. If you're in a positionE                    where you need to choose, select the one that best H                    fits your own requirements, considering, for example,E                    whether or not the layered products or specific OS G                    features you want are available, and considering theiF                    expected cost-of-ownership over the lifetime of the'                    system installation.e  D                    If you are asking this question, you are probablyC                    comparing OpenVMS to UNIX. It was once certainly C                    true that OpenVMS and UNIX were quite different.mF                    In more recent times, there are tools and C APIs onG                    OpenVMS that directly provide or that easily supportnD                    porting UNIX programs and commands, and there areH                    equivalent packages bringing various OpenVMS features4                    and mechanisms to UNIX platforms.  D                    If you seek UNIX tools on OpenVMS rather than theG                    more philosophical discussion found in this section,sG                    please see the GNV package and other GNU discussions D                    in Section 13.2.6, and please see the plethora ofC                    C calls currently available in the HP C Run-TimeFC                    Library documentation, briefly discussed over inv"                    Section 13.2.1.  D           __________________________________________________________@           2.5  Is HP continuing funding and support for OpenVMS?                      Yes.   J                    Active development of new OpenVMS releases is underway,:                    as well as the continuation of support.  G                    Please see the following URLs for details, roadmaps,n+                    and related information:p  3                    o  http://www.hp.com/go/openvms/p          J                                                                        2-5 s  d          &                    General Information      D           __________________________________________________________<           2.6  What OpenVMS distribution kits are available?  7                    Various distributions are available.   I                    For the most current information on the available part E                    numbers and current products (OpenVMS distribution H                    kits, media, documentation, etc) and the most currentC                    associated licensing information, please see the E                    current OpenVMS Software Product Description (SPD) *                    document, available at:  9                    o  http://h18000.www1.hp.com/info/spd/a  H                       OpenVMS typically uses SPD 25.01.xx, SPD 41.87.xx,'                       and SPD 82.35.xx.   C                    The CD-ROMs listed in Table 2-1 contain just the G                    OpenVMS Alpha operating system. The operating system I                    distribution kits are bootable, and can be used to run J                    BACKUP from the optical media, as well as performing an+                    installation or upgrade.   J           ________________________________________________________________-           Table 2-1  OpenVMS Alpha Media Kits_  J                    _______________________________________________________J                    Part______________Description__________________________  D                    QA-MT1AG-H8       OpenVMS Alpha V6.2-1H3 hardwareF                                      release CD-ROM; also requires QA-1                                      MT1AA-H8.6.2j  E                    QA-MT1AR-H8       OpenVMS Alpha V7.1-2 maintenance 3                                      release CD-ROMb  E                    QA-MT1AT-H8       OpenVMS Alpha V7.2-1 maintenancea3                                      release CD-ROM   E                    QA-MT1AU-H8       OpenVMS Alpha V7.2-2 maintenance_3                                      release CD-ROMs  G                    QA-MT3AA-H8       OpenVMS Alpha and VAX products and_<                                      documentation on CD-ROM  H                    QA-MT3AE-H8       OpenVMS Alpha and VAX documentationJ           ___________________________on_CD-ROM____________________________  F                    OpenVMS I64 is distributed on DVD-ROM media, and isF                    bootable. OpenVMS I64 licensing is implemented on aG                    per-processor-socket basis, with the classic license                       2-6               &                    General Information        G                    tiers based on the numbers of processor sockets that E                    can be present. Further, three general product and D                    licensing groupings are optionally available withD                    OpenVMS I64, the Foundation Operating EnvironmentI                    (FOE), the Enterprise Operating Environment (EOE), andFH                    (as/when/if available) the Mission Critical OperatingH                    Environment (MCOE). Seperate per-product licenses areG                    generally also available for various of the products ;                    within the Operating Environment groups.   J           ________________________________________________________________.           Table 2-2  OpenVMS I64 Order Numbers  J                    _______________________________________________________J                    Part______________Description__________________________  <                    BA322AA#???       OpenVMS I64 FOE Product  <                    BA323AA#???       OpenVMS I64 EOE Product  J           _________BA324AA#???_______OpenVMS_I64_MCOE_Product_____________  D                    The product suffix required for the order numbersA                    listed in Table 2-2 can be found in Table 2-3.   J           ________________________________________________________________-           Table 2-3  OpenVMS I64 Media Suffix   J                    _______________________________________________________J                    Suffix____________Description__________________________  C                    A18               OpenVMS I64 FOE V8.2 DVD media   >                    AJR               OE media kit on DVD media  J           _________0D1_______________Factory_installation_________________  H                    The OpenVMS VAX, OpenVMS Alpha and OpenVMS I64 sourceD                    listings sets referenced in Table 2-4 include theI                    source listings of most of OpenVMS, and these machine- F                    readable distributions are invaluable for any folksJ                    working directly with OpenVMS internals, as well as forI                    folks interested in seeing examples of various OpenVMS *                    programming interfaces.  J                                                                        2-7 o             &                    General Information        J           ________________________________________________________________1           Table 2-4  OpenVMS Source Listings Kitso  J                    _______________________________________________________J                    Part______________Description__________________________  J                    QB-MT1AB-E8       OpenVMS Alpha Source Listings kit and,                                      license  J                    QT-MT1AB-Q8       OpenVMS Alpha Source Listings Updates  H                    BA422AA           OpenVMS I64 Source Listings kit and,                                      license  H                    QB-001AB-E8       OpenVMS VAX Source Listings kit and,                                      license  H                    QT-001AB-Q8       OpenVMS VAX Source Listings Updates  H                    BA422AA           OpenVMS I64 source listings kit andJ           ___________________________license______________________________  I                    Additional OpenVMS packages and technologies includingtD                    NetBeans, XML, SOAP, UDDI, JDK, Perl, Tomcat, SSLG                    and such are discussed within the OpenVMS e-BusinessiI                    Infrastructure Package SPD 80.58.xx. Again, please seeoI                    the OpenVMS SPD and the documents and parts referencedo:                    there for the most current information.  =                    For information on non-commercial softwareeF                    distributions for use by and for OpenVMS Hobbyists,,                    please see Section 2.8.1.  '           ______________________________G           2.6.1  Where can I download OpenVMS and Layered Product Kits?   D                    HP customers with commercial licenses and supportG                    contracts can download software product distribution 6                    kits from the following HP website:  *                    o  http://www1.sqp.com/  E                    You can also find pointers to the Software RolloutrG                    Report and to the OpenVMS SPD listings via the aboves                    SQP website.                       2-8 t  l          &                    General Information        D                    Information on obtaining and transfering licensesG                    is available in Section 2.6 and Section 2.8.4, while H                    information on the OpenVMS Hobbyist licensing programI                    and on obtaining hobbyist product distribution kits is $                    in Section 2.8.1.  D           __________________________________________________________3           2.7  In what language is OpenVMS written?o  E                    OpenVMS is written in a wide variety of languages.s  A                    In no particular order, OpenVMS components areeH                    implemented using Bliss, Macro, Ada, PLI, VAX and DECG                    C, Fortran, UIL, VAX and Alpha SDL, Pascal, MDL, DECpI                    C++, DCL, Message, and Document. And this is certainlyrF                    not a complete list. However, the rumor is NOT trueI                    that an attempt was made to write pieces of OpenVMS inrJ                    every supported language so that the Run-Time LibrariesI                    could not be unbundled. (APL, BASIC, COBOL and RPG area?                    just some of the languages NOT represented!)u  F                    There are a large variety of small and not-so-smallI                    tools and DCL command procedures that are used as partvI                    of the OpenVMS build, and a source code control systemiH                    capable of maintaining over a hundred thousand sourceG                    files across multiple parallel development projects,f,                    and overlapping releases.  D           __________________________________________________________:           2.8  Obtaining and Transfering OpenVMS licenses?  ?                    The following sections describe hobbyist and J                    educational license programs, as well as information on5                    commercial licenses and transfers.a  F                    For information on the available commercial OpenVMSE                    licenses and for information on license transfers, F                    please see Section 2.8.4. OpenVMS Hobbyist licensesB                    are discussed in Section 2.8.1. For informationC                    on the licensing implementation, troubleshooting G                    licensing problems, on the License Unit Requirements F                    Table (LURT), and other related details, please seeI                    Section 5.39. For configuring and troubleshooting LMF,s$                    see Section 12.4.  J                                                                        2-9               &                    General Information      '           _____________________________t?           2.8.1  Questions asked by Hobbyist OpenVMS licensees?   E                    If you are a member of an HP-recognized user groupoG                    (eg: Encompass, Enterex, DECUS), and are consideringtJ                    acquiring and using a VAX, Alpha or (soon) IA-64 systemD                    for hobbyist (non-commercial) use, (free) licenseE                    product authorization keys (PAKs) for OpenVMS VAX,uC                    OpenVMS Alpha, and (reportedly) OpenVMS I64, and 2                    layered products are available.  C                    In addition to the license keys, OpenVMS VAX andsB                    Alpha distribution CD-ROM distribution kits areC                    available with OpenVMS, DECwindows Motif, DECnetfB                    and TCP/IP networking, compilers, and a varietyD                    of layered products. (A hobbyist distribution forD                    OpenVMS I64 is expected.) (While the hobbyist CD-F                    ROM distributions are intended for and tailored forJ                    OpenVMS Hobbyists, the contents and capabilities of theI                    Hobbyist installation kits included within the OpenVMSeH                    Hobbyist distribution do not differ from the standardJ                    distribution installation kits. The products are chosenE                    to reflect the most popular products and the spacee+                    available on the media.)   J                    If you have questions on what else is authorized by theI                    license agreement and on what other distribution mediarH                    is available to you, well, please read the applicable1                    software license agreement(s).o  ;                    For further information, please link to:g  5                    o  http://www.openvmshobbyist.org/   D                    On the OpenVMS Hobbyist license registration formD                    at the above website (as of August 2005), you areJ                    offered the choice of the "OpenVMS VAX" license(s), theI                    "OpenVMS Alpha" license(s), and the "Layered Products" G                    licenses. You will want the operating system licensesD                    for your particular OpenVMS platform and you willF                    want the "Layered Products" licenses. You will wantE                    to select and to acquire two sets of license PAKs.   G                    For vendors wishing to license products specifically E                    for hobbyist use (and to not issue hobbyist PAKs), F                    the program provides hobbyists with the license PAK$                    OPENVMS-HOBBYIST.                      2-10e o  n          &                    General Information        B                    If you plan to use a hardware emulator (eg: VAXG                    emulator) on a Microsoft Windows platform, make sure C                    you have an OpenVMS distribution kit that can beiG                    installed and/or booted with the particular emulator I                    package you plan to use. For additional information oneG                    emulators, please see Section 13.12 and particularlyhA                    please see the emulator-related documentation.   '           _____________________________ 5           2.8.1.1  Vendors offering Hobbyist Licensese  )                    o  GrayMatter Softwaree=                       http://www.graysoft.com/GSCHobbyPR.htmls=                       http://www.graysoft.com/GSCHobbyPR.htmlo  %                    o  Argent Softwarer@                       http://jams.argent-software.com/hobby.html                      o  Kednos,                       http://www.kednos.com/                      o  LJKe$                       http://ljk.com  &                    o  Process SoftwareB                       http://www.process.com/openvms/hobbyist.html                      o  Raxco 4                       http://www.raxco.com/hobbyist/  <                    o  Software Resources International (SRI)E                       http://www.softresint.com/charon-vax/Tools_and_A                       tips.htm  F                    Hobbyist license product additions, and any updatesG                    for products already listed here are welcome. PleaseoE                    contact the FAQ Editor (hoff{atsign}hp{period}com)m  '           _____________________________f7           2.8.2  OpenVMS Educational and CSLG licenses?t  F                    For information on OpenVMS licenses for educational?                    customers, please see the HP Campus SoftwarerG                    License Grant (CSLG) license program and the OpenVMSa/                    Educational license program:   0                    o  http://www.openvmsedu.com/  J                                                                       2-11               &                    General Information      '           _____________________________sB           2.8.3  What developer and partner licensing programs are                  available?   F                    Commercial software developers can join the HP DSPPC                    program, and can (potentially) receive discountssD                    on various software product licenses and softwareC                    distributions, as well as on hardware purchases.e  0                    o  http://www.hp.com/go/dspp/  I                    The DSPP program is the descendent of the DIGITAL ISVN H                    and DIGITAL ASAP programs and the Compaq CSA program,J                    and the analogous developer and partner programs at HP.  D                    One of the benefits available is a (free) licenseC                    product authorization key (PAK) that enables thefF                    generation of license PAKs-the so-called PAKGEN PAKI                    generator license PAK. An example of this is available_F                    on the OpenVMS Freeware V8.0 distribution. (And no,H                    you can't use the Freeware PAKGEN PAK to generate any/                    license PAK you might want.)a  I                    Please see Section 2.8.3 for additional details on the                      DSPP program.  ?                    For information on the OpenbVMS Hobbyist andbC                    OpenVMS Educational license programs, please sees!                    Section 2.8.1.n  '           _____________________________b@           2.8.4  How do I obtain or transfer an OpenVMS license?  J                    To transfer a commercial OpenVMS license from one ownerG                    to another, or to purchase a commercial license, youoG                    can contact HP at regional sales office or reseller.l  J                    For information on the hobbyist license program, please%                    see Section 2.8.1.a  D           __________________________________________________________=           2.9  Does OpenVMS support the Euro currency symbol?   H                    OpenVMS can generate the %xA4 character code used forG                    the Euro, and the DECwindows DECterm can display thetJ                    glyph. Please check with the vendor of your terminal or<                    terminal emulator for additional details.                      2-121               &                    General Information      D           __________________________________________________________F           2.10  OpenVMS Ports? Itanium? Ports to IA-32, EM64T or AMD64                 systems?  H                    OpenVMS has been ported to and is operational on fourI                    architectures: VAX, Alpha, IA-64, and IA-32. The first D                    three have available native ports of OpenVMS, theG                    fourth is available via emulation. VAX is the oldest E                    architecture, and limited to 32-bit virtual and up E                    to 34-bit physical addressing. The Alpha and IA-64 D                    architectures are both 64-bit architectures, withE                    64-bit virtual addressing available. The available F                    IA-32 emulation is provided for the OpenVMS VAX andE                    other VAX operating systems, and provides a 32-bitaE                    VAX environment. For additional information on thee7                    emulation, please see Section 13.12.   H                    As for (the lack of) a native port for IA-32, OpenVMSF                    Engineering presently and continues to believe thatD                    there would be insufficient market (read: profit,E                    customer interest) to justify the cost involved inpF                    a native port of OpenVMS to systems using the IntelF                    IA-32 architecture. In addition to the direct costsJ                    involved in any port and in addition to the substantialD                    effort involved in moving backwards from a 64-bitI                    environment on Alpha and on IA-64 to a 32-bit platformrJ                    (such as IA-32), and the exceedingly non-trivial deviceH                    qualification costs and the costs in moving backwardsE                    into older PCI and I/O environments (IA-32 systemsdG                    more than a few years old have equivalently aged I/O:H                    support and buses), each organization and each personF                    maintaining a product or a package for OpenVMS willF                    have to justify a port to "OpenVMS IA-32", "OpenVMSG                    EM64T" or "OpenVMS AMD64", akin to the decisions andiH                    the effort involved in porting a product from OpenVMSD                    VAX to OpenVMS Alpha, or the port to OpenVMS I64.  E                    Platform ports of many of the various products can G                    be easy, and many of the ports of applications usingaF                    documented OpenVMS features are expected to requireH                    little more than a source rebuild. Other products canE                    and do depend on platform-specific or undocumented A                    features, and the associated ports can be more G                    involved. Regardless, ports of operating systems are:E                    very large and involved projects. The prerequisite   J                                                                       2-13               &                    General Information        G                    product requirements for an OpenVMS operating system B                    port are also non-trivial, as well-compilers inF                    particular are obviously required, and the suite ofI                    compilers provided must maintain a very high degree of J                    source-level compatibility across the platforms. In theG                    case of the HP Integrity port, OpenVMS I64 V8.0 useduG                    cross-compilers and cross-tools operating on OpenVMSiJ                    Alpha systems, while V8.2 and later have various native'                    compilers available."  E                    The OpenVMS I64 port was centrally built using theeI                    existing OpenVMS Alpha environment and around the work E                    and the knowledge from the OpenVMS Alpha port, and G                    OpenVMS Engineering fully expects that customers and G                    ISVs will use and will continue to use OpenVMS Alpha,I                    systems to assist with their own ports to OpenVMS I64. E                    OpenVMS Engineering fully expects to see customers J                    using mixed-architecture clusters and fully shared file$                    systems, as well.  E                    OpenVMS Engineering is well aware of the AMD AMD64sI                    (64-bit) platform and processors. (At least one of theaG                    available VAX emulators can reportedly utilize partscG                    of the AMD64 instruction set, please contact the VAXSE                    emulator vendor(s) or maintainer(s) for assistance F                    and details on their products.) OpenVMS EngineeringE                    is also well aware of the Intel EM64T platform and J                    processors. There are no plans to provide a native portG                    of HP OpenVMS for any systems based on the AMD AMD64 1                    nor Intel EM64T architectures.   J                    As part of the work leading to the Itanium port, seniorG                    engineers had extensively evaluated the products and I                    the architectures available across the high-end 64-bitSJ                    computing space, and chose to target Itanium for 64-bitI                    environments-this while under the Compaq organization.iH                    This included looking at IA-32. HP (a co-developer ofF                    Itanium with Intel) had seperately chosen to targetD                    Intel Itanium for its high-end computer products.F                    Compaq then announced plans for the future of AlphaD                    through EV7-series products and platforms, and HPD                    (entirely seperately) announced plans for PA-RISCF                    products and platforms. The Itanium target has beenE                    maintained consistently since the Itanium port wasn                      2-14g y  r          &                    General Information        F                    announced by Compaq, and has also been consistentlyJ                    maintained by HP and by the combined company. For thoseJ                    folks prefering to follow the schedules and the productG                    deliveries, OpenVMS Engineering had OpenVMS I64 V8.06E                    ready (internally) ahead of schedule-and with moreoF                    features available within the release than had beenG                    originally planned for the release. (For informationeC                    on and for schedules of future OpenVMS releases,rJ                    please see the roadmap that is available at the OpenVMS                    website.)  H                    OpenVMS I64 itself does not require and does not planF                    to utilize the Itanium IA-32 32-bit environment forH                    the operation of OpenVMS itself. OpenVMS I64 V8.0 andF                    later run natively on the Itanium processor family,C                    with no use of IA-32 instructions. While OpenVMS C                    can and does support 32-bit OpenVMS applications E                    and addressing on Itanium, this is done with sign-lH                    extension addressing techniques entirely analogous toF                    what was done with 32-bit applications operating inH                    the 64-bit Alpha environment. Both OpenVMS 32-bit andH                    64-bit applications operate within the native ItaniumG                    instruction set and run-time environment, and do notl5                    use the Itanium IA-32 environment..  H                    But yes, a native IA-32 port or a native AMD AMD64 orF                    Intel EM64T port of OpenVMS would certainly be niceE                    to have-this, of course, following the traditionalGI                    Linux preference for having a Linux port available for/E                    most (all?) computer architectures known, and evenoC                    for certain high-end refrigerators and toasters,1D                    and similar appliance-like devices. (The downsideC                    of this all-encompassing approach: this requires C                    near-infinite engineering and support costs from F                    the various vendors involved, and the qualificationF                    efforts and costs of most everything-everywhere. OrH                    reduced or eliminated testing and support efforts. OrG                    an unfortunate combination of these two. These costs G                    are huge, and the benefits derived from the work are F                    comparatively small when given the comparable costsH                    of more targeted (and thus supported and supportable)G                    hardware configurations-the platform targets are and D                    must be carefully selected and considered by eachI                    vendor. Put another way, there are no plans to provideS  J                                                                       2-15 r  e          &                    General Information        I                    a native port of HP OpenVMS for systems based on Intel G                    IA-32 processors, nor for systems based on AMD AMD64t@                    nor Intel EM64T architectures and processors.  B                    All this material having been written, have youE                    looked at the system configurations and pricing ofrI                    the available HP Integrity Intel Itanium systems? Low-eH                    end computer hardware is clearly a commodity product,F                    and the systems are priced, serviced, upgraded, andE                    replaced accordingly. Intel Itanium is a commodity G                    microprocessor presently used in platforms available G                    from various hardware vendors, including (obviously) J                    from HP. Further, Itanium is a microprocessor availableF                    from and supported by Intel, a semiconductor vendorC                    known for exceedingly high-volume microprocessor C                    fabrication process and production capabilities.3  I                    For information on supported platforms and processors,_F                    please see the OpenVMS Software Product Description                    (SPD) at:  9                    o  http://h18000.www1.hp.com/info/spd/n  H                       OpenVMS typically uses SPD 25.01.xx, SPD 41.87.xx,'                       and SPD 82.35.xx.   >                    Please see Section 14.4.5 for Intel Itanium                    terminology.a  D           __________________________________________________________A           2.11  Are there any network-accessible OpenVMS systems?m  E                    Yes, though various restrictions can and do apply.e                      o  HobbesB                       Hobbes is a MicroVAX 3100 Model 40 for whichG                       free access and accounts are available to OpenVMS J                       enthusiasts. This system has BASIC, Pascal, Fortran,E                       and C compilers installed. If you would like an >                       account on Hobbes, please see the FAQ at  4                      o  http://www.hobbesthevax.com/  /                    o  OpenVMS Galaxy Test-DriveAF                       HP currently offers an OpenVMS Galaxy Test-DriveA                       system, based on an AlphaServer 4100 seriesi                      2-16                &                    General Information        J                       configured as two instances of the OpenVMS operating8                       system. For details, please visit:  4                      o  http://www.testdrive.hp.com/  (                    o  HP DSPP Test-DriveC                       The HP DSPP program offers various test-drive @                       systems, including an HP Integrity Itanium>                       development system and an HP OpenVMS I64H                       installation on an HP Integrity rx2600 server. ForG                       details on the DSPP program and on the test-drive_J                       systems, please see section Section 2.8.3 and please                       visit:  4                      o  http://www.testdrive.hp.com/  /                      o  http://www.hp.com/dspp/a  E                       The test-drive systems do require registration,.;                       though access to the systems is free.l  #                    o  EncompasserveiG                       Encompasserve offers free access an OpenVMS Alphas                       system.y  2                      o  telnet://eisner.decus.org/                      o  OpenECSdH                       OpenECS offers free access to a VAX 6000 model 530:                       system. If interested, please visit:  1                      o  http://vax6k.openecs.org/d  *                    o  The Deathrow ClusterJ                       The maintainers of the Deathrow Cluster offer accessD                       to an OpenVMS VAX and an OpenVMS Alpha system,.                       configured in a cluster.  5                      o  telnet://deathrow.vistech.neti  ;                    o  The Preatorian Public OpenVMS ClusteroJ                       The maintainers of the Deathrow Cluster offer accessE                       to an OpenVMS Alpha cluster. Details are at theo+                       website listed below:   1                      o  http://www.preatorian.net   J                                                                       2-17 i  O          &                    General Information      D           __________________________________________________________2           2.12  What version of OpenVMS do I need?  E                    For information on supported platforms, please seerI                    the OpenVMS Software Product Description (SPD) for the :                    particular OpenVMS version of interest.  9                    o  http://h18000.www1.hp.com/info/spd/m  H                       OpenVMS typically uses SPD 25.01.xx, SPD 41.87.xx,'                       and SPD 82.35.xx.c  I                    For a table of the minimum and (as applicable) maximum J                    OpenVMS versions required for various platforms, pleaseG                    see the hardware support chart at HP OpenVMS websitehJ                    and (as available) the following (potentially volatile;'                    intra-website) link:.  ;                    o  http://h71000.www7.hp.com/openvms/hw__'                       supportchart.htmlu  ?                    For information on the Multia, related Alpha >                    single-board computers, or other officiallyE                    unsupported systems, please see Section 14.4.1 and $                    Section 14.4.2.1.  F                    The following is a rule-of-thumb for Alpha platformE                    support. The table Table 2-5 contains the earliest F                    OpenVMS Alpha release with support for a particular3                    series of Alpha microprocessors:I  J           ________________________________________________________________8           Table 2-5  OpenVMS Alpha Version Rule-Of-Thumb  J                    _______________________________________________________4                                MicroprocessorOpenVMSJ                    Generic_____Generation____Version_____General_Comments_  E                    EV4         21064         V1.0        few systems;hI                                                          most EV4 require G                                                          later; upgrade B                                                          available  C                    EV5         21164         V6.2        subsequentpJ                                                          upgrade available                      2-18                &                    General Information      J           ________________________________________________________________@           Table 2-5 (Cont.)  OpenVMS Alpha Version Rule-Of-Thumb  J                    _______________________________________________________4                                MicroprocessorOpenVMSJ                    Generic_____Generation____Version_____General_Comments_  C                    EV56        21164A        V6.2-1H3    subsequent_H                                                          upgrade to V7.1B                                                          and later  C                    EV6         21264         V7.1-2      subsequent J                                                          upgrade typicallyE                                                          to V7.2-1 orO>                                                          later  C                    EV67        21264A        V7.1-2      subsequentAJ                                                          upgrade typicallyE                                                          to V7.2-1 ora>                                                          later  K                    EV68        21264B, C     V7.2-1      believed/probable; E                                and D                     currently an D                                                          unconfirmedJ           _______________________________________________expectation______  ?                    Specific hardware present and various system J                    configurations can require OpenVMS Alpha releases later6                    than those referenced in Table 2-5.  D           __________________________________________________________2           2.13  How can I submit OpenVMS Freeware?  G                    For the guidelines and submission info, please visit                     the URL:a  <                    o  http://www.hp.com/go/openvms/freeware/  C                    To order the current OpenVMS Freeware CD-ROM kiteH                    (shipping and handling charges apply), please request+                    part number QA-6KZAA-H8.w        J                                                                       2-19 .  p          &                    General Information      D           __________________________________________________________0           2.14  Porting applications to OpenVMS?  G                    Porting can range from simple to rather complex, and I                    depends on the features used on the original platform._  I                    This section covers generic porting, and porting among_G                    OpenVMS VAX OpenVMS Alpha, and OpenVMS I64. (Porting?C                    among OpenVMS VAX, OpenVMS Alpha and OpenVMS I64 F                    is often quite simple and involves little more thanJ                    rebuilding from source, though a few applications usingI                    features specific to the platform or the architecture,oJ                    or using undocumented or unsupported interfaces can andG                    likely will require some additional effort to port.)   I                    Several manuals on porting from OpenVMS VAX to OpenVMS H                    Alpha are available in the OpenVMS documentation set,I                    including information on porting VAX Macro32 assembler D                    code to the Macro32 compiler on OpenVMS Alpha, onH                    management differences, on upgrading privileged code,-                    and application migration:n  7                    o  http://www.hp.com/go/openvms/doc/r  H                    Documentation on porting to OpenVMS I64 is available,                    as well.   I                    Details on the C programming environment are available                     at:  C                    o  http://www.openvms.compaq.com/commercial/c/c_s                        index.html  I                    Details on porting VAX C to HP C are are available at:   G                    o  http://www.openvms.compaq.com/commercial/c/index_                        vax.htmI  >                    An OpenVMS Porting Library is available at:  M                    o  http://www.openvms.compaq.com/ebusiness/Technology.html   H                    Information on the Enterprise Toolkit, a Visual-basedJ                    development environment for developing applications forG                    OpenVMS using a Microsoft platform, is available at:t  E                    o  http://www.openvms.compaq.com/commercial/et/et_Q                        index.html                      2-20                &                    General Information        C                    Details on DCE, CORBA, BridgeWorks, and COM/DCOM .                    middleware is available at:  N                    o  http://www.openvms.compaq.com/commercial/middleware.html  D                    Information on the COE standards is available at:  1                    o  http://diicoe.disa.mil/coe/   F                    A wide variety of programming development tools andG                    middleware are available as commercial products (eg:nC                    DECset, IBM WebSphere MQ-formerly MQseries), andSF                    various tools are also available as shareware or asG                    Freeware. Please see other sections of this FAQ, ands                    please see:  7                    o  http://www.hp.com/go/dspp_catalog   D           __________________________________________________________@           2.15  What resources are available to OpenVMS software                 developers?o  G                    The HP Developer and Software Product Partner (DSPP) D                    program is open to and intended to support and toH                    assist HP OpenVMS software partners, consultants, and%                    service providers:   -                    o  http://www.hp.com/dspp/p  J                    DSPP provides members with various benefits, please see+                    the website for details.   G                    For those not familiar with the DSPP program or with G                    its history, the DIGITAL Association of Software and F                    Application Partners (ASAP) program and the DIGITALF                    Independent Software Vendors Network (ISVN) programI                    were incorporated into the Compaq CSA program, and theiJ                    CSA program has subsequently been incorporated into the#                    HP DSPP program.p  I                    Please see Section 2.8.3 for additional details on thes                     DSPP program.    J                                                                       2-21               &                    General Information      D           __________________________________________________________?           2.16  memory management, resource management, process                   scheduling, etc?  I                    So you have been instructed to write a school researchAC                    paper on OpenVMS, and you need technical contentaF                    on the OpenVMS Virtual Memory System, on any memoryG                    segmentation, on OpenVMS Resource Management, on themF                    OpenVMS File System, on the OpenVMS user interface,                    etc.h  E                    Invariably, your professor/instructor/teacher willSD                    ask you a series of questions. Most commonly, theH                    questions will request descriptions of one or more ofH                    the following items, and at varying levels of detail:  5                    o  process scheduling algorithm(s)u  0                    o  Interprocess comunications  B                    o  Process or system synchronization constructs  =                    o  Memory management and/or virtual memory $                       implementation  0                    o  RMS or XQP file structures  )                    o  Resource managementt  +                    o  History of HP OpenVMS   C                    o  History of Compaq and/or of Digital Equipment '                       Corporation (DEC)   E                    Any particular presentation or research paper, andeC                    particularly a scholastic presentation, can havelF                    many different potential target audiences, and veryD                    different presentation levels. Further, the usualE                    underlying reason for scholastic presentations andrG                    scholastic research projects really has little to donE                    with the subject matter, it is a task specificallyeD                    intended to teach the student(s) (eg: you) how toE                    perform the research. The instructor already knowsoG                    most of (all of?) the information that you have been $                    asked to collect.                      2-22                &                    General Information        D                    For very technical details on OpenVMS and OpenVMSI                    internals, the book you want is the Internals and DataeE                    Structures Manual (IDSM), available in your school)H                    or computing center library, and the IDSM can also beG                    purchased. Additional technical details of the Alpha)I                    microprocessor are available in the Alpha ArchitecturefG                    Reference Manual documentation that is available forVG                    download. (Pointers to Alpha technical documentation A                    are available in Section 14.6, and elsewhere.)   I                    For higher-level (less technical) details, the OpenVMS J                    documentation set is available on-line. The ProgrammingH                    Concepts and the File Systems manual are probably theJ                    best manuals to start with, depending on the particular9                    level of detail the research requires.M  H                    And please understand the hesitation of various folksD                    to provide you with a completely-written researchH                    report on your topic. Why? We might have to work withI                    you after you graduate-you need to know how to performdI                    at least basic research on your own, regardless of thet                    topic.p  D           __________________________________________________________+           2.17  Basic Units of Measurement?h  H                    OpenVMS and the underlying hardware use various unitsJ                    of measurement for disk and memory storage, and relatedC                    abbreviations also typically exist. This sectionmC                    covers the most common units, and the associatedo!                    abbreviations.w  '           _____________________________ 5           2.17.1  How many bytes are in a disk block?   C                    A disk block is the minimum unit of disk storage )                    allocation in OpenVMS.p  G                    Under OpenVMS VAX and OpenVMS Alpha, the disk volumeaG                    block size is consistent, with each block containinge                    512 bytes.   C                    The minimum disk allocation granularity actually H                    permissible (in the ODS-2 and ODS-5 volume structuresJ                    commonly used on OpenVMS) is determined on a per-volumeH                    basis, and is typically based on a combination of the  J                                                                       2-23 t  p          &                    General Information        G                    total number blocks on the disk volume and the total D                    size of the volume storage bitmap. The allocationE                    granularity is known as the volume cluster factor-oG                    the cluster factor is the number of blocks in a diskvH                    cluster, and it is the smallest number of blocks that@                    can be allocated on a particular disk volume.  I                    Prior to OpenVMS V7.2, the maximum permissible size ofaG                    the bitmap requires larger cluster factors as volumesH                    sizes increase. Starting with V7.2, the bitmap can beH                    larger, and cluster factors as small as one block can                    be used.r  E                    The number of bytes in a file can be determined bysJ                    multiplying the number of blocks allocated for the fileG                    times the number of bytes in a block. For sequentialsG                    files (only), the FFB (XAB$W_FFB, in the File Header E                    XAB) value can be used to find out how much of the B                    last (XAB$L_EBK) block is used. FFB and EBK areD                    meaningful only for sequential files, and only inF                    a limited context-partial block allocations are notG                    permitted. For other file formats, the EOF marker is "                    not meaningful.  E                    Disk allocations always occur only in units of the E                    cluster factors, which can be from one block up to E                    (potentially) clusters of eighteen blocks or more, H                    depending on the volume cluster factor. (OpenVMS V7.2G                    and later optionally provide for a cluster factor ofnE                    one up to volumes of approximately 137 gigabytes.)   A                    OpenVMS assumes that the device driver and theeI                    underlying storage device will present the file systemaJ                    with addressable units of storage of 512 bytes in size,H                    or the appearance of same. Various third-party CD-ROMH                    devices, for instance, support only 2048 byte blocks,F                    and such devices are incompatible with the standard*                    OpenVMS device drivers.  G                    To determine the number of bytes required for a file G                    from DCL, one option uses the f$file_attributes item I                    EOF, multiplied by the size of a block in bytes (512). I                    This does not account for the unused space in the lastrH                    block of a sequential file, but it also does not haveF                    to differentiate sequential files from other files.                      2-24                &                    General Information      '           _____________________________a6           2.17.2  How many bytes are in a memory page?  I                    A memory page is the minimum unit of memory allocation E                    in OpenVMS. With OpenVMS VAX, the memory page size G                    matches the disk block size: it is always 512 bytes.g  H                    With OpenVMS Alpha, the memory page size is variable,D                    and it can range from 8192 bytes (8 kilobytes) upG                    to 64 kilobytes. The current system page size can be H                    determined using the sys$getsyi or f$getsyi PAGE_SIZEI                    item. Programs with hardcoded constants for the memory G                    page size (or page alignment) should always assume a -                    page size of 64 kilobytes.e  I                    On OpenVMS I64, the memory page size is also variable,_B                    ranging from 4096 bytes (4 kilobytes) up to 256I                    megabytes (MB) and potentially up to 4 gigabytes (GB).mI                    As with OpenVMS Alpha, sys$getsyi and f$getsyi and thenI                    PAGE_SIZE itemcode can and should be used to determineeH                    the current system page size. In general, OpenVMS I64B                    will use a page size of 8 kilobytes, or larger.  G                    On OpenVMS Alpha and on OpenVMS I64, a 512 byte area I                    of memory- equivalent in size to an OpenVMS VAX memoryn;                    page-is often refered to as a "pagelet".   '           _____________________________i@           2.17.3  How do I convert? Disk Blocks? KB, MB, GB, TB?  I                    The smallest granularity of disk storage addressing isaJ                    called a disk block, or sometimes a disk sector. GroupsE                    of disk blocks are usually organized together into_F                    the smallest unit of storage that can be allocated,E                    and this unit is called a disk cluster. The numberVG                    of blocks in a cluster is the cluster factor, and isiC                    established when the disk volume is initialized.   I                    Each individual disk block is composed of five hundred I                    twelve (512) bytes, or one-half kilobyte. Each byte istI                    comprised of eight bits. A bit represents the smallestyJ                    unit of information, typically refered to as a one or a                    zero.    J                                                                       2-25               &                    General Information        C                    OpenVMS tends to uses base two notation for disk3F                    storage, while disk storage capacity specificationsH                    from most storage vendors will generally use base ten                    notation.  F                    An OpenVMS disk block is 512 bytes in size; this is:                    one-half kilobyte in base two notation.  @                    The following table describes the prefix, theH                    abbreviation, and the associated base ten (as used byJ                    marketing and by storage vendors) and base two (OpenVMS?                    and various other operating systems) values.v  ?                     Base Ten                           Base Two P                     --------------------------------   -------------------------P           Kilobyte  (KB)  10**3                 1000   2**10                1024P           Megabyte  (MB)  10**6              1000000   2**20             1048576P           Gigabyte  (GB)  10**9           1000000000   2**30          1073741824P           Terabyte  (TB)  10**12       1000000000000   2**40       1099511627776P           Petabyte  (PB)  10**15    1000000000000000   2**50    1125899906842624P           Exabyte   (EB)  10**18 1000000000000000000   2**60 1152921504606846976  D                    The base ten representation of the 2**40 value isF                    1099511627776, which is obviously rather ugly. WhenC                    viewed as a base eight or base sixteen (octal oreE                    hexadecimal, respectively) value, the value is far6D                    nicer. Specifically, the value is 10000000000 andF                    40000000 when represented in octal and hexadecimal,                     respectively.  5                                          FAQ Notation   E                       Within the OpenVMS FAQ, a thousand bits (either E                       assuming base two or base ten, as determined by E                       the context) is refered to as a kilobit, and is F                       always represented by the appreviation Kb, whileF                       a thousand bytes is refered to as a kilobyte andE                       is always abbreviated as KB. Similar notational F                       usage also holds for Megabits (Mb) and Megabytes<                       (MB), and for the various other units.  D                    OpenVMS operating system references to system andE                    storage are generally to the base-two version (eg: D                    1024, in the case of a kilobyte or kilobit) whileJ                    storage hardware references and hardware specificationsD                    are generally to the base-ten version (eg: 1000).                      2-26o c  i          &                    General Information        I                    To convert OpenVMS disk blocks to (base two) kilobytes E                    (KB; 1024 bytes), simply divide by two. To convertaI                    blocks to (base two) megabytes, divide by 2048. BlocksiC                    to (base two) gigabytes (GB), divide by 2097152.oI                    These particular divisions can also be performed usingyH                    bitshifts: to divide a value by two, shift the binary7                    value rightward by one bit position.t  J                    To convert OpenVMS disk blocks to (base ten) kilobytes,4                    divide by approximately 1.953125.  G                    For those folks with an interest in odd applications F                    for prefixes, and particularly for those folks alsoE                    rummaging around deep within the OpenVMS operatingoH                    system, a microfortnight is approximately one second.                                                          J                                                                       2-27 d  s                    J                    _______________________________________________________              3        Documentation      D           __________________________________________________________A           3.1  Where can I find online copies of OpenVMS manuals?o  I                    The HP OpenVMS and HP Layered Product documentation isI(                    copyrighted material.  E                    HTML format on-line product documentation sets for G                    specific HP OpenVMS products are presently available                     at:  7                    o  http://www.hp.com/go/openvms/doc/   J                    Documentation is offered on separately orderable CD-ROMG                    media through a subscription to the Consolidated On- I                    Line Documentation (ConOLD) product (see Section 2.6.)II                    ConOLD manuals are readable with BNU, a viewer that islH                    supplied with the documentation distribution. BNU canG                    display HTML, Bookreader, and documentation in other7                    formats.s  G                    MGBOOK, a viewer for Bookreader-format documentationIH                    is available for character-cell terminals (eg. VTxxx)F                    via the WKU VMS Freeware file server - see question,                    Section 13.1 for details.  D                    Information on the XPDF DECwindows PDF viewer forF                    OpenVMS is available in Section 13.1, and XPDF kitsF                    are available on various Freeware distributions. AnG                    alternative on OpenVMS Alpha uses the Adobe Java PDF E                    viewer, though this viewer is generally considered E                    to be both slower and more resource-intensive when /                    compared to the XPDF viewer.a            J                                                                        3-1                                    Documentation      D           __________________________________________________________B           3.2  What online information and websites are available?  G                    On your OpenVMS system, the HELP command can providelD                    a wealth of information, not only on DCL commandsD                    but on system services (HELP System_Services) andE                    Run-Time Library routines (HELP RTL_Routines). ThewH                    introduction displayed when you type the HELP commandI                    with no additional keywords provides further pointers.s  9                    OpenVMS Marketing runs a web server ate0                    http://www.hp.com/go/openvms/  D                    Here, you will find product information, strategyJ                    documents, product roadmaps, the contents of the latest4                    OpenVMS Freeware CD-ROM and more.  J           ________________________________________________________________%           Table 3-1  OpenVMS Websitese  J           ________________________________________________________________J           URL_______Sponsor_______________________________________________             HP OpenVMS Marketing  1                     http://www.hp.com/go/openvms/r             Encompass DFWCUG  3                     http://www.openvmshobbyist.org//             Arne Vajhj   0                     http://www.levitte.org/~ava/             Saiga Systemsh  )                     http://www.saiga.com/              Wayne Sewell  -                     http://www.tachysoft.com/              proGIS Software   4                     http://www.progis.de/openvms.htm             Jeff Cameron  0                     http://www.jcameron.com/vms/  B           David Mathog's (quite useful) information about OpenVMS.  <                     http://saf.bio.caltech.edu/soft_doc.html             Cracking                      3-2                                    Documentation      J           ________________________________________________________________-           Table 3-1 (Cont.)  OpenVMS Websitesa  J           ________________________________________________________________J           URL_______Sponsor_______________________________________________             "The Beave"nF           Includes system cracking information that can be of interestI           to OpenVMS System Managers, and to OpenVMS Network and SecuritySJ           Managers. This information is available at the Deathrow cluster.  B                     http://manson.vistech.net/ht_root/Hack-VMS-faq             Undocumented Features              DECUS Deutschland   H                     http://zinser.no-ip.info/www/eng/vms/qaa/undoc.htmlx             Arne Vajhjn  =                     http://www.levitte.org/~ava/vms_tip.htmlx   H           The OpenVMS Freeware contains various examples of undocumented!           features and interfacesi  :                     http://www.hp.com/go/openvms/freeware/  G           Comparisons of UNIX and Linux shell commands and DCL Commands   G                     http://www.mcsr.olemiss.edu/unixhelp/VMStoUNIX.htmle  C                     http://wwwvms.mppmu.mpg.de/vmsdoc/UNIX_VMS_CMD_m                     XREF.HTML   ?           Comparisons of emacs and OpenVMS text editor commands   H                     http://www.unh.edu/cis/docs/vms-to-unix/Emacs/cheat-                     sheet.html             Bibliographies  ?                     http://www.openvms.org/pages.php?page=Bookso  >                     http://www.levitte.org/~ava/vms_book.htmlx             Introductory  I                     Please see Table 3-2 for listings of introductory web 0                     sites and related materials.             Programming   $           An OpenVMS Programming FAQ  @                     http://www.pdv-systeme.de/users/martinv/VMS_(                     Programming_FAQ.html             Networking  J                                                                        3-3 3  x                               Documentation      J           ________________________________________________________________-           Table 3-1 (Cont.)  OpenVMS Websites_  J           ________________________________________________________________J           URL_______Sponsor_______________________________________________  I           Tutorial information and tips for connecting OpenVMS systems to0           the Internet  3                     http://www.tmesis.com/internet/n  F           Documentation and Specifications for DECnet Phase IV, DECnet:           task-to-task DCL examples, and a whole lot more.  8                     http://www.hp.com/go/openvms/wizard/  "           HP OpenVMS Documentation  J                     Please see Table 3-2 for listings of documentation web0                     sites and related materials.             System Performance  %                     See Section 14.2.              Patch (ECO) Kits  B                     For the HP Services FTP server hosting VariousG                     contract-access and non-contract access ECO (patch)e3                     kits, see section Section 5.17.t             Catalogs and Pricing  7           HP Product QuickSpecs and product information   9                     http://www.hp.com/go/productbulletin/h  :           The HP Systems and Options Catalog (SOC) archive  3                     http://www.compaq.com/products/ =                     quickspecs/soc_archives/SOC_Archives.html   (           Hardware and Software Archives  E           The VAXarchive, including hardware and software information   8                     http://vax.sevensages.org/index.html  &           A VAX to Alpha upgrade diary  J                     http://www3.sympatico.ca/n.rieck/docs/alpha_diary.html  =           Scanned versions of old DIGITAL manuals from DFWCUG   >                     http://www.montagar.com/~patj/dec/hcps.htm  E           A wide variety of HP VAX, Alpha, platform and other product ;           documentation. Some introductory, some technical.v  I                     http://www.compaq.com/support/techpubs/qrg/index.html                       3-4 e  e                               Documentation      J           ________________________________________________________________-           Table 3-1 (Cont.)  OpenVMS Websites   J           ________________________________________________________________J           URL_______Sponsor_______________________________________________  %           dtrwiz's Datatrieve website   J           __________http://dtrwiz.home.netcom.com/________________________  D           __________________________________________________________F           3.3  How do I extract the contents of a HELP topic to a text                file?  C                    To extract all the text of a HELP topic (and its D                    subtopics) to a text file for perusal with a textI                    editor, printing out, etc., use the following command:e  E                    $ HELP/OUT=filename.txt help-topic [help-subtopic]   C                    If the help text you want is not in the standardiE                    help library (for example, it's help for a utility_C                    such as MAIL that has its own help library), add C                    /LIBRARY=libname after the HELP verb. To see the A                    names of help library files, do a directory of "                    SYS$HELP:*.HLB.  D           __________________________________________________________=           3.4  Does OpenVMS Marketing have an e-mail address?S  B                    Yes - if you can't get the answers to marketingJ                    questions elsewhere, if you have comments or complaintsJ                    about OpenVMS, send mail to openvms-info{atsign}hp.com.G                    This address is not a support channel, and is solelyhE                    intended to provide informal method to communicatet>                    directly with members of OpenVMS Marketing.  D           __________________________________________________________C           3.5  Where can I learn about OpenVMS executive internals?   B                    The OpenVMS Internals and Data Structure manualC                    (IDSM) explains how the OpenVMS executive works.1G                    The book covers the operating system kernel: processeH                    management; memory management; the I/O subsystem; andE                    the mechanisms that transfer control to, from, andVI                    among these. It gives an overview of a particular areafF                    of the system, followed by descriptions of the dataJ                    structures related to that area and details of the code,                    that implements the area.  J                                                                        3-5 o  c                               Documentation        H                    The first edition of the OpenVMS Alpha internals bookJ                    describes Version 1.5. Although there have been severalE                    releases of OpenVMS Alpha since Version 1.5 (V6.1, J                    V6.2, V7.0, V7.1, etc) and many details in the book areG                    no longer accurate, it continues to provide a strong ?                    conceptual description of OpenVMS internals.   H                    This book has been split into five pieces, each to beG                    updated separately. The first such volume, published_B                    in early 1997, was "OpenVMS Alpha Internals andD                    Data Structures: Scheduling and Process Control,"F                    which covers the Version 7.0 implementation of trueE                    multithreading and the changed scheduling model itc                    implies._  D                    The internals books are available through Digital)                    Press, see Section 3.6   D           __________________________________________________________B           3.6  Where can new users find tutorial information about                OpenVMS?V  H                    First, see if your local site has information on thisG                    topic. Each site can have site-specific features and H                    configuration. Some sites will have site-specific newG                    user's documentation, covering various site-specificbJ                    things that are difficult or impossible for the general2                    OpenVMS documentation to cover.  '           _____________________________ #           3.6.1  Tutorial Websites?   @                    Various websites with OpenVMS information areE                    available; Table 3-2 contains some suggested URLs.   J           ________________________________________________________________@           Table 3-2  OpenVMS Tutorial and Documentation Websites  J                    _______________________________________________________J                    URL_______Sponsor______________________________________                      Introductoryt  <                    http://www.levitte.org/~ava/vms_faq.htmlx  <                    http://saf.bio.caltech.edu/vms_sheet.html                      3-6 ?                                  Documentation      J           ________________________________________________________________H           Table 3-2 (Cont.)  OpenVMS Tutorial and Documentation Websites  J                    _______________________________________________________J                    URL_______Sponsor______________________________________  C                    http://seqaxp.bio.caltech.edu/www/vms_beginners_                     faq.html   ;                              Various introductory materials_  9                    http://www.montagar.com/openvms_class/   E                              Members of the Encompass DFWCUG maintaingE                              a website with many materials available,nA                              including an Overview of OpenVMS, an D                              Introduction to DCL and the TPU Editor,E                              Advanced DCL Command Procedures, OpenVMS ?                              Operations: Batch, Print, Tape, an C                              Introduction to OpenVMS Management, to @                              OpenVMS User Management, to OpenVMSG                              Network Management, and to OpenVMS ClusterhF                              Management. These training materials haveF                              been presented at various DECUS symposia.  F                    http://www.mcsr.olemiss.edu/unixhelp/VMStoUNIX.html  H                              A comparison table of various command-levelJ                              tasks, with information on the UNIX and LinuxE                              shell command(s), and on the OpenVMS DCLO(                              command(s).  +                    HP OpenVMS Documentation,  4                    http://www.hp.com/go/openvms/doc/  H                              Various introductory guides as well as moreJ                              advanced manuals are available in the OpenVMSC                              and layered product documentation set.   &                    HP OpenVMS Training  ;                    http://www.compaq.com/training/home.htmlc?                    http://www.openvms.compaq.com/wbt/index.htmli  I                              HP offers training information and TechnicaltH                              Resource Kits (TRKs) and other Training forH                              OpenVMS. An OpenVMS certification (testing)7                              program is also available.s  /                    http://www.jcameron.com/vms/a  J                                                                        3-7 v  n                               Documentation      J           ________________________________________________________________H           Table 3-2 (Cont.)  OpenVMS Tutorial and Documentation Websites  J                    _______________________________________________________J                    URL_______Sponsor______________________________________  ,                              An OpenVMS Quiz  +                    http://www.CCSScorp.com/   B                              CCSS Interactive Learning has OpenVMS/                              training materialss  +                    http://www.acersoft.com/d  G                              AcerSoft Training information, and Shannonv+                              Knows Punditryw  )                    http://www.mindiq.com/n  8                              MindIQ training information  ,                    http://www.quadratrix.be/  G                              Quadratrix; OpenVMS training, products and G                              services; affiliated with Global Knowledge J           ___________________and_KeyJob___________________________________  '           ______________________________%           3.6.2  Books and Tutorials?a  F                    Some of the OpenVMS books that are now or that haveI                    been available from the Elsevier Digital Press imprint   7                    o  http://www.digitalpressbooks.com/   +                    are listed in Table 3-3:e  J           ________________________________________________________________           Table 3-3  DP Booksp  J           ________________________________________________________________J           Title_and_Author_____________________ISBN_______________________  <           Getting Started with OpenVMS         1-55558-279-6           Michael D. Duffy  <           Getting Started with OpenVMS System  1-55558-243-5!           Management, 2nd EditionL$           David Donald Miller, et al                      3-8 o  m                               Documentation      J           ________________________________________________________________%           Table 3-3 (Cont.)  DP Books   J           ________________________________________________________________J           Title_and_Author_____________________ISBN_______________________  <           Introduction to OpenVMS, 5th         1-55558-194-3           Edition            Lesley Ogilvie Ricea  <           Introduction to OpenVMS              1-878956-61-2           David W Bynon   <           OpenVMS Alpha Internals: Scheduling  1-55558-156-0           and Process Control   <           OpenVMS AXP Internals and Data       1-55558-120-X!           Structures: Version 1.5o  <           OpenVMS System Management Guide      1-55558-143-9           Baldwin, et al  <           The OpenVMS User's Guide, Second     1-55558-203-6           Editiong           Patrick Holmay  <           Using DECwindows Motif for OpenVMS   1-55558-114-5           Margie Sherlock   <           VAX/VMS Internals and Data           1-55558-059-9!           Structures: Version 5.2s  <           Writing Real Programs in DCL,        1-55558-191-9           Second Edition%           Hoffman and Anagnostopoulos   <           Writing OpenVMS Alpha Device         1-55558-133-1           Drivers in CJ           Sherlock_and_Szubowicz__________________________________________  F                    Within the above table, no attempt is made to trackG                    which books are currently in print, or are currently                      out of print.  J                    For various featured OpenVMS books, also please see the5                    books link at the OpenVMS website:p  2                    o  http://www.hp.com/go/openvms  J                                                                        3-9                                    Documentation        F                    For a bibliography of various OpenVMS books, please                    see:   @                    o  http://www.levitte.org/~ava/vms_book.htmlx  D           __________________________________________________________C           3.7  What OpenVMS mailing lists and forums are available?s  I                    Various OpenVMS mailing lists are available, with some G                    of the available lists detailed in Table 3-4, as aree>                    the various discussion forums in Table 3-5.  J           ________________________________________________________________*           Table 3-4  OpenVMS Mailing Lists  J           ________________________________________________________________J           Subscription____________________Interest_Area___________________  >           OpenVMS Freeware archive        FSupdate@goatley.comI           announcement list               FSupdate-request@goatley.com[1]   F           Two-way echo of                 VMSnet-Internals@goatley.com;           vmsnet.internals                VMSnet-Internals- @                                           request@goatley.com[1]  ?           OpenVMS Alpha Internals         Alpha-IDS@goatley.comcJ           discussions                     Alpha-IDS-request@goatley.com[1]  ?           BLISS discussions               BLISSters@goatley.com J                                           BLISSters-request@goatley.com[1]  C           Process Software MultiNet       Info-MultiNet@process.com 8           mailing list (news gateway)     Info-MultiNet-@                                           request@process.com[1]  B           Process Software TCPware        Info-TCPware@process.com7           mailing list (news gateway)     Info-TCPware- @                                           request@process.com[1]  ?           Process Software PMDF mailing   Info-PMDF@process.com J           list (news gateway)             Info-PMDF-request@process.com[1]  F           The Software Resources          CHARON-VAX-Users@process.com;           International (SRI) CHARON-VAX  CHARON-VAX-Users- @           VAX emulator package            request@process.com[1]  J           ________________________________________________________________H           [1]This is the subscription address. Usually, you will want toF           send a mail message with no subject line, and a SUBSCRIBE or7           HELP command in the body of the mail message.r                      3-10                                     Documentation      J           ________________________________________________________________2           Table 3-4 (Cont.)  OpenVMS Mailing Lists  J           ________________________________________________________________J           Subscription____________________Interest_Area___________________  :           Info-Zip's Zip & UnZip          Info-Zip@wku.eduE           discussion list                 Info-Zip-Request@wku.edu[1]   <           RADIUS-VMS, a RADIUS server     radius-vms@dls.netG           for OpenVMS discussion forum    radius-vms-request@dls.net[1]o  :           Internet Service Providers      vms-isps@dls.netE           (ISPs) running OpenVMS          vms-isps-request@dls.net[1]s  A           Users of Mark Daniel's WASD     http://wasd.vsm.com.au/s$           web server for OpenVMS VAX'           and Alpha exists. Information $           about this list server and(           details on how to subscribe to'           the list are available at the            referenced website.o  U           VMS Forum                       http://www.neurophys.wisc.edu/comp/ava/vms_h5                                           forum.htmlxsJ           ________________________________________________________________H           [1]This is the subscription address. Usually, you will want toF           send a mail message with no subject line, and a SUBSCRIBE or7           HELP command in the body of the mail message.MJ           ________________________________________________________________  H                    Various OpenVMS discussion forums are available, withE                    some of the available lists detailed in Table 3-5.u  J           ________________________________________________________________.           Table 3-5  OpenVMS Discussion Forums  J           ________________________________________________________________J           DescriptioForum_Location________________________________________  #           The comp.os.vms newsgroup(  $                     news:comp.os.vms             HP ITRC Forums  W                     http://forums.itrc.hp.com/service/forums/familyhome.do?familyId=288c  6           Hunter Goatley: The HG OpenVMS Message Board  D                     http://www.goatley.com/scripts/vmsboard/view.com  -           Computing.Net: OpenVMS Message Area   J                                                                       3-11    t                               Documentation      J           ________________________________________________________________6           Table 3-5 (Cont.)  OpenVMS Discussion Forums  J           ________________________________________________________________J           DescriptioForum_Location________________________________________  K                     http://www.computing.net/openvms/wwwboard/wwwboard.htmls  2           Tek-Tips: DEC (HP/Compaq): OpenVMS Forum  #                     http://www.tek-eE                     tips.com/gthreadminder.cfm/lev2/3/lev3/19/pid/951h             OpenVMS.Org forums  +                     http://www.openvms.org/e  $           OpenVMSHobbyist.Org forums  3                     http://www.openvmshobbyist.org/   6           Encompasserve (DECUSserve) Notes Conferences  J           __________telnet://www.encompasserve.org/_______________________  D           __________________________________________________________D           3.8  What is this Ask The Wizard website I've heard about?  E                    The HP OpenVMS Ask The Wizard (ATW) website was anFI                    informal area discussing OpenVMS, containing questionsi;                    and answers on a wide variety of topics.   H                    o  http://www.hp.com/go/openvms/wizard/ (retired; use"                       ITRC forums)  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the available_F                    ATW Wizard.zip archive, please see Section 3.8. ATWF                    has been superceded (for new questions) by the ITRCD                    discussion forums; the area remains available for                    reference.s  I                    To access a cited topic directly, use the URL filenamenI                    WIZ_topic-number.HTML, or use the topic search engine. D                    Cited topics are shown in parentheses, and act asG                    unique topic addresses. These should not be confused E                    with the relative topic numbers shown at the site.oI                    For example, the topic (1020) can be accessed directlyeH                    using the URL filename wiz_1020.html, at the web site8                    that the following URL resolves into:  :                    o  http://www.hp.com/go/openvms/wizard/                      3-12o e  u                               Documentation        E                    A zip archive (named wizard.zip) containing all ofpG                    the available topics and questions can be downloadeddD                    from the above URL. The wizard.zip zip archive isH                    completely regenerated when/if existing topics postedE                    out to the ATW website are updated. Copies of thislD                    wizard.zip archive also generally ship out on the-                    OpenVMS Freeware, as well.   I                    New (informal) questions and discussions are now being_H                    directed away from the ATW area to the ITRC area, and>                    specifically to the ITRC discussion forums:  -                    o  http://www.itrc.hp.com/   D           __________________________________________________________F           3.9  Where can I find the latest C run-time library manuals?  G                    The C run-time library (RTL) reference documentation G                    has been moved from the C language documentation set H                    to the OpenVMS documentation set. For the most recentE                    version of the C RTL documentation and the OpenVMS F                    standard C library, please see the OpenVMS manuals.  H                    In addition to the user-mode C RTL, there is a secondI                    kernel-mode RTL accessable to drivers on OpenVMS Alpha J                    and OpenVMS I64. For details on this second library andG                    on the duplicate symbol errors that can be triggered I                    when this library is referenced during an incorrectly- F                    specified LINK command, please see Section 10.22.1.F                    For general information on this kernel RTL, see theJ                    Digital Press book Writing OpenVMS Device Drivers in C.H                    For details, please see the associated OpenVMS source)                    listings distribution.   7                    o  http://www.hp.com/go/openvms/doc/                   J                                                                       3-13 e  s                    J                    _______________________________________________________  '           4        Time and Timekeepingh      C                    This chapter discusses time, timekeeping, system D                    time synchronization, clock skew and clock drift,I                    implications of using SUBMIT/AFTER=TOMORROW, and other '                    time-related topics.   D           __________________________________________________________>           4.1  A brief history of OpenVMS Timekeeping, please?  D                    Why does OpenVMS regards November 17, 1858 as the'                    beginning of time...   F                    The modified Julian date adopted by the SmithsonianI                    Astrophysical Observatory (SAO) for satellite tracking6J                    is Julian Day 2400000.5, which turns out to be midnight(                    on November 17, 1858.  J                    SAO started tracking satellites with an 8K (nonvirtual)G                    36-bit IBM 704 in 1957 when Sputnik went into orbit. I                    The Julian day was 2435839 on January 1, 1957. This is J                    11225377 octal, which was too big to fit into an 18-bitJ                    field. With only 8K of memory, the 14 bits left over byG                    keeping the Julian date in its own 36-bit word wouldSH                    have been wasted. SAO also needed the fraction of theH                    current day (for which 18 bits gave enough accuracy),F                    so it was decided to keep the number of days in theI                    left 18 bits and the fraction of a day in the right 18e$                    bits of one word.  I                    Eighteen bits allows the truncated Julian Day (the SAO G                    day) to grow as large as 262143, which from November H                    17, 1858, allowed for 7 centuries. Possibly, the dateF                    could only grow as large as 131071 (using 17 bits),C                    but this still covers 3 centuries and leaves the F                    possibility of representing negative time. The 1858I                    date preceded the oldest star catalogue in use at SAO,tH                    which also avoided having to use negative time in any:                    of the satellite tracking calculations.  J                                                                        4-1               '                    Time and Timekeepingv        J                    The original Julian Day (JD) is used by astronomers andI                    expressed in days since noon January 1, 4713 B.C. This G                    measure of time was introduced by Joseph Scaliger in H                    the 16th century. It is named in honor of his father,G                    Julius Caesar Scaliger (note that this Julian Day isTG                    different from the Julian calendar that is named for 5                    the Roman Emperor Julius Caesar!).   E                    Why 4713 BC? Scaliger traced three time cycles and F                    found that they were all in the first year of theirH                    cyle in 4713 B.C. The three cycles are 15, 19, and 28J                    years long. By multiplying these three numbers (15 * 19G                    * 28 = 7980), he was able to represent any date from .                    4713 B.C. through 3267 A.D.  J                    The starting year was before any historical event knownG                    to him. In fact, the Jewish calendar marks the start_G                    of the world as 3761 B.C. Today his numbering schemeeI                    is still used by astronomers to avoid the difficulties I                    of converting the months of different calendars in useg)                    during different eras.o  +                    The following web sites:   J                    o  http://www.openvms.compaq.com/openvms/products/year-$                       2000/leap.html  5                    o  http://www.eecis.udel.edu/~ntp/   *                    o  http://www.nist.gov/  ;                    o  http://www.boulder.nist.gov/timefreq/o  A                    o  http://www.tondering.dk/claus/calendar.html)  L                    o  http://es.rice.edu/ES/humsoc/Galileo/Things/gregorian_#                       calendar.html   0                    o  http://www.timeanddate.com  I                    are all good time-related resources, with some generalt0                    and some specific to OpenVMS.                        4-2 k  d          '                    Time and Timekeepingi      '           _____________________________ <           4.1.1__Details_of_the_OpenVMS system time-keeping?  7           4.1.1.1__VAX_hardware_time-keeping details...              4.1.1.1.1  TOY clock  F                    This is battery backed up hardware timing circuitryJ                    used to keep the correct time of year during rebooting,G                    power failures, and system shutdown. This clock onlyhJ                    keeps track of months, days, and time. The time is keptJ                    relative to January 1st, at 00:00:00.00 of the year the*                    clock was initiailized.J                    The VAX Time-Of-Year (TOY) clock (used to save the timeI                    over a reboot or power failure) is specified as havingDH                    an accuracy of 0.0025%. This is a drift of roughly 65%                    seconds per month.i  J                    The VAX Interval Time is used to keep the running time,G                    and this has a specified accuracy of .01%. This is ai?                    drift of approximately 8.64 seconds per day.y  F                    Any high-IPL activity can interfere with the IPL 22E                    or IPL 24 (this depends on the VAX implementation) G                    clock interrupts-activities such as extensive devicetG                    driver interrupts or memory errors are known to slowM                    the clock.   '           _____________________________n#           4.1.1.1.2  EXE$GQ_SYSTIMEw  F                    This is the OpenVMS VAX system time cell. This cellG                    contains the number of 100ns intervals since a knownwF                    reference. This cell is incremented by 100000 every6           _________10ms_by_an_hardware_interval timer.  $           4.1.1.1.3  EXE$GQ_TODCBASE  G                    This cell contains the time and date the system timeoE                    was last adjusted by EXE$SETTIME. It uses the sameSH                    format as EXE$GQ_SYSTIME. On adjustment of the systemJ                    time a copy of EXE$GQ_SYSTIME is stored in this cell inH                    both memory and on disk. This cell is used to get the,                    year for the system time.  J                                                                        4-3    p          '                    Time and Timekeeping       '           _____________________________e            4.1.1.1.4  EXE$GL_TODR  G                    This cell contains the time and date the system timehE                    was last adjusted by EXE$SETTIME. It uses the sametI                    format as the time of year clock. On adjustment of the G                    system time this cell gets saved back to both memory G                    and disk. The contents of this cell are used to test 1                    the validity of the TOY clock. C                    The system parameters SETTIME and TIMEPROMPTWAIT_=                    determine how the system time will be set._  ?                    o  IF SETTIME = 0 and the TOY clock is validrH                       THEN the contents of the TOY clock are compared toJ                       those of EXE$GL_TODR.  IF the TOY clock is more than.                       a day behind EXE$GL_TODR?                         THEN the TOY clock is presumed invalid.q  G                      o  IF the TOY clock is within a day of EXE$GL_TODR F                         THEN the system time is calculated as follows:  H                      o  EXE$GQ_SYSTIME = EXE$GQ_TODCBASE + ((TOY_CLOCK -.                         EXE$GL_TODR) * 100000)  @                    o  IF SETTIME = 1 or the TOY clock is invalidH                       THEN the value of TIMEPROMPTWAIT determines how toD                       reset the time of year.  IF TIMEPROMPTWAIT > 0H                         THEN the user is prompted for the time and date,D                         for a length of time equal to TIMEPROMPTWAIT(                         microfortnights.  -                      o  IF TIMEPROMPTWAIT = 0dI                         THEN the time of year is the value of EXE$GL_TODRi                         + 10ms.   -                      o  IF TIMEPROMPTWAIT < 0 4                         to proceed until they do so.  G                      o  THEN the user is prompted for the time and date "                         and unable  J                    When booting a CD-ROM containing an OpenVMS VAX system,G                    the system will typically be deliberately configured H                    prompt the user to input the time - this is necessary:                    in order to boot with the correct time.                      4-4               '                    Time and Timekeeping         G                    If either TIMEPROMPTWAIT or SETTIME are set to zero, E                    OpenVMS VAX will use the TOY clock to get the time A                    of year, and the year will be fetched from the_D                    distribution medium. The value of the year on theG                    distribution medium (saved within the SYS.EXE image) I                    will most likely be that of when the kit was mastered, I                    and cannot be changed. Unless the current year happens H                    to be the same year as that on the distribution, mostH                    likely the year will be incorrect. (Further, with theG                    calculation of Leap Year also being dependent on theaE                    current year, there is a possibility that the daten0                    could be incorrect, as well.)  '           _____________________________ 9           4.1.1.2__Alpha_hardware_time-keeping details...   9           4.1.1.2.1  Battery-Backed Watch (BB_WATCH) Chipv  F                    This is battery backed up hardware timing circuitryJ                    used to keep the correct time of year during rebooting,H                    power failures, and system shutdown. This clock keepsC                    track of date and time in 24 hour binary format.uF                    The BB_WATCH time is used to initialize the runningF                    system time during bootstrap, and the BB_WATCH timeF                    is read when the SET TIME command is issued with noG                    parameters; when the running system time is reset tofG                    the value stored in the BB_WATCH. The running system.F                    time is written into the BB_WATCH when the SET TIME6                    command is issued with a parameter.  I                    The specification for maximum clock drift in the Alpha E                    hardware clock is 50 parts per million (ppm), thatvF                    is less than 0.000050 seconds of drift per second,E                    less than 0.000050 days of drift per day, or less/G                    than 0.000050 years of drift per year, etc. (eg: An4J                    error of one second over a day-long interval is roughlyG                    11ppm, or 1000000/(24*60*60).) Put another way, thislH                    is .005%, which is around 130 seconds per month or 26$                    minutes per year.  J                    The software-maintained system time can drift more thanH                    this, primarily due to other system activity. TypicalH                    causes of drift include extensive high-IPL code (softJ                    memory errors, heavy activity at device IPLs, etc) that  J                                                                        4-5 T  x          '                    Time and Timekeeping         H                    are causing the processing of the clock interrupts to                    be blocked.  '           _____________________________ #           4.1.1.2.2  EXE$GQ_SYSTIME   H                    This is the OpenVMS Alpha system time cell. This cellH                    contains the number of 100ns intervals since NovemberD                    17, 1858 00:00:00.00. This cell is incremented byC           _________100000_every_10ms_by an hardware interval timer.T  )           4.1.1.2.3  EXE$GQ_SAVED_HWCLOCKl  J                    This cell is used by OpenVMS Alpha to keep track of theJ                    last time and date that EXE$GQ_SYSTIME was adjusted. ItJ                    keeps the same time format as EXE$GQ_SYSTIME. The valueI                    in this cell gets updated in memory and on disk, everye5                    time EXE$GQ_SYSTIME gets adjusted.   F                    o  The system parameters SETTIME and TIMEPROMPTWAIT@                       determine how the system time will be set.  $                    o  If SETTIME = 0G                       then EXE$INIT_HWCLOCK reads the hardware clock too*                       set the system time.  -                      o  IF TIMEPROMPTWAIT > 0 G                         THEN the value of TIMEPROMPTWAIT determines how C                         long the user is prompted to enter the time F                         and date. If time expires and no time has beenI                         entered the system acts as if TIMEPROMPTWAIT = 0.   -                      o  IF TIMEPROMPTWAIT = 0 C                         THEN the system time is calculated from theo=                         contents of EXE$GQ_SAVED_HWCLOCK + 1.v  -                      o  IF TIMEPROMPTWAIT < 0oG                         THEN the user is prompted for the time and daterG                         and unable to continue until the information ist                          entered.  F                    Unlike the VAX, the Alpha hardware clock tracks theF                    full date and time, not just the time of year. ThisE                    means it is possible to boot from the CD-ROM media E                    without entering the time at the CD-ROM bootstrap. B                    (This provided that the time and date have been+                    initialized, of course.)d                      4-6               '                    Time and Timekeepinge        F                    IA-64 (Itanium) hardware time-keeping details to be                    added...h  '           _____________________________ E           4.1.1.3  Why does VAX need a SET TIME at least once a year?_  I                    Because the VAX Time Of Year (TOY) has a resolution of I                    497 days, the VAX system time is stored using both the H                    TOY and the OpenVMS VAX system image SYS.EXE. BecauseH                    of the use of the combination of the TOY and SYS.EXE,F                    you need to issue a SET TIME command (with the timeI                    parameter specified) at least once between January 1st_F                    and about April 11th of each year, and whenever youG                    change system images (due to booting another OpenVMS J                    VAX system, booting the standalone BACKUP image, an ECO/                    that replaces SYS.EXE, etc).-  C                    The SET TIME command (with the current time as alD                    parameter) is automatically issued during variousG                    standard OpenVMS procedures such as SHUTDOWN, and ittF                    can also obviously be issued directly by a suitablyH                    privileged user. Issuing the SET TIME command (with aI                    parameter) resets the value stored in the TOY, and (ifrG                    necessary) also updates the portion of the time (theeC                    current year) saved in the SYS.EXE system image._  C                    This VAX TOY limit is the reason why OpenVMS VAXoE                    installation kits and standalone BACKUP explicitly_I                    prompt for the time during bootstrap, and why the time_J                    value can "get weird" if the system crashes outside theJ                    497 day window (if no SET TIME was issued to update theH                    saved values), and why the time value can "get weird"G                    if a different SYS$SYSTEM:SYS.EXE is used (alternate_8                    system disk, standalone BACKUP, etc).  '           _____________________________t;           4.1.2  How does OpenVMS VAX maintain system time?_  I                    VAX systems maintain an interval clock, and a hardware_                    clock.   E                    The VAX hardware clock is called the TOY ("Time Of J                    Year") clock. The register associated with the clock is<                    called the TODR ("Time Of Day Register").  J                                                                        4-7 i  i          '                    Time and Timekeepingy        H                    The TOY clock-as used-stores time relative to JanuaryI                    first of the current year, starting at at 00:00:00.00.oJ                    It is a 100 Hz, 32-bit counter, incremented every 10ms,=                    and thus has a capacity of circa 497 days.   C                    OpenVMS (on the VAX platform) stores system date E                    information-and in particular, the current year-in 8                    the system image, SYS$SYSTEM:SYS.EXE.  E                    The TOY is used, in conjunction with the base datelI                    that is stored and retrieved from the system image, toiH                    initialize the interval clock value that is stored in"                    EXE$GQ_SYSTIME.  E                    Once the interval clock is loaded into the runningtE                    system as part of the system bootstrap, the system G                    does not typically reference the TOY again, unless a H                    SET TIME (with no parameters) is issued. The intervalF                    clock value is updated by a periodic IPL22 or IPL24H                    (depending on the specific implementation) interrupt.H                    (When these interrupts are blocked as a result of theG                    activity of higher-IPL code-such as extensive drivernJ                    interrupt activity or a hardware error or a correctableG                    (soft) memory error-the clock will "loose" time, and J                    the time value reported to the user with appear to have                     slowed down.)  F                    When SET TIME is issued with no parameters, the TOYE                    clock is loaded into the system clock; the runningmD                    system clock is set to the time stored in the TOYE                    clock. This assumes the TOY clock is more accurate B                    than the system clock, as is normally the case.  B                    On most (all?) VAX systems, the battery that isH                    associated with the TOY clock can be disconnected andE                    replaced if (when) it fails-TOY clock failures are_J                    quite commonly caused by a failed nickel-cadmium (NiCd)B                    or lithium battery, or by a failed Dallas chip.                                4-8               '                    Time and Timekeepingg      D           __________________________________________________________<           4.2  Keeping the OpenVMS system time synchronized?  D                    To help keep more accurate system time or to keepH                    your system clocks synchronized, TCP/IP Services NTP,E                    DECnet-Plus DTSS (sometimes known as DECdtss), DCE I                    DTS, and other techniques are commonly used. If you doOG                    not or cannot have IP access to one of the availablefH                    time-base servers on the Internet, then you could useI                    dial-up access to NIST or other authoritative site, or_I                    you can use a direct connection to a local authorativeO                    clock.r  F                    There exists code around that processes the digitalC                    (ie: binary) format time that is available via amI                    modem call into the NIST clock (the Automated Computer_I                    Telephone Service (ACTS) service), and code that grabsDJ                    the time off a GPS receiver digital link, or a receiverG                    (effectively a radio and a codec) that processes the_G                    time signals from radio stations WWV, WWVH, WWVB, or9                    similar.y  C                    Processing the serial or hardware time protocols I                    often involves little more than reading from an EIA232 H                    (RS232) serial line from the receiver, something thatE                    is possible from most any language. Information on_G                    correctly drifting the OpenVMS system clock to match_I                    the time-base time is available within the logic of atrG                    least one OpenVMS Freeware package. (See Section 4.3n9                    for a few potential hardware options.)   D                    One example of acquring a time-base through localD                    integrated hardware involves the IRIG time formatC                    (IRIG-A, -B, -G), a binary signal containing thetC                    current time in hours, minutes, seconds and days E                    since the start of the current year. IRIG can alsonI                    contain the time of day as the number of seconds sinceMF                    midnight. HP Custom Systems and third-party vendorsE                    have variously offered IRIG-based reader/generator8/                    modules for OpenVMS systems.A  C                    One of the easiest approaches is a network-based F                    GPS or other similar receiver. Basically, this is aF                    network server box that provides an NTP server withG                    the necessary hardware for external synchronization. B                    In addition to the antenna and the receiver and  J                                                                        4-9 m             '                    Time and Timekeepingt        I                    processing components, these devices provide a network F                    interface (NIC) and support for an NTP time server,D                    and applications including the NTP support withinD                    TCP/IP Services and within various third-party IPJ                    stacks can then be used to synchronize with the the NTPH                    information provided by time-base receivers. No otherG                    host software is required, and no host configuration/F                    steps and no host software beyond NTP are required.J                    (See Section 4.3 for a few potential hardware options.)  J                    Differing time servers (DECnet-Plus DTSS, DCE DTS, NTP,I                    etc) do not coexist particularly well, particularly ifeF                    you try to use all these together on the same node.D                    Please pick and use just one. (If needed, you canJ                    sometimes configure one package to acquire its timebaseJ                    from another protocol, but one and only one time serverI                    package should have direct control over the management G                    of and drifting of the local OpenVMS system time. In G                    the specific case of DECnet-Plus DTSS, older product J                    versions and versions V7.3 and later provide a providerJ                    module, a module which permits DTSS to acquire its timeI                    from NTP. For details on this, please see the commentsn6                    in the module DTSS$NTP_PROVIDER.C.)  I                    Unlike DECnet-Plus, TCP/IP Services NTP is not capablecF                    of connecting to a time-base other than the networkG                    time base or the local system clock. Third-party andtD                    open source NTP implementations are available for$                    OpenVMS, as well.                      Useful URLs:   J                    o  http://www.boulder.nist.gov/timefreq/service/nts.htm  K                    o  http://www.boulder.nist.gov/timefreq/service/acts.htm   ;                    o  http://www.boulder.nist.gov/timefreq/   *                    o  http://www.time.gov/                              4-10t e  g          '                    Time and Timekeeping]      D           __________________________________________________________+           4.3  External time-base hardware?R  G                    Here are a few possibilities for providers of a GPS-oG                    based receiver with an embedded NTP server, strictly_F                    culled from the first few pages of a Google search.I                    Availability, pricing, OpenVMS compatibility and otherR)                    factors are not known.o  0                    o  http://www.galleon.eu.com/  5                    o  http://www.meinberg.de/english/   1                    o  http://www.ntp-servers.com/_  H                    For a direct-connected (local, non-IP, non-NTP) link,C                    there are serial options available. Google finds_F                    Spectracom Corporation has a NetClock that could beJ                    used here, based on a quick look-I do not know if thereG                    is OpenVMS host software, but that would be possible E                    to write for the ASCII data stream that the devicepF                    supports. (Such coding requires knowledge of serialH                    I/O, character processing, and knowledge of the clockH                    drift API mechanisms in OpenVMS-there exists FreewareH                    tools that could be used to learn how to tie into the9                    clock drifting mechanisms of OpenVMS.)b  4                    o  http://www.spectracomcorp.com/  (           http://www.spectracomcorp.com/  I                    Information on, and experiences or recommendations for H                    or against these or other similar devices is welcome.  '           _____________________________ :           4.3.1  Why do my cluster batch jobs start early?  J                    Your system time is skewed across your cluster members,I                    and the cluster member performing the queue management I                    tasks has a system time set later than the system time_7                    of the member running the batch job.   >                    This behaviour is most noticable when usingD                    SUBMIT/AFTER=TOMORROW and similar constructs, andE                    use of /AFTER="TOMMOROW+00:01:00" or such is often_F                    recommended as a way to avoid this. The combinationI                    time value specified should be larger than the maximum   J                                                                       4-11    h          '                    Time and Timekeepings        H                    expected time skew. In the example shown, the maximum@                    cluster clock skew is assumed less than 1:00.  D                    You can also maintain your system times in betterE                    synchronization, with available tools described inO-                    Section 4.2 and elsewhere.   '           _____________________________ 7           4.3.2  Why does my OpenVMS system time drift?n  E                    Memory errors, hardware problems, or most anything_G                    operating at or above IPL 22 or IPL 24 (clock IPL is F                    system family dependent; code executing at or aboveC                    the clock IPL will block the processing of clock_H                    interrupts), can cause the loss of system time. ClockE                    drift can also be caused by normal (thermal) clock E                    variations and even by the expected level of clockd                    drift.5  G                    When clock interrupts are blocked as a result of thesE                    activity of high-IPL code-such as extensive drivertJ                    interrupt activity or a hardware error or a correctableG                    (soft) memory error-the clock will "loose" time, and_J                    the time value reported to the user with appear to haveI                    slowed down. Correctable memory errors can be a common G                    cause of system time loss, in other words. Heavy PCIw8                    bus traffic can also cause lost time.  I                    One bug in this area involved the behaviour of certain I                    graphics controllers including the ELSA GLoria SynergyiF                    PBXGK-BB; the PowerStorm 3D10T effectively stallingH                    the PCI bus. See Section 5.16 for details on the ELSAG                    GLoria Synergy controller, and make certain you haver:                    the current GRAPHICS ECO kit installed.  G                    Clock drift can also be (deliberately) caused by thed8                    activity of the DTSS or NTP packages.  A                    Also see Section 4.1.1.2.1, Section 4.1.1, andd!                    Section 4.3.4.                             4-12T    u          '                    Time and Timekeepingt      '           _____________________________ 9           4.3.3  Resetting the system time into the past?   G                    You can resynchronize system time using DCL commandshC                    such as SET TIME and SET TIME/CLUSTER, but theseeD                    commands can and obviously will cause the currentJ                    system time to be set backwards when the specified timeH                    predates the current system time. This time-resettingD                    operation can cause application problems, and canG                    adversely effect applications using absolute timers,lF                    applications that assume time values will always beA                    unique and ascending values, and applications.r  G                    Setting the time backwards by values of even an hour H                    has caused various run-time problems for applicationsH                    and layered products. For this reason, this techniqueJ                    was not considered supported during the Year 2000 (Y2K)C                    testing; a system or cluster reboot was strongly B                    recommended as the correct means to avoid these                    problems.  J                    Application programmers are encouraged to use the time-I                    related and TDF-related events that are available with F                    the $set_system_event system service, and/or to useF                    UTC or similar time, as these techniques can permitE                    the application to better survive retrograde clock F                    events. (There is an ECO to repair problems seen inI                    the DECnet-Plus support for generating TDF events from I                    DTSS, and this applies to V7.3 (expected to be in ECO4 G                    and later) V7.3-1 (expected to be in ECO3 and later) G                    and V7.3-2 (expected to be in ECO1 and later). Apply J                    the most current DECnet-Plus ECO kits for these OpenVMSJ                    releases, for best TDF event support from DECnet-Plus.)  7                    See Section 4.3.4 and Section 4.3.1.e  '           _____________________________o9           4.3.4  How can I drift the OpenVMS system time?g  G                    With DECdts and TCP/IP Services NTP, the system timePI                    value is "drifted" (rather than changed), to avoid theiH                    obvious problems that would arise with "negative timeG                    changes". The same basic clock drifting technique is I                    used by most (all?) time servers operating on OpenVMS, I                    typically using the support for this provided directly_"                    within OpenVMS.  J                                                                       4-13 T             '                    Time and Timekeeping         D                    An example of the technique used (on OpenVMS VAX)G                    to drift the system time is the SETCLOCK tool on the $                    OpenVMS Freeware.  J                    For information on the use of the EXE$GL_TIMEADJUST andH                    EXE$GL_TICKLENGTH cells on OpenVMS Alpha, see OpenVMSI                    AXP Internal and Data Structures, located on page 348.g  G                    For those areas which switch between daylight savingSF                    time (DST) and standard time, the time value is notH                    drifted. The time is adjusted by the entire interval.F                    This procedure is inherent in the definition of theD                    switch between DST and standard time. (Do look atE                    either not switching to daylight time, or (better) J                    using UTC as your time-base, if this change-over is not2                    feasible for your environment.)  7                    See Section 4.3.4 and Section 4.3.3.K  '           _____________________________ B           4.3.5  How can I configure TCP/IP Services NTP as a time                  provider?  H                    An NTP time provider provides its idea of the currentI                    time to NTP clients via the NTP protocol. Most systemsc*                    are NTP clients, but...  D                    NTP has a heirarchy of layers, called strata. TheI                    further away from the actual NTP time source (InternetlG                    time servers are at stratum 1), the lower the stratasC                    (and the larger the number assigned the statum).a  H                    NTP explicity configured at stratum one provides timeJ                    to NTP operating at lower strata, and the provided timeI                    is acquired based on the local system time or via somen;                    locally-accessible external time source.d  E                    NTP at other (lower) strata both receive time from F                    higher strata and can provide time to lower strata,J                    and automatically adjust the local stratum. The highestF                    stratum is one, and the lowest available stratum is                    fifteen.   E                    The TCP/IP Services NTP package can operate at anydI                    stratum, and can be configured as a peer, as a client, I                    or as a broadcast server. NTP can also provide time to ?                    a DECnet-Plus DTSS network, see Section 4.2.f                      4-14J u  a          '                    Time and Timekeeping         J                    With TCP/IP Services V5.0 and later, the only supportedF                    reference clock is the LCL (local system clock). IfF                    your system has an excellent clock or if the systemF                    time is being controlled by some other time serviceF                    or peripheral (such as DTSS services, GPS services,E                    a cesium clock, a GPIB controller or other similar I                    time-related peripheral), you can configure NTP to use.F                    the system clock as its reference source. This willJ                    mimic the master-clock functionality, and will configreH                    NTP as a stratum 1 time server. To do this, enter the8                    following commands in TCPIP$NTP.CONF:  ,                    server 127.127.1.0 prefer.                    fudge 127.127.1.0 stratum 0  H                    For local-master functionality, the commands are very!                    similiar. Use:s  %                    server 127.127.1.0e.                    fudge 127.127.1.0 stratum 8  G                    The difference between these two is the stratum, and.J                    the omission of the prefer keyword. Specifying a higherI                    stratum allows the node to act as a backup NTP server,/H                    or potentially as the sole time server on an isolatedG                    network. The server will become active only when alldH                    other normal synchronization sources are unavailable.C                    The use of "prefer" causes NTP to always use the F                    specified clock as the time synchronization source.  C                    With the TCP/IP Services versions prior to V5.0, B                    the NTP management is rather more primitive. ToA                    configure the local OpenVMS system from an NTPiG                    client to an NTP server (on TCP/IP Services versions @                    prior to V5.0), add the following line to the;                    sys$specific:[ucx$ntp]ucx$ntp.conf file:t  !                    master-clock 1e  G                    Also, for TCP/IP Services prior to V5.0, see the NTP !                    template file:   9                    SYS$SPECIFIC:[UCX$NTP]UCX$NTP.TEMPLATE.  J                                                                       4-15    e          '                    Time and Timekeepinge        G                    Note that NTP does not provide for a Daylight Saving F                    Time (DST) switch-over, that switch must arise fromI                    the timezone rules on the local system and/or from the E                    SYS$EXAMPLES:DAYLIGHT_SAVINGS procedure. (Further, A                    there is a known bug in SYS$EXAMPLES:DAYLIGHT_oG                    SAVINGS.COM in V7.3, please obtain the available ECO                     kit.)  B                    For current TCP/IP Services and related OpenVMS-                    documentation, please see:u  7                    o  http://www.hp.com/go/openvms/doc/   D           __________________________________________________________H           4.4  Managing Timezones, Timekeeping, UTC, and Daylight Saving                Time?  >                    You will want to use the command procedure:  4                    o  SYS$MANAGER:UTC$TIME_SETUP.COM  H                    to configure the OpenVMS Timezone Differential FactorC                    (TDF) on OpenVMS V6.0 and later. Select the BOTHaD                    option. This configures the OpenVMS TDF settings,E                    though it may or may not configure the TDF and the B                    timezone rules needed or used by other softwareH                    packages. Please do NOT directly invoke the following&                    command procedures:  I                    o  SYS$MANAGER:UTC$CONFIGURE_TDF.COM ! do not directly                        use   J                    o  SYS$MANAGER:UTC$TIMEZONE_SETUP.COM ! do not directly                       use   F                    TCP/IP Services V5.0 and later use the OpenVMS TDF,H                    UTC, and timezone support. Earlier versions use a TDFJ                    mechanism and timezone database that is internal to theI                    TCP/IP Services package. Also on the earlier versions, D                    the TDF must be manually configured within TCP/IPE                    Services, in addition to the OpenVMS configurationm                    of the TDF.                        4-16l e  e          '                    Time and TimekeepingT        F                    DECnet-Plus in V7.3 and later uses the OpenVMS TDF,G                    UTC, and timezone support, and displays its timezone I                    prompts using UTC$TIME_SETUP.COM. Earlier versions use H                    a TDF TDF mechanism, timezone database, and automaticB                    switch-over that is internal to the DECnet-PlusE                    package. Also on earlier versions, the TDF must beeH                    configured within the DECnet-Plus DECdtss package, inD                    addition to the OpenVMS configuration of the TDF.  B                    Application code using HP C (formerly Compaq C,C                    formerly DEC C) will use the OpenVMS UTC and TDFXI                    mechanisms when the C code is compiled on OpenVMS V7.0cF                    and later (and when the macro _VMS_V6_SOURCE is NOTF                    defined). HP C does NOT use the OpenVMS UTC and TDFD                    mechanisms when the C code is compiled on OpenVMSC                    releases prior to V7.0, or when the preprocessort:                    declaration _VMS_V6_SOURCE is declared.  C                    DCE DTS TDF management details to be determined.   F                    In OpenVMS Alpha V6 releases (V6.1, V6.2, V6.2-1Hx,H                    etc), the TDF value is written to SYS$BASE_IMAGE.EXE.I                    With OpenVMS Alpha V7.0 and later and with OpenVMS VAXtG                    V6.0 and later, SYS$SYSTEM:SYS$TIMEZONE.DAT containsnF                    the TDF. This means that OpenVMS Alpha systems willD                    need to have the TDF value reset manually-usuallyE                    within SYSTARTUP_VMS.COM-on reboots prior to V7.0.t  E                    During OpenVMS Bootstrap, the SYSINIT module readsmE                    SYS$TIMEZONE.DAT to acquire the TDF for use in the H                    system global cell EXE$GQ_TDF. This is done to ensureH                    that the system boots with a valid TDF (a value whichD                    may be zero). The UTC system services get the TDFF                    from this cell. These services, as well as the HP CF                    RTL, must have a valid TDF. (Prior to OpenVMS V7.3,D                    if either DECnet-Plus or DECnet/VAX Extensions isF                    configured and run, the image DTSS$SET_TIMEZONE.EXEH                    is invoked and can override the TDF and timezone ruleD                    settings from SYSINIT or from UTC$TIME_SETUP.COM-C                    this image runs even if DTSS is disabled. If the C                    settings do not match (due to inconsistencies inaC                    timezone specification in UTC$TIME_SETUP.COM and J                    NET$CONFIGURE.COM), DTSS will reset the values to match$                    its definitions.)  J                                                                       4-17               '                    Time and Timekeepingc        D                    Prior to OpenVMS V7.3, daylight saving time (DST)H                    switchover is handled automatically only when DCE DTSI                    or DECnet-Plus DTSS is in use. In V7.3, OpenVMS can beuF                    configured to automatically switch over to daylightD                    time, and also generates an event that interestedI                    applications can use to detect the switch-over between 3                    standard time and daylight time.m  B                    The manual switchover between daylight time andB                    standard time is correctly accomplished via theF                    SYS$EXAMPLES:DAYLIGHT_SAVINGS.COM command procedure                    procedure.   1                                              Noteh  D                       NTP (alone) does NOT provide automatic switch-                       over.s  1                                              Note   A                       The DST switch-over does NOT drift the time ?                       value; the switch-over applies the entire4G                       difference as a unit, as is standard and expectedh@                       practice. (Do look at either not switching@                       to daylight time, or (better) using UTC as@                       your time-base, if this one-hour change isA                       not feasible within your environment.) (FornE                       information associated with drifting the systenc6                       time, please see Section 4.3.4.)  F                    If you switch the TDF or DST setting, you will alsoD                    want to restart or reconfigure any time-sensitiveF                    applications (those not using the time differentialB                    factor (TDF) change event available in V7.3 andE                    later). Examples of these applications can include F                    the need to restart the NFS client and NTP. (In theI                    case of NTP, will want to try to "drift" the time (seeeI                    Section 4.2 and see Section 4.3.4), and will find thatrJ                    the DST switch-over will exceed the NTP-defined maximumH                    threshold allowed for drifting. Hence the NTP restart*                    is presently required.)                          4-18d    n          '                    Time and Timekeepingl      '           _____________________________tF           4.4.1  Creating, Updating and Managing Timezone Definitions?  F                    One issue with the UTC implementation on OpenVMS isG                    the behaviour of C functions and other programs that G                    use SYS$TIMEZONE_RULE; the OpenVMS mechanism assumes F                    all control over the timezone and the daylight timeI                    switchover. This allows calculation of the time by thee6                    C library and various applications.  H                    This can be incompatible with a system or applicationG                    that requires manual modifications to the DST or TDF C                    settings, or that requires a local or customized A                    timezone definition. For such a site to ensure D                    the timekeeping is correct, the site must provideF                    procedure that sets the local time and the TDF when7                    the SYS$TIMEZONE_RULE says to do it.   I                    If a site requires a non-standard time switch-over, asoH                    in coordinating with a shift change or due to changesD                    in the local or regional timezone rules, the siteG                    will need to use the zic compiler to create a custom !                    timezone rule.a  F                    Additionally, applications may need to have specialG                    actions taken or actions queued just before the time I                    change takes effect. If the application source code is H                    available, one of the best ways to handle this is viaH                    the TDF and time-change notification events availableG                    via the OpenVMS sys$set_system_event system service.   J                    For information on zic and related tools used to manageE                    the OpenVMS Timezone database, please see the HP C I                    Run-time Library Utilities Reference Manual-though the F                    title would imply otherwise, this particular manualD                    is part of the OpenVMS documentation set, and notG                    part of the HP C (formerly Compaq C, formerly DEC C).%                    documentation set.   @                    For related information, see Section 4.4.1.1.          J                                                                       4-19 t  a          '                    Time and Timekeepingd      '           _____________________________uG           4.4.1.1  Customizing or Updating your TDF (Timezone) Setting?   I                    Individual, local, and regional differences on the use I                    (or the lack of use) of Daylight Saving Time (DST) areSH                    quite common, as are occasional regulatory changes toH                    the particular applicable regional DST settings. (eg:F                    The United States Government is expecting to changeF                    its DST rules starting in March of 2007; please see0                    Section 4.4.1.2 for details.)  H                    DST-related ECO kits are now available for various ofJ                    the supported releases, please see the ECO FTP site for                    details.d  C                    If you need or wish to add, modify or remove DST H                    rules for your area, or otherwise alter the rules forG                    your local area, you will probably end up creating anI                    variation to an existing timezone rule, or potentially B                    simply downloading a new set of DST rules. ThisE                    requirement can arise, for instance, if your local)I                    region changes its timezone rules, or if you are using G                    an OpenVMS release that does not have an ECO kit fort/                    the US DST rules available.)_  D                    The necessary zone line to add for support of theH                    hypothetical new WhereEverLand timezone will probably,                    look something like this:  R                    # Zone  NAME            GMTOFF  RULES/SAVE      FORMAT  [UNTIL]L                    Zone    WhereEver       2:00    -               WhereEver  F                    The OpenVMS source files for the timezone rules are                    stored here:   ;                    SYS$COMMON:[SYS$ZONEINFO.SYSTEM.SOURCES]e  F                    You'll then want to use the zic compiler to compileH                    your own new timezone definition, or to compile a newE                    set of timezone definitions that have been freshlyc6                    downloaded from a published source.  @                    The zic compiler is documented in the OpenVMSG                    Documentation Set, and specifically in the HP C Run-aF                    Time Library Reference Manual. (Despite the name ofG                    this manual, it is part of the OpenVMS documentationt1                    set and not of the C manuals.)                       4-20e m  ,          '                    Time and Timekeepingo        D                    Once you have created and compiled a new timezoneI                    rule (or have downloaded and have compiled a whole new H                    set of timezone rules), use the SYS$MANAGER:UTC$TIME_I                    SETUP.COM to select the new timezone if necessary-withSH                    V7.3 and later, this tool will automically notice theG                    new timezone and will offer it, on earlier releases,eJ                    you may/will have to hack the code of the tool somewhatG                    to allow it to present the new timezone rule. (If anvG                    existing timezone rule is simply changing, you don'tr0                    need this re-selection step.)  1                                              Notel  A                       As mentioned in Section 4.4.2, please don'thF                       modify or redefine the TZ logical name (found onE                       older configurations), or the SYS$TIMEZONE_NAME C                       logical name, or any other time- or timezone- F                       related logical names directly yourself. Rather,F                       please use the zic compiler and/or the UTC$TIME_*                       SETUP.COM procedure.  E                    For various published timezone rules or updated toeD                    same, see the tar.gz files (these are gzipped tar*                    archives) available at:  2                    o  ftp://elsie.nci.nih.gov/pub/  G                    These are gzipped tar archives, and are the pubished H                    source used for the OpenVMS timezone rules on OpenVMSH                    V7.3 and later, and within the predecessor C run-timeE                    environment timezone support used on older OpenVMS_E                    releases. You'll need to first gunzip and then use B                    vmstar to unpack and access the contents of the                    archives.  J                    The published timezone rules include the effective dateJ                    ranges for the individual rules, so you can reload yourH                    rules prior to a particular set of new rules becomingD                    effective. The effective dates for the particularI                    timezone rules are additionally necessary to allow thecJ                    appropriate translation of older dates and times withinG                    the appropriate historical context of the particular '                    date and time value.o  >                    For related information, see Section 4.4.1.  J                                                                       4-21 l             '                    Time and Timekeepingo      '           _____________________________D@           4.4.1.2  US Daylight Time Changes Starting 1-Mar-2007?  D                    The United States Federal Government is presentlyG                    expecting to change its DST rules starting in March,VE                    2007. (The change-over date and the planned changesH                    itself has not come to pass as of this writing, hence&                    the phrasing used.)  G                    As amended, US daylight time will be increased to behH                    effective from the second Sunday in March through theF                    first Sunday of November. Other countries, US localF                    political geographies and businesses may or may notG                    follow suite and implement these changes, obviously.o  E                    For further regulatory details, see the US Uniform I                    Time Act of 1966 (15 U.S.C 260a(a)), as amended by the -                    Energy Policy Act of 2005.t  I                    For details on how to create, customize or to downloadhE                    new rules and to update your local timezone rules, .                    please see Section 4.4.1.1.  '           _____________________________ :           4.4.2  Timezones and Time-related Logical Names?  D                    Various logical names are used to manage time andF                    timezones, and you should avoid direct modificationD                    of these logical names as the implementations areF                    subtle and quick to change. As discussed in sectionD                    Section 4.4.3, you will want to use the followingA                    command procedure to maintain the time and the                     timezone:  4                    o  SYS$MANAGER:UTC$TIME_SETUP.COM  H                    If you want to venture into uncharted territories andF                    modify the TDF used within older releases of TCP/IPI                    Services-within releases prior V5.0-you can attempt ton;                    use the following undocumented commands:r  C                    SET TIME/DIFF=[positive or negative TDF integer]a                     GENERATE TIME  B                    to reset the value of the logical name UCX$TDF.                      4-22  s  k          '                    Time and Timekeeping         6                    Prior to OpenVMS V7.3, the command:  <                    $ SETTZ :== $SYS$SYSTEM:DTSS$SET_TIMEZONE!                    $ SETTZ MODIFY   J                    can be used to modify the settings of the SYS$TIMEZONE_B                    DAYLIGHT_SAVING, SYS$TIMEZONE_DIFFERENTIAL, andF                    SYS$TIMEZONE_NAME system logical names based on the%                    SYS$TIMEZONE_RULE.a  D                    The following are other TDF-related logical namesB                    used/available on OpenVMS systems, with typicalF                    daylight time and standard time settings for the US.                    Eastern Time (ET) timezone.  "                    $daylight_time:>                    $ DEFINE/SYSTEM/EXECUTIVE MAIL$TIMEZONE EDTG                    $ DEFINE/SYSTEM/EXECUTIVE NOTES$TIMEZONE "-0400 EDT" Z                    $ DEFINE/SYSTEM/EXECUTIVE LISP$DAYLIGHT_SAVING_TIME_P true  ! Not 'EDT'K                    $ DEFINE/SYSTEM/EXECUTIVE LISP$TIME_ZONE 05   ! Constantv                    $"                    $standard_time:>                    $ DEFINE/SYSTEM/EXECUTIVE MAIL$TIMEZONE ESTG                    $ DEFINE/SYSTEM/EXECUTIVE NOTES$TIMEZONE "-0500 EST"oZ                    $ DEFINE/SYSTEM/EXECUTIVE LISP$DAYLIGHT_SAVING_TIME_P false ! Not 'EST'K                    $ DEFINE/SYSTEM/EXECUTIVE LISP$TIME_ZONE 05   ! Constantn                    $H                    $ DEFINE/SYSTEM/EXECUTIVE UCX$NFS_TIME_DIFFERENTIAL -U                        'f$integer(f$element(0," ",f$logical("notes$timezone"))/-100)'w  F                    For information on modifying these timezone logical@                    names and on managing the timezone rules, see!                    Section 4.4.1.e  '           _____________________________ =           4.4.3  How to troubleshoot TDF problems on OpenVMS?   H                    This is an OpenVMS Alpha system prior to V7.0 and the9                    startup is not invoking the procedure:   1                    SYS$MANAGER:UTC$TIME_SETUP.COM_  J                    This is an OpenVMS system prior to V6.0, where there is4                    no OpenVMS TDF nor UTC available.  J                                                                       4-23               '                    Time and Timekeepinga        B                    The version of the application does not use theF                    OpenVMS TDF. This includes TCP/IP Services prior toF                    V5.0, applications using HP C built on or targetingG                    OpenVMS prior to V7.0, and systems using the DECnet- G                    Plus DTSS mechanisms prior to the release associated H                    with OpenVMS V7.3. (DCE DTS TDF management details to"                    be determined.)  A                    If you should find either of the following twoa=                    timezone-related database files located inM)                    SYS$SPECIFIC:[SYSEXE]:   ;                    o  SYS$SPECIFIC:[SYSEXE]SYS$TIMEZONE.DATe  ?                    o  SYS$SPECIFIC:[SYSEXE]SYS$TIMEZONE_SRC.DATd  H                    These two files are in an erroneous location and must9                    be recreated in the correct directory:V  &                    SYS$COMMON:[SYSEXE]  &                    If the DCL command:  ;                    $ DIRECTORY SYS$SYSTEM:SYS$TIMEZONE*.DAT   J                    shows these files in SYS$SPECIFIC:[SYSEXE], then deleteJ                    them and use SYS$MANAGER:UTC$TIME_SETUP.COM to recreate                    them.  B                    On OpenVMS versions prior to V7.3, if the file:  5                    $ SYS$STARTUP:DTSS$UTC_STARTUP.COM   J                    is present on your system, then you may need to invoke:  ?                    $ @SYS$UPDATE:DTSS$INSTALL_TIMEZONE_RULE.COM   C                    to recreate the timezone files correctly. Invoke ?                    this command immediately after [re]executingt3                    SYS$MANAGER:UTC$TIME_SETUP.COM.)t  F                    If SYS$UPDATE:DTSS$INSTALL_TIMEZONE_RULE.COM is notG                    present on your system, then you may need to execute *                    the following commands:  <                    $ DELETE SYS$STARTUP:DTSS$UTC_STARTUP.COM<                    $ DEASSIGN/SYSTEM/EXEC SYS$TIMEZONE_RULE.                      4-24r a  h          '                    Time and Timekeeping         H                    If your system time is being reported as being off byJ                    one hour (or whatever the local DST change), please seeI                    sections Section 4.7, Section 4.4 and Section 10.22.1.   D           __________________________________________________________F           4.5  Why does the SET TIME command fail? Help managing DTSS?  F                    If you try to set the system time with the SET TIMEB                    command, and see one of the following messages:  6                    %SET-E-NOTSET, error modifying timeC                    -SYSTEM-F-IVSSRQ, invalid system service requestr  6                    %SET-E-NOTSET, error modifying time>                    -SYSTEM-E-TIMENOTSET, time service enabled;D                      enter a time service command to update the time  A                    This occurs if the time on the local system is E                    controlled by a time service software, for example H                    the distributed time service software (DTSS) providedD                    as part of the DECnet-Plus installation. The DTSSF                    software communicates with one or more time serversG                    to obtain the current time. It entirely controls thewI                    local system time (for DECnet-Plus, there is a processkF                    named DTSS$CLERK for this); therefore, the usage ofJ                    the SET TIME command (and the underlying $SETTIM system(                    service) is disabled.  D                    The first message is displayed on systems runningF                    DECnet-Plus V6.1 and earlier. On systems with newerJ                    DECnet-Plus software, the second (and more informative)$                    message is given.  G                    You shouldn't have to change the time manually - youlH                    should be doing this through the time server - but if>                    you insist... you'll have to shutdown DTSS:  '                    $ RUN SYS$SYSTEM:NCLe                    DISABLE DTSSe                    DELETE DTSS  I                    This will shutdown DTSS$CLERK. You may then change thefF                    system time as usual. To restart the DTSS software,                    type   .                    $ @SYS$STARTUP:DTSS$STARTUP  J                                                                       4-25               '                    Time and Timekeeping         E                    You will need a number of privileges to issue thisrG                    command, and you must also be granted the NET$MANAGES=                    identifer to shutdown and to restart DTSS.m  H                    If you wish to "permanently" disable DTSS on a systemF                    running DECnet-Plus, the above NCL sequence must beF                    performed each time the system is bootstrapped. (OnI                    DECnet-Plus V7.3 and later, you can define the logicalyJ                    name NET$DISABLE_DTSS to disable the DTSS startup. ThisH                    logical name must be defined in the command procedureG                    SYLOGICALS.COM, as this logical name must be present G                    and defined sufficiently early in the OpenVMS systemu:                    bootstrap sequence for it to function.)  I                    If DTSS is running and no time servers are configured,tC                    you can (and will) see the following messages att%                    regular intervals:s  K                    %%%%%%%%%%%  OPCOM   2-SEP-1999 19:41:20.29  %%%%%%%%%%% 5                    Message from user SYSTEM on UNHEDIaQ                    Event: Too Few Servers Detected from: Node LOCAL:.mynode DTSS,F@                            at: 1999-09-02-19:41:20.296-04:00Iinf-                            Number Detected=0, ,                            Number Required=1J                            eventUid   5FA70F4F-616E-11D3-A80E-08002BBEDB0FJ                            entityUid  DE9E97DE-6135-11D3-8004-AA000400BD1BJ                            streamUid  D6513A46-6135-11D3-8003-AA000400BD1B  J                    You can either configure the appropriate number of timeI                    servers, or you can disable DTSS, or you can ignore it3G                    and (if OPCOM is set to write to the log via via theaG                    logical names in SYLOGICALS.COM/SYLOGICALS.TEMPLATE)r4                    clean out OPERATOR.LOG regularly.  C                    You can also simply disable the display of these4                    messages:  '                    $ run sys$system:ncl H                    block event dispatcher outbound stream local_stream -&                        global filter -?                        ((Node, DTSS), Too Few Servers Detected)h                          4-26                '                    Time and Timekeepingt        F                    If you wish to disable the automatic TDF adjustmentI                    for the daylight time switch-over (on OpenVMS versionsS;                    prior to V7.3), you can use the command:r  '                    $ run sys$system:ncl 8                    set dtss automatic TDF change = false  F                    or alternatively, you can set the local timezone toH                    one that does not include the automatic daylight time                    change-over.   D                    OpenVMS V7.3 and later simplify time and timezone                    management.  D           __________________________________________________________F           4.6  Setting time on AlphaServer ES47, ES80, GS1280 console?  B                    To set the base system time on an member of theD                    AlphaServer ES47, AlphaServer ES80 or AlphaServerC                    GS1280 series system family, you must access them@                    Platform Management Utility (PMU). The PMU isH                    implemented within this family of related AlphaServerE                    systems, and is part of a layer providing servicesdD                    beyond those of the traditional Alpha SRM consoleH                    layer, and within a layer architecturally implementedF                    beneath the SRM console. In particular, the PMU andD                    related management components are used to provideF                    services across multiple vPars or nPars partitions.G                    In particular, the SRM obtains and manages the local F                    system time on these systems as a delta time offsetD                    from the underlying base system time. Neither theG                    SRM console nor OpenVMS directly accesses nor altershH                    the underlying base system time nor other information3                    maintained within the PMU layer.   A                    The PMU uses the System Management components, I                    centrally including the Backplane Manager (MBM) module D                    found in each drawer, user interface, PCI and CPUH                    management components, and the interconnections amongG                    these provided by the private system management LAN. J                    When the system has power applied and the main breakers/                    are on, the MBMs are active.f    J                                                                       4-27               '                    Time and Timekeeping.        G                    The PMU offers a command line interface for a serial I                    communications or telnet connection and allows commandNI                    and control of the MBM, and of the server. The PMU andiG                    the MBM system management components are responsiblee+                    for the following tasks:   I                    o  Show the system configuration and provide the basic1*                       debugging capability  C                    o  Initiate the firmware update or load the test0&                       firmware version  C                    o  Power on or off, halt, or reset the system or                        partitione  C                    o  The system partitioning and cabling functionse  E                    o  Displays of the health of hardware environment,TG                       including such constructs as fans, power suppliest?                       and environmental and temperature values.r  4                    o  Remote server management tasks  ?                    o  The connection to the virtual SRM console   8                    o  Set and show the base system time.  I                    You can use the MBM commands SHOW TIME and SET TIME to I                    view and to manipulate the base system time. The deltasH                    time value for the primary MBM will be indicated, andJ                    it is this value in conjunction with the base time thatH                    is used to generate the time available to OpenVMS viaH                    the SRM console. If you issue a SET TIME=time commandH                    from OpenVMS, the delta time will change, but not theJ                    MBM base system time. If you change the MBM base systemI                    time, the calculated time available to OpenVMS via theoG                    SRM console(s) will change. (Resetting the base timenH                    thus involves changing the base system time, and thenJ                    issuing SET TIME=time command(s) to each of the OpenVMSG                    vPars or nPars environments to adjust the respectiveiI                    delta time values.) Rebooting, resetting or issuing an ;                    MBM SET TIME will reset the system time.t  E                    Typically, you will want to establish the MBM timeu@                    value once, and probably setting it to UTC orF                    such, and you will then want to boot each partitionI                    conversationally, setting the SETTIME system parameter:                      4-28t               '                    Time and Timekeeping         E                    to force the entry of the time within each bootinglG                    system environment. Once the MBM time value has been D                    set once, you will typically not want to alter itF                    again. You will typically want to manage and modify>                    only the time values within each partition.  E                    The time and data values stored in the primary MBM I                    and replicated in the zero or more secondary MBMs thatrF                    might be present within the system are coordinated.  J                    To enter the PMU from the SRM console, and to exit back                    to SRM:  ;                    MBM - (PMU, Platform Management Utility)   8                      From SRM P00> enter {Esc} {Esc} MBMH                      CTRL/[ CTRL/[ MBM           (MBM must be uppercase)A                      MBM> connect                (to exit to SRM)_  F                    The <CTRL/[> is the escape character. Use the citedF                    key sequences to enter the PMU. You can also accessJ                    the PMU through a modem, or from a terminal or terminalF                    emulator or terminal server connected to the serverC                    management LAN. Having the server management LAN F                    bridged to an untrusted LAN can be unwise, however,E                    and with risks analogous to those of configuring a J                    traditional VAX or Alpha console serial line to an open9                    terminal server or to a dial-in modem.   J                    See the AlphaServer GS1280 documentation for additional                    information.   D           __________________________________________________________I           4.7  UTC vs GMT vs vs UT1/UT1/UT2 TDF? What are these acronyms?T  D                    The results of an international compromise-thoughF                    some would say an international attempt to increaseH                    confusion-UTC is refered to as "Coordinated UniversalE                    Time" (though not as CUT) in English and as "Temps F                    Universel Coordinn" (though not as TUC) in French.G                    (No particular information exists to explain why UTC I                    was chosen over the equally nonsensical TCU, according H                    to Ulysses T. Clockmeister, one of the diplomats thatB                    helped establish the international compromise.)  J                                                                       4-29 s  o          '                    Time and Timekeepingp        F                    Universal Time UT0 is solar time, UT1 is solar timeG                    corrected for a wobble in the Earth's orbit, and UT2cI                    is UT1 corrected for seasonal rotational variations ino;                    rotation due to the Earth's solar orbit.n  B                    GMT-Greenwich Mean Time-is UT1. GMT is the timeC                    at the classic site of the since-disbanded Royal J                    Greenwich Observatory; at the most widely-known tourist4                    attraction of Greenwich, England.  D                    UTC is based on an average across multiple atomicI                    clocks, and is kept within 0.9 seconds of GMT, through I                    the insertion (or removal) of seconds. In other words, G                    UTC matches GMT plus or minus up to 0.9 seconds, but "                    UTC is not GMT.  H                    TDF is the Timezone Differential Factor, the intervalE                    of time between the local time and UTC. Areas that I                    celebrate daylight saving time (DST) will see periodic I                    changes to the TDF value, when the switch-over between F                    daylight time and standard time occurs. The switch-E                    over itself is entirely left to local governmentalnH                    folks, and can and has varied by political entity andJ                    politics, and the switch-over has varied over the years-                    even at the same location.o  B                    If your local OpenVMS system time is off by oneF                    hour (or whatever the local DST change) for some orD                    all applications, you probably need to reset yourG                    local TDF. (For related details, please see sections 4                    Section 4.4 and Section 10.22.1.)  I                    Further discussions of history and politics, the Royal.H                    Observers' outbuildings, and the compromise that leftJ                    the English with the Time Standard (the Prime Meridian)E                    and the French with the standards for Distance andeH                    Weight (the Metric System) are left to other sources.J                    Some of these other sources include the following URLs:  2                    o  ftp://elsie.nci.nih.gov/pub/  C                    o  http://physics.nist.gov/GenInt/Time/time.htmln  +                    o  http://nist.time.gov/                       4-30t    U          '                    Time and TimekeepingI      D           __________________________________________________________;           4.8  Using w32time or an SNTP as a time provider?   J                    No standards-compliant NTP or SNTP server is reportedlyF                    capable of synchronizing with the Microsoft Windows$                    w32time services.  D                    Further, NTP clients are not generally capable of5                    synchronizing with an SNTP server.   C                    Open Source (Free) NTP servers (qv: OpenNTP) are H                    available for Microsoft Windows platforms, and TCP/IPD                    Services and third-party packages all provide NTPD                    servers for OpenVMS, and NTP and SNTP clients can1                    synchronize with these srvers.d                                                            J                                                                       4-31 e                       J                    _______________________________________________________  0           5        System Management Information      D           __________________________________________________________*           5.1  What is an installed image?  B                    The term "install" has two distinct meanings inH                    OpenVMS. The first relates to "installing a product",I                    which is done with either the SYS$UPDATE:VMSINSTAL.COMo?                    command procedure or the POLYCENTER SoftwareeE                    Installation (PCSI) utility (PRODUCT command). TheiC                    second meaning relates to the use of the INSTALLe;                    utility, which is what concerns us here.t  E                    The INSTALL utility is used to identify to OpenVMSiD                    a specific copy of an image, either executable orG                    shareable, which is to be given some set of enhancedeB                    properties. For example, when you issue the SETF                    PASSWORD command, the image SYS$SYSTEM:SETP0.EXE isG                    run. That image needs to have elevated privileges to (                    perform its function.  G                    The other important attribute is /SHARED. This meanslI                    that shareable parts of the image (typically read-onlysJ                    code and data) are loaded into memory only once and areH                    shared among all users on a system. Executable imagesH                    can be installed /SHARED as well as shareable libraryH                    images. (The term "shareable" has dual meanings here,G                    too. See the OpenVMS Programming Concepts Manual fort$                    further details.)  H                    It's important to note that there is no such thing asF                    "installing a shareable image with privileges". TheI                    INSTALL utility will let you do it, but the privilegesEJ                    you specify will be ignored. To have a callable routineF                    run with enhanced privileges that are not availableE                    to its caller, you must construct your routines asoD                    "user-written system services" (UWSS) and installC                    the shareable image with the /PROTECT qualifier.iG                    See the OpenVMS Programming Concepts Manual for more I                    information on user-written system services. Note alsosH                    that in many cases the need to grant privileges to an  J                                                                        5-1 n             0                    System Management Information        G                    image can be replaced with the use of the "Protected I                    Subsystems" feature that grants a rights identifier to I                    an image. See the OpenVMS Guide to System Security for 7                    information on Protected Subsystems.   D           __________________________________________________________7           5.2  Are there any known viruses for OpenVMS?a  E                    Viruses and worms are common on personal computerscB                    because the operating systems involved, such asC                    the Microsoft MS-DOS, Windows 95, Windows 98 and C                    Windows ME variants, do not particularly protect B                    the operating system or the file system againstD                    hostile action by programs. Microsoft Windows NT,G                    Windows 2000 and Windows XP do implement protectionseF                    for specific configurations and do implement memoryE                    protection models, but many users of these systemsuF                    choose to operate with full adminstrator access andG                    thus the available protections are entirely defeatedyF                    and entirely not relevent, and any program that canH                    activate itself or can cause the user to activate theJ                    code can subvert the operating system and take over theJ                    hardware, at which point the malicious code can do mostH                    anything it wishes, including hiding copies of itselfJ                    in other programs or in the file system, redistributingI                    itself via mail, IM, or network connections, or can beTH                    used as a zombie in staging attacks on other systems.  F                    This is less likely with multi-user systems such asD                    OpenVMS, Unix, Linux, MVS and other platforms forI                    various reasons. First, the operating system runs in a7F                    privileged mode in memory that is protected againstD                    modification by normal user programs. Any programD                    cannot simply take over the hardware as it can onF                    operating systems without security and particularlyD                    without memory page protections. Secondly, multi-D                    user systems can be set up so that non-privilegedF                    programs cannot modify system programs and files onH                    disk, and this is normal for most installations. BothJ                    of these protection schemes mean that traditional viralF                    infections don't work on these OSes. Third, typicalF                    applications and configurations tend to prevent theC                    uncontrolled execution of untrusted code as partSF                    of received mail messages or web access; one of the                      5-2               0                    System Management Information        C                    central vulnerabilities of the Microsoft WindowsNF                    platform involves its intentionally easy ability toD                    dynamically (and transparently) activate code andD                    macros that are embedded within mail messages and%                    within data files.   J                    It is possible for OpenVMS and other multi-user systemsH                    to become infected by viruses or worms, but to do so,F                    the program containing the virus must be run from aI                    user account that has amplified privileges. So long asaH                    the system administrator is careful that only trustedD                    applications are run from such accounts (and thisE                    is generally the case) and so long as there are noaE                    OpenVMS system security breaches (due to maliciousoF                    operator activity, OpenVMS errors, or errors withinD                    trusted and privileged product packages) there isG                    no of modifications to the operating system or othert>                    protected files from the virus or the worm.  F                    The FAQ maintainer is aware of a few (and very old)E                    DECnet worms that have affected OpenVMS systems onMG                    DECnet networks ("WANK" was one), but is aware of non?                    OpenVMS viruses that are loose in the field.   C                    To protect against viruses and other attempts at C                    system interference or misuse, please follow the J                    security recommendations in the OpenVMS Guide to SystemE                    Security. Additionally, you will want to keep your F                    OpenVMS ECOs current and you will want to apply allG                    mandatory ECO kits and any security MUPs for OpenVMS.E                    and OpenVMS products, and you will want to keep toaG                    OpenVMS releases with Prior Version Support (PVS) or$E                    with Current Version Support. (This is obviously aoI                    general system maintenance recommendation, in addition.E                    to being a good system security recommendation-newUH                    security features and capabilities are implemented inI                    more recent OpenVMS releases, for instance. Details onmF                    PVS releases are available over in Section 5.10.6.)B                    You may also want to consider optional softwareG                    products which can monitor your system for intrusionbI                    or infection attempts. Computer Associates (CA) offerseF                    various products in this area, as to other vendors.    J                                                                        5-3               0                    System Management Information        H                    Rocksoft offers the Veracity data integrity tool (forG                    info, send mail to demo@rocksoft.com). MD5 tools arelG                    also available; see Section 5.30 for details on MD5.s  C                    Tools to scan OpenVMS file systems for MicrosoftrB                    Windows infections are and have been available,E                    including a commercial package from Sophos , and aiD                    port of the open source Clam Antivirus scanner atE                    http://www.clamav.net/ and with an OpenVMS port ata?                    http://fafner.dyndns.org/~alexey/clamav.zip.   C                    These scanning tools are particularly useful fortH                    systems running Samba or Advanced Server (PATHWORKS),G                    as these servers tend to have a higher population ofoF                    files intended for Microsoft Windows systems users,D                    and as common virus and worm attacks can find andJ                    infect files on the file shares that these products canJ                    provide. These infections do not target OpenVMS itself,H                    though the OpenVMS server (and any other platform andH                    any other server capable of storing files for WindowsE                    systems) can silently host files containing commone0                    Microsoft Windows infections.  D           __________________________________________________________7           5.3  Sources of OpenVMS security information?t  J                    Where can I get information on OpenVMS system security?  6                    o  http://www.hp.com/go/openvms/doc  S                    o  http://www.blacksheepnetworks.com/security/resources/openvms/   D           __________________________________________________________8           5.4  How do I mount an ISO-9660 CD on OpenVMS?  H                    ISO-9660 support was added in the following releases:  &                    o  OpenVMS VAX V6.0  &                    o  OpenVMS AXP V1.5  H                    An add-on ISO-9660 kit was also available for OpenVMSH                    VAX V5.5, V5.5-1, V5.5-2, and V5.5-2H4. This requiresH                    the installation of the F11CD kit from the InfoServerF                    CD, from the Consolidated Distribution CD under theI                    InfoServer area, or the F11CD ECO kit. (Upgrades to V6 7                    and later are strongly recommended.)o                      5-4 i             0                    System Management Information        I                    By default, OpenVMS senses the specific type of media.SG                    If you are working with dual-format media-media thatiG                    uses both the ODS-2 and ISO-9660 formats on the sameoG                    CD-ROM-then MOUNT will first detect and then defaultaH                    to the ODS-2 format. If you wish to override this andE                    explicitly mount the media using ISO-9660, use the                     command:I  L                    $ MOUNT/MEDIA_FORMAT=CDROM  device-name[:] [volume-label]  D                    In most circumstances, you will not need nor will@                    you want to include an explicit /MEDIA_FORMATJ                    specification. For further information, please refer toJ                    the OpenVMS MOUNT Utility Manual. Particularly note theI                    information on the MOUNT /MEDIA_FORMAT and /UNDEFINED_I"                    FAT qualifiers.  D                    The MOUNT /UNDEFINED_FAT qualifier is of interestC                    because ISO-9660 media can be mastered on a wideoC                    variety of operating system platforms, and theseOE                    platforms do not necessarily support the semanticsdI                    needed for files containing predefined record formats..G                    The /UNDEFINED_FAT allows you to specify the defaultMG                    attributes for files accessed from volumes using theE#                    ISO-9660 format.   >                    An example which works for most CD-ROMs is:  V                    $ MOUNT/MEDIA_FORMAT=CDROM/UNDEFINED_FAT=STREAM:2048 DUA0: FREEWARE  E                    This particular MOUNT command forces access to the H                    CD-ROM media using the ISO-9660 volume structure, andG                    the use of the MOUNT /UNDEFINED_FAT qualifier causes$G                    any file whose file attributes are "undefined" to be J                    returned with "stream" attributes with a maximum record                    length 2048.   B                    On OpenVMS, the ISO-9660 format is (internally)G                    considered to be the ODS-3 file structure, while the0H                    High Sierra extensions to the standard are consideredA                    to be the ODS-4 file structure. The Rock RidgesE                    extensions are not currently available on OpenVMS._    J                                                                        5-5               0                    System Management Information        F                    For details on ODS-1 and ODS-2 file specifications,E                    see Kirby McCoy's VMS File System Internals ManualpF                    (published by Digital Press, but potentially out of#                    print), and see:   B                    o  http://pdp-11.trailing-edge.com/www/ods1.txt  B                    o  Look for the Freeware V5.0 directory ODS2 at<                       http://www.hp.com/go/openvms/freeware/  D           __________________________________________________________;           5.5  How do I extract the contents of a PCSI kit?t  J                    A growing number of OpenVMS products are being providedH                    in PCSI (POLYCENTER Software Installation) kits whichI                    are installed using the PRODUCT INSTALL command. These H                    are alternatives to or replacement for VMSINSTAL kitsG                    which were BACKUP savesets. PCSI kits are not BACKUPaI                    savesets and are structured differently from VMSINSTAL                     kits.  C                    If you want to extract product files from a PCSIYG                    kit, create a directory into which the kit should ben:                    expanded and use the following command:  G                    $ PRODUCT COPY prodname /SOURCE=[where-the-kit-is] - F                        /DEST=[destination-directory] /FORMAT=REFERENCE  B                    A PCSI kit file has a file specification of the"                    following form:  6                    DEC-VAXVMS-FORTRAN-V0603-141-1.PCSI  E                    In this example, "FORTRAN" is the "prodname". PCSInC                    will expand the kit files into the directory youSG                    specify and subdirectories beneath such as [SYSEXE],tF                    [SYSLIB], etc., reflecting the eventual destinationC                    of files found there. Most of the actual productmF                    files (images, etc.) will be in the subdirectories.E                    In the top-level directory will be a file with the.J                    file type PCSI$DESCRIPTION that specifies where variousH                    files should go. For more details, see the POLYCENTERG                    Software Installation Developer's Guide for OpenVMS,DI                    which can be found in the OpenVMS documentation on theM<                    Consolidated Online Documentation CD-ROM.                      5-6 T             0                    System Management Information      D           __________________________________________________________9           5.6  Emergency (Conversational) System Startup?s  F                    If you need to perform system management operationsD                    on an OpenVMS system and cannot access the systemB                    through normal means-the password on the SYSTEMA                    username was forgetten and no other privileged F                    usernames are available, or one or more core systemD                    product authorization key (PAK) software licensesE                    are unavailable or expired-then you must perform aE8                    conversational (emergency) bootstrap.  &                    Here are the steps:  G                    1  Halt the system. Exactly how this is done depends D                       on the specific system model: Depending on theI                       model, this can involve pressing the <HALT> button, G                       entering <CTRL/P> on the console, or pressing the 1                       <BREAK> key on the console.   E                    2  At the console prompt, use a console command toeD                       boot into the SYSBOOT utility. (SYSBOOT allowsH                       conversational changes to system parameters.) (TheE                       console syntax for the conversational bootstrap H                       varies by system model and by system architecture-D                       this typically involves specifying a flag withH                       the lowest bit set. See Section 14.3.5 for related,                       details.) For example:  E                       On VAX, use one of the following three commandsoE                       depending on the particular model of VAX systemu                       involved:e                         B/R5:1                       B/1h                       @GENBOO                          On Alpha:u  "                       b -flags 0,1  E                       If your system has a non-zero system root (such G                       as root SYSE, shown here), you will have to use aE<                       console command such as the following:  J                                                                        5-7               0                    System Management Information                               On VAX:                           B/E0000001#                       B/R5:E0000001 C                       @<console media procedure name varies widely>i                         On Alpha:   "                       b -flags e,1  J                       On the IA-64 architecture systems, you can establishG                       and manage an EFI boot alias for a conversational D                       bootstrap as discussed in Section 14.3.5.1 andG                       in Section 14.3.10, or you can use VMS_LOADER.EFI I                       interactively as shown here. Of the core mechanisms G                       discussed in Section 14.3.5.1, the following uses F                       an EFI Shell command to perform a conversationalE                       bootstrap of root SYSE via the partition device G                       fsn:. There are alternative mechanisms available.   <                       fsn:\efi\vms\vms_loader.efi -flags e,1  B                       If your Alpha system has a hardware passwordG                       (various systems support a password that prevents H                       unauthorized access to the console), you will needF                       to know theis password and will need to enter itH                       using the LOGIN or similar command at the console.G                       If you get an "Inv Cmd" error trying to perform a-G                       conversational bootstrap, and you do not have the0E                       hardware console password for the console LOGIN F                       command, you are stuck-you will need to call forF                       hardware service for assistance in resetting theG                       hardware console password. The implementation and H                       the syntax used for the console password mechanism2                       does vary by implementation.  F                    3  Once at the SYSBOOT prompt, request that OpenVMSH                       read the system startup commands directly from theE                       system console, that the window system (if any) G                       not be started, and that OpenVMS not record these H                       particular parameter changes for subsequent system                       reboots:                        5-8 e  -          0                    System Management Information        '                       SET/STARTUP OPA0: )                       SET WINDOW_SYSTEM 0 *                       SET WRITESYSPARAMS 0                       CONTINUE  G                    4  At the $ prompt, the system will now be acceptingeJ                       startup commands directly from the console. Type the1                       following two DCL commands:                          $ SPAWN +                       $ @SYS$SYSTEM:STARTUPf  F                    5  You should now see the dollar ($) prompt of DCL.  I                       The result of these two commands will be the normaleD                       system startup, but you will be left logged inF                       on the console, running under a fully privilegedI                       username. Without the use of the SPAWN command, you E                       would be logged out when the startup completes.   E                       Perform the task(s) required, such as resetting F                       the password on the SYSTEM username as describedI                       in Section 5.6.1 or registering one or more license G                       product authorization keys (PAKs) as described ine$                       Section 5.6.2.  G                    6  Once you log out of this session, the system williH                       complete the startup and can be used normally. YouF                       can choose to reboot the system, but that is not                        necessary.  C                    Some system managers will suggest a method usingnD                    the UAFALTERNATE system parameter rather than theD                    SET/STARTUP OPA0: command shown. This approach isH                    not always available and is accordingly less commonlyH                    recommended, as there can easily be an alternate userD                    authorization database (SYS$SYSTEM:SYSUAFALT.DAT)G                    configured on the system. With a system manager thatyF                    has configured an alternate SYSUAFALT.DAT file, theF                    UAFALTERNATE method will fail-well, assuming you doH                    not know the password of a privileged username stored3                    within SYSUAFALT.DAT, of course.     J                                                                        5-9               0                    System Management Information        G                    The UAFALTERNATE system parameter is used to triggerpG                    what is sometimes known as the console backdoor. TherH                    OPA0: system console is critical to system operationsF                    and system security, and will allow access when theF                    SYSUAF system authorization database is unavailableG                    or corrupted, when core product license PAKs are notdI                    registered, expired or disabled (NOLICENSE errors), orvI                    in various other cases of system failures. All this isrH                    in addition to the role of the console in the displayD                    of certain system-critical event messages. AccessG                    to the OPA0: console has a security exposure that istF                    equivalent to direct access to the system hardware.  C                    When LOGINOUT detects an error (such as a SYSUAFmC                    corruption, by a missing SYSUAF, missing productyF                    licenses, or other trigger), it will prevent accessF                    to the OpenVMS system from all terminals except theC                    system console. The OPA0: system console will benD                    allowed access, and the resulting process will beF                    fully privileged. Resetting the UAFALTERNATE systemI                    parameter-in the absence of an alternate SYSUAF systemmI                    authorization database-will cause the console backdoor E                    to be opened simply because LOGINOUT cannot locateeC                    SYS$SYSTEM:SYSUAFALT.DAT. When the authorizationbE                    database cannot be located, access will be grantedt)                    from the console only.   C                    For further information on emergency startup andt@                    shutdown, as well as for the official OpenVMSJ                    documentation on how to change the SYSTEM password fromF                    the console in an emergency, please see the OpenVMSG                    System Manager's Manual in the OpenVMS documentation                     set.   D                    For information and recommendations on setting upE                    OpenVMS system security, please see the NCSC ClassTF                    C2 appendix of the Guide to OpenVMS System SecurityA                    manual, also in the OpenVMS documentation set.d  J                    You can also use the conversational bootstrap techniqueG                    shown earlier (the steps until SET/STARTUP) to alteroE                    various system parameters, as well. At the SYSBOOTa?                    prompt, you can enter new parameters values:u                      5-10h r  i          0                    System Management Information        %                    SHOW MAXPROCESSCNT                     SET . 64                     CONTINUE   D                    The <.> is a shorthand notation used for the last@                    parameter examined within SYSGEN and SYSBOOT.  '           _____________________________,D           5.6.1  I've forgotten the SYSTEM password - what can I do?  D                    If you have forgotten or do not have the password@                    for the SYSTEM username, you must perform theH                    conversational bootstrap as described in Section 5.6,F                    and must enter the following commands once you have1                    reached the dollar ($) prompt:   S                    $ SET DEFAULT SYS$SYSTEM:  ! or wherever your SYSUAF.DAT resides -                    $ RUN SYS$SYSTEM:AUTHORIZEa6                    MODIFY SYSTEM /PASSWORD=newpassword                    EXIT}  @                    You have now reset the password on the SYSTEM                    username.  '           _____________________________SB           5.6.2  My product licenses have expired - what can I do?  G                    If you have a system with no licenses for OpenVMS or I                    for OpenVMS users and thus cannot log into the OpenVMSeF                    system normally, you should be able to log into theF                    console serial terminal-this is the terminal deviceE                    known as OPA0:-and perform the commands necessary.e  I                    For systems that are not configured with an accessable F                    console serial terminal-as can be the case with howB                    some DECwindows workstations are configured-youF                    must log in over the network or from a local serialB                    connection. If you cannot log in over a networkE                    connection (SET HOST, telnet, etc) or from another E                    local serial terminal connection, you will have tosI                    halt the system and perform a conversational bootstrapaC                    as described in Section 5.6. You must then enterUE                    licensing-related commands once the conversationalh?                    bootstrap has reached the dollar ($) prompt.i  J                                                                       5-11 a  n          0                    System Management Information        F                    Use the following DCL command to invoke a menu thatJ                    allows you to manage and to register new or replacement                     license PAKs:  +                    $ @SYS$UPDATE:VMSLICENSE   J                    You have now registered the license PAKs. Direct use ofH                    the DCL commands LICENSE and SHOW LICENSE and such is,                    also obviously available.  B                    If you wish to connect a serial console on yourG                    DECwindows workstation, please see Section 14.3.3.3, D                    Section 14.3.6, Section 11.10, and Section 14.17.  H                    For information on troubleshooting DECwindows, please$                    see Section 11.5.  D           __________________________________________________________B           5.7  How do I change the node name of an OpenVMS System?  B                    The first step is to get a BACKUP of the systemE                    disk before making any changes-use the system disk H                    backup procedures as documented in the OpenVMS SystemG                    Management Manual, making sure to use the procedures @                    and commands appropriate for the system disk.  H                    Changing the node name involves a number of steps-theJ                    node name tends to be imbedded in a number of different0                    data files around the system.  G                    o  Update the SCSNODE in MODPARAMS.DAT, and then run D                       AUTOGEN as far as the SETPARAMS phase. (Do not"                       reboot yet.)  D                    o  Modify the DECnet node name. (NETCONFIG is theD                       DECnet Phase IV tool, and NET$CONFIGURE is the(                       DECnet-Plus tool.)  H                    o  Modify the host node name on the various queues inF                       the queue database. (each queue has a host name,I                       and it defaults to the SCS node name of the queue'syE                       host system. See the command INIT/QUEUE/ON=nodetE                       for information.) Site-specific startup commandcE                       procedures can explicitly specify the (local or G                       even the current) node on the /ON parameter in an 3                       INIT/QUEUE/START/ON= command.w                      5-12P e  r          0                    System Management Information        C                    o  Modify the node name saved in any application I                       databases, or any local node-conditional operationsfG                       present in the site-specific system startup, etc. H                       (SEARCH for the node name, specifying all types of                       files.)i  I                    o  Use the AUTHORIZE utility command RENAME/IDENTIFIERmC                       to rename the SYS$NODE_oldnodename rightslist_D                       identifier to match the new node name. (Do notE                       change the binary value of this identifier, andT4                       do not delete the identifier.)  F                       If you have erroneously deleted or duplicate theG                       identifier, you can locate existing references to H                       the binary identifier value using the Freeware DFUG                       package, and specifically the commands SEARCH/ACE I                       and /OWNER. You must (re)create the correctly-named E                       identifier using the binary value that is oftensG                       stored in various Access Control List Entry (ACE)hH                       structures and object owner fields associated withF                       files and objects present in the OpenVMS system.  G                    o  Reset any license PAKs that are restricted to the_9                       old node name to the new node name.   J                    o  If the node name is part of a disk volume label, see#                       Section 5.13.   F                    o  Reboot the node or-if in a VMScluster-reboot theG                       whole VMScluster. (This tends to catch any errorss#                       immediately.)   H                    o  Modify the IP node name. (The TCP/IP Services toolF                       is UCX$CONFIG prior to V5.0, and is TCPIP$CONFIGC                       in V5.0 and later releases.) Note that TCP/IP C                       Services ties the IP host name to the current G                       SCSNODE value within its UCX$CONFIGURATION.DAT or G                       TCPIP$CONFIGURATION.DAT database. Thus if SCSNODE G                       is changed, the IP host name reconfiguration mustsG                       occur, and the required reconfiguration can occurpD                       only after a system reboot. Accordingly, it isC                       best to perform the TCP/IP Services host namer<                       reconfiguration step after the reboot.  J                                                                       5-13 u  i          0                    System Management Information        H                    There are likely a few other areas where the nodenameJ                    will be stored. Local procedures and data files are oneG                    such example, and various sites will have the systemEI                    name loaded in the operator control panel via the OCP_aI                    TEXT console environment variable available at the SRMa;                    prompt on some Alpha systems is another.s  F                    If the system is configured in a VMScluster and youG                    change either the SCSNODE or the SCSSYSTEMID-but notTF                    both values-then you will have to reboot the entireD                    VMScluster. (The VMScluster remembers the mappingC                    between these two values, and will assume that aeD                    configuration problem has occured if a mismatchedE                    pair appears, and will refuse to let a node with aS8                    mismatched pair join the VMScluster.)  G                    To calculate the correct SCSSYSTEMID value, multiplyCC                    the DECnet Phase IV area number by 1024, and addtD                    the DECnet Phase IV node number. For example, theI                    SCSSYSTEMID value for a DECnet node with address 19.22 7                    is 19478. ((19 * 1024) + 22 = 19478)   E                    This may well have missed one or two configuration I                    tools (or more!) that are needed at your site-the nodeSJ                    name tends to get stored all over the place, in layered5                    products, and in local software...   >                    Also see Section 15.6.3 and Section 15.6.4.  D           __________________________________________________________C           5.8  Why doesn't OpenVMS see the new memory I just added?   F                    When adding memory to an OpenVMS system, you shouldH                    check for an existing definition of the PHYSICALPAGESC                    (OpenVMS VAX) or PHYSICAL_MEMORY (OpenVMS Alpha)sF                    parameter in the SYS$SYSTEM:MODPARAMS.DAT parameterH                    database, use a text editor to reset the value in theF                    file to the new correct value as required, and then1                    perform the following command:   @                    $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT FEEDBACK  A                    This AUTOGEN command will reset various system F                    parameters based on recent system usage (FEEDBACK),D                    and it will reset the value for the PHYSICALPAGESF                    parameter to the new value. It will also reboot the"                    OpenVMS system.                      5-14e e             0                    System Management Information        H                    PHYSICALPAGES and PHYSICAL_MEMORY can also be used toH                    deliberately lower the amount of memory available forF                    use by OpenVMS. This ability can be useful in a fewH                    specific circumstances, such as testing the behaviourC                    of an application in a system environment with aoH                    particular (lower) amount of system memory available.  I                    PHYSICALPAGES and PHYSICAL_MEMORY can be set to -1 (onfJ                    OpenVMS Alpha) or (better and simpler) the entry can beH                    removed from the MODPARAMS.DAT file, to indicate that7                    all available memory should be used.o  D           __________________________________________________________C           5.9  How do I change the text in a user's UIC identifier?t  <                    The text translations of the numeric UserE                    Identification Code (UIC) are based on identifiers F                    present in the OpenVMS rightslist. Documentation onH                    this area is included in the _Guide to OpenVMS System$                    Security_ manual.  E                    To control the identifiers shown for a user's UIC, G                    you use AUTHORIZE. Each user has an associated group J                    identifier, and an identifier specific to the user. And6                    each user should have a unique UIC.  G                    To alter the text of a user or group identifier, use $                    commands such as:  -                    $ RUN SYS$SYSTEM:AUTHORIZE :                    UAF> rename/ident oldgroupid newgroupid9                    UAF> rename/ident olduserid  newuseridt  H                    If you should find yourself missing an identifier forH                    a particular user, you can add one for the user's UIC+                    using a command such as:a  B                    UAF> add/ident/value=uic=[group,user] newuserid  D                    The UIC user identifier text is assigned when theH                    username is created, and is the text of the username.F                    The UIC group group identifier is assigned when theF                    first username is created in the UIC group, and theF                    text is based on the account name specified for theE                    first user created in the group. The value of thisoH                    identifier is [groupnumber, 177777]. To add a missing@                    group identifier, use an asterisk as follows:  J                                                                       5-15 k  s          0                    System Management Information        @                    UAF> add/ident/value=uic=[group,*] newgroupid  I                    You may find cases where an identifier is missing fromdF                    time to time, as there are cases where the creationE                    of a UIC group name identifier might conflict with C                    an existing username, or a user identifier mighteI                    conflict with an existing group identifier. When thesesI                    conflicts arise, the AUTHORIZE utility will not create H                    the conflicting group and/or user identifier when the'                    username is created.l  I                    You can can add and remove user-specified identifiers,oC                    but you should avoid changing the numeric valuesnG                    associated with any existing identifiers. You shoulddF                    also avoid reusing UICs or identifiers when you addG                    new users, as any existing identifiers that might bepJ                    present on objects in the system from the old user willH                    grant the same access to the new user. Please see the/                    security manual for details.r  D           __________________________________________________________;           5.10__What_are_the_OpenVMS_version upgrade paths?   9           5.10.1  OpenVMS Alpha Upgrade (or Update) Paths)  1                                              Notet  D                       Upgrade path information here has occasionallyC                       been found to be wrong. Information here doesAG                       not reflect cluster rolling upgrade requirements; D                       see Section 5.10.4 for related rolling upgradeC                       information; versions permissible for rollingSE                       upgrades can be and often are more constrained.sB                       When upgrade information here conflicts withD                       the official documentation, please assume thatD                       the information here is wrong. Corrections and;                       updates to this material are welcome.                                   5-16e e  v          0                    System Management Information                            From V1.0, /                        you can upgrade to V1.5.t*                    From V1.5, or V1.5-1H1,/                        you can upgrade to V6.1.h                    From V6.1,//                        you can upgrade to V6.2. &                    From V6.1, or V6.2,/                        you can upgrade to V7.0.S<                    From V6.1, V6.2, V6.2-1H(1,2,3), or V7.0,/                        you can upgrade to V7.1.                     From V6.2,iI                        you can update to V6.2-1H1, V6.2-1H2, or V6.2-1H3.kJ                    From V6.2, V6.2-1H(1,2,3), V7.1, V7.1-1H(1,2), or V7.2,!                        to V7.2-1.p*                    From V6.2, ... or V7.2,+                        to V7.2-1H1, to 7.3.nA                    From V7.1, you can update to V7.1-1H(1,2), ...r+                        to V7.2-1H1, to 7.3. A                    From 7.2, 7.2-1, 7.2-1H1, 7.2-2, 7.3 or 7.3-1,o0                        you can upgrade to V7.3-2C                    From V7.3, V7.2-2, V7.2-1H1, V7.2-1, and V7.1-2,_0                        you can upgrade to V7.3-1                    From V7.3-1, <                        you can upgrade to V7.3-2 or to V8.2.)                    From V7.3-1 or V7.3-2,e/                        you can upgrade to V8.2.k'                    From V7.3-2 or V8.2,v/                        you can upgrade to V8.3._  G                    Some typical OpenVMS Alpha upgrade (or update) paths                     are:                           J                                                                       5-17               0                    System Management Information        I                    V1.0 -> V1.5 -> V6.1 -> (V6.2, V7.0, V7.1, V7.2, V7.3)-E                    V1.5-1H1 -> V6.1 -> (V6.2, V7.0, V7.1, V7.2, V7.3)t#                    V6.2 -> V6.2-1H3v!                    V6.2 -> V7.2-1                     V6.2 -> V7.3r)                    V6.2-1H(1,2,3) -> V7.1r+                    V6.2-1H(1,2,3) -> V7.2-1 9                    V6.2 through 7.1-1H2 inclusive -> V7.3 !                    V7.1 -> V7.1-2 !                    V7.1 -> V7.2-1I)                    V7.1-1H(1,2) -> V7.1-2e)                    V7.1-1H(1,2) -> V7.2-1m#                    V7.1-2 -> V7.3-1 #                    V7.2 -> V7.2-1H1t)                    V7.2 -> V7.3 -> V7.3-12+                    V7.2-1 -> (V7.3, V7.3-1) 3                    V7.2-2 -> (V7.3, V7.3-1, V7.3-2) +                    V7.3 -> (V7.3-1, V7.3-2)m+                    V7.3-1 -> (V7.3-2, V8.2) )                    V7.3-2 -> (V8.2, V8.3)   H                    Note that OpenVMS Alpha V7.0 does not include supportH                    for hardware and/or configurations first supported inJ                    OpenVMS Alpha V6.2-1H1, V6.2-1H2, or V6.2-1H3; one must;                    upgrade to OpenVMS Alpha V7.1, or later.s  C                    One cannot update directly to a V6.2-1Hx Limited G                    Hardware Release (LHR) from any release prior to the D                    baseline V6.2 release. The same prohibition holdsC                    for performing updates directly to V7.1-1Hx from_G                    any release prior to V7.1-this is not supported, andaF                    does not produce the expected results. The LHR kitsG                    can, however, be directly booted and can be directlyuI                    installed, without regard to any operating system thati7                    might be present on the target disk.A  I                    Users of OpenVMS Alpha V7.1-1H1, V7.1-1H2, V7.2-1H1 or G                    other hardware are encouraged to upgrade to the next H                    available non-hardware-release, and should preferablyI                    upgrade to the current or to a supported OpenVMS AlphaA                    release.                           5-18  e  t          0                    System Management Information        D                    OpenVMS Alpha updates for LHRs (through V7.1-1Hx)E                    require the use of VMSINSTAL for the update. These J                    LHR releases use PCSI for the installation, but not forI                    the update. Non-LHR releases use PCSI for installs andO                    upgrades.  C                    OpenVMS Alpha V7.1-2 and later use PCSI for LHRsrC                    and for OpenVMS upgrades and for all OpenVMS ECOsG                    kit installations; V7.1-2 and later use upgrades and.H                    not updates. VMSINSTAL OpenVMS ECO kits (updates) areG                    not used on OpenVMS Alpha V7.1-2 and later; prior to I                    V7.1-2, VMSINSTAL-based ECO (update) kits are used fort                    OpenVMS.   '           _____________________________i+           5.10.2  OpenVMS I64 Upgrade Pathsr  1                                              Note   D                       Upgrade path information here has occasionallyC                       been found to be wrong. Information here doesrG                       not reflect cluster rolling upgrade requirements;rD                       see Section 5.10.4 for related rolling upgradeC                       information; versions permissible for rolling_E                       upgrades can be and often are more constrained.CB                       When upgrade information here conflicts withD                       the official documentation, please assume thatD                       the information here is wrong. Corrections and;                       updates to this material are welcome.i                      From V8.2,A8                        you can upgrade to V8.2-1 or V8.3                    From V8.2-1, .                        you can upgrade to V8.3  J                    Some typical OpenVMS I64 upgrade (or update) paths are:  )                    V8.2 -> V8.2-1 -> V8.3   D                    OpenVMS I64 V8.2 is the first production release.D                    OpenVMS I64 V8.0 and V8.1 were intended for earlyH                    adopters of OpenVMS on Integrity servers, and are not8                    considered to be production releases.  J                                                                       5-19               0                    System Management Information        G                    To utilize OpenVMS I64 V8.2, you must perform a fulleE                    installation of V8.2. No supported upgrade path torH                    V8.2 is available from previous releases; there is noF                    upgrade from OpenVMS I64 E8.2, nor from the earlier)                    V8.1 or V8.0 releases.h  '           _____________________________ 3           5.10.3  OpenVMS VAX Release Upgrade Pathst  1                                              Note   D                       Upgrade path information here has occasionallyC                       been found to be wrong. Information here does G                       not reflect cluster rolling upgrade requirements;nD                       see Section 5.10.4 for related rolling upgradeC                       information; versions permissible for rollingeE                       upgrades can be and often are more constrained. B                       When upgrade information here conflicts withD                       the official documentation, please assume thatD                       the information here is wrong. Corrections and;                       updates to this material are welcome.   O                    From V5.0 through V5.4-3 inclusive, one can upgrade to V5.5.tM                    From V5.5, V5.5-1, or V5.5-2HW, one can upgrade to V5.5-2. I                    From V5.5, V5.5-1, or V5.5-2, one can upgrade to V6.0.bK                    From V5.5-2, V5.5-2H4, or V6.0, one can upgrade to V6.1.(?                    From V6.0, or V6.1, one can upgrade to V6.2.i?                    From V6.1, or V6.2, one can upgrade to V7.0.eE                    From V6.1, V6.2, or V7.0, one can upgrade to V7.1. R                    From V6.1, one can upgrade to V7.3 (with VAXBACK ECO for V6.1).  >                    Some typical OpenVMS VAX upgrade paths are:  E                    V5.x -> V5.5 -> V6.0 -> V6.2 -> (V7.1, V7.2, V7.3) %                    V5.5-2HW -> V5.5-2nG                    V5.5-2, or V5.5-2H4 -> V6.1 -> (V6.2, V7.0, or V7.1) @                    V6.1 -> V6.1 with VAXBACK ECO -> (V7.2, V7.3)                    V6.2 -> V7.2o                    V6.2 -> V7.3B  J                    Note that OpenVMS VAX V6.0 does not include support forH                    hardware and/or configurations first added in OpenVMSF                    VAX V5.5-2H4, one must upgrade to OpenVMS VAX V6.1.  J                    Note that OpenVMS VAX V5.5-2HW is a pre-release versionI                    of V5.5-2. Any system running it should be upgraded to $                    V5.5-2, or later.                      5-20  n  X          0                    System Management Information        H                    If you attempt a direct upgrade from OpenVMS VAX V6.1D                    to V7.2 or later without having first applied theH                    VAXBACK ECO kit to your V6.1 system, you will receive$                    an error message:  G                    %BACKUP-E-INVRECTYP, invalid record type in save set   C                    and the upgrade will fail. Acquire and apply the I                    VAXBACK ECO kit for OpenVMS VAX V6.1. OpenVMS VAX V6.2 H                    and later do not require an application of an ECO for0                    an upgrade to V7.2 and later.  '           _____________________________ 7           5.10.4  OpenVMS Cluster Rolling Upgrade Paths5  F                    Rolling Upgrades permit the OpenVMS Cluster and theD                    applications to remain available while individualG                    systems are being upgraded to a new OpenVMS release.u  B                    Rolling Upgrades require multiple system disks.  ?                    OpenVMS Cluster Rolling Upgrades for OpenVMS @                    Alpha, OpenVMS I64 and OpenVMS VAX may (will)D                    have architecture-specific, or additional upgradeG                    requirements or prerequisites, and have requirementscI                    around which versions and architectures of OpenVMS canaH                    coexist within a OpenVMS Cluster than what are listed                    here.  G                    For specific details on Rolling Upgrades, please see F                    the OpenVMS Upgrade and Installation Manual for theG                    particular release, and the OpenVMS Software Product C                    Descriptions for OpenVMS and for OpenVMS Cluster                     software:  9                    o  http://h18000.www1.hp.com/info/spd/o  H                       OpenVMS typically uses SPD 25.01.xx, SPD 41.87.xx,'                       and SPD 82.35.xx.l  F                    for further details on the Rolling Upgrade, and for'                    support information.b    J                                                                       5-21               0                    System Management Information      '           _____________________________ 1           5.10.5  OpenVMS VAX Manual Organizationt  F                    The documentation for older releases of OpenVMS VAXF                    was comprised of various platform-specific manuals,F                    manuals that include instructions that are specificD                    to installing and upgrading on the particular VAXB                    platform. These older manuals can be useful forD                    learning platform- or console-specific operationsE                    or requirements for the particular (and older) VAX                     platform.  H                    There is far less console command syntax, and consoleI                    storage media variability, among the more recent AlphaaH                    and Integrity processors. The newer platform operatorD                    and management interfaces are far more consistent-                    across the platform lines.   '           _____________________________sA           5.10.6  OpenVMS Product Version and Support Informations  E                    For information on Prior Version Support (PVS) and C                    Mature Product Support (including information on D                    support end dates for OpenVMS and various layeredC                    products), please see the support resources linkhH                    available at the main OpenVMS website or the services@                    links available at the main services website:  3                    o  http://www.hp.com/go/openvms/   3                    o  http://www.hp.com/go/serviceso  H                    And see the following links, with the caveat that theC                    direct "/hps" links shown here may become stale:n  :                    o  http://www.hp.com/hps/os/os_pvs.html  ;                    o  http://www.hp.com/hps/os/os_ovms.htmlr  I                    For information on the supported and required versionsAH                    of layered products, and the minimum required layeredJ                    product versions for various configurations, please seeF                    the Software Rollout Report (SWROLL), available at:  B                    o  http://h71000.www7.hp.com/openvms/os/swroll/  I                    For additional related information, see Section 2.6.1.t                      5-22                0                    System Management Information        E                    For information on the release history of OpenVMS, E                    including information on the code names of various 3                    releases and the major features:s  G                    o  http://www.openvms.compaq.com/openvms/os/openvms- *                       release-history.html  G                    Additional release history information, as well as aSH                    variety of other trivia, is available in the VAX 20th$                    anniversary book:  L                    o  http://www.openvms.compaq.com/openvms/20th/vmsbook.pdf  '           _____________________________ ;           5.10.7  OpenVMS Alpha and I64 Upgrade Terminology   C                    OpenVMS Alpha and OpenVMS I64 use the POLYCENTERnJ                    Software Product Install Utility, occasionly refered toG                    as SPIU and rather more commonly known as PCSI. PCSIrI                    is a component of the OpenVMS operating system, and istG                    available on OpenVMS VAX, OpenVMS Alpha, and OpenVMSt                    I64.S  D                    The following terms apply to OpenVMS Alpha and toE                    OpenVMS I64 Upgrades and Installations using PCSI:r  J                    o  UPDATE: Typically used for Limited Hardware ReleasesF                       (LHR) releases. Performed via VMSINSTAL. AppliesG                       only to the OpenVMS release that the LHR is based J                       on, or to an intermediate LHR. (eg: V7.1-1H2 appliesD                       only to V7.1-1H1 and to V7.1, not to any otherE                       releases.) LHRs within a series are cumulative, H                       containing all files and features of previous LHRs)                       in the same series.c  E                       VMSINSTAL-based Updates and VMSINSTAL-based ECOsG                       kits are not generally used to upgrade OpenVMS on I                       releases of OpenVMS Alpha V7.1-2 and later, nor are H                       thse used on OpenVMS I64; only PCSI-based UpgradesH                       and Installs are used. VMSINSTAL remains availableI                       for other uses and other products; for upgrades and J                       installations of products other than OpenVMS itself.    J                                                                       5-23 S  E          0                    System Management Information        I                    o  UPGRADE: Performed via PCSI. Upgrades can typicallyoE                       be applied directly to a release-specific range F                       of earlier OpenVMS releases. The product releaseI                       documentation specifies the prior OpenVMS releases;rA                       if your release is not one of the specifiedtD                       releases, you will have to perform one or moreG                       additional upgrades (through intermediate OpenVMSaJ                       releases) to reach one of the prerequisite releases.  H                    o  INSTALL: Performed via PCSI. With an installation,D                       no existing version of the operating system isI                       assumed present, nor are any files from any copy ofvJ                       the operating system might be present preserved, andJ                       the entire contents of the target disk are destroyed0                       via a disk initialization.  E                    o  PRESERVE: Performed via PCSI. Otherwise similar D                       to an installation, this option skips the diskE                       reinitialization. User files on the target disk H                       are preserved. Any existing operating system files7                       on the target disk are clobbered.e  I                    o  LHR: Limited Hardware Release. LHRs are specific to,J                       and are targeted at new hardware configurations, andJ                       are not shipped to customers with support contracts.H                       At least one LHR kit must be specifically acquiredE                       when purchasing new hardware, new hardware that F                       is not (yet) supported by any mainline (non-LHR)F                       release. LHRs have an "H" in the OpenVMS version>                       string, indicating a "Hardware" release.  J                       You will not generally want to continue using an LHRI                       once a subsequent OpenVMS release is available; you G                       will want to upgrade off the LHR at your earliest "                       convenience.  J                    For minimum OpenVMS versions for various platforms, see                     Section 2.12.                                5-24                0                    System Management Information      D           __________________________________________________________J           5.11  Why do I have a negative number in the pagefile reservable                 pages?  C                    Seeing a negative number in the reservable pagessH                    portion of the SHOW MEMORY/FULL command can be normalF                    and expected, and is (even) documented behaviour. AF                    pagefile with a negative number of reservable pagesI                    is overcommitted, which is generally goodness assumingoI                    that every process with reserved pages does not try tolH                    occupy all of the reserved pagefile space at the same                    time.  E                    To understand how the pagefile reservation processaJ                    works, think about how a traditional bank operates whenI                    accepting customer deposits and making loans. It's the I                    same idea with the pagefile space. There is less money J                    in the bank vault than the total deposits, because muchF                    of the money has been loaned out to other customersG                    of the bank. And the behaviour parallels that of the I                    pagefile down to the problems that a "run on the bank" G                    can cause for banking customers. (Though there is no C                    deposit insurance available for pagefile users.)f  D                    If all of the running applications try to use theJ                    reserved space, the system manager will need to enlargeH                    the pagefile or add one or more additional pagefules.  >                    To determine if the pagefile is excessivelyD                    overcommitted, watch for "double overcommitment"-F                    when the reservable space approaches the negatationB                    of the available total space-and watch that theG                    total amount of free space available in the pagefilenJ                    remains adequate. If either of these situations arises,;                    additional pagefile storage is required.-  H                    Additional pagefile information: Additional pagefilesF                    can typically be created and connected on a runningJ                    OpenVMS system. New processes and new applications willJ                    tend to use the new pagefile, and existing applicationsH                    can be restarted to migrate out of the more congestedI                    pagefiles. Pagefiles are generally named PAGEFILE.SYS, E                    and multiple pagefiles are generally configured on G                    separate disk spindles to spread the paging I/O load C                    across the available disk storage. When multipleeI                    pagefiles are present on recent OpenVMS versions, eachE  J                                                                       5-25               0                    System Management Information        I                    pagefile file should be configured to be approximately >                    the same total size as the other pagefiles.  D                    For additional information on pagefile operationsB                    and related commands, see the system managementD                    and performance management manuals in the OpenVMS%                    documentation set.o  F                    With OpenVMS V7.3 and later, the displays have beenB                    changed and these negative values are no longer                    visible.f  D           __________________________________________________________B           5.12  Do I have to update layered products when updating                 OpenVMS?  G                    The Software Public Rollout Reports for OpenVMS list E                    the current and future availability of HP software E                    products shipping on the OpenVMS Software Products H                    Library kits (CDROM consolidations) for OpenVMS AlphaI                    and/or OpenVMS VAX. Specifically, the required minimumh;                    versions for product support are listed.n  D                    Comprehensive Public Rollout Information, listingJ                    previous product versions as well as currently shippingE                    versions, has been compiled into a separate set ofnF                    reports. The product information is grouped to show,                    Operating System support.  F                    You may or may not be able to use older versions ofH                    local applications, third-party products, and variousH                    HP OpenVMS layered products with more recent versionsF                    of OpenVMS. User-mode code is expected to be upwardG                    compatible. Code executing in a privileged processoriE                    mode-typically either executive or kernel mode-may D                    or may not be compatible with more recent OpenVMS                    versions.  F                    These Software Rollout (SWROLL) Reports are updated)                    regularly. Please see:o  B                    o  http://h71000.www7.hp.com/openvms/os/swroll/  >                    For related information, see Section 2.6.1.                      5-26                0                    System Management Information      D           __________________________________________________________;           5.13  How do I change the volume label of a disk?V  I                    Dismount the disk, and mount it privately. If the diskeJ                    is mounted by more than one node in an OpenVMS Cluster,G                    dismount it from all other nodes. If this disk is anOJ                    OpenVMS system disk, shut down all other nodes that are/                    bootstrapped from this disk.   I                    Issue the SET VOLUME/LABEL command, specifying the new                     label.   F                    On OpenVMS V6.0 and later, issue the following PCSIG                    command to reset the label information stored withinoJ                    the PCSI database to reflect the new disk volume label:  =                    $ PRODUCT REGISTER VOLUME old-label devicer  I                    Locate any references in the system startup (typicallyhH                    including the disk MOUNT commands) and any DISK$labelB                    references in application files, and change the,                    references appropriately.  B                    If this is a system disk (for the host or for aF                    satellite), also check the DECnet MOP or LANCP bootJ                    database, as well as any references to the disk created*                    by CLUSTER_CONFIG*.COM.  H                    If Compaq Analyze is in use, check the system startupB                    procedures for the Compaq Analyze tool. CertainG                    versions of Compaq Analyze will record specific disk ?                    volume labels within the startup procedures.e  2                    Remount the disk appropriately.  D           __________________________________________________________4           5.14  How can I set up a shared directory?  G                    To set up a shared directory-where all files createdED                    in the directory are accessible to the members ofI                    specified group of users-you can use an access controlo0                    list (ACL) and an identifier.  D                    The following also shows how to set up a resourceF                    identifier, which further allows the disk resourcesH                    to be charged to the specified identifier rather thanF                    each individual user. (If you don't want this, thenH                    omit the attributes option on the identifier creationG                    and omit the entry added in the disk quota database.n  J                                                                       5-27               0                    System Management Information        A                    Add an identifier using the AUTHORIZE utility:u  D                    ADD/IDENTIFER/ATTRIBUTES=RESOURCE groupidentifier  G                    Grant the identifier to each user in the group using                     AUTHORIZE:   <                    GRANT/IDENTIFIER groupidentifier username  I                    If disk quotas are in use, add an entry via SYSMAN fort                    each disk:d  2                    DISKQUOTA ADD groupidentifier -<                      /PERMQUOTA=pq/OVERDRAFT=od/DEVICE=ddcu:  I                    Set the shared directory to have an ACL similar to thesG                    following using the SET SECURITY (V6.0 and later) orA<                    SET ACL (versions prior to V6.0) command:  9                    (DEFAULT_PROTECTION,S:RWED,O:RWED,G,W)I@                    (IDENTIFIER=groupidentifier,OPTIONS=DEFAULT,-6                      ACCESS=READ+WRITE+EXECUTE+DELETE)1                    (IDENTIFIER=groupidentifier, - 6                      ACCESS=READ+WRITE+EXECUTE+DELETE)<                    (CREATOR,ACCESS=READ+WRITE+ACCESS+DELETE)  H                    If there are files already resident in the directory,I                    set their protections similarly. (The OPTIONS=DEFAULT,t@                    DEFAULT_PROTECTION, and CREATOR ACEs apply to                     directories.)  C                    The default protection mask is used to establish G                    the default file protection mask, this mask does not J                    prevent the users holding the specified groupidentifierJ                    from accessing the file(s), as they can access the fileF                    via the explicit identifier granting access that is&                    present in the ACL.  D                    For further information, see the OpenVMS Guide toG                    System Security Manual, specifically the sections on B                    ACLs and identifiers, and resource identifiers.                          5-28  n             0                    System Management Information      D           __________________________________________________________@           5.15  Why do I get extra blank pages on my HP Printer?  H                    For information on configuring telnet print symbiont,I                    on device control libraries such as SYSDEVCTL.TLB, andeJ                    for ways of dealing with the extra blank pages that canG                    arise on various HP printers, please see the OpenVMS H                    Ask The Wizard area, starting particularly with topic                    (1020):  H                    o  http://www.hp.com/go/openvms/wizard/ (retired; use"                       ITRC forums)  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the available F                    ATW Wizard.zip archive, please see Section 3.8. ATWF                    has been superceded (for new questions) by the ITRCD                    discussion forums; the area remains available for                    reference.e  D                    There are a variety of discussions of this and ofF                    related printing topics in the Ask The Wizard area,/                    in addition to topic (1020).c  )                    Also see Section 5.34.   D           __________________________________________________________F           5.16  Drivers and Configuration of New Graphics Controllers?  ?                    This section contains information on various G                    graphics controllers supported by OpenVMS Alpha, and F                    specifically information on where and how to obtainF                    device drivers for specific early OpenVMS releases-E                    device drivers for controllers are integrated into B                    and shipped with OpenVMS Alpha, but versions ofH                    these device drivers are sometimes made available for5                    specific earlier OpenVMS releases.   '           _____________________________ )           5.16.1  The ELSA GLoria Synergy   I                    On OpenVMS Alpha V7.1-2, V7.2, and V7.2-1, acquire the F                    appropriate GRAPHICS PCSI kit, and all prerequisite$                    OpenVMS ECO kits:  4                    o  VMS712_GRAPHICS-V0300 or later  3                    o  VMS72_GRAPHICS-V0100 or later   J                                                                       5-29 n  d          0                    System Management Information        4                    o  VMS712_GRAPHICS-V0300 or later  J                    The ELSA GLoria Synergy is the PBXGK-BB; the PowerStormF                    3D10T. Please ensure you have the most current ECOsE                    for this and other graphics controllers installed;rG                    check for and install the current GRAPHICS kit. (See_H                    Section 4.3.2 for some unexpectedly related details.)  H                    On OpenVMS Alpha V7.2-1, the files necessary for thisF                    graphics controller are located in the distribution$                    CD-ROM directory:  ,                    DISK$ALPHA0721:[ELSA.KIT]  A                    Also check for any available (later) ECO kits.   C                    An earlier kit (ALP4D20T01_071) (for V7.1, V7.1-oF                    1H1, and V7.1-1H2) was once available, but has beenC                    superceded and is not recommended. Use of V7.1-2nF                    or later (and use of one the above GRAPHICS kits as<                    required) is typically the best approach.  F                    OpenVMS V7.2-2 and later mainline releases directly*                    support the controller.  G                    Additional information is available in topics (3419) 9                    and (5448) in the Ask The Wizard area:s  H                    o  http://www.hp.com/go/openvms/wizard/ (retired; use"                       ITRC forums)  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the available F                    ATW Wizard.zip archive, please see Section 3.8. ATWF                    has been superceded (for new questions) by the ITRCD                    discussion forums; the area remains available for                    reference.   I                    Support for the ELSA GLoria Synergy is integrated into.6                    all current OpenVMS Alpha releases.                            5-30r .             0                    System Management Information      '           _____________________________70           5.16.2  PowerStorm 300, PowerStorm 350  @                    The PowerStorm 300 is the PBXGD-AC, while the2                    PowerStorm 350 is the PBXGD-AE.  G                    For support of the PowerStorm 300 and PowerStorm 3503J                    graphics controllers, acquire and install the following&                    available ECO kits:  ,                    For OpenVMS Alpha V7.1-2:  =                    o  DEC-AXPVMS-VMS712_P350-V0100-4 or later   A                    o  DEC-AXPVMS-VMS712_GRAPHICS-V0300-4 or latera  ,                    For OpenVMS Alpha V7.2-1:  =                    o  DEC-AXPVMS-VMS721_P350-V0100-4 or later   A                    o  DEC-AXPVMS-VMS721_GRAPHICS-V0300-4 or later   D                    Support for the PowerStorm 300 and PowerStorm 350I                    series graphics controllers is integrated into current *                    OpenVMS Alpha releases.  '           _____________________________>2           5.16.3  PowerStorm 3D30, PowerStorm 4D20  F                    PowerStorm 3D30 (PBXGB-AA), PowerStorm 4D20 (PBXGB-H                    CA) information is available in Ask The Wizard topics*                    including topic (2041):  H                    o  http://www.hp.com/go/openvms/wizard/ (retired; use"                       ITRC forums)  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the available F                    ATW Wizard.zip archive, please see Section 3.8. ATWF                    has been superceded (for new questions) by the ITRCD                    discussion forums; the area remains available for                    reference.2      J                                                                       5-31 2  8          0                    System Management Information      '           _____________________________t           5.16.4  Radeon 7500   I                    Install the current GRAPHICS ECO kit for OpenVMS Alpha I                    V7.2-2 or V7.3-1 for support of the Radeon 7500 series 4                    PCI and AGP graphics controllers.  F                    Support for this controller (without an ECO kit) isG                    first integrated into and available in OpenVMS Alpha E                    V7.3-2. (Please do always install the most current H                    GRAPHICS ECO kit whenever one is available, however.)  D           __________________________________________________________C           5.17  How can I acquire OpenVMS patches, fixes, and ECOs?   G                    You can acquire and download kits containing OpenVMS H                    fixes (ECOs) for various releases, as well as relatedD                    support information, via the ITRC support center:  -                    o  http://www.itrc.hp.com/   <                    o  ftp://ftp.itrc.hp.com/openvms_patches/  E                    Some systems with Internet firewalls may/will have E                    to use passive mode FTP to access the above sites. J                    Assuming recent/current versions of the TCP/IP Services=                    package, the DCL FTP command necessary is:a  F                    $ DIRECTORY/FTP/ANONYMOUS/PASSIVE ftp.itrc.hp.com::  I                    You can subscribe to an email notification list at thes                    ITRC site.a  H                    For a list of OpenVMS ECO kits recently released, you                    can use:f  J                    o  http://Eisner.DECUS.org/conferences/OpenVMS-patches_                        new_1.HTML  E                    Examples and ECO kit installation instructions areCB                    included in the cover letter. For ECO kit emailD                    notifications, lists of available ECO kits, coverG                    letters and other associated documentation, look in:e  -                    o  http://www.itrc.hp.com/L  <                    o  ftp://ftp.itrc.hp.com/openvms_patches/  G                    For additional information, please see Section 5.17.                       5-32                0                    System Management Information        F                    Do NOT attempt to install a VMSINSTAL-based OpenVMSC                    ECO kit on OpenVMS Alpha V7.1-2 and later. WhilelE                    VMSINSTAL itself remains available, it is not usedeG                    for OpenVMS Alpha ECO kits starting in OpenVMS AlphaoF                    V7.1-2. OpenVMS Alpha V7.1-2 and later use PCSI for$                    OpenVMS ECO kits.  I                    See Section 5.30 for information on ECO kit checksums.   D           __________________________________________________________9           5.18  How do I move the queue manager database?   B                    To move the location of the queue database, the?                    SYS$QUEUE_MANAGER.QMAN$QUEUES and SYS$QUEUE_ J                    MANAGER.QMAN$JOURNAL files, to a disk that is fast(er),J                    has plenty of free space, and that is not heavily used.F                    If the queue database is on a (busy) OpenVMS systemD                    disk, you can and probably should move it off the7                    system disk to another disk spindle.d  .                    To move the queue database:  H                    1  Checkpoint the journal file. This reduces the fileJ                       size to the in-memory database size. This will cause&                       the noted delay.  2                       $ RUN SYS$SYSTEM:JBC$COMMAND+                       JBC$COMMAND> DIAG 0 78  ,                    2  Stop the queue manager  2                       $ STOP/QUEUE/MANAGER/CLUSTER  J                    3  Backup the .QMAN$QUEUES and .QMAN$JOURNAL files from6                       the present location for safety.  V                       $ backup SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$*  DISK:[DIR]  D                    4  Create a new directory for the queue database.F                       Insure that this disk is accessible to all nodesI                       that can run the queue manager. If the /ON list foruF                       the queue manager is "/ON=(*)", the disk must be;                       available to all nodes in the cluster   3                       $ CREATE/DIR fast_disk:[qman]   J                                                                       5-33               0                    System Management Information        J                    5  Copy the .QMAN$QUEUES and .QMAN$JOURNAL files to the#                       new directory   Z                       $ copy SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$*  fast_disk:[qman]  4                    6  Delete the old queue database.  L                       $ DELETE SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$*;*  C                    7  Restart the queue manager pointing to the new                        location  <                       $ START/QUEUE/MANAGER fast_disk:[qman]  D           __________________________________________________________B           5.19  How do I delete an undeletable/unstoppable (RWAST)                 process?  E                    "Undeleteable" jobs are usually "undeleteable" forcG                    a reason-this can track back to insufficient process.H                    quotas, to a kernel-mode error in OpenVMS or a third-A                    party device driver, or to other odd problems.>  F                    These undeletable jobs typically become of interestF                    because they are holding onto a particular resourceF                    (eg: tape drive, disk drive, communications widget)C                    that you need to use... If the particular device E                    supports firmware, ensure that the device firmware I                    is current - TQK50 controllers are known for this when E                    working with old firmware. (That, and the infamous G                    "MUA4224" firmware bug.) If this device has a driver D                    ECO kit available, acquire and apply it... If theI                    particular relevant host component has an ECO, acquireX                     and apply it.  G                    Useful tools include SDA (to see what might be goingeG                    on) and DECamds (which increase and thus potentiallyhF                    fix quota-related problems). (nb: Applications with>                    quota leaks will obviously not stay fixed.)  J                    If the stuck application is BACKUP, ensure you have theI                    current BACKUP ECO and are directly following the V7.1 J                    or (better) V7.2 or later process quota recommendationsI                    for operator BACKUP accounts. Quota details are in the 3                    OpenVMS System Manager's Manual.                       5-34_ _             0                    System Management Information        G                    If the firmware and ECO levels are current, the best J                    approach is to take a system crashdump, and pass a copyH                    of the dump file along to whomever is maintaining theH                    device driver for the particular device/widget/driverF                    involved, with any details on how you got into thisB                    situation. (The reboot involved with taking the?                    crashdump will obviously clear the problem.)r  I                    There was some kernel-mode code (typically for OpenVMSnF                    VAX) that can reset the device ownership field, butE                    that is rather obviously only an interim solution- D                    the real fix is avoiding the loss of the IRP, theG                    process quota leak, or whatever else is "jamming up"u-                    this particular process...s  D           __________________________________________________________2           5.20  How do I reset the error count(s)?  I                    The system reboot is the only supported approach prior F                    to V7.3-2, but a reboot is obviously undesirable inE                    various situations-there is presently no supportedrI                    mechanism to reset error counts once the error(s) havefE                    been logged on these older releases. On V7.3-2 and 6                    later, you can use the DCL command:  1                    $ SET DEVICE/RESET=ERROR_COUNT_  E                    As for an unsupported approach-and be aware of theoD                    potential for triggering a system crash, you needE                    to determine the system address of the error countaG                    field. For a device, this is at an offset within thecE                    device's UCB structure. On VAX, the field is at anVI                    offset symbolically defined as UCB$W_ERRCNT. On Alpha, H                    this field's offset is symbolically defined as UCB$L_H                    ERRCNT. The former is a word in size; the latter is a                    longword.  J                    You now need to locate the system address of the UCB$%_F                    ERRCNT field of the device you wish to reset. EnterF                    SDA. In the following, you will see designations inI                    {} separated by a /. The first item in braces is to be H                    used on the VAX and the second item should be used on.                    an Alpha. (ie. {VAX/Alpha})  J                                                                       5-35 u  r          0                    System Management Information        #                    $ ANALYZE/SYSTEMpE                    SDA>  READ SYS${SYSTEM/LOADABLE_IMAGES}:SYSDEF.STBuC                    SDA>  ! SHOW DEVICE the device with the error(s)l,                    SDA>  SHOW DEVICE <ddnc:>6                    SDA>  EVALUATE UCB+UCB${W/L}_ERRCNTL                    Hex = hhhhhhhh   Decimal = -dddddddddd         UCB+offset  D                    Record the hexadecimal value 'hhhhhhhh' returned.  I                    You can now exit from SDA and $ RUN SYS$SHARE:DELTA or ?                    do what I prefer to do, issue the following:o  1                    SDA> SPAWN RUN SYS$SHARE:DELTA   D                    On both VAX and Alpha, the DELTA debugger will beF                    invoked and will ident- ify itself. On Alpha, thereB                    will be an Alpha instruction decoded. For thoseG                    unfamiliar with DELTA, it does not have a prompt and J                    only one error message-Eh? (Well, for sake of argument,J                    there might be another error produced on the console ifI                    you're not careful. This second error is more commonly ,                    known as a system crash.)  =                    If you are on a VAX, enter the command: [Wi  =                    If you are on Alpha, enter the command: [L   E                    These set the prevailing mode to word and longwordr@                    respectively. Remem- ber the UCB${W/L)_ERRCNT                    differences?o  ,                    Now issue the command 1;M  3                    DELTA will respond with 00000001n  I                    You are now poised to ZAP the error count field. To dolI                    so you need to en- ter the system address and view its G                    contents. The format of the command to do this is of                     the form:  !                    IPID:hhhhhhhh/n  J                    For an IPID, use the IPID of the SWAPPER process. It is#                    always: 00010001   A                    Thus, to ZAP the error count, you would enter:   %                    00010001:hhhhhhhh/                       5-36                0                    System Management Information        F                    When you enter the / SDA will return the content ofG                    the address hhhhhhhh. This should be the error countpG                    (in hexadecimal) of the device in question. If it isiJ                    not, you did something wrong and I'd suggest you type aI                    carriage return and then enter the command EXIT to getIH                    out of DELTA. Regroup and see where your session went                    awry.  F                    If you entered your address correctly and the errorJ                    count was returned as in the following example, you can                    proceed.n  D                    00010001:80D9C6C8/0001   ! output on VAX, 1 error  J                    00010001:80D9C6C8/00000001   ! output on Alpha, 1 error  I                    You can now ZAP the error count by entering a zero and 9                    typing a carriage return. For example:S  N                    00010001:80D9C6C8/0001 0<return>   ! output on VAX. 1 error  T                    00010001:80D9C6C8/00000001 0<return>   ! output on Alpha, 1 error  C                    Now type the command EXIT and a carriage return.   4                    Alternatively, reboot the system.  D           __________________________________________________________I           5.21  How do I find out if the tape drive supports compression?   I                    For various SCSI-based MK-class magnetic tape devices:a  E                    $ Devdepend2 = F$GETDVI("$n$MKcxxx:","DEVDEPEND2") *                    $ Comp_sup = %X00200000*                    $ Comp_ena = %X00400000D                    $ IF (Devdepend2.AND.Comp_sup).EQ.Comp_sup THEN -?                        WRITE SYS$OUTPUT "Compression supported" D                    $ IF (Devdepend2.AND.Comp_ena).EQ.Comp_ena THEN -=                        WRITE SYS$OUTPUT "Compression enabled"o  D           __________________________________________________________G           5.22  Can I copy SYSUAF to another version? To VAX? To Alpha?r  @                    The format of the SYSUAF.DAT, RIGHTSLIST, andI                    associated files are upward-compatible, and compatibleeD                    across OpenVMS VAX, OpenVMS Alpha and OpenVMS I64H                    systems. (This compatibility is a a basic requirementF                    of mixed-version OpenVMS Cluster configurations andE                    OpenVMS upgrades-for specific support information,i  J                                                                       5-37 a             0                    System Management Information        E                    please see the OpenVMS Cluster rolling upgrade and C                    mixed-version requirements.) That said, it's thefH                    contents of the SYSUAF and RIGHTSLIST files that will.                    make this more interesting.  G                    The same basic steps necessary for moving RIGHTSLISTcF                    and SYSUAF files to another node are rather similarE                    to the steps involved in merging these files in an J                    OpenVMS Cluster-see the appendix of the OpenVMS ClusterI                    documentation for details of merging files. (You mightaJ                    not be merging the contents of two (or more) files, butH                    you are effectively merging the contents of the files7                    into the target system environment.)o  "                    Considerations:  H                    o  applications often hold SYSUAF or RIGHTSLIST open,F                       meaning a system reboot is often the best way to)                       activate new files.   F                    o  the meanings of the RESTRICTED and CAPTIVE flagsI                       settings on the UAF entries have changed over time.   J                    o  the new NET$PROXY.DAT file that is initially createdJ                       based on the contents of the NETPROXY.DAT during theE                       OpenVMS VAX V6.1 upgrade and during the OpenVMS D                       Alpha V6.2 upgrade. This file is maintained in1                       parallel with NETPROXY.DAT.c  J                    o  the RIGHTSLIST identifier values and UIC values thatG                       end up scattered around the target system must beeJ                       rationalized with the contents of the new RIGHTSLIST'                       and SYSUAF files.r  G                    The lattermost case-resolving the identifier values-lG                    is often the most interesting and difficult part. If I                    you find that an identifier value (or identifier name) F                    from the source RIGHTSLIST collides with that of anE                    identifier existing on the target system, you musthE                    first determine if the two identifiers perform the H                    same function. In most cases, they will not. As such,E                    you will have to find and chance all references tocF                    the identifier value(s) (or name(s)) to resolve the                    "collision".g                      5-38t    r          0                    System Management Information        E                    If you encounter a collision, changing both of thefB                    identifier binary values (or names) involved inE                    the collision to new and unique values can prevent C                    security problems if you should miss a couple ofoF                    identifiers embedded somewhere on the target systemF                    during the whole conversion process-rather than theD                    wrong alphanumeric value for the identifier beingE                    displayed, you'll simply see the binary format forpE                    the identifier displayed, and no particular accessvE                    will be granted. And any DCL commands or such thatrH                    reference the old alphanumeric name will fail, ratherJ                    than silently (and potentially erroneously) succeeding.  J                    Similar requirements exist for UIC values, as these tooH                    tend to be scattered all over the system environment.G                    Like the binary identifier values, you will find UICnJ                    values associated with disks, ACLs, queues, and various$                    other structures.  G                    For a list of the various files shared in an OpenVMSmC                    Cluster and that can be involved when relocatingpF                    an environment from one node to another (or mergingH                    environments into an OpenVMS Cluster), please see theH                    SYLOGICALS.TEMPLATE file included in OpenVMS V7.2 and"                    later releases.  G                    Procedures to extract the contents of a (potentiallyIF                    corrupt) queue database are provided on the OpenVMSE                    Freeware (V5) and can be used to combine two queuetC                    databases together while shuffling files betweeng)                    OpenVMS Cluster hosts.l  J                    For related discussions of splitting a cluster into twoJ                    or for removing a node from cluster (political divorce,I                    etc), see topics (203), (767), (915) and others in the '                    Ask The Wizard area:   H                    o  http://www.hp.com/go/openvms/wizard/ (retired; use"                       ITRC forums)  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the availablecF                    ATW Wizard.zip archive, please see Section 3.8. ATWF                    has been superceded (for new questions) by the ITRC  J                                                                       5-39 i  i          0                    System Management Information        D                    discussion forums; the area remains available for                    reference.   D           __________________________________________________________9           5.23  How do I delete (timeout) idle processes?h  F                    There is no such command integrated within OpenVMS,F                    though there are (optional) timers available withinJ                    certain terminal servers and similar devices, and thereG                    is an integrated time-of-day mechanism that providesl?                    control over when a user can access OpenVMS.   E                    As for available tools, there are DECUS, freeware, I                    and third-party tools known variously as "idle processcI                    killers" (IPK) or "terminal timeout" programs, as welldJ                    as various other names. Examples include: Saiga SystemsE                    Hitman, Watchdog, MadGoat Watcher (via the MadGoat.H                    site or the OpenVMS Freeware), Kblock, the NetworkingE                    Dynamics tool known as Assassin, and the Zap tool.tI                    Also available is the XLNperformance system managementd,                    utility, from XLNsystems.  A                    A related package (for DECwindows sessions) ist                    xtermlock._  D                    If the forgetful users are in an application menuG                    environment, the menu can potentially be extended too+                    provide this capability.d  D           __________________________________________________________C           5.24  Do I need a PAK for the DECevent (HP Analyze) tool?s  D                    DECevent and HP (Compaq) Analyze are available toH                    customers with support contracts. The PAK is requiredI                    only for the advanced functions of DECevent, the basic E                    bits-to-text translation of the error log does not E                    require a license PAK. Ignore the prompt, in other I                    words. (The PAK should be available to you if you have H                    a hardware support contract or warrantee, and the PAKE                    enables the use of the advanced error analysis andy>                    notification capabilities within DECevent.)  C                    Please see the following website for details andp&                    downloads: Analyze)  =                    o  http://www.compaq.com/support/svctools/s                      5-40h    f          0                    System Management Information        D                    Also see the tool that is available on V7.3-2 and                    later.   &                    $ ANALYZE/ERROR/ELV  D           __________________________________________________________>           5.25  INITIALIZE ACCVIO and ANSI tape label support?  F                    A change was made (back in 1988) to (as it was thenI                    known) VAX/VMS V5.1-1 that added support for the then- J                    new ANSI X3.27-1987 magnetic tape label standard. PriorI                    to the ANSI X3.27-1987 standard, the date field in theaH                    ANSI HDR1 record permits dates only as far as the endI                    of Year 1999. With ANSI X3.27-1987, dates through Year H                    1999 and dates from Years 2000 to 2099 are permitted.  C                    Versions of INIT.EXE and MTAACP.EXE from VAX/VMS J                    releases prior to V5.1-1 will potentially have problemsG                    properly processing ANSI magnetic tapes when Y2K and I                    later dates are involved-the DCL INITIALIZE command is G                    known to encounter access violation (ACCVIO) errors.   G                    The available solutions include upgrades, or settingaH                    the date back. Direct initialization of the tape withG                    the new headers (via $qio) is also clearly possible, J                    though the limitation within the old MTAACP.EXE magtape=                    ACP image is not nearly so easy to bypass.   D           __________________________________________________________7           5.26  How do I recover from INSVIRMEM errors?s  E                    Prior to OpenVMS Alpha V7.0 and on all OpenVMS VAXEJ                    releases, VIRTUALPAGECNT and PGFLQUOTA limit the amountE                    of virtual address space that is available to each                     process.p  F                    Further limiting the amount of address space is theE                    size of system space (S0 and S1 space). On OpenVMStF                    Alpha versions prior to V7.0 and on all OpenVMS VAXF                    releases, VIRTUALPAGECNT and MAXPROCESSCNT togetherG                    determine the size of the page table data structures D                    that occupy large tracts of system space. When noJ                    system virtual address space is available for the stuffI                    that needs it-this includes the page tables, non-paged H                    pool, and various other structures-then the values ofH                    VIRTUALPAGECNT and MAXPROCESSCNT cannot be increased.  J                                                                       5-41 D  U          0                    System Management Information        G                    In OpenVMS Alpha V7.0 and later, the page table datalH                    structures have been moved out of S0 and S1 space andJ                    into page table space. In OpenVMS Alpha V7.2 and later,H                    certain large data structures found in non-paged poolH                    (eg: lock management structures) have been moved intoG                    64-bit space, thus freeing up room in non-paged poolrH                    and in S0 and S1 space (where non-paged pool resides)E                    while also permitting much larger data structures.   D           __________________________________________________________J           5.27  How can I prevent a serial terminal line from initiating a                 login?  ;                    In SYSTARTUP_VMS.COM, issue the command:   =                    $ SET TERMINAL/NOTYPEAHEAD/PERMANENT ddcu:   F                    This will prevent any unsolicited terminal input onE                    ddcu:, and this unsolicited input is what triggers I                    JOB_CONTROL to start up LOGINOUT on the terminal. Once E                    LOGINOUT starts up on the serial line, you can see H                    interesting behaviour (eg: audits, process creations,H                    etc) as LOGINOUT tries to "chat" with whatever deviceG                    is hooked onto the remote end of the serial terminal                     line.  D           __________________________________________________________>           5.28  How does PCSI use the image BUILD_IDENT field?  E                    The (undocumented) build ident field in an OpenVMSdF                    Alpha image header is 16 bytes long, and is used asH                    a counted string of 0-15 characters (ie, as an .ASCICG                    string, a string with the character count in byte 0) G                    and was originally introduced to provide information J                    for use by VMSINSTAL patch kits to determine whether an3                    image should be replaced or not._  J                    Starting with OpenVMS Alpha V7.1-2, OpenVMS EngineeringH                    uses the PCSI utility to package and install ECO kitsE                    for OpenVMS. PCSI uses the generation attribute (aSF                    32-bit unsigned integer) specified for files in theF                    product description file (PDF) of a PCSI kit as theC                    basis for performing file conflict detection andnI                    resolution. When a product is installed, PCSI modifiesiH                    the build ident field of Alpha image headers to storeJ                    an encoded form of the generation number. It also looksJ                    at the build ident field of previously installed images                      5-42n    h          0                    System Management Information        J                    to obtain the generation information for those files asI                    input to the file conflict processing algorithm. (Only 6                    images have this field, obviously.)  H                    PCSI interprets the build ident field of a previously.                    installed image as follows:  F                    o  if the string length is 15, the 5th character isE                       a hyphen, and the last ten characters are a tenoH                       digit number with leading zeros, then the last tenJ                       characters are treated as a valid generation number.  H                    o  for V7.1-2 through V7.2-1, inclusive, if the aboveF                       test fails, the information is obtained from the,                       PCSI product database.  H                    o  in releases after V7.2-1 and with current PCSI ECOJ                       kits, if the above test fails, an invalid generationI                       number is treated as 0000000000 so that the ECO kitvH                       will simply replace the image rather than assuming4                       the PCSI database is in error.  D                    So, what will you see in the image identification;                    displayed via the ANALYZE/IMAGE command?o  I                    For an image that has been built as part of an OpenVMSeE                    Engineering system build, you will generally see a H                    build ID string in the format "X6TE-SSB-0000"-X6TE isI                    the build number for the OpenVMS Alpha V7.2-1 release.(J                    This id format is used within the OpenVMS system build,H                    and can generally only be seen associated with images=                    that have not yet been processed via PCSI.a  F                    During the installation of V7.2-1, PCSI will modifyC                    the image header to have a build ident string ofiC                    "X6TE-0050120000". During installation of an ECOuE                    kit containing this image with a generation number F                    of 50130052, for example, PCSI would determine thatJ                    50130052 is greater than 50120000, and will replace theH                    existing image on the target disk with the version of5                    the image included in the ECO kit.S  H                    Ranges of PCSI generation numbers for various OpenVMSF                    releases are included in Table 5-1. The use of xxxxF                    indicates a range of generations is available, fromI                    0000 to 9999, inclusive. The format of, the particularo  J                                                                       5-43 i  a          0                    System Management Information        F                    operation of, and the assignment of PCSI generation?                    numbers is subject to change without notice.S  J           ________________________________________________________________+           Table 5-1  PCSI Generation Number2  J                    _______________________________________________________                    Generation J                    Number____________Generation_Source____________________  +                    0040100000        V7.1-2   0                    004011xxxx        V7.1-2 ECOs  )                    0050100000        V7.2   .                    005011xxxx        V7.2 ECOs  +                    0050120000        V7.2-1A  0                    005013xxxx        V7.2-1 ECOs  -                    0050140000        V7.2-1H1   2                    005015xxxx        V7.2-1H1 ECOs  +                    0050160000        V7.2-2r  0                    005017xxxx        V7.2-2 ECOs  )                    0060000000        V7.3t  .                    006001xxxx        V7.3 ECOs  +                    0060020000        V7.3-1l  0                    006003xxxx        V7.3-1 ECOs  +                    0060100000        V7.3-2b  0                    006011xxxx        V7.3-2 ECOs  )                    0070040000        V8.2m  .                    007005xxxx        V8.2 ECOs  +                    0070060000        V8.2-1   J           _________007007xxxx________V8.2-1_ECOs__________________________  D           __________________________________________________________H           5.29  How can I tell what software (and version) is installed?  I                    There is unfortunately no consistent nor single way to J                    make this determination-this is one of the reasons that<                    a move to PCSI installations is underway.                      5-44                0                    System Management Information        F                    On OpenVMS Alpha, you can use VMSINSTAL.HISTORY andG                    PRODUCT SHOW PRODUCT to determine what packages have C                    been installed via the VMSINSTAL and PCSI tools,                      respectively.  I                    To see which OpenVMS Alpha ECO kits have been applied,wF                    look in VMSINSTAL.HISTORY on OpenVMS Alpha prior toG                    V7.1-2, and use PRODUCT SHOW PRODUCT/FULL on OpenVMS *                    Alpha V7.1-2 and later.  G                    On OpenVMS VAX, you can use PRODUCT SHOW PRODUCT andhH                    (for software that is installed via VMSINSTAL on V7.33                    and later) in VMSINSTAL.HISTORY.s  F                    For products installed on OpenVMS VAX prior to V7.3I                    using VMSINSTAL, there is no reliable way to determine D                    what products have been installed. If the productB                    provides a RELEASE_NOTES file (as many do), youE                    can look for the list of these files via DIRECTORYiH                    SYS$HELP:*.RELEASE_NOTES. Again, this approach is NOTI                    reliable: some kits do not provide release notes, some.G                    system managers will install only the release notes, F                    some system managers will delete release notes, andF                    release notes for multiple versions can be present.  H                    On most packages, you can generally use ANALYZE/IMAGEB                    on one of the core images, looking at the imageD                    identification area. Some of the product-specific,                    mechanisms available are:  2                    o  DQS DQS$VERSION logical name  "                    o  C CC/VERSION  %                    o  C++ CXX/VERSION   7                    o  TCP/IP TCPIP SHOW VERSION command   D           __________________________________________________________C           5.30  What file checksum tools are available for OpenVMS?   H                    The undocumented (prior to V8.2) DCL command CHECKSUMJ                    is the usual means, and provides a rather simple-mindedF                    checksum suitable to detect basic file corruptions.G                    Starting with V8.2, additional algorithms beyond theO4                    classic XOR scheme are available.  J                                                                       5-45 e  a          0                    System Management Information        E                    One of the most common schemes beyond the CHECKSUMEG                    XOR scheme is MD5, and information and a source codesC                    example are available via the MD5 RFC. Pre-builthH                    versions of MD5 are available at the OpenVMS FreewareF                    website ( http://www.hp.com/go/openvms/freeware/ ),J                    and on the OpenVMS Freeware V8.0 distribution. Also seeJ                    the CHECKSUM/ALGORITHM=MD5 command available on OpenVMS"                    V8.2 and later.  H                    The OpenVMS Alpha ECO (patch) kit checksums availableH                    at the ECO website are determined using the following(                    DCL command sequence:  5                    $ CHECKSUM kitname.pcsi-dcx_axpexep2                    $ SHOW SYMBOL CHECKSUM$CHECKSUM  H                    See Section 5.17 for information on acquiring OpenVMS$                    ECO (patch) kits.  D           __________________________________________________________C           5.31  What (and where) is the OpenVMS Management Station?   C                    For information and current kits for the OpenVMS I                    Management Station (OMS), a PC-based tool that permits ?                    you to manage an OpenVMS system, please see:   K                    o  http://www.openvms.compaq.com/openvms/products/argus/   D           __________________________________________________________B           5.32  How to determine current disk fragmentation level?  ;                    The HP OpenVMS Disk File Optimizer (DFO) C                    defragmentation package provides a fragmentation G                    monitoring tool, and a DFO product authorization key H                    (PAK) is not required for the fragmentation reporting                    tool:  -                    $ DEFRAG SHOW/VOLUME ddcu:e  E                    The DFU tool available on the OpenVMS Freeware canS?                    generate a report on the disk fragmentation:h  $                    DFU> REPORT ddcu:                      5-46n               0                    System Management Information      D           __________________________________________________________H           5.33  SYSBOOT-I-FILENOTLOC, Unable to locate SYS$CPU_ROUTINES?  G                    A message at the OpenVMS Alpha bootstrap such as thee                    following:a  :                    %SYSBOOT-I-FILENOTLOC, Unable to locate.                      SYS$CPU_ROUTINES_1C02.EXE=                    %SYSBOOT-E-LDFAIL, failed to load execlet, &                      status = 00000910  F                    indicates that the particular OpenVMS Alpha releaseG                    does not contain support for the target platform. In(H                    this case, OpenVMS does not recognize Alpha family 1CH                    member 02 as a supported platform. A later version ofH                    OpenVMS might support the platform, or there might beF                    no support on any release. Ensure that you have theH                    most current firmware, and review the minimum version1                    requirements for the platform.   G                    The execlet load failure and other similar bootstrap I                    status values can often be decoded using either of the (                    following techniques:                      $ exit %x910 5                    %SYSTEM-W-NOSUCHFILE, no such files                    $  )                    $ x = f$message(%x910)a"                    $ show symbol x=                      X = "%SYSTEM-W-NOSUCHFILE, no such file"f                    $  -                    Also see Section 14.4.4.1.   D           __________________________________________________________E           5.34  How can I customize the DCPS device control for a newq                 printer?  J                    To customize DCPS for an otherwise unsupported printer,6                    you can try the following sequence:  G                    o  Extract the most closely-associated setup modulesI?                       from the existing device control library,vF                       DCPS$DEVCTL.TLB. (For instance, you can probablyA                       extract and use the HP LaserJet 4000 series G                       definitions for the HP LaserJet 4050 series. EachrC                       printer will vary, please consult the printertD                       documentation for specifics and requirements.)  J                                                                       5-47    a          0                    System Management Information        =                    o  rename each extracted setup module to as$                       corresponding:  )                       LPS$$UNRECOGNIZED_*y  J                    o  Insert all of the above-renamed setup modules into aJ                       newly-created device control library specific to the"                       new printer:  -                       $ LIBRARY/TEXT/CREATE -_>                           SYS$COMMON:[SYSLIB]HP4050_DEVCTL.TLB,                           LPS$$UNRECOGNIZED*  G                       The above assumes the filename HP4050_DEVCTL.TLB, (                       alter as required.  F                    o  Set up your DCPS startup procedures to include a7                       search-list logical name such as:   B                       $ DEFINE/SYSTEM/EXECUTIVE DCPS_HP4050_LIB  -:                           SYS$LIBRARY:HP4050_DEVCTL.TLB, -5                           SYS$LIBRARY:DCPS$DEVCTL.TLB   E                    o  Supply DCPS_HP4050_LIB as the library parametertA                       in the queue startup for this printer, thistB                       is the P3 parameter to the command procedure;                       SYS$STARTUP:DCPS$EXECUTION_QUEUE.COM.e  C                    o  The HP4050_DEVCTL library may/will need to bedG                       recreated and modules re-edited and replaced withfD                       each DCPS upgrade, particularly if any modulesH                       are updated in the original library. You will alsoG                       want to determine if the upgraded version of DCPS ?                       directly supports the particular printer.t  D                    o  To customize the processing of file extensionsG                       within DCPS (to enable or disable graybar output,iF                       for instance), use the information available in:  K                       SYS$LIBRARY:DCPS$FILE_EXTENSION_DATA_TYPE.DAT_DEFAULTt  4                    to create your own site-specific:  @                    SYS$LIBRARY:DCPS$FILE_EXTENSION_DATA_TYPE.DAT  )                    Also see Section 5.15.                       5-48e t  f          0                    System Management Information      D           __________________________________________________________D           5.35  Why do $GETDEV MOUNTCNT and SHOW DEVICE mount counts                 differ?I  E                    MOUNTCNT returns the local mount count, while SHOW ?                    DEVICE returns the cluster-wide mount count.f  D           __________________________________________________________@           5.36  What software is needed for Postscript printers?  D                    The NorthLake PrintKit (www.nls.com) and DECprintF                    Supervisor (DCPS) are common choices for support of2                    Postscript printers on OpenVMS.  )                    o  http://www.nls.com/w  H                    o  http://www.openvms.compaq.com/openvms/Print/print_#                       sw_prods.html   A                    You may also require the installation of an IP #                    transport stack.g  E                    Also please see Section 15.2.2 and Section 15.2.3.t  D           __________________________________________________________A           5.37  How do I remove a PCSI-installed patch (ECO) kit?a  D                    You cannot PRODUCT REMOVE a PCSI patch (ECO) kit.  I                    In order to remove an ECO kit, PCSI would have to have D                    copies of all the other version of the files fromF                    all other patches and products that previously wereH                    installed. This can clearly involve a large number ofG                    files and a large archive of old file versions and a G                    substantial quantity of disk space. While removal is F                    clearly theoretically possible, it is not currently                    implemented.r  G                    The following is the supported mechanism to remove a "                    PCSI patch kit.  H                    1  Execute a PRODUCT SHOW PRODUCT product-name. /FULLJ                       command. The "maintenance" column (132 column width)H                       shows the patches that have been installed. Keep a+                       copy of this listing.   J                    2  Acquire kits for all of the maintenance kits listed.  G                    3  Re-install the prior FULL version of the product.eI                       This will remove all patch kits, setting to productc3                       back to "original" condition.   J                                                                       5-49    c          0                    System Management Information        I                    4  Re-install all the patches in the list from step 1, H                       except those patches which you have determined you"                       do not want.  E                    The above information also applies to PCSI PARTIALo                    kits.  D           __________________________________________________________H           5.38  SYSINIT-E, error mounting system device, status=0072832C  B                    This message can arise during an OpenVMS system                    bootstrap...t  V                    %MOUNT-F-DIFVOLMNT, different volume already mounted on this device  C                    For details and further information, use the DCL                     command:   2                    $ HELP/MESSAGE /STATUS=%X72832C  D           __________________________________________________________/           5.39  Resolving License PAK Problems?_  F                    The PAK release date, the PAK termination date, andH                    the PAK version are the usual culprits when a licenseH                    product authorization key (PAK) check failure occurs.  H                    The PAK termination date is the date when the license#                    PAK will expire.0  F                    The PAK release date is the date of the most recentD                    release date of the software package that will beH                    permitted by the particular license PAK. (The releaseG                    date check is analogous to a product version check.)_D                    The PAK version indicates the most recent product<                    version that is permitted by the license.  G                    Having multiple license PAKs registered (and active) I                    can also cause problems if an expired PAK gets loaded. H                    You will want to DISABLE license PAKs you do not wish"                    to have loaded.  H                    Other problems include a failure to register each PAKI                    in all license databases throughout a multiple-system-fH                    disk cluster, with a consistent set of /INCLUDE lists@                    specified across each of the duplicated PAKs.                      5-50                0                    System Management Information        F                    Additionally, you could have an invalid LMF$LICENSEC                    logical name defined. (If no LMF$LICENSE logical G                    name is defined, the standard license database named <                    SYS$SYSTEM:LMF$LICENSE.LDB will be used.)  C                    You can display license failures by defining the *                    following logical name:  C                    $ DEFINE/SYS/EXEC LMF$DISPLAY_OPCOM_MESSAGE TRUEO  =                    Enable your terminal as a license operatoreB                    (REPLY/ENABLE=LICENSE), define the LMF$DISPLAY_G                    OPCOM_MESSAGE logical name, and then try the failingmD                    operation again. You should see one or more OPCOM&                    messages displayed.  I                    If you have the LMF$DISPLAY_OPCOM_MESSAGE logical name F                    defined, you can (will?) see spurious license checkD                    failures-various products will check for multipleH                    licenses, and a few products will check for PAKs thatG                    either have not yet been or will not be issued. Once I                    you figure out which license has failed, you will want 1                    to deassign this logical name.R  1                                              Note   G                       That there are no license check failures does notaG                       indicate that the particular product or operationOD                       or use is permissible per applicable licensing?                       agreements. Please consult the applicablehD                       agreement(s) for licensing-related information'                       and requirements.   C                    To register a license PAK on a DECwindows systemeF                    when DECwindows cannot start (because of an expiredH                    license or other licensing problem), follow the stepsE                    outlined in section Section 5.6 up through the userF                    of the AUTHORIZE command. In place of the AUTHORIZEI                    command, use the console to register the license PAKs.iJ                    Also see Section 12.4 for licensing and troubleshooting                    information.   E                    For information on licensing and on the numbers of J                    license units required for various products and variousH                    platforms, the License Unit Requirements Table (LURT)#                    is available at:I  J                                                                       5-51 h             0                    System Management Information        C                    o  http://www.compaq.com/products/software/info/r  D           __________________________________________________________4           5.40  Changing the OpenVMS Version Number?  J                    Fool your friends, baffle your enemies, run the OpenVMSH                    version of your choice! Instantly back-port all thoseD                    useful new OpenVMS features to an ancient OpenVMS                    version!   ,                    On OpenVMS Alpha systems:  5                    $ SET DEFAULT SYS$COMMON:[SYS$LDR]                     $ RUN SYSVER                     REPLACE V9.9u                    WRITE                    $ EXIT   C                    How does SYSVER work? SYSVER looks for SYS$BASE_ >                    IMAGE.EXE within the default directory, andE                    updates the version string stored within. And yes, I                    obviously, SYS$BASE_IMAGE.EXE resides in the directory (                    SYS$COMMON:[SYS$LDR].  *                    On OpenVMS VAX systems:  5                    $ set default SYS$COMMON:[SYS$LDR]e8                    $ copy SYS.EXE SYS.EXE_IN-CASE-I-FAIL"                    $ patch SYS.EXE1                    define sys$gq_version=800044b8m!                    set mode ascii *                    !examine sys$gq_version,                    !examine sys$gq_version+44                    deposit sys$gq_version   = "V9.9"4                    deposit sys$gq_version+4 = "    "                    updatet                    exita                    $ Exitr  :                    Then reboot the system at your leisure.                            5-52s t  o          0                    System Management Information      D           __________________________________________________________E           5.41  How to prevent users from choosing obvious passwords?o  G                    To prevent users from selecting obvious passwords on,F                    OpenVMS, you will want to use the reserved passwordI                    (password screening) mechanism. Effectively, you mergepD                    your list of reserved passwords into the existingJ                    reserved words database maintained by OpenVMS. (You canH                    also then require all users to reset their passwords-F                    via the pre-expired password mechanism-thus forcingE                    users to select new passwords.) For details on the I                    password screening mechanism, of the reserved password G                    database (VMS$PASSWORD_DICTIONARY.DATA), and detailsaD                    of how to merge your list of prohibited passwordsG                    into the database, please see the associated chapter_E                    in the OpenVMS security manual. For details of thelC                    password expiration mechanism, see the AUTHORIZE 1                    command qualifier /PWDEXPIRED.   I                    You can also implement a site-specific password filterrC                    with the information provided in the back of the D                    OpenVMS Programming Concepts manual. The passwordG                    filter permits you to establish particular and site- F                    specific password requirements. For details, pleaseC                    see the system parameter LOAD_PWD_POLICY and the G                    programming concepts manual, and see the examples in E                    SYS$EXAMPLES:. (Examples and documentation on V7.3 E                    and later reflect both platforms, the examples are F                    found only on OpenVMS VAX kits on earlier releases.J                    The capabilities have existed on both the VAX and Alpha0                    platforms for some time now.)  B                    To verify current passwords, you can also use aH                    technique known to system crackers as the "dictionaryJ                    attack" - the mechanism that makes this attack somewhatJ                    more difficult on OpenVMS is the hashing scheme used onH                    OpenVMS, and the file protections used for the SYSUAFJ                    authorization database. Given a dictionary of words andH                    the unprotected contents of the SYSUAF file, a searchI                    for obvious passwords can be performed. Interestingly,oG                    a "dictionary attack" also has the unfortunate side- I                    effect of exposing the password to the user-while this-F                    is clearly the goal of a system cracker, authorizedH                    privileged and non-privileged system users should not  J                                                                       5-53 u  r          0                    System Management Information        G                    know nor have access to the (cleartext) passwords of                     other users.   D                    Accordingly, OpenVMS does not store the cleartestE                    password. Further, OpenVMS uses a password hashingwJ                    algorithm, not an encryption algorithm. This means thatJ                    storage of a cleartext password is deliberated avoided,I                    and the cleartext value is deliberately very difficulttF                    to obtain. The hash is based on a Purdy Polynomial,G                    and the hash itself includes user-specific values inEI                    addition to the password, values that make the resultse<                    of the password hash unique to each user.  I                    Regardless of the use of a password hashing scheme, if J                    a copy of your password file should become available toH                    a system cracker, you will want to force all users to1                    use new passwords immediately.   E                    If you should require a user to verify a password, F                    use the username, the user's salt value (this valueD                    is acquired via $getuai) and the user's specifiedG                    cleartext password, and compare the resulting hashedeE                    value (using a call to $hash_password) against the H                    saved hashed password value (this value also acquiredF                    via $getqui). For reasons of security, avoid savingG                    a cleartext password value in any data files, and dooG                    not maintain the cleartext password in memory longereH                    than required. (Use of sys$acm on V7.3-1 and later is                     recommended.)  A                    Kerberos authentication (client and server) is F                    available on OpenVMS V7.3 and later. Integration ofG                    Kerberos support into various Compaq and into third-r.                    party products is expected.  A                    External authentication is available in V7.3-1 D                    and later, with support for user-written external6                    authentication in V7.3-2 and later.  C                    If you are simply looking for OpenVMS access andmD                    the SYSTEM and all other privileged passwords areI                    forgotten or otherwise unavailable, please see sectionnD                    Section 5.6 and/or the OpenVMS documentation set.  H                    Also please see the NCSC C2 guidelines in the OpenVMS#                    security manual.                       5-54c y  r          0                    System Management Information      D           __________________________________________________________?           5.42__Please_help_me_with_the OpenVMS BACKUP utility?   8           5.42.1  Why isn't BACKUP/SINCE=BACKUP working?  J                    If you are seeing more files backed up than previously,I                    you are seeing the result of a change that was made toDJ                    ensure BACKUP can perform an incrementation restorationC                    of the files. In particular, if a directory filelI                    modification date changes, all files underneath it are I                    included in the BACKUP, in order to permit incremental C                    restoration should a directory file get renamed.o  '           _____________________________ J           5.42.1.1  Why has OpenVMS gone through the agony of this change?  D                    When a directory is renamed, the modified date isE                    changed. When the restoration needs to restore theiI                    directory and its contents, and the restoration should_G                    not result in the restoration of the older directorytJ                    name when a series of incremental BACKUPs are restored.H                    Thus an incremental BACKUP operation needs to pick up&                    all of the changes.  E                    Consider performing an incremental restoration, to D                    test the procedures. This testing was how OpenVMSC                    Engineering found out about the problem that wascB                    latent with the old BACKUP selection scheme-theB                    old incremental BACKUP scheme would have missedG                    restoring any files under a renamed directory. HenceaF                    the change to the selection mechanisms mentioned in"                    Section 5.42.1.  '           ______________________________>           5.42.1.2  Can you get the old BACKUP behaviour back?  I                    Yes, please see the /NOINCREMENTAL qualifier availablelD                    on recent OpenVMS versions (and ECO kits). Use ofF                    this qualifier informs BACKUP that you are aware ofE                    the limitations of the old BACKUP behaviour aroundi1                    incremental disk restorations.         J                                                                       5-55    I          0                    System Management Information      '           _____________________________ >           5.42.2  What can I do to improve BACKUP performance?  @                    Use the documented commands in the manual forE                    performing incremental BACKUPs. Use the documenteduG                    incremental procedures. Don't try to use incrementaln9                    commands in a non-incremental context.a  G                    Also consider understanding and then using /NOALIAS,eJ                    which will likely be a bigger win than will anything toJ                    do with the incremental BACKUPs, particularly on systemD                    disks and any other disks with directory aliases.  H                    See the OpenVMS documentation for additional details.  H                    Ignoring hardware performance and process quotas, theJ                    performance of BACKUP during a disk saveset creation is6                    typically limited by three factors:  )                    1  Default extend sizea  E                       The default behavior can have poor performance, C                       as the extend operation can involve extensiveoH                       additional processing and I/O operations. ConsiderI                       changing the default extend value on the volume, or 8                       change the extend for the process:  ,                       $ set rms/extend=65000  $                    2  Output IO size  G                       The default IO size for writing an RMS sequentialoF                       file is 32 blocks, an increase from the value ofI                       16 blocks used on earlier versions. Setting this to H                       the maximum of 127 can reduce the number of IOs by+                       almost a factor of 4:   )                       $ set rms/block=127e  G                       Note that the performance might be better on some I                       controllers if the block count is a multiple of 4 -s                       e.g. 124  7                    3  Synchronous writes to the saveset   F                       Starting with OpenVMS V7.3, you can now persuadeF                       RMS to turn on write-behind for sequential filesI                       opened unshared. (Please see the V7.3 release notesuI                       or more recent documentation for details.) EnablingoF                       the write-behind operations involves setting theD                       dynamic system parameter RMS_SEQFILE_WBH to 1.                      5-56s    l          0                    System Management Information        F                       This parameter is dynamic, and it can be enabledG                       and disabled without a reboot, and changes in itsyF                       setting can and will directly effect the runningJ                       system. In order to get the full benefit from write-F                       behind operations, you also need to increase theG                       RMS local buffer count from the default of 2 to a J                       larger number. Raising the value to 10 is probably a?                       reasonable first estimate for this value.   -                       $ run sys$system:sysmank+                       PARAMETERS USE ACTIVEe6                       PARAMETERS SET RMS_SEQFILE_WBH 1-                       PARAMETERS WRITE ACTIVEx                       EXIT@                       $ SET RMS/BUFFER=10/EXTEND=65000/BLOCK=127N                       $ BACKUP source-specification ddcu:[dir]saveset.bck/SAVE  '           _____________________________ 8           5.42.3  Why is BACKUP not working as expected?  C                    First, please take the time to review the BACKUPaE                    documentation, and particularly the BACKUP commandcF                    examples. Then please download and install the mostI                    current BACKUP eco kit. Finally, please please set the J                    process quotas per the System Management documentation.B                    These steps tend to resolve most problems seen.  A                    BACKUP has a very complex interface, and there0C                    are numerous command examples and extensive usersH                    documentation available. For a simpler user interfaceC                    for BACKUP, please see the documentation for theA'                    BACKUP$MANAGER tool.V  E                    As for recent BACKUP changes, oddities, bugs, etc:   I                    o  A change made in OpenVMS V6.2 WILL cause more files E                       to be included into a file-based BACKUP saveset E                       using /SINCE=BACKUP as all files underneath any E                       directory with a sufficiently recent (selected) G                       date will be included in the saveset. This change0F                       was deliberate and intentional, and was mandatedE                       by the need to provide a functional incrementalx"                       restoration.  J                                                                       5-57 C  _          0                    System Management Information        E                       Without the inclusion of these apparently-extraaG                       files, an incremental saveset can NOT be reliablyl                       restored.   D                    o  As part of the OpenVMS V6.2 change, the /SINCEF                       command-without the specification of the =BACKUPF                       keyword-selected more files than it should have.F                       This is a bug. This bug has been remedied in theI                       OpenVMS BACKUP source code and in some of (all of?)r*                       the BACKUP ECO kits.  >                    When working with BACKUP, you will want to:  E                    o  Ensure you have your process quotas set per theiF                       recommendations in the OpenVMS System ManagementH                       documentation. Deviation from these values can andF                       will lead to access violation (ACCVIO) and other)                       untoward behaviour.e  J                    o  Get the current BACKUP ECO kit and install it BEFORE?                       you attempt to troubleshoot any problems.L  G                    o  Learn about the /NOINCREMENTAL (new) and /NOALIASrE                       (V6.2 and later) command qualifiers. The formertH                       qualifier returns to the pre-V6.2 behaviour of theG                       /SINCE file selection mechanism, while the latteryE                       (specified with /IMAGE) reduces the replicationRH                       of files on system disks and other disks with fileJ                       alias and directory alias entries. Both of these canG                       reduce the numbers of files that will be selecteds9                       and thus included into the saveset.e  F                       Learn what /IGNORE=INTERLOCK means. This commandG                       probably does not provide what you think it does-eG                       those file system interlocks that this command istH                       ignoring were implemented for a reason, after all.G                       Ignoring these interlocks can lead to missed dataoH                       and potentially to corruptions to individual filesH                       stored within the output saveset, corruptions thatE                       may or may not be reported. For details on this_F                       BACKUP command qualifier, please see the Ask The*                       Wizard topic (2467).                        5-582 C  o          0                    System Management Information        =                    When working with the BACKUP callable API:   J                    o  Build your applications with the most current BACKUPH                       API available. Changes made to the V7.1-2 and V7.2H                       API were incompatible with the V7.1 and V7.2-1 andG                       later APIs, and this incompatibility was repairedaI                       via a BACKUP ECO kit. Do NOT build your applicationCF                       with the versions of the BACKUP API that shippedJ                       with V7.1-2 and V7.2, as these are incompatible withF                       the BACKUP API constants that were used on other                       versions.e  '           _____________________________,8           5.42.4  How do I fix a corrupt BACKUP saveset?  I                    BACKUP savesets can be corrupted by FTP file transfersiF                    and by tools such as zip (particularly when the zipF                    tool has not been asked to save and restore OpenVMSF                    file attributes or when it does not support OpenVMSH                    file attributes; use the zip "-V" option), as well as2                    via other means of corruptions.  H                    If you have problems (eg: NOTSAVESET errors) with theG                    BACKUP savesets after unzipping them or after an FTP_G                    file transfer, you can try restoring the appropriaten5                    saveset attributes using the tool:   1                    $ BACKUP/LIST saveset.bck/SAVEp)                    Listing of save set(s)o  R                    %BACKUP-F-NOTSAVESET, saveset.bck/SAVE is not a BACKUP save setT                    $ @SRH:[UTIL]RESET_BACKUP_SAVESET_FILE_ATTRIBUTES.COM saveset.bck1                    $ BACKUP/LIST saveset.bck/SAVE_)                    Listing of save set(s)   1                    Save set:          saveset.bcke.                    Written by:        username                    ...  E                    This tool is available on the OpenVMS Freeware (in G                    the [000TOOLS] directory). The Freeware is available F                    at various sites-see the Freeware location listingsH                    elsewhere in the FAQ-and other similar tools are also2                    available from various sources.  J                                                                       5-59 h             0                    System Management Information        F                    In various cases, a SET FILE/ATTRIBUTES command canJ                    also be used. As the parameters of this command must beG                    varied as the target BACKUP saveset attributes vary, 4                    this approach is not recommended.  I                    Also see the "SITE VMS", /FDL, and various other file--J                    attributes options available in various FTP tools. (NotF                    all available FTP tools support any or all of these                    options.)  G                    Browser downloads (via FTP) and incorrect (binary oraF                    ascii FTP transfer modes) are notorious for causingG                    RMS file corruptions and particularly BACKUP savesetlD                    corruptions. You can sometimes help encourage theG                    browser to select the correct FTP transfer type code !                    (via RFC1738):p  A                    o  ftp://host/urlname.ext;type=i ! request ftp +                       image/binary transferi  A                    o  ftp://host/urlname.ext;type=a ! request ftp )                       ascii/text transferi  J                    You can also often configure the particular web browserF                    to choose the appropriate transfer mode by default,C                    based on the particular file extensions, using ahI                    customization menu available in most web browsers. You H                    can select that the specific file extentions involvedJ                    use the FTP binary transfer mode, which will reduce the.                    number of corruptions seen.  '           ______________________________C           5.42.5  How do I write a BACKUP saveset to a remote tape?e  G                    How to do this correctly was described at DECUS long G                    ago. On the OpenVMS host with the tape drive, createi3                    the following SAVE-SET.FDL file:t                      RECORDu8                            FORMAT                  fixed7                            SIZE                    8192                           5-60                0                    System Management Information        1                    Then create BACKUP_SERVER.COM:e                      $ !R                    $ ! BACKUP_SERVER.COM - provide remote tape service for BACKUP.                    $ !                    $ set noon '                    $ set rms/network=16 ,                    $ allocate mka500 tapedevE                    $ mount/nounload/over:id/block=8192/assist tapedev C                    $ convert/fdl=SAVE-SET sys$net tapedev:save-set.s,                    $ dismount/unload tapedev                    $ stop/id=0  G                    On the node where you want to do the backup, use the                     DCL command:b                      $ backup - $                        srcfilespec -K                        node"user pwd"::"task=backup_server"/block=8192/saveL  F                    One area which does not function here is the volumeH                    switch; multi-reel or multi-cartridge savesets. SinceG                    the tape is being written through DECnet and RMS and E                    the magtape ACP, BACKUP won't see the media switch H                    and will split an XOR group across the reel boundary.E                    BACKUP might well be willing to read such a multi-.F                    reel or multi-cartridge saveset (directly, not overE                    the net) as the XOR blocks are effectively ignored I                    until and unless needed for error recovery operations. I                    BACKUP likely will not be able to perform an XOR-based @                    recovery across reel or cartridge boundaries.  I                    Unfortunately BACKUP can't read tapes over the network D                    because the RMS file attributes on a network taskE                    access look wrong; the attributes reported includea+                    variable length records.   '           _____________________________e=           5.42.6  How to perform a DoD security disk erasure?o  ?                    Sometimes refered to as disk, tape, or mediatG                    declassification, as formatting, as pattern erasure,nC                    or occasionally by the generic reference of data,G                    remanence. Various references to the US Deparment ofCJ                    Defence (DoD) or NCSC "Rainbow Books" documentation are-                    also seen in this context.L  J                                                                       5-61 .             0                    System Management Information        G                    While this erasure task might initially appear quite_G                    easy, basic characteristics of the storage media andnF                    of the device error recovery and bad block handlingH                    can make this effort far more difficult than it might$                    initially appear.  F                    Obviously, data security and sensitivity, the costsB                    of exposure, applicable legal or administrativeB                    requirements (DoD, HIPPA or otherwise), and theG                    intrinsic value of the data involved are all centralpH                    factors in this discussion and in the decision of theI                    appropriate resolution, as is the value of the storagec%                    hardware involved.   C                    With data of greater value or with data exposure F                    (sometimes far) more costly than the residual valueI                    of the disk storage involved, the physical destruction B                    of the platters may well be the most expedient,G                    economical, and appropriate approach. The unintended I                    exposure of a bad block containing customer healthcare F                    data or of credit card numbers can quite be costly,G                    of course, both in terms of the direct loss, and the D                    longer-term and indirect costs of such exposures.  F                    Other potential options include the Freeware RZDISKE                    package, the OpenVMS INITIALIZE/ERASE command (and E                    potentially in conjunction with the $erapat system C                    service) and OpenVMS Ask The Wizard (ATW) topics G                    including (841), (3926), (4286), (4598), and (7320).uD                    For additional information on sys$erapat, see theF                    OpenVMS Programming Concepts manual and the OpenVMSH                    VAX examples module SYS$EXAMPLES:DOD_ERAPAT.MAR. SomeH                    disk controllers and even a few disks contain supportG                    for data erasure. Some DSSI Disk ISEs, for instance.   D                    For the prevention of casual disk data exposures,C                    a generic INITIALIZE/ERASE operation is probably ?                    sufficient. This is not completely reliable, E                    particularly if the data is valuable, or if legal, A                    administrative or contractual restrictions are E                    stringent-there may well be revectored blocks that G                    are not overwritten or not completely overwritten by I                    this erasure, as discussed above, and these blocks can H                    obviously contain at least part of most any data thatI                    was stored on the disk - but this basic disk overwrite_                      5-62_ _  _          0                    System Management Information        H                    operation is likely sufficient to prevent the typical+                    information disclosures.p  C                    You will want to consult with your site security I                    officer, your corporate security or legal office, withaE                    HP Services or your prefered service organization,$E                    or with a firm that specializes in erasure or data_I                    declassification tasks. HP Services does traditionallye@                    offer a secure disk declassification service.  '           _____________________________r9           5.42.7  How to enable telnet virtual terminals?   D                    To enable virtual terminal support for telnet andA                    rlogin devices, add the following logical name 3                    definitions into SYLOGICALS.COM:T  B                    $ DEFINE/SYSTEM/EXECUTIVE TCPIP$RLOGIN_VTA TRUEB                    $ DEFINE/SYSTEM/EXECUTIVE TCPIP$TELNET_VTA TRUE  I                    See SYS$STARTUP:SYLOGICALS.TEMPLATE for details on thed6                    typical contents of SYLOGICALS.COM.  I                    In SYSTARTUP_VMS.COM, ensure that a command similar to ,                    the following is invoked:  a                    $ SYSMAN IO CONNECT VTA0/NOADAPTER/DRIVER=SYS$LOADABLE_IMAGES:SYS$TTDRIVER.EXEc  J                    In MODPARAMS.DAT, add the following line or (if alreadyH                    present) mask the specified hexidecimal value into anJ                    existing TTY_DEFCHAR2, and perform a subsequent AUTOGEN+                    with an eventual reboot:s  )                    TTY_DEFCHAR2 = %X20000   2                    This value is TT2$M_DISCONNECT.  F                    On older TCP/IP Services-versions prior to V5.0-youB                    will have to perform the following UCX command:                      $ UCX4                    UCX> SET CONF COMM/REMOTE=VIRTUAL    J                                                                       5-63    $          0                    System Management Information      '           _____________________________ ;           5.42.7.1  Volume Shadowing MiniCopy vs MiniMerge?   F                    MiniMerge support has been available for many yearsG                    with OpenVMS host-based volume shadowing, so long asLH                    you had MSCP controllers (eg: HSC, HSJ, or HSD) whichH                    supported the Volume Shadowing Assist known as "Write$                    History Logging".  B                    If you are interested in mini-merge and similarE                    technologies, please see the Fibre Channel webpagee7                    and the information available there:S  B                    o  http://www.openvms.compaq.com/openvms/fibre/  C                    Mini-Merge support was originally intended to be F                    controller-based and was expected with HSG80 seriesJ                    storage controllers and was expected to require ACS 8.7,                    and OpenVMS Alpha V7.3-1.  D                    Host-based Mini-Merge (HBMM) is now available forE                    specific OpenVMS releases via a shadowing ECO kit, F                    and is also present in OpenVMS V8.2 and later. HBMMI                    applies to the HSG80 series and-like host-based volumecI                    shadowing-to most other (all other?) supported storage                     devices.   E                    The following sections describe both Mini-Copy and G                    Mini-Merge, and can provide a basis for discussions.   '           _____________________________T            5.42.7.1.1  Mini-Copy?  I                    A Shadowing Full Copy occurs when you add a disk to annG                    existing shadowset using a MOUNT command; the entiretE                    contents of the disk are effectively copied to the F                    new member (using an algorithm that goes through inF                    127-block increments and reads one member, comparesH                    with the target disk, and if the data differs, writesD                    the data to the target disk and loops back to theC                    read step, until the data is equal for that 127- F                    block section). (This is one of the reasons why theG                    traditional recommendation for adding new volumes to F                    a shadowset was to use a BACKUP/PHYSICAL copy of anF                    existing shadowset volume, simply because the readsJ                    then usually matched and thus shadowing usually avoided,                    the need for the writes.)                      5-64_ _  _          0                    System Management Information        G                    If you warn OpenVMS ahead of time (at dismount time)eI                    that you're planning to remove a disk from a shadowsetlB                    but re-add it later, OpenVMS will keep a bitmapE                    tracking what areas of the disk have been modified H                    while the disk was out of the shadowset, and when youH                    re-add it later with a MOUNT command OpenVMS only hasI                    to update the areas of the returned disk that the bit-eG                    map indicates are now out-of-date. OpenVMS does thiswH                    with a read source / write target algorithm, which isG                    much faster than the shenanigans the Full Copy does,AI                    so even if all of the disk has changed, a Mini-Copy is +                    faster than a Full Copy.   '           _____________________________O!           5.42.7.1.2  Mini-Merge?c  F                    A Shadowing Merge is initiated when an OpenVMS nodeI                    in the cluster (which had a shadowset mounted) crashesdH                    or otherwise leaves unexpectedly, without dismountingI                    the shadowset first. In this case, OpenVMS must ensure.I                    that the data is identical, since Shadowing guarantees D                    that the data on the disks in a shadowset will beJ                    identical. In a regular Merge operation, Shadowing usesJ                    an algorithm similar to the Full Copy algorithm (exceptE                    that it can choose either of the members' contents_H                    as the source data, since both are considered equallyJ                    valid), and scans the entire disk. Also, to make thingsF                    worse, for any read operations in the area ahead ofG                    what has been merged, Shadowing will first merge theoH                    area containing the read data, then allow the read to                    occur.s  B                    A Merge can be very time-consuming and very I/OH                    intensive. If a node crashes, the surviving nodes canF                    query to determine what exact areas of the disk theF                    departed node was writing to just before the crash,H                    and thus Shadowing only needs to merge just those fewF                    areas, so this tends to take seconds, as opposed toI                    potentially requiring many minutes or even hours for a &                    regular full Merge.        J                                                                       5-65               0                    System Management Information      D           __________________________________________________________;           5.43  Please explain DELETE/ERASE and File Locks?   D                    DELETE/ERASE holds the file lock and also holds aG                    lock on the parent directory for the duration of the F                    erasure. This locking can obviously cause an accessC                    conflict on either the file or on the directory- E                    it might well pay to rename files into a temporary F                    directory location before issuing the DELETE/ERASE,G                    particularly for large files and/or for systems with D                    multiple overwrite erase patterns in use; for anyH                    systems where the DELETE/ERASE erasure operation will                     take a while.  D           __________________________________________________________'           5.44  Managing File Versions?i  A                    Some applications will automatically roll fileeE                    version numbers over, and some will require manual"J                    intervention. Some will continue to operate without theI                    ability to update the version, and some will be unableSI                    to continue. Some sites will specifically (attempt to)aH                    create a file with a version of ;32767 to prevent the5                    creation of additional files, too.   D                    To monitor and resolve file versions, you can use&                    commands including:  6                    $ SET FILE/VERSION_LIMIT=n filename>                    $ SET DIRECTORY/VERSION_LIMIT=n [directory]  E                    And you can also monitor file version numbers, and I                    can report problems with ever-increasing file versions G                    to the organization(s) supporting the application(s) H                    generating files with ever-increasing version numbersA                    for details on potential problems, and for any G                    recommendations on resetting the version numbers fornE                    the particular product or package. If required, ofs                    course.  F                    The following pair of DCL commands-though obviouslyC                    subject to timing windows- can be used to renameeG                    all the versions of a file back down to a contiguousc6                    sequence of versions starting at 1:  4                    $ RENAME file.typ;*   RENAME.TMP;2                    $ RENAME RENAME.TMP;* file.typ;                      5-66w ,  l          0                    System Management Information        H                    The key to the success of this RENAME sequence is theH                    specification of (only) the trailing semicolon on theC                    second parameter of each of the RENAME commands.w  E                    You may also see the numbers of files reduced withdF                    DELETE commands, with multiple directories, or withA                    PURGE commands such as the following examples:l  '                    $ PURGE/BEFORE="-2-"r,                    $ PURGE/BEFORE="TODAY-2-"#                    $ PURGE/KEEP=10"d  H                    You can use DFU (Freeware) to quickly and efficientlyD                    scan for all files with large(r) version numbers:  2                    DFU SEARCH/VERSION=MINIMUM=nnnn  D                    If you are creating or supporting an application,G                    selecting temporary or log file filenames from amongtH                    a set of filenames-selecting filenames based on time,E                    on process id, on the day of week, week number, orrJ                    month, on the f$unique lexical (V7.3-2 and later), etc-H                    is often useful, as this approach more easily permitsG                    on-line adjustments to the highest file versions andiC                    easily permits on-line version compression using D                    techniques shown above. With differing filenames,D                    you are less likely to encounter errors resultingE                    from files that are currently locked. You can also G                    detect the impending version number limit within the H                    application, and can clean up older versions and roll@                    the next file version creation to ;1 or such.  (                    Also see Section 9.4.  D           __________________________________________________________5           5.45  Host-based Volume Shadowing and RAID?   J                    Host-based Volume Shadowing (HBVS) is Disk Mirroring is                     RAID Level 1.  D                    HBVS is capable of shadowing devices of different>                    geometries, of different block counts (withE                    dissimilar device shadowing; allowing for mixturesgD                    of hardware) and-with dynamic volume expansion-ofE                    growing volumes on the fly, and HBVS is capable of G                    shadowing/mirroring/raid-1 operations across clusterhD                    configurations up to the full span-please see the  J                                                                       5-67 n  e          0                    System Management Information        B                    Cluster SPD for the current supported span; theF                    supported span limit is currently multiple hundredsG                    of kilometers-of a cluster. HBVS can be layered onto 7                    controller (hardware) RAID, as well.e  I                    For information on host-based striping, please see thee-                    StorageWorks RAID product.                                                                                               5-68f c  e                    J                    _______________________________________________________  &           6        Information on Mail      D           __________________________________________________________J           6.1  MAIL keeps saying I have new messages, but I don't. What do                I do?  J                    if you see the %MAIL-W-NONEWMAIL, no new messages errorG                    reported when MAIL indicates you have messages, thenUD                    the NEWMAIL count has become skewed from reality.  D                    The count of new mail messages is kept separatelyC                    from your mail folder, and is stored in VMSMAIL_ E                    PROFILE.DATA. It sometimes happens that this counteF                    differs from what is stored in your mail folder. IfD                    this arises, invoke MAIL and repeatedly enter theF                    READ/NEW command (or press the keypad hyphen key onG                    an LK-compatible keyboard) until you see no new mailsG                    messages. Then enter the command one more time. This 3                    will resynchronize the counters.   G                    If you are operating in a cluster and find your mail C                    counts inconsistent across cluster members, your_J                    customer is likely missing a definition of the VMSMAIL_D                    PROFILE logical name-and is probably also missingE                    definitions of other logical names associated withuE                    other shared files-or has one or more inconsistentaI                    definitions of this and likely of other logical names.   C                    For details on the configuration data files that >                    must be shared within a cluster, please seeE                    SYS$STARTUP:SYLOGICALS.TEMPLATE on V7.2 and later.   D           __________________________________________________________=           6.2  How do I send or read attachments in VMS MAIL?d  F                    Is there any way to send or read mail with files as(                    attachments from VMS?      J                                                                        6-1 m  d          &                    Information on Mail        I                    Not directly with the OpenVMS MAIL facility, but theren-                    are several other options:t  H                    o  Install PINE, available commercially from InnosoftF                       or free from Andy Harper. With PINE you can bothE                       send and receive MIME messages, if you have theo4                       appropriate viewers available.  /                      o  http://www.process.com/   G                      o  http://www.agh.cc.kcl.ac.uk/files/vms/pine-vms/   >                      o  ftp://ftp2.kcl.ac.uk/pub/vms/pine-vms/  G                    o  If you are working from an X Windows display, youtJ                       can use the OpenVMS version of Netscape Navigator orJ                       Mozilla. The mail download protocol chosen to accessH                       the mail server from the Navigator or Mozilla mailH                       client can be POP or IMAP, with the former causingH                       messages to be downloaded while the latter permitsF                       messages to be retained on the mail server. Most8                       folks prefer IMAP for this reason.  G                    o  MPACK/MUNPACK. To send a MIME mail, construct the H                       message with attachments manually using MPACK. YouJ                       cannot send the resulting file directly through MAILI                       because an extra blank header line will be inserted H                       between your message and the OpenVMS MAIL headers,J                       which will cause the message to appear as plain textG                       in most mail programs. Some TCP/IP stacks provide I                       a work around for this problem, and if that doesn't E                       work, you should generally be able to force the F                       message directly into the SMTP port of your mail?                       machine. Examples of both methods are in:a  Q                      o  http://saf.bio.caltech.edu/pub/software/openvms/mmail.com   C                       To read a MIME mail message, open it in MAIL, E                       extract it to a file, then use MUNPACK to break 5                       out and decode the attachments.   G                       MPACK/MUNPACK tools are also available on OpenVMSS$                       Freeware V5.0.  D                    o  With OpenVMS V7.2 and later, use the MIME tool,                       supplied with OpenVMS.                      6-2 P  u          &                    Information on Mail      D           __________________________________________________________4           6.3  How can I block SMTP mail relay spam?  G                    Use the anti-spam capabilities present in the TCP/IPn8                    Services V5.1 and later SMTP servers.  "                    Use a firewall.  G                    On earlier TCP/IP Services releases, some simple DCLsF                    can reportedly prevent relay SMTP spam. Use the UCXG                    command SHOW SERVICE SMTP/FULL to find the directoryeE                    containing the UCX$SMTP_RECV_STARTUP.COM file, and ,                    insert the following DCL:             $       !e           $       ! Block spam.n           $       ! P           $       MY_ADDRESS_LONG[0,32]=F$INTEGER(F$TRNLNM("SYS$REM_NODE")-"::")R           $       MY_ADDRESS=F$FAO("!UB.!UB.!UB.!UB",F$CVUI(0,8,MY_ADDRESS_LONG),-M                    F$CVUI(8,8,MY_ADDRESS_LONG),F$CVUI(16,8,MY_ADDRESS_LONG),-m2                    F$CVUI(24,8,MY_ADDRESS_LONG))'">           $       MY_ADDRESS_REVERSE=F$FAO("!UB.!UB.!UB.!UB",-N                    F$CVUI(24,8,MY_ADDRESS_LONG),F$CVUI(16,8,MY_ADDRESS_LONG),-M                    F$CVUI(8,8,MY_ADDRESS_LONG),F$CVUI(0,8,MY_ADDRESS_LONG))'" S           $       WRITE SYS$OUTPUT F$TIME()+" "+F$TRNLNM("SYS$REM_NODE")+MY_ADDRESSeD           $       UCX SHOW HOST 'MY_ADDRESS_REVERSE'.INPUTS.ORBS.ORG!           $       IF $STATUS.EQ.1r           $       THEN?           $         WRITE SYS$OUTPUT "SPAM from relay rejected"            $         EXIT           $       ENDIF I           $       UCX SHOW HOST 'MY_ADDRESS_REVERSE'.SPAMSOURCES.ORBS.ORG !           $       IF $STATUS.EQ.1a           $       THENA           $         WRITE SYS$OUTPUT "SPAM source relay rejected"            $         EXIT           $       ENDIF            $       !O!           $       ! Run receiver.            $       !m6           $       run sys$system:ucx$smtp_receiver.exe           $       goto exitm      J                                                                        6-3 n  m                    J                    _______________________________________________________  +           7        Information on Utilities       D           __________________________________________________________;           7.1  How do I play an audio CD on my workstation?   F                    If you've installed the DECwindows examples, you'llD                    find DECW$CDPLAYER.C, .DAT, .EXE, .UIL, and .UID.F                    Copy the .UID and .DAT files to DECW$USER_DEFAULTS:B                    (typically SYS$LOGIN:), define the logical nameF                    DECW$CD_PLAYER to be the device name of your CD-ROMI                    drive (eg. DKA400:), give yourself PHY_IO and DIAGNOSEuF                    privileges, and run the .EXE. (These privileges areG                    required, as the access to the CD-related extensions G                    will require the use of the privilege-protected IO$_lD                    DIAGNOSE I/O function code.) You can also installF                    the image with these privileges. See the source forH                    additional details - note that the comments regardingG                    the need for SYSGEN CONNECT are no longer applicableu/                    (at least as of VMS V5.5-2).   D                    There's also SYS$EXAMPLES:CDROM_AUDIO.C and .EXE,E                    a non-Motif program, available on OpenVMS VAX, and C                    DECW$EXAMPLES:DECW$CDPLAYER.* on OpenVMS VAX and !                    OpenVMS Alpha.e  E                    The standard OpenVMS ATA (IDE) SYS$DQDRIVER devicenA                    driver does not support the necessary does notiC                    support the necessary IO$_DIAGNOSE function codea@                    that is required for access to audio CD mediaD                    commands (on OpenVMS versions prior to V7.3), but@                    an updated SYS$DQDRIVER device driver (sourceB                    code and all) with this capability and with theC                    source code of an updated DECW$CDPLAYER CD audio F                    player is available on the OpenVMS Freeware websiteA                    (www.hp.com/go/openvms/freeware/, look for the D                    directory /dqdriver/), and these updates are alsoE                    included on OpenVMS Freeware V5.0, and OpenVMS ECO2C                    kits containing newer versions of the driver are1E                    available. Freeware V6.0 has a version of DQDRIVERpF                    that is newer than that of the OpenVMS Alpha V7.3-2  J                                                                        7-1 d             +                    Information on Utilitiesi        J                    release, with additional capabilities and with improved%                    error diagnostics.   D                    OpenVMS Alpha V7.3 and later include a version ofH                    SYS$DQDRIVER with the necessary IO$_DIAGNOSE support.  D           __________________________________________________________C           7.2  How do I access a Microsoft Windows floppy disk fromn                OpenVMS?e  G                    The HP Advanced Server (formerly known as PATHWORKS)eB                    for OpenVMS product includes an unsupported andH                    undocumented utility called PCDISK, and this tool canH                    read and write various Microsoft MS-DOS and MicrosoftG                    Windows FAT-format diskettes, and can usually access I                    FAT-format volumes written by other operating systems.   G                    ProGIS in Germany sells a product called VMove which/I                    supports DOS files on many different device types. For A                    more information, send mail to info@progis.de.   C                    Engineering Software has a product called VAKSATRH                    which will read, write, and erase files on MS-DOS FATG                    diskettes. Available for both VAX and Alpha. Contacte;                    ed@cityscape.co.uk for more information.   E                    MadGoat PC Exchange (PCX) is a utility for copyingiG                    files to and from MS-DOS and Microsoft Windows (FAT)eH                    format diskettes under OpenVMS, using an RX23 (3.5"),H                    RX26 (3.5"), or RX33 (5.25") diskette drive. For 3.5"H                    diskettes, high-density disks can be read or written;H                    double-density disks are read-only. Only high-density3                    disks are supported on the RX33.S  -                    o  http://www.madgoat.com/   F                    The Freeware package WINFX is available on Freeware?                    V6.0, and can read the FAT volume structure.   <                    o  http://www.hp.com/go/openvms/freeware/                            7-2 a  i          +                    Information on UtilitiesS      D           __________________________________________________________E           7.3  How do I play sound files on an AlphaStation? DECsoundb                doesn't work.  F                    Various of the more recent AlphaStation systems useH                    a different sound board (Microsoft Sound System) thanE                    the earlier DEC 3000 series systems, and DECsound,oC                    as supplied by DECwindows Motif, doesn't supporttG                    this board nor this interface. HP offers an optional C                    product, Multimedia Services (MMOV) for OpenVMS:F  9                    o  http://h18000.www1.hp.com/info/spd/=  H                       OpenVMS typically uses SPD 25.01.xx, SPD 41.87.xx,'                       and SPD 82.35.xx.   J                    which provides a replacement for DECsound for this cardJ                    as well as many other features (an AVI and MPEG player,/                    video capture support, etc.)a  ;                    Ensoniq sound support is also available.s  D           __________________________________________________________9           7.4  How do I read IBM EBCDIC tapes on OpenVMS?i  J                    Most (all?) IBM EBCDIC-based systems can read and writeD                    ANSI-labeled ASCII magtapes. Fixed-length recordsF                    (MOUNT /FOREIGN /BLOCKSIZE=512 /RECORDSIZE=512, forE                    one-block records) and the DCL COPY command can bewI                    used to transfer fixed-record-size text files out onto G                    tape media, or to read from fixed-record tape media.fG                    Please consult the IBM documentation for the details J                    and command syntax needed when reading and writing ANSIF                    media using IBM JCL or other applicable IBM command                    language.  I                    There exists various freeware around (TAPECOPY, ETAPE,CG                    TCOPY, MTEXCH) that can read and write EBCDIC tapes.-C                    Visit the Encompasserve (DECUS) website software E                    archives search engine and search for "EBCDIC" for                     details.k  0                    o  http://www.encompassus.org  B                    OpenVMS does not include an integrated tool forG                    EBCDIC tape processing, but does provide a characterpE                    conversion API useful within application programs.w  J                                                                        7-3               +                    Information on Utilitiesp        +                    One source for ETAPE is:c  <                    o  http://www.ualr.edu/ftp/vms/ETAPE_SRC/  G                    The OpenVMS Freeware V5.0 distribution included thise'                    ETAPE tool, as well.   D           __________________________________________________________6           7.5  How can I patch an OpenVMS Alpha image?  7                    Using the OpenVMS Freeware tool ZAP:p  H                    o  Look for the RMS_TOOLS directory on Freeware V5.0:<                       http://www.hp.com/go/openvms/freeware/  C                    tell ZAP to read a block (bucket) of informationRG                    based on the virtual block number (VBN), using X fordG                    hexadecimal. Dump yourself into the OpenVMS debugger H                    with R2 pointing into the buffer, EXAMINE/INSTRUCTIONI                    as needed, alter the buffer as required, GO to get out'G                    of the debugger and back into ZAP, and use the ZAP Wt6                    command to write the updated block.                                                                7-4    g                    J                    _______________________________________________________             8        DCL Details      D           __________________________________________________________5           8.1  DCL Symbols and OpenVMS Logical Names?n  J                    DCL symbols are programming-style variables implementedD                    within the DCL command interpreter, and these areC                    used both for programming and to provide commandaB                    verb synonyms. Symbols are local to the commandE                    interpreter operating within a particular process, J                    and are not shared. Lists of symbols can be copied intoG                    subprocesses during a subprocess creation operation, E                    but these symbols are neither copied back into the D                    parent process when the subprocess exits, nor are8                    symbols ever shared across processes.  D                    Symbols can be specified in and utilized in basicH                    mathematical operations, and bit-level operations areF                    available with the f$cvsi and f$cvui bit extractionB                    lexical functions, and with the square-bracketsF                    notation for bit insertion (see Section 8.13 for anG                    example), and with bitwise operators. Symbols are ofrH                    two basic types, STRING and INTEGER, and these (or anJ                    undefined symbol) can be differentiated with the f$typeF                    lexical function. DCL symbols can also be used as aI                    mechanism to abbreviate a DCL command verb, or an easye9                    way to invoke a DCL command procedure.t  B                    Symbols can have local or global scope within aE                    process, and scope is affected by nested procedureaG                    calls and DCL constructs such as CALL and SET SCOPE,bD                    but such discussions are beyond the scope of this                    section.   G                    OpenVMS Logical names can store device names, device E                    and directory specifications, rooted or searchlist H                    specifications, and full filenames. Logical names canE                    also store arbitrary data, but there are no native I                    mathematical or bitwise operators available. Analogous E                    to DCL symbols, process-local logical names can be H                    copied into subprocesses during a subprocess creation  J                                                                        8-1 e  p                              DCL Details        G                    operation, but these process-local logical names are G                    neither copied back into the parent process when the E                    subprocess exits, nor are these logical names ever                     shared.  H                    Logical names are implemented deep within the OpenVMSI                    executive, and are organized into logical name tables.vE                    Logical names can be stored in tables private to alG                    process( LNM$PROCESS, the process-local logical nameoJ                    table) , that can be shared among processes in the sameH                    job tree ( LNM$JOB, the job logical name table) or inJ                    logical name tables that are shared among larger groupsE                    of processes (eg: LNM$GROUP, the UIC group logicalsJ                    name table and LNM$SYSTEM, the system-wide logical nameJ                    table). Logical names are centrally intended to provideE                    various I/O-related capabilities, including deviceaJ                    independence and configuration customization-correctly-H                    written application programs can use logical names toJ                    avoid embedding specific device or device and directoryJ                    specifications, and to allow filename and configuration"                    customizations.  I                    One of the most powerful capabilities of logical namessG                    beyond the device independence provided involves the_C                    defaulting capabilities; you can use RMS parsing D                    (directly, or with mechanisms such as the f$parseH                    lexical function) to provide a filename and a defaultH                    filename. To provide the mechanism that allows SYSUAFD                    to be located in an arbitrary position or even anA                    arbitrary filename, a construct similar to theS%                    following is used:i  >                    $ UAF = F$PARSE("SYSUAF","SYS$SYSTEM:.DAT")  C                    This design allows the logical name SYSUAF to belH                    optionally defined, and - when present-to specify theE                    particular location and name of the file. PortionsIF                    of the full file specification that are omitted areI                    retrieved using the default translation of SYS$SYSTEM:v-                    and the file type of .DAT.E  G                    Logical names also have assigned processor modes, asaH                    some translations must be trustworthy. In the exampleI                    above, only trusted and privileged system users shouldSI                    be able to redirect the SYSUAF authorization database,                       8-2                                   DCL Details        G                    so any definition of the SYSUAF logical name must be J                    made in EXECUTIVE mode in a trusted logical name table.  G                    As for common OpenVMS terminology, logical names are H                    "defined" and the associated processing is refered toH                    as "translation", while symbols are "equated" and theI                    associated processing is refered to as "substitution". D                    "Lexical functions" are processing routines builtH                    into DCL, and typically prefixed with f$. Many of theI                    lexical functions are built upon correspondingly-namedm3                    system services, though not all.e  G                    Symbol substitution occurs only when the DCL commandaD                    interpreter is reading and processing the commandI                    input; for information on DCL symbol substitution, seetI                    Section 8.10. For program access, see the RTL routines86                    lib$set_symbol and lib$get_symbol.)  J                    For information on logical name translation, please seeH                    f$trnlnm lexical function and the DCL commands DEFINEF                    and DEASSIGN, as well as underlying system servicesF                    such as sys$trnlnm. Logical name translation occursE                    when requested, or as the file or I/O operation is                     started.t  E                    Please see the OpenVMS User's Guide in the OpenVMS H                    documentation set for a far more detailed description'                    of these constructs.p  E                    For related materials, please see Section 8.10 and_                     Section 8.11.  D           __________________________________________________________5           8.2  How do I run a program with arguments?   E                    The RUN command does not accept arguments. To passfF                    arguments to a program, you must use what is calledF                    a "foreign command", and either an explicit commandF                    as shown here, or an automatic foreign command. For                    example:   3                    $ unzip :== $disk:[dir]unzip.exeb                    $ unzip -?r  J                                                                        8-3 n  (                              DCL Details        G                    The leading $ in the equivilence name for the symbol D                    definition is what makes the DCL symbol a foreignD                    command. If the device and directory are omitted,*                    SYS$SYSTEM: is assumed.  G                    Under OpenVMS V6.2 and later, DCL supports automatic B                    foreign command definition via the logical nameG                    DCL$PATH. An example of a definition of this logicalo                    name is:   M                    $ DEFINE DCL$PATH SYS$DISK:[],ddcu:[mytooldir],SYS$SYSTEM:   G                    DCL will first look for a command in the DCL command E                    table, and if no match is found and if DCL$PATH is H                    defined, it will then look for command procedures andH                    executable images with filenames matching the commandH                    specified, in the directories specified via DCL$PATH.G                    The first match found is invoked, and under OpenVMS, I                    the DCL$PATH support will cause a command procedure to E                    be activated in preference to an executable image.   A                    For more information on foreign commands or on E                    automatic foreign command support, see the OpenVMS_!                    User's Manual.i  )                    See also Section 10.3.r  F                    If you want to create a detached process that takesJ                    arguments from a command line, it must be run under theI                    control of a command line interpreter (CLI) (typicallytF                    DCL). This is done by placing the command line in aH                    file, specifying SYS$SYSTEM:LOGINOUT.EXE as the imageI                    to run and the command file as the input. For example:g  2                    $ OPEN/WRITE CMD TEMP_INPUT.COM6                    $ WRITE CMD "$ MYCOMMAND arguments"                    $ CLOSE CMDK                    $ RUN/DETACHED SYS$SYSTEM:LOGINOUT /INPUT=TEMP_INPUT.COMd  F                    Various OpenVMS library calls (such as lib$spawn(),E                    cli$dcl_parse(),  and the C library system() call) G                    require access to a command line interpreter such asnI                    DCL to perform requested actions, and will not operateg-                    if a CLI is not available.                       8-4                                   DCL Details        E                    When a CLI is not available, these calls typicallydF                    return the error status SS$_NOCLI. And as mentionedH                    above, invoke the image LOGINOUT to cause a CLI (suchF                    as DCL) to be mapped into and made available in the1                    context of the target process.t  J                    For examples of how TCP/IP Services sets up its foreignB                    commands (which includes tools such as uuencodeF                    and uudecode), please see the DCL command procedure9                    SYS$STARTUP:TCPIP$DEFINE_COMMANDS.COM.e  )                    Also see Section 8.12._  D           __________________________________________________________1           8.3  How can I clear the screen in DCL?   C                    The simplest way is the TYPE/PAGE NLA0: command.   F                    You can set up a symbol to clear the screen in your                    LOGIN.COM:o  ,                    $ CLS :== TYPE/PAGE NLA0:  D           __________________________________________________________B           8.4  Using REPLY/LOG from DCL? Disabling Console OPCOMs?  H                    Your terminal must be enabled as an operator terminalF                    before the REPLY/LOG command can be used, but a DCLF                    procedure (batch command file, system startup, etc)E                    does not have an associated terminal. To make thiskG                    work, use the following sequence to enable the OPA0:_G                    console as the operator terminal, then the REPLY/LOGS,                    command will be accepted:  3                    $ DEFINE/USER SYS$COMMAND _OPA0:l                    $ REPLY/LOG3                    $ DEFINE/USER SYS$COMMAND _OPA0:o!                    $ REPLY/ENABLEt  G                    To disable the system console terminal (OPA0:) as ann@                    operator terminal, use the following command:  3                    $ DEFINE/USER SYS$COMMAND _OPA0: "                    $ REPLY/DISABLE  J                                                                        8-5 u  n                              DCL Details        H                    Also see SYLOGICALS.COM (and SYLOGICALS.TEMPLATE) forE                    information on configuring the behaviour of OPCOM,uD                    including the (default) use of the system consoleD                    (OPA0:) as an operator terminial and the specificI                    contents and behaviour of the system operator log fileg                     OPERATOR.LOG.  D           __________________________________________________________8           8.5  How do I generate a random number in DCL?  @                    With V7.3-2 and later, f$unique can be usefulF                    here. Alternatively, here is a pseudo-random numberH                    generator, just do a GOSUB RAND and the global symbolG                    RANDOM will contain a randomly generated number. You H                    can feed the generator a ceiling value (__CEIL)  or a%                    new seed (__SEED).   M           $! RAND - returns a positive random number ("RANDOM") between 0 andR           $!        __CEIL - 1. -           $! sharris-at-sdsdmvax.fb3.noaa.gov            $ RAND:            $f&           $ IF F$TYPE(__SEED) .EQS. ""           $ THEN7           $     ! seed the random number generator, ...i"           $     __NOW = F$CVTIME()0           $     __HOUR = 'F$EXTRACT(11,2,__NOW)'2           $     __MINUTE = 'F$EXTRACT(14,2,__NOW)'2           $     __SECOND = 'F$EXTRACT(17,2,__NOW)'0           $     __TICK = 'F$EXTRACT(20,2,__NOW)'           $eK           $     __SEED == __TICK + (100 * __SECOND) + (6000 * __MINUTE) + -l$                    (360000 * __HOUR)N           $     ! the generator tends to do better with a large, odd seed, ...)           $     __SEED == (__SEED .OR. 1)e           $     ! clean up, ...f$           $     DELETEX/SYMBOL __NOW%           $     DELETEX/SYMBOL __HOUR:'           $     DELETEX/SYMBOL __MINUTE='           $     DELETEX/SYMBOL __SECOND %           $     DELETEX/SYMBOL __TICKo           $ ENDIF            $t?           $ IF F$TYPE(__CEIL) .EQS. "" THEN __CEIL = %X3FFFFFFFs                      8-6 e  e                              DCL Details                   $o(           $ __SEED == __SEED * 69069 + 1           $tA           $ RANDOM == (__SEED.AND.%X3FFFFFFF)/(%X40000000/__CEIL)            $            $ RETURN  D           __________________________________________________________,           8.6  What does the MCR command do?  H                    The MCR is an artifact of RSX compatibility mode, theH                    operating system from which OpenVMS is descended. MCRE                    is the Monitor Console Routine, and the command iseI                    intended to activate RSX compatibility mode utilities.eE                    When used on OpenVMS, the command is most commonly G                    used to run the specified image and-because the toolnG                    detects the image is not a compatibility-mode image- D                    it acts as a form of RUN command with the defaultH                    file specification of SYS$SYSTEM:.EXE. MCR passes anyI                    (optional) command line arguments in a fashion similar 8                    to a foreign command. In other words:                       $ MCR FOO BAR  $                    is equivalent to:  "                     $ FOO :== $FOO                     $ FOO BARo  I                    MCR is not documented. Use of a foreign command or thexH                    DCL$PATH mechanism is preferred. For details on this,#                    see Section 8.2.g  D           __________________________________________________________9           8.7  How do I change the OpenVMS system prompt?   G                    You can use the SET PROMPT command for this purpose. J                    SET PROMPT sets the DCL prompt to the specified string.  E                    When you want to display variable information, yousD                    will need to establish a tie-in that provides theE                    information to the SET PROMPT command as required.   C                    If you wish to display the default directory forrE                    instance, you will have to establish a tie betweenaJ                    the SET DEFAULT command and the SET PROMPT commands, asI                    there is no direct way to get the default directory as   J                                                                        8-7                                   DCL Details        I                    the DCL prompt. You can easily acquire or create a setII                    of DCL command procedures that perform the SET DEFAULTdG                    and SET PROMPT for you. These DCL command proceduress/                    often use a command such as:i  :                    $ set prompt='f$environment("default")'  J                    More advanced users could implement a system service orH                    other intercept, and use these tools to intercept theE                    directory change and reset the prompt accordingly.iB                    (This approach likely involves some kernel-modeD                    programming, and requires write access to various9                    undocumented OpenVMS data structures.)E  J                    There are related tools available from various sources,5                    including the following web sites:   6                    o  ftp://ftp.hhs.dk/pub/vms/setpmt/  ?                    o  ftp://ftp.tmesis.com/sys_service_hook.src   J                    o  James F. Duff has also made available a Macro32 toolJ                       known as TIME_PROMPT, a tool that sets the prompt to.                       the current system time.  C                    o  Many folks have contributed DCL procedures tosE                       perform this task. Visit the newsgroup archivesw3                       for information and examples.e  D           __________________________________________________________C           8.8  Can I do DECnet task-to-task communication with DCL?o  1                    Yes, you can do this with DCL.   H                    The OpenVMS DECnet documentation shows various simpleI                    examples using the task object and the TYPE command to_H                    trigger the execution of a DCL command procedure on aH                    remote node. An example DCL command procedure that isH                    rather more advanced than using the TYPE command as aB                    trigger is included in the Ask The Wizard area:  H                    o  http://www.hp.com/go/openvms/wizard/ (retired; use"                       ITRC forums)                      8-8 r                                 DCL Details        D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the availablehF                    ATW Wizard.zip archive, please see Section 3.8. ATWF                    has been superceded (for new questions) by the ITRCD                    discussion forums; the area remains available for                    reference.i  H                    DCL does not include support asynchronous I/O, thus aJ                    predetermined protocol or a predetermined "turn-around"I                    command sequence must be implemented in order to avoid J                    protocol deadlocks-cases where both tasks are trying toH                    write or both tasks are trying to read. The task thatJ                    is writing messages to the network must write (or writeH                    and read) a predetermined sequence of messages, or itI                    must write a message that tells the reader that it can H                    now start writing messages. (This is the essence of a>                    basic half-duplex network protocol scheme.)  D           __________________________________________________________=           8.9  How can I get the width setting of a terminal?A  ;                    $ width = f$getdvi(terminal,"DEVBUFSIZ")l  D           __________________________________________________________9           8.10  Why doesn't DCL symbol substitution work?e  E                    The DCL symbol substitution processing occurs onlyrD                    at the DCL prompt, not within data and not withinG                    files. If you wish to perform symbol substitution inhE                    this environment, you typically write a small fileeD                    containing the command(s) and data to be invoked-D                    potentially only the data-and you then invoke theE                    created procedure or reference the specified data.   D                    In this case, use of a file containing nolinemodeH                    commands or other techniques might be useful-you willG                    want to ensure that the text editor you use does notlH                    attempt to use screen mode or similar, as this is notE                    generally considered adventageous within a command                     procedure.t  A                    Tools such as FTP have alternatives: COPY/FTP.     J                                                                        8-9 _  _                              DCL Details        F                    DCL symbol substitution occurs in two passes, usingH                    the ampersand and the apostrophe. In most cases, onlyJ                    the apostrophe is necessary. In a few cases-such as theJ                    DCL PIPE command-you will may need to use the ampersandI                    to get the substitution to work. The following exampleVJ                    uses ampersand substitution to transfer the contents of2                    the header into a logical name:  W                    $ PIPE CC/VERSION | (READ SYS$PIPE hdr ; DEFINE/JOB/NOLOG hdr &hdr )   H                    A logical name (in the job logical name table; sharedG                    by all processes in the current job) was used as DCL"I                    symbols cannot be returned back out from a DCL PIPE orN,                    other spawned subprocess.  D                    For related materials, please see Section 8.1 and                     Section 8.11.  D           __________________________________________________________7           8.11  How can I substitute symbols in a PIPE?C  E                    Use DCL ampersand substitution, and not apostrophe+                     substitution.  M           $ pipe show system | search sys$input opcom | (read sys$input pid ; F               pid=f$element(0," ",pid) ; define/system opcom_pid &pid)           $ show log opcom_pid9               "OPCOM_PID" = "0000020B" (LNM$SYSTEM_TABLE)   D           __________________________________________________________?           8.12  Use of RUN/DETACH, LOGINOUT, and logical names?   G                    With a command to create a detached process such as:   K                    $ RUN/DETACHED SYS$SYSTEM:LOGINOUT /INPUT=TEMP_INPUT.COM   I                    If you are trying to use a logical name as the /INPUT,$B                    /OUTPUT or /ERROR on a RUN/DETACH command, thenE                    you must translate the logical name specifications3E                    to physical references before passing them, or the_J                    definitions must reside in a logical name table that is8                    visible to the newly-created process.  F                    Also note that LOGINOUT only creates the SYS$LOGIN,H                    SYS$LOGIN_DEVICE, and SYS$SCRATCH logical names if itI                    is processing a login that is based on the contents of.J                    a SYSUAF record-without access to the associated SYSUAFI                    record, this information is not available to LOGINOUT.                       8-10  b  h                              DCL Details        E                    (If you want to see these particular logical names H                    created, then please specify the /AUTHORIZE qualifier0                    on the RUN/DETACHED command.)  D                    If you do not specify LOGINOUT as the image, thenI                    there is no easy way to get these logical names. Also,lF                    any logical names that are used in the target imageD                    file specification must also be in a logical nameE                    table accessible (by default) by the newly-creatediH                    detached process. Shared tables include the group (ifG                    the process is in the same UIC group) and the system H                    table. (If the target process is to be in another UICH                    group, a suitablly privileged user or application canG                    create the necessary logical name(s) directly in theV3                    other group logical name table.)t  D                    When in doubt, create a short DCL command file asE                    input, and use a SHOW LOGICAL and similar commandstG                    to examine the context. (And use physical device andtI                    directory references on the RUN/DETACH of the LOGINOUTrG                    image, when specifying this command file as /INPUT.) D                    Also remember to check both security auditing andG                    system accounting when troubleshooting problems with "                    the RUN/DETACH.  (                    Also see Section 8.2.  D           __________________________________________________________@           8.13  How to use escape and control characters in DCL?  G                    To write a message and then the bell character, use:   "                    $ bell[0,7] = 74                    $ write sys$output "Hello''bell'"  /                    To write blinking text, use:   "                    $ esc[0,7] = 27+                    $ text = "Blinking Text" @                    $ write sys$output "''esc'[5m''text'''esc'[m"  @                    Also see sections Section 11.6, Section 12.1.    J                                                                       8-11 l                       J                    _______________________________________________________             9        Files      D           __________________________________________________________)           9.1  How can I undelete a file?   H                    OpenVMS doesn't have an "undelete" function. However,G                    if you are quick to write-protect the disk or if youdJ                    can guarantee that no new files get created or existingE                    files extended, your data is still on the disk andoF                    it may be possible to retrieve it. The FLORIAN toolJ                    available from various websites can potentially recoverJ                    the file, see question Section 13.1 for pointers. OtherG                    alternatives here include the DFU tool, available onp<                    the OpenVMS Freeware CD-ROM distribution.  H                    If you are setting up a user environment for yourselfJ                    or for others, it is quite easy to use DCL to intercept6                    the DELETE command, using a symbol:  8                    $ DEL*ETE :== @SYS$LOGIN:MYDELETE.COM  @                    The DELETE symbol will cause the procedure toA                    be invoked whenever the user enters the DELETE G                    command, and it can copy the file(s) to a "trashcan"tE                    subdirectory before issuing a "real" DELETE on the)H                    files. Other procedures can retrieve the file(s) fromJ                    the "trashcan" subdirectory, and can (and should) cleanH                    out the "trashcan" as appropriate. (Realize that thisE                    DELETE symbol can interfere with DELETE/GLOBAL and /                    other similar DCL commands.)s  D           __________________________________________________________I           9.2  Why does SHOW QUOTA give a different answer than DIR/SIZE?w  G                    DIRECTORY/SIZE doesn't take into account the size ofIF                    file headers which are charged to your quota. Also,G                    unless you use DIRECTORY/SIZE:ALL, you will see only F                    the "used" size of the file, not the allocated sizeG                    which is what gets charged against your quota. Also, ;                    you may have files in other directories.   J                                                                        9-1                                   Files        ;                    $ DIRECTORY/SIZE=ALL/GRAND [username...]PI                    Grand total of D1 directories, F1 files, B1/B2 blocks.)=                    $ DIRECTORY/SIZZ=ALL/GRAND [-]username.DIRoD                    Grand total of 1 directory, 1 file, B3/B4 blocks.                    $ SHOW QUOTA C                    User [username] has B5 blocks used, B6 availablelP                    of B7 authorized and permitted overdraft of B8 blocks on disk  D                    If the user has no files in other directories andH                    all file-headers are only 1 block, then the following                     should apply:  "                      B5=B2+B4+F1+1  G                    If the diskquota has drifted out of synchronization, H                    then the system-manager can force a quota rebuild-dueE                    to various factors, the quota file can potentially F                    drift from the actual use over time, and a periodicE                    rebuild can be performed at appropriate intervals.   D                    Also be aware that the DIRECTORY/SIZE command canH                    report larger values than might otherwise be expectedF                    when used to evaluate files and/or directories thatF                    are alias links-such as the system roots on OpenVMSC                    system disks-as the command reports a total that F                    is cumulative over all of the files and directoriesC                    examined, without regard for which ones might betF                    alias entries and which are not. (In other words, aG                    DIRECTORY/SIZE of an entire OpenVMS system disk willnF                    report a disk useage value larger than the (usuallyC                    more accurate) value reported by the SHOW DEVICESI                    command. This as a result of the alias entries linkingoH                    each SYS$SYSDEVICE:[SYSCOMMON]SYS*.DIR directory fileD                    and the SYS$SYSDEVICE:[000000]VMS$COMMON.DIR file                    together.)   D           __________________________________________________________I           9.3  How do I make sure that my data is safely written to disk?   E                    If your application must absolutely guarantee thatOG                    data is available, no matter what, there's really noEI                    substitute for RMS Journaling and host- or controller-_J                    based shadowing. However, you can achieve a good degreeG                    of data integrity by issuing a SYS$FLUSH RMS call at G                    appropriate times (if you're using RMS, that is.) If I                    you're using a high-level language's I/O system, checko                      9-2 o  t                              Files        I                    that language's documentation to see if you can accessuI                    the RMS control blocks for the open file. In C you cant0                    use fflush followed by fsync.  E                    For details on disk bad block handling on MSCP and H                    on SCSI disk devices, please see Ask The Wizard (ATW)                     topic (6926).  H                    o  http://www.hp.com/go/openvms/wizard/ (retired; use"                       ITRC forums)  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the available_F                    ATW Wizard.zip archive, please see Section 3.8. ATWF                    has been superceded (for new questions) by the ITRCD                    discussion forums; the area remains available for                    reference.   D           __________________________________________________________J           9.4  What are the limits on file specifications and directories?  H                    A file specification has an aggregate maximum size ofE                    255 characters (NAM$C_MAXRSS) at present, assumingbC                    ODS-2 limits and traditional DCL process parsing C                    settings (SET PROCESS/PARSE_STYLE). The node and I                    device specification may be up to 255 characters each-mF                    file name and file types may be up to 39 charactersG                    each. File versions are from 1 through 32767, thoughtG                    0 (latest version), -0 (oldest version) and -n (n'th I                    previous version) can be used in most contexts. A file I                    specification may not have more than 8 directories andeI                    subdirectories or-with a rooted directory, two sets ofrH                    eight are possible-and while it is possible to createH                    subdirectories of greater depth, accessing them underH                    ODS-2 is somewhat problematic in most cases, and thus%                    should be avoided.m  =                    Under ODS-5 with extended DCL parsing (SET C                    PROCESS/PARSE_STYLE), the filename length limits F                    are up around 4,095 (NAML$C_MAXRSS) characters, and=                    directories can be around 255 levels deep.       J                                                                        9-3 c  i                              Files        E                    Application developers should use OpenVMS-suppliednJ                    routines for parsing file specifications - this ensuresE                    that changes in what is allowable will not tend toiI                    break your application. Consider that various parts ofuI                    the file specification may contain quoted strings withsG                    embedded spaces and other punctuation! Some routineslH                    of interest are SYS$FILESCAN, SYS$PARSE and LIB$TRIM_E                    FILESPEC. For further information, see the OpenVMS .                    Guide to File Applications.  A                    Performance of larger directory files improvesuF                    (greatly) with OpenVMS V7.2 and later-operations onG                    directory files of 128 blocks and larger were rather H                    slower on earlier OpenVMS releases due to the smallerG                    size of the directory cache and due to the directory (                    I/O processing logic.  F                    For fastest directory deletions, consider a reverseI                    deletion-delete from the last file in the directory topI                    the first. This reversal speeds the deletion operationaF                    by avoiding unnecessary directory I/O operations asH                    the files are deleted. Tools such as the Freeware DFUI                    can be used for this purpose, as can various availableO9                    reverse-DELETE DCL command procedures.n  )                    Also see Section 5.44.   D           __________________________________________________________G           9.5  What is the largest disk volume size OpenVMS can access?   @                    One Terabyte (TB; 2**31 blocks of 2**9 bytes;D                    0x07FFFFFFF blocks). 255 volumes in a volume set.E                    The largest contiguous allocation possible for anye9                    particular file is 0x03FFFFFFF blocks.l  H                    Prior to the release of V6.0, the OpenVMS file systemH                    was limited to disk volumes of 8.38 GB (2**24 blocks,,                    16777216 blocks) or less.  I                    On some systems, there are restrictions in the consolesJ                    program that limit the size of the OpenVMS system disk.C                    Note that data disks are not affected by consoleaB                    program limits. For example, all members of theF                    VAXstation 3100 series are limited to a system diskH                    to 1.073 GB or less due to the console, though largerF                    data disks are possible. This limit due to the SCSI                      9-4 S  S                              Files        I                    drivers used by and built into the console ROM to readeJ                    the OpenVMS bootstrap files, and these same drivers areF                    also used by OpenVMS to write the system crashdump.  D                    There are numerous discussions of this VAXstationE                    3100 in the comp.os.vms newsgroup archives. PleaseyI                    use Google newsgroup search to search the archives foroG                    further details, for discussions of the workarounds,nG                    and for details of the potential for a simple failedmD                    bootstrap and particularly for discussions of theB                    potential for severe system disk corruptions on                    crashes.   C                    Some SCSI disks with capacities larger than 8.58 H                    gigabytes (GB) will require the use of an OpenVMS ECOE                    kit (eg: ALPSCSI04_062 or later; see Section 14.25iG                    for details) for new SCSI device drivers. Failure togG                    use this ECO can cause "rounding errors" on the SCSIqH                    disk device capacity-OpenVMS will not use nor displayG                    the full capacity of the drive-and "%sysinit-e-erroroF                    mounting system device status equals 000008C4" (8C4G                    -> "%SYSTEM-?-FILESTRUCT, unsupported file structuresG                    level") errors during bootstrap. (One workaround for H                    the bootstrap when the bitmap is located far into theI                    disk is the use of INIT/INDEX=BEGIN.) The problem here I                    involves the particular extensions and fields used for G                    larger capacity disks within the SCSI specifications A                    and within the various intepretations of same.   -                    For ATA (IDE) disk drives:   J                    o  Versions of SYS$DQDRIVER *BEFORE* X-15 topped out at                       8.455 GB.A  G                       Fixed drivers (equal or greater than "X-15") weres!                       shipped in:c  7                      o  OpenVMS Alpha V7.2-1, and laterI  7                      o  V7.2 UPDATE V1.0 ECO, and later   9                      o  V7.1-2 UPDATE V1.0 ECO, and later   9                      o  V7.1-2 UPDATE V3.0 ECO, and laterd  J                                                                        9-5 l  d                              Files        H                    o  The newer SYS$DQDRIVER driver operates to disks upH                       to 33 GB without (known) problems, and effectivelyE                       works with rather larger disks (up to circa 137nG                       GB) but is known to report an incorrect number oft9                       "cylinders" with disks above 33 GB.h  G                    See Section 14.4.4.2 for additional ATA SYS$DQDRIVERo                    information.   E                    Be aware that a known restriction in certain older J                    versions of the Alpha SRM Console prevents booting mostF                    ATA (IDE) drives larger than 8.455 GB, depending onE                    exactly where the various files are located on theaD                    volume. Updated SRM consoles for systems with SRMG                    and ATA (IDE) drive support are (will be) available.rE                    (OpenVMS Engineering has successfully bootstrapped I                    20GB ATA (IDE) disks using the appropriate SRM console                     version.)  1                                              Note.  A                       All disk-related listed in this section are D                       stated in units of "disk (base ten) gigabytes"G                       (1 GB = 10^9 bytes) and not in units of "softwarei@                       (base two) gigabytes" (1 GB = 2^30; 1 GB =F                       1073741824.) bytes. Please see Section 14.25 forC                       details of the nomenclature and of the units.   I                    Be aware that larger disks that are using an extensioniD                    of SCSI-2- disks that are using a mode page fieldG                    that the SCSI-2 specifications normally reserved foriH                    tape devices-to permit a larger disk volume size willE                    require a SCSI driver update for OpenVMS, and thisoG                    change is part of V7.1-2 and later, and also part ofdE                    ALPSCSI07_062 and later. (These larger disks disks I                    will typically report a DRVERR, or will see the volumerH                    size "rounded down".) SCSI disks larger than 16777216J                    blocks cira 8.455 GB (base ten); 8GB (base two) requireJ                    this ECO, or require the use of OpenVMS Alpha V7.1-2 or                    later.   C                    Applications written in C can be limited to fileeF                    sizes of two gigabytes and less, as a result of theG                    use of longword values within C file operations, and D                    specifically off_t. This restriction is lifted inH                    OpenVMS V7.3-1 and later, and with the application of                      9-6                                   Files        J                    the C ECO kits available for specific earlier releases.I                    The use of a longword for off_t restricts applicationsaG                    using native C I/O to file sizes of two gigabytes orrI                    less, or these applications must use native RMS or XQP81                    calls for specific operations.s  9                    Also see Section 14.13, Section 14.25.s  D           __________________________________________________________E           9.6  What is the maximum file size, and the RMS record size                 limit?   E                    RMS can store individual files of a size up to the H                    maximum supported volume size. Under OpenVMS V6.0 andG                    later, the volume size and the RMS maximum file sizemB                    limit is 2**31 * 512 bytes-one terabyte (1 TB).  D                    "Use a volume set to provide a large, homogeneousI                    public file space. You must use a volume set to create D                    files that are larger than a single physical diskH                    volume. (The file system attempts to balance the loadI                    on the volume sets, for example, by creating new files F                    on the volume that is the least full at the time.)"  H                    "You can add volumes to an existing volume set at anyI                    time. The maximum number of volumes in a volume set is I                    255." Further, with a 255 member bound-volume set, theYF                    theoretical maximum limit of files is 4,261,478,145B                    files, less the directories and reserved files.  E                    The RMS formats-sequential, relative, and indexed- G                    are limited by the one terabyte maximum volume size. H                    RMS relative files are further limited to a number ofF                    records that will fit in 32 bits-4 billion records.F                    Sequential and indexed formats do not have a record                    limit.   :                    Also see Section 2.17.1, Section 14.25.            J                                                                        9-7 n  e                              Files      D           __________________________________________________________D           9.7  How do I write CD-Recordable or DVD media on OpenVMS?  F                    How to create CD-R, CD-RW, DVD-R, DVD+R, DVD-RW, or+                    DVD+RW media on OpenVMS?L  H                    For information on CD and DVD optical media drives onH                    OpenVMS, please see Section 14.29. For information onH                    the creation of OpenVMS media and of OpenVMS bootableG                    media, a full step-by-step sequence is documented incJ                    the OpenVMS Ask The Wizard topic (9820). An abbreviated<                    version of the sequence is included here.  B                    Recording (writing) of CD and DVD optical mediaF                    requires a recording or media mastering applicationJ                    or tool, and both commercial and non-commercial optionsE                    are available. For OpenVMS V8.3 and later, see theOI                    COPY/RECORDABLE_MEDIA command available within OpenVMSnH                    itself. Alternatively, please see CDRECORD (both non-G                    DVD and DVD versions are available, and at least one J                    commercial version is available), and also see DVDwriteE                    (commercial) or DVDRECORD (open source). A port of3C                    CDRECORD is present in OpenVMS V7.3-1 and later._  H                    o  Acquire a comparatively recent SCSI-based or ATAPIE                       (IDE) CD-R or DVD-R/RW or DVD+R/RW drive. OlderOH                       drives can be very problematic, while newer drivesI                       are readily available, and are cheap and very fast, E                       and tend to have better compliance with current=H                       standards. Use of older drives is not recommended.J                       Related device requirements information is available'                       in Section 14.29.E  C                    o  Get the most recent LDDRIVER available on the I                       Freeware, or activate and use the LD version latent J                       in OpenVMS Alpha V7.3-1 and V7.3-2 by loading the LDH                       command verb (look within SYS$MANAGER:CDRECORD.COMJ                       for related details), or use the integrated LD found0                       in OpenVMS V8.2 and later.  I                       In particular, you will want to use the current ECO H                       kit for LDDRIVER (as available), or the version ofH                       LD distributed with V8.2. The OpenVMS V8.2 versionE                       of LDDRIVER was also kitted on Freeware V7.0 asc                       LD071.                      9-8 R  c                              Files        H                       If you are not running OpenVMS V8.2, the specifiedC                       LD071 kit or later, or a current ECO with the H                       update, you will want to upgrade, or you will want-                       to use the DCL command:m  <                       SET FILE/CACHING_ATTRIBUTES=NO_CACHING  ?           on the LD partition file. This is a workaround for anpG           incompatibility found between older LDDRIVER versions and then           XFC caching support.  C                       As an alternative to LD and LDDRIVER, you can J                       acquire and load the VD64 package from the Freeware.  E                    o  Use the COPY/RECORDABLE_MEDIA command availableR?                       within OpenVMS V8.3 and later, or use the C                       version of CDRECORD built in V7.3-1 or later, B                       or obtain and utilize one of the open sourceE                       or commercial versions of the CDRTOOLS/CDRECORD C                       or DVDRTOOLS/CDRECORD tools, or other similar_D                       recording tools. Freeware V6.0 distribution. (I                       http://www.hp.com/go/openvms/freeware/ ) An OpenVMSoI                       port of the cmcd CD audio ripper is also reportedly 9                       available. http://www.amb.org/xmcd/t  J                       Versions of CDRECORD (non-DVD) are latent in OpenVMSD                       Alpha V7.3-1 and later. Commercial versions ofH                       CDDRECORD-with DVD capabilities-are also availableJ                       for various platforms, and particularly a variant ofI                       CDRECORD known as CDRECORD-ProDVD. COPY/RECORDABLE_tA                       MEDIA is built into OpenVMS V8.3 and later.a  ?                       Beware the tool chosen: some versions and F                       configurations of CDRECORD can record DVD media,I                       as can the DVDRECORD package, as can the commercialeH                       DVDwrite package. Many versions of CDRECORD cannotI                       record DVD media, including the version of CDRECORD.D                       latent within OpenVMS and the version found onE                       Freeware V6.0; these versions cannot record DVD'                       media.  F                    o  Build the contents of the disk on the LD or VD64'                       device partition.e  J                    o  Use the chosen recording tool to record the contentsC                       of the LD or VD64 partition directly onto the %                       optical medium.u  J                                                                        9-9 u  .                              Files        C                    Alternatively, consider the following command one2                    OpenVMS Alpha V7.3-1 and later:  1                    @SYS$MANAGER:CDRECORD.COM HELP   H                    While folks have had success getting PC-based CD-R/RWE                    or DVD-R/RW or DVD+R/RW tools to work with OpenVMSwH                    partitions, it is far easier and more reliable to useJ                    the OpenVMS-based versions of these tools and directly-I                    attached devices. If you use a Windows-based tool, yougG                    will want to specifically select its raw mode, image I                    mode, or block-copy mode, depending on the terminology D                    within the particular tool. The transfer mode andG                    selections is variously refered to as a disk-at-onceeH                    (DAO) 2048-byte block ISO Mode 1 raw/image/block data'                    disk recording mode.a  A                    More details: Creation of CD recordable or DVDcD                    recordable media under OpenVMS typically involvesF                    one of two approaches: the use of the optional CD-RJ                    (`Scribe') capabilities available for the InfoServer orG                    other "offline" hardware packages (PC-based packageseH                    will be included in this), or the use of a host-basedH                    package such as the CDRECORD or COPY/RECORDABLE_MEDIAI                    (V8.3 and later) or other utilities, including OpenVMSzJ                    ports of common open-source tools made available by Dr.I                    Eberhard Heuser-Hofmann and various others. Commercial G                    packages and options are also available. Dr. Heuser- H                    Hofmann has DVDwrite , a commercial package which canI                    record DVD media. ( http://home.tiscali.de/dvd4openvms                     )  I                    OpenVMS can read ODS-2, ODS-5, and ISO-9660 format CD-dH                    ROMs and DVD-ROMs directly. (If you are very careful,F                    you can create a dual-format CD-R; a CD-R with bothJ                    ODS-2 and ISO-9660 or both ODS-5 and ISO-9660 or both.)  I                    OpenVMS does not support ISO-9660:1999, nor the JolietrH                    or Rock Ridge extensions to ISO-9660, nor can OpenVMS5                    decrypt copy-protected video DVDs.   C                    InfoServer hardware configurations are no longer E                    available from HP, but may potentially be acquired E                    through other means; as used equipment. InfoServer G                    support also has very specific CD-R recording device                       9-10l E  F                              Files        D                    prerequisites, and these recording devices are no.                    longer generally available.  H                    Packages related to the use of DVD archiving are alsoF                    available, see the multi-volume capabilities of the/                    DVDarchive/restore Freeware.   R                    http://www.geocities.com/SiliconValley/Lakes/9999/vmscdwri.html  G                    Additional information is available at the followingt                    sites:y  :                    o  http://www.djesys.com/vms/cdrom.html  J                    o  http://www.cd-info.com/CDIC/Technology/CD-R/vms.html  8                    o  http://www.faqs.org/faqs/cdrom/cd-4                       recordable/part1/preamble.html  2                    o  http://www.tmesis.com/CDrom/  3                    o  http://www.tditx.com/~odsiso/m  G                    U.S. Design offers a package that includes the toolswI                    necessary to create a CD or DVD-R with either ISO-9660sE                    or ODS-2 format, for standalone CD-R/RW, DVD-R, or H                    DVD+R/RW drives, for recent OpenVMS versions. Details$                    are available at:  .                    o  http://www.usdesign.com/  B                    Also see Section 9.7.2 for details on access to9                    recorded media on older CD-ROM drives.s  '           _____________________________ 2           9.7.1  CD and DVD notation, terminology?  D                    CD-ROM is pre-recorded Compact Disk media, and isE                    the original and oldest CD format. The original CDtI                    media was physically stamped, a recording process thatmF                    is now largely reserved to the highest-volume media-                    reproduction requirements.l  E                    CD-R is CD Recordable, a write-once storage medium G                    that can be read by all but the oldest of CD drives;mH                    a format which can be read and often even recorded by%                    most CD-RW drives.   J                                                                       9-11 i  8                              Files        H                    CD-RW is CD ReWritable, a format which is readable byI                    many CD drives and by most CD-R drives, and with medianH                    that can be recorded and re-recorded by CD-RW drives.  G                    CD media recording speeds are listed as multiples of=F                    150 kilobytes per second, so a 10X drive records atH                    1500 kilobytes (1.5 megabytes) per second. 600 MB (70H                    minutes) and 700 MB (80 minutes) recording capacitiesH                    are both widely available. The minutes designation isF                    derived from the traditional audio-format recording4                    capacity of the particular media.  H                    DVD-R/RW is the older of two common Digital VersatileF                    Disk recording formats, and the DVD-R Recordable orJ                    DVD-RW ReWritable media can be read by many DVD drives.E                    As with CD-R formats in older CD drives, older DVDtI                    and particularly first-generation DVD players may havet6                    problems reading this media format.  B                    DVD+R/RW is the newer of the two common DigitalB                    Versatile Disk recording formats, and the DVD+RD                    Recordable or DVD+RW ReWritable media can be readD                    by many DVD drives. Akin to DVD-R/RW media, olderH                    and particularly first-generation DVD drives can have6                    problems reading this media format.  F                    The DVD Plus-series drives and media tend to recordD                    faster than Minus drives, as (as of this writing)F                    the Plus (+) drives do not require an initial mediaI                    formatting pass and the Minus (-) drives do. While theoG                    appropriate Plus (+) or Minus (-) DVD raw media must E                    be chosen for the particular DVD recorder (and DVDlH                    recording drives that are compatible with and capableE                    of using both Plus and Minus media are available),cE                    the resulting recorded media is generally readable G                    (playable) in all recent DVD drives and DVD players,eH                    regardless of type. (Compatibility is best within theF                    same media-series devices of course, but be certainG                    to verify compatibility across devices regardless of F                    the particular device or particular recording media                    chosen.)                           9-12u    a                              Files        F                    Presently Plus (+) media is slightly more expensiveD                    than Minus (-), but with the prices of all CD andE                    all DVD media continuing to consistently fall, the I                    differences in DVD media costs are becoming irrelevent D                    for all but the production of huge volumes of DVD                    media.i  J                    The rated DVD recording speeds are in multiples of 1353G                    kilobytes per second, thus a DVD 1X drive is roughly_F                    equivalent to a CD 9X drive in I/O requirements and"                    transfer speed.  H                    DVD drive recording speed can and does vary. DVD diskJ                    drive recording speed is limited by the rated recordingG                    speed of the media used, so the slower (and cheaper) I                    DVD media will not record any more quickly in a faster D                    drive. A 2.4X DVD drive loaded with 1X media will                     record at 1X.  '           _____________________________ I           9.7.2  Use of RRD42 and other older (embossed-media) CD drives?   I                    The RRD42 series SCSI CD-ROM drive is sufficiently old_F                    that it can have problems processing CD-R and CD-RWF                    media. Other very old CD drives can have equivalentG                    media compatibility problems when attempting to readeI                    (much) newer CD media and newer CD media technologies.tG                    These older CD drives are generally intended for usetF                    with the so-called embossed media, rather than withI                    non-embossed recorded (recordable) media now in common                     circulation.   G                    Please consider using a slightly-less-ancient CD-ROM H                    or CD-R or CD-RW drive when working with non-embossed%                    recorded CD media.t  E                    To paraphrase one knowledgable-though deliberatelybF                    nameless-storage engineer, "The RRD42 drive is just2                    past the drooling idiot stage".          J                                                                       9-13 :                                 Files      '           _____________________________D?           9.7.3  Creating Bootable OpenVMS I64 CD or DVD Media?n                  SYS$SETBOOT?t  E                    If you are creating a bootable CD or DVD media for"E                    use with OpenVMS I64, you will want to specify theEI                    SYS$SETBOOT block size of 2048, and you will also wanteG                    a disk cluster factor that is a multiple of four viaoG                    INITIALIZE/CLUSTER=4 (or 8, or...), or you will wanteE                    to ensure that SYS$EFI.SYS and SYS$DIAGNOSTICS.SYSGF                    are aligned to a multiple of four blocks; to a 2048E                    byte boundary. This alignment and this blocking is I                    only necessary for OpenVMS I64, and only when creating <                    optical media OpenVMS I64 for bootstraps.  I                    The default 512-byte block setting used by SYS$SETBOOT I                    is the correct and expected value for traditional disk 5                    bootstraps on OpenVMS I64 systems.o  G                    Once the boot files are loaded, OpenVMS I64 operatesaH                    with 512-byte blocks; as is the case with ATAPI disksG                    on OpenVMS Alpha, all application code will only see1C                    512-byte blocks on optical media on OpenVMS I64.   =                    OpenVMS I64 V8.2 and later are expected toGA                    have a version of SYS$SETBOOT that will flag a G                    misaligned SYS$EFI.SYS and (if present) a misaligneda,                    SYS$DIAGNOSTICS.SYS file.  G                    For information on SYS$SETBOOT and the SET BOOTBLOCKBA                    command, please see Section 14.3.9 and see thenG                    OpenVMS documentation. The purpose and intent of thesF                    SYS$SETBOOT.EXE image and the SET BOOTBLOCK commandF                    is analogous to the WRITEBOOT.EXE image on existing9                    OpenVMS VAX and OpenVMS Alpha systems.   E                    For information on CD and DVD optical media drives G                    on OpenVMS, please see Section 14.29. For additional J                    related information on creating bootable OpenVMS media,:                    please see Ask The Wizard topic (9820).                              9-14e t  p                              Files      D           __________________________________________________________>           9.8  What I/O transfer size limits exist in OpenVMS?  C                    The maximum transfer size is an attribute of the ?                    particular I/O device, controller and driver E                    combination; there is no inherent limit imposed by H                    OpenVMS (other than the fact that, today, byte counts>                    and LBNs are generally limited to 32 bits).  F                    The maximum size of a device I/O request is limitedE                    by the value in UCB$L_MAXBCNT, which is set by the J                    device driver based on various factors. (Also check theJ                    setting of the MAXBUF system parameter for buffered I/O<                    transfers, and check the process quotas.)  J                    Currently, SCSI drivers limit I/O transfers to FE00(16)E                    bytes, 65024 bytes (decimal). The reasons for this C                    transfer size limitation are largely historical._I                    Similarly, DSSI devices are limited to the same value,aG                    this for hardware-specific reasons. Transfers to HSCmD                    and HSJ device controllers via the CI are limitedE                    to 1,048,576 bytes. Client MSCP-served devices areME                    limited to 65535 bytes-to help ensure that the I/OiI                    fragmentation processing happens on the client and notg(                    on the server system.  G                    Parts of the OpenVMS I/O subsystem are optimized for E                    data transfers less than 64KB, because (obviously)oJ                    most I/O operations are (substantially) less than that.I                    OpenVMS can handle larger transfers, if the driver ands,                    the device can handle it.  5                    Also see Section 9.4, Section 9.5.f  D           __________________________________________________________C           9.9  Can I use ODBC to connect to OpenVMS database files?p  J                    Yes, you can use various available third-party packagesJ                    that permit remote ODBC clients to access RMS files and@                    various commercial databases via the network.  B                    For RMS, consider acquiring one of the packagesF                    available from EasySoft, Attunity Connect (formerlyC                    known as ISG Navigator), Oracle (DB Integrator),dE                    SolutionsIQ, OpenLink Software (OpenLink Universals.                    Data Access), and Synergex.  J                                                                       9-15 _  _                              Files        4                    The unixODBC package available atF                    http://www.unixodbc.org has variously been found to/                    operate on OpenVMS, as well.s  E                    For specific commercial databases (other than RMS,nG                    of course), contact the database vendor directly for                     assistance.  D           __________________________________________________________I           9.10  If my disks are shown as VIOC Compatible, am I using XFC?e  2                    Yes, you are using XFC caching.  I                    Disks that are using XFC caching use communication and F                    coordination protocols that are compatible with theF                    older VIOC caching implementation. With the initialD                    implementation of XFC on OpenVMS, you can use theE                    command SHOW MEMORY/CACHE to see no disks reported F                    in full XFC mode; all disks shown will be listed in*                    "VIOC Compatable Mode".  I                    If you have the OpenVMS system parameter VCC_FLAGS set G                    to 2 and are using OpenVMS Alpha V7.3-1 or later, or G                    are using OpenVMS Alpha V7.3 with the VMS73_XFC V2.0 J                    ECO kit or later or with the UPDATE kits, you are using                    XFC.5  D                    Another confusion: the XFC product version is andI                    remains V1.0 in all released configurations, please do J                    not confuse the internal XFC product version (displayedJ                    by various commands) with the version number associatedH                    with the various ECO kit(s). XFC V1.0 does not permitI                    volumes to enter full XFC caching, as displayed by the J                    "Vols in Full XFC mode" portion of the DCL command SHOW'                    MEMORY/CACHE output.p  D           __________________________________________________________>           9.11  RMS Sequential Files and Platform Portability?  F                    When working with mixed platforms, you will want toI                    become familiar with the various RMS sequential recordoH                    formats, including Variable with Fixed Control (VFC),G                    stream, stream LF, and stream CR, among other recorde                    formats.                       9-16     t                              Files        <                    Switching formats uses CONVERT/FDL or SETB                    FILE/ATTRIBUTES. The former converts files, theH                    latter resets attributes. Text editors tend to selectE                    attributes when creating new files that may or mayaF                    not meet requirements. If the default attributes doG                    not match your requirements, create a stub file, SETdH                    FILE/ATTR, then edit the existing file. (Most editorsA                    will preserve attributes on an existing file.)T  H                    When working with Windows, stream is usually the bestC                    choice for sequential file operations. Stream LF F                    is most commonly used with UNIX and C applications.H                    Windows and UNIX tend not to be able to directly readG                    files of "unexpected" sequential RMS record formats.   F                    VFC is a common OpenVMS format, encoding the recordI                    length into the record. It is this extra data that canrJ                    cause corruption-like problems when viewed without RMS;I                    either directly via $qio or via the file system API on J                    other operating system platforms. You will want to lookF                    at the low-level record formats, and at the RMS andJ                    the Files and Applications documentation in the OpenVMS                    manuals.   C                    If transfering through other platforms, use of a I                    current version of Zip (with the "-Vv" or "-V" option)tE                    and unzip, or use of a BACKUP saveset will contain H                    and maintain the RMS file and record attributes. (ForF                    BACKUP and its own attributes requirements, see the%                    restoration tool.)   D           __________________________________________________________)           9.12  How to read locked files?   C                    Files can be locked by applications, and various H                    approaches including CONVERT/SHARE and DUMP/ALLOCATEDF                    can be used, as can the following command sequence:  ;                    $ open/read/share=write x lockedfile.txt                     $ type xo  J                    If you can rebuild the application from source, details@                    related to file sharing are in Section 10.17.  J                                                                       9-17 m  s                    J                    _______________________________________________________  2           10       OpenVMS Programming Information      D           __________________________________________________________I           10.1  Modular Programming, Facility Prefixes and Symbol Naming?   G                    Please first review the OpenVMS Programming ConceptsaG                    Manual and the Guide to Modular Programming manuals.tF                    Both are available within the OpenVMS documentationE                    set, and provide details of the expected norms form$                    OpenVMS programs.  D                    o  Learn about the facility prefix, and use a theJ                       appropriate prefix uniformly throughout all externalG                       symbols, all logical names, and all files located F                       in shared directories. The prefix and the use ofI                       the dollar sign (<$>) and the underscore (<_>) helpoF                       avoid collisions with other products. Use of theE                       dollar sign is reserved to registered products.   G                    o  Please consider use of tools such as the Freeware H                       SDL package, and the GNM package. These permit youI                       to generate include files and message documentation"F                       akin to that of OpenVMS, providing users of your:                       product with a familiar environment.  I                    o  For product installations, consider use of the PCSI J                       installation utility, and provide a product-specificB                       configuration DCL command procedure (usuallyE                       SYS$MANAGER:prefix$CONFIG.COM) if configuration "                       is required.  ?                    o  The product startup file is usually namedw=                       SYS$STARTUP:prefix$STARTUP.COM, and the :                       shutdown file (if needed) is usually6                       SYS$STARTUP:prefix$SHUTDOWN.COM.  D                    OpenVMS provides a registry for facility prefixesE                    and for MESSAGE message compiler codes. To request E                    a prefix and a message facility code for a productkG                    you distributinng to other customer sites, send yourp  J                                                                       10-1 t             2                    OpenVMS Programming Information        F                    request in a mail message addressed to product[-at-J                    sign-]hylndr.sqp.zko.dec.com, requesting the submission@                    form and details of the registration process.  1                                              NoteT  A                       Please do not request facility prefixes forv@                       products that local to your business, yourA                       site, or your system. Facility prefixes and A                       message codes and the facility registration"A                       process are intended solely for HP productsfA                       and Partner Products (and yes, even OpenVMS A                       Freeware packages) that will be distributed1=                       across multiple OpenVMS customer sites.   C                    For a list of common coding bugs, please see theeH                    remainder of this section of the FAQ and specificallyJ                    Section 10.22, please also see the Ask The Wizard topicF                    (1661), and for information on debugging an OpenVMS8                    application, please see topic (7552).  H                    o  http://www.hp.com/go/openvms/wizard/ (retired; use"                       ITRC forums)  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the available F                    ATW Wizard.zip archive, please see Section 3.8. ATWF                    has been superceded (for new questions) by the ITRCD                    discussion forums; the area remains available for                    reference.r  D           __________________________________________________________?           10.2  Can I have a source code example of calling...?l  J                    Please use the available SEARCH command on OpenVMS, andE                    please remember to search the available resources, D                    including the support databases and the newsgroupI                    archives. Please also realize that most OpenVMS systemsJ                    services use similar calling sequences, meaning that anJ                    example of calling sys$getjpi can be used as an exampleI                    for sys$getsyi and sys$getdvi. Students: please do nottF                    expect folks to write your homework for you. As for$                    search resources:  4                    o  SEARCH SYS$EXAMPLES:*.* target  6                    o  SEARCH TCPIP$EXAMPLES:*.* target                      10-2_ _  _          2                    OpenVMS Programming Information        <                    o  http://www.hp.com/go/openvms/freeware/  ,                    o  http://www.google.com/  C                    OpenVMS programming documentation, including thedH                    numerous example programs found in recent versions ofI                    the OpenVMS Programming Concepts manual, is available:   7                    o  http://www.hp.com/go/openvms/doc/n  J                    As for details of argument passing, most OpenVMS systemE                    services and RTL routines pass string arguments bykD                    descriptor. Languages which support native stringE                    data types create descriptors automatically; thoseeE                    which do not (eg., C) require that you set them upeG                    explicitly. For further details on using descriptors H                    and particularly for using descriptors from C, please%                    see Section 10.13.F  J                    There is extensive information available on how to callG                    OpenVMS system services and OpenVMS Run-Time LibrarysF                    routines, including examples in numerous languages.;                    Among the best available references are:e  1                    o  Your language's User Manual   <                    o  OpenVMS Programming Environment Manual  9                    o  OpenVMS Programming Concepts Manual   F                    o  OpenVMS Programming Interfaces: Calling a System                       Routine   .                    o  OpenVMS Calling Standard  H                    In addition, you can also locate answers, source codeG                    examples and related discussions in the James SearchFD                    Assistant (formerly NLSA (Natural Language SearchJ                    Assistant), itself formerly known as Ask Compaq (AskQ))                    database:  F                    o  http://www2.itrc.hp.com/service/james/CPQhome.do  A                    In this area, you will find the source code ofD@                    programming examples for calls to many of theH                    OpenVMS system services (and from various programming?                    languages), including calls to core servicesuG                    sys$getjpi[w], sys$getsyi[w] and sys$qio[w], as wellS  J                                                                       10-3 e  n          2                    OpenVMS Programming Information        I                    as source code examples for calls to many other systemeJ                    services and run-time library routines, and examples ofH                    one of the more difficult calling interfaces found onH                    OpenVMS systems, that of the smg$create_menu routine.  G                    Arne Vajhj has put together a collection of OpenVMSC8                    example programs. It can be found at:  /                    o  ftp://ftp.hhs.dk/pub/vms/c  F                    Additional information and examples for OpenVMS are!                    available via:u  H                    o  http://www.hp.com/go/openvms/wizard/ (retired; use"                       ITRC forums)  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the available F                    ATW Wizard.zip archive, please see Section 3.8. ATWF                    has been superceded (for new questions) by the ITRCD                    discussion forums; the area remains available for&                    reference. and via:  <                    o  http://www.hp.com/go/openvms/freeware/  D           __________________________________________________________A           10.3  How do I get the arguments from the command line?   A                    If you're writing a program and want to acceptiI                    arguments from a foreign command, you can use LIB$GET_dI                    FOREIGN to get the command line and parse it yourself,EJ                    or if you're programming in C, use the normal argc/argv                    method.  D                    To write an application which uses the normal DCLF                    verb/qualifier/parameter syntax for invocation, seeF                    the description of the CLI$ routines in the OpenVMS>                    Callable Utility Routines Reference Manual.  F                    It is possible to write an application which can beE                    used both ways; if a DCL verb isn't used to invokelE                    the image, the application parses the command linetJ                    itself. One way to do this is to call CLI$GET_VALUE forI                    a required parameter. If it is not present (or you get J                    an error), call LIB$GET_FOREIGN to get the command line+                    and do the manual parse.                       10-4  e  h          2                    OpenVMS Programming Information        (                    See also Section 8.2.  D           __________________________________________________________E           10.4  How do I get a formatted error message in a variable?a  C                    Use the SYS$PUTMSG system service with an actionLJ                    routine that stores the message line(s) in the variableE                    of your choice. Be sure the action routine returns.C                    a "false" (low bit clear) function value so thateE                    SYS$PUTMSG doesn't then try to display the messageOJ                    (unless you want it to.) See the description of $PUTMSGI                    in the System Services Reference Manual for an example(.                    of using an action routine.  D           __________________________________________________________D           10.5  How do I link against SYS$SYSTEM:SYS.STB on an Alpha                 system?   I                    LINK/SYSEXE is the OpenVMS Alpha equivalent of linking F                    against SYS.STB. This links against the base image:%                    SYS$BASE_IMAGE.EXEp  G                    Also see Section 10.11, particularly for pointers toaF                    the details on shareable images and shareable imageH                    creation, and see Section 10.22 for details of inner-G                    mode floating point requirements, of data alignment,nG                    requirements for use of /NOSYSLIB, and other relatednH                    inner-mode programming details, and see Section 10.111                    for image-related information.e  D           __________________________________________________________@           10.6  How do I do a SET DEFAULT from inside a program?  C                    The problem is that SYS$SETDDIR only changes the H                    default directory - NOT the default disk. The defaultJ                    disk is determined by the logical SYS$DISK. If you wantI                    to change the default disk within a program, then call F                    LIB$SET_LOGICAL to change the logical SYS$DISK. YouI                    will need to call both LIB$SET_LOGICAL and SYS$SETDDIRaI                    to change both default disk and the default directory!         J                                                                       10-5 t  a          2                    OpenVMS Programming Information      D           __________________________________________________________I           10.7  How do I turn my Fortran COMMON into a shareable image ons                 Alpha?  F                    You need to add SYMBOL_VECTOR=(<common-name>=PSECT)G                    to your options file. On OpenVMS VAX all OVR/REL/GBL H                    psects were automatically exported into the shareableI                    image's Global Symbol Table. On OpenVMS Alpha you have F                    to tell the linker that you want this done by meansI                    of the PSECT keyword in the SYMBOL_VECTOR options file                     statement.t  G                    This has several advantages over OpenVMS VAX. First,rI                    you don't have to worry about the address of the psect D                    when you try to create a new, upwardly compatibleJ                    version of the shareable image. Second, you can controlE                    which psects, if any, are made visible outside the #                    shareable image.   F                    By default, COMMON PSECTs in HP Fortran for OpenVMSH                    Alpha (as well as most other OpenVMS Alpha compilers)H                    are NOSHR. On VAX, the default was SHR which requiredE                    you to change the attribute to NOSHR if you wanted H                    your COMMON to be in a shareable image but not write-H                    shared by all processes on the system. If you do want&                    write-sharing, use:  .                    CDEC$ PSECT common-name=SHR  I                    in the Fortran source code (the CDEC$ must be begin inrJ                    column 1) or a linker options file PSECT_ATTR statement<                    to set the COMMON PSECT attribute to SHR.  B                    For further information, see the Linker manual.  D           __________________________________________________________D           10.8  How do I convert between IEEE and VAX floating data?  F                    In OpenVMS V6.1 and later, the routine CVT$CONVERT_C                    FLOAT is documented in the LIB$ Run-Time Library C                    Reference Manual, and can perform floating point H                    conversions between any two of the following floatingH                    datatypes: VAX (F,D,G,H), little-endian IEEE (single,I                    double, quad), big-endian IEEE (single, double, quad),l0                    CRAY and IBM System\370, etc.                      10-6h m  s          2                    OpenVMS Programming Information        I                    HP Fortran (all OpenVMS platforms) has a feature which C                    will perform automatic conversion of unformattedsB                    data during input or output. See the HP FortranG                    documentation for information on "non-native data in @                    I/O" and the CONVERT= OPEN statement keyword.  B                    There are floating-point conversion source code<                    packages available for various platforms.  G                    For further floating-point related information, see:o  M                    o  http://www.hhs.dk/anonymous/pub/vms/collection/ieee.zip   D           __________________________________________________________E           10.9  How do I get the argument count in a Fortran routine?   E                    On VAX, many programmers would use a MACRO routine1B                    which accessed the AP register of the caller toE                    get the address of the argument list and hence the J                    argument count. This was not guaranteed to work on VAX,F                    but usually did. However, it doesn't work at all onF                    OpenVMS Alpha, as there is no AP register. On AlphaJ                    systems, you must use a language's built-in function toJ                    retrieve the argument count, if any. In Fortran this isG                    IARGCOUNT, which is also available in DEC Fortran on                     OpenVMS VAX.o  F                    Note that omitting arguments to Fortran routines isC                    non-standard and is unsupported. It will work inOF                    many cases - read the DEC Fortran release notes for*                    additional information.  D           __________________________________________________________H           10.10  How do I get a unique system ID for licensing purposes?  B                    Many software developers desire to use a uniqueF                    hardware ID to "lock" a given copy of their productF                    to a specific system. Most VAX and Alpha systems doF                    not have a unique hardware-set "system ID" that canG                    be used for this purpose. HP OpenVMS products do not E                    use hardware IDs in the licensing methods, as manylI                    users consider a hardware-based licensing scheme to beaJ                    negative attribute when considering software purchases.  J                                                                       10-7 .             2                    OpenVMS Programming Information        E                    HP OpenVMS uses a software-based system called the C                    License Management Facility (LMF). This provides C                    for software keys (Product Authorization Keys or F                    PAKS) which support capacity and user-based licenseC                    checking. HP offers an LMF PAK Generator to DSPPoG                    (formerly CSA) members-see Section 2.8.3 for general J                    details on the DSPP offerings, and on the DSPP-providedG                    Freeware PAKGEN PAK that is available for those that G                    are interested in details. (Sorry, no; you can't use H                    the Freeware PAKGEN PAK to generate any PAK you mightD                    want. Folks at HP also thought of that one, too.)  I                    For information on licensing, please see Section 12.4.D  G                    However, if a hardware-based method is required, theeE                    most common method is based on an Ethernet adaptorrH                    hardware address. Sample source code for implementing(                    this is available at:  H                    o  http://www.hp.com/go/openvms/wizard/ (retired; use"                       ITRC forums)  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the availablerF                    ATW Wizard.zip archive, please see Section 3.8. ATWF                    has been superceded (for new questions) by the ITRCD                    discussion forums; the area remains available for                    reference.   D           __________________________________________________________H           10.11  What is an executable, shareable, system or UWSS image?  B                    Executable code in OpenVMS typically resides inD                    an image-an image is a file-the file extension isG                    typically .EXE-that contains this code. Common types I                    of images include executable images, shareable images, >                    system images, and protected (UWSS) images.  F                    Executable images are programs that can be directlyH                    executed. These images can grant enhanced privileges,G                    with an INSTALL of the image with /PRIVILEGE, or can D                    grant enhanced access with the specification of aF                    subsystem identifier on the ACL associated with the                    image.a                      10-8D m  a          2                    OpenVMS Programming Information        E                    Shareable images contain code executed indirectly,lE                    these images are referenced from executable images G                    and/or from other shareable images. These images can3F                    not grant enhanced privileges, even with the use ofE                    INSTALL with /PRIVILEGE or a subsystem identifier.sF                    These shareable images can be dynamically activatedE                    (a LINK that occurs at run-time) via the LIB$FIND_rD                    IMAGE_SYMBOL run-time library (RTL) routine. (SeeD                    `protected images' for information on `privileged&                    shareable images'.)  D                    System images are intended to run directly on theH                    VAX or Alpha hardware-these are normally used for theB                    kernel code that comprises an operating system.  J                    Protected images-also refered to as User-Written SystemI                    Services (UWSS), or as privileged shareable images-arepH                    similiar in some ways to a standard shareable images,H                    but these images include a `change mode' handler, andI                    execute in an `inner' processor mode (privileged mode;CJ                    executive or kernel), and code executing in inner modesH                    has implicit SETPRV privilege. Must be INSTALLed withG                    /PROTECT. Note that inner-mode code has restrictions J                    around calling library routines, around calling variousF                    system services, and around calling code located in7                    other protected or shareable images.   I                    Loadable images and device drivers are images that caneG                    be used to add code into the OpenVMS kernel. Pseudo-nF                    device drivers are a particularly convenient way toF                    add executable code, with associated driver-definedF                    data structures, into the kernel. The pseudo-deviceI                    driver includes the UCB and DDB data structures, and aoI                    calling interface with support for both privileged and H                    unprivileged access to the driver code via sys$qio[w]                    calls.M  D                    A cookbook approach to creating OpenVMS shareable2                    images is available at the URL:  H                    o  http://www.hp.com/go/openvms/wizard/ (retired; use"                       ITRC forums)    J                                                                       10-9 G  T          2                    OpenVMS Programming Information        D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the available F                    ATW Wizard.zip archive, please see Section 3.8. ATWF                    has been superceded (for new questions) by the ITRCD                    discussion forums; the area remains available for                    reference.   D           __________________________________________________________8           10.12  How do I do a file copy from a program?  H                    There are several options available for copying filesG                    from within a program. Obvious choices include using G                    lib$spawn(),  system(), sys$sndjbc() or sys$creprc() J                    to invoke a DCL COPY command. Other common alternativesF                    include using the callable convert routines and theE                    BACKUP application programming interface (V7.1 andS                    later).  D           __________________________________________________________&           10.13  What is a descriptor?  B                    A descriptor is a data structure that describesA                    a string or an array. Each descriptor containsdH                    information that describes the type of the data beingD                    referenced, the size of the data, and the addressE                    of the data. It also includes a description of thecJ                    storage used for the data, typically static or dynamic.7                    Descriptors are passed by reference.   C                    The following are examples of creating and using G                    descriptors in C, with the use of the angle brackets @                    normally expected by the C include statements=                    deliberately altered in deference to HTML:r  +                        #include {descrip.h} 0                        #include {lib$routines.h}*                        #include {stsdef.h}#                        int RetStat; *                        char TxtBuf[TXTSIZ]8                        struct dsc$descriptor StaticDsc =C                          { 0, DSC$K_DTYPE_T, DSC$K_CLASS_S, NULL };r5                        struct dsc$descriptor DynDsc =TC                          { 0, DSC$K_DTYPE_T, DSC$K_CLASS_D, NULL }; +                        int DynDscLen = 255;bC                        $DESCRIPTOR( ConstDsc, "This is a string" );l                      10-10    t          2                    OpenVMS Programming Information        B                        /* finish setting up a static descriptor */<                        StaticDsc.dsc$w_length      = TXTSIZ;E                        StaticDsc.dsc$a_pointer     = (void *) TxtBuf;   C                        /* finish setting up a dynamic descriptor */ E                        RetStat = lib$sget1_dd( &DynDscLen, &DynDsc ); =                        if ( !$VMS_STATUS_SUCCESS( RetStat ) ) (                          return RetStat;  8                        /* release the dynamic storage */:                        RetStat = lib$sfree1_dd( &DynDsc );;                        if (!$VMS_STATUS_SUCCESS( RetStat )) (                          return RetStat;  F                    Static descriptors reference storage entirely underG                    application program control, and the contents of the H                    descriptor data structure can be modified as requiredG                    (by the application). OpenVMS routines do not modify I                    the contents of a static descriptor, nor do they alter D                    the address or length values stored in the staticJ                    descriptor. (The term "static" refers to the descriptorE                    data structure, and not necessarily to the storaget1                    referenced by the descriptor.)s  B                    Dynamic descriptors reference storage under theG                    control of the run-time library, and the contents of H                    a dynamic descriptor data structure-once initialized-I                    can only be modified under control of run-time libraryeJ                    routines. The dynamic storage referenced by the dynamicI                    descriptor is allocated and maintained by the run-timeiF                    library routines. Various OpenVMS routines do alterJ                    the contents of the descriptor data structure, changingJ                    the value for the amount and the address of the storageG                    associated with the dynamic descriptor, as required.nJ                    Routines can obviously access and alter the contents of<                    the storage referenced by the descriptor.  E                    OpenVMS languages that include support for stringsbD                    or arrays are expected to use descriptors for theE                    particular structure. Most OpenVMS languages, such.A                    as Fortran and BASIC, use descriptors entirely J                    transparently. Some, like DEC C, require the programmerD                    to explicitly create and maintain the descriptor.  J                                                                      10-11 O  a          2                    OpenVMS Programming Information        E                    For further information on string descriptors, see G                    the OpenVMS Programming Concepts manual, part of thed-                    OpenVMS documentation set.   D                    Fortran defaults to passing integers by referenceD                    and characters by descriptor. The following sitesG                    discuss mixing Fortran and C source code in the sameO                    application:X  I                    o  http://www.hhs.dk/anonymous/pub/vms/misc/FORTRAN_C_e                       CALL.COM  F                    o  ftp://ftp.hhs.dk/pub/vms/misc/FORTRAN_C_CALL.COM  D           __________________________________________________________B           10.14  How do I create a process under another username?  J                    Many server processes can operate within the context ofE                    the target user using privileges, using calls such D                    as sys$chkpro and (more commonly in this context)J                    sys$check_access as needed to determine if access wouldI                    be permitted for the specified user within the current_"                    security model.  B                    With OpenVMS V6.2 and later, the persona systemE                    services (SYS$PERSONA_*) can be used to assume theoJ                    persona of the specified user-these allow the server toJ                    operate as the specified user, in a controlled fashion.I                    The persona services can be used as a "wrapper" aroundhH                    a sys$creprc process creation call, as well-this willG                    create a seperate process entirely under the assumedi                    persona.r  I                    Information on the persona system services is included B                    in the OpenVMS V6.2 new features documentation,D                    and in the OpenVMS V7.1 and later system servicesE                    documentation. These system services exist and are @                    supported in OpenVMS V6.2 and later releases.  J                    Typical mechanisms for creating a process under another$                    username include:  E                    o  personna services around a sys$creprc call. Seei                       above.                      10-12 o             2                    OpenVMS Programming Information        =                    o  via DECnet task-to-task, using explicit F                       specification of username and password, or usingE                       a DECnet proxy. This creates a network-mode job G                       under the target user. The network-mode job might I                       do little more than a RUN/DETACH of an image passed E                       in via task-to-task-task-to-task communications C                       are fully available using strictly DCL-to-DCL G                       processing, or using a compiled language and DCL,                        etc.)e  B                    o  SUBMIT/USER, or the username argument on theJ                       sys$sndjbc call. This creates a batch-mode job underI                       the specified username. The batch-mode job might do I                       little more than a RUN/DETACH of an image passed in &                       via a parameter.  J                    o  the UIC argument on the sys$creprc call. This mimicsJ                       the UIC of the target user, and is certainly not the7                       prefered mechanism for this task.   -                    o  Via pseudo-terminals..._  D                    There are likely a few other mechanisms around...I                    There are various tools available from DECUS and other J                    sources that allow various forms of user impersonation,F                    as well. These tools will require version-dependentJ                    kernel code and enhanced privileges for some of (or all(                    of) their operations.  D           __________________________________________________________B           10.15  Why do lib$spawn, lib$set_symbol fail in detached                  processes?   E                    The processing within run-time library (RTL) calls_H                    such as lib$attach, lib$disable_ctrl, lib$do_command,D                    lib$enable_ctrl, lib$get_symbol, lib$run_program,E                    lib$set_symbol, lib$set_logical, and lib$spawn, isFF                    dependent on and requires the presence of a commandI                    language interpreter (CLI), such as DCL. Without a CLI H                    present in the current process, these calls will failE                    with a "NOCLI, no CLI present to perform function"d                    error.o  J                    Detached processes typically do not have a CLI present.  J                                                                      10-13 x  i          2                    OpenVMS Programming Information        G                    In place of lib$spawn, sys$creprc can often be used.tI                    The context of the parent process (symbols and logical>I                    names) will not be propogated into the subprocess whentJ                    sys$creprc is used, though when there is no CLI presentE                    in the process this (lack of) propogation is moot.f  D                    To create a detached process with a CLI, you mustD                    specify LOGINOUT as the target image as discussedE                    elsewhere in the FAQ, or only use these calls (andtH                    any other calls requiring a CLI) from images that areH                    running in an "interactive", "batch", or "other" mode                    process.   E                    Also note that the lib$spawn and the C system call J                    will fail in a CAPTIVE login environment. The lib$spawnJ                    call can be gotten to work in this environment with the5                    specification of the TRUSTED flag.d  D           __________________________________________________________@           10.16  Where can I obtain Bliss, and the libraries and"                  supporting files?  E                    The Bliss language compilers and documentation areoC                    available on the OpenVMS Freeware distributions.S  I                    Bliss language source code that contains the followinge                    statement:c  7                      LIBRARY 'SYS$LIBRARY:STARLET.L32';s  @                    or similar requires the presence of the BlissG                    libraries. These libraries are created on the targetPF                    system using the Bliss require files, and are built6                    using the following Bliss commands:  I                    STARLET.L32 contains the public interfaces to OpenVMS:n  H                        $ BLISS /LIBRARY=SYS$COMMON:[SYSLIB]STARLET.L32 -2                            SYS$LIBRARY:STARLET.REQ  J                    LIB.L32 contains both the public and private interfaces                    to OpenVMS:  D                        $ BLISS /LIBRARY=SYS$COMMON:[SYSLIB]LIB.L32 -F                            SYS$LIBRARY:LIB.REQ+SYS$LIBRARY:STARLET.REQ                      10-14 l  o          2                    OpenVMS Programming Information        E                    The equivilent files for Bliss64 are created with:t  G                        $ BLISS/A64/LIBRARY=SYS$COMMON:[SYSLIB]LIB.L64 - F                            SYS$LIBRARY:LIB.R64+STARLET.REQ+STARLET.R64K                        $ BLISS/A64/LIBRARY=SYS$COMMON:[SYSLIB]STARLET.L64 - 2                            SYS$LIBRARY:STARLET.R64  C                    Some Bliss code may also require the OpenVMS VAXuF                    architecture flags. The following is the equivilent5                    of the Alpha ARCH_DEFS.REQ module:s             !eA           ! This is the OpenVMS VAX version of ARCH_DEFS.REQ, andrD           ! contains the architectural definitions for conditionallyC           ! compiling OpenVMS Bliss sources for use on VAX systems. D           ! (If you should encounter compilation errors here, please>           ! seriously consider upgrading your Bliss compiler.)           !s           MACRO VAXPAGE = 1%;s           MACRO BIGPAGE = 0%;            !rE           MACRO VAX =                     ! = 1 if compiled BLISS/VAX_I                   %BLISS(BLISS32V)%;      ! = 0 if not compiled BLISS/VAX   Y           MACRO EVAX =                    ! = 1 if compiled BLISS/E* (Obsolete, old name)sV                   (%BLISS(BLISS32E) OR %BLISS(BLISS64E))%; ! = 0 if compiled /VAX /Inn  T           MACRO ALPHA =                   ! = 1 if compiled BLISS/E* (New arch name)V                   (%BLISS(BLISS32E) OR %BLISS(BLISS64E))%; ! = 0 if compiled /VAX /Inn  T           MACRO IA64 =                    ! = 1 if compiled BLISS/I* (New arch name)Y                   (%BLISS(BLISS32I) OR %BLISS(BLISS64I))%; ! = 0 if compiled /VAX or /Annp             MACRO ADDRESSBITS =fM                   %BPADDR%;               ! = 32 or 64 based on compiler usedE  G                    Some Bliss code may require the definition files for:F                    the OpenVMS older LIBRTL routine lib$tparse, or the.                    newer lib$table_parse call:  G                        $ BLISS /LIBRARY=SYS$COMMON:[SYSLIB]TPAMAC.L32 - 1                            SYS$LIBRARY:TPAMAC.REQ     J                                                                      10-15 m             2                    OpenVMS Programming Information      D           __________________________________________________________9           10.17  How can I open a file for shared access?   J                    When creating a file, it is often useful to allow otherH                    applications and utilities-such as TYPE-to share readF                    access to the file. This permits you to examine the8                    contents of a log file, for instance.  I                    A C source example that demonstrates how to do this iseJ                    available in topic (2867) in the OpenVMS Ask The Wizard                    area:  H                    o  http://www.hp.com/go/openvms/wizard/ (retired; use"                       ITRC forums)  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the availableeF                    ATW Wizard.zip archive, please see Section 3.8. ATWF                    has been superceded (for new questions) by the ITRCD                    discussion forums; the area remains available for                    reference.r  F                    Depending on the environment, you may need to use CI                    calls such as fsync and fflush, and-in specific cases- ,                    the setvbuf(_IONBF) call.  A                    For related materials around commands that can G                    potentially be used to override file locking-to view E                    the file contents as currently written to disk-see                      Section 9.12.  D           __________________________________________________________G           10.18  How can I have common sources for messages, constants?   D                    Use the GNM tools on the OpenVMS Freeware to haveB                    common sources for MSG (message) files and SDMLC                    (Document) documentation files. Use the DOCUMENT E                    command to convert the SDML documentation into the G                    necessary formats (Text, Postscript, HTML, etc). Use H                    the MESSAGE/SDL tool (latent in OpenVMS) to create anH                    SDL file based on the messages. Then use the SDL toolI                    (available on the OpenVMS Freeware) to convert the SDL J                    file into language-specific definitions. (There is alsoF                    a converter around to convert SDL into SDML, if youG                    want to get pictures of the data structures for your "                    documentation.)                      10-16 M             2                    OpenVMS Programming Information      D           __________________________________________________________?           10.19  How do I activate the OpenVMS Debugger from ana                  application?   ,                    #include {lib$routines.h}%                    #include {ssdef.h}f&                    #include {string.h}                      main()S                        {6                        char ascic_debug_commands[128];<                        char *dbgcmd = "*show calls;go;exit";  >                        strcpy( ascic_debug_commands, dbgcmd );J                        ascic_debug_commands[0] = (char) strlen( dbgcmd ) -           1;  D                        lib$signal(SS$_DEBUG,1,ascic_debug_commands);                           return 1;                        }  H                    Also see Section 10.28 for another related discussionH                    of the OpenVMS Debugger, and of a technique that uses(                    the SS$_DEBUG signal.  D           __________________________________________________________*           10.20  Dealing with Endian-ness?  F                    OpenVMS VAX, OpenVMS Alpha and OpenVMS I64 (as wellH                    as all Microsoft Windows implementations) all supportG                    and all use the little-endian byte ordering. Certain/B                    Alpha microprocessors and certain Intel ItaniumH                    processors can be configured to operate in big-endianE                    and potentially in bi-endian mode. HP-UX typicallys'                    operates big-endian.e  G                    With little-endian byte order, the least significant H                    byte is always the first byte; the byte at the lowestC                    address. With big-endian byte ordering, the byterJ                    storage order in memory is dependent on the size of theH                    data (byte, word, longword) that is being referenced.  F                    Endian-ness is a problem has been solved many times@                    before. Some of the typical solutions include@                    htonl/htons and ntohl/ntohs in the standard CE                    library and the TCP/IP Services XDR (eXternal Data F                    Representation) libraries. One of the more recently  J                                                                      10-17    u          2                    OpenVMS Programming Information        E                    introduced network formats, and one that is seeing B                    extensive press and marketing coverage, is XML.  D           __________________________________________________________7           10.21  How to resolve LINK-I-DATMISCH errors?M  D                    The message LINK-I-DATMISCH is informational, andH                    indicates that the version of the specified shareableF                    image found in the system shareable image directoryI                    does not match the version of the shareable image that F                    was originally loaded into IMAGELIB.OLB, one of theF                    OpenVMS libraries typically searched by the LINKER.  I                    From a privileged username, you can usually completely =                    repair this via the following DCL command:   K           $ LIB/REPLACE/SHARE SYS$LIBRARY:IMAGELIB.OLB SYS$SHARE:LIBRTL.EXEo  E                    This command assumes that the shareable image thatlH                    was found in the SYS$SHARE: area is valid and upward-I                    compatiable, and that the image has simply replaced and@                    older version without also updating IMAGELIB.  D           __________________________________________________________E           10.22  HP C and other OpenVMS C Programming Considerations?L  E                    VAX C V3.2 was released for OpenVMS VAX systems inTI                    1991. DEC C V4.0 replaced VAX C V3.2 in 1993 as the HPuG                    C compiler for OpenVMS VAX systems. HP C is the ANSIlG                    C compiler for OpenVMS Alpha systems. VAX C predateshG                    the ANSI C standards, and has various areas that areeJ                    not compliant with ANSI C requirements. HP C is an ANSIH                    C compiler, and can also compile most VAX C code whenI                    /STANDARD=VAXC is specified. Versions of this compiler I                    between V3.2 and V6.5 (exclusive) were known as DEC C,V+                    DIGITAL C, and Compaq C._  J                    Both compilers can be installed at the same time on theI                    same OpenVMS VAX system, allowing a migration from VAXhJ                    C to DEC C, and allowing the same DEC C code to be used4                    on OpenVMS VAX and OpenVMS Alpha.  E                    The system manager can choose the system default CeJ                    compiler when HP C is installed on a system with VAX C,H                    and a C programmer can explicitly select the required=                    compiler for a any particular compilation.t                      10-18               2                    OpenVMS Programming Information        H                    A current "C" license PAK allows access to both VAX C;                    and HP C on the same OpenVMS VAX system.o  H                    Various HP C versions can be installed on OpenVMS VAXH                    V5.5-2 and later. OpenVMS VAX releases such as V5.5-2G                    and V6.0 will require the installation of a HP C RTLaF                    kit, a kit that is included with the HP C compiler.G                    OpenVMS VAX versions V6.1 and later do not require apH                    seperate RTL kit, but HP C RTL ECO kits are availableF                    to resolve problems found with the C RTL on various$                    OpenVMS releases.  H                    With HP C, for automatic resolution of the standard CJ                    library routines by the LINKER utility, use the /PREFIXJ                    qualifier, such as /PREFIX=ALL_ENTRIES. If a particularE                    application program replaces an existing C library H                    routine, use /PREFIX=(ALL_ENTRIES,EXCEPT=(...)). (VAXH                    C required explicit specification of an RTL shareable>                    image or C object library during the link.)  H                    When the /PREFIX is requested, the compiler generatesI                    a "decc$" prefix on the specified symbols. This prefixnD                    allows the LINKER to resolve the external symbolsG                    against the symbols present in the DECC$SHR library.eG                    The DECC$SHR library is included in the IMAGELIB.OLBbG                    shareable image library, and IMAGELIB is searched byAH                    default when any program (written in any language) isG                    LINKed. Because the standard C library routine namesBH                    are very likely to match application routines writtenI                    in other languages, a prefix "decc$" is added to the CoF                    symbol names to assure their uniqueness; to preventD                    symbol naming conflicts. C programs, however, canI                    sometimes have private libraries for various purposes,aD                    and the external routines share the same names asF                    the library routines. (This is not recommended, butJ                    there are applications around that use this technique.)H                    Thus the need to explicity specify whether or not theE                    "decc$" prefix should be prepended to the externaln0                    symbol names by the compiler.  B                    The qualifiers, and most (all?) with associatedF                    pragmas, that may be of interest when migrating VAX*                    C code to HP C include:  J                                                                      10-19 e  o          2                    OpenVMS Programming Information        D                    o  Failure to specify the prefixing qualifier (onH                       certain and usually older versions of C) can causeH                       the compiler to not add the prefixes for the namesC                       of the C library routines into the referencesfD                       placed in the object module, which can in turnF                       cause problems resolving the external symbols inA                       the library when the object code is linked:              /PREFIX=ALL_ENTRIESt  I                    o  Some VAX C programs erroneously write to the string C                       literals. By default, HP C does not allow then*                       constants to change.  *           /ASSUME=WRITABLE_STRING_LITERALS  F                    o  Enables sharing ("shr") of globals and of externC                       variables. HP C sets externs as non-shareablen0                       ("noshr"), VAX C as "shr".             /SHARE_GLOBALS  C                    o  VAX C assumes common block model for externalc                       linkages.m  #           /EXTERN_MODE=COMMON_BLOCKq  J                    o  Refers to the padding placed between member elementsG                       within a struct. Disabling member alignment packstA                       the data more tightly into memory, but this E                       packaging has performance implications, both onrC                       OpenVMS VAX and particularly on OpenVMS Alpha                        systems.             /[NO]MEMBER_ALIGNMENT   G                    o  Enable all manner of useful compiler diagnostics:   N           /WARN=ENABLE=(LEVEL4,QUESTCODE)/STANDARD=PORT/ACCEPT=NOVAXC_KEYWORDS  E                       You can disable extraneous diagnostics with thew                        following:  #                       #ifdef __DECCs*                       #pragma message saveK                       #pragma message disable /* insert message tag here */                        #endif                      10-20               2                    OpenVMS Programming Information        C                    Permit structure members to be naturally alignedt@                    whenever possible, and avoid using /NOMEMBER_F                    ALIGNMENT. If you need to disable member alignment,G                    use the equivilent #pragma to designate the specific J                    structures. The alignment of structure members normallyD                    only comes into play with specific unaligned dataD                    structures-such as the sys$creprc quota itemlist-H                    and with data structures that are using data that wasG                    organized by a system using byte or other non-member                     alignment./  J                    Versions of HP C such as V6.0 include the capability toH                    extract the contents of the standard header librariesF                    into directories such as SYS$SYSROOT:[DECC$LIB...],H                    and provide various logical names that can be definedG                    to control library searches. With HP C versions such H                    as V6.0, the default operations of the compiler matchH                    the expectations of most OpenVMS programmers, withoutF                    requiring any definitions of site-specific library-F                    related logical names. (And logical names left fromH                    older DEC C versions can sometimes cause the compiler3                    troubles locating header files.)a  D                    HP C V5.6 and later include a backport library, aC                    mechanism by which HP C running on older OpenVMSnG                    releases can gain access to newer RTL routines addedoI                    to the RTL in later OpenVMS releases-the language RTLsrH                    ship with OpenVMS itself, and not with the compilers.  C                    Example C code is available in SYS$EXAMPLES:, in B                    DECW$EXAMPLES (when the DECwindows examples areG                    installed), in TCPIP$SERVICES (or on older releases, J                    UCX$EXAMPLES) when HP TCP/IP Services is installed), onA                    the Freeware CD-ROMs, and at web sites such ase  H                    o  http://www.hp.com/go/openvms/wizard/ (retired; use"                       ITRC forums)  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the availableAF                    ATW Wizard.zip archive, please see Section 3.8. ATWF                    has been superceded (for new questions) by the ITRCD                    discussion forums; the area remains available for                    reference.)  J                                                                      10-21 g             2                    OpenVMS Programming Information      '           _____________________________e(           10.22.1  Other common C issues  H                    The localtime()  function and various other functionsI                    maintain the number of years since 1900 in the "structdJ                    tm" structure member tm_year. This field will contain aI                    value of 100 in the year 2000, 101 for 2001, etc., andtI                    the yearly incrementation of this field is expected toa                    continue.  H                    The C epoch typically uses a longword (known as time_E                    t) to contain the number of seconds since midnight G                    on 1-Jan-1970. At the current rate of consumption of G                    seconds, this longword is expected to overflow (when F                    interpreted as a signed longword) circa 03:14:07 onF                    19-Jan-2038 (GMT), as this time is circa 0x7FFFFFFFB                    seconds since the C base date. (The most commonE                    solution is to ensure that time_t is an unsigned.)   D                    If C does not correctly handle the display of theF                    local system time, then check the UTC configurationJ                    on OpenVMS-the most common symptom of this is a skew ofG                    one hour (or whatever the local daylight saving time I                    change might be). This skew can be caused by incorrect F                    handling of the "is_dst" setting in the applicationH                    program, or by an incorrect OpenVMS UTC configurationB                    on the local system. (See section Section 4.4.)  G                    Floating point is prohibited in OpenVMS Alpha inner- F                    mode (privileged) code, and in any process or otherF                    execution context that does not have floating pointE                    enabled. C programmers developing and working with I                    OpenVMS Alpha high-IPL kernel-mode code such as device I                    drivers will want to become familiar with the floatingzJ                    point processing available in the environment, and withJ                    the C compiler qualifier /INSTRUCTION_SET=[NO]FLOATING_H                    POINT. Device drivers and other similar kernel-mode CH                    code must be compiled with /INSTRUCTION_SET=FLOATING_9                    POINT and /EXTERN_MODEL=STRICT_REFDEF._  F                    Additionally, the SYS$LIBRARY:SYS$LIB_C.TLB/LIBRARYH                    parameter will be needed to be appended to the moduleI                    specification or declared via the C compiler's include H                    library logical name mechanism when the C compiler isI                    resolving kernel-mode data structures and definitions. F                    This library contains OpenVMS kernel-mode and other                      10-22    g          2                    OpenVMS Programming Information        C                    system declaractions, and particularly a mixture D                    of undocumented definitions and declarations, andE                    particularly definitions and declarations that areEF                    subject to change (and that can accordingly lead toD                    requirements for the recompilation of application                    code).   H                    In addition to the user-mode C Run-Time Library (RTL)C                    mentioned in the OpenVMS C RTL documentation and.H                    referenced over in Section 3.9, there is a second andH                    parallel kernel-mode RTL accessable to device driversE                    and other kernel code on OpenVMS Alpha and OpenVMS E                    I64. The most common time this second C library isdF                    noticed is when C code is (erroneously) linked withH                    /SYSEXE/SYSLIB, and duplicate symbol errors typicallyI                    then arise. As code running in supervisor-, executive- E                    or kernel-mode context cannot call out a user-moderC                    RTL or other user-mode library, you will want toTG                    respecify the command as LINK /SYSEXE/NOSYSLIB. ThistI                    will eliminate the duplicate symbol errors, since onlyUJ                    the kernel-mode library will be referenced, and it willG                    also avoid calling out into the user-mode libraries.0  G                    When sharing variables with other languages, here is ,                    some example HP C code...                            ...2                          #pragma extern_model save;                          #pragma extern_model strict_refdefd4                          extern int   VMS$GL_FLAVOR;5                          #pragma extern_model restoreR                          ...  D                    and here is some associated example Bliss code...                            ...!                          EXTERNAL *                             VMS$GL_FLAVOR,                          ....=          J                                                                      10-23               2                    OpenVMS Programming Information      '           _____________________________r*           10.22.2  Other common C++ issues  B                    HP C++ (a separate compiler from HP C) providesC                    both symbol mangling and symbol decoration. SomeaE                    of the details of working with longer symbol names B                    and the resulting symbol name mangling in mixedD                    language environments are listed in the shareableG                    image cookbook, and in the C++ documentation. SymboltG                    name decoration permits the overloading of functionsrC                    (by adding characters to the external symbol forrD                    the function to indicate the function return typeD                    and the argument data types involved), and mixed-H                    language external references can and often do need toI                    disable this decoration via the extern "C" declarationm                    mechanism:n  #                          extern "C"a                            {;                            extern int ExternSymbol(void *);V@                            extern int OtherExternSymbol(void *);                            }  I                    Also see Section 14.7 for information on /ARCHITECTURE &                    and /OPTIMIZE=TUNE.  H                    See Section 10.15 for information on the C system and>                    the lib$spawn call in CAPTIVE environments.  D                    Constructs such as the order of incrementation orF                    decrementation and the order of argument processingJ                    within an argument list are all implementation-defined.?                    This means that C coding constructs such as:I                          i = i++; "                        a[i] = i++;)                        foo( i, i++, --i);   I                    are undefined and can have (adverse) implications when I                    porting the C code to another C compiler or to another I                    platform. In general, any combination of ++, -, =, +=, J                    -=, *=, etc operators that will cause the same value toJ                    be modified multiple times (between what the ANSI/ISO CJ                    standard calls "sequence points") produce undefined and3                    implementation-specific results.t                      10-24 g  t          2                    OpenVMS Programming Information        E                    Within C, the following are the "sequence points":/F                    the ";" at the end of a C statment, the ||, &&, ?:,F                    and comma operators, and a call to a function. NoteH                    specifically that = is NOT a sequence point, and thatG                    the individual arguments contained within a function?J                    argument list can be processed from right to left, from8                    left to right, or at any random whim.  E                    HP C for OpenVMS VAX (formerly DEC C) and VAX C dot4                    differ in the related processing.  F                    So you are looking for OpenVMS-specific definitions#                    (include files)?   @                    UCBDEF.H, PCBDEF.H and other OpenVMS-specificG                    definitions-these are considered part of OpenVMS andRF                    not part of the C compiler kit-are available on all1                    recent OpenVMS Alpha releases.   D                    To reference the version-dependent symbol libraryH                    sys$share:sys$lib_c.tlb, use a command similar to the-                    following for compilation:,  9                    $ CC sourcea+SYS$LIBRARY:SYS$LIB_C/LIBe  I                    You can also define DECC$TEXT_LIBRARY to reference the                     library.n  C                    You will want to review the Programming ConceptsnH                    manual, and specifically take a quick look at Chapter                    21.  G                    And some general background: the STARLET definitions G                    (and thus the sys$starlet_c.tlb library) contain the F                    symbols and the definitions that are independent ofE                    the OpenVMS version. The LIB definitions (and thuseF                    sys$lib_c) contain symbols and definitions that canI                    be dependent on the OpenVMS version. You won't need togI                    rebuild your code after an OpenVMS upgrade if you haveeH                    included definitions from STARLET. The same cannot beI                    said for some of the definitions in LIB-you might needoG                    to rebuild your code. (The UCB structure can and hashB                    changed from release to release, for instance.)  I                    Recent versions of C automatically search sys$starlet_iD                    c.tlb. Explicit specification of sys$lib_c.tlb is                    required.  J                                                                      10-25               2                    OpenVMS Programming Information        E                    Also see the Ask The Wizard website topics (2486), &                    (3803), and (1661):  H                    o  http://www.hp.com/go/openvms/wizard/ (retired; use"                       ITRC forums)  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the available F                    ATW Wizard.zip archive, please see Section 3.8. ATWF                    has been superceded (for new questions) by the ITRCD                    discussion forums; the area remains available for                    reference.T  A                    See Section 9.5 for information on the C off_t H                    limitations, resolved in OpenVMS V7.3-1 and later andG                    in ECO kits available for specific OpenVMS releases. I                    The use of a longword for off_t restricts applications G                    using native C I/O to file sizes of two gigabytes or_I                    less, or these applications must use native RMS or XQP 1                    calls for specific operations.   D           __________________________________________________________<           10.23  Status of Programming Tools on OpenVMS VAX?  G                    DECthreads V7.3 and the HP C compiler (also known asaE                    Compaq C and DEC C) V6.4 are presently expected toiE                    be the last updates and the last releases of theseaH                    development packages for use on OpenVMS VAX. The run-G                    time support for both DECthreads (CMA$RTL) and for C G                    (DECC$CRTL) will continue to be maintained, and willnE                    continue to be available on OpenVMS VAX. The VAX C H                    V3.2 compiler is the final VAX C compiler release forH                    OpenVMS VAX, and the VAX C Run-Time Library (VAXCRTL)6                    will also continue to be available.  ?                    New development and new features and product F                    enhancements continue for the OpenVMS Alpha and the<                    OpenVMS IA-64 DECthreads and C compilers.                                10-26 r  s          2                    OpenVMS Programming Information      D           __________________________________________________________@           10.24  Choosing a Version Number for Application Code?  G                    One of the common rules-of-thumb used for choosing asI                    displayed version number string for a new version of ahG                    layered product or an application, its implications,gF                    and its expected effects on client applications and"                    users, follows:  G                    o  No functional and no application-visible changes, C                       bugfixes only-the edit number is incremented.aI                       These tend to be very small, very isolated, or ECO-iH                       level changes. These can also be distributions forG                       specific hardware configurations or platforms, asdJ                       is the case with an OpenVMS Limited Hardware ReleaseG                       (LHR). Application rebuilds are not expected, andaG                       there is an assumption that general user-providediH                       application-related regression testing will not be                       required.   B                    o  Minimal functional and very few user-visibleJ                       changes-the maintenance number is incremented. TheseF                       tend to be very small or even ECO-level changes,G                       though somewhat larger than an edit-level change.BI                       Application rebuilds are not expected, and there isaJ                       an assumption that user-provided application-related>                       regression testing will not be required.  D                    o  Various small and upward-compatible functionalF                       changes-the minor version number is incremented.J                       The changes are user-visible, and are intended to beJ                       user-visible. Application rebuilds are not expected.H                       Some application programmers may choose to perform'                       regression tests.l  D                    o  Large and/or potentially incompatible changes-C                       the major version number is incremented. SomeLD                       applications might need to be rebuilt. VariousD                       application programmers will choose to performH                       regression tests of their respective applications.  E                    For additional version-numbering materials and foriF                    information on assigning module generation numbers,G                    please see the OpenVMS (POLYCENTER) Software ProductSH                    Installation Utility-variously refered to by acronyms  J                                                                      10-27               2                    OpenVMS Programming Information        E                    including PCSI and SPIA-reference manual available 8                    within the OpenVMS documentation set.  A                    Of course, all of this is obviously subject tocF                    interpretation, particularly around the distinctionF                    between large and small changes and such. The scaleE                    of the application is also a factor, as larger and(E                    more complex applications will tend toward smaller I                    increments and will tend to see the maintenance number)J                    incremented, while new releases of smaller applicationsJ                    will tend to see the minor version incremented somewhat#                    more frequently.   I                    The goal of all this is to provide a guide to relativepF                    scale of changes and the associated effort involvedH                    in an upgrade for the user and/or for the application                    programmer.  D           __________________________________________________________4           10.25  Selecting a Process Dump Directory?  E                    You can customize the device and directory for theAI                    process dump by defining the logical names SYS$PROCDMP D                    and SYS$PROTECTED_PROCDMP. The former is for non-E                    privileged dumps, while the latter is the location @                    where privileged image dumps are written, andI                    preferably an area protected against untrusted access.                     For example:   5                    $ define SYS$PROCDMP SYS$ERRORLOG:aE                    $ define /exec SYS$PROTECTED_PROCDMP SYS$ERRORLOG:s  I                    The abouve presumes that the SYS$ERRORLOG logical namef.                    points to a valid location.  H                    There is presently no means to change the name of theF                    generated dump file from IMAGENAME.DMP to somethingD                    else. Accordingly, you will want to use differentD                    target directories for this purpose, particularlyC                    if there is more than one application or process 5                    potentially writing process dumps.l                          10-28 i  r          2                    OpenVMS Programming Information      D           __________________________________________________________-           10.26  Access to Itanium Assembler?   @                    If you are interested in accessing the nativeE                    Intel Itanium assembler within the OpenVMS I64 GNVdG                    environment-and since the iasi64 assembler is a UnixcI                    program and GNV is a Unix environment for OpenVMS I64- E                    you can simply copy iasi64.ext into your gnu:[bin] @                    directory in place of "as.", and of "AS.EXE".  I                    Alternately and probably also better, you can write an_G                    "as." script to invoke the iasi64.exe image from itsnD                    particular prefered location on the local system.  :                    A typical "as." script looks like this:  1                    path/iasi64.exe $1 $2 $3 $4 $5   D           __________________________________________________________1           10.27  Kernel-mode coding restrictions?t  G                    Floating point is prohibited in OpenVMS Alpha inner- J                    mode (privileged) code, and within any process or otherF                    execution context that does not have floating point)                    enabled and available.O  H                    Programmers developing and working with OpenVMS AlphaE                    high-IPL kernel-mode code, such as device drivers,oJ                    will further want to become familiar with the floating-E                    point processing and the instruction set emulation E                    available in the particular target environment (ifSI                    any). When working with C, inner-mode programmers will_H                    want to become familiar with the C compiler qualifier7                    /INSTRUCTION_SET=[NO]FLOATING_POINT.   F                    Device drivers and other similar kernel-mode C codeH                    must be compiled with /INSTRUCTION_SET=FLOATING_POINT3                    and /EXTERN_MODEL=STRICT_REFDEF.a  G                    Additionally, inner-mode code cannot call out to thecF                    user-mode language run-time libraries nor to any ofH                    the OpenVMS system run-time libraries. In particular,J                    this prohibition prevents pages of inner-mode-protectedJ                    memory from being allocated and interspersed within theJ                    user-mode heap or other such user-mode data structures.  J                                                                      10-29               2                    OpenVMS Programming Information        H                    The prohibtion on user libraries also generally meansI                    that such code must be linked with LINK /NOSYSLIB, andaF                    quite probably also with /SYSEXE. The former causesE                    the linker to avoid searching the system shareablegG                    image libraries (via IMAGELIB.OLB), while the latteraI                    brings in symbols typically only known to or otherwisei9                    accessable from the OpenVMS executuve.P  D                    To include kernel-mode C programming definitions,F                    macros and system constants within a C compilation,E                    include SYS$LIBRARY:SYS$LIB_C.TLB/LIBRARY on the C E                    compilation. (Constructs defined within the system C                    macro library LIB.MLB or within its C equivalent A                    SYS$LIB_C.TLB tend to be version-dependent, or.?                    undocumented, or both.) As an example of theaJ                    compilation, the following is a typical C device driver'                    compilation command:n  V           $   CC /STANDARD=RELAXED_ANSI89/INSTRUCTION=NOFLOATING_POINT/EXTERN=STRICT -P                   'DEBUG_CC_DQ_OPT' 'ARCH_CC_OPT' 'CHECK_CC_OPT' 'SHOW_CC_OPT' -E                   /LIS=LIS$:xxDRIVER/MACHINE_CODE/OBJ=OBJ$:xxDRIVER -7C                   SRC$:xxDRIVER.C+SYS$LIBRARY:SYS$LIB_C.TLB/LIBRARYn  I                    Additionally, code running in executive mode in an ASTnJ                    or in kernel mode cannot call RMS services, or routines9                    which directly or indirectly call RMS._  D                    For related kernel-mode programming materials andG                    driver documentation, please see the Writing OpenVMS E                    Alpha Device Driversin C book, ISBN 1-55558-133-1.   D           __________________________________________________________=           10.28  Decoding an Access Violation (ACCVIO) Error?t  H                    To decode the virtual addresses returned by an accessG                    violation or by another similar OpenVMS display, you E                    need to have created and retained a listings file-tJ                    preferably one with machine code generation enabled-and#                    a full link map.:  D                    Starting with the virtual address reported by theB                    error, use the link map to find the module thatI                    contributed the code that contains the virtual address J                    range. Calculate the offset from the base of the range,H                    by subtracting the base of the range from teh failingF                    virtual address. Then use the compiler listings for                      10-30               2                    OpenVMS Programming Information        H                    the particular component that contributed the code to@                    locate the offset of the failing instruction.  J                    If the map and listings information was not maintained,J                    working backwards is far more difficult-you are left toH                    use the binary instruction data around the failure toI                    locate the associated source code, and this process ishG                    far more involved. This usually involves matching upiJ                    blocks of decoded instructions around the failing code,G                    or the direct analog involving matching up ranges ofBH                    decoded instructions. Keep the maps and listing files*                    around, in other words.  J                    Rather easier than an approach based on virtual addressH                    arithmetic and far easier than working backwards fromI                    the instruction stream is to use integrated debugging- G                    this inclusion is arguably an essential component of E                    any non-trivial application-and to use the OpenVMS                     Debugger.  D                    The OpenVMS Debugger in particular can be used toI                    examine the source code, to examine the stack, and can I                    even be programmed to wait patiently for the incidence E                    of a particular value or failure or condition, andoE                    this is far easier than working backwards from the.E                    instruction stream is to use integrated debugging-aG                    this inclusion is arguably an essential component ofkE                    any non-trivial application-and to use the OpenVMSOD                    Debugger. The debugger can also be activated fromD                    within a signal handler, and commands to generateD                    a traceback can be generated directly, or throughG                    the invocation of a procedure containing a series of %                    debugger commands.   F                    Details on the debugger are in the OpenVMS DebuggerE                    Manual, and also see the discussion of dyanmically <                    activating the Debugger in Section 10.19.              J                                                                      10-31               2                    OpenVMS Programming Information      D           __________________________________________________________0           10.29  Generating an AUTODIN-II CRC32?  I                    The following code can be used to generate an AUTODIN-eJ                    II 32-bit Cyclic Redundency Check (CRC32) value from anJ                    input string descriptor, similar to that used by the HPH                    C compiler for its /NAMES=SHORTENED mechanism, and by@                    various other applications requiring a CRC32.  H                    The routine uses the OpenVMS library routine lib$crc_J                    table to generate a sixteen longword array of data fromI                    the specified encoded polynomial coefficient (AUTODIN- F                    II, in this case), and then lib$crc to generate theA                    CRC32 value from the array and the input data.p  H           static int CreateCRC32( struct dsc$descriptor *InputDataDesc )
             {              uint32 AUTODIN2;             uint32 Seed = ~0UL; /             uint32 Coefficient = 0x0EDB88320UL;t              uint32 CRCArray[16];  ,             lib$establish( lib$sig_to_ret );  F             lib$crc_table( (void *) &Coefficient, (void *) CRCArray );S             AUTODIN2 = lib$crc( (void *) CRCArray, (void *) &Seed, InputDataDesc );              AUTODIN2 ^= Seed;                return AUTODIN2;
             }   D           __________________________________________________________+           10.30  Enabling built-in tracing?   *                    $ RUN SYS$SYSTEM:SYSMAN?                    SYSMAN> SYS_LOAD ADD TR$DEBUG TR$DEBUG/LOAD_            STEP=INIT/LOG                     SYSMAN> Exit 6                    $ @SYS$UPDATE:VMS$SYSTEM_IMAGES.COM  8                    To stop it from loading early in boot  +                    $  RUN SYS$SYSTEM:SYSMAN @                    SYSMAN> SYS_LOAD REMOVE TR$DEBUG TR$DEBUG/LOG                    SYSMAN> Exito6                    $ @SYS$UPDATE:VMS$SYSTEM_IMAGES.COM                      10-32 u  e          2                    OpenVMS Programming Information        F                    The first occurance of the name TR$DEBUG within theE                    command is considered the "product" and the secondcE                    is considered the "image" that should exist within '                    SYS$LOADABLE_IMAGES.t  A                    When TR$DEBUG loads in the init phase, it wille1                    automatically turn on tracing.o  1                    Also see the SDA TR extension.S                                                                      J                                                                      10-33                         J                    _______________________________________________________             11       DECwindowsr      D           __________________________________________________________A           11.1  How do I let someone else display something on mye                 workstation?  I                    On a workstation, you will want to use the "Customize" A                    menu of the session manager utility and select C                    "Security". When the pop-up box appears, you can I                    select the host node, username, and tranport that will F                    allow you to launch an application that targets the'                    workstation display.a  B                    If this does not provide you with access to the:                    display, You need a checklist of sorts:  C                    o  Make sure that you've specified the X-windows C                       "display" correctly on the remote host. For a J                       DECnet transport, the specification uses two colons,H                       while the TCP/IP transport typically uses one. TheF                       X Windows server and the X Windows screen followH                       the host specification, delimited by a period. For                       example:  J           ________________________________________________________________0           Table 11-1  X Windows Display Commands  J                    _______________________________________________________J                    Shell_____Command______________________________________                      csh  <                              # setenv DISPLAY vms.domain:0.0                      sh and ksh   H                              # $ DISPLAY=vms.domain:0.0 ; export DISPLAY                      DCL  C                              $ SET DISPLAY/CREATE/NODE=vms.domain - J           ___________________/TRANSPORT=TCPIP/SERVER=server/SCREEN=screen_  E                    o  If you have verified the command is correct and G                       things are still not working, ensure the Security F                       settings on the OpenVMS host side will allow the  J                                                                       11-1                                   DECwindows         G                       incoming connection: Pull down the "Options" menurJ                       in the Session Manager, and select "Security...". IfJ                       you do not find your host and username and transportI                       listed among the authorized users, you will need tor#                       add an entry.g  I                      o  There are various transports available, including F                         LOCAL, DECNET, LAT, and TCPIP. You must SelectA                         the transport appropriate to the incomingr#                         connection.   D                      o  If the transport is "DECnet", do NOT add the;                         double colon (::) to the node name.   D                      o  If the transport is "TCPIP", "Username" mustG                         be an asterisk (*). Why? Because unlike DECnet, G                         the TCP/IP protocol does not provide the remote H                         username information in the incoming connection.  G                      o  If the connection is "TCPIP", it is best to use C                         a full domain name (e.g. Node.Subd.Domain). C                         However, you may have to use the IP addressoC                         itself, if your host does not have a way torD                         resolve the address via DNS. If you have theH                         luxury of fixed addresses (eg: you are not usingH                         DHCP), then it can be helpful to add two entriesI                         for each TCP/IP host, one that specifies the host E                         name and one that specifies the host address.   F                      o  There are various TCP/IP packages for OpenVMS,B                         and you must use syntax appropriate to the,                         transport installed.  D                      o  If a TCP/IP connection is still not working,C                         ensure that the transport you want has beenu>                         activated for use with DECwindows. SeeG                         Section 11.14 for details of configuring TCP/IP '                         as a transport.d  G                    o  There is a log file created in SYS$MANAGER: whicheC                       can tell you which transports are loaded, and H                       also tell you what connect attempts were rejected,F                       including showing what the presented credentialsC                       were. This file is SYS$MANAGER:DECW$SERVER_0_ G                       ERROR.LOG, although the 0 could be another number1H                       if you have multiple servers on the workstation. I                      11-2  e  s                              DECwindowst        I                       have found this file to be very useful for trackingyF                       down what needs to be put in the Session Manager'                       Security entries.   D           __________________________________________________________A           11.2  How do I create a display on another workstation?   I                    To create a display from an OpenVMS host to a remote X J                    Windows display, use one of the following DCL commands:  S                    $ SET DISPLAY /CREATE /TRANSPORT=net_transport /NODE=remote_nodehI                    $ SET DISPLAY /CREATE /TRANSPORT=LAT /NODE=remote_nodeoL                    $ SET DISPLAY /CREATE /TRANSPORT=DECnet /NODE=remote_nodeK                    $ SET DISPLAY /CREATE /TRANSPORT=TCPIP /NODE=remote_nodea  J                    Note that LAT is typically used only for the VXT seriesD                    X Windows terminals, but it can also be used fromJ                    OpenVMS to OpenVMS systems on various OpenVMS releases,J                    such as on OpenVMS Alpha V6.1 and later. For details onG                    configuring the TCP/IP transport, see Section 11.14.e  H                    If you are interested in X Windows terminals and haveH                    an older VAXstation system around, please see the EWS,                    package on Freeware V5.0.  D           __________________________________________________________F           11.3  How can I get the information from SHOW DISPLAY into a                 symbol?   E                    Use the undocumented SHOW DISPLAY/SYMBOL, and thentI                    reference the symbols DECW$DISPLAY_NODE, DECW$DISPLAY_ C                    SCREEN, DECW$DISPLAY_SERVER and/or DECW$DISPLAY_                     TRANSPORT.   A                    An example of calling the underlying (and also F                    undocumented) sys$qio programming interface for the4                    WSDRIVER (WSAn:) is available at:  9                    http://www.hp.com/go/openvms/freeware/   H           Look in the Freeware V4.0 directory /srh_examples/DECUS_UNDOC_           CLINIC/.    J                                                                       11-3 n  c                              DECwindowsi      D           __________________________________________________________8           11.4  How do I get a log of a DECterm session?  H                    If you are working from a DECwindows DECterm terminalF                    emulator, you can use the AutoPrint feature. ChooseJ                    the "Printer..." menu item from the "Options" menu, setG                    the printing destination to the name of the file youpG                    want, and set "Auto Print Mode". You are now free toy                    continue.  D                    It should be noted that all of the characters andH                    escape sequences are captured, but if you display theE                    resulting log file on a DECterm, then you will seeo9                    exactly what was originally displayed.   E                    You can also use the "Print Screen" screen capture H                    available in the DECwindows session manager menus, ifJ                    you simply wish to snapshot a particular portion of the%                    X Windows display.r  I                    If you are using the Freeware VTstar terminal emulatoreH                    package, you will find a similar logging mechanism is*                    available in the menus.  D           __________________________________________________________5           11.5  Why is DECwindows Motif not starting?   D                    First check to see if there is a graphics device,E                    usually a G* device. (eg: On a DEC 2000 model 300,eG                    use the command SHOW DEVICE GQ) If you do not find am#                    graphics device:   D                    o  OpenVMS has failed to find the appropriate IRQC                       information for an EISA graphics card (on the G                       DEC 2000 series) such as the HP (Compaq) QVision, G                       and did not autoconfigure it. Run the correct ECUrF                       (for Tru64 UNIX and OpenVMS) and reboot. This is;                       necessary only on EISA-based systems.p  D                    o  You have an EISA-based system (such as the DECC                       2000 model 300) and do not have a HP (Compaq)fH                       QVision video card. This EISA graphics card shouldF                       have Compaq printed on it, and identifies itselfD                       as a CPQ3011 or a CPQ3111. If it is not one ofC                       these two EISA devices, then OpenVMS does notrD                       support it. (There are no other supported EISAJ                       graphics controllers, and EISA graphics are normally                      11-4e                                   DECwindowsi        F                       used with DECwindows only on the DEC 2000 series                       systems.)   D                    o  You have a PCI-based system, and do not have aI                       supported graphics controller-examples of supported 8                       controllers include the following:  #                      o  Radeon 7500   8                      o  PowerStorm 3D30, PowerStorm 4D20  )                      o  3DLabs Oxygen VX1t  I                       See Section 5.16 for further information on some ofT1                       these graphics controllers.f  C                    o  You have booted the system minimally, or haveCE                       otherwise disabled the device autoconfiguration                        process.  <                    If there is a G* graphics device present:  ?                    o  There may have been a severe error in thei>                       DECwindows startup. Type the contents ofA                       SYS$MANAGER:DECW$SERVER_0_ERROR.LOG for anya@                       information on errors starting the server.  F                    o  The system parameter WINDOW_SYSTEM is not set toH                       1. While this was a common way for system managersE                       to disable the DECwindows server startup, it is E                       not particularly reliable as DECwindows can now -                       "correct" this setting.e  F                       If you really do not want an OpenVMS system withE                       workstation hardware to bootstrap and configurec@                       itself as a workstation, add the following3                       definition to SYLOGICALS.COM:   G                       $ DEFINE/SYSTEM/EXEC DECW$IGNORE_WORKSTATION TRUE   G                    o  You may not have a valid DECwindows Motif license G                       loaded. To check for the two most common types of F                       Motif product authorization keys (PAKs), use the-                       following DCL commands:   2                       $ LICENSE LIST DW-MOTIF/FULL6                       $ LICENSE LIST NET-APP-SUP*/FULL  J                                                                       11-5                                   DECwindows         F                       and examine the information displayed. Make sureF                       that one of these licenses is present, valid and                       active..  E                       For information on registering software licensee@                       product authorization keys (PAKs) when youE                       cannot log into the system directly, please see $                       Section 5.6.2.  E                    o  Check that the DECW$PRIVATE_SERVER_SETUP.COM is E                       correct for the graphics controller in use. For                        instance:,  E                       The following is from the 9FX Vision 330 Owners G                       Guide, EK-V330G-OG pg 2-9. Place the following in H                       DECW$PRIVATE_SERVER_SETUP.COM, creatibng .COM fromF                       .TEMPLATE if necessary. Locate the DECW$PRIVATE_G                       SERVER_SETUP.COM file in SYS$SPECIFIC:[SYSMGR] orsG                       in SYS$COMMON:[SYSMGR] as appropriate; the former C                       file is used for this system within a clustersC                       configuration, and the latter is used for all H                       systems that do not also have a local copy of this4                       file in SYS$SPECIFIC:[SYSMGR].  6                       $ DECW$XSIZE_IN_PIXELS == xvalue6                       $ DECW$YSIZE_IN_PIXELS == yvalueI                       $ DEFINE/SYSTEM DECW$SERVER_REFRESH_RATE rate_in_Hz   G                       Also see Section 11.11. Details of the PowerStormeI                       3D30 and 4D20 settings are available in the OpenVMS(*                       Ask The Wizard area.  D           __________________________________________________________;           11.6  How do I set the title on a DECterm window?   B                    If you are creating a new DECterm window, check  =                    $ HELP CREATE /TERMINAL /WINDOW_ATTRIBUTES   I                    If you want to change the title of an existing window, J                    use the following control sequences, where <esc> is theJ                    ANSI escape code, value decimal 27, and "text label" is,                    what you want to display:  G                    To set the DECterm title, send the escape character, J                    then the characters "]21;", then the text label string,G                    and then an escape character followed by a backslash                     character.p                      11-6                                    DECwindowsu        I                    To set the icon label, send the escape character, thenbE                    the characters "]2L;", then the icon label string,nG                    and then an escape character followed by a backslasho                    character.r  E                    To set both the DECterm title and icon to the fullsG                    device name, you can use the following DCL commands:a             $  esc[0,7] = 27O           $  fulldevnam = F$Edit(F$GetDVI("TT","FULLDEVNAM"),"UPCASE,COLLAPSE")hB           $  write sys$output esc+ "]21;" + fulldevnam + esc + "\"B           $  write sys$output esc+ "]2L;" + fulldevnam + esc + "\"  G                    You can also change the title and the icon using theo*                    Options-Window... menu.  :                    Also see Section 12.1 and Section 8.13.  D           __________________________________________________________J           11.7  How do I customize DECwindows, including the login screen?  H                    To customize various DECwindows Motif characteristicsJ                    including the defaults used by the SET DISPLAY command,H                    the DECwindows login screen background logo used (theG                    default is the DIGITAL, Compaq, or HP logo), variousVH                    keymaps (also see Section 11.7.2 and Section 11.7.1),C                    the FileView defaults, session manager defaults, G                    the DECwindows login processing, DECwindows log fileeG                    processing, and various other DECwindows attributes,e(                    see the example file:  A                    $ SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.TEMPLATE   I                    This example template file is typically copied over toIE                    the filename SYS$COMMON:[SYSMGR]DECW$PRIVATE_APPS__D                    SETUP.COM and then modified to meet site-specific                     requirements.  I                    Additionally, various X tools such as xsetroot, bitmaplG                    and xrdb-some these can be useful in customizing theyJ                    appearance of an application or of the DECwindows Motif@                    display-are provided in the DECW$UTILS: area.  D                    When using DECwindows V1.2-4 and later on OpenVMSC                    Alpha, the default desktop is the Common DesktopmC                    Environment (CDE). You can select your preferredlE                    desktop (CDE or DECwindows Motif) when logging in,cB                    or you can change the default to the DECwindows  J                                                                       11-7 n                                 DECwindows         E                    Motif desktop using the DCL symbol decw$start_new_ F                    desktop in the DECwindows private application setupH                    command procedure. See SYS$MANAGER:DECW$PRIVATE_APPS_H                    SETUP.TEMPLATE for further details, and how to create/                    DECW$PRIVATE_APPS_SETUP.COM.e  D                    Note that with DECwindows CDE, the root window isC                    no longer visible by default. The root window iswE                    hidden behind the "backdrop" window of the currentoJ                    CDE workspace. To make the root window visible, use theG                    CDE style manager selection "backdrop none", and useiI                    information such as that in the OpenVMS FAQ to set the                     root window.   >                    To add a new backdrop to the DECwindows CDEC                    environment, the backdrop must first be in or bedE                    converted into X11 pixmap format. (This conversiontF                    is often possible using tools such as xv.) Then (ifC                    necessary) create the default backdrop directory F                    SYS$COMMON:[CDE$DEFAULTS.USER.BACKDROPS]. Place theH                    X11 pixmap file containing the desired image into theE                    backdrops directory, ensure that it has a filename G                    extension of .PM. (The xv default filename extensioneE                    for the X11 pixmap file is .XPM, while CDE expectsFH                    only to see files with .PM.) Now invoke the CDE styleC                    manager and select a new backdrop. You will findpF                    your image will be placed at the end of the list of'                    backdrops available.o  F                    If you require a message be included on the initialG                    display-where the start session display and the logogJ                    appears-you can use either of the following approaches:  F                    o  The simplest approach requires OpenVMS V7.3-2 orC                       later, and the corresponding DECwindows V1.3-cD                       1 kit or later. You will want to create a fileG                       named SYS$COMMON:[SYSMGR]DECW$GREET.TXT, and thiseE                       will be displayed in a popup-with an OK button-(G                       when the login box is displayed. This is intended D                       specifically for applications requiring such a                       display.                          11-8l    l                              DECwindows         C                    o  The second approach involves copying the filey)                       XRESOURCES.DAT fromi  M                       SYS$SYSDEVICE:[VMS$COMMON.CDE$DEFAULTS.SYSTEM.CONFIG.C]              into the directory  K                       SYS$SYSDEVICE:[VMS$COMMON.CDE$DEFAULTS.USER.CONFIG.C]   E           and editing the copy. Specifically, look for the following:_  3                       Dtlogin*greeting.labelString:s  H                       The line is normally commented out, and by default*                       contains the string:  ,                       Welcome to %localhost%  G                       You can change this text to something akin to the                         following:  <           Dtlogin*greeting.labelString:  Welcome to Heck \n\L           This is a Trusted System owned by the Rulers of the planet Zark\n\
           \n\r           We Come In Peace\n\            \n@           If you want Privacy, you've come to the wrong place\n\           \n  A                       The lines of text will be centered for you.   F                       In most DECwindows versions, you will be able toI                       onbtain only about eight (8) lines of text. Changes H                       have been implemented in DECwindows V1.3 and laterG                       that permit up to about twenty-five (25) lines ofo                       text.   I                    The login logo is stored as an XPM bitmap image in the g                    text file SYS$SYSROOT:[SYSCOMMON.CDE$DEFAULTS.SYSTEM.APPCONFIG.ICONS.C]DECDTLOGO.PM,e                    and it can be changed. Copy the file to SYS$SYSROOT:[SYSCOMMON.CDE$DEFAULTS.USER.APPCONFIG.ICONS.C]DECDTLOGO.PM,_H                    as DECwindows upgrades can replace the system version                     of this file.  I                    On DECwindows V1.3-1 and later (and possibly on V1.3), H                    both DECwindows CDE and DECwindows Motif displays useI                    this logo file. On older releases, only the DECwindows C                    CDE displays used this logo file, while the logo G                    used for the Motif login display was hard-coded into E                    the package and the only available override is the   J                                                                       11-9 "  r                              DECwindowst        H                    DECW$LOGINLOGO command procedure mechanism within theH                    customized, site-specific DECW$PRIVATE_APPS_SETUP.COM                    file.  G                    Look at the contents of the DECDTLOGO.PM file and at_F                    other *.XPM files and tools for additional details.  '           _____________________________S;           11.7.1  How do I customize DECwindows keymapping?d  J                    Various keymaps can be implemented on OpenVMS and otherD                    X Windows systems, allowing the implementation ofE                    a Dvorak-style or other alternate keymappings. ForaE                    details, see the available X Windows documentationoG                    (this is the documentation associated with X WindowsnD                    itself, and not the product documentation for theB                    OpenVMS operating system nor for the DECwindowsC                    X Windows implementation) and see the DECwindowsoA                    *.DECW$KEYMAP (text-format) files found in the 5                    DECwindows DECW$KEYMAP: directory.E  H                    For other keymapping information, see Section 11.7.2.  '           _____________________________sC           11.7.2  Why does the DELETE key delete forward instead of                    backward?D  J                    Some operating systems use <Ctrl/H> as <Delete>; as theH                    character back-delete key. Most OpenVMS applications,I                    VT-series terminals (check the terminal settings, many F                    can have this configured within the terminal set-upH                    menus), and DECterm terminals all use <Delete> as theJ                    character back-delete, and use <Ctrl/H> as a request to=                    move to the beginning of the command line.   A                    The Integrity EFI console does use <Ctrl/H> asr>                    <Delete>; as the character back-delete key.  H                    Also see the SET TERMINAL/BACKSPACE command available-                    on OpenVMS V8.2 and later.   J                    This behaviour involves the Motif virtual key bindings.J                    When a Motif application starts, it looks at the vendorH                    string returned in the display connection informationI                    and attempts to match the string to a table of virtuala                    bindings.                      11-10 T  n                              DECwindowsn        @                    You can override the default bindings in yourG                    decw$xdefaults.dat file. Here is the entry you would <                    make to get the default OpenVMS bindings.  ,                    *defaultVirtualBindings:\*                     osfCancel :  <F11> \n\)                     osfLeft :  <Left> \n\e&                     osfUp  :  <Up> \n\+                     osfRight :  <Right> \n\ )                     osfDown :  <Down> \n\t0                     osfEndLine :Alt  <Right> \n\1                     osfBeginLine :Alt  <Left> \n\D,                     osfPageUp :  <Prior> \n\-                     osfPageDown :  <Next> \n\C2                     osfDelete :Shift  <Delete> \n\.                     osfUndo :Alt  <Delete> \n\0                     osfBackSpace :  <Delete> \n\/                     osfAddMode :Shift  <F8> \n\ )                     osfHelp :  <Help> \n\e'                     osfMenu :  <F4> \n\n+                     osfMenuBar :  <F10> \n\t-                     osfSelect :  <Select> \n\r1                     osfActivate :  <KP_Enter> \n\k1                     osfCopy :Shift  <DRemove> \n\ ,                     osfCut  :  <DRemove> \n\(                     osfPaste :  <Insert>                      To merge:  2                    $ xrdb :== $decw$utils:xrdb.exe:                    $ xrdb -nocpp -merge decw$xdefaults.dat  F                    Also note that the DECW$UTILS:DECW$DEFINE_UTILS.COMH                    procedure can be used to establish the xrdb and other                    symbols.   G                    Also see the DECxterm directory of Freeware V5.0 fortE                    details on connecting to OpenVMS from various UNIXd                    platforms.   H                    For other keymapping information, see Section 11.7.1.      J                                                                      11-11                                   DECwindowsh      D           __________________________________________________________<           11.8  Why doesn't XtAppAddInput() work on OpenVMS?  F                    Yes, XtAppAddInput()  does work on OpenVMS. The MITC                    definition of the X Windows call XtAppAddInput() 8                    includes platform-specific arguments.  D                    On platforms where C is the typically the primaryB                    programming language for the platform, the fileA                    descriptor mask is one of the arguments to thes)                    XtAppAddInput()  call.g  F                    On OpenVMS, the platform-specific arguments to thisG                    call include an event flag and an IOSB, as these aretI                    the traditional OpenVMS constructs used to synchronizemF                    the completion of asynchronous operations. While itH                    would be easier to port non-OpenVMS C code that callsD                    XtAppAddInput()  over to OpenVMS if the argumentsF                    included the C file descriptor, this would make theH                    call unusable from other OpenVMS languages, and wouldF                    make it extremely difficult to use OpenVMS features2                    such as ASTs and sys$qio calls.  D                    One restriction on the event flag: the event flagJ                    chosen must be from event flag cluster zero. When usingF                    the traditional lib$get_ef and lib$free_ef calls toF                    allocate and deallocate event flags, you must firstJ                    explicitly call lib$free_ef to free up some event flagsH                    in event flag cluster zero. Please see the event flagH                    documentation for specific details on these calls andF                    for specific event flags that can be freed in event%                    flag cluster zero.r  E                    Here is some example code that covers calling thisn&                    routine on OpenVMS:                                        11-12 a  n                              DECwindows         2                        m->InputID = XtAppAddInput(%                            m->AppCtx,n&                            m->InputEF,(                            m->InputIosb,-                            the_callback, 1 );f1                        if ( !((int) m->InputID ))                             {)                            XtAppErrorMsg(e)                                m->AppCtx, /                                "invalidDevice",l/                                "XtAppAddInput", 0                                "XtToolkitError",5                                "Can't Access Device", /                                (String *) NULL,r3                                (Cardinal *) NULL );_                            ...  D           __________________________________________________________J           11.9  Why do the keyboard arrow keys move the DECwindows cursor?  E                    Congratulations, you have just stumbled into "dead F                    rodent" mode. This DECwindows environment-where theF                    keyboard arrow keys move the mouse cursor and whereJ                    the [SELECT], [PREV], and [NEXT] keys emulate the threeJ                    mouse buttons-allows rudimentary system operations when5                    the mouse is among the casualties.t  A                    To enter or exit "dead rodent" mode, enter then-                    following: <CTRL/SHIFT/F3>s  D           __________________________________________________________;           11.10  Why does half my DECwindows display blank?t  I                    This is likely a result of receiving an OPCOM or otheriE                    console message on a system that shares the systemeC                    console with the DECwindows graphics workstation                     display.t  F                    You can toggle off the console display window usingD                    <CTRL/F2> and you can enable a serial console per6                    Section 14.3.6 or Section 14.3.3.3.      J                                                                      11-13 _  _                              DECwindows         B                    Also see the console message window applicationG                    available with recent DECwindows versions-DECwindows D                    versions V1.2-3 and later will enable this windowB                    by default. For details on this console messageC                    window, see the DECW$CONSOLE_SELECTION option inY@                    SYS$STARTUP:DECW$PRIVATE_APPS_SETUP.TEMPLATE.  F                    On older releases, you can disable output using the                    following:   =                    $ SET TERMINAL/PERMANENT/NOBROADCAST OPA0:e2                    $ DEFINE/USER SYS$COMMAND OPA0:"                    $ REPLY/DISABLE  I                    Also see Section 14.3.3.2, Section 14.17, and Also seea                    Section 8.4,   D           __________________________________________________________C           11.11  %DECW-W-NODEVICE, No graphics device found on thish                  system?  2                    To resolve the following error:  L                    %DECW-W-NODEVICE, No graphics device found on this systemQ                    -DECW-I-NODECW, DECwindows graphics drivers will not be loaded   G                    o  Ensure that the system parameter WINDOW_SYSTEM is G                       set to 1. If it is not set to a value of 1, issue1#                       the commands:_  -                       $ run sys$system:sysgen_!                       USE CURRENTt)                       SET WINDOW_SYSTEM 1 "                       WRITE ACTIVE#                       WRITE CURRENT                        EXIT  -                       Then reboot the system.u  H                    o  On OpenVMS Alpha, ensure the SYSMAN IO PREFIX LISTI                       is set correctly, and specifically ensure the DECW$rG                       prefix is included in the existing list. If it ist3                       not, you will need to add it:                       11-14 e  o                              DECwindows         !           $ run sys$system:sysman            IO SHOW PREFIXI           IO SET PREFIX=(DECW$,*)   * = list returned by the show command            IO AUTO/LOGt           EXIT  F                    o  Ensure that the image SYS$SHARE:DECW$ICBM.EXE isG                       installed in memory. If it is not installed, then !                       install it:i  1           $ INSTALL LIST/FULL SYS$SHARE:DECW$ICBM /           $ INSTALL REPLACE SYS$SHARE:DECW$ICBMy)           $ EDIT SYS$MANAGER:SYCONFIG.COMl  4           $! The following line was added to install1           $! support for the Mach64 Graphics Cardi           $!/           $ INSTALL REPLACE SYS$SHARE:DECW$ICBM_           $ ^Z  -                       Then reboot the system._  I                       The ICBM mechanism is not used on and not needed by 6                       more recent DECwindows versions.  I                    o  If the system still complains "%DECW-W-NODEVICE, NoLB                       graphics device found on this system", then:  1                      o  Boot the system as normals  (                      o  Login as SYSTEM.  E                      o  Create the file SYS$COMMON:[SYSMGR]DECW$USER_uI                         AUTOCONFIG.DAT. Protection must permit world reade                         access.c  H                      o  Add the following string on the very first line:  !           CLEAR_PFLAG = ISA_4BYTE   %                      o  Save the file1  0                      o  Set the file protections  D           $ SET PROTECTION=W:RE SYS$MANAGER:DECW$USER_AUTOCONFIG.DAT  )                      o  Reboot the systemn  )                    Also see Section 11.5.   J                                                                      11-15                                   DECwindowsy      D           __________________________________________________________9           11.12  How can I reset the warning bell volume?   J                    With DECwindows CDE drivers and ECOs starting with ECOsG                    for the DECwindows keyboard driver SYS$IKBDRIVER.EXE B                    in OpenVMS Alpha V7.1-2 and V7.2-1 and with theE                    SYS$IKBDRIVER.EXE included in OpenVMS V7.2-1H1 andoH                    later, the DECwindows CDE controls will now correctlyA                    manage the setting of the warning bell volume.c  F                    Unfortunately, the equivalent controls in the olderH                    DECwindows Motif interface are not compatible and can<                    no longer manage the warning bell volume.  J                    If you need to manage the volume with DECwindows Motif,9                    consider using the following approach:,  2                    $ @decw$utils:decw$define_utils%                    $ xset b 1 100 100a  D                    The numerics are the volume, pitch, and duration,                     respectively.  J                    Why? When OpenVMS first started supporting the PC-styleJ                    keyboards, the X Windows Server and the keyboard driverH                    interface did not support the pitch and duration, andH                    neither did DECwindows Motif. The DECwindows keyboardH                    driver was accordingly changed to use the volume fromE                    the keyclick setting (keyclick is not available inrF                    a PC-style keyboard) and the bell volume setting to2                    control the pitch and duration.  H                    DECwindows CDE does provide sliders for setting pitchE                    and duration, so the keyboard driver and X WindowsfJ                    Server were modified to provide all of the information,J                    and now the DECwindows CDE sliders work. This change isI                    unfortunately incompatible with the old scheme used on H                    the pre-CDE desktops, and the volume controls are nowH                    incompatible with the current keyboard drivers. Hence#                    the use of xset.$                              11-16 .  ,                              DECwindows       D           __________________________________________________________=           11.13  How can I alter the DECwindows CDE backdrop?D  H                    To select a separate backdrop to be displayed on each/                    screen using DECwindows CDE:a  J                    o  Click on the Application Manager. This is the drawer.                       icon on the CDE toolbar.  ,                    o  Click on Desktop Tools  I                    o  Click on Set Default Screen and select the requireda                       screen  A                    o  Click on the Style Manager. This is the oneeE                       containing the mouse and ttt on the CDE toolbarR  0                    o  Now change the background.  D           __________________________________________________________A           11.14  How can I enable the DECwindows TCP/IP Transporto  D                    To configure the TCP/IP transport for DECwindows,F                    first ensure that a TCP/IP package is installed andC                    configured. Then set the DCL symbol DECW$SERVER_sA                    TRANSPORTS in SYS$MANAGER:DECW$PRIVATE_SERVER_rE                    SETUP.COM to the appropriate local value, based on1J                    the comments in that file. If you do not have a copy ofI                    SYS$STARTUP:DECW$PRIVATE_SERVER_SETUP.COM, the use theiJ                    following COPY command to create this file based on the*                    provided template file:  A           $ COPY SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE -_=           $_ SYS$COMMON:[SYSMGR]DECW$PRIVATE_SERVER_SETUP.COMn  D           __________________________________________________________G           11.15  Can I use DECwindows 1.2-* on OpenVMS V7.3-2 or later?   *                    The short answer is no.  F                    OpenVMS Alpha V7.3-2 only supports DECwindows MotifF                    V1.3 and later. If you require DECwindows V1.2-6 orI                    earlier, then you are limited to operations on OpenVMSe5                    Alpha V7.3-1 and earlier releases.   F                    The central technical reason involves depdendenciesJ                    among the parts of the X11 subsystem that are deliveredI                    with the base OpenVMS operating system including the X G                    Windows display server and the transport images, and   J                                                                      11-17 _  _                              DECwindowsI        I                    the parts of the DECwindows product that are deliveredCH                    within the DECwindows installation kits including theD                    client libraries and the DECwindows applications.  H                    DECwindows V1.3 and later made substantial changes toH                    the transport layer, and these required correspondingI                    changes to both the associated client and server code. I                    OpenVMS Alpha V7.3-2 includes the server and transportcE                    with the V1.3 modifications. These changes were inrH                    support of the upgrade of Xlib from X11R5 to X11R6.6,I                    and transport-level changes associated with support of 1                    the Kerberos and LBX features.   J                    If you attempt to load DECwindows V1.2-6 images onto anG                    OpenVMS Alpha V7.3-2 or later system, the DECwindows F                    libraries will not function with with system imagesH                    and will particularly not function with the transport                    layer.   D           __________________________________________________________2           11.16  How to add Fonts into DECwindows?  F                    The following assumes DECwindows V1.3-1 and OpenVMSJ                    Alpha V7.3-2 and later unless stated otherwise, and canG                    permit fonts of various formats to be added into thea*                    DECwindows environment.  E                    The recommended location for user font files is toaC                    place them in the directories which are reservedo@                    for this purpose, typically located below the7                    SYS$COMMON:[SYSFONT.DECW] directory.   8                    SYS$COMMON:[SYSFONT.DECW.USER_100DPI]7                    SYS$COMMON:[SYSFONT.DECW.USER_75DPI]o  J                    The above are recommended for PCF files of 100 Dots PerE                    Inch (DPI) and of 75 DPI resolution, respectively.   8                    SYS$COMMON:[SYSFONT.DECW.USER_COMMON]  E                    The above is recommended for other PCF files, suchhH                    as terminal (character cell) fonts, and fonts used by)                    specific applications.   :                    SYS$COMMON:[SYSFONT.DECW.USER_CURSOR16]:                    SYS$COMMON:[SYSFONT.DECW.USER_CURSOR32]                      11-18    p                              DECwindowss        9                    The above are recommended for cursors.1  8                    SYS$COMMON:[SYSFONT.DECW.USER_SPEEDO]  7                    SPEEDO is recommended for SPD files.D  :                    SYS$COMMON:[SYSFONT.DECW.USER_TRUETYPE]  B                    USER_TRUETYPE is recommended for TrueType (TTF)E                    fonts. Fonts placed in this directory should be in 0                    the "Windows / Linux" format.  H                    The directory will contain the font files themselves,B                    and a data file that describes each font in theH                    directory. This file is named DECW$FONT_DIRECTORY.DATJ                    or DECW$FONT_DIRECTORY_extension.DAT, where "extension"C                    is replaced by the type of font (100DPI, SPEEDO, )                    TRUETYPE, TYPE1, etc.)o  J                    Make sure that the file protection on the font files is:                    set to allow world access to the fonts.  D                    For example: to add TrueType fonts to DECwindows,I                    place the font files in SYS$COMMON:[SYSFONT.DECW.USER_E                    TRUETYPE]  <                    A directory listing might look like this:  ;           Directory SYS$COMMON:[SYSFONT.DECW.USER_TRUETYPE]e  Z           ARKOI8N.TTF;1                            46KB/48KB        5-MAR-1995 04:00:00.00Z           backstage.ttf;1                          55KB/56KB       19-JUL-2004 09:42:20.92Z           IDAutomationHC39M_Free.ttf;1             27KB/32KB       29-JUL-2003 11:25:48.00
           ... Z           texsi.ttf;1                             133KB/136KB      25-MAY-2003 15:31:11.00Z           texw.ttf;1                              150KB/152KB      25-MAY-2003 15:32:33.00  *           Total of 37 files, 3.09MB/3.23MB  =                    The case of the filename is not important.G  E                    TrueType fonts should be in Stream_LF file format.D  F                    To generate the appropriate DECW$FONT_DIRECTORY.DATA                    file for most font formats, issue the command:r  ,                    $ FONTCOMPILER /DIRECTORY  J                                                                      11-19 L                                 DECwindowsP        H                    The above may or may not operate with TrueType files,F                    and you will likely have to generate the DECW$FONT_F                    DIRECTORY_TRUETYPE.DAT file manually. A sample file                    follows:h             37O           BACKSTAGE.ttf -Grfonts-Backstage-bold-r-normal--0-0-0-0-p-0-iso8859-1nd           IDAutomationHC39M_Free.ttf -IDAutomation-HC39M-medium-r-normal--0-0-0-0-m-0-misc-Barcode39L           SUSESerif-Bold.ttf -Suse-Suse-bold-r-normal--0-0-0-0-p-0-iso8859-1O           SUSESerif-Roman.ttf -Suse-Suse-medium-r-normal--0-0-0-0-p-0-iso8859-1CO           SUSESans-Bold.ttf -Suse-Suse-bold-r-normal-sans-0-0-0-0-p-0-iso8859-1nV           SUSESans-BoldOblique.ttf -Suse-Suse-bold-o-normal-sans-0-0-0-0-p-0-iso8859-1T           SUSESans-Oblique.ttf -Suse-Suse-medium-o-normal-sans-0-0-0-0-p-0-iso8859-1R           SUSESans-Roman.ttf -Suse-Suse-medium-r-normal-sans-0-0-0-0-p-0-iso8859-1X           SUSESansMono-Bold.ttf -Suse-Suse Mono-bold-r-normal-sans-0-0-0-0-m-0-iso8859-1
           ... S           MCTIMEBI.TTF -UOregon-MAC C Times-bold-i-normal--0-0-0-0-p-0-macedonian-0ST           MCTIMEI.TTF -UOregon-MAC C Times-medium-i-normal--0-0-0-0-p-0-macedonian-0  D                    The first line of this data file is the number ofF                    font file entries which follow. Each entry consistsG                    of the font file name, and a font description. ThereCG                    are fourteen fields in the description, separated by E                    hyphens (dashes, "-"). Fields may contain embedded )                    spaces. The fields arer  F                    o  Foundry: the name of the company or person which(                       produced the font.  H                    o  Family: the name of the Typeface (what most people,                       will call the "font").  H                    o  Weight: How "heavy" the type appears. Normal fontsC                       are "medium" or "regular", variations includea3                       "bold", "demi", "light", etc.L  H                    o  Slant: "r" for regular, "i" for italic, or "o" for                       oblique.  J                    o  Width: "normal", "wide", "narrow", "condensed", etc.  F                    o  Style: normally left empty, it can also identifyG                       variations on a basic family such as "sans" (sans G                       serifs; without the serif, the ending and usually H                       pointed portion of the stroke). Fonts of different?                       styles can be grouped in the same family.                       11-20                                   DECwindows         G                    o  Sizes: the next four fields identify the size andtH                       scale of individual characters for fonts that haveG                       fixed point sizes. For fonts which scale (such as >                       TrueType), the four fields are all zero.  H                    o  Spacing: "p" for proportional, "m" for monospaced,0                       or "c" for character cell.  F                       Note: although DECwindows can identify differentI                       spacings within a family, the author has found thatsJ                       mixing monospaced and proportional fonts in the sameH                       family may cause some proportional font options toH                       not appear in a font selection menu within NotepadG                       (only). (A fix for this is expected in DECwindows &                       V1.5 and later.)  G                    o  The next field is always zero for TrueType fonts.,  J                    o  Character Set: the last two fields identify the nameI                       and version number of the character set representedbJ                       within the font. For many applications, these fields-                       are informational only.f  H                    The next step is to update the list of fonts known to6                    DECwindows, using the xset utility.  1                    $ mc decw$utils:xset fp rehashe  D                    It is also possible to reset the font list to the                    default:   2                    $ mc decw$utils:xset fp default  E                    This is useful if you need to recover from errors.N  F                    The Notepad utility, normally available through theJ                    "Applications" menu in Session Manager, is a convenientA                    way to see if the font is available. Start theMH                    application, select "Options", then select "Font...".E                    In the "Family (Foundry)" window, you will see thebJ                    list of fonts available. User-added TrueType fonts willJ                    normally be at the end of this list. Select the desiredF                    font family, then select the Size (dpi) (which willF                    always be 0(0) for TrueType fonts), and the variousJ                    font options (Weight, Slant, Width, etc.) should appearH                    in the next window. You should then be able to selectH                    the desired font and click <OK> or <Apply> to use it,A                    or <Cancel> to exit without changing the font.   J                                                                      11-21                                   DECwindows         H                    If you don't see all of the fonts you added, check toI                    see that the number at the beginning of the DECW$FONT_ I                    DIRECTORY*.DAT file is correct, that the files are setSF                    to world (or appropriate) access, and that TrueType1                    fonts are in Stream_LF format.   G                    Some applications require entering a full font name,oC                    which will look like the font description entry.e  H                    Please keep in mind that not all applications can useD                    every font which may be available on your system.C                    For example, DECterm is designed to use families D                    of fonts specifically designed for character cellD                    applications. Other fonts (specifically TrueType)F                    may work erratically, and may result in an unusableC                    display. It is best to use only monospaced fonts(B                    specifically intended for DECterm with DECterm.  F                    The SYS$COMMON:[SYSFONT.DECW.USER_TRUETYPE] doesn'tD                    exist on OpenVMS VAX V7.3 with DECwindows V1.2-6,E                    but the procedure above does appear to work if theeF                    directory is created and the instructions above are                    followed.                                                              11-22                         J                    _______________________________________________________  ,           12       Miscellaneous Information      D           __________________________________________________________B           12.1  Where can I find information on escape and control                 sequences?  E                    Information on escape and control sequences can beiG                    found in the OpenVMS I/O User's Reference Manual, ingG                    the chapter on the terminal driver. The chapter alsocH                    includes details on the general format and content of#                    these sequences.d  G                    Specific details on the escape and control sequences H                    supported by a particular serial device are typicallyH                    found in the documentation provided with the specificD                    device. Information on the sequences supported byG                    DECwindows DECterm terminal emulator are included ina0                    the DECwindows documentation.  C                    Examples of common escape and control sequences- H                    those typically used by the OpenVMS screen managementB                    package-can be found in the OpenVMS system fileE                    SYS$SYSTEM:SMGTERMS.TXT. (This file can be queried.I                    under program control using SMG$GET_TERM_DATA, and youDB                    don't need to use all of SMG to use this call.)  G                    The following refers to the function keys on the LK- I                    series keyboards found on the VT-series terminals suchlF                    as the VT220 and VT510, and the LK-series keyboardsG                    found on the OpenVMS workstations, and the keyboards G                    found on compatible terminals. (Though note that the F                    keyboard itself does not generate the sequence, theG                    terminal or terminal emulator generates the sequencenI                    in response to user input.) In the following, {CSI} is G                    decimal code 155 and can be replaced by the sequence H                    "{ESC}[" (without the quotes) particularly for seven-E                    bit operations, SS3 is decimal code 143 and can beoB                    replaced by "{ESC}O" particularly for seven-bitC                    operations. Older VT1xx series terminals and any1F                    other terminals operating with seven-bit characters  J                                                                       12-1    s          ,                    Miscellaneous Information        G                    should not be sent eight-bit operators such as {CSI}.                    and {SS3}.   5           PF1={SS3}P PF2={SS3}Q PF3={SS3}R PF4={SS3}SDK           KP0={SS3}p KP1={SS3}q KP2={SS3}r KP3={SS3}s KP4={SS3}t KP5={SS3}unS           KP6={SS3}v KP7={SS3}w KP8={SS3}x KP9={SS3}y KPCOMMA={SS3}l KPMINUS={SS3}m S           KPPERIOD={SS3}n ENTER={SS3}M DNARROW={CSI}B UPARROW={CSI}A LFARROW={CSI}D R           RTARROW={CSI}C FIND={CSI}1~ INSERT={CSI}2~ REMOVE={CSI}3~ SELECT={CSI}4~S           PREV={CSI}5~ NEXT={CSI}6~ F6={CSI}17~ F7={CSI}18~ F8={CSI}19~ F9={CSI}20~sJ           F10={CSI}21~ F11={CSI}23~ F12={CSI}24~ F13={CSI}25~ F14={CSI}26~W           HELP={CSI}28~ DO={CSI}29~ F17={CSI}31~ F18={CSI}32~ F19={CSI}33~ F20={CSI}34~v  G                    An example of working with escape sequences (in DCL)                     follows:   #                    $ esc5m = "*[5m" $                    $ esc5m[0,8] = 27#                    $ esc0m = "*[0m"t$                    $ esc0m[0,8] = 27E                    $ write sys$output esc5m + "blinking text" + esc0m   J                    Documentation on an ANSI terminal relatively similar to4                    the VT525 series is available at:  J                    o  ftp://ftp.boundless.com/pub/text/adds/docs/260_prog/  J                    o  ftp://ftp.boundless.com/pub/text/adds/docs/260_user/  A                    Also see the various documentation and manualss                     available at:  +                    o  http://www.vt100.net/a  E                    Information on the ReGIS graphics character set is                      available at:  H                    o  http://www.cs.utk.edu/~shuford/terminal/dec_regis_                       news.txt                      Also:  A                    o  http://www.boundless.com/Text_Terminals/VT/   7                    Also see Section 11.6, Section 8.13.i                      12-2* C  E          ,                    Miscellaneous Information      D           __________________________________________________________F           12.2  Does DECprint (DCPS) work with the LRA0 parallel port?                      No.  A                    The parallel printing port LRA0: found on many I                    OpenVMS Alpha systems is capable of some bidirectional H                    communications, with enough for basic operations with*                    most parallel printers.  E                    DECprint (DCPS) requires more than just the simplehI                    handshaking provided by the LRA0: port, therefore DCPSa5                    does not work with the LRA0: port.   D           __________________________________________________________A           12.3  How do I check for free space on a (BACKUP) tape?   H                    You cannot know for certain, though you can certainly3                    estimate the remaining capacity.   D                    Tape media is different than disk media, as disksI                    have a known and pre-determined fixed capacity. ModernaJ                    disks also appear logically perfect, based on bad blockI                    revectoring support and the extra blocks hidden withineG                    the disk structure for these bad block replacements.m  C                    The capacity of tape media is not nearly as pre-iI                    determined, and the capacity can vary across differentiB                    tape media (slightly different media lengths orB                    different foil markers or other variations, forI                    instance) and even on the same media over time (as badiJ                    spots in the media arise). Tapes can vary the amount ofG                    recording media required, depending on the remaining E                    length of the tape, the numbers of correctable and C                    uncorrectable media errors that might occur, the I                    numbers and sizes of the inter-record gaps and related F                    tape structure overhead, the particular media errorH                    recovery chosen, the tape density, the efficiently ofH                    any data compression in use, and the storage overheadG                    required by BACKUP, tar, and other similar commands.   D                    BACKUP using with the default settings results inH                    approximately 15% overhead, in terms of saveset size.H                    (eg: Assuming a 500 KB input, the total size would be                    575 KB.)   +                    Assuming no compression: >                    4 GB media / 575 KB saveset = 7294 savesets  J                                                                       12-3 d  $          ,                    Miscellaneous Information        ,                    Assuming 1:2 compression:?                    8 GB media / 575 KB saveset = 14588 savesetsu  1                                              Note   G                       There are no inter-record gaps on DAT tapes. WhenyF                       determining media capacity, you have to considerB                       these gaps with nine-track magtape media andC                       other formats with gaps. This is not the case D                       with DAT (DDS), as the format has no recordingC                       gaps. However, the block structure underneath F                       the variable length record recording is based onD                       a block size of circa 124 KB. Further, writingD                       doubles filemarks and such can cause a loss ofG                       up to the underlying block size. Thus even though C                       there are no inter-record gaps on DAT, largero6                       savesets are still usually best.  I                    The compression algorithms used on various devices arerG                    generally not documented-further, there is no way topF                    calculate the effective data compression ratio, theF                    tape mark overhead, and similar given just the dataG                    to be stored on tape-short of actually trying it, ofs                    course.  I                    A typical compression ratio found with "everyday" data 4                    is somewhere around 1:1.8 to 1:2.  1                                              Noten  @                       OpenVMS often uses the term COMPACTION forF                       compression control, as in the qualifier /MEDIA_(                       FORMAT=COMPACTION.  D           __________________________________________________________5           12.4  Correctly using license PAKs and LMF?   D                    If you have multiple LMF$LICENSE.LDB databases inE                    your OpenVMS Cluster, then each and every PAK must J                    be installed in each and every license database presentE                    in an OpenVMS Cluster. Even if you use /EXCLUDE or F                    /INCLUDE, you need to have a consistent set of PAKsG                    registered across all licensing databases present in '                    the OpenVMS Cluster.n                      12-4                ,                    Miscellaneous Information        G                    If your software license permits it, you can use theoC                    following two commands to transfer license PAKs:   $                    $ LICENSE COPY...D                    $ LICENSE ISSUE/PROCEDURE/OUTPUT=file product,...  I                    To display the particular license(s) required (such aspI                    when you receive a NOLICENSE error), use the followingm                     DCL sequence:  .                    $ SET PROCESS/PRIVILEGE=ALL!                    $ REPLY/ENABLE F                    $ DEFINE/SYSTEM/EXECUTIVE LMF$DISPLAY_OPCOM_MESSAGE  D                    This logical name will cause all license failuresF                    to generate OPCOM messages, and this will hopefullyF                    show which license(s) you need- there may well alsoG                    be additional license failures displayed, as variousUH                    products can check for and can be enabled by multipleG                    license PAKs. You will want to deassign this logical_"                    name when done.  8                    Some of the more common license PAKs:  L             DECnet Phase IV:   DVNETRTG, DVNETEND, DVNETEXT, or NET-APP-SUP*L             DECnet-Plus:       DVNETRTG, DVNETEND, DVNETEXT, or NET-APP-SUP*3             TCP/IP Services:   UCX, or NET-APP-SUP*eC             OpenVMS Alpha:     OPENVMS-ALPHA and OPENVMS-ALPHA-USERe&             OpenVMS VAX:       VAX-VMS-             OpenVMS Galaxy:    OPENVMS-GALAXY 7             Cluster (Alpha):   VMSCLUSTER, NET-APP-SUP* 7             Cluster (VAX):     VAXCLUSTER, NET-APP-SUP*   A                    Various NET-APP-SUP (NAS) license packages are_I                    available, each with differing collections of productsyC                    authorized. See the various NAS Software ProductsD                    Description (SPD) documents for specific details.  9                    o  http://h18000.www1.hp.com/info/spd/   H                       OpenVMS typically uses SPD 25.01.xx, SPD 41.87.xx,'                       and SPD 82.35.xx.n  C                    To determine which license PAK is failing (via aFI                    license check failure OPCOM message), use the command:.  K                    $ DEFINE/SYSTEM/EXECUTIVE LMF$DISPLAY_OPCOM_MESSAGE TRUE   J                                                                       12-5               ,                    Miscellaneous Information        ?                    Realize that defining this logical name willCA                    cause license checks that are otherwise hiddentE                    (unimplemented, latent, or part of a check for anymG                    of a series of licenses) to become visible. In otheriE                    words, expect to see zero or more spurious license G                    check calls when you define this, in addition to the 4                    check for the particular license.  F                    For information on PAKGEN and on generating licenseE                    PAKs, please see Section 10.10. For information on F                    obtaining commercial and hobbyist licenses, and forJ                    additional adminstrative information on LMF, please see3                    Section 2.8.4 and Section 2.8.1.,                                                                                  12-6e v  h                    J                    _______________________________________________________  -           13       Finding and Using Software       A                    For information on programming on OpenVMS, see                     Chapter 10.  D           __________________________________________________________I           13.1  Where can I find freeware/shareware/software for OpenVMS?u  E                    o  Details on many commercial OpenVMS products are :                       available in the catalog located at:  9                      o  http://www.hp.com/go/dspp_catalog   J                    o  The OpenVMS Freeware is is distributed with OpenVMS,J                       and is also available for download at various sites,.                       including the following:  >                      o  http://www.hp.com/go/openvms/freeware/  /                      o  ftp://ftp.montagar.com/   7                      o  ftp://mvb.saic.com/freewarev40/   B                       and at various other sites. The website alsoD                       includes various updates and new packages thatE                       become available after the CD-ROM distributions "                       are created.  E                       Submissions to the OpenVMS Freeware can be madet                       via:  >                      o  http://www.hp.com/go/openvms/freeware/  J                       To acquire the OpenVMS Freeware CD-ROM distribution,H                       you can order an OpenVMS distribution from HP (theH                       Freeware is included)(see the OpenVMS SPD for partH                       numbers), or you can specifically order a Freeware=                       distribution from HP under part number:h  #                      o  QA-6KZAA-H8   I                       The Freeware CD-ROM set contains a large assortmentrJ                       of freeware, and is a good starting point if lookingF                       for utilities. Many of the packages listed belowH                       are also on the Freeware CD. Some of the most oft-H                       requested OpenVMS tools on the Freeware CD include  J                                                                       13-1 F  D          -                    Finding and Using Software         G                       ZIP and UNZIP and GZIP (please see Section 13.11,rI                       MMK (make), PINE, PERL, TAR, UUENCODE and UUDECODE.aE                       Many other tools are available on the Freeware.   A                    o  The UUENCODE and UUDECODE tools and various F                       other tools are also available as part of TCP/IPF                       Services package. (Use the DCL command procedureH                       SYS$STARTUP:TCPIP$DEFINE_COMMANDS.COM available onH                       V5.0 and later to set up the necessary DCL foreignJ                       command symbols used for these and for various other9                       tools provided by TCP/IP Services.)s  D                    o  OpenVMS software (formerly at Western KentuckyG                       University (WKU) is now available via Madgoat and 4                       via Process Software archives:  A                      o  http://www.process.com/openvms/index.html   /                      o  http://www.madgoat.com/e  B                    o  The FILESERV packages are also available via)                       anonymous FTP from:   ;                      o  ftp://ftp.process.com/vms-freeware/d  C                      o  ftp.process.com, under [.WKU.VMS.FILESERV].   5                      o  ftp.vms.stacken.kth.se, underC4                         [.MIRRORS.WKU.VMS.FILESERV].  E                      o  ftp.ctrl-c.liu.se, under [.WKU.VMS.FILESERV].s  '                      o  ftp.riken.go.jp   G                      o  ftp.vsm.com.au, under kits and kits/decwindows.   C                      o  ftp.vsm.com.au, via the WWW instead of FTP.t  E                       The packages are also available via e-mail fromdF                       FILESERV@PROCESS.COM. Send the commands HELP andI                       DIR ALL in the body of a mail message to this emaildG                       address for further information on retrieving then                       files.  C                    o  Arne Vajhj operates an OpenVMS website, withe6                       software and other pointers, at:  4                      o  http://www.levitte.org/~ava/                      13-2                -                    Finding and Using Software         G                    o  Jouk maintains a summary of various public-domain F                       and open-source software ports, and specifically?                       ports of packages for use on OpenVMS, at:   =                      o  http://nchrem.tnw.tudelft.nl/openvms/h  G                    o  The Kermit file transfer package is available at:o  7                      o  http://www.columbia.edu/kermit/t  2                      o  ftp://kermit.columbia.edu/  -                    o  ZMODEM is available at:   7                      o  ftp://ftp.cs.pdx.edu/pub/zmodem   F                       See the FILES file in that directory for furtherH                       details. Note that this freeware version of ZMODEMI                       will interoperate only with ZMODEM software that isrJ                       licensed from Omen Technology. (This package is alsoJ                       available on various of the Freeware distributions.)  C                    o  A good source of software for OpenVMS systemsoF                       and for various other platforms is the EncompassH                       (formerly known as DECUS) library. Online catalogs@                       are available as well as some software via  +                      o  ftp://ftp.decus.orgn  2                      o  gopher://gopher.decus.org/  -                      o  http://www.decus.org/1  F                    o  DECUS SIG Tape collections are available on Mark(                       Berryman's system,  +                      o  ftp://mvb.saic.com/t  G                    o  David Jones's DECthreads-based HTTP_SERVER World- I                       Wide Web server for OpenVMS, often known as the OSUD                        webserver:  .                      o  http://kcgl1.eng.ohio-9                         state.edu/www/doc/serverinfo.htmly  J                    o  Secure Shell (SSH) support for OpenVMS is available.H                       Use of SSH V2 with current updates is recommended,  J                                                                       13-3    O          -                    Finding and Using Software         E                       as the security of older SSH releases have been_6                       compromised. Server for OpenVMS:  >                      o  Secure Shell (SSH) Server for OpenVMS:  1                         o  http://kcgl1.eng.ohio- 5                            state.edu/~JONESD/ssh/DOC/w  C                         Secure Shell (SSH) FISH Client for OpenVMS:o  6                         o  http://www.free.lp.se/fish/  G                         SSH V2 support is included with TCP/IP Services B                         V5.4 and later, and support is likely alsoI                         available within available third-party IP stacks.h  ;                         For information on the SSH key fileaH                         configuration, see topic 151.22 and following inH                         the VMS notes conference on the Deathrow ClusterE                         (deathrow.vistech.net and openvms-rocks.com).DF                         You can telnet into the host, and an announcedH                         anonymous login is/was available; username DEMO,&                         password USER.  B                       Information on OpenSSL (SSLeay) for OpenVMS:  6                      o  http://www.free.lp.se/openssl/  3                      o  http://www.free.lp.se/fish/u  H                       Information on OpenSSL (SSLeay) and OSU Web server%                       interoperation:O  @                      o  http://www.ourservers.net/openvms_ports/  H                       OpenSSL is included with OpenVMS V7.3-1 and later.  F                    o  DECwindows Motif V1.2-3 includes NCSA Mosaic 2.4F                       built for TCP/IP Services (UCX). V1.2-4 includesF                       Spyglass Enhanced Mosaic, which supports many ofI                       the Netscape enhancements. Versions of the NetscapepH                       Navigator and particularly the Mozilla Web BrowserG                       are also available for OpenVMS. The Compaq SecuretI                       Web Browser (CSWB) kit is a packaged version of the 6                       Mozilla.org Mozilla Web Browser.  I                    o  A port of the NCSA Mosaic web browser that supports G                       TCP/IP Services, Multinet and SOCKETSHR/NETLIB is %                       available from:   6                      o  ftp://wvnvms.wvnet.edu/mosaic/                      13-4t h             -                    Finding and Using Software         A                       Versions of the Mosaic web browser are also 0                       available on the Freeware.  H                    o  Lynx (a character-cell World-Wide-Web web browser)'                       is available fromr  8                      o  ftp://ftp2.cc.ukans.edu/pub/lynx  I                       Versions of Lynx, a character-cell web browser, are =                       also available on the OpenVMS Freeware.P  I                    o  The Netscape Navigator and Mozilla web browsers are #                       available at:T  O                      o  http://www.openvms.compaq.com/ebusiness/Technology.htmle  /                      o  http://www.mozilla.org/   E                    o  PGP (Phil Zimmerman's "Pretty Good Privacy") is J                       available from various distribution sites, includingI                       those listed in the PGP FAQ. Information on PGP and H                       on OpenVMS downloads of PGP is available. Relevant#                       URLs include:o  -                      o  http://www.ipgpp.org/C  ;                      o  http://web.mit.edu/network/pgp.htmlS  ,                      o  http://www.pgpi.com/  ?                      o  http://www.yrl.co.uk/~phil/pds/pds.htmlo  +                      o  http://www.nai.com/f  B                    o  GNU Privacy Guard (GPG, GnuPG) is available.  C                       Search the comp.os.vms newsgroup archives for C                       information regarding GnuPG; the source code,eG                       binaries for various platforms, and documentation +                       are all available at:   -                      o  http://www.gnupg.org/e  J                       The OpenVMS source code and OpenVMS Alpha images can"                       be found at:  H                      o  http://saf.bio.caltech.edu/pub/SOFTWARE/openvms/  B                      o  ftp://ftp.process.com/vms-freeware/mathog/  G                       As of this writing, the port only runs on OpenVMS,H                       Alpha, but an investigation of an OpenVMS VAX port8                       is reportedly under consideration.  J                                                                       13-5 .  W          -                    Finding and Using Software         G                    o  An archive of the CENA DECwindows, X Windows, and I                       VMS software packages can be found at the followingD                       sites:  0                      o  http://decwarch.free.fr/  6                      o  ftp://ftp2.cnam.fr/decwindows/  ;                      o  ftp://ftp.ctrl-c.liu.se/decwindows/t  H                      o  ftp://ftp.vms.stacken.kth.se/mirrors/decwindows/  ?                      o  http://www.multimania.com/pmoreau/decw/T  G                       Other FTP mirror sites for the DECwindows archiveo                       include:  0                      o  axp.psl.ku.dk (Multinet)  .                      o  ftp2.cnam.fr (MadGoat)  F                       ftp.x.org (in /contrib/vms) is effectively not aG                       mirror, but it does have various OpenVMS packages 2                       from the DECwindows archive.  H                       A list of the http mirror sites for the DECwindows.                       archive is available at:  Q                      o  http://axp616.gsi.de:8080/wwwar/cena/decwindows/cena.htmlT  I                       Various of these packages are also available on the                        Freeware.   C                    o  ImageMagick is an X11 package for display anduE                       interactive manipulation of images. The package-F                       includes tools for image conversion, annotation,D                       compositing, animation, and creating montages.E                       ImageMagick can read and write many of the moreeG                       popular image formats (e.g. JPEG, TIFF, PNM, XPM,e&                       Photo CD, etc.).  3                      o  http://www.imagemagick.org/S  F                       Versions of ImageMagick are also included on the                       Freeware.s  C                    o  XV is a image viewing and editing tool and is-%                       available from:1  6                      o  ftp://ftp.cis.upenn.edu/pub/xv  /                      o  http://www.sanface.com/                       13-6C T  s          -                    Finding and Using Software         A                      o  ftp://www-pi.physics.uiowa.edu/~dyson/xv/   I                    o  Many software packages are available for displayinghE                       various bitmap files (.JPG, .GIF, .BMP, etc) oneG                       OpenVMS. Xloadimage, Xli, Xv, ImageMagick are thepG                       most common tools used under OpenVMS. Various webeD                       browsers such as Mozilla (qv) can also displayH                       various file formats on OpenVMS. You can find some?                       of these tools at the DECwindows Archive:e  I                      o  http://www.multimania.com/pmoreau/decw/index.htmlt  J                      o  http://www.multimania.com/pmoreau/decw/images.html  G                    o  GHOSTSCRIPT (gs) and GHOSTVIEW (gv) are available >                       from the Freeware V5.0 and Freeware V6.0$                       distributions:  >                      o  http://www.hp.com/go/openvms/freeware/  B                       Versions are also available on the Freeware.                         Also see:y  :                      o  http://www.cs.wisc.edu/~ghost/gnu/  G                    o  XPDF, a DECwindows viewer for PDF (Adobe Acrobat)n/                       files, is available from:   4                      o  http://www.foolabs.com/xpdf/  F                       Software and installation kits for XPDF are also0                       available on the Freeware.  H                       Beware: the XPDF tool included on OpenVMS FreewareG                       V4.0 is dated, and has been found to have various J                       bugs. Use the Freeware V5.0 version of the XPDF kit,(                       or (better) later.  F                       A Java-based PDF viewer is available from Adobe,E                       and is known to operate on recent OpenVMS Alphac                       releases:e  -                      o  http://www.adobe.com/   E                    o  Various OpenVMS-related tools-both freeware and F                       shareware-such as txt2pdf-are available from at:  /                      o  http://www.sanface.com/r  J                                                                       13-7    h          -                    Finding and Using Software         C                    o  The MPEG library version 1.1 is available for .                       OpenVMS VAX and Alpha at  I                      o  ftp://ftp.x.org/contrib/vms/mpeglib-11-vms.readmei  F                      o  ftp://ftp.x.org/contrib/vms/mpeglib-11-vms.zip  J                       Various MPEG players and related tools are available&                       on the Freeware.  E                    o  An Archie clone is available at INFO.CS.PUB.RO. F                       Telnet to that machine, and login as VMSARCI. ItH                       contains now listings for over 30 ftp servers with<                       over 14 gigabytes of OpenVMS software.  J                       The most useful commands are LIST, which generates aJ                       list of scanned ftp servers, and FIND string, whichsG                       looks for a file containing "string" in the name;hI                       the search modes are only "substring" [default] andnI                       "exact", and regex search is not supported (so FIND I                       EMACS will work, but FIND *EMACS* or FIND *EMACS*.* @                       will not). The search is case-insensitive.  G                       The maintainer of the site (stfp@roipb.cs.ipb.ro)lF                       requests that anyone submit notifications of FTPJ                       servers with OpenvMS software that are not listed on                       the site.0  D                    o  The Levitte (extended :-) Family (and OpenVMS)                       website:  /                      o  http://www.levitte.org/Y  4                      o  http://www.levitte.org/~ava/  B                    o  Robert Alan Byer's OpenVMS Hobbyist Systems,J                       including OpenVMS public domain software and various                       ports:  2                      o  http://www.ourservers.net/  0                    o  CalTech Software Archives:  L                      o  http://saf.bio.caltech.edu/pub/software/openvms/aaa_$                         contents.txt  =                    o  DJE Systems Website (David J. Dachtera)   ;                      o  http://www.djesys.com/freeware/vms/c  "                    o  Web Servers:                      13-8  m             -                    Finding and Using Software         C                       Apache Web server (HP Secure Web Server (SWS,i&                       formerly CSWS)):  O                      o  http://www.openvms.compaq.com/ebusiness/Technology.html   0                      o  http://www.er6.eng.ohio-7                         state.edu/~jonesd/apache/1_3_9/   B                       The SOAP Toolkit is available at the OpenVMS                       website.  $                       OSU Web server  0                      o  http://www.er6.eng.ohio-9                         state.edu/www/doc/serverinfo.htmln  5                      o  http://www.kjsl.com/archives/e  C                      o  email list: VMS-WEB-daemon-Request@KJSL.COMS  %                       WASD Web server   4                      o  http://wasd.vsm.com.au/wasd/  *                       Purveyor Web server:  F                      o  email list: listserv@cjis.ci.lincoln.ne.us, noE                         subject, one line message: SUBSCRIBE PURVEYOR   9                       FastCGI software is available from:   9                      o  http://www.DigitalSynergyInc.com/_  E                    o  CD-R (CD-Recordable) media tools are available,f-                       please see Section 9.7._  6                    o  Grace (WYSIWYG 2D plotting tool)  @                      o  http://plasma-gate.weizmann.ac.il/Grace/  J                    o  The POV-Ray ("Persistance of Vision" Raytracer) ray-J                       tracing graphics package is available on the OpenVMS                       Freeware.o  5                    o  Majordomo mailing list handler:   O                      o  http://www.openvms.compaq.com/ebusiness/Technology.htmls  H                    o  PINE (OpenVMS tools for sending and receiving MIME                       mail):  >                      o  ftp://ftp2.kcl.ac.uk/pub/vms/pine-vms/  G                      o  http://www.agh.cc.kcl.ac.uk/files/vms/pine-vms/   J                                                                       13-9 i  w          -                    Finding and Using Software         I                       A MIME tool is available in OpenVMS V7.2 and later.e  D                       Also see the mmencode base64 encode and decode#                       available at:   E                      o  http://nucwww.chem.sunysb.edu/htbin/software_                           list.cgi  ?                    o  Menufinder (menu-driven system managementg#                       environment):   <                      o  http://www.itre.com/mf/download.html  B                    o  SYSLOGCLIENT (a client for processing SYSLOGF                       requests) has been provided for download by Mark                        Hemker at:  B                      o  http://home.insightbb.com/~hemker/vms.html  .                    o  tcgmsg, pvm, mpi, linda:  @                      o  ftp://v36.chemie.uni-konstanz.de/tcgmsg_*                         vms/tcgmsg_vms.zip  D                    o  OpenVMS software that can control a Tripp-LiteE                       Uninterruptable Power Supply (UPS) is availabler                       from:S  T                      o  http://saf.bio.caltech.edu/pub/software/openvms/tcontrol.zip  H                       UPShot web-based software for controlling a UPS is%                       available from:a  <                      o  http://www.tmesis.com/apc/beta.htmlx  J                       OpenVMS software for controlling Liebert UPS devices=                       are available from the Liebert website:g  =                      o  http://www.liebert.com/apc/beta.htmlx   J                    o  Examples of using the OpenVMS Foreign MAIL interface'                       are available at:   V                      o  http://www.hhs.dk/anonymous/pub/vms/collection/foreignmail.zip  G                      o  http://www.hhs.dk/anonymous/pub/vms/nbl/nbl.zip   H                    o  For tools to manage or to search your OpenVMS MAIL                        file, see:  U                      o  http://vms.process.com/scripts/fileserv/fileserv.com?MLSEARCHW                      13-10 {  }          -                    Finding and Using SoftwareR        I                    o  AscToHTM attempts to convert any plain text file toSI                       HTML, while AscToTab restricts itself to files thatIH                       are plain text tables. (Versions are also availabe/                       on the OpenVMS Freeware).   B                      o  http://www.jafsoft.com/asctohtm/index.html  B                      o  http://www.jafsoft.com/asctotab/index.html  F                    o  Information on the SAMBA package, a package thatF                       provides SMB-based Microsoft Windows PC disk andB                       print services for OpenVMS, is available at:  F                      o  http://ifn03.ifn.ing.tu-bs.de/ifn/sonst/samba-                          vms.html  -                      o  http://www.samba.org/u  >                      o  http://www.hp.com/go/openvms/freeware/  G                       To subscribe to the SAMBA-VMS mailing list e-mailaE                       listproc@samba.org with no subject line and the 4                       following single line of text:  8                       subscribe samba-vms Your Full Name                         Also see::  /                      o  http://lists.samba.org/u  E                    o  The Perl language is available for OpenVMS, see /                       Section 13.9 for details.u  3                    o  XML is available for OpenVMS.s  D                       Source code of an XML Parser is available from                       Oracle.s                         Also see:   ;                      o  http://www.python.org/sigs/xml-sig/   H                       An XML parser is available as part of OpenVMS V7.3                        and later.  G                    o  Python kit, and resource, and documentation sites                        include:  D                      o  http://www.pi-net.dyndns.org/anonymous/kits/  4                      o  http://vmspython.dyndns.org/  .                      o  http://www.python.org/  J                                                                      13-11 y  e          -                    Finding and Using Software         =                    o  GTK+ (The GIMP GUI Tookit) for OpenVMS:_  O                      o  http://www.openvms.compaq.com/ebusiness/Technology.htmlK  D                    o  The OpenVMS Porting Library now available, andG                       is intended to permit easier porting of C and C++ @                       applications from UNIX systems to OpenVMS:  O                      o  http://www.openvms.compaq.com/ebusiness/Technology.html   ,                       GTK is also available.  /                    o  Mlucas (specialized FFT):g  @                      o  ftp://hogranch.com/pub/mayer/README.html  E                    o  Tools to monitor the terminals and the activityTE                       of other OpenVMS users (in addition to existingtF                       auditing capabilities in OpenVMS) are available.C                       Peek and Spy (Networking Dynamics) and ContrldG                       (Raxco) are two of the commercial packages, whilecE                       the freeware Supervisor package is available ono"                       OpenVMS VAX.  :                      o  http://www.networkingdynamics.com/  -                      o  http://www.raxco.com/l  )                    o  Python for OpenVMS:   .                      o  http://www.python.org/  4                       Also see the OpenVMS Freeware.  3                    o  Various packages for OpenVMS:   L                      o  http://richj.home.mindspring.com/richware/index.html  H                      o  http://www3.sympatico.ca/n.rieck/links/cool_vax_                          vms.html  E                    o  TSM (Terminal Server Manager) is available via:   0                      o  Look at Freeware V5.0 at>                         http://www.hp.com/go/openvms/freeware/  G                      o  Beware: The TSM saveset shipped on the FreewaresA                         V5.0 disk media is known to be corrupted.5C                         Download a new copy of the saveset from the                       13-12 s  =          -                    Finding and Using Software         E                         Freeware V5.0 FTP server or from the Freewarel%                         V5.0 website.   &                    o  TCL for OpenVMS:  D                      o  ftp://sapodilla.rsmas.miami.edu/pub/VMS-tcl/  J                    o  make, gmake, mmk and other build tools are available&                       on the Freeware.  J                    o  An OpenVMS port of the ht://Dig web search engine is#                       available at:a  5                      o  ftp://ftp.pdv-systeme.de/vms/   >                    o  A mySQL database client is available at:  A                      o  http://mysql.holywar.net/Downloads/MySQL-e:                         3.22/mysql-3.22.25-clients-vms.zip  A                      o  http://mysql.holywar.net/Downloads/MySQL- =                         3.22/mysql-3.22.25-clients-vms.readme   E                       For additional information related to the mySQL C                       port, please search the comp.os.vms newsgroup E                       archives. A MySQL port is also available on the '                       OpenVMS Freeware.   >                      o  http://www.hp.com/go/openvms/freeware/  F                    o  If you need to change the file modification dateJ                       and are looking for a utility such as the UNIX touchH                       tool, look at DFU on the OpenVMS Freeware (DFU SETG                       or simular), or use an existing DCL commands sucho                       as:s  K                       $ SET FILE/PROTECT=(current_protection_mask) [...]*.*   I                    o  A table listing translations between UNIX shell and G                       OpenVMS DCL commands was posted to comp.os.vms bysJ                       Christopher Smith some time ago. This page should beC                       available from the google newsgroup archives.   I                       For information on and the status of the OpenOffice23                       port for OpenVMS, please see:   5                      o  http://www.oooovms.dyndns.org   J                                                                      13-13               -                    Finding and Using Softwarep        I                    o  The UNIX touch tool is available via various means:   5                       $ RENAME filename.ext;version *t  M                      o  http://nucwww.chem.sunysb.edu/helplib/@hvmsapps/TOUCH   B                       MadGoat FILE tool (see the MadGoat archives)  :                    o  use /REVISION_DATE or /CREATION_DATE  =                    o  The DFU tool (see the OpenVMS Freeware)t                      o  The pair:   ;           $ set file 'p1' /acl=(ident=[system],access=none) C           $ set file 'p1' /acl=(ident=[system],access=none) /deleteE  *                       $ SET FILE/VERSION=0  /                    o  The following touch hack:(  ,           $!   Command procedure SETDATE.COM           $!7           $!   Changes the DATES for an input file to a "           $!   file named OUTFILE.           $!$           $assign/nolog 'p1' outfile.           $convert/fdl=sys$input 'p1' outfile:           date            creation   01-apr-2010            expiration 01-Apr-2012            revision   01-Apr-2011           backup
           ...i  @                    o  The following RMS system service sequence:  B                      o  sys$open(),  with the XABRDT XAB structure                          chained.  E                      o  set the desired values within the XABRDT XAB.   #                      o  sys$close()e  H                    Various OpenVMS tools and utilities are available at:  <                    o  http://wwwvms.mppmu.mpg.de/vmssig/src/  H                    OpenVMS ports of the xmcd and MPlayer tools have also.                    been reported as available.                      13-14 S  i          -                    Finding and Using Software       D           __________________________________________________________8           13.2  Where can I find UNIX tools for OpenVMS?  J                    There are OpenVMS DCL and UNIX shell command comparison$                    tables posted at:  E                    o  http://wwwvms.mppmu.mpg.de/vmsdoc/UNIX_VMS_CMD_                        XREF.HTMLi  I                    o  http://www.mcsr.olemiss.edu/unixhelp/VMStoUNIX.htmlo  E                    The GNV package (Section 13.2.6) and the various CfJ                    library calls available in current/recent libraries are9                    the replacement for the POSIX package.2  '           _____________________________ /           13.2.1  C system and library routinese  J                    Common C system and library routines are present in theJ                    DEC C run-time library, which is available for V5.5 andH                    later, and is shipped in V6.1 and later. DEC C is theH                    upgrade for VAX C, DEC C and VAX C can coexist on theI                    same system OpenVMS VAX system, and both compilers cant6                    be enabled via the "C" license PAK.  G                    Also see SYS$EXAMPLES:, and (if either is installed)lE                    the DECW$EXAMPLES: and TCPIP$EXAMPLES (or prior toe.                    V5.0, UCX$EXAMPLES:) areas.  F                    The HP C Run-Time Library documentation is now partE                    of the OpenVMS Operating System Documentation, and A                    separate from the HP C compiler documentation.   7                    o  http://www.hp.com/go/openvms/doc/   I                    Additionally, there have been large-scale increases to H                    the capabilities and features available within recentH                    HP C compilers. If you have not taken the opportunityD                    to skim the current C compiler documentation, youE                    may well be surprised with the sheer volume of newh2                    C capabilities discussed there.        J                                                                      13-15 f  r          -                    Finding and Using Softwaren      '           _____________________________12           13.2.2  X Windows utilities and routines  @                    Various X Windows utilities are available forG                    DECwindows. DECwindows is an implementation of the XoJ                    Windows environment and libraries, and provides variousF                    libraries, and provides various desktop interfaces,1                    including COE, Motif, and XUI.i  G                    xwd, xev, mosaic web browser, xrdb, bmtoa and atobm, D                    xpr, ico, etc. are available. Look in DECW$UTILS:A                    in DECwindows Motif V1.2-3 and later. Also seee?                    DECW$EXAMPLES: for example X and C programs.   G                    Miscellaneous tools and examples are also available. F                    Examples include the older DWAUTH (X Windows SYSUAFG                    authorize-like tool) tool, various versions of grep,eH                    fgrep, yacc, vmstar, uuencode, gawk, etc. html tools,F                    the mx SMTP mail exchange package, X windows flightA                    simulator, the mxrn X windows news reader, the/E                    OSU HTTPD WWW server, a WWW gopher browser, CastleeD                    Wolfenstein (Wolf3D), etc. are all on the variousD                    OpenVMS Freeware distributions. (Also see the GNVH                    package (Section 13.2.6) for related materials, APIs,                    and tools.)  '           _____________________________i9           13.2.3  TCP/IP Tools and Utilities for OpenVMS?o  I                    TCP/IP Services (formerly known as UCX) contains toolsrF                    such as ping, uuencode, smtp, snmp, rcp, nfs, tnfs,                    etc.   I                    OpenVMS V6.2 and later includes DCL-integrated support B                    for various IP tools, with commands such as SETE                    HOST/TELNET, and COPY/FTP. This interface requires G                    the installation of an IP stack, and TCP/IP Services F                    (UCX) V3.3 and later as well as any then-current orI                    now-current third-party IP stack can be used. Once the H                    IP stack is installed and configured, the DCL commandG                    qualifiers such as /FTP, /RCP, /RLOGIN, /TELNET, and J                    /TN3270 are available on various DCL commands including                    DIRECTORY.   G                    Various C programming examples in TCPIP$EXAMPLES andU@                    (on releases prior to V5.0) in UCX$EXAMPLES:.                      13-16 l  n          -                    Finding and Using Softwares      '           _____________________________ $           13.2.4  The vi text editor  D                    vile, vim and elvis are all clones of the vi text6                    editor, and all operate on OpenVMS.  I                    Versions of vile are available on the Freeware and at:a  D                    o  http://www.clark.net/pub/dickey/vile/vile.html  #                    vim: vi improvedo  2                    o  http://www.polarfox.com/vim/  '           _____________________________h'           13.2.5  The Emacs Text Editora  I                    OpenVMS ports of versions of the Emacs text editor can/J                    be found on various OpenVMS Freeware distributions (eg:J                    OpenVMS Freeware V7.0 has a port of Emacs 21.2), and at/                    various web sites including:M  H                    o  http://www.glug.org/people/ttn/software/emacs-for-                       vms/  C                    "Emacs isn't a text editor, it's a way of life."n  I                    For comparisions of OpenVMS text editors and UNIX, see !                    the following:   J                    o  http://www.unh.edu/cis/docs/vms-to-unix/Emacs/cheat-                        sheet.html  '           _____________________________ (           13.2.6  GNV: Various GNU tools  G                    Information on the GNU on VMS (GNV; "GNU's Not VMS")iG                    Project, which aims to port and provide GNU softwarejH                    (bash, flex, bison, tar, grep, gcc emulation, etc) to,                    OpenVMS, is available at:  1                    o  http://gnv.sourceforge.net/1  !                    Software info:   9                    o  http://vms.gnu.ai.mit.edu/software/o  $                    Software archive:  @                    o  ftp://vms.gnu.ai.mit.edu/gnu-vms/software/  J                                                                      13-17               -                    Finding and Using Softwarev        H                    Various GNU tools are also available on the Freeware.  '           _____________________________i            13.2.6.1  GCC compiler  F                    Yes, gcc is available for OpenVMS Alpha and OpenVMS                    I64.   E                    o  gcc compilation compatibility for OpenVMS Alpha D                       and I64 is available as a component of the GNVG                       package. This causes the HP C compiler to emulateiF                       the interface and compilation behaviours of gcc.  N                       http://h71000.www7.hp.com/opensource/opensource.html#gnv  #                    o  GNV Home Pageb  1                       http://gnv.sourceforge.net/f  A                    o  GCC Home Page - GNU Project - Free Softwaree&                       Foundation (FSF)  )                       http://gcc.gnu.org/.                      o  GNU/FSF   C                       ftp://ftp.tmk.com/vms-freeware/gcc-for-alpha/   *                    o  Help GCC - SUNY NCSB  I                       http://nucwww.chem.sunysb.edu/helplib/@hvmsapps/GCCo  *                    o  Redhat's gcc Archive  V                       ftp://ftp.mirror.ac.uk/sites/sources.redhat.com/ftp/gcc/releases  7                    o  Malmberg's Ftp Service - gcc281_ua  <                       ftp://ftp.qsl.net/pub/wb8tyw/gcc281_u/  8                    o  updated header-files for GNU C 2.8  <                       ftp://ftp.qsl.net/pub/wb8tyw/gcc281_u/  B                    In addition to gcc, the HP C compiler and otherE                    development tools are part of the OpenVMS HobbyistVH                    licensing program for non-commercial users, and theseI                    and other tools are available to commercial developers I                    via the HP DSPP partner program. (See Section 2.15 forS(                    information on DSPP.)                      13-18 a             -                    Finding and Using Software       D           __________________________________________________________6           13.3  What is the status of PL/I on OpenVMS?  G                    Kednos now owns and supports the former DIGITAL PL/I G                    compiler and run-time support on OpenVMS, and is the E                    contact for product status, support and associatedo                    plans.S  C                    As of this writing, (older) versions of the PL/I D                    run-time library and associated supporting imagesH                    remain available on OpenVMS VAX and on OpenVMS Alpha,G                    including the DECmigrate VEST translated images run-nI                    time support on OpenVMS Alpha, though neither the PL/I G                    shareable image nor the DECmigrate (AEST) translated D                    image support for the PL/I run-time are availableC                    (from HP) on nor present on OpenVMS I64 systems.ME                    Newer versions of the PL/I run-time library may beoC                    (are?) available from Kednos for various OpenVMStG                    platforms; please contact Kednos for product detailsp$                    and availability.  +                    o  http://www.kednos.comr  D           __________________________________________________________8           13.4  Where can I get the Mozilla Web Browser?  G                    Mozilla.org is an open source organization providing E                    HTML-related tools; software that is the basis for J                    various utilities including the Mozilla web browser and8                    the Secure Web Browser (SWB) package.  >                    OpenVMS Engineering is continuously portingJ                    Mozilla.org's web browser to OpenVMS, and OpenVMS portsE                    of the current Mozilla baselevels and releases aretG                    available. The OpenVMS Mozilla port includes the webhI                    browser, the mail client, the Composer HTML editor, an H                    IRC chat client, a netnews (NNTP) reader, and various                    other tools.e  G                    The Mozilla web browser download and the development H                    and release schedules for this and for other Mozilla-2                    related tools are available at:  -                    o  http://www.mozilla.org/e  J                                                                      13-19 e  e          -                    Finding and Using Softwarer        B                    The available Secure Web Browser (SWB) kit is aC                    packaged version of the Mozilla Web Browser, and J                    typically the SWB version number matches the underlying#                    Mozilla version.r  C                    A hardware configuration appropriate for MozillabE                    generally involves an OpenVMS Alpha system with an F                    EV56 Alpha microprocessor, or an EV6 or more recentF                    processor, and with 256 megabytes of system memory.F                    The performance of Mozilla on EV5-based and earlierF                    Alpha microprocessor systems is generally viewed asH                    inadequate, this due to the extensive use of an AlphaF                    instruction subset that is first available with the2                    EV56 microprocessor generation.  <                    Mozilla is not available for OpenVMS VAX.  I                    Various versions of the Netscape Navigator web browser 6                    are based on the Mozilla code-base.  D           __________________________________________________________1           13.5  Where can I get Java for OpenVMS?   D                    Java is available on and is included with OpenVMSH                    Alpha, starting with the OpenVMS Alpha V7.2 and laterI                    releases. Java download kits are available for OpenVMS 1                    Alpha V7.1 and later releases.   H                    Java is not available on OpenVMS VAX. As for why: theE                    Java language definition requires a floating point J                    format (IEEE) that is not native to VAX, and this wouldI                    require the emulation of all floating point operations G                    within Java applications. Further, the C source code I                    used to implement for Java itself is heavily dependent I                    on passing IEEE floating point values around among the H                    many internal subroutines, and adding support for VAXH                    would entail changes to the HP C compiler for OpenVMSJ                    VAX-and specifically to the VAX VCG code generator thatI                    is used by HP C on OpenVMS VAX systems-in order to add I                    support for passing IEEE-format floating point doubles G                    around. Alternatively, extensive changes to the Java/J                    source code to remove the assumption that the double is0                    an IEEE floating point value.                      13-20 o  m          -                    Finding and Using Softwaret        I                    There are currently no plans to make a version of Java J                    available for OpenVMS VAX. (A prototype version of JavaI                    was created for OpenVMS VAX, and performance was foundt.                    to be inadequate. At best.)  G                    If Java2 or other environment lifts the requirementshB                    for IEEE floating point as part of the language>                    definition, this decision may be revisited.  J                    If you are having problems with Display Postscript, youI                    need to upgrade your Java kit-1.2.2-3 and later removeoH                    the requirement for Display Postcript extensions, andF                    Java 1.2.2-3 is required with DECwindows V1.2-6 and                    later.h  H                    For additional information on Java for Alpha systems,I                    please see the OpenVMS documentation (V7.2 and later),.*                    and the following site:  A                    o  http://www.compaq.com/java/alpha/index.htmlm  E                    HP Secure Web Server (SWS, formerly CSWS) includes H                    CSWS_JAVA, which provides the following Apache TomcatC                    technologies: JavaServer Pages 1.1, Java Servlet E                    2.2, and MOD_JK. Also available is CSWS_PHP, a PHPdJ                    implementation. (SWS is based on the Apache web server.                    See SOFT1.)  D           __________________________________________________________7           13.6  Obtaining user input in DCL CGI script?n  E                    If you choose to use the GET method, then the formyG                    data is available in the DCL symbol QUERY_STRING, ins&                    URL-encoded format.  H                    If you use the POST method, then you need to read theE                    form data from stdin. For a DCL CGI script running H                    under the Netscape FastTrack web server, you can read=                    the data using the following READ command:   .                    $ READ SYS$COMMAND postdata  .                    to read the information in.  A                    The following describes the use of DCL commandwE                    procedures as CGI scripts with the OSU web server:t  H                    o  http://www.levitte.org/~ava/cgiscripts_other.htmlx  J                                                                      13-21 F  w          -                    Finding and Using Softwareu        I                    DCL CGI is also discussed in the Writing Real Programs B                    in DCL book, and in the Ask The Wizard website.  D           __________________________________________________________C           13.7  How can a batch job get its own batch entry number?o  I                    To have a batch procedure retrieve its own batch entry -                    number, use the following:d  8                    $ Entry = F$GETQUI("DISPLAY_ENTRY", -A                        "entry_number","display_entry","this_job")   H                    Remember that the entry numbers issued by the OpenVMSG                    Job Controller are always opaque longword values. Do F                    not assume you know the format of the entry number,H                    nor the range of entry numbers you might see, nor theE                    algorithm that is used to assign enty numbers. You 8                    should simply assume opaque longword.  D           __________________________________________________________=           13.8  How do I convert to new CMS or DTM libraries?w  F                    A change was made to the format of the CMS databaseD                    for CMS libraries starting with V3.5-03-to ensureH                    that earlier versions of CMS are unable to access theI                    database once the "conversion" to V3.5-05 and later is G                    made, you must issue the following two commands when J                    upgrading from V3.5-03 and prior. (The only differencesF                    between CMS version V3.5-03 and CMS version V3.5-05G                    involve changes to ensure that no earlier version ofPG                    CMS can access the "converted" database, and corruptF                    it.)   C                    To perform the "conversion", issue the following 9                    commands for each CMS library present:   ;                    $ RENAME disk:[directory]00CMS.* 01CMS.*r9                    $ COPY NLA0: disk:[directory]00CMS.CMSs  E                    The new file 00CMS.CMS must have the same securityhH                    settings as the 01CMS.CMS file, and is created solelyD                    to ensure continued compatibility with tools thatH                    expect to find a 00CMS.CMS file (eg: various versionsA                    of the Language-Sensitive text editor LSEDIT).c                      13-22               -                    Finding and Using Software         F                    If you choose to install and use the longer variantJ                    names support that is available with CMS V4.1 or later,H                    you cannot mix earlier CMS versions within a cluster.F                    If you attempt to mix older and newer versions, youH                    will typically see the following BADLIB and BADTYPSTRI                    error sequence when accessing the CMS library from the &                    older CMS versions:  L                    %CMS-F-BADLIB, there is something wrong with your libraryN                    -CMS-F-BADTYPSTR, header block type is 145; it should be 17  G                    Please see the CMS V4.1 release notes for additional #                    details on this.e  F                    To perform the equivalent "conversion" for DEC TestJ                    Manager (DTM) V3.5 and prior versions to V3.6 and laterJ                    versions, issue the following DCL commands for each DTM#                    library present:   ;                    $ RENAME disk:[directory]00DTM.* 01DTM.* 9                    $ COPY NLA0: disk:[directory]00DTM.DTM   E                    Like CMS, this change is intended to prevent older F                    versions of DTM from accessing newer libraries, andH                    corrupting the contents. Like CMS, once the librariesE                    are renamed, they cannot and should not be renamedwI                    back to the older names; like CMS, the changes are not '                    downward-compatible.i  G                    To convert version 1 (ancient) DTM and CMS libraries J                    forward, please see the DTM CONVERT and the CMS CONVERT                    commands.  D           __________________________________________________________1           13.9  Where can I get Perl for OpenVMS?t  >                    OpenVMS support is included in the standardG                    distribution of Perl, the popular scripting language C                    created by Larry Wall. In addition to nearly alliF                    of the functionality available under Unix, OpenVMS-J                    specific Perl modules provide interfaces to many nativeE                    features, as well as access to Oracle, Ingres, andtJ                    Sybase databases via the Perl DBI available on OpenVMS.  J                                                                      13-23               -                    Finding and Using Software         D                    A website useful for getting started with Perl onF                    OpenVMS-where you will find such things as downloadC                    links, instructions, auxiliary tools, and sample +                    scripts-is available at:d  2                    o  http://www.sidhe.org/vmsperl  C                    If you have a C compiler, the best way to obtain H                    Perl is to download and build it yourself. The latestC                    production quality source kit is available from:v  @                    o  http://www.perl.com/CPAN/src/stable.tar.gz  G                    You will need GUNZIP and VMSTAR (both available from C                    the OpenVMS Freeware CD, or from other sites) toaF                    unpack the archive; once you've done that, read the7                    instructions in the README.vms file.l  >                    Binary distributions for most Alpha and VAXI                    environments are available on the OpenVMS Freeware CD-tJ                    ROM and from various websites, including the following:  @                    o  http://www.sidhe.org/vmsperl/prebuilt.html  <                    o  http://www.hp.com/go/openvms/freeware/  G                    During active Perl development cycles, test kits areY,                    sometimes found at: from:  *                    o  ftp://ftp.sidhe.org/  D                    Watch the mailing list (see below) for details on)                    experimental releases.c  C                    Charles Lane maintains pages on how to write CGIkF                    scripts in Perl for the OSU HTTP server, as well asJ                    more general tips, tricks, and patches for building and+                    running Perl on OpenVMS:i  :                    o  http://www.crinoid.com/crinoid.htmlx  I                    There are OpenVMS-specific Perl modules that implement E                    interfaces to a subset of the VMS System Services. J                    With these modules, you can get (and often set) device,I                    job, queue, user, system, and performance information.lI                    The lock manager, RMS indexed files, screen managementeI                    utilities, and Intracluster Communication Services arel                      13-24 m  s          -                    Finding and Using Software         I                    also accessible via Perl. The relevant modules are all/"                    available from:  D                    o  http://www.perl.com/CPAN/modules/by-module/VMS  C                    To subscribe to the OpenVMS Perl mailing list (aMA                    discussion forum for both user support and new B                    development), send an email message to vmsperl-%                    subscribe@perl.org   @                    The mailing list archives may be searched at:  F                    o  http://www.xray.mpe.mpg.de/mailing-lists/vmsperl  D           __________________________________________________________A           13.10  Obtaining the DECmigrate (AEST or VEST, and TIE)e                  translator?  I                    The DECmigrate image translation family provides toolstG                    that translate OpenVMS VAX images for use on OpenVMSnJ                    Alpha, and OpenVMS Alpha images for use on OpenVMS I64,,                    Details are available at:  Q                    o  http://h71000.www7.hp.com/openvms/products/omsva/omsva.htmls  E                    VEST is the name sometimes given to the DECmigratefD                    translation tool for VAX images, AEST is the nameF                    given to the Alpha translation tools, and TIE namesF                    the DECmigrate run-time environment within OpenVMS.G                    (If you've ever noticed images with filenames ending J                    with _TV and wondered what this meant, these images areJ                    part of TIE.) And yes, you can use AEST to re-translateJ                    images that were translated using VEST; you can perform7                    a second translation of a VAX image.r  D                    Please see Section 13.12 for related information.F                    Please see the website for the most current detailsG                    on availability and plans and status of translationsr-                    for OpenVMS I64 platforms.           J                                                                      13-25 L  r          -                    Finding and Using Software       D           __________________________________________________________F           13.11  Where can I get Zip, Unzip, self-extracting zip, etc?  D                    Many packages are provided in ZIP, GZIP, or BZIP2G                    format, which requires you to acquire the associatedtI                    unzip tool to unpack it. You can get ZIP and UNZIP and F                    related and similar tools from the following areas:  J                    o  http://www.hp.com/go/openvms/freeware/ . Look in the?                       [000TOOLS...] and [*ZIP*...] directories./  H                    o  ftp://ftp.process.com/vms-freeware/unzip.alpha_exe  F                    o  ftp://ftp.process.com/vms-freeware/unzip.vax_exe  C                    o  http://zinser.no-ip.info/www/vms/sw/zip.htmlxp  4                    o  http://www.djesys.com/zip.html  6                    o  http://www.djesys.com/unzip.html  I                    o  The master Info-Zip web site is at http://www.info- I                       zip.org/ . OpenVMS ports of current versions of zip I                       and unzip are typically available at this web site, +                       as is a mailing list.o  A                              Freeware V4.0 [000TOOLS...]*ZIP*.EXES  ?                       The Freeware V4.0 [000TOOLS...] pre-builtnB                       versions of ZIP will erroneously return BILFC                       errors on OpenVMS V7.2 and later. This is notoC                       the only error lurking within these pre-built C                       versions, just the most obvious. Accordingly, E                       please use one of the far more current versionsOD                       that are now readily available, whether on theG                       most recent Freeware distribution, or from one ofi-                       the sites listed above.   2                       Do not use the Freeware V4.04                       [000TOOLS...]*ZIP*.EXE images.  B                    Directions for creating and using the sfx self-J                    extracting zip file compression mechanism are available9                    in the unzip kit that is available at:   :                    o  Look in a recent unzip* directory at<                       http://www.hp.com/go/openvms/freeware/  J                    o  With the UNZIP542 directory from Freeware V5.0, look0                       for the file UNZIPSFX.TXT.                      13-26 -             -                    Finding and Using Softwaref        H                    If you want to build the zip images for yourself (eg:F                    for an older OpenVMS version), pull over the entireE                    contents of a recent unzip and unzip directory, ordE                    Info-Zip directory, or visit one of the web sites.dH                    With most OpenVMS ports of the tools, find and invokeD                    LINK.COM. No compilers are needed, as objects are4                    provided with most distributions.  G                    HP OpenVMS Engineering uses a tool known as FTSV foraF                    creating self-extracting compressed files using theF                    OpenVMS DCX compression tools, as seen with variousD                    OpenVMS ECO (patch) kits. (sfx typically providesG                    better compression than does DCX.) FTSV and FTSO aremJ                    available on Freeware V7.0, for OpenVMS VAX and OpenVMSI                    Alpha. Due to changes in the image headers, no version B                    of FTSV is presently available for OpenVMS I64.  D           __________________________________________________________6           13.12  Are VAX Hardware Emulators Available?  G                    Software-based emulators of the VAX architecture and I                    for specific VAX hardware platforms are available from #                    various sources:w  G                    o  Software Resources International (SRI) CHARON-VAXm0                       http://www.softresint.com/  &                    o  Tim Stark's TS10;                       http://sourceforge.net/projects/ts10/i  0                    o  Bob Supnik's Trailing Edge4                       http://simh.trailing-edge.com/  E                    VAX emulators that operate on PC systems and/or onaG                    OpenVMS Alpha systems are available. For informationrD                    on an alternative to using a VAX emulator- on theH                    available DECmigrate VAX executable image translator-,                    please see Section 13.10.            J                                                                      13-27                         J                    _______________________________________________________  '           14       Hardware Information       D           __________________________________________________________F           14.1  What are the OpenVMS differences among VAX, Alpha, and                 IA-64?  F                    In terms of software, very few. As of OpenVMS V6.1,G                    the OpenVMS VAX and OpenVMS Alpha platforms achieved I                    "feature parity". Subsequent work has seen significantiH                    enhancements and new features added on OpenVMS Alpha.I                    OpenVMS I64 started with "feature parity" with OpenVMSVC                    Alpha at the V8.2 release, and OpenVMS Alpha and J                    OpenVMS I64 are based on and built from the same sourceD                    pool. (There do exist low-level platform-specificE                    differences, and platform-specific code is presenttG                    within the shared source code pool, obviously.) Most-?                    applications can just be recompiled and run.p  3                    Some differences to be aware of:   C                    o  The default double-precision floating type on E                       OpenVMS Alpha is VAX G_float, whereas on VAX it H                       is usually D_float. D_float is available on Alpha,E                       but D_float values are converted to G_float for J                       computations and then converted back to D_float whenF                       stored. Because the G_float type has three fewerG                       fraction bits than D_float, some applications may F                       get different results. IEEE float types are also1                       available on OpenVMS Alpha.   J                    o  The preferred floating point format on the Alpha and9                       on the IA-64 architectures is IEEE.   D                    o  Data alignment is extremely important for bestF                       performance on OpenVMS Alpha and on OpenVMS I64.G                       This means that data items should be allocated at I                       addresses which are exact multiples of their sizes. I                       Quadword alignment will offer the best performance, G                       especially for character values and those smaller B                       than 32 bits. Compilers will naturally align  J                                                                       14-1 e             '                    Hardware Informationi        F                       variables where they can and will issue warnings:                       if they detect unaligned data items.  F                    o  HP C is the only C compiler HP offers on OpenVMSJ                       Alpha and on OpenVMS I64, and is a direct descendantE                       of Compaq C and DEC C on OpenVMS Alpha. HP C is F                       highly compatible with DEC C on OpenVMS VAX, butD                       does differ somewhat in its syntax and supportF                       when compared with the older VAX C compiler mostH                       OpenVMS VAX programmers are traditionally familiarF                       with. Read up on the /EXTERN_MODEL and /STANDARDG                       qualifiers to avoid the most common problems, and H                       see the documentation in the DEC C for OpenVMS VAXG                       manuals around migrating from VAX C to DEC C. (In I                       addition to HP C, there have been open-source ports ;                       such as Gnu C available for OpenVMS.)   A                    o  The page size on Alpha and IA-64 systems is E                       variable, but is at least 8 kilobytes. This can D                       have some effect on applications which use theI                       $CRMPSC system service as well as on the display of H                       available memory pages. The page size is availableE                       from $GETSYI using the SYI$_PAGE_SIZE itemcode.n  C                    There are also a number of manuals which discuss J                    migration to OpenVMS Alpha and to OpenVMS I64 availableA                    in the OpenVMS documentation, both in the mainrI                    documentation and (depending on the age of the manuals,C                    involved) in the archived documentation section.   B                    As mentioned earlier, more recent OpenVMS AlphaC                    and OpenVMS I64 releases have added features and I                    support that are not available on OpenVMS VAX. Salient 3                    additions include the following:   H                    o  64-bit addressing in OpenVMS Alpha V7.0 and later,)                       and on OpenVMS I64.U  J                    o  Multi-host SCSI support (SCSI TCQ) in V6.2 and later  6                    o  PCI support (platform-dependent)  J                    o  OpenVMS Galaxy (vPars) support in OpenVMS Alpha V7.2                       and later                       14-2  n  w          '                    Hardware InformationT        >                    Please see Section 14.4.5 for Intel Itanium                    terminology.e  D           __________________________________________________________C           14.2  Seeking performance information for Alpha (and VAX)i                 systems?  A                    HP makes a wide range of performance documents E                    available through its FTP and WWW Internet servers %                    (see Section 3.2).)  H                    The following contain information on Integrity, AlphaE                    and VAX products, with the VAX information largely.E                    accessable via archive-related links at the Alpha-r-                    related product web pages:   2                    o  http://www.hp.com/go/server/  F                    o  http://www.compaq.com/alphaserver/vax/index.html  H                    The following sites are reachable via the AlphaServerH                    information pages, and contain information on various2                    retired VAX and Alpha products:  J                    o  http://www.compaq.com/alphaserver/archive/index.html  I                    o  http://www.compaq.com/alphaserver/performance/perf_u                       tps.html  $                    Also see CPU2000:  6                    o  http://www.spec.org/osg/cpu2000/  J                    o  http://www.spec.org/osg/cpu2000/results/cpu2000.html  D           __________________________________________________________=           14.3  Console Commands, Serial Lines, and Controls?   E                    This section contains information on VAX and AlphavE                    consoles, and details related to console commands,e<                    serial lines, and configuration settings.      J                                                                       14-3 c  /          '                    Hardware Informatione      '           _____________________________.G           14.3.1  What commands are available in the Alpha SRM console?h  H                    In addition to the normal BOOT commands and such (seeD                    Section 14.3.5.2 for some details) and the normalE                    contents of the console HELP text, operations suchhI                    as I/O redirection and floppy disk access are possibleu-                    at the SRM console prompt:.  A                    1  Format a FAT floppy, and insert it into the 0                       AlphaStation floppy drive.  I                    2  Perform the following at AlphaStation SRM Console :   -                          >>> show * > env.dat 1                          >>> show conf > conf.datc;                          >>> cat env.dat > fat:env.dat/dva0 =                          >>> cat conf.dat > fat:conf.dat/dva0N  E                    3  You may use the SRM "ls" command to display the(-                       contents of the floppy.e  0                          >>> ls fat:env.dat/dva01                          >>> ls fat:conf.dat/dva0   C                    4  You can now transfer the FAT-format floppy to %                       another system.e  '           _____________________________ 6           14.3.2  What does SRM mean? What is PALcode?  H                    The abbreviation SRM is derived from the Alpha SystemC                    Reference Manual, the specification of the Alpha <                    architecture and the associated firmware.  D                    PALcode is a name assigned to a particular set ofB                    functions provided by the SRM firmware. PALcodeE                    is used to provide low-level functions required by I                    higher-level operating system or application software, I                    functions which may not be directly available in AlphatC                    hardware. PALcode is implemented using available D                    Alpha instructions and using the Alpha processor,E                    though PALcode operates in a mode which simplifieslC                    programming. PALcode is also permitted access tohE                    processor-specific and otherwise internal featuresPG                    of a particular Alpha microprocessor implementation; H                    microprocessor-specific features which are not easilyF                    accessable to operating system or application code.                      14-4                '                    Hardware Informationc      '           _____________________________-J           14.3.3  Alpha COM ports and VAX console serial line information?  E                    This section contains information on the Alpha COM H                    communication ports, and related settings, as well asJ                    on the VAX console bulkhead and VAX console serial line                    connection.  '           _____________________________pE           14.3.3.1  Which terminal device name is assigned to the COM.                     ports?  D                    COM2 is normally TTA0:. COM1 is normally TTB0: ifG                    the Alpha workstation is booted with the SRM console H                    environment variable set to graphics, and is OPA0: if0                    the console is set to serial.  I                    On the DEC 2000 series (sometimes incorrectly known bySJ                    the name of the system as sold for Microsoft Windows NTG                    Alpha; as the DECpc 150 AXP series) on older OpenVMSrG                    Alpha releases, COM1 through COM4 are known as OPA0:_H                    through OPA3:. On all current OpenVMS releases, theseG                    ports are serviced by the terminal driver and not by /                    the console OPDRIVER driver.,  J                    Often the easiest way to determine the OpenVMS terminalF                    name assigned to the port is to connect a terminal,G                    log in interactively, and look at the output of SHOWnG                    TERMINAL. (Device names can vary by OpenVMS version,eE                    as well as by the SRM console environment variabler                    selection.)  G                    For serial console hardware and related information, G                    and for pin-outs and related information, please see 2                    Section 14.3 and Section 14.26.  '           _____________________________mJ           14.3.3.2  Which serial port is the console on the MicroVAX 3100?  G                    Just to keep life interesting, the MicroVAX 3100 haslD                    some "interesting" console ports behaviours basedF                    on the setting of the BREAK enable switch. When theD                    console is not enabled to respond to BREAK, MMJ-1G                    is the console port. MMJ-3 will (confusingly) outputhF                    the results of the selftest in parallel with MMJ-1.I                    When the console is enabled to respond to BREAK, MMJ-3   J                                                                       14-5 u  g          '                    Hardware Informatione        I                    becomes the console port, and MMJ-1 will (confusingly)tI                    output the results of selftest in parallel with MMJ-3.a  '           _____________________________ J           14.3.3.3  How can I set up an alternate console on a VAXstation?  H                    Most VAXstation series systems and a few Alpha seriesI                    systems have a switch - most often labeled S3, largelyeH                    for historical reasons-that enables one of the serialE                    lines as the system console device; as OPA0:. ThismJ                    disables console output to the graphics display. (For a@                    related behaviour, please see Section 11.10.)  H                    All VAXstation 3100 series systems provide a S3 slideG                    switch, though the oldest may be missing the cut-out D                    through the enclosure that provides access to theJ                    switch. The slide switch is located near the diagnosticH                    LED display. (The slide switch is accessable with the"                    cover removed.)  G                    Various members of the DEC 3000 series Alpha systemsgJ                    also have a similarly-labled S3 switch for selection of)                    the alternate console.   I                    The particular port that becomes the console can vary.pG                    The printer MMJ connection is used on all VAXstationeD                    3100 series. On VAXstation II, the console DB9 isI                    used, rather than the graphics display. On most (all?)eI                    AlphaStation series systems, typically the COM1 serialc,                    port becomes the console.  >                    Also see Section 14.3.6, Section 11.10, andH                    Section 14.17. Beware the two different DB9 pin-outs;9                    see Section 14.27 for related details.   J                    For information on registering software license productG                    authorization keys (PAKs), please see Section 5.6.2.e  '           _____________________________JD           14.3.3.4  Please explain the back panel of the MicroVAX II  J                    The MicroVAX-series console bulkhead interface was usedF                    with the KA630, as well as with the KA650 and KA655                    processors.                      14-6s t  a          '                    Hardware Information         F                    There are three controls on the console bulkhead of!                    these systems:V  <                      Triangle-in-circle-paddle: halt enable.@                        dot-in-circle: halt (<break>) is enabled,@                                       and auto-boot is disabled.E                        dot-not-in-circle: halt (<break>) is disabled, ?                                       and auto-boot is enabled.   H                      Three-position-rotary: power-up bootstrap behaviour/                        arrow: normal operation.r3                        face: language inquiry mode.t<                        t-in-circle: infinite self-test loop.  G                      Eight-position-rotary: console baud rate selectionrG                        select the required baud rate; read at power-up.A  B                    There are several different bulkheads involved,C                    including one for the BA23 and BA123 enclosures, F                    and one for the S-box (BA2xx) series enclosure. TheI                    console bulkheads typically used either the MMJ serial G                    line connection, or the MicroVAX DB9 (not the PC DB9 D                    pin-out), please see the descriptions of these inE                    section Section 14.26. For available adapters, see !                    Section 14.27.A  F                    Also present on the console bulkhead is a self-testJ                    indicator: a single-digit LED display. This matches theJ                    final part of the countdown displayed on the console orI                    workstation, and can be used by a service organization F                    to determine the nature of a processor problem. TheD                    particular countdown sequence varies by processorC                    type, consult the hardware or owner's manual foraG                    the processor, or contact the local hardware servicemF                    organization for information the self-test sequenceJ                    for a particular processor module. Note that self-testsI                    2, 1 and 0 are associated with the transfer of control F                    from the console program to the (booting) operating                    system.          J                                                                       14-7 e  a          '                    Hardware Information       '           _____________________________ ?           14.3.4  What are Alpha console environment variables?r  H                    Alpha systems have a variety of variables with valuesJ                    set up within the SRM system console. These environmentD                    variables control the particular behaviour of theJ                    console program and the system hardware, the particularG                    console interface presented to the operating system, B                    various default values for the operating systemE                    bootstrap, and related control mechanisms-in other F                    words, "the environment variables provide an easilyD                    extensible mechanism for managing complex console                    state."  H                    The specific environment variables differ by platformJ                    and by firmware version-the baseline set is established-                    by the Alpha Architecture:t  J                    AUTO_ACTION ("BOOT", "HALT", "RESTART", any other valueK                    assumed to be HALT),  BOOT_DEV, BOOTDEF_DEV, BOOTED_DEV, H                    BOOT_FILE, BOOTED_FILE, BOOT_OSFLAGS, BOOTED_OSFLAGS,J                    BOOT_RESET ("ON", "OFF"), DUMP_DEV, ENABLE_AUDIT ("ON",@                    "OFF"), LICENSE, CHAR_SET, LANGUAGE, TTY_DEV.  B                    OpenVMS Galaxy (vPars) firmware can add consoleD                    environment variables beginning with such strings@                    as LP_* and HP_*, and each particular consoleI                    implementation can (and often does) have various sorts J                    of platform-specific extensions beyond these variables.H                    These variables allow both vPars (virtual partitions)I                    and lPars and lPars (logical partition) support; vPars E                    is a generic name for soft partitioning constructsoH                    such as OpenVMS Galaxy, while lPars is a generic name;                    applied to hard partitioning constructs.g  H                    The contents of a core set of SRM console environmentH                    variables are accessible from OpenVMS Alpha using theF                    f$getenv lexical and the sys$getenv system service.F                    (These calls are first documented in V7.2, but haveD                    been present in OpenVMS Alpha for many releases.)G                    Access to arbitary SRM console environment variablesrI                    is rather more involved, and not directly available tooI                    application software operating outside of kernel-mode.n                        14-8                '                    Hardware Informatione      '           _____________________________V8           14.3.5  What are the boot control flag values?  F                    Integrity, VAX and Alpha primary bootstraps supportD                    flag values; a mechanism which permits the systemF                    manager to perform specific customizations or site-F                    specific debugging of the OpenVMS system bootstrap.B                    While very similar, there are differences among@                    the boot flag implementations for the various!                    architectures.   '           _____________________________i:           14.3.5.1  What are the I64 IPB boot flag values?  H                    The OpenVMS I64 primary bootstrap flags are processedD                    within the IA-64 primary bootstrap image IPB.EXE;A                    within the SYS$EFI.SYS structures. The primary E                    bootstrap boot flags are largely parallel to thoseSE                    of OpenVMS Alpha (see Section 14.3.5.2, though thehI                    console and the console mechanisms used to specify theMI                    boot command, the boot flags, and boot command optionst&                    do differ markedly.  H                    You can specify the boot flags via an EFI environmentJ                    variable VMS_FLAGS , or via the boot alias boot optionsF                    mechanism, or by appending the requested boot flags<                    onto the specification of VMS_LOADER.EFI.  I                    To set the bootstrap flags environment variable at thel)                    EFI shell prompt, use:   -                    Shell> SET VMS_FLAGS "0,1"f  B                    When you register an EFI boot alias (please seeE                    Section 14.4.5 for Intel Itanium terminology), you G                    will be asked if you want to enter boot options, and G                    what type. To add boot flags to a boot alias, select J                    Unicode as the boot options type, and enter an SRM-likeG                    options string, such as the conversational bootstrap 5                    selected by the following example:d                      -flages 0,1  G                    For related information on managing EFI boot aliases @                    from OpenVMS I64, please see Section 14.3.10.  J                                                                       14-9 b             '                    Hardware Information         G                    When using VMS_LOADER.EFI to request boot flags, you B                    will want to specify the invocation as follows:  5                    fsn:\efi\vms\vms_loader -flags 0,1   F                    The above shows a conversational bootstrap request.  ?                    Typical boot flags are listed in Table 14-1.   J           ________________________________________________________________8           Table 14-1  I64 Conversational Bootstrap Flags  J                    _______________________________________________________J                    Bit_______Example_Mnemonic__________Description________  E                    0         0,1     CONV              Conversational @                                                        bootstrap  C                    1         0,2     DEBUG             Load SYSTEM_.I                                                        DEBUG.EXE (XDELTA)-  F                    2         0,4     INIBPT            Stop at initialI                                                        system breakpoints   E                    16        0,10000 DBG_INIT          Enable verbose I                                                        bootstrap messages   H                    17        0,20000 USER_MSGS         Enable additionalI                                                        bootstrap messageso  D                    17        0,200000?                 Request for aE                                                        bootstrap fromlJ           _____________________________________________USB_keydisk________  I                    For a conversational bootstrap of the OpenVMS I64 root G                    SYS4 associated with the fs2: EFI file system device B                    with full bootstrap messaging enabled, specify:  9                    fs2:\efi\vms\vms_loader -flags 4,30001   '           _____________________________o<           14.3.5.2  What are the Alpha APB boot flag values?  J                    The flags listed in Table 14-2 are passed (via registerC                    R5) to the OpenVMS Alpha primary bootstrap imageeH                    APB.EXE. These flags control the particular behaviour$                    of the bootstrap.  &                    BOOT -FL root,flags                      14-10    m          '                    Hardware Information:        J           ________________________________________________________________:           Table 14-2  Alpha Conversational Bootstrap Flags  J                    _______________________________________________________J                    Bit_____Mnemonic__________Description__________________  E                    0       CONV              Conversational bootstrap   B                    1       DEBUG             Load SYSTEM_DEBUG.EXE5                                              (XDELTA)V  C                    2       INIBPT            Stop at initial system E                                              breakpoints if bit 1 set 8                                              (EXEC_INIT)  H                    3       DIAG              Diagnostic bootstrap (loads:                                              diagboot.exe)  J                    4       BOOBPT            Stop at bootstrap breakpoints>                                              (APB and Sysboot)  I                    5       NOHEADER          Secondary bootstrap does notaA                                              have an image headerf  @                    6       NOTEST            Inhibit memory test  A                    7       SOLICIT           Prompt for secondaryn;                                              bootstrap file   D                    8       HALT              Halt before transfer to@                                              secondary bootstrap  A                    9       SHADOW            Boot from shadow set   ?                    10      ISL               LAD/LAST bootstrap   G                    11      PALCHECK          Disable PAL rev check halt3  E                    12      DEBUG_BOOT        Transfer to intermediatet>                                              primary bootstrap  ?                    13      CRDFAIL           Mark CRD pages bad   H                    14      ALIGN_FAULTS      Report unaligned data traps9                                              in bootstrapa  D                    15      REM_DEBUG         Allow remote high-level>                                              language debugger  I                    16      DBG_INIT          Enable verbose boot messages 9                                              in EXEC_INITt  J                    17      USER_MSGS         Enable subset of verbose bootE                                              messages (user messages)v  F                    18      RSM               Boot is controlled by RSM  J                                                                      14-11 y             '                    Hardware Information       J           ________________________________________________________________B           Table 14-2 (Cont.)  Alpha Conversational Bootstrap Flags  J                    _______________________________________________________J                    Bit_____Mnemonic__________Description__________________  J           _________19______FOREIGN___________Boot_involves_a_foreign_disk_  G                    If you want to set the boot flags "permanently", use 4                    the SET BOOT_FLAGS command, e.g.:  +                    >>> SET BOOT_OSFLAGS 0,1_  '           ______________________________:           14.3.5.3  What are the VAX VMB boot flag values?  D                    The flags described in Table 14-3 are passed (viaJ                    register R5) to the OpenVMS VAX primary bootstrap imageH                    VMB.EXE. These flags control the particular behaviour$                    of the bootstrap.  J           ________________________________________________________________8           Table 14-3  VAX Conversational Bootstrap Flags  J                    _______________________________________________________J                    Bit_____Mnemonic__________Description__________________  D                    0       CONV              Conversational boot. AtI                                              various points in the system J                                              boot procedure, the bootstrapD                                              code solicits parameterE                                              and other input from thesF                                              console terminal. If DIAGH                                              is set, then the diagnosticH                                              supervisor should enter itsJ                                              menu mode and prompt user forA                                              the devices to test.   H                    1       DEBUG             Debug. If this flag is set,F                                              OpenVMS VAX maps the codeI                                              for the XDELTA debugger into J                                              the system page tables of the<                                              running system.                        14-12 b  o          '                    Hardware Information       J           ________________________________________________________________@           Table 14-3 (Cont.)  VAX Conversational Bootstrap Flags  J                    _______________________________________________________J                    Bit_____Mnemonic__________Description__________________  J                    2       INIBPT            Initial breakpoint. If RPB$V_F                                              DEBUG is set, OpenVMS VAXG                                              executes a BPT instruction G                                              immediately after enabling 5                                              mapping.a  I                    3       BBLOCK            Secondary boot from the bootmG                                              block. Secondary bootstrap H                                              is a single 512-byte block,J                                              whose LBN is specified in R4.  G                    4       DIAG              Diagnostic boot. SecondarynH                                              bootstrap is the DiagnosticH                                              Supervisor image; the imageD                                              [SYSMAINT]DIAGBOOT.EXE.  H                    5       BOOBPT            Bootstrap breakpoint. StopsF                                              the primary and secondaryF                                              bootstraps with an XDELTAI                                              breakpoint instruction prior @                                              to the memory test.  D                    6       HEADER            Image header. Takes theD                                              transfer address of theF                                              secondary bootstrap imageC                                              from that file's image H                                              header. If the RPB$V_HEADERI                                              bit is not set, the image is E                                              assumed to have no imagetC                                              header, and control issI                                              transfered to the first bytetH                                              of the secondary boot file.  H                    7       NOTEST            Memory test inhibit. Sets aG                                              bit in the PFN bit map for I                                              each page of memory present. F                                              Does not test the memory.  G                    8       SOLICT            File name. VMB prompts for D                                              the name of a secondary<                                              bootstrap file.  J                                                                      14-13 _  _          '                    Hardware Information       J           ________________________________________________________________@           Table 14-3 (Cont.)  VAX Conversational Bootstrap Flags  J                    _______________________________________________________J                    Bit_____Mnemonic__________Description__________________  B                    9       HALT              Halt before transfer.H                                              Executes a HALT instructionH                                              before transferring controlH                                              to the secondary bootstrap.  A                    10      NOPFND            No PFN deletion (not E                                              implemented; intended towH                                              tell VMB not to read a fileF                                              from the boot device thatG                                              identifies bad or reservedoF                                              memory pages, so that VMBI                                              does not mark these pages as F                                              valid in the PFN bitmap).  B                    11      MPM               Specifies that multi-F                                              port memory is to be usedF                                              for the total EXEC memoryI                                              requirement. No local memoryrC                                              is to be used. This is G                                              for tightly-coupled multi-lJ                                              processing. If the RPB$V_DIAGJ                                              bit is also enabled, then theI                                              Diagnostic Supervisor entersn?                                              its AUTOTEST mode.r  F                    12      USEMPM            Specifies that multi-portE                                              memory should be used insI                                              addition to local memory, asoH                                              though both were one single;                                              pool of pages.   B                    13      MEMTEST           Specifies that a moreH                                              extensive algorithm be usedI                                              when testing main memory for I                                              hardware uncorrectable (RDS)f4                                              errors.                          14-14 P  f          '                    Hardware InformationO      J           ________________________________________________________________@           Table 14-3 (Cont.)  VAX Conversational Bootstrap Flags  J                    _______________________________________________________J                    Bit_____Mnemonic__________Description__________________  F                    14      FINDMEM           Requests the use of MA780I                                              multiport memory if the mainMI                                              MS780 memory is insufficientoC                                              for booting. This is aDC                                              remnant of the supportfF                                              for the VAX-11/782 seriesF                                              system and its AsymmetricC                                              Multiprocessing (ASMP)dE                                              environment. Support foriH                                              the VAX-11/782 and for ASMPH                                              was withdrawn with the V5.0H                                              release; with the advent ofF                                              Symmetric MultiprocessingJ           ___________________________________(SMP)_support._______________  C                    The exact syntax is console-specific, recent VAXV6                    consoles tend to use the following:  &                      >>> BOOT/R5:flags  '           _____________________________aB           14.3.6  How do I boot an AlphaStation without monitor or                   keyboard?   G                    The AlphaStation series will boot without a keyboard E                    attached. To use a serial terminal as the console, C                    issue the SRM console command SET CONSOLE SERIAL F                    followed by the console INIT command. Once this SRMD                    command sequence has been invoked and the CONSOLEJ                    environment variable is set to SERIAL, the Alpha systemE                    will use the serial terminal. (Set the environmenteE                    variable to GRAPHICS to select the console displayn4                    output via the graphics display.)  F                    The DEC 3000 series has a jumper on the motherboardE                    for this purpose. Various older Alpha workstationslI                    generally will not (automatically) bootstrap without a_H                    keyboard connected, due to the self-test failure thatA                    arises when the (missing) keyboard test fails.   J                                                                      14-15    a          '                    Hardware Information         I                    The usual settings for the console serial terminal (orfG                    PC terminal emulator acting as a serial console are:h  O                    9600 baud, 8 bits, no parity, one stop bit (9600 baud, 8N1).   D                    AlphaServer 4100 and derivative series platforms,G                    and AlphaServer GS80, GS160, and GS320 series systempH                    consoles are capable of 57600 baud. See the COM2_BAUDI                    console environment variable, and ensure that you havei7                    current SRM firmware version loaded.   D                    The AlphaStation and AlphaServer series use a PC-H                    compatible DB9 serial connector for the COM1 and COM2H                    serial lines (and for the OPA0: console line, if thatH                    was configured via SRM), please see Section 14.26 for'                    details and pin-out.   J                    For information on registering software license productG                    authorization keys (PAKs), please see Section 5.6.2.4  @                    For a related behaviour of DECwindows, please<                    see Section 11.10. For information on theF                    VAXstation alternate console mechanisms, please see$                    Section 14.3.3.3.  '           _____________________________ =           14.3.7  Downloading and using SRM console Firmware?/  E                    This section discusses downloading and using Alpha_>                    console firmware, sometimes called PALcode.  '           _____________________________ F           14.3.7.1  Where can I get updated console firmware for Alpha                     systems?  F                    Firmware updates for HP Alpha systems are available                    from:  Q                    o  ftp://ftp.digital.com/pub/Digital/Alpha/firmware/index.html   G                    o  ftp://ftp.digital.com/pub/Digital/Alpha/firmware/m  R                    o  ftp://ftp.digital.com/pub/Digital/Alpha/firmware/readme.html                      14-16 e  r          '                    Hardware Information         G                    The latest and greatest firmware-if updated firmwareoJ                    has been released after the most recent firmware CD was-                    distributed-is located at:a  O                    widftp://ftp.digital.com/pub/Digital/Alpha/firmware/interim/a  F                    For information on creating Alpha bootable floppiesI                    containing the firmware, and for related tools, pleased+                    see the following areas:   W                    widftp://ftp.digital.com/pub/DEC/Alpha/firmware/utilities/mkboot.txt_  Z                    widftp://ftp.digital.com/pub/DEC/Alpha/firmware/utilities/mkbootarc.txt  Y                    widftp://ftp.digital.com/pub/DEC/Alpha/firmware/utilities/mkntboot.txte  F                    The SROM firmware loader expects an ODS-2 formattedI                    floppy, see mkboot. As for which image to use, the ROMeG                    image uses a header and the file extension .ROM, andME                    the SROM bootable floppy cannot use the .ROM file.c  G                    To check the firmware loaded on recent OpenVMS Alphal,                    systems, use the command:  A                    $ write sys$output f$getsyi("console_version")hA                    $ write sys$output f$getsyi("palcode_version") #                    SDA> CLUE CONFIGh  C                    Also see Section 14.3.7.2. For information on HPhE                    Integrity EFI firmware upgrades and for a sequence H                    useful in generating CD-R or CD-RW media containing aC                    firmware disk image, please see Section 14.3.11.l  '           _____________________________sF           14.3.7.2  How do I reload SRM firmware on a half-flash Alpha                     system?i  E                    Some of the AlphaStation series systems are "half- I                    flash" boxes, meaning only one set of firmware (SRM or G                    AlphaBIOS) can be loaded in flash at a time. Getting?F                    back to the SRM firmware when AlphaBIOS (or ARC) is8                    loaded can be a little interesting...  I                    That said, this usually involves shuffling some files,nF                    and then getting into the AlphaBIOS firmware updateH                    sequence, and then entering "update srm" at the apu->                    prompt.  J                                                                      14-17    0          '                    Hardware Informationo        J                    To shuffle the files, copy the target SRM firmware fileG                    (as200_v7_0.exe is current) to a blank, initialized, G                    FAT-format floppy under the filename A:\FWUPDATE.EXE   F                    From the AlphaBIOS Setup screen, select the UpgradeJ                    AlphaBIOS option. Once the firmware update utility gets                     going, enter:  (                         Apu-> update srm  C                               Answer "y" to the "Are you ready...?"   "                         Apu-> quit  H                    You've reloaded the flash. Now power-cycle the box to&                    finish the process.  -                    Also see Section 14.3.7.1.   '           _____________________________oA           14.3.7.3  How do I switch between AlphaBIOS/ARC and SRMl                     consoles?   G                    The specific steps required vary by system. You must C                    first ensure that the particular Alpha system is H                    supported by OpenVMS (see the SPD), that all core I/OF                    components (graphics, disk controllers, etc) in theJ                    system are supported by OpenVMS (see the SPD), and thatF                    you have an OpenVMS distribution, that you have theG                    necessary license keys (PAKs), and that you have the 1                    necessary SRM firmware loaded.   F                    A typical sequence used for switching over from theI                    AlphaBIOS graphics console to the SRM console follows:   D                    1  Press <F2> to get to the AlphaBIOS setup menu.  4                    2  Pick the "CMOS Setup..." item.  J                    3  Press <F6> to get to the "Advanced CMOS Setup" menu.  H                    4  Change the "Console Selection" to "OpenVMS Console                       (SRM)".   C                    5  Press <F10>, <F10>, then <Enter> to save your                        changes.  -                    6  Power-cycle the system.c                      14-18 n  i          '                    Hardware Informationl        >                    Most Alpha systems support loading both theH                    AlphaBIOS/ARC console and the SRM console at the sameE                    time, but systems such as the AlphaStation 255 arehG                    "half-flash" systems and do not support the presence3H                    of both the AlphaBIOS/ARC and SRM console firmware atH                    the same time. If you have a "half-flash" system, youI                    must load the SRM firmware from floppy, from a networkyE                    download, or from a firmware CD-ROM. Following the0F                    normal AlphaBIOS or ARC firmware update sequence toG                    the APU prompt, and then explictly select the targetuF                    console. In other words, power up the system to theJ                    AlphaBIOS or ARC console, use the supplementary optionsH                    to select the installation of new firmware (typicallyF                    from CD-ROM), and then rather than using a sequence6                    which updates the current firmware:  #                        Apu-> update3                          -or- '                        Apu-> update ARC #                        Apu-> verifyt!                        Apu-> quit -                        Power-cycle the systems  I                    Use the following sequence to specifically update (andhI                    load) SRM from AlphaBIOS/ARC on a "half-flash" system:.  '                        Apu-> update SRMt#                        Apu-> verifyO!                        Apu-> quit -                        Power-cycle the system   I                    Use the following sequence to specifically update (andaG                    load) the AlphaBIOS/ARC console from SRM on a "half-f!                    flash" system:   *                        >>> b -fl 0,A0 ddcu7                        BOOTFILE: firmware_boot_file.exeP  '                        Apu-> update ARC #                        Apu-> verify !                        Apu-> quitb-                        Power-cycle the system     J                                                                      14-19               '                    Hardware Information         I                    Once you have the SRM loaded, you can directly install D                    OpenVMS or Tru64 UNIX on the system. Do not allowD                    Microsoft Windows NT or other operating system(s)F                    to write a "harmless" signature to any disk used byG                    OpenVMS Alpha or OpenVMS VAX, as this will clobber a H                    key part of the disk; this will overwrite the OpenVMSH                    bootblock. (On OpenVMS Alpha and OpenVMS VAX, you canJ                    generally recover from this so-called "harmless" action3                    by using the WRITEBOOT.EXE tool.   G                    Using OpenVMS I64 and the EFI console, the bootblockgF                    structures are expected to be compatible with thoseE                    of Microsoft Windows and other Integrity operating J                    systems; please see the discussion of the SET BOOTBLOCKJ                    command and the SYS$SETBOOT.EXE image in Section 9.7.3,J                    in Section 14.3.9, and in the OpenVMS documentation for$                    related details.)  G                    If you have a "full-flash" system and want to selectlD                    the SRM console from the AlphaBIOS or ARC consoleF                    environment, select the "Switch to OpenVMS or Tru64B                    UNIX console" item from the "set up the system"F                    submenu. Then power-cycle the system. If you have aG                    "full-flash" system with the SRM console and want tot9                    select AlphaBIOS/ARC, use the command:   (                       >>> set os_type NT  .                    and power-cycle the system.  =                    For information on acquiring firmware, seenG                    Section 14.3.7.1. For information on OpenVMS licenseeA                    PAKs (for hobbyist use) see Section 2.8.1. ForpA                    information on the Multia, see Section 14.4.1.m  J                    Information on enabling and using the failsafe firmwareI                    loader for various systems-this tool is available onlynI                    on some of the various Alpha platforms-is available insJ                    the hardware documentation for the system. This tool isH                    used/needed when the firmware has been corrupted, and,                    cannot load new firmware.  A                    The full list of AlphaBIOS key sequences-these H                    sequences are needed when using an LK-series keyboardB                    with AlphaBIOS, as AlphaBIOS expects a PC-style                    keyboard:                      14-20 s  s          '                    Hardware Information         '                             F1   Ctrl/Ae'                             F2   Ctrl/Bl'                             F3   Ctrl/Ce'                             F4   Ctrl/Dt'                             F5   Ctrl/E '                             F6   Ctrl/Ft'                             F7   Ctrl/P '                             F8   Ctrl/Rn'                             F9   Ctrl/Tn'                            F10   Ctrl/U '                         Insert   Ctrl/Vv'                         Delete   Ctrl/W '                      Backspace   Ctrl/Hm'                         Escape   Ctrl/[ '                         Return   Ctrl/Mm'                       LineFeed   Ctrl/J 8                       (Plus) +   upselect (some systems):                      (Minus) -   downselect (some systems)+                            TAB   down arrow")                       SHIFT+TAB  up arrow   '           _____________________________F,           14.3.8  Console Management Options  E                    Options to collect multiple consoles into a singleEG                    server are available, with both hardware options and"G                    software packages that can provide advanced featuresl$                    and capabilities.  G                    Some of the available console management options for                     OpenVMS:,  5                    o  Heroix: http://www.robomon.com/t  C                    o  KI Products: http://www.ki.com/products/clim/l  ?                    o  Global Maintech: http://www.globalmt.com/   3                    o  TECsys: http://www.tditx.com/)  C                    o  CA: http://www.cai.com/products/commandit.htmP  D                    Computer Associates is the owner of what was onceG                    known as the VAXcluster Console System (VCS) console I                    management package, and has integrated this capability 8                    into the CA management product suite.  J                                                                      14-21 e             '                    Hardware Informationv      '           _____________________________l2           14.3.9  Why do my EFI Boot Aliases Fail?  I                    OpenVMS I64 boot aliases contain signature information D                    referencing the specific volume, meaning that theB                    entries are specific to the disk volume and not@                    the disk device. This also means that certainG                    operations, such as the SET BOOTBLOCK command or therG                    RUN SYS$SETBOOT.EXE operation that can rewrite these J                    volume signatures (signature or GUID values) can render2                    existing boot aliases unusable.  D                    If your boot aliases do not function as expected,C                    first try removing and re-adding them; this will A                    resynchronize the boot aliases with the volume.J                    contents. If you are using the SET BOOTBLOCK command orH                    the RUN SYS$SETBOOT.EXE operation to rewrite the diskI                    bootblock, you can request that the current signatures J                    (if any) be preserved, and this will typically maintainA                    the validity of your EFI console boot aliases.   '           _____________________________PC           14.3.10  Can OpenVMS access the EFI console Boot Aliases?m  I                    For access to the EFI console environment from OpenVMS G                    I64, see the BOOT_OPTIONS.COM command procedure, and J                    the EFI SET, SHOW and BCFG mechanisms. Details on theseF                    are in the System Manager's and particularly in the5                    System Manager's Utilities manual.   F                    For related information on boot aliases, please see$                    Section 14.3.5.1.  '           _____________________________ >           14.3.11  Downloading and using EFI Console Firmware?  H                    HP Integrity EFI system firmware can be downloaded inI                    the form of a bootable image master, unzipped and thenIF                    burned onto CD or DVD media (please see Section 9.7E                    for details of recording optical media directly on H                    OpenVMS), and the system can then generally be bootedD                    off the created media to perform the EFI firmware                    upgrade.                         14-22 ,  l          '                    Hardware Informations        I                    The HP Integrity Server website is accesssable via thesH                    following URL, and the available services and supportI                    information there has links to the available platform-aJ                    specific firmware images and upgrade-related materials:  5                    o  http://www.hp.com/go/integrity/   J                    To use the following sequence, you will need a writableG                    or rewritable CD drive and software, and a blank CD-DE                    R or CD-RW disk. If you use CD writer software forcD                    another platform, you will want to use the block,E                    binary, ISO or raw mode operations appropriate foraI                    the particular chosen recording package. The following C                    directions assume use of OpenVMS and native CD-R_F                    capabilities, please see Section 9.7 for associated                    details._  B                    1  First, you must acquire the Integrity serverG                       firmware from the above URL. Select the platform, D                       and navigate to the supporting information andG                       specifically to the Download Drivers and Software                        link  J                    2  Select Cross operating system (BIOS, Firmware, etc.)  F                    3  Locate the appropriate ISO-format firmware file.G                       There are several firmware file formats available D                       and there are also various off-line diagnosticB                       images, choose the ISO-format firmware file.  E                    4  Read the directions for the firmware file, then2G                       download the ISO-format firmware (zip-compressed) F                       file. A binary-mode FTP transfer should be used.  E                    5  Unzip the file into the corresponding .ISO data H                       file. Somewhat confusingly, the .ISO extension canE                       indicate either a block-oriented raw image of acI                       disk, or a disk with the ISO-9660 volume structure.sC                       In this case, the former is intended and thistG                       file contains a a block copy or disk image of thefH                       firmware disk for the platform, and may or may notH                       be an ISO-9660 volume structure. The unzip tool isF                       available on the OpenVMS Freeware and elsewhere;I                       please see Section 13.11 for details and locations.   J                                                                      14-23    o          '                    Hardware Informationt        D                    6  Use CDRECORD or other available recording toolE                       (please see Section 9.7 for related details) to_H                       burn a CD-R or CD-RW disk, specifying the ISO file;                       as the source for the burn operation._  F                    7  Shut the Integrity Server system down to the EFI$                       console level.  G                    8  Unload the recorded CD media from the CD-R drive, F                       label it, and load it into the Integrity consoleE                       drive. This assuming the disk was not generated H                       directly on an Integrity CD-R/RW-capable drive, of                       course.i  G                    9  Using the EFI shell, display the current firmware /                       version using the commands                         info fw   D                   10  Exit the EFI shell and select the boot optionsC                       maintenance menu; create a boot alias for the F                       removable media drive for the CD; for the newly-,                       created firmware disk.  E                   11  Boot it. Follow the directions displayed by thefH                       firmware loader and related documentation, heedingC                       the release notes that were reviewed earlier.   E                   12  Perform a cold restart of the Integrity server.   J                    For information on Alpha SRM console firmware upgrades,-                    please see Section 14.3.7.   D           __________________________________________________________7           14.4  What platforms will OpenVMS operate on?a  I                    For the list of boxes that are officially and formally3C                    supported by OpenVMS Engineering, please see thei>                    OpenVMS Software Product Description (SPD).  9                    o  http://h18000.www1.hp.com/info/spd/   H                       OpenVMS typically uses SPD 25.01.xx, SPD 41.87.xx,'                       and SPD 82.35.xx.                       14-24               '                    Hardware Informationt        J                    Sometimes a particular and officially unsupported AlphaH                    box or Alpha motherboard will sufficiently resemble aH                    supported box that the platform can effectively mimicE                    and can bootstrap OpenVMS. Alternatively, somebody D                    (usually one or more engineers within the OpenVMSH                    Engineering group) will have put together a bootstrapC                    kit - such as the kit for the Alpha Multia-which @                    permits OpenVMS to bootstrap on the platform.  C                    Contrary to the assumptions of some folks, there_A                    are platform-level differences even within theaE                    VAX and within the Alpha platforms- hardware-level_I                    differences that can require moderate to extensive new_G                    coding within OpenVMS. Within a platform series, andfI                    particularly within Alpha platforms (and those few VAXnJ                    systems) that support Dynamic System Recognition (DSR),1                    OpenVMS can usually bootstrap.   A                    DSR is a mechanism by which OpenVMS can gatherVG                    platform-specific information, and DSR is the reason4F                    why newer Alpha systems can be more easily and moreF                    commonly supported on older OpenVMS Alpha releases.G                    DSR is implemented with OpenVMS Alpha code, with SRM G                    console code, and with platform non-volatile memory.   E                    OpenVMS users with experience on older OpenVMS VAX_F                    releases and VAX hardware will recall that then-newF                    VAX systems either required an OpenVMS VAX upgrade,F                    or that earlier releases would mis-identified then-E                    newer VAX systems-such as the case of the VAX 7000 F                    model 800 being (mis)identified as a VAX 7000 modelE                    600 when bootstrapped on OpenVMS VAX V5.5-2. (This F                    (mis)identification was the outcome of a deliberateI                    engineering effort to permit the VAX 7000 model 800 to J                    bootstrap on V5.5-2; the system manager could configureF                    the VAX 7000 model 800 to (mis)identify itself as aH                    model 600, to permit the system to bootstrap on V5.5-F                    2.) OpenVMS VAX and VAX platforms lack DSR support.  C                    OpenVMS I64 (please see Section 14.4.5 for Intel I                    Itanium terminology) supports a platform-level feature D                    similar to the OpenVMS Alpha DSR mechanism, basedF                    on the ACPI interface and the byte-code interpreterF                    implemented within OpenVMS, within the EFI console,F                    and particularly within non-volatile memory located  J                                                                      14-25 _  _          '                    Hardware InformationB        I                    on (byte-code interpreter compliant) PCI I/O hardware._H                    ACPI tables provide the information that was formerlyI                    retrieved from DSR and from the SRM, and the byte-codenJ                    interpreter can (theoretically) permit at least limitedG                    operations with (compliant) PCI hardware, whether ortH                    not OpenVMS has a driver for the particular hardware.  B                    The byte code interpreter may or may not permitC                    operations with any particular PCI hardware, andoG                    may or may not have sufficient performance for localaH                    requirements, and PCI hardware may or may not includeF                    the necessary ROM-based drivers in the PCI hardwareB                    non-volatile storage. (The intent of this IntelE                    platform-level effort is to move the host softwareiE                    drivers out onto the specific PCI hardware, and tooE                    permit the same byte code to operate regardless ofIF                    the particular host platform.) At least the initialH                    releases of OpenVMS I64 will not have support for theH                    byte code interpreter nor for arbitrary PCI or systemH                    hardware, but will have support for ACPI-based system;                    identification and system configuration.   '           _____________________________ &           14.4.1  on the Alpha Multia?  I                    Yes, there are a set of unsupported images that permittF                    specific OpenVMS Alpha versions to bootstrap on theE                    Multia UDB system. These images and the associated E                    instructions are available at the OpenVMS FreewareD                    website:   <                    o  http://www.hp.com/go/openvms/freeware/  7           Look in the Freeware V5.0 /multia/ directory.   B                    Instructions are included IN the kits. READ THE(                    INSTRUCTIONS. PLEASE!  I                    Some of the restrictions involved when running OpenVMSoD                    on the Multia system include (but may well not be-                    limited to) the following:   H                    o  The PCMCIA support was completely removed, becauseJ                       the Intel chip on the Multia was not compatable with7                       the Cirrus chip on the Alphabook.                       14-26 C             '                    Hardware Information         F                       This means, of course, that you will not see and>                       cannot use any PCMCIA cards on a Multia.  I                       The Multia uses shared interrupts, and as a result, H                       a special ZLXp-E series graphics device driver-oneI                       that does not use interrupts-is needed. This driver -                       is provided in the kit.   2                    o  The serial lines don't work.  I                    o  If you have a Multia with a PCI slot, you can't use_<                       any PCI card that requires interrupts.  D                    o  The SRM console on this system is very old andB                       very fragile. (This SRM console was designedG                       only and strictly for diagnostic use, and was not @                       particularly tested or used with OpenVMS.)  G                    o  If things don't work for you, don't expect to seeeG                       any OpenVMS updates, nor SRM console updates, norM"                       any support.  F                    o  Do not expect to see any new versions of OpenVMSI                       on the Multia nor on any other unsupported systems. H                       If such new versions do appear and do work, please9                       consider it as a pleasant surprise.   D                    The Multia images are not included on the OpenVMSI                    Freeware V4.0 CD-ROM kit, the kit that was distributed J                    with OpenVMS V7.2. (These images became available after*                    Freeware V4.0 shipped.)  E                    Other sources of information for OpenVMS on Multiao                    include:   D                    o  http://www.djesys.com/vms/hobbyist/multia.html  F                    o  http://www.djesys.com/vms/hobbyist/mltianot.html  E                    o  http://www.djesys.com/vms/hobbyist/support.html   F                    o  http://www.netbsd.org/Ports/alpha/multiafaq.html  F                    o  http://www.brouhaha.com/~eric/computers/udb.html  J                                                                      14-27    U          '                    Hardware Information       '           _____________________________u2           14.4.2  on AlphaPC 164LX? AlphaPC 164SX?  J                    OpenVMS Alpha is not supported on the AlphaPC 164LX andH                    164SX series, though there are folks that have gottenE                    certain of the LX series to load SRM and bootstrapSI                    OpenVMS. (The Aspen Durango II variant, specifically.)e  E                    One problem has been generally reported: ATA (IDE)tG                    bootstraps will fail; SCSI storage and a SCSI CD-ROMr&                    device is required.  -                    Also see Section 14.4.2.1.   '           _____________________________ 2           14.4.2.1  on the NoName AXPpci33 system?  I                    Information on bootstrapping OpenVMS (using the MultiaaJ                    files described in Section 14.4.1) on the (unsupported):                    NoName AXPpci33 module is available at:  C                    o  http://www.jyu.fi/~kujala/vms-in-axppci33.txt   <           Tips for using the Multia files with the AXPpci33:  C                    o  You have to use the Multia kit and follow the H                       directions in ALPHA8, but do *not* load the MultiaJ                       SRM firmware into the AXPpci33. Rather, download andJ                       use the latest firmware for the AXPpci33 from the HP5                       Alpha firmware website instead.e  :                    o  64 MB memory is generally necessary.  F                    o  you cannot use any PCI cards, and if you plan onG                       networking, you need to find an ISA Ethernet cardv+                       supported by OpenVMS.   F                    o  When the AXPpci33 board bootstraps, it will dumpH                       some stuff like a crash dump, but it will continueB                       and-so far-this hasn't caused any particular                       hassles.  F                    o  The system shutdown and reboot procedures do not$                       work properly.  H                    o  The serial console is reported to not work, thoughH                       the serial ports apparently do work. The status of3                       the parallel port is unknown.                       14-28 n  p          '                    Hardware Informationb        E                    o  Rumour has it that you have one of the AXPpci33rC                       motherboards with the PS/2 mouse and keyboardoC                       connectors and a VGA card (one that will workRE                       under DECwindows) and you can run DECwindows ons!                       the system.q  '           _____________________________ )           14.4.3  on the Alpha XL series?t                      No.  J                    OpenVMS Engineering does not formally support the AlphaH                    XL series, nor will OpenVMS (informally) bootstrap on'                    the Alpha XL series.l  G                    OpenVMS can not, will not, and does not bootstrap onaH                    the Alpha XL series. The Alpha XL series was targetedI                    for use (only) with the Microsoft Windows NT operating_                    system.  J                    The Alpha XL platform does not resemble other supported                    platforms.i  '           _____________________________ H           14.4.4  OpenVMS on the Personal Workstation -a and -au series?  B                    Though OpenVMS is not supported on the PersonalJ                    Workstation -a series platforms, OpenVMS might or might1                    not bootstrap on the platform.   H                    If you wish to attempt this, you must ensure that allE                    graphics and all I/O controllers in the system are F                    supported by OpenVMS. You must also ensure that you9                    have the most current firmware loaded.C  G                    Here are some salient differences within the variousy/                    Personal Workstation series:   C                    o  The -a series was designed and was tested for G                       Windows NT use. Only. It is not supported for uset#                       with OpenVMS.s  I                    o  The -au series was designed and tested for Windows,cC                       OpenVMS, and Tru64 UNIX compatibility, and isd4                       considered a supported system.  J                                                                      14-29 y  P          '                    Hardware Information         I                    o  There are at two different and distinct variants of.J                       the family, and usually refered to by their internal-                       hardware project names.i  G                      o  The Miata MX5. The Miata MX5 variant has no USB F                         ports and no on-board SCSI. The on-board IntelI                         SIO chipset is not supported by OpenVMS, and thusfF                         OpenVMS cannot bootstrap ATAPI CD-ROM devices.  I                         That said, the Miata MX5 -a series typically cameaI                         with DEC branded Adaptec 2940UW SCSI controllers,PE                         Matrox Millennium graphics cards, no L3 cache I                         module, and an Toshiba IDE CD-Rom. Some came with E                         very high end Powerstorm graphics card if the I                         system was destined to do CAD or movie rendering.m  C                         Graphics and other I/O can and does vary by                           package.  B                         The Miata MX5 is not supported by OpenVMS.  H                      o  The Miata GL. The Miata GL variant has USB portsF                         and on-board SCSI and bootstraps using the on-E                         board Cypress IDE chipset and an ATAPI CD-ROM I                         are supported by OpenVMS. The Miata GL -a variant E                         is need not be configured with an add-on SCSI G                         controller, given both the ability to bootstrapi@                         from ATAPI CD-ROM and the on-board SCSI.  C                         Graphics and other I/O can and does vary byb                          package.  H                         Various of the Miata GL systems are supported by                          OpenVMS.  G                    For obvious reasons, most folks will prefer and willAI                    select a Miata GL system, given the choice between theaJ                    Miata MX5 and the Miata GL series. And as for your nextJ                    question, you cannot necessarily nor easily distinguishF                    the Miata MX5 from the Miata GL based solely on the                     model number.  <                    See Section 14.4.4.2 for related details.                      14-30 _  s          '                    Hardware Information       '           _____________________________nF           14.4.4.1  OpenVMS on the Whitebox Windows-Only series Alpha?  D                    Though OpenVMS is not supported on the "Whitebox"D                    series of Alpha platforms, OpenVMS might or mightD                    not bootstrap on the platform. These systems wereG                    specifically configured, targeted and supported only J                    for use with the Microsoft Windows NT operating system.  C                    On some of the "Whitebox" systems, the followingeG                    sequence of console commands can potentially be usedaG                    to convert the system over to unsupported use by andAG                    for OpenVMS Hobbyist users. (But please note that ifnE                    you wish to attempt this, you must ensure that alloE                    graphics and all I/O controllers in the system arewJ                    supported by OpenVMS, and you must ensure that you haveI                    the most current SRM firmware loaded. (For information I                    on locating and downloading the most current Alpha SRM G                    firmware, please see Section 14.3.7.1.) And you mustcI                    realize that the resulting Whitebox configuration willrG                    be entirely unsupported and may or may not be stabler                    and useful.)   "                    set os_type vmsD                    cat nvram  ! too see what is in this, if anything                    edit nvramt%                    10 set srm_boot on:                    20 e                     init   E                    If your nvram has other contents, you will need to E                    change the line numbers (10 and 20) to reflect thefJ                    contents of your configuration. To obtain documentationE                    on the commands of the console editor, enter the ?_-                    command within the editor.I  J                    The above sequence was reportedly tested on the DIGITALD                    Server 3300 series, a relative of the AlphaServerG                    800 series. The DIGITAL Server 3300 is not supported E                    by OpenVMS, though the AlphaServer 800 series is a J                    supported platform. The sequence may or may not work onJ                    other platforms, and may or may not work on the DIGITAL(                    Server 3300 platform.  )                    Also see Section 5.33.c  J                                                                      14-31 S  f          '                    Hardware Informationq      '           _____________________________ I           14.4.4.2  OpenVMS and Personal Workstation ATA (IDE) bootstrap?   J                    OpenVMS will boot and is supported on specific PersonalH                    Workstation -au series platforms, though OpenVMS willJ                    require a SCSI CD-ROM if the Intel Saturn I/O (SIO) IDEI                    chip is present in the configuration- only the Cypress F                    IDE controller chip is supported by OpenVMS for IDEI                    bootstraps. (Configurations with the Intel SIO are notyA                    generally considered to be supported systems.)   F                    If you have an -au series system, you can determineI                    which IDE chip you have using the SRM console command:S  '                      SHOW CONFIGURATIONt  J                    If you see "Cypress PCI Peripheral Controller", you canH                    bootstrap OpenVMS from IDE storage. If you see "IntelF                    SIO 82378", you will need to use and bootstrap fromH                    SCSI. (A procedure to load DQDRIVER on the Intel SIO-I                    once the system has bootstrapped from a SCSI device-islI                    expected to be included as part of the contents of thelB                    DQDRIVER directory on Freeware V5.0 and later.)  G                    Many of the -a series systems will include the Intele;                    SIO, and thus cannot bootstrap from IDE.   :                    See Section 14.4.4 for related details.  '           _____________________________ 6           14.4.5  On the Intel Itanium IA-64 platform?  =                    OpenVMS has been ported to the Intel IA-64iE                    architecture; to HP Integrity systems based on the32                    Intel Itanium Processor Family.  F                    The first release of OpenVMS I64 was V8.0, with theG                    first general or first production release of OpenVMS I                    I64 known as V8.2. Yes, there was a V8.1 release, too.   J                    Some Intel and HP terminology: Itanium Processor FamilyD                    is the name of the current implementation; of theC                    current Intel microprocessor family implementingPC                    the IA-64 architecture. IA-64 is the name of thecF                    Intel architecture implementing the VLIW (Very LongE                    Instruction Word) design known as EPIC (Explicitly 3                    Parallel Instruction Computing).                       14-32 _  t          '                    Hardware InformationR        J                    I64 is the name of a family of HP computer systems thatF                    use Intel Itanium processors and that are supportedI                    by "HP OpenVMS for Integrity Servers" (and itself more E                    commonly known as "OpenVMS I64"); by one of the HPaH                    operating systems that runs on HP Integrity hardware.  I                    The Extensible Firmware Interface (EFI) is the name ofsG                    the console environment for Itanium systems, and the"F                    Baseboard Management Console (BMC) and the optionalJ                    Management Processor (MP) are the most typical hardware6                    interfaces into the system console.  '           _____________________________u>           14.4.5.1  Where can I get Intel Itanium information?  I                    Intel Itanium Processor Family and IA-64 Architecture, A                    Hardware, Software, and related docoumentationg.                    materials are available at:  D                    o  ftp://download.intel.com/design/IA-64/manuals/  F                    o  ftp://download.intel.com/design/IA-64/Downloads/  9                    o  ftp://download.intel.com/design/IA-e6                       64/Downloads/archSysSoftware.pdf  9                    o  ftp://download.intel.com/design/IA- /                       64/Downloads/24870101.pdf   G                    Information on the classic Intel Extensible Firmware H                    Interface (EFI) (for IA-64) and of the multi-platformG                    Unified EFI (UEFI) console project documentation are 3                    available at the following URLs:                       o  Intelw0                       http://developer.intel.com                      o  UEFI)                       http://www.uefi.org   >                    Please see Section 14.4.5 for Intel Itanium                    terminology.     J                                                                      14-33 u  n          '                    Hardware Information.      D           __________________________________________________________I           14.5  What is the least expensive system that will run OpenVMS?a  F                    The cheapest systems that are or have been recentlyD                    offered by HP that will run OpenVMS Alpha are theB                    AlphaServer DS10 server, the AlphaStation XP900F                    workstation, the AlphaStation VS10 workstation, andG                    the AlphaStation XP1000 workstation. Other companiesdJ                    sell Alpha-powered systems and Alpha motherboards, someI                    of which will run (and can be purchased with) OpenVMS-eI                    see the OpenVMS Software Product Description (SPD) foreG                    details on the supported systems and configurations.eF                    There are also many used AlphaStation, AlphaServer,G                    and DEC 3000 series models available which are quite J                    suitable. For more experienced OpenVMS system managers,E                    the (unsupported) Multia can bootstrap OpenVMS-seet.                    Section 14.4.1 for details.  C                    Used Itanium-based systems that a hobbyist couldCE                    likely use to bootstrap OpenVMS I64 have been seen E                    selling on auction websites for under US$1000. New H                    Integrity rx2620 series systems (officially supportedG                    by OpenVMS I64) have been offered as part of a week- J                    long DSPP porting and training package for US$2000. SeeJ                    Section 2.8.3 for details on the DSPP program. Also seeJ                    the HP Renew used- and/or refurbished-equipment program<                    for any hardware that might be available.  B                    Free and commercial VAX software-based hardwareE                    emulators are available for various platforms. See 6                    Section 13.12 for details on those.  ?                    Hobbyist-related hardware platform selection A                    information-various options and considerations B                    around VAX, Alpha and Integrity systems, and anF                    introduction to hardware emulation-is available at:0                    http://www.hoffmanlabs.org/ )  J                    Depending on the OpenVMS version and configuration, theJ                    OpenVMS Software Product Description (SPD) is available                    at:  7                    o  http://www.hp.com/go/openvms/doc/c                        14-34               '                    Hardware Informationw        J                    When purchasing a system, ensure that the system itselfH                    is supported, that the system disk drive is supportedF                    or closely compatible, that the optical (CD or DVD)G                    drive is supported or is closely compatable and that E                    (in the case of SCSI devices) it also specifically C                    supports 512-byte block transfers; no equivalentAH                    requirement exists for IDE devices. Also particularlyH                    ensure that the video controller is supported. Use ofH                    supported HP hardware will generally reduce the level2                    of integration effort involved.  F                    A CD-ROM, CD-R or DVD drive is required for OpenVMSF                    Alpha installations, and a DVD-ROM or recordable orG                    rewritable DVD DVD drive is required for OpenVMS I64r!                    installations.   J                    CD-ROM drive compatibility information is available at:  B                    o  http://sites.inka.de/pcde/dec-cdrom-list.txt  D           __________________________________________________________B           14.6  Where can I get more information on Alpha systems?  D                    HP operates an AlphaServer information center at:  1                    o  http://www.hp.com/go/server   C                    Alpha Technical information and documentation is                      available at:  E                    o  ftp://ftp.compaq.com/pub/products/alphaCPUdocs/   H                    o  http://h18000.www1.hp.com/products/software/alpha-                       tools/  B                    o  ftp://ftp.digital.com/pub/DEC/Alpha/systems/  1                    o  http://ftp.digital.com/pub/ @                       Digital/info/semiconductor/literature/dsc-"                       library.html  +                    o  Alpha Systems Update: C                       http://www.compaq.com/alphaserver/fb_acu.html   B                    Software Product Description (SPD) information,<                    including platform support documentation:  9                    o  http://h18000.www1.hp.com/info/spd/_  J                                                                      14-35               '                    Hardware Informationw        H                       OpenVMS typically uses SPD 25.01.xx, SPD 41.87.xx,'                       and SPD 82.35.xx.r  B                    Information on Multia hardware is available at:  F                    o  http://www.netbsd.org/Ports/alpha/multiafaq.html  G                    Information on DEC 3000 series hardware is availabled                    at:  L                    o  http://www.phys.ufl.edu/~prescott/linux/alpha/dec3000-"                       sysinfo.html  L                    o  http://www.phys.ufl.edu/~prescott/linux/alpha/dec3000-                       docs.html   @                    o  http://ftp.netbsd.org/pub/NetBSD/misc/dec-%                       docs/index.htmlh  B                    The NetBSD folks maintain useful Alpha hardware"                    information at:  C                    o  http://www.netbsd.org/Ports/alpha/models.html   D           __________________________________________________________D           14.7  Describe Alpha instruction emulation and instruction                 subsets?  B                    The Alpha architecture is upward- and downward-E                    compatible, and newer instructions are emulated onaF                    older platforms, for those cases where the compilerF                    is explicitly requested to generate the newer Alpha                     instructions.  J                    In particular, OpenVMS Alpha V7.1 and later include theG                    instruction emulation capabilities necessary for therG                    execution of newer Alpha instructions on older Alpha.G                    microprocessors. (Instruction emulation capabilitiesiD                    are available for user-mode application code, andG                    are not available to device drivers or other similar2%                    kernel-mode code.)F  A                    Alpha instructions are available in groups (orrI                    subsets). Obviously, there is the base instruction setoH                    that is available on all Alpha microprocessors. Then,F                    the following are the current instruction extension                      14-36 4  e          '                    Hardware Information         D                    groups (or subsets) that are available on some of8                    various recent Alpha microprocessors:  0                    o  byte/word extension (BWX):=                       LDBU, LDWU, SEXTB, SEXTW, STB, and STW.t  E                    o  floating-point and square root extension (FIX):eF                       FTOIS, FTOIT, ITOFF, ITOFS, ITOFT, SQRTF, SQRTG,'                       SQRTS, and SQRTT.   ,                    o  count extension (CIX):,                       CTLZ, CTPOP, and CTTZ.  2                    o  multi-media extension (MVI):E                       MAXSB8, MAXSW4, MAXUB8, MAXUW4, MINSB8, MINSW4, C                       MINUB8, MINUW4, PERR, PKLB, PKWB, UNPKBL, and                        UNPKBW.   C                    The typical instruction subset that provides theeF                    biggest win-and of course, your mileage may vary-isH                    typically the instruction set that is provided by theJ                    EV56 and later; specifically, the byte-word instructionD                    subset. To select this subset, use the following:  ;                    /ARCHITECTURE=EV56/OPTIMIZE=TUNE=GENERICu  E                    The /ARCHITECTURE controls the maximum instructionsE                    subset that the compiler will generally use, whileII                    the /OPTIMIZE=TUNE controls both the instruction-level.H                    scheduling and also the instructions generated insideG                    loops-any code resulting from /OPTIMIZE=TUNE that iseF                    specific to an instruction subset will be generatedD                    only inside loops and will also be "protected" byD                    an AMASK-based test that permits the execution ofC                    the proper code for the particular current Alphas"                    microprocessor.  F                    Typically /OPTIMIZE=TUNE=GENERIC is the appropriateG                    choice for tuning, and the /ARCHITECTURE selects the I                    minimum target architecture for general use throughout &                    the generated code.  D                    generated for later architectures and instructionE                    subsets will run on older Alpha systems due to theoC                    emulation, but if /ARCHITECTURE is a significantrE                    benefit, then the emulation might be a performance                     penalty.   J                                                                      14-37               '                    Hardware Information_        E                    Please see the OpenVMS Ask The Wizard area for thefG                    source code of a (non-privileged) tool that looks atsF                    the instruction subsets available on the particularJ                    Alpha microprocessor that the tool is run on. This toolF                    demonstrates the use of the Alpha AMASK and IMPLVER                     instructions.  @                    Please see Section 10.22 and Section 14.9 forA                    additional details and related considerations.   D           __________________________________________________________9           14.8  So how do I open up the DEC 3000 chassis?   H                    After removing those two little screws, tilt the backG                    end of the top shell upwards-then you can remove the                     lid.b  D           __________________________________________________________'           14.9  What is byte swizzling?   I                    "Swizzling" is the term used to describe the operation D                    needed to do partial longword (i.e. byte or word)D                    accesses to I/O space on those systems that don'tG                    support it directly. It involved shifting the offset J                    into an address space by 5 (or 7 for one older system),I                    and ORing this into the base address. It then requiredfJ                    the size of the operation to be ORed into the low order                    bits.  F                    That is, because the EV4 and EV5 CPUs did not bringF                    bits 0 and 1 off the chip, to do programmed I/O forI                    bytes/words, the information on the size/offset of thesG                    transfer was encoded into the address data. The dataeG                    itself then had to be shifted into the correct "byteoE                    lane" ; into the required offset position within ao%                    longword transfer;e  I                    The EV56 microprocessor supports byte/word instructionhI                    references in memory space, however only specific EV56lI                    systems can support byte/word accesses into I/O space;iF                    device drivers may or may not be able to utilize toE                    byte/word instructions to access device registers.rH                    Further, even on an EV56 system with hardware supportF                    for byte/word accesses into I/O space, the relevantF                    OpenVMS routines typically do not support byte/word)                    access into I/O space.                       14-38 M  A          '                    Hardware Informationa        D                    Systems based on the EV6 microprocessor (with the@                    salient exception of the AlphaServer GS60 andD                    AlphaServer GS140 series, for reasons of platformF                    compatability) support a flat, byte addressable I/O                    space.t  I                    If a device driver uses CRAM or IOC$WRITE_IO/IOC$READ_cH                    IO, then OpenVMS will correctly process the swizzlingE                    requirements without requiring changes the driver;rG                    OpenVMS will transparently swizzle and unswizzle thehE                    I/O space references, if needed for the particulareI                    target platform. (Access and use of these routines may G                    or may not be feasible within the requirements for alH                    particular device driver, with the decision typicallyG                    based on the target performance requirements and the G                    expected frequency of device references and thus thedH                    expected frequency of calls to these or other similar                    routines.)i  E                    To use byte/word operations on MEMORY, you need totH                    tell the compiler to use the EV56 or EV6 architectureB                    (/ARCHITECTURE=EV56). Memory operations did not?                    swizzle, but the compiler would do long/quad D                    access, and extract/insert bytes as needed. UsingD                    /ARCHITECTURE=EV56 allows smaller, more efficient4                    byte/word access logic to memory.  G                    If the application is directly referencing I/O spacenI                    access across a range of Alpha systems such as is doneaJ                    with the X Windows device drivers, then the driver willF                    need to know how to do swizzling for old platforms,H                    and byte access for new platforms. Device drivers forG                    new graphics controllers can specifically target and H                    specifically require platforms based on EV6 and laterI                    Alpha microprocessors because of this requirement, for                     instance.  @                    Please see Section 10.22 and Section 14.7 forA                    additional details and related considerations.f          J                                                                      14-39    4          '                    Hardware Information       D           __________________________________________________________E           14.10  What is the layout of the VAX floating point format?i  D                    The VAX floating point format is derived from oneD                    of the PDP-11 FP formats, which helps explain itsH                    strange layout. There are four formats defined: F 32-H                    bit single-precision, D and G 64-bit double-precisionF                    and H 128-bit quadruple precision. For all formats,G                    the lowest addressed 16-bit "word" contains the signoG                    and exponent (and for other than H, some of the mostdF                    significant fraction bits). Each successive higher-I                    addressed word contains the next 16 lesser-significant I                    fraction bits. Bit 15 of the first word is the sign, 1 G                    for negative, 0 for positive. Zero is represented by F                    a biased exponent value of zero and a sign of zero;D                    the fraction bits are ignored (but on Alpha, non-F                    zero fraction bits in a zero value cause an error.)F                    A value with biased exponent zero and sign bit 1 isG                    a "reserved operand" - touching it causes an error -vF                    fraction bits are ignored. There are no minus zero,8                    infinity, denormalized or NaN values.  F                    For all formats, the fraction is normalized and theJ                    radix point assumed to be to the left of the MSB, henceG                    the following range: 0.5 less than or equal to f and I                    less than 1.0. The MSB, always being 1, is not stored.iI                    The binary exponent is stored with a bias varying with B                    type in bits 14:n of the lowest-addressed word.  E             FP      Exponent    Exponent    Mantissa (Fraction) bits,oB             Type      Bits        Bias        including hidden bitF             ==========================================================6              F         8           128              246              D         8           128              566              G        11          1024              536              H        15         16384             113  I                    The layout for D is identical to that for F except for /                    32 additional fraction bits.O  H                    Example: +1.5 in F float is hex 000040C0 (fraction of7                    .11[base 2], biased exponent of 129)e                          14-40               '                    Hardware InformationO      D           __________________________________________________________>           14.11  Where can I find more info about VAX systems?  F                    o  HP provides limited VAX platform information viaH                       links at the AlphaServer website, itself available                       via:2                       http://www.hp.com/go/server/  G                    o  Jim Agnew maintains a MicroVAX/VAXstation FAQ at:.I                       http://www.people.vcu.edu/~agnew/MVAX/MVAX_FAQ.HTML   8                    o  The VAXstation 3100 Owner's Guide:E                       http://www.whiteice.com/~williamwebb/intro/DOC-2                       i.html  C                    o  VAXstation 3520 and VAXstation 3540 (Firefox)C                       Manual:1C                       http://starfish.osfn.org/rcs/VAX/vs3540sg.pdf   .                    o  VAX Console information:M                       http://www.mcmanis.com/chuck/computers/vaxen/panels.htme  H                    o  A field guide to PDP-11 (and VAX) Q-bus and UNIBUS.                       modules can be found at:D                       http://metalab.unc.edu//pub/academic/computer-E                       science/history/pdp-11/hardware/field-guide.txt_  B                    o  Various VAX historical information (also see3                       Section 2.1) can be found at:n?                       http://telnet.hu/hamster/vax/e_index.htmlt  D           __________________________________________________________H           14.12  Where can I find information on NetBSD for VAX systems?  A                    Gunnar Helliesen maintains a NetBSD VAX FAQ att  .                    o  http://vaxine.bitcon.no/  D           __________________________________________________________@           14.13  What system disk size limit on the MicroVAX and!                  VAXstation 3100?o  G                    System disks larger than 1.073 gigabytes (GB)-1ffffffJ                    hexidecimal blocks - are not supported on any member ofJ                    the VAXstation 3100 series and on certain older membersD                    of the MicroVAX 3100 series, and are not reliableD                    on these affected systems. (See below to identify  J                                                                      14-41 o  t          '                    Hardware Informationf        F                    the affected systems-the more recent members of theB                    MicroVAX 3100 series systems are NOT affected.)  H                    Various of the SCSI commands used by the boot driversE                    imbedded in the console PROM on all members of theeG                    VAXstation 3100 series use "Group 0" commands, whichaI                    allow a 21 bit block number field, which allows accesssH                    to the first 1fffff hexidecimal blocks of a disk. AnyF                    disk references past 1fffff will wrap-this wrappingI                    behaviour can be of particular interest when writing ahF                    system crashdump file, as this can potentially leadD                    to system disk corruptions should any part of the=                    crashdump file be located beyond 1.073 GB.   F                    More recent systems and console PROMs use "Group 1"J                    SCSI commands, which allow a 32 bit block number field.  E                    There was a similar limitation among the oldest ofoD                    the MicroVAX 3100 series, but a console boot PROMH                    was phased into production and was made available forJ                    field retrofits-this PROM upgrade allows the use of theI                    "Group 1" SCSI commands, and thus larger system disks.NG                    There was no similar PROM upgrade for the VAXstationX                    3100 series.r  ;                    Systems that are affected by this limit:_  J                    o  VAXstation 3100 series, all members. No PROM upgrade#                       is available.   H                    o  MicroVAX 3100 models 10 and 20. No PROM upgrade is                        available.  I                    o  MicroVAX 3100 models 10e and 20e. Only systems with H                       console VMB versions prior to V6.4 are affected. AH                       PROM upgrade for these specific systems is (or was&                       once) available.                      Also see   E                    o  http://www.whiteice.com/~williamwebb/intro/DOC-H                       i.html  (                    Also see Section 9.5.                      14-42               '                    Hardware Informations      D           __________________________________________________________8           14.14  What are the VAX processor (CPU) codes?                CPU:    Platform:              -----   ---------3              KA41-A : MicroVAX 3100 Model 10 and 20p4              KA41-B : VAXserver 3100 Model 10 and 20               KA41-C : InfoServer5              KA41-D : MicroVAX 3100 Model 10e and 20e 6              KA41-E : VAXserver 3100 Model 10e and 20e5              KA42-A : VAXstation 3100 Model 30 and 40t5              KA42-B : VAXstation 3100 Model 38 and 48 .              KA43-A : VAXstation 3100 Model 763              KA45   : MicroVAX 3100 Model 30 and 40m.              KA46   : VAXstation 4000 Model 60,              KA47   : MicroVAX 3100 Model 80)              KA48   : VAXstation 4000 VLC 2              KA49-A : VAXstation 4000 Model 90/90A.              KA49-B : VAXstation 4000 Model 95.              KA49-C : VAXstation 4000 Model 96,              KA50   : MicroVAX 3100 Model 90,              KA51   : MicroVAX 3100 Model 95(              KA52   : VAX 4000 Model 100(              KA53   : VAX 4000 Model 105(              KA54   : VAX 4000 Model 106,              KA55   : MicroVAX 3100 Model 85,              KA56   : MicroVAX 3100 Model 96(              KA57   : VAX 4000 Model 108,              KA58   : MicroVAX 3100 Model 88,              KA59   : MicroVAX 3100 Model 98              KA85   : VAX 8500              KA86   : VAX 8600              KA88   : VAX 88000              KA600  : VAX 4000-50 (aka VAXbrick)9              KA610  : MicroVAX I, VAXstation I (aka KD32) $              KA620  : rtVAX (VAXeln)"              KA62A  : VAX 6000-200"              KA62B  : VAX 6000-3000              KA630  : MicroVAX II, VAXstation II2              KA640  : MicroVAX 3300, MicroVAX 3400Q              KA650  : VAXstation 3200, MicroVAX 3500, MicroVAX 3600, MicroVAX III "              KA64A  : VAX 6000-400A              KA655  : MicroVAX 3800, MicroVAX 3900, MicroVAX III+e"              KA65A  : VAX 6000-500  J                                                                      14-43               '                    Hardware Information         1              KA660  : VAX 4000-200, VAX 4 upgradea"              KA66A  : VAX 6000-600"              KA670  : VAX 4000-300"              KA675  : VAX 4000-400"              KA680  : VAX 4000-500#              KA681  : VAX 4000-500Ac"              KA690  : VAX 4000-600#              KA691  : VAX 4000-605Aa#              KA692  : VAX 4000-700As#              KA693  : VAX 4000-605Ae#              KA694  : VAX 4000-705Ai               KA730  : VAX-11/730               KA750  : VAX-11/750,              KA780  : VAX-11/780, VAX-11/782               KA785  : VAX-11/785"              KA7AA  : VAX 7000-600"              KA7AB  : VAX 7000-700"              KA7AC  : VAX 7000-800              KA800  : VAXrta(              KA820  : VAX 8200, VAX 8300(              KA825  : VAX 8250, VAX 8350              KA865  : VAX 8650  D           __________________________________________________________>           14.15  Where can I get software and hardware support                  information?o  J                    Please contact the HP Customer Support Center. ServicesC                    and information, manuals, guides, downloads, andiI                    various other information is available via the supportW                    link at:n  9                    o  http://www.hp.com/products/openvms/t  I                    Various hardware and system documentation is availableu                    at:  4                    o  http://www.hp.com/go/services/  I                    TSM (Terminal Server Manager), DEChub, DECserver, etc.                     information:l  E                    o  http://www.compaq.com/support/digital_networks_n                       archive/                      14-44 m             '                    Hardware Information         D                    The owner and maintainer of current DECserver andE                    related hardware is DIGITAL Network Products Group                     (DNPG):  *                    o  http://www.dnpg.com/  D           __________________________________________________________B           14.16  Where can I get hardware self-maintenance support                  assistance?  D                    The HP Parts Directory and the HP Parts ReferenceE                    Guide (arguably the most direct descendents of the G                    HP Assisted Services program, of the Compaq AssistedeE                    Services program, and of the now-ancient DECmaileraC                    program) are available to customers that wish totC                    maintain their own system(s) (self-maintenance),hF                    but that wish some level of assistance in acquiringD                    specific parts, hardware diagnostics and hardwareC                    manuals for the system(s), and that wish to havetJ                    access to spares and module-level repairs for customer-3                    performed hardware module swaps:h  1                    o  http://www.hp.com/go/parts/p  2                    o  http://www.hp.com/buy/parts/  H                    The HP Parts Reference Guide replaces the CAS-CatalogH                    and DAS-Catalog parts catalogs and related resources.  I                    Details of the available self-maintenance programs and G                    services can vary by geography and by the particular I                    services channel(s), and current program specifics are 0                    available via the above URLs.  D           __________________________________________________________G           14.17  Why does my system halt when I power-cycle the consolei                  terminal?  I                    Various VAX and Alpha consoles are designed to processsC                    the BREAK signal, treating it as a HALT request.I  J                    A BREAK is a deliberately-generated serial line framing                    error.h  ?                    When a serial line device such as a terminal E                    powers up (or sometimes when powering down) it cansD                    generate framing errors. These framing errors are8                    indistingushable from a BREAK signal.  J                                                                      14-45 r  y          '                    Hardware InformationD        D                    When a BREAK is received on a serial line consoleE                    for various VAX systems-including most VAXstation,Q@                    MicroVAX, and VAX 4000 series-it is typicallyG                    interpreted as a HALT. Alpha systems will also oftenlD                    process a BREAK in a similar fashion, halting the                    system.  D                    There is no uniform or generally-available way toJ                    disable this behaviour on every VAX or Alpha system. OnJ                    some systems, BREAK processing can be disabled in favorG                    of [CTRL/P], or [CTRL/P] is the only way to halt thep                    processor.O  I                    The most common way to avoid these halts is to disabletG                    the serial line console or to simply not power-cycleoC                    the console terminal. There is certain important E                    system state information that is displayed only onnH                    the console, OpenVMS expects to always have access to&                    the system console.  (                    Also see Section 5.6.  D           __________________________________________________________H           14.18  Can I reuse old keyboards, mice and monitors with a PC?  F                    Older HP keyboards (those with the DIGITAL logo andG                    the RJ modular jacks), older HP mice (those with the F                    DIGITAL logo and with the RJ modular jacks, or withE                    a DIN connector with pins in a configuration other G                    than the PC-standard DIN connector pin orientation),RD                    and older video monitors (with RGB synch-on-greenD                    video signaling) all use signaling formats and/orC                    communications protocols that differ from the PCvE                    standards, and are not (easily) interchangable nor6H                    (easily) compatible with typical PC peripheral deviceH                    controllers. The LK201 and LK401 keyboards, the VSXXXG                    series mice, the VR260 and VR290 monitors, etc., arerF                    incompatible with most PC systems and with most KVM                    switches.  G                    Newer HP (and Compaq) keyboards (those with with PC- H                    style DIN plugs, and the HP, Compaq or DIGITAL logo),D                    newer HP mice (with PC-pin DIN plugs, and the HP,D                    Compaq or DIGITAL logo), and newer video monitorsG                    (multi-synch, usually with a VGA or SVGA connection,tE                    or later) are often interchangeable with "industry                       14-46 o  i          '                    Hardware Information         C                    standard" PC systems, and can often be used with G                    most PC peripheral device controllers. LK461, LK463,aG                    LK46W, LK471, PC7XS-CA, VRC16, VRC21, TFT-series LCDgF                    flat-panel displays, etc., are typically reasonablyD                    compatible with most PC systems, and will usuallyI                    perform as expected within the limits of the hardware. E                    (For details of CRT and LCD display compatibility, -                    please see Section 14.19.)   D                    Rule of thumb: if the peripheral device componentF                    was sold for use with the DEC 2000 (DECpc 150 AXP),F                    an AlphaServer series, an AlphaStation series, or aI                    more recent Alpha system, it will probably work with a G                    PC peripheral controller or with a PC-compatible KVM F                    switch. If the peripheral device component was soldJ                    for use with an VT420 or older terminal, most VAX, mostG                    VAXstation, and most Alpha systems with names in the I                    format DEC [four-digit-number], it probably won't workr>                    on a PC system or with a PC-compatible KVM.  I                    Note that the above is a general guideline, and shouldnI                    not be read to indicate that any particular peripheraliA                    device will or will not work in any particular H                    configuration, save for those specific configurations9                    the device is explicitly supported in.O  B                    Software Integrators sells a video adapter cardF                    called Gemini P1 which will drive many of the olderE                    HP (DIGITAL-logo) fixed-frequency monitors on a PCa                    system:  *                    o  http://www.si87.com/  D                    The DIGITAL (classic 2-5-2-style) part number 29-J                    32549-01 converts the output from the RGB cable (3 BNC,J                    synch-on-green) that comes with the VAXstation 3100 andG                    VAXstation 4000 series to a female SVGA D connector.SD                    You may be able to find third-party converters orF                    adapters (3 BNCs with synch-on-green signaling to 5=                    BNCs with VGA/SVGA, or to 15-pin VGA/SVGA.v  E                    This adapter will allow PC multisync monitors withaF                    the needed frequency specifications to be used withI                    the VAXstation series synch-on-green video connection.sF                    It may well also work with a VAXstation 2000 series  J                                                                      14-47 w  -          '                    Hardware Informationa        A                    systems, but specifics and performance of thattI                    combination are not immediately known at this writing.e  G                    The protocol definition for the old DIGITAL keyboard I                    and mouse interfaces is buried at the back of the QDSS I                    section in the old VAXstation II manual, specifically, E                    in the back of the VCB02 Video Subsystem Technical I                    Manual (EK-104AA-TM). The keyboard wiring and protocolwE                    is in appendix B, and occupies circa 44 pages. The :                    mouse is in appendix C, circa 12 pages.  *                    Also see Section 14.19.  D           __________________________________________________________J           14.19  Which video monitor works with which graphics controller?  J                    To determine the answer to the "will this video monitorI                    or this LCD panel work with this graphics controller?"pJ                    question, please first locate the resolution(s) and theG                    frequencies that are possible/supported at both endseI                    of the video cable (on the display and on the graphics E                    controller, in other words), and then determine ifoJ                    there are any matching settings available. If there areI                    multiple matches, you will need to determine which onev6                    is most appropriate for your needs.  G                    You will also need to determine if the video monitor-F                    or graphics controller requires the 3 BNC signalingF                    with the synchronization signals on the green wire,F                    or the 5 BNC signaling common on many PCs, or otherF                    connections such as the DB15 video connector or USBD                    connector used on various systems. (BNC signalingF                    is comparatively old, but prevalent with many olderG                    hobbyist AlphaStation or VAXstation configurations.)   J                    If there are no matches, you will likely need to changeG                    the hardware at one or both ends of the video cable.   E                    The refresh frequencies for many devices have been H                    posted to comp.os.vms and/or other newsgroups. Search6                    the archives for details. Also see:  /                    o  http://www.repairfaq.org/   4                    o  http://www.mirage-mmc.com/faq/  Z                    o  http://www.geocities.com/SiliconValley/Foothills/4467/fixedsync.html                      14-48 m  p          '                    Hardware Information/        D                    o  http://saturn.tlug.org/sunstuff/ffmonitor.html  A                    o  http://hawks.ha.md.us/hardware/monitor.htmle  E                    LCD-based and plasma-based flat-panel displays are E                    generally compatible with all recent OpenVMS Alpha-B                    systems and supported graphics controllers. ForF                    best results, you should generally set the graphicsG                    controller to match the native LCD or plasma displayrA                    resolution and (for LCD displays) also set the G                    controller refresh rate to 60Hz. Check your graphicsfD                    controller and your display documentation for anyD                    device-specific requirements and/or configuration#                    recommendations.   G                    Some of the older graphics controllers around do notuG                    necessarily generate stable signals at 60 Hz, if theoJ                    controller can even generate that refresh rate; you mayG                    end up upgrading to a less-old controller. (At leastdI                    some of the PowerStorm 3D30 and PowerStorm 4D20 serieswE                    controllers, for instance, are not necessarily the_F                    best choice for 60 Hz operations with an LCD, basedD                    on empirical testing with an AlphaStation XP1000,F                    PowerStorm 3D30, and a TFT2025 series LCD. DegradedC                    or mismatched signals produce degraded displays, H                    obviously. The newest graphics controllers compatibleC                    with your particular system are generally better H                    choices here for use with LCD; the Radeon 7500 seriesC                    is a good choice for most EV6-class AlphaStationn)                    systems, for instance.   *                    Also see Section 14.18.  D           __________________________________________________________A           14.20  Where can I get information on storage hardware?a  F                    Information on various HP (Compaq, DIGITAL) OpenVMSG                    and other disk storage hardware and controllers, and I                    related technical information on SCSI, device jumpers, )                    etc., is available at:t  2                    o  http://theref.aquascape.com/  1                                              Notet  B                       the aquascape website appears to have becomeD                       unavailable, and the FAQ maintainer is unaware  J                                                                      14-49               '                    Hardware Information         D                       of a new or replacement server. You may or mayF                       not have some success looking for this or of anyF                       other now-unavailable sites using the world-wide&                       web archives at:  0                       o  http://www.archive.org/  D           __________________________________________________________D           14.21  Why does my LK401 keyboard unexpectedly autorepeat?  6                    There are several modes of failure:  C                    o  Pressing 2 and 3 keys at the same time causes D                       one key to autorepeat when released. Check theF                       hardware revision level printed on the bottom ofE                       the keyboard. If the revision level is C01, theeH                       keyboard firmware is broken. Call field service toH                       replace the keyboard with any revision level other                       than C01.w  E                    o  Pressing certain keys is always broken. Typical F                       symptoms are: delete always causes a autorepeat,D                       return needs to be pressed twice, etc. This isF                       frequently caused by having keys depressed whileE                       the keyboard is being initialized. Pressing ^F2nD                       several times or unplugging and replugging theG                       keyboard frequently fix this problem. (Ensure younE                       have current ECO kits applied; there is a patchd5                       available to fix this problem.)t  H                    o  A key that was working spontaneously stops workingG                       correctly. This may be either of the two previouspF                       cases, or it may be bad console firmware. EnsureF                       that you have the most recent firmware installedI                       on your Alpha system. In particular, an old versiontI                       of the DEC 3000 SRM firmware is known to have a buga@                       that can cause this keyboard misbehaviour.                                  14-50 u  i          '                    Hardware Information       D           __________________________________________________________I           14.22  Problem - My LK411 sends the wrong keycodes or some keys                   are dead   H                    Check the firmware revision on the keyboard. HardwareF                    revision B01 introduced an incompatability with theD                    device driver which causes the keyboard to not beF                    recognized correctly. There is a patch available toF                    fix this problem: [AXPDRIV06_061] - the fix is alsoJ                    included in OpenVMS V6.2. The rev A01 keyboard, and the6                    LK450 should work without problems.  C                    If you are working from another operating system E                    platform, please see the DECxterm tool and related_8                    information on OpenVMS Freeware V5.0.  D           __________________________________________________________F           14.23  Which DE500 variant works with which OpenVMS version?  E                    Ensure you have a version of the Alpha SRM console F                    with support for the DE500 series device. Apply ALLI                    mandatory ECO kits for the OpenVMS version in use, andmG                    also apply the CLUSIO, ALPBOOT, and ALPLAN kits, and G                    apply any available ALPCPU ECO kit for the platform.                       o  DE500-XA:                       auto-detection, no auto-negotiation,E                       OpenVMS V6.2-1H1 and ALPBOOT ECO, also V7.0 and $                       later and ECO.?                       Device hardware id 02000011 and 02000012. 7                       Component part number 54-24187-01                       o  DE500-AA7                       auto-detection, auto-negotiation,tG                       OpenVMS V6.2 and ALPBOOT and ALPLAN ECOs, or V7.1O(                       and later and ECO.?                       Device hardware id 02000020 and 20000022.e7                       Component part number 54-24502-01                       o  DE500-BA7                       auto-detection, auto-negotiation,iF                       OpenVMS V6.2-1H3 and CLUSIO, ALPBOOT, ALPLAN and@                       ALPCPU ECOs, or V7.1-1H1 or later and ECO.F                       Device hardware id 02000030 (check connector, vsH                       DE500-FA) (other values on old Alpha SRM firmware)7                       Component part number 54-24602-01r  J                                                                      14-51 i             '                    Hardware Informationr        A                    o  DE500-FA (100 megabit fibre optic Ethernet)b0                       OpenVMS V7.1-1H1 and laterF                       Device hardware id 02000030 (check connector, vsG                       DE500-BA) (other values possible on old Alpha SRM                        firmware)H7                       Component part number 54-24899-01b  J                    To check the DE500 device hardware id from OpenVMS, use)                    the following command:   #                    $ ANALYZE/SYSTEMo,                    SDA> SHOW LAN/DEVICE=EWc:  <                    The "hardware version" will be displayed.  E                    To set the DE500 speed and duplex settings via theOI                    associated Alpha SRM console environment variable, seei                    Table 14-4.  J           ________________________________________________________________5           Table 14-4  DE500 Speed and Duplex Settings   J           ________________________________________________________________J           EWx0_MODE_setting_________________Meaning_______________________  F           Twisted-Pair                      10 Mbit/sec, nofull_duplex  D           Full Duplex, Twisted-Pair         10 Mbit/sec, full_duplex  F           AUI                               10 Mbit/sec, nofull_duplex  F           BNC                               10 Mbit/sec, nofull_duplex  G           Fast                              100 Mbit/sec, nofull_duplex   E           FastFD (Full Duplex)              100 Mbit/sec, full_duplex   J           Auto-Negotiate____________________Negotiation_with_remote_device  A                    To override the console setting and use LANCP:d              $ RUN SYS$SYSTEM:LANCP)           LANCP> SET DEVICE EWA0/SPEED=10 ,           LANCP> DEFINE DEVICE EWA0/SPEED=106           LANCP> SET DEVICE EWA0/SPEED=100/full_duplex9           LANCP> DEFINE DEVICE EWA0/SPEED=100/full_duplexd                      14-52               '                    Hardware Informationn        C                    Fast Ethernet (100Base, 100 megabit) controllersaF                    such as the DE500 series have a pair of connectionsC                    available-while traditional Ethernet (10Base, 10oF                    megabit) is inherently a half-duplex protocol, FastG                    Ethernet can be configured to use one or both of thefF                    available connections, depending on the controller.A                    Fast Ethernet can thus be half- or full-duplexuF                    depending on the configuration and the capabilitiesE                    of the network controller and the Ethernet network I                    plant. Some Fast Ethernet controllers can also operate H                    at traditional Ethernet speeds, these controllers areH                    thus often refered to as 10/100 Ethernet controllers.  D           __________________________________________________________B           14.24  How do I set the speed and duplex on OpenVMS I64?  F                    OpenVMS I64 on Integrity servers does not provide aE                    console-level environment variable akin to the SRMrI                    console variables used to manage the network speed andsF                    duplex settings on OpenVMS Alpha and Alpha systems.H                    On OpenVMS I64 on Integrity servers, LANCP is used toI                    manage the speed and the duplex setting of the networkp                    controllers.               $ RUN SYS$SYSTEM:LANCP)           LANCP> SET DEVICE EWA0/SPEED=10g,           LANCP> DEFINE DEVICE EWA0/SPEED=106           LANCP> SET DEVICE EWA0/SPEED=100/full_duplex9           LANCP> DEFINE DEVICE EWA0/SPEED=100/full_duplex   C                    The EFI-level network bootstrap operations for a H                    network-based upgrade or a network-based installationJ                    of OpenVMS I64 require the use of autonegotiation and a3                    switch capable of supporting it.e  >                    See Section 14.23 for a related discussion.  D           __________________________________________________________+           14.25  Third-party or Unsupportedi4                  disk/tape/controllers/SCSI/widgets?  I                    A wide variety of third-party and formally-unsupportedrD                    widgets-SCSI and ATA/ATAPI (IDE) disks and tapes,A                    graphics controllers, etc-are obviously widelyt@                    available, and are used on various platforms.  J                                                                      14-53    e          '                    Hardware Information         H                    If you purchase third-party or unsupported or genericF                    SCSI, ATA/ATAPI (IDE) storage devices, you and yourH                    device vendor will be responsible for the testing andI                    the support of the devices. In general, you can expect I                    that HP will address non-standards-compliance problems E                    within OpenVMS (changes that will also not prevent G                    operations with other supported devices, of course), E                    but you and/or the device vendor and/or the device F                    manufacturer are responsible for finding and fixingG                    problems in the particular third-party device and or '                    controller involved.   I                    In particular, realize that neither SCSI nor ATA/ATAPI D                    (IDE) is a particularly standard interface, theseD                    interfaces tend to be a collection of optionally-G                    implemented and standardized interface features. You I                    should not and can not simply assume that all SCSI nor G                    ATA/ATAPI (IDE) storage devices are interchangeable./G                    If you want to try to use a generic SCSI device, usetJ                    V6.2 or later, or (better) V7.1-2 or later. If you wishG                    to try to use ATA/ATAPI (IDE), use OpenVMS V7.1-2 or                     later.e  J                    On older OpenVMS releases, see the disk capacity limits!                    (Section 9.5).a  D                    With SCSI disks on releases prior to V6.2, ensureF                    that you have the ARRE and ARWE settings configuredE                    correctly (disabled). (If not, you will see DRVERRc=                    fatal drive errors and error log entries.)   F                    Some SCSI disks set the medium type byte as part ofJ                    the SCSI size field-this is a SET CAPACITY extension toH                    SCSI specs. This problem also applies to VAX V7.1 and                    later.   F                    Disks with SCSI disk sizes past 8.58 GB and/or withJ                    the SET CAPACITY extension require ALPSCSI07 ECO or theJ                    OpenVMS Alpha V7.1-2 or later release. (See Section 9.5(                    for further details.)  >                    Based on the displays of the (undocumented)J                    SYS$ETC:SCSI_INFO tool; this tool is present in OpenVMS"                    V6.2 and later:                      14-54 _  _          '                    Hardware InformationW        K           Issuing 6-byte MODE SENSE QIOW to get current values for page 01h 0                  Page Code ................. 01hF                  Page Name ................. Read-Write Error Recovery0                  Saveable .................. Yes/                  Size ...................... 10eD                  Hex Data .................. E6 08 50 00 00 00 08 002                                              00 00  I                    The E6 shown indicates that the AWRE and ARRE bits are F                    set, and this is incompatible with OpenVMS versionsE                    prior to V6.2. Further along in the same SCSI_INFOn,                    display, if you also see:  N           Issuing 6-byte MODE SENSE QIOW to get changeable values for page 81h0                  Page Code ................. 01hF                  Page Name ................. Read-Write Error Recovery0                  Saveable .................. Yes/                  Size ...................... 10uD                  Hex Data .................. C0 08 50 00 00 00 08 002                                              00 00  G                    The C0 value means that the AWRE and ARRE values can F                    be changed on this particular SCSI device. (This isI                    not always the case.) If the bits are set, you can use I                    RZDISK from the OpenVMS Freeware, and can reset the E6hI                    flag byte to hexadecimal 26 (or whatever the remainings=                    mask when you remove bits C0) on page one.o  J                    Each SCSI and ATA/ATAPI (IDE) host contains non-trivialI                    SCSI and IDE driver software, and each device containsAH                    equally non-trivial firmware- taken together with theF                    mechanical and electronic components, this softwareJ                    and firmware will determine whether or not a particular4                    device will function as expected.  F                    Also note that various devices-such as various SCSIF                    CD-R devices -can implement and can require vendor-E                    specific protocol extensions, and these extensionsbG                    can require modifications to OpenVMS or the addition C                    of various utilities. In various of these cases, D                    these devices perform functions that will requireD                    them to use SCSI or ATA/ATAPI (IDE) commands thatB                    are (hopefully) architecturally-compatible SCSIC                    or ATA/ATAPI (IDE) command extensions. (Also seee0                    Section 7.1 and Section 9.7.)  J                                                                      14-55               '                    Hardware Information         I                    Some SCSI tapes lack odd-byte transfer support, makingoJ                    operations with OpenVMS problematic at best, as OpenVMSE                    expects odd-byte support. Examples of such include H                    LTO-1 devices such as the HP Ultrium 230 series tape,I                    and the DLT VS80 series tapes. Due to the lack of odd-1I                    byte transfer support, LTO-1 devices are not supported H                    by OpenVMS. LTO devices in the LTO-2 and later seriesE                    do reportedly presently all have odd-byte transfer H                    support, and operations are reportedly rather easier.:                    Do check for formal support, of course.  J                    In order for OpenVMS to officially support a particularJ                    device, integration and testing work is mandated. ThereF                    can be no certainty that any particular device willF                    operate as expected in any particular configurationD                    without first performing this (non-trivial) work.  I                    It is quite possible to find two devices-both entirely C                    compliant with applicable standards or interface08                    documents-that will not interoperate.  ?                    The same general statement holds for OpenVMS I                    bootstrapping on an unsupported VAX or Alpha platform. H                    It might or might not work. In particular, please seeE                    the OpenVMS Software Product Description (SPD) forKF                    the list of platforms supported by OpenVMS. OpenVMSB                    is not supported on the Personal Workstation -aE                    series, on the Digital Server series platforms, on H                    the AlphaServer 2100 series 5/375 CPU, on the Multia,F                    on the AlphaServer DS20L, and on a variety of otherI                    platforms. (You might or might not see success booting 6                    OpenVMS on any of these platforms.)  '           _____________________________ ;           14.25.1  Lists of third-party widgets on OpenVMS?   J                    Various folks have successfully used common third-partyH                    disk disk devices with OpenVMS, such as the ATA (IDE)H                    and SCSI variants of the Iomega Zip250 removable disk                    device.  E                    Common SCSI CD-R/CD-RW devices such as the Plextor F                    PlexWriter 12/10/32S SCSI series and the HP DVD200iF                    series (recording CD-R) have also been successfullyD                    utilized with various AlphaStation and VAXstation                      14-56               '                    Hardware Information         G                    systems, and with tools such as CDRECORD. (A PlextorAF                    PlexWriter burn of 614400000 bytes (300000 sectors)B                    requires just over six minutes at 12x, using anD                    AlphaStation XP1000 666 MHz EV67 system UltraSCSIF                    host.) (See Section 9.7 for detailed discussions ofH                    recording optical media on OpenVMS, and the available                    tools.)  G                    If you choose to attempt to use third-party devices,aH                    ensure that you have the most current OpenVMS versionB                    and the most current ECO kit(s) applied. In theF                    specific case of the ATA (IDE) Iomega Zip250 drive,D                    ensure that you have the most current revision of*                    SYS$DQDRIVER installed.  '           _____________________________eG           14.25.2  Are the 2X-KZPCA-AA and SN-KZPCA-AA LVD Ultra2 SCSI?,  H                    Yes. Both of these controllers are Ultra2 low-voltage7           _________differential_(LVD)_SCSI controllers.   7           14.25.3  Resolving DRVERR fatal device error?   I                    If this is on an OpenVMS version prior to V6.2, pleaserH                    see the AWRE and ARRE information included in section!                    Section 14.25.u  D           __________________________________________________________7           14.26  Looking for connector wiring pin-outs?_  E                    The DECconnect DEC-423 Modified Modular Jack (MMJ)nH                    appears similar to a telphone or network modular jac,I                    though with the key offset to one side. The DECconnectyI                    MMJ connector pin-out is listed in Table 14-5, with aneJ                    end-on view of the connector pins and the connector key                    shown below.   J           ________________________________________________________________%           Table 14-5  DEC MMJ Pin-outs  J                    _______________________________________________________J                    Pin_____Description____________________________________  4                    1       Data Terminal Ready (DTR)  )                    2       Transmit (TXD)s  1                    3       Transmit Ground (TXD-)   J                                                                      14-57 /  w          '                    Hardware Informationw      J           ________________________________________________________________-           Table 14-5 (Cont.)  DEC MMJ Pin-outl  J                    _______________________________________________________J                    Pin_____Description____________________________________  0                    4       Receive Ground (RXD-)  (                    5       Receive (RXD)  J           _________6_______Data_Set_Ready_(DSR)___________________________  !              +------------------+_!              | 1  2  3  4  5  6 | !              +------------+    ++                             +____+  D                    The BC16E-nn (where the "-nn" indicates the cableG                    length) cabling and keying "flips over" or "crosses- I                    over" the signal wires, and this allows all DECconnectrG                    MMJ connections to be wired identically; the ends of G                    the BC16E are symmetrical and fully interchangeable, E                    and allows either end of the cable to be connectedtG                    either to the terminal or to the host. Specifically,sB                    the BC16E-nn cross-over wiring looks like this:  7                   Terminal                         Host 6                   MMJ                              MMJ  9                DTR 1 --->---------->----------->--- 6 DSR 9                TXD 2 --->---------->----------->--- 5 RXDs5                    3 ------------------------------ 4i5                    4 ------------------------------ 3 9                RXD 5 ---<----------<-----------<--- 2 TXDo9                DSR 6 ---<----------<-----------<--- 1 DTR   F                    DECconnect parts and connections are available fromF                    HP, and MMJ crimping dies for use in typical telco-J                    style crimping tools, and MMJ connectors, are availableH                    from Blackbox and from other communications equipment                    vendors.   I                    The PC-compatible DB9 connector pin-out found on AlphaaH                    and Integrity COM serial ports-and on most PC systems+                    is listed in Table 14-6.n                      14-58    o          '                    Hardware Information         J           ________________________________________________________________$           Table 14-6  PC DB9 Pin-out  J                    _______________________________________________________J                    Pin_____Description____________________________________  4                    1       Data Carrier Detect (DCD)  (                    2       Received Data  (                    3       Transmit Data  4                    4       Data Terminal Ready (DTR)  !                    5       Groundn  /                    6       Data Set Ready (DSR)   0                    7       Request To Send (RTS)  (                    8       Clear To Send  J           _________9_______floating_______________________________________  F                    The MicroVAX DB9 console connector pin-out predatesB                    the PC-style DB9 pin-out (adapters discussed inE                    Section 14.27), and uses a then-common (and older)sI                    standard pin-out, and uses the EIA-232 series standarda/                    signals shown in Table 14-7.l  J           ________________________________________________________________*           Table 14-7  MicroVAX DB9 Pin-out  J                    _______________________________________________________J                    Pin_____Description____________________________________  ,                    1       Protective Ground  *                    2       Transmited Data  (                    3       Received Data  0                    4       Request To Send (RTS)  4                    5       Data Terminal Ready (DTR)  /                    6       Data Set Ready (DSR)   (                    7       Signal Ground  F                    8       Shorted to pin 9 on MicroVAX and VAXstation"                            2000...  J           _________9_______...series_systems,_otherwise_left_floating.____  F                    When pin 8 is shorted to pin 9, this is a BCC08 (orH                    variant) cable, most commonly used as a console cable  J                                                                      14-59 e  n          '                    Hardware Informations        J                    on the MicroVAX 2000 and VAXstation 2000 series. (OtherJ                    systems may or may not tolerate connecting pin 8 to pin                    9.)  -                    The BN24H looks like this:   &                         MMJ       RJ45  $                          1---------8$                          2---------2$                          3---------1$                          4---------3$                          5---------6$                          6---------7  -                    The BN24J looks like this:   &                         MMJ       RJ45  $                          1---------7$                          2---------6$                          3---------3$                          4---------1$                          5---------2$                          6---------8                      Also see:  :                    o  http://www.hp.com/go/openvms/wizard/  :                    o  http://www.airborn.com.au/rs232.html  5                    o  http://www.stanq.com/cable.html   E                    o  For adapters and connectors, see Section 14.27.   D           __________________________________________________________C           14.27  What connectors and wiring adapters are available?   H                    The H8571-B and H8575-B convert the (non-2000-series)B                    MicroVAX DB9 to the DECconnect DEC-423 ModifiedD                    Modular Jack (MMJ) pin-out; to the MMJ DECconnectG                    wiring system. The MicroVAX 2000 and VAXstation 2000 G                    requires a BCC08 cable (which has the 8-9 short, seeGI                    Section 14.26) and the H8571-C or the H8571-D DB25-to-vI                    MMJ adapter for use with DECconnect. (For a discussioneH                    of the console bulkhead on the MicroVAX II series andF                    on other closely-related series systems, please see%                    Section 14.3.3.4.)r                      14-60 3  C          '                    Hardware Information         H                    Somewhat less ancient HP (HP, Compaq or DIGITAL logo)D                    systems will use either the DECconnect MMJ wiringD                    directly or-on most (all?) recent system designs-H                    the PC-compatible DB9 9-pin pin-out; the PC-style COM8                    serial port interface and connection.  G                    There are two DB9 9-pin pin-outs, that of the H8571- E                    B and similar for the MicroVAX and other and older H                    systems, and that of the H8571-J for the PC-style COMJ                    port, AlphaStation, Integrity, and other newer systems.G                    The older MicroVAX DB9 and the PC-style DB9 pin-outs &                    are not compatible.  J           ________________________________________________________________<           Table 14-8  DECconnect MMJ Connectors and Adapters  J                    _______________________________________________________J                    Part________Converts_BC16E_MMJ_male_to_fit_into________  B                    H8571-A     EIA232 DB25 25-pin female (common).J                                Functionally similar to the H8575-A, thoughD                                the H8575-A has better ESD shielding.  F                    H8571-B     Older MicroVAX (other than the MicroVAXI                                2000) DB9 EIA232 serial port. Functionally I                                similar to the H8575-B, though the H8575-B H                                has better ESD shielding. Note: Cannot beJ                                used on a PC, Alpha nor Integrity DB9 9-pin)                                connector.n  D                    H8571-C     25 pin DSUB Female to MMJ, Unfiltered  ?                    H8571-D     EIA232 25 pin male (modem-wired)n  B                    H8571-E     25 pin DSUB Female to MMJ, Filtered  I                    H8571-J     PC, Alpha, Integrity 9 pin (DB9) male (PC-yJ                                style COM serial port) Note: Cannot be usedH                                on the older MicroVAX DB9 9-pin connector  E                    H8572-0     BC16E MMJ double-female (MMJ extender)n  B                    H8575-A     EIA232 DB25 25-pin female (common).J                                Functionally similar to the H8571-A, thoughD                                the H8575-A has better ESD shielding.  J                                                                      14-61               '                    Hardware Informationi      J           ________________________________________________________________D           Table 14-8 (Cont.)  DECconnect MMJ Connectors and Adapters  J                    _______________________________________________________J                    Part________Converts_BC16E_MMJ_male_to_fit_into________  F                    H8575-B     Older MicroVAX (other than the MicroVAXI                                2000) DB9 EIA232 serial port. FunctionallywI                                similar to the H8571-B, though the H8575-BcH                                has better ESD shielding. Note: Cannot beJ                                used on a PC, Alpha nor Integrity DB9 9-pin(                                connector  G                    H8575-D     25 Pin to MMJ with better ESD Protectionr  @                    H8575-D     25 Pin to MMJ with better and ESD)                                Protectionc  A                    H8575-E     25 Pin Integrity rx2600 ManagementaC                                Processor (MP) port to MMJ, with ESDt)                                Protection   ;                    H8577-AA    6 pin Female MMJ to 8 pin MJi  F                    BC16E-**    MMJ cable with connectors, available inJ           _____________________various_lengths____________________________  H                    Numerous additional adapters and cables are availableG                    from the (now out of print) OPEN DECconnect Building I                    Wiring Components and Applications Catalog, as well as :                    descriptions of the above-listed parts.  J                    The DECconnect wiring system has insufficient signalingG                    for modems, and particularly lacks support for modemn#                    control signals.d  G                    The H8571-A and H8575-A are MMJ to DB25 (female) andwG                    other connector wiring diagrams and adapter-, cable- D                    and pin-out-related discussions are available at:  :                    o  http://www.hp.com/go/openvms/wizard/  H                    Jameco has offered a USB-A to PS/2 Mini DIN 6 AdapterH                    (as part 168751), for those folks wishing to (try to)<                    use PS/2 Keyboards via USB-A connections.  I                    The LK463 USB keyboard is also a potential option, fortF                    those wishing to connect an OpenVMS keyboard to USBI                    systems or (via the provided adapter) to PS/2 systems.nF                    The LK463 provides the classic OpenVMS keyboard and                      14-62    _          '                    Hardware Information_        F                    keyboard layout on USB-based system configurations,B                    including operations with the USB connection onI                    specific Alpha systems (and specifically on those with G                    supported USB connections) and on Integrity servers.   I                    For information on the Alpha console COM port(s) or oneA                    the VAX console port, please see Section 14.3.t  D           __________________________________________________________;           14.28  What is flow control and how does it work?s  8                    XON/XOFF is one kind of flow control.  G                    In ASCII, XON is the <CTRL/Q> character, and XOFF isn                     the <CTRL/S>.  E                    XON/XOFF flow control is typically associated with J                    asynchronous serial line communications. XON/XOFF is anI                    in-band flow control, meaning that the flow control is *                    mixed in with the data.  B                    CTS/RTS is another type of flow control, and isF                    sometimes called hardware flow control. Out-of-bandE                    means that seperate lines/pins from the data linesa@                    (pins) are used to carry the CTS/RTS signals.  B                    Both kinds of flow control are triggered when aH                    threshold is reached in the incoming buffer. The flowI                    control is suppose to reach the transmitter in time to1J                    have it stop transmitting before the receiver buffer isJ                    full and data is lost. Later, after a sufficient amountH                    of the receiver's buffer is freed up, the resume flowF                    control signal is sent to get the transmitter going                    again.t  E                    DECnet Phase IV on OpenVMS VAX supports the use ofiB                    asynchronous serial communications as a networkD                    line; of asynch DECnet. The communication devicesC                    (eg. modems, and drivers) must not be configuredlD                    for XON/XOFF flow control. The incidence of theseD                    (unexpected) in-band characters will corrupt dataC                    packets. Further, the serial line device drivers.D                    might normally remove the XON and XOFF charactersH                    from the stream for terminal applications, but DECnetG                    configures the driver to pass all characters through F                    and requires that all characters be permitted. (TheG                    communication devices must pass through not only the   J                                                                      14-63 u             '                    Hardware Informationm        I                    XON and XOFF characters, they must pass all characters I                    including the 8-bit characters. If data compression is_J                    happening, it must reproduce the source stream exactly.J                    No addition or elimination of null characters, and full%                    data transparency.e  B                    An Ethernet network is rather different than anC                    asynchronous serial line. Ethernet specifies the I                    control of data flow on a shared segment using CSMA/CDcI                    (Carrier Sense Multiple Access, with Collision Detect)fH                    An Ethernet station that is ready to transmit listensH                    for a clear channel (Carrier Sense). When the channelH                    is clear, the station begins to transmit by assertingG                    a carrier and encoding the packet appropriately. The E                    station concurrently listens to its own signal, to_H                    permit the station to detect if another station beganH                    to transmit at the same time-this is called collisionE                    detection. (The collision corrupts the signal in a I                    way that can reliably be detected.) Upon detecting theyG                    collision, both stations will stop transmitting, andpG                    will back off and try again a little later. (You canaG                    see a log of this activity in the DECnet NCP networkE                    counters.)u  I                    DECnet provides its own flow control, above and beyonddG                    the flow control of the physical layer (if any). The D                    end nodes handshake at the beginning to establishE                    a transmit window size-and a transmitter will only F                    send that much data before stopping and waiting forG                    an acknowledgement. The acknowledgement is only sent J                    when the receiver has confirmed the packet is valid. (AI                    well-configured DECnet generally avoids triggering any2D                    underlying (out-of-band) flow control mechanism.)  D           __________________________________________________________0           14.29  CD and DVD device requirements?  J                    Read access to DVD-ROM, DVD+R/RW, DVD-R/RW, CD-ROM, andJ                    CD-R/RW devices on ATAPI (IDE) connections is generallyJ                    handled transparently by SYS$DQDRIVER, and SYS$DQDRIVERD                    will transparently de-block the media-native 2048E                    byte disk blocks with the 512-byte blocks expectedw=                    by OpenVMS and by native OpenVMS software.e                      14-64               '                    Hardware Information         J                    Read access to DVD-ROM, DVD+R/RW, DVD-R/RW, CD-ROM, andI                    CD-R/RW devices on SCSI is handled by DKDRIVER, though J                    SYS$DKDRIVER will not transparently de-block the nativeJ                    2048-byte disk blocks into the 512-byte blocks expectedI                    by OpenVMS. The drive or external software is expectedEF                    to provide this de-blocking, thus either a 512-byteJ                    block capable drive (such as all RRD-series SCSI CD-ROMH                    drives) is required, or host software is required forH                    a 2048-byte block drive. Third-party SCSI drives withI                    UNIX references in their support documentation or with_H                    explicit 512-byte selectors or swiches will generallyD                    (but not always, of course) operate with OpenVMS.  F                    At least some of the Plextor PlexWriter SCSI drivesI                    can be successfully accessed (for read and write) from F                    OpenVMS, as can at least one Pioneer SCSI DVD driveF                    (for CD media). The Pioneer SCSI DVD drive switchesF                    to 2048 byte blocks for DVD media, and a block-sizeG                    conversion tool (written by Glenn Everhart) or other /                    similar tool can be applied.b  I                    OpenVMS also has supported HP DVD drives for the ATAPIo                    (IDE) bus.   A                    For some related information (and details on a <                    commercial DVDwrite package), please see:  C                    o  http://home.tiscali.de/dvd4openvms/supported_S#                       hardware.html   F                    No device driver currently presently permits directH                    block-oriented recording on DVD-RAM nor DVD+RW media,<                    nor other recordable or rewritable media.  B                    Recording (writing) of CD and DVD optical mediaF                    requires a recording or media mastering applicationJ                    or tool, and both commercial and non-commercial optionsH                    are available. See Section 9.7 for related details onI                    CDRECORD (both non-DVD and DVD versions are available,rE                    and at least one commercial version is available),eH                    and also see DVDwrite (commercial) or DVDRECORD (open                    source).e    J                                                                      14-65 e  t          '                    Hardware Informationa        A                    For information on the GKDRIVER (SYS$GKDRIVER)uI                    generic SCSI device driver and of the the IO$_DIAGNOSE_H                    $qio[w] interfaces (of SYS$DKDRIVER, SYS$DNDRIVER andE                    SYS$DQDRIVER) that are utilized by most CD and DVDII                    recording tools to send commands to SCSI, USB or ATAPIlG                    devices (most USB and ATA devices-or more correctly,lI                    most ATAPI devices-can use SCSI-like command packets),sH                    please see the SYS$EXAMPLES:GKTEST.C example, and seeG                    DECW$EXAMPLES:DECW$CDPLAYER.C example and please see E                    the various associated sections of the OpenVMS I/O +                    User's Reference Manual.   H                    For information on creating bootable optical media on5                    OpenVMS, please see Section 9.7.3.u  D           __________________________________________________________C           14.30  Office-Friendly (Quieter) Integrity rx2620 series?   G                    The part number for the so-called Office-Friendly or H                    Office Environment Integrity rx2620 series is AD244A.  H                    The AD244A option is incompatible with and eliminatesF                    the redundant cooling and power supply capabilitiesE                    of, but greatly reduces the sound output from, the E                    Integrity rx2620 rack-mount computer-room variant. H                    (Server rack-mount configurations are rated for soundF                    output in the range of 70dB, per the HP QuickSpecs.I                    Suitable for the intended installation into a computer G                    room of course, but likely rather loud for an office -                    environment installation.)   G                    If you wish to retrofit this option into an existing C                    Integrity rx2620 series, you must also order thegB                    HA113A1 (#53E) installation service; the optionG                    reportedly can not be installed by an end-user. AlsotJ                    reportedly, the option can be factory-ordered on customF                    configurations. If configuring for or converting anC                    existing rack-mount configuration for the officeaE                    environment, also consider acquiring the availablev;                    pedestal-mounting option for the series.i                            14-66               '                    Hardware Information       D           __________________________________________________________D           14.31  KVM switches for AlphaServer and Integrity Servers?  G                    Various folks have reported success with the Raritan(H                    series KVM (and specifically APKME the), and with the+                    HP-branded KVM switches.   F                    If you choose a KVM for use with Alpha or Integrity=                    servers, do ensure it provides either UnixlG                    compatibility, X Windows compatibility, or specifieshI                    the Alpha or Integrity system. (This all usually meansiF                    that the switch supports keyboards that use the so-J                    called scanset three key-down and key-up sequences-key-H                    down and key-up are key to the way X Windows and thus%                    DECwindows works.)i  G                    Also see the discussion in Section 14.18 for relatedsF                    information, and particularly for older pinouts-forJ                    those keyboard and mouse devices that pre-date the PS/2I                    DIN connections, the PC VGA/SVGA video connection, andrG                    such. Almost all VAX systems pre-date these pinouts,yG                    and peripherals intended for the older Alpha systemsC/                    also pre-date these pinouts.c                                            J                                                                      14-67 a  8                    J                    _______________________________________________________  7           15       Information on Networks and ClustersS      H                    The following sections contain information on OpenVMSG                    Networking with IP and DECnet, and on clustering andSE                    volume shadowing, on Fibre Channel, and on relatedn/                    products and configurations.   D           __________________________________________________________2           15.1  How to connect OpenVMS to a Modem?  J                    Please see the Ask The Wizard area topics starting with5                    (81), (1839), (2177), (3605), etc.   H                    o  http://www.hp.com/go/openvms/wizard/ (retired; use"                       ITRC forums)  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the availableiF                    ATW Wizard.zip archive, please see Section 3.8. ATWF                    has been superceded (for new questions) by the ITRCD                    discussion forums; the area remains available for                    reference.u  D           __________________________________________________________*           15.2  OpenVMS and IP Networking?  H                    The following sections contain information on OpenVMSD                    and IP networking, as well as IP printing topics.  '           _____________________________H9           15.2.1  How to connect OpenVMS to the Internet?   D                    Some tutorial information and tips for connectingD                    OpenVMS systems to the Internet are available at:  5                    o  http://www.tmesis.com/internet/         J                                                                       15-1 R  S          7                    Information on Networks and Clusters       '           _____________________________ .           15.2.2  Connecting to an IP Printer?  D                    To connect a printer via the IP telnet or lpr/lpdJ                    protocols, you will need to install and configure an IPH                    stack on OpenVMS, and configure the appropriate print                    queue.h  F                    With current OpenVMS IP implementations, the choiceE                    of telnet or lpr/lpd really amounts to determiningtJ                    which of these works better with the particular printer                    involved.  H                    To support network printing, the printer must includeG                    an internal or external NIC or JetDirect; an adapter,:                    connecting the network and the printer.  H                    While it is normally possible to use a host-connectedJ                    printer-when the host supports an LPD or telnet daemon,H                    and OpenVMS and most other operating systems have theF                    ability to serve locally-attached printers to otherF                    hosts on the network-it is generally far easier andG                    far more effective to use a printer that is directly H                    attached to the network. If your present printer doesI                    not have a NIC or a JetDirect, acquire an internal (if J                    available) or external NIC or JetDirect. Or replace theI                    printer. And obviously, most any operating system that E                    can serve its local printers usually also provides D                    a client that can access remote network-connected                    printers.  C                    Please see the Ask The Wizard (ATW) area topics-sH                    starting with topic (1020)-for additional information0                    on IP-based network printing.  H                    o  http://www.hp.com/go/openvms/wizard/ (retired; use"                       ITRC forums)  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the availablepF                    ATW Wizard.zip archive, please see Section 3.8. ATWF                    has been superceded (for new questions) by the ITRCD                    discussion forums; the area remains available for                    reference.   J                    Please see Section 15.2.3 for information on Postscript                    printing.                      15-2l               7                    Information on Networks and Clusters       '           _____________________________pC           15.2.3  How do I connect a PostScript printer via TCP/IP?n  I                    Using TCP/IP Services (UCX) as the TCP/IP stack, it ismG                    possible to configure queues using the UCX$TELNETSYMsE                    (TCP/IP Services prior to V5.0) or TCPIP$TELNETSYMoH                    (with V5.0 and later) in order to print to PostscriptI                    printers. This assumes however that the printer itself F                    can convert whatever is passed to it into somethingH                    intelligible. As an example, if the printer has an IPJ                    address of 123.456.789.101 and jobs should be passed to#                    port 9100 then :h  A                    $ INITIALIZE/QUEUE/ON="123.456.789.101:9100" -e2                        /PROCESSOR=UCX$TELNETSYM  -"                        my_ip_queue  A                    $ INITIALIZE/QUEUE/ON="123.456.789.101:9100" -v4                        /PROCESSOR=TCPIP$TELNETSYM  -"                        my_ip_queue  E                    The port number of 9100 is typical of HP JetDirectaE                    cards but may be different for other manufacturers                     cards.i  F                    As a better alternative, DCPS Version 1.4 and laterD                    support IP queues using either HP TCP/IP ServicesD                    for OpenVMS software or Process Software MultinetF                    for OpenVMS. The usage of this type of interface isI                    documented in the DCPS documentation or release notes,sG                    and the DCPS$STARTUP.TEMPLATE startup template file.i  J                    For general and additional (non-Postscript) IP printingH                    information, please see topic (1020) and other topicsH                    referenced in that topic elsewhere within the Ask The                    Wizard area.   H                    o  http://www.hp.com/go/openvms/wizard/ (retired; use"                       ITRC forums)  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the available F                    ATW Wizard.zip archive, please see Section 3.8. ATWF                    has been superceded (for new questions) by the ITRCD                    discussion forums; the area remains available for'                    reference. Also see:   ,                    o  http://www.wotsit.org/  J                                                                       15-3 s  o          7                    Information on Networks and Clustersd        ?                    Please see Section 15.2.2 for pointers to anR/                    introduction to IP printing.h  '           _____________________________pH           15.2.4  How do I set a default IP route or gateway on OpenVMS?  H                    If you have TCP/IP Services, then use the command for2                    TCP/IP Services V5.0 and later:                      $ TCPIP;                    SET ROUTE/GATE=x.x.x.x/DEFAULT/PERMANENTo  D                    And for earlier TCP/IP Services versions, use the                    command:                       $ UCX;                    SET ROUTE/GATE=x.x.x.x/DEFAULT/PERMANENT   '           _____________________________lE           15.2.5  How can I set up reverse telnet (like reverse LAT)?a  G                    Though it may seem obvious, Telnet and LAT are quite_J                    different-with differing capabilities and design goals.  J                    Please see the documentation around the TCP/IP ServicesJ                    for OpenVMS TELNET command CREATE_SESSION. This commandC                    is the equivilent of the operations performed inyF                    LTLOAD.COM or LAT$SYSTARTUP.COM. There is no TELNETE                    equivilent to the sys$qio[w] control interface for F                    LTDRIVER (as documented in the I/O User's ReferenceF                    Manual) available, though standard sys$qio[w] callsI                    referencing the created TN device would likely operateM                    as expected._  '           ______________________________J           15.2.6  Why can't I use PPP and RAS to connect to OpenVMS Alpha?  B                    OpenVMS Alpha IP PPP does not presently supportF                    authentication, and the Microsoft Windows NT optionD                    to disable authentication during a RAS connectionI                    apparently doesn't currently work-RAS connections will H                    require authentication-and this will thus prevent RAS                    connections.c  E                    Future versions of OpenVMS and TCP/IP Services maysI                    add this, and future versions of Microsoft Windows maynB                    permit operations with authentication disabled.                      15-4  t  B          7                    Information on Networks and Clusters       D           __________________________________________________________.           15.3  OpenVMS and DECnet Networking?  H                    The following sections contain information on OpenVMS)                    and DECnet networking.   '           _____________________________ 2           15.3.1  Can DECnet-Plus operate over IP?  C                    Yes. To configure DECnet-Plus to operate over IP-G                    transport and over IP backbone networks, install and G                    configure DECnet-Plus, and install and configure the J                    PWIP mechanism available within the currently-installedI                    IP stack. Within TCP/IP Services, this is a PWIPDRIVERnG                    configuration option within the UCX$CONFIG (versionsfG                    prior to V5.0) or TCPIP$CONFIG (with V5.0 and later)J&                    configuration tool.  '           _____________________________cG           15.3.2  What does "failure on back translate address request"P                   mean?r  %                    The error message:   M                    BCKTRNSFAIL, failure on the back translate address requesti  I                    indicates that the destination node is running DECnet- I                    Plus, and that its naming service (DECnet-Plus DECdns,_D                    LOCAL node database, etc) cannot locate a name toE                    associate with the source node's address. In other_H                    words, the destination node cannot determine the nodeG                    name for the node that is the source of the incoming                     connection.  H                    Use the DECNET_REGISTER mechanism (on the destinationB                    node) to register or modify the name(s) and theF                    address(es) of the source node. Check the namespace/                    on the source node, as well.   B                    Typically, the nodes involved are using a LOCALH                    namespace, and the node name and address settings areI                    not coherent across all nodes. Also check to make sureiI                    that the node is entered into its own LOCAL namespace. I                    This can be a problem elsewhere, however. Very rarely, I                    a cache corruption has been known to cause this error. 7                    To flush the cache, use the command:_  J                                                                       15-5    _          7                    Information on Networks and Clusters         '                    $ RUN SYS$SYSTEM:NCL_?                    flush session control naming cache entry "*"   J                    Also check to see that you are using the latest ECO forG                    DECnet-Plus for the version you are running. DECnet- 9                    Plus can use the following namespaces:   D                    o  DECdns: DECnet-Plus distributed name services.  B                    o  LocalFile: a local file containing names and                        addresses.  D                    o  DNS/BIND: the TCP/IP distributed name services                        mechanism.  @                    o  The TCP/IP Services (UCX) local host file.  >                    Of these, searching DNS/BIND and LocalFile,>                    respectively, is often the most appropriate!                    configuration.   '           _____________________________ 9           15.3.3  Performing SET HOST/MOP in DECnet-Plus?   B                    First, issue the NCL command SHOW MOP CIRCUIT *  '                    $ RUN SYS$SYSTEM:NCL)%                    SHOW MOP CIRCUIT *l  A                    Assume that you have a circuit known as FDDI-0 D                    displayed. Here is an example of the SET HOST/MOP<                    command syntax utilized for this circuit:  J                    $ SET HOST/MOP/ADDRESS=08-00-2B-2C-5A-23/CIRCUIT=FDDI-0  +                    Also see Section 15.6.3.h  '           _____________________________J=           15.3.4  How to flush the DECnet-Plus session cache?   '                    $ RUN SYS$SYSTEM:NCL3?                    FLUSH SESSION CONTROL NAMING CACHE ENTRY "*"                         15-6                7                    Information on Networks and Clusters       D           __________________________________________________________>           15.4  How to determine the network hardware address?  I                    Most Alpha and most VAX systems have a console commandrC                    that displays the network hardware address. Many_C                    systems will also have a sticker identifying the E                    address, either on the enclosure or on the networkc%                    controller itself.   J                    The system console power-up messages on a number of VAXG                    and Alpha systems will display the hardware address,nC                    particularly on those systems with an integratedr4                    Ethernet network adapter present.  C                    If you cannot locate a sticker on the system, ifoD                    the system powerup message is unavailable or doesG                    not display the address, and if the system is at theeB                    console prompt, start with the console command:                      HELP   G                    A console command similar to one of the following is B                    typically used to display the hardware address:                      SHOW DEVICE                     SHOW ETHERNET                    SHOW CONFIG  I                    On the oldest VAX Q-bus systems, the following consolesG                    command can be used to read the address directly off G                    the (DELQA, DESQA, or the not-supported-in-V5.5-and- 4                    later DEQNA) Ethernet controller:  %                    E/P/W/N:5 20001920a  E                    Look at the low byte of the six words displayed byeH                    the above command. (The oldest VAX Q-bus systems-suchH                    as the KA630 processor module used on the MicroVAX IIH                    and VAXstation II series-lack a console HELP command,G                    and these systems typically have the primary network_F                    controller installed such that the hardware addressB                    value is located at the system physical address                    20001920.)   H                    If the system is a VAX system, and another VAX systemE                    on the network is configured to answer Maintenance C                    and Operations Protocol (MOP) bootstrap requests   J                                                                       15-7    H          7                    Information on Networks and Clusters         D                    (via DECnet Phase IV, DECnet-Plus, or LANCP), theB                    MOM$SYSTEM:READ_ADDR.EXE tool can be requested:                       B/R5:100 ddcu&                    Bootfile: READ_ADDR  G                    Where ddcu is the name of the Ethernet controller in F                    the above command. The primarly local DELQA, DESQA,F                    and DEQNA Q-bus controllers are usually named XQA0.H                    An attempt to MOP download the READ_ADDR program willG                    ensue, and (if the download is successful) READ_ADDRr5                    will display the hardware address.   B                    If the system is running, you can use DECnet orE                    TCP/IP to display the hardware address with one of *                    the following commands.  %                    $! DECnet Phase IV '                    $ RUN SYS$SYSTEM:NCP 2                    SHOW KNOWN LINE CHARACTERISTICS  !                    $! DECnet-Plus '                    $ RUN SYS$SYSTEM:NCLh4                    SHOW CSMA-CD STATION * ALL STATUS  3                    $! TCP/IP versions prior to V5.0                     $ UCX&                    SHOW INTERFACE/FULL  4                    $! TCP/IP versions V5.0 and later                    $ TCPIP&                    SHOW INTERFACE/FULL  C                    A program can be created to display the hardware_B                    address, reading the necessary information fromC                    the network device drivers. A complete example CtI                    program for reading the Ethernet or IEEE 802.3 networkrH                    controller hardware address (via sys$qio calls to theH                    OpenVMS network device driver(s)) is available at the!                    following URL:   :                    o  http://www.hp.com/go/openvms/wizard/                        15-8c e  r          7                    Information on Networks and Clusterso        H                    To use the DECnet Phase IV configurator tool to watchD                    for MOP SYSID activity on the local area network:  '                    $ RUN SYS$SYSTEM:NCP M                    SET MODULE CONFIGURATOR KNOWN CIRCUIT SURVEILLANCE ENABLED   H                    Let the DECnet Phase IV configurator run for at leastD                    20 minutes, and preferably longer. Then issue the&                    following commands:  '                    $ RUN SYS$SYSTEM:NCP_P                    SHOW MODULE CONFIGURATOR KNOWN CIRCUIT STATUS TO filename.txtN                    SET MODULE CONFIGURATOR KNOWN CIRCUIT SURVEILLANCE DISABLED  E                    The resulting file (named filename.txt) can now beaH                    searched for the information of interest. Most DECnetG                    systems will generate MOP SYSID messages identifying H                    items such as the controller hardware address and theH                    controller type, and these messages are generated and7                    multicast roughly every ten minutes.r  I                    Information on the DECnet MOP SYSID messages and otheroH                    parts of the maintenance protocols is included in theH                    DECnet network architecture specifications referenced#                    in section DOC9.   '           _____________________________lJ           15.4.1  How do I reset the LAN (DECnet-Plus NCL) error counters?  .                    On recent OpenVMS releases:  )                    $ RUN SYS$SYSTEM:LANCP E                    SET DEVICE/DEVICE_SPECIFIC=FUNCTION="CCOU" devname   '           _____________________________p>           15.4.2  How do I install DECnet Phase IV on VMS 7.1?  F                    On OpenVMS V7.1, all DECnet binaries were relocatedF                    into separate installation kits-you can selectivelyI                    install the appropriate network: DECnet-Plus (formerlycG                    known as DECnet OSI), DECnet Phase IV, and HP TCP/IP 1                    Services (often known as UCX).   I                    On OpenVMS versions prior to V7.1, DECnet Phase IV was J                    integrated, and there was no installation question. YouI                    had to install the DECnet-Plus (DECnet/OSI) package on_  J                                                                       15-9 s  o          7                    Information on Networks and Clusterso        H                    the system, after the OpenVMS upgrade or installation                    completed.   F                    During an OpenVMS V7.1 installation or upgrade, theD                    installation procedure will query you to learn ifH                    DECnet-Plus should be installed. If you are upgradingI                    to V7.1 from an earlier release or are installing V7.1 E                    from a distribution kit, simply answer "NO" to the J                    question asking you if you want DECnet-Plus. Then-afterF                    the OpenVMS upgrade or installation completes - useI                    the PCSI PRODUCT INSTALL command to install the DECnet I                    Phase IV binaries from the kit provided on the OpenVMSs-                    software distribution kit.w  E                    If you already have DECnet-Plus installed and wishtF                    to revert, you must reconfigure OpenVMS. You cannotG                    reconfigure the "live" system, hence you must rebootnF                    the system using the V7.1 distribution CD-ROM. ThenE                    select the DCL ($$$ prompt) option. Then issue thei                    commands:  9                    $$$ DEFINE/SYSTEM PCSI$SYSDEVICE DKA0: ?                    $$$ DEFINE/SYSTEM PCSI$SPECIFIC DKA0:[SYS0.]uO                    $$$ PRODUCT RECONFIGURE VMS /REMOTE/SOURCE=DKA0:[VMS$COMMON]i  J                    The above commands assume that the target system deviceH                    and system root are "DKA0:[SYS0.]". Replace this withE                    the actual target device and root, as appropriate. F                    The RECONFIGURE command will then issue a series ofH                    prompts. You will want to reconfigure DECnet-Plus offG                    the system, obviously. You will then want to use the E                    PCSI command PRODUCT INSTALL to install the DECnet D                    Phase IV kit from the OpenVMS distribution media.  J                    Information on DECnet support, and on the kit names, isH                    included in the OpenVMS V7.1 installation and upgrade!                    documentation.r  I                    Subsequent OpenVMS upgrade and installation proceduresmH                    can and do offer both DECnet Phase IV and DECnet-Plus!                    installations.                           15-10 d             7                    Information on Networks and Clustersn      D           __________________________________________________________D           15.5  How can I send (radio) pages from my OpenVMS system?  >                    There are third-party products available toB                    send messages to radio paging devices (pagers),B                    communicating via various protocols such as TAPF                    (Telocator Alphanumeric Protocol); paging packages.  H                    RamPage (Ergonomic Solutions) is one of the availableF                    packages that can generate and transmit messages toG                    radio pagers. Target Alert (Target Systems; formerlytH                    the DECalert product) is another. Networking DynamicsC                    Corp has a product called Pager Plus. The SystemfD                    Watchdog package can also send pages. The ProcessA                    Software package PMDF can route specific emaili:                    addresses to a paging service, as well.  H                    Many commercial paging services provide email contactF                    addresses for their paging customers-you can simplyF                    send or forward email directly to the email address)                    assigned to the pager.w  F                    Some people implement the sending of pages to radioD                    pagers by sending commands to a modem to take theH                    "phone" off the "hook", and then the paging sequence,G                    followed by a delay, and then the same number that aiH                    human would dial to send a numeric page. (This is notG                    entirely reliable, as the modem lacks "call progressnD                    detection", and the program could simply send theH                    dial sequence when not really connected to the paging?                    company's telephone-based dial-up receiver.)u  D                    See Section 13.1 for information on the available'                    catalog of products._  D           __________________________________________________________4           15.6  OpenVMS, Clusters, Volume Shadowing?  H                    The following sections contain information on OpenVMSF                    and Clusters, Volume Shadowing, and Cluster-related%                    system parameters.r        J                                                                      15-11 e  2          7                    Information on Networks and Clusters       '           _____________________________ B           15.6.1  OpenVMS Cluster Communications Protocol Details?  D                    The following sections contain information on theI                    OpenVMS System Communications Services (SCS) Protocol.gJ                    Cluster terminology is available in Section 15.6.1.2.1.  '           _____________________________s?           15.6.1.1  OpenVMS Cluster (SCS) over DECnet? Over IP?.  H                    The OpenVMS Cluster environment operates over variousE                    network protocols, but the core of clustering usesbF                    the System Communications Services (SCS) protocols,D                    and SCS-specific network datagrams. Direct (full)+                    connectivity is assumed.   G                    An OpenVMS Cluster does not operate over DECnet, norw                    over IP.i  9                    No SCS protocol routers are available.   F                    Many folks have suggested operating SCS over DECnetC                    or IP over the years, but SCS is too far down in B                    the layers, and any such project would entail aE                    major or complete rewrite of SCS and of the DECnet D                    or IP drivers. Further, the current DECnet and IPI                    implementations have large tracts of code that operate F                    at the application level, while SCS must operate inG                    the rather more primitive contexts of the system andSJ                    particularly the bootstrap-to get SCS to operate over aI                    DECnet or IP connection would require relocating major F                    portions of the DECnet or IP stack into the kernel.G                    (And it is not clear that the result would even meet ;                    the bandwidth and latency expectations.)e  D                    The usual approach for multi-site OpenVMS ClusterI                    configurations involves FDDI, Memory Channel (MC2), oraJ                    a point-to-point remote bridge, brouter, or switch. TheI                    connection must be transparent, and it must operate atiJ                    10 megabits per second or better (Ethernet speed), withI                    latency characteristics similar to that of Ethernet oreI                    better. Various sites use FDDI, MC2, ATM, or point-to-e!                    point T3 link.d                        15-12 i  v          7                    Information on Networks and Clustersr      '           _____________________________ D           15.6.1.2  Configuring Cluster SCS for path load balancing?  I                    This section discusses OpenVMS Cluster communications, J                    cluster terminology, related utilities, and command and&                    control interfaces.  '           _____________________________ *           15.6.1.2.1  Cluster Terminology?  I                    SCS: Systems Communication Services. The protocol usednH                    to communicate between VMSCluster systems and betweenE                    OpenVMS systems and SCS-based storage controllers.cC                    (SCSI-based storage controllers do not use SCS.)o  C                    PORT: A communications device, such as DSSI, CI,.G                    Ethernet or FDDI. Each CI or DSSI bus is a differentpG                    local port, named PAA0, PAB0, PAC0 etc. All Ethernet >                    and FDDI busses make up a single PEA0 port.  B                    VIRTUAL CIRCUIT: A reliable communications pathF                    established between a pair of ports. Each port in aF                    VMScluster establishes a virtual circuit with every.                    other port in that cluster.  I                    All systems and storage controllers establish "VirtualeA                    Circuits" to enable communications between allr,                    available pairs of ports.  H                    SYSAP: A "system application" that communicates usingH                    SCS. Each SYSAP communicates with a particular remote1                    SYSAP. Example SYSAPs include:   ;                    VMS$DISK_CL_DRIVER connects to MSCP$DISK G                    The disk class driver is on every VMSCluster system. J                    MSCP$DISK is on all disk controllers and all VMSClusterH                    systems that have SYSGEN parameter MSCP_LOAD set to 1  ;                    VMS$TAPE_CL_DRIVER connects to MSCP$TAPEcG                    The tape class driver is on every VMSCluster system.IJ                    MSCP$TAPE is on all tape controllers and all VMSClusterI                    systems that have SYSGEN parameter TMSCP_LOAD set to 1(  <                    VMS$VAXCLUSTER connects to VMS$VAXCLUSTERD                    This SYSAP contains the connection manager, whichG                    manages cluster connectivity, runs the cluster state J                    transition algorithm, and implements the cluster quorum  J                                                                      15-13 l  c          7                    Information on Networks and Clustersi        G                    algorithm. This SYSAP also handles lock traffic, and B                    various other cluster communications functions.  ;                    SCS$DIR_LOOKUP connects to SCS$DIRECTORY F                    This SYSAP is used to find SYSAPs on remote systems  !                    MSCP and TMSCPsF                    The Mass Storage Control Protocol and the Tape MSCPE                    servers are SYSAPs that provide access to disk and H                    tape storage, typically operating over SCS protocols.J                    MSCP and TMSCP SYSAPs exist within OpenVMS (for OpenVMSG                    hosts serving disks and tapes), within CI- and DSSI- I                    based storage controllers, and within host-based MSCP- F                    or TMSCP storage controllers. MSCP and TMSCP can beH                    used to serve MSCP and TMSCP storage devices, and canJ                    also be used to serve SCSI and other non-MSCP/non-TMSCP#                    storage devices.   I                    SCS CONNECTION: A SYSAP on one node establishes an SCS F                    connection to its counterpart on another node. ThisJ                    connection will be on ONE AND ONLY ONE of the available$                    virtual circuits.  '           _____________________________c5           15.6.1.2.2  Cluster Communications Control?   G                    When there are multiple virtual circuits between two H                    OpenVMS systems it is possible for the VMS$VAXCLUSTERG                    to VMS$VAXCLUSTER connection to use any one of these J                    circuits. All lock traffic between the two systems will?                    then travel on the selected virtual circuit.I  H                    Each port has a "LOAD CLASS" associated with it. ThisF                    load class helps to determine which virtual circuitG                    a connection will use. If one port has a higher loaddH                    class than all others then this port will be used. IfH                    two or more ports have equally high load classes thenE                    the connection will use the first of these that it J                    finds. Prior to enhancements found in V7.3-1 and later,H                    the load class is static and normally all CI and DSSII                    ports have a load class of 14(hex), while the Ethernet H                    and FDDI ports will have a load class of A(hex). WithG                    V7.3-1 and later, the load class values are dynamic.h                      15-14    W          7                    Information on Networks and Clusters         E                    For instance, if you have multiple DSSI busses andsH                    an FDDI, the VMS$VAXCLUSTER connection will chose theF                    DSSI bus as this path has the system disk, and thusH                    will always be the first DSSI bus discovered when the(                    OpenVMS system boots.  C                    To force all lock traffic off the DSSI and on tocD                    the FDDI, for instance, an adjustment to the loadE                    class value is required, or the DSSI SCS port mustl                    be disabled.i  D                    In addition to the load class mechanisms, you canC                    also use the "preferred path" mechanisms of MSCP E                    and TMSCP services. This allows you to control the1H                    SCS connections used for serving remote disk and tapeI                    storage. The preferred path mechanism is most commonlycF                    used to explicitly spread cluster I/O activity overH                    hosts and/or storage controllers serving disk or tapeJ                    storage in parallel. This can be particularly useful ifJ                    your hosts or storage controllers individually lack theH                    necessary I/O bandwidth for the current I/O load, andI                    must thus aggregate bandwidth to serve the cluster I/O                     load.  E                    For related tools, see various utilities includingTI                    LAVC$STOP_BUS and LAVC$START_BUS, and see DCL commands 0                    including SET PREFERRED_PATH.  '           _____________________________ I           15.6.1.2.3  Cluster Communications Control Tools and Utilities?   C                    In most OpenVMS versions, you can use the tools:L  0                    o  SYS$EXAMPLES:LAVC$STOP_BUS  1                    o  SYS$EXAMPLES:LAVC$START_BUS   F                    These tools permit you to disable or enable all SCS9                    traffic on the on the specified paths.   I                    You can also use a preferred path mechanism that tells I                    the local MSCP disk class driver (DUDRIVER) which path I                    to a disk should be used. Generally, this is used with H                    dual-pathed disks, forcing I/O traffic through one ofI                    the controllers instead of the other. This can be used   J                                                                      15-15               7                    Information on Networks and Clusters         I                    to implement a crude form of I/O load balancing at thes"                    disk I/O level.  E                    Prior to V7.2, the preferred path feature uses thet                    tool:  -                    o  SYS$EXAMPLES:PREFER.MAR/  G                    In OpenVMS V7.2 and later, you can use the followingr                    DCL command:e  '                    $ SET PREFERRED_PATHW  D                    The preferred path mechanism does not disable norC                    affect SCS operations on the non-preferred path.e  D                    With OpenVMS V7.3 and later, please see the SCACPG                    utility for control over cluster communications, SCS H                    virtual circuit control, port selection, and related.  '           _____________________________ 4           15.6.2  Cluster System Parameter Settings?  H                    The following sections contain details of configuring5                    cluster-related system parameters.S  '           _____________________________ E           15.6.2.1  What is the correct value for EXPECTED_VOTES in a                      VMScluster?e  E                    The VMScluster connection manager uses the conceptoF                    of votes and quorum to prevent disk and memory dataD                    corruptions-when sufficient votes are present forF                    quorum, then access to resources is permitted. WhenJ                    sufficient votes are not present, user activity will beG                    blocked. The act of blocking user activity is called8G                    a "quorum hang", and is better thought of as a "user H                    data integrity interlock". This mechanism is designedI                    to prevent a partitioned VMScluster, and the resultantpI                    massive disk data corruptions. The quorum mechanism isvH                    expressly intended to prevent your data from becoming&                    severely corrupted.                        15-16    H          7                    Information on Networks and Clusterse        E                    On each OpenVMS node in a VMScluster, one sets twoaC                    values in SYSGEN: VOTES, and EXPECTED_VOTES. The G                    former is how many votes the node contributes to thefF                    VMScluster. The latter is the total number of votesE                    expected when the full VMScluster is bootstrapped.e  G                    Some sites erroneously attempt to set EXPECTED_VOTESRF                    too low, believing that this will allow when only aI                    subset of voting nodes are present in a VMScluster. It G                    does not. Further, an erroneous setting in EXPECTED_nC                    VOTES is automatically corrected once VMSclusterrH                    connections to other nodes are established; user dataG                    is at risk of severe corruptions during the earliesttG                    and most vulnerable portion of the system bootstrap, @                    before the connections have been established.  F                    One can operate a VMScluster with one, two, or manyI                    voting nodes. With any but the two-node configuration, G                    keeping a subset of the nodes active when some nodesoC                    fail can be easily configured. With the two-node B                    configuration, one must use a primary-secondaryI                    configuration (where the primary has all the votes), a J                    peer configuration (where when either node is down, theF                    other hangs), or (preferable) a shared quorum disk.  A                    Use of a quorum disk does slow down VMSclustergA                    transitions somewhat - the addition of a thirdsF                    voting node that contributes the vote(s) that wouldB                    be assigned to the quorum disk makes for fasterE                    transitions-but the use of a quorum disk does meanPJ                    that either node in a two-node VMScluster configuration;                    can operate when the other node is down.L  1                                              Note_  A                       The quorum disk must be on a non-host-basedA?                       shadowed disk, though it can be protected D                       with controller-based RAID. Because host-basedB                       volume shadowing depends on the lock managerD                       and the lock manager depends on the connectionC                       manager and the connection manager depends oniA                       quorum, it is not technically feasible (nor F                       even particularly reliable) to permit host-basedB                       volume shadowing to protect the quorum disk.  J                                                                      15-17 e  h          7                    Information on Networks and Clustersc        G                    If you choose to use a quoum disk, a QUORUM.DAT file C                    will be automatically created when OpenVMS first H                    boots and when a quorum disk is specified - well, theI                    QUORUM.DAT file will be created when OpenVMS is booteddG                    without also needing the votes from the quorum disk.a  A                    In a two-node VMScluster with a shared storageuF                    interconnect, typically each node has one vote, andG                    the quorum disk also has one vote. EXPECTED_VOTES is                      set to three.  F                    Using a quorum disk on a non-shared interconnect isH                    unnecessary-the use of a quorum disk does not provideG                    any value, and the votes assigned to the quorum disk H                    should be assigned to the OpenVMS host serving access                    to the disk._  C                    For information on quorum hangs, see the OpenVMSoA                    documentation. For information on changing thetD                    EXPECTED_VOTES value on a running system, see theB                    SET CLUSTER/EXPECTED_VOTES command, and see theF                    documentation for the AMDS and Availability ManagerC                    tools. Also of potential interest is the OpenVMSeJ                    system console documentation for the processor-specificG                    console commands used to trigger the IPC (InterrrupteC                    Priority Level %x0C; IPL C) handler. (IPC is notiE                    available on OpenVMS I64 V8.2.) AMDS, AvailabilityhC                    Manager, and the IPC handler can each be used toPD                    clear a quorum hang. Use of AMDS and AvailabilityJ                    Manager is generally recommended over IPC, particularlyH                    because IPC can cause CLUEXIT bugchecks if the systemG                    should remain halted beyond the cluster sanity timer J                    limits, and because some Alpha consoles and most (all?)E                    Integrity consoles do not permit a restart after au                    halt.  ?                    The quorum scheme is a set of "blade guards" E                    deliberately implemented by OpenVMS Engineering torF                    provide data integrity-remove these blade guards atD                    your peril. OpenVMS Engineering did not implementG                    the quorum mechanism to make a system manager's life H                    more difficult- the quorum mechanism was specificallyH                    implemented to keep your data from getting scrambled.                      15-18 r  n          7                    Information on Networks and Clusters       '           _____________________________e9           15.6.2.1.1  Why no shadowing for a Quorum Disk?   F                    Stated simply, Host-Based Volume Shadowing uses theJ                    Distributed Lock Manager (DLM) to coordinate changes toF                    membership of a shadowset (e.g. removing a member).D                    The DLM depends in turn on the Connection ManagerI                    enforcing the Quorum Scheme and deciding which node(s)TJ                    (and quorum disk) are participating in the cluster, andI                    telling the DLM when it needs to do things like a lock G                    database rebuild operation. So you can't introduce aSG                    dependency of the Connection Manager on Shadowing torG                    try to pick proper shadowset member(s) to use as theeI                    Quorum Disk when Shadowing itself is using the DLM and I                    thus indirectly depending on the Connection Manager to G                    keep the cluster membership straight-it's a circular                     dependency.  E                    So in practice, folks simply depend on controller- H                    based mirroring (or controller-based RAID) to protectC                    the Quorum Disk against disk failures (and dual-XF                    redundant controllers to protect against most casesG                    of controller and interconnect failures). Since thisaF                    disk unit appears to be a single disk up at the VMS9                    level, there's no chance of ambiguity.C  '           _____________________________uE           15.6.2.2  Explain disk (or tape) allocation class settings?S  E                    The allocation class mechanism provides the systemsI                    manager with a way to configure and resolve served and H                    direct paths to storage devices within a cluster. AnyG                    served device that provides multiple paths should be8G                    configured using a non-zero allocation class, either6E                    at the MSCP (or TMSCP) storage controllers, at the H                    port (for port allocation classes), or at the OpenVMSE                    MSCP (or TMSCP) server. All controllers or servers F                    providing a path to the same device should have theE                    same allocation class (at the port, controller, or_!                    server level)._  E                    Each disk (or tape) unit number used within a non- G                    zero disk (or tape) allocation class must be unique,rF                    regardless of the particular device prefix. For theH                    purposes of multi-path device path determination, anyJ                    disk (or tape) device with the same unit number and the  J                                                                      15-19 m  a          7                    Information on Networks and Clustersi        H                    same disk (or tape) allocation class configuration is1                    assumed to be the same device.r  B                    If you are reconfiguring disk device allocationH                    classes, you will want to avoid the use of allocationF                    class one ($1$) until/unless you have Fibre ChannelJ                    storage configured. (Fibre Channel storage specifically@                    requires the use of allocation class $1$. eg:                    $1$DGA0:.)t  '           _____________________________lH           15.6.2.2.1  How to configure allocation classes and Multi-Path                       SCSI?E  B                    The HSZ allocation class is applied to devices,F                    starting with OpenVMS V7.2. It is considered a portJ                    allocation class (PAC), and all device names with a PACI                    have their controller letter forced to "A". (You mightAI                    infer from the the text in the "Guidelines for OpenVMS J                    Cluster Configurations" that this is something you haveF                    to do, though OpenVMS will thoughtfully handle this%                    renaming for you.)u  H                    You can force the device names back to DKB by settingH                    the HSZ allocation class to zero, and setting the PKBJ                    PAC to -1. This will use the host allocation class, andG                    will leave the controller letter alone (that is, thecI                    DK controller letter will be the same as the SCSI porttI                    (PK) controller). Note that this won't work if the HSZrI                    is configured in multibus failover mode. In this case,rH                    OpenVMS requires that you use an allocation class for                    the HSZ.   H                    When your configuration gets even moderately complex,C                    you must pay careful attention to how you assign F                    the three kinds of allocation class: node, port andF                    HSZ/HSJ, as otherwise you could wind up with deviceC                    naming conflicts that can be painful to resolve.h  @                    The display-able path information is for SCSIE                    multi-path, and permits the multi-path software tosJ                    distinguish between different paths to the same device.E                    If you have two paths to $1$DKA100, for example byiI                    having two KZPBA controllers and two SCSI buses to theeH                    HSZ, you would have two UCBs in a multi-path set. The                      15-20 d  l          7                    Information on Networks and Clustersi        I                    path information is used by the multi-path software toS6                    distinguish between these two UCBs.  G                    The displayable path information describes the path;SF                    in this case, the SCSI port. If port is PKB, that'sF                    the path name you get. The device name is no longerH                    completely tied to the port name; the device name nowJ                    depends on the various allocation class settings of the1                    controller, SCSI port or node.c  D                    The reason the device name's controller letter isF                    forced to "A" when you use PACs is because a sharedH                    SCSI bus may be configured via different ports on theJ                    various nodes connected to the bus. The port may be PKBG                    on one node, and PKC on the other. Rather obviously,cH                    you will want to have the shared devices use the sameD                    device names on all nodes. To establish this, youE                    will assign the same PAC on each node, and OpenVMSeE                    will force the controller letter to be the same oneE                    each node. Simply choosing "A" was easier and moretG                    deterministic than negotiating the controller letter J                    between the nodes, and also parallels the solution usedF                    for this situation when DSSI or SDI/STI storage was                    used.  E                    To enable port allocation classes, see the SYSBOOTlE                    command SET/BOOT, and see the DEVICE_NAMING system                     parameter.O  D                    This information is also described in the Cluster=                    Systems and Guidelines for OpenVMS Cluster *                    Configurations manuals.  '           _____________________________o=           15.6.3  Tell me about SET HOST/DUP and SET HOST/HSCs  I                    The OpenVMS DCL commands SET HOST/DUP and SET HOST/HSCsE                    are used to connect to storage controllers via thenI                    Diagnostics and Utility Protocol (DUP). These commandsiH                    require that the FYDRIVER device driver be connected.J                    This device driver connection is typically performed byJ                    adding the following command(s) into the system startup%                    command procedure:   J                                                                      15-21               7                    Information on Networks and Clusters         $                    On OpenVMS Alpha:  !           $ RUN SYS$SYSTEM:SYSMANE?           SYSMAN> IO CONNECT FYA0/NOADAPTER/DRIVER=SYS$FYDRIVER"  "                    On OpenVMS VAX:  !           $ RUN SYS$SYSTEM:SYSGEN2(           SYSGEN> CONNECT FYA0/NOADAPTER  G                    Alternatives to the DCL SET HOST/DUP command includetI                    the console SET HOST command available on various mid- 2                    to recent-vintage VAX consoles:  G                    Access to Parameters on an Embedded DSSI controller:s  ?           SET HOST/DUP/DSSI[/BUS:{0:1}] dssi_node_number PARAMSC  C                    Access to Directory of tools on an Embedded DSSIa                    controller:  ?           SET HOST/DUP/DSSI[/BUS:{0:1}] dssi_node_number DIRECT   C                    Access to Parameters on a KFQSA DSSI controller:   ;           SHOW UQSSP ! to get port_controller_number PARAMS :           SET HOST/DUP/UQSSP port_controller_number PARAMS  H                    These console commands are available on most MicroVAXJ                    and VAXstation 3xxx series systems, and most (all?) VAXH                    4xxx series systems. For further information, see theG                    system documentation and-on most VAX systems-see theD%                    console HELP text.a  A                    EK-410AB-MG, _DSSI VAXcluster Installation andrC                    Troubleshooting_, is a good resource for settingyC                    up a DSSI VMScluster on OpenVMS VAX nodes. (ThisaE                    manual predates coverage of OpenVMS Alpha systems,nG                    but gives good coverage to all hardware and softwareoI                    aspects of setting up a DSSI-based VMScluster-and most E                    of the concepts covered are directly applicable tokI                    OpenVMS Alpha systems. This manual specifically coverssF                    the hardware, which is something not covered by the>                    standard OpenVMS VMScluster documentation.)  G                    Also see Section 15.3.3, and for the SCS name of theR0                    OpenVMS host see Section 5.7.                      15-22               7                    Information on Networks and ClustersS      '           _____________________________N8           15.6.4  How do I rename a DSSI disk (or tape?)  G                    If you want to renumber or rename DSSI disks or DSSI I                    tapes, it's easy-if you know the secret incantation...                        From OpenVMS:  *                    $ RUN SYS$SYSTEM:SYSGEN1                    SYSGEN> CONNECT FYA0/NOADAPTER                     SYSGEN> ^ZUL                    $ SET HOST/DUP/SERV=MSCP$DUP/TASK=PARAMS <DSSI-NODE-NAME>                    ...$                    PARAMS> STAT CONFR                    <The software version is normally near the top of the display.>                    PARAMS> EXIT                     ...  D                    From the console on most 3000- and 4000-class VAXD                    system consoles... (Obviously, the system must be0                    halted for these commands...)  #                    Integrated DSSI:n  H                    SET HOST/DUP/DSSI[/BUS:[0:1]] dssi_node_number PARAMS                      KFQSA:a  C                    SET HOST/DUP/UQSSP port_controller_number PARAMSs  D                    For information on how to get out into the PARAMSE                    subsystem, also see the HELP at the console prompt_G                    for the SET HOST syntax, or see the HELP on SET HOST G                    /DUP (once you've connected FYDRIVER under OpenVMS).e  F                    Once you are out into the PARAMS subsystem, you canJ                    use the FORCEUNI option to force the use of the UNITNUMG                    value and then set a unique UNITNUM inside each DSSIoI                    ISE-this causes each DSSI ISE to use the specfied unit)G                    number and not use the DSSI node as the unit number.nJ                    Other parameters of interest are NODENAME and ALLCLASS,J                    the node name and the (disk or tape) cluster allocation                    class.   C                    Ensure that all disk unit numbers used within an H                    OpenVMS Cluster disk allocation class are unique, andG                    all tape unit numbers used within an OpenVMS ClusteraH                    tape allocation class are also unique. For details on  J                                                                      15-23 p  n          7                    Information on Networks and Clustersl        I                    the SCS name of the OpenVMS host, see Section 5.7. For ?                    details of SET HOST/DUP, see Section 15.6.3.   '           _____________________________dJ           15.6.5  Where can I get Fibre Channel Storage (SAN) information?  L                    o  http://www.openvms.compaq.com/openvms/fibre/index.html  '           _____________________________wC           15.6.6  Which files must be shared in an OpenVMS Cluster?t  G                    The following files are expected to be common acrosscH                    all nodes in a cluster environment, and though SYSUAFA                    is very often common, it can also be carefullymD                    coordinated-with matching UIC values and matchingC                    binary identifier values across all copies. (ThelG                    most common use of multiple SYSUAF files is to allow_I                    different quotas on different nodes. In any event, the J                    binary UIC values and the binary identifier values mustI                    be coordinated across all SYSUAF files, and must match I                    the RIGHTSLIST file.) In addition to the list of files H                    (and directories, in some cases) shown in Table 15-1,F                    please review the VMScluster documentation, and the3                    System Management documentation.m  J           ________________________________________________________________1           Table 15-1  Cluster Common Shared FilesS  J                    _______________________________________________________J                    Filename___________________Default_Specification_______  =                    SYSUAF                     SYS$SYSTEM:.DATe  =                    SYSUAFALT                  SYS$SYSTEM:.DATt  =                    SYSALF                     SYS$SYSTEM:.DAT   =                    RIGHTSLIST                 SYS$SYSTEM:.DATn  =                    NETPROXY                   SYS$SYSTEM:.DATe  =                    NET$PROXY                  SYS$SYSTEM:.DATt  =                    NETOBJECT                  SYS$SYSTEM:.DATn  =                    NETNODE_REMOTE             SYS$SYSTEM:.DAT   H                    QMAN$MASTER                SYS$SYSTEM:; this is a set>                                               of related files                      15-24 b  S          7                    Information on Networks and Clusters       J           ________________________________________________________________9           Table 15-1 (Cont.)  Cluster Common Shared Filese  J                    _______________________________________________________J                    Filename___________________Default_Specification_______  =                    LMF$LICENSE                SYS$SYSTEM:.LDBn  >                    VMSMAIL_PROFILE            SYS$SYSTEM:.DATA  =                    VMS$OBJECTS                SYS$SYSTEM:.DATI  >                    VMS$AUDIT_SERVER           SYS$MANAGER:.DAT  >                    VMS$PASSWORD_HISTORY       SYS$SYSTEM:.DATA  >                    NETNODE_UPDATE             SYS$MANAGER:.COM  >                    VMS$PASSWORD_POLICY        SYS$LIBRARY:.EXE  =                    LAN$NODE_DATABASE          SYS$SYSTEM:.DAT   >                    VMS$CLASS_SCHEDULE         SYS$SYSTEM:.DATA  H                    SYS$REGISTRY               SYS$SYSTEM:; this is a setJ           ____________________________________of_related_files____________  I                    In addition to the documentation, also see the currentiG                    version of the file SYS$STARTUP:SYLOGICALS.TEMPLATE.tF                    Specifically, please see the most recent version ofJ                    this file available, starting on or after OpenVMS V7.2.  G                    A failure to have common or (in the case of multiple F                    SYSUAF files) synchronized files can cause problemsG                    with batch operations, with the SUBMIT/USER command,eJ                    with the general operations with the cluster alias, andE                    with various SYSMAN and related operations. ObjectnC                    protections and defaults will not necessarily be D                    consistent, as well. This can also lead to systemI                    security problems, including unintended access denialstG                    and unintended object accesses, should the files andeJ                    particularly should the binary identifier values become                    skewed.  '           _____________________________a8           15.6.7  How can I split up an OpenVMS Cluster?  F                    Review the VMScluster documentation, and the SystemF                    Management documentation. The following are the keyF                    points, but are likely not the only things you will"                    need to change.  J                                                                      15-25               7                    Information on Networks and Clusters         J                    OpenVMS Cluster support is directly integrated into theJ                    operating system, and there is no way to remove it. YouH                    can, however, remote site-specific tailoring that was@                    added for a particular cluster configuration.  H                    First: Create restorable image BACKUPs of each of theI                    current system disks. If something gets messed up, you 0                    want a way to recover, right?  D                    Create standalone BACKUP kits for the OpenVMS VAXF                    systems, and create or acquire bootable BACKUP kits1                    for the OpenVMS Alpha systems.a  I                    Use CLUSTER_CONFIG or CLUSTER_CONFIG_LAN to remove the I                    various system roots and to shut off boot services and '                    VMScluster settings.   E                    Create as many architecture-specific copies of theaI                    system disks as required. Realize that the new systemsLF                    will all likely be booting through root SYS0-if youJ                    have any system-specific files in any other roots, save                    them.  J                    Relocate the copies of the VMScluster common files onto0                    each of the new system disks.  F                    Reset the console parameters and boot flags on each7                    system for use on a standalone node.   I                    Reset the VAXCLUSTER and NISCS_LOAD_PEA0 parameters tor4                    0 in SYSGEN and in MODPARAMS.DAT.  E                    Clobber the VMScluster group ID and password using                     SYSMAN.  J                    Reboot the systems seperately, and run AUTOGEN on each.  E                    Shut off MOP services via NCP or LANCP on the boot                      server nodes.  H                    Permanent seperation also requires the duplication ofI                    shared files. For a list of the files commonly shared,p-                    please see Section 15.6.6.r  J                    Also see the topics on "cluster divorce" in the Ask The                    Wizard area.e  H                    o  http://www.hp.com/go/openvms/wizard/ (retired; use"                       ITRC forums)                      15-26 e  a          7                    Information on Networks and Clusters-        D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the availablecF                    ATW Wizard.zip archive, please see Section 3.8. ATWF                    has been superceded (for new questions) by the ITRCD                    discussion forums; the area remains available for                    reference.n  D                    Information on changing node names is included in                    Section 5.7.   '           _____________________________ .           15.6.8  Details on Volume Shadowing?  I                    This section contains information on host-based volumelJ                    shadowing; on the disk mirroring capabilities available"                    within OpenVMS.  '           _____________________________AG           15.6.8.1  Does volume shadowing require a non-zero allocationr                     classes?  C                    Yes, use of host-based Volume Shadowing requires H                    that the disk(s) involved be configured in a non-zero$                    allocation class.  I                    Edit SYS$SYSTEM:MODPARAMS.DAT to include a declarationeG                    of an non-zero allocation class, such as setting thee8                    host allocation class to the value 7:                       ALLOCLASS = 7  7                    Then AUTOGEN the system, and reboot.4  F                    You should now be able to form the shadow set via a1                    command such as the following:-  O                    $ MOUNT dsa1007: /SHADOW=($7$dkb300:,$7$dkb500:) volumelabelW  F                    When operating in an OpenVMS Cluster, this sequenceH                    will typically change the disk names from the SCSNODEH                    prefix (scsnode$dkann) to the allocation-class prefixI                    ($7$dkannn). This may provide you with the opportunity G                    to move to a device-independent scheme using logical G                    name constructs such as the DISK$volumelabel logical I                    names in your startup and application environments; anaF                    opportunity to weed out physical device references.  J                                                                      15-27               7                    Information on Networks and Clusters         I                    Allocation class one is used by Fibre Channel devices;sJ                    it can be best to use another non-zero allocation classH                    even if Fibre Channel is not currently configured and)                    not currently planned.                                                                                                     15-28    t                            J           ________________________________________________________________           Index     ;           1858                              Ambassador,1-10 4             17-Nov-1858,4-1                 AMD,2-14=           2000                              AMD64,2-13,  2-14t=           __Year,5-41___________________      Terminology,2-4 8           A                                 ANSI C,10-183           ______________________________    AP,10-7U7           Access Control List Entry,        Apache,13-9T9              5-13                           APB.EXE,14-10 7           ACCVIO,5-41                       Archie,13-8o:           ACE,5-13                          Archival MediaE           ACPI,14-25                          DVDarchive/restore,9-11V=           Acrobat,13-7                      Archive.Org,14-50 ?           ACS,5-64                          ARCH_DEFS.REQ,10-15e@           ACTS,4-9                          Argent Software,2-11A           AD244A,14-66                      Argument Pointer,10-7mE           Adobe                             ARRE,14-54,  14-55, 14-57IE             Acrobat,13-7                    ARWE,14-54,  14-55, 14-57y  0             PDF,13-7                        ASAP  6           Advanced Server,5-4                 See DSPPG           AEST,13-19,  13-25                Ask The Wizard,3-12,  5-29, J           Agnew, Jim,14-41                     5-30, 5-31, 5-40, 8-9, 9-3,G           Allocation Class                     10-2, 10-4, 10-8, 10-10, I             Fibre Channel,15-28                10-16, 10-21, 10-26, 15-1, @             Non-Zero,15-27,  15-28             15-2, 15-3, 15-276             Volume Shadowing,15-27            See ITRC6           ALLOCLASS system parameter,       ASMP,14-15F              15-27                          Asymmetric Multiprocessing           Alpha,2-146             Terminology,2-4                   See ASMPH           AlphaPC 164LX,14-28               ATA,7-1,  9-5, 14-28, 14-32,J           AlphaPC 164SX,14-28                  14-53, 14-54, 14-55, 14-57,;           AlphaServer ES47                     14-64, 14-66s?             Time,4-27                       ATAPI,14-64,  14-66 7           AlphaServer ES80                  Athlon,2-14cH             Time,4-27                       ATW,3-12,  5-29, 5-30, 5-31,J           AlphaServer GS1280                   5-40, 8-9, 9-3, 10-2, 10-4,I             Time,4-27                          10-8, 10-10, 10-16, 10-21, G           AlphaStation XP1000,14-49            10-26, 15-1, 15-2, 15-3,_4           AMASK,14-37,  14-38                  15-27  6                                               See ITRC  J                                                                    Index-1                                   Index        >           AUTOGEN,5-14                      BNU Bookreader,3-16           Automatic foreign command,8-3     Bookreader5           Automatic Foreign Command,8-4       BNU,3-1 8           AVI,7-3                             MGBOOK,3-1C           ______________________________    Boot Alias,14-9,  14-22s>           B                                 Boot Aliases,14-22;           ______________________________    Bootblock,14-20c5           Backdoor,5-10                     Bootstrapr9           Backdrop,11-8                       Alpha,14-10 6           Backdrops,11-8                      I64,14-97           BACKUP,5-21,  9-17                  VAX,14-12eB           BACKUP/IGNORE=INTERLOCK,5-58      BOOT_OPTIONS.COM,14-228           Bad Block Handling,9-3            Browser,13-4C           BADLIB,13-23                      Byers, Robert Alan,13-8 ;           BADTYPSTR,13-23                   Byte lane,14-38 7           bash,13-17                        bzip2,13-26SJ           Batch,13-22                       ______________________________-           BB_WATCH,4-5                      C J           BC16E,14-58,  14-62               ______________________________;           BCC08,14-60                       C,10-18,  10-26oF           BCKTRNSFAIL,15-5                    Compaq C Compiler,10-18,6           Berryman, Mark,1-4,  13-3              10-26J           Bi-Endian,10-17                     DEC C Compiler,10-18,  10-26B           Big-Endian,10-17                    Device Drivers,10-22I           BIND,15-6                           HP C Compiler,10-18,  10-26 B           bison,13-17                         VAX C Compiler,10-183           Blackbox,14-58                    C2,5-54e:           Bliss                             CA,5-3,  14-212             Architecture Flags,10-15        Caesar8             BLISS32E,10-15                    Julius,4-28             BLISS32I,10-15                  CalTech,13-8I             BLISS32V,10-15                  Campus Software License Grant 6             BLISS64E,10-15                    See CSLGJ             BLISS64I,10-15                  Carrier Sense Multiple Access,E             Compiler,10-14                     with Collision Detect,a4             Rebuilding System Libraries,       14-64D                10-14, 10-15                 Castle Wolfenstein,13-16.           Block                             CDA             Disk,2-25                         embossed media,9-13 C           BMC,14-33                           Recording,9-9,  14-57 8           BN24H,14-60                       CD-Audio,7-19           BN24J,14-60                       CD Player,7-1h           BNC,14-47                       Index-2 d                                 Index        A           CD-R,9-9,  13-9, 14-56, 14-57     Console Backdoor,5-10aI           CD-R/RW,9-8,  9-11                CONSOLE environment variable,n4           CDRECORD,9-8,  9-9, 14-57,           14-158              14-65                          Contrl,13-12I           CDRECORD-ProDVD,9-9               Conversational bootstrap,5-7,hA           CDRTOOLS,9-8,  9-9, 14-65            14-9, 14-10, 14-15h6           CD-RW,9-9,  13-9, 14-57           COPY,10-10F           CDWRITE,9-9                       COPY/RECORDABLE_MEDIA,9-8,2           CGI,13-21                            9-96           CHARON-VAX,3-10,  13-27           CPAN,13-256           CHECKSUM,5-45                     CRAM,14-397           CHECKSUM/ALGORITHM=MD5,5-46       CRC32,10-32r9           Clam,5-4                          $creprc,10-10 /           cli$get_value,10-4                CSA 6           Clock                               See DSPP5             TODR,4-5,  4-7                  CSLG,2-11 9             TOY,4-5,  4-7                   CSMA/CD,14-64   5           Clockmeister, Ulysses T.          CSWB,13-4f  5             See Time                          See SWBeI           CLUEXIT,15-18                     Cyclic Redundency Check,10-32iJ           Cluster                           ______________________________-             Disk,2-25                       D J           Cluster Load Balancing,15-14      ______________________________6           Cluster Terminology,15-13         4D20,14-496           CMA$RTL.EXE,10-26                 3D30,14-49C           CMS,13-22                         Dachtera, David J.,13-8 ?           00CMS,13-22                       Data Remanence,5-61o:           01CMS,13-22                       Datatrieve,3-4:           Columbia University,13-3          DATMISCH,10-18F           COM1,14-5,  14-16                 Daylight Saving Time,4-16,@           COM2,14-5,  14-16                    4-25, 4-30, 10-22H           COMMON,10-6                         US Changes 1-Mar-2007,4-22F           Compaq,5-40                       DAYLIGHT_SAVINGS.COM,4-16,  3           Compaq Secure Web Browser            4-18P  E             See SWB                         DB9,14-58,  14-59, 14-60,U4           Composer                             14-62E             Mozilla,13-19                   DCE DTS,4-10,  4-17, 4-18 9           Computer Associates,5-3,          DCL,3-3,  3-7 H              14-21                            Automatic foreign command,4           Connection Manager,15-19               8-3A           console,14-6,  14-15                Foreign command,8-3hC           Console,14-5                        Lexical functions,8-327             VAXstation 3100,9-4               PIPE,8-10h  9                                               Symbols,8-1a  J                                                                    Index-3 l  e                              Index        2           DCL$PATH,8-4                      DELETE:           DCPS,12-3                           Undelete,9-1<           DCX,13-27                         Descriptor,10-117           DDB,10-9                          Deutsch,1-2 >           DEASSIGN,8-3                      Developer Programs6           Deathrow Cluster,2-17               See DSPP>           Debugger                          Device Driver,10-9:             Signalling SS$_DEBUG,10-17      Device Drivers5           DEC-423,14-57                       C,10-22 B           DECalert,15-11                      Floating Point,10-22J           DECC$CRTL.EXE,10-26               DEVICE_NAMING system parameter5           DECconnect,14-57                     ,15-21cF           DECdns,15-6                       DFU,5-67,  9-1, 9-4, 13-13>           DECdocument,vi                    DIAGBOOT.EXE,14-139           DECDTLOGO,11-9                    DIAGNOSE,5-40 =           DECdtss,4-9                       Dictionary attackh;           DECevent,5-40                       Password,5-53eJ           DECmigrate,13-19,  13-25,         DIGITAL Network Products Group5              13-27                             ,14-45 @           DECnet,14-64,  15-6               Digital Synergy,13-9G             Asynchronous,14-63              Digital Versatile Disk,9-12 5             DECNET_REGISTER,15-5            Discountsh             MOP,15-66           DECprint,12-3                       See DSPP0           DECsound,7-3                      Disk8           DEC Test Manager,13-23              Block,2-25:           DECthreads,10-26                    Cluster,2-25A           DECUS,1-9                           Data Remanence,5-61 :             See User Group                    Erasure,5-619             Hobbyist Licenses,2-10            Sector,2-25 ;           DECUServe,1-3                       Security,5-61t>           DECUS Software Library,13-3       Disk Mirroring,9-2  B           DECW$CDPLAYER,7-1                   See Volume Shadowing1           DECW$CDPLAYER.C,14-66             Disks,J           DECW$EXAMPLES:DECW$CDPLAYER.C       ATA,7-1,  9-5, 14-28, 14-32,E              ,14-66                              14-53, 14-54, 14-55,a6           DECW$KEYMAP Logical Name,              14-57D              11-10                            Bad Block Handling,9-38           DECwindows Transport,11-17          CD-R,14-56@           DECwindows V1.2-6,11-17             CD-R/RW,9-8,  9-11?           DECwindows V1.3,11-17               CD-Recordable,9-9 A           DEFINE,8-3                          DVD+R/RW,9-8,  9-11 ;                                               dvd200i,14-57 A                                               DVD-R/RW,9-8,  9-11 @                                               DVD-Recordable,9-9                      Index-4 s  a                              Index        H           Disks (cont'd)                    DST,4-16,  4-18, 4-25, 4-30,4             FAT Format,7-2                     10-22H             Floppy,7-2                        US Changes 1-Mar-2007,4-22=             IDE,7-1,  9-5, 14-28, 14-32,    DTM,13-22,  13-23o7                14-53, 14-54, 14-55,         00DTM,13-23e7                14-57                        01DTM,13-23iA             Jumpers,14-49                   DTSS,4-9,  4-10, 4-18m=             MSCP,9-3                          DTSS$CLERK,4-25 G             PC Format,7-2                     Too Few Servers Detected,r5             PlexWriter,14-57,  14-65             4-26t;             SCSI,9-3,  9-15, 14-2,          DTSS$CLERK,4-25gJ                14-28, 14-32, 14-35,         DTSS$INSTALL_TIMEZONE_RULE.COM4                14-42, 14-49, 14-53,            ,4-24D                14-54, 14-55, 14-56,         DTSS$NTP_PROVIDER.C,4-10F                14-57                        DTSS$SET_TIMEZONE.EXE,4-17E             SCSI-2,9-6                      DTSS$UTC_STARTUP.COM,4-24C0             Volume Set,9-7                  Dump;             Zip,14-56,  14-57                 Process,10-28a5           Disk Shadowing,9-2                DVD,14-57 ;           Distributed Lock Manager,           Recording,9-9 B              15-19                          DVD+R,9-9,  9-11, 13-98           Distribution Kits,2-8             DVD+R/RW,9-8D           DJE Systems,13-8                  DVD+RW,9-9,  13-9, 14-659           DKDRIVER,14-65,  14-66            dvd200i,14-57 C           DLM,15-19                         DVDarchive/restore,9-11_<           DLT VS80,14-56                    DVD-R,9-9,  13-9?           DNDRIVER,14-66                    DVD-R/RW,9-8,  9-11 9           DNPG,14-45                        DVD-RAM,14-65eF           DNS,15-6                          DVDRTOOLS,9-8,  9-9, 14-65=           DOCUMENT,10-16                    DVD-RW,9-9,  13-9cE                                             DVDwrite,9-8,  9-9, 9-10,c4             See DECdocument                    14-658           DoD,5-61                          Dvorak,11-10G           DOD_ERAPAT,5-62                   Dynamic System Recognition, 4           Download Kits,2-8                    14-25J           DQDRIVER,7-1,  9-5, 14-32,        ______________________________-              14-57, 14-64, 14-66            E J           Driver                            ______________________________3             Device,10-9                     EB,2-25l6           DRVERR,14-54,  14-57              EBCDIC,7-3E           DSPP,2-12,  2-17, 2-21, 14-34     e-Business Infrastructurel:           DSR,14-25                            Package,2-8/           DSSI,5-62                         ECOh  7                                               kits,5-32e  J                                                                    Index-5 a  n                              Index        5           Editor,13-17                      ETAPE,7-3d:           Editors,3-3                       Ethernet,14-64=           Edit Version,10-27                Event Flags,11-12o4           EFI,5-8,  14-9, 14-20, 14-22,     EWS,11-38              14-23, 14-33                   Exabyte,2-259           EFI Boot Alias,14-9,  14-22       Examples,10-3lB           EIA-232,14-59                     EXE$GL_TICKLENGTH,4-14B           ELSA GLoria Synergy,5-30          EXE$GL_TIMEADJUST,4-14;           ELV,5-41                          EXE$GL_TODR,4-4tD           elvis,13-17                       EXE$GQ_SAVED_HWCLOCK,4-6D           EM64T,2-13,  2-14                 EXE$GQ_SYSTIME,4-3,  4-6;             Terminology,2-4                 EXE$GQ_TDF,4-17o?           emacs,3-3,  13-17                 EXE$GQ_TODCBASE,4-31;           embossed media,9-13               EXE$SETTIME,4-4wA           Encompass                         Executable Image,10-8uE             See User Group                  Executive mode code,10-29eA             Hobbyist Licenses,2-10          EXPECTED_VOTES systemm>           Encompasserve,1-3,  2-17             parameter,15-17  ?           Encompass Software Library,       Explicitly ParalleleD              13-3                              Instruction Computing6           Endian-ness,10-17                   See EPICI           Energy Policy Act of 2005,        Extensible Firmware Interface 5              4-22                             See EFI J           Engineering Software,7-2          ______________________________-           Ensoniq,7-3                       FrJ           Enterex                           ______________________________9             Hobbyist Licenses,2-10          f$getenv,14-8e  7           Enterprise Operating              f$parse,8-2n8              Environment                    f$trnlnm,8-39             See EOE                         f$unique,5-67 @           EOE,2-7                           Facility Prefix,10-2>           EPIC,14-33                        FAQ Sections (Old)G           $erapat,5-62                        DCL$PATH Logical Name,8-4 6           Erasure,5-61                        DCL1,8-38           Ergonomic Solutions,15-11           DCL10,8-108           Error analysis,5-40                 DCL11,8-108           Error Log Viewer                    DCL12,8-116             See ELV                           DCL3,8-56           ES47                                DCL4,8-56             Time,4-27                         DCL5,8-66           ES80                                DCL6,8-76             Time,4-27                         DCL7,8-76                                               DCL8,8-86                                               DCL9,8-9                      Index-6 i  a                              Index        G           FAQ Sections (Old) (cont'd)       FAQ Sections (Old) (cont'd)/  :             DECw$IGNORE_WORKSTATION           Mgmt10,15-169                Logical Name,11-5              Mgmt11,5-14t9             DECw1,11-1                        Mgmt12,5-60s:             DECw10,11-7                       Mgmt13,15-219             DECw11,11-12                      Mgmt14,15-9e9             DECw12,11-13                      Mgmt15,5-15i9             DECw13,11-13                      Mgmt16,5-16 9             DECw14,11-14                      Mgmt17,5-25a9             DECw15,11-16                      Mgmt18,5-26 9             DECw16,11-17                      Mgmt19,5-27 7             DECw17,11-17                      Mgmt2,5-2 9             DECw2,11-3                        Mgmt20,5-59$9             DECw3,11-3                        Mgmt21,5-27/9             DECw4,11-4                        Mgmt23,5-29 9             DECw5,11-10                       Mgmt24,5-29N9             DECw6,11-4                        Mgmt25,5-32e:             DECw9,11-6                        Mgmt26,15-239             DECwindows,11-1                   Mgmt27,5-33 9             Doc1,3-1                          Mgmt28,15-4 7             Doc10,3-5                         Mgmt3,5-4s9             Doc11,3-6                         Mgmt30,5-34r9             Doc13,3-10                        Mgmt31,5-35 9             Doc14,3-12                        Mgmt32,5-37 9             Doc2,3-2                          Mgmt33,5-37 9             Doc4,3-5                          Mgmt34,5-40 9             Doc5,3-5                          Mgmt35,5-55e9             File1,9-1                         Mgmt36,15-4l9             File2,9-1                         Mgmt37,5-40d9             File3,9-2                         Mgmt38,5-41X9             File4,9-3                         Mgmt39,5-41 7             File5,9-4                         Mgmt4,5-6e9             File6,9-7                         Mgmt40,5-42A9             File7,9-8,  9-11                  Mgmt41,5-42 :             File8,9-15                        Mgmt42,15-209             File9,9-15                        Mgmt43,5-44s:             Intro1,1-2                        Mgmt44,15-24:             Intro2,1-2                        Mgmt45,15-259             Intro3,1-3                        Mgmt46,5-45 I             Intro4,1-4                        Mgmt47,15-13,  15-14, 15-15a9             Intro5,1-5                        Mgmt48,5-46 9             Intro6,1-8                        Mgmt49,5-46b>             Intro7,1-3                        Mgmt5,5-7,  5-119             Intro8,1-9                        Mgmt50,5-47i9             Mgmt1,5-1                         Mgmt51,5-47   J                                                                    Index-7                                   Index        G           FAQ Sections (Old) (cont'd)       FAQ Sections (Old) (cont'd)   8             Mgmt52,5-49                       Prog7,10-68             Mgmt53,5-49                       Prog8,10-68             Mgmt54,15-27                      Prog9,10-78             Mgmt56,5-49                       Soft1,13-18             Mgmt57,5-50                       Soft10,8-9:             Mgmt58,15-6                       Soft12,13-23:             Mgmt59,5-50                       Soft13,13-25:             Mgmt6,15-3                        Soft14,13-269             Mgmt60,5-52                       Soft2,13-15U9             Mgmt61,15-19                      Soft3,13-19 9             Mgmt62,5-53                       Soft4,13-20o9             Mgmt63,5-64                       Soft5,10-18 9             Mgmt64,5-57                       Soft6,13-21 9             Mgmt9,5-12                        Soft7,13-22a9             Misc12,12-3                       Soft8,13-22h7             Misc13,12-3                       Time1,4-1m@             Misc15,15-11                      Time10,4-25,  4-278             Misc17,15-9                       Time11,4-39             Misc19,15-12                      Time12,4-29S9             Misc2,12-1                        Time13,4-20 7             Misc20,12-4                       Time2,4-7 8             Misc4,14-60                       Time3,4-128             Misc6,15-5                        Time4,4-168             Misc7,15-7                        Time5,4-237             Misc9,15-4                        Time6,4-9 8             Prog1,10-2                        Time7,4-148             Prog10,10-7                       Time8,4-137             Prog11,10-8                       Time9,4-7 7             Prog12,10-10                      Util1,7-1E7             Prog13,10-10                      Util2,7-2 7             Prog14,2-23                       Util3,7-3i7             Prog15,2-25                       Util5,7-3s7             Prog16,10-12                      Util6,7-4 6             Prog17,10-13                      VAX8,4-36             Prog18,10-14                      VMS1,2-18             Prog19,10-16                      VMS10,2-128             Prog2,10-4                        VMS11,2-138             Prog20,10-16                      VMS12,2-168             Prog21,10-17                      VMS13,2-188             Prog22,10-17                      VMS14,2-198             Prog23,10-18                      VMS15,2-208             Prog3,10-5                        VMS16,2-218             Prog4,10-5                        VMS17,2-226             Prog5,10-5                        VMS2,2-3                      Index-8 5  3                              Index        J           FAQ Sections (Old) (cont'd)       ______________________________-             VMS3,2-4                        GcJ             VMS4,2-4                        ______________________________6             VMS5,2-5                        gawk,13-163             VMS7,2-6                        GB,2-25f5             VMS8,2-9                        gcc,13-18 ?             VMS9,2-10,  2-12                gcc emulation,13-17 8           Farmer, Ken,1-3                   $getdvi,10-28           FAT Disks,7-2                     $getjpi,10-28           FFT,13-12                         $getqui,5-54?           fgrep,13-16                       $getsyi,10-2,  14-2u9           $filescan,9-4                     Gigabyte,2-25e:           FILE tool,13-14                   GKDRIVER,14-66:           File Versions,5-66                GKTEST.C,14-66A           Firefox                           Global Maintech,14-21d7             Service Guide,14-41             gmake,13-13 4           Firmware,14-23                    GMT,4-305           FISH,13-4                         GNM,10-16 =           Flat-panel display,14-49          GNU,13-17,  13-18t6           flex,13-17                        GnuPG,13-5B           Flight simulator,13-16            GNU Privacy Guard,13-5=           Floating point,10-29              GNV,13-17,  13-18 6           Floating Point,10-6               Google,1-38             Device Drivers,10-22            gopher,13-164           Floppy,7-2                        GPG,13-56           FLORIAN,9-1                       Grace,13-9D           $flush,9-2                        GrayMatter Software,2-11>           FOE,2-7                           grep,13-16,  13-172           Fonts,11-18                       GS12807           Foreign command,8-3                 Time,4-27Y5           Foreign Command,8-4               GTK,13-12 6           Fortran,10-7                      GUID,14-226           Foundation Operating              gzip,13-26J              Environment                    ______________________________-                                             H J             See FOE                         ______________________________9           FreeVMS,2-2                       H8571-A,14-62iA           Freeware,9-4,  10-4, 10-16        H8571-B,14-60,  14-62_A             SETCLOCK,4-14                   H8571-C,14-60,  14-62oA           FSF,13-18                         H8571-D,14-60,  14-62_9           ftso,13-27                        H8571-E,14-62 9           ftsv,13-27                        H8571-J,14-62_9                                             H8572-0,14-62M  J                                                                    Index-9                                   Index        D           H8575-A,14-62                     IA-64 Architecture,2-14,;           H8575-B,14-62                        14-25, 14-33T:           H8575-D,14-62                     IARGCOUNT,10-78           H8575-E,14-62                     iasi64,10-29H           H8577-AA,14-62                    IDE,7-1,  9-5, 14-28, 14-32,J           half-flash,14-19                     14-53, 14-54, 14-55, 14-57,4           Hard Partitions,14-8                 14-64:           Hardware                          Identifier,5-2<             Serial Number,10-7                Subsystem,10-91           Harmless signature,14-20          Imageu=           $hash_password,5-54                 Executable,10-8G;           HBMM,5-64                           Loadable,10-9 <           HBVS,15-19                          Protected,10-9<           Helliesen, Gunnar,14-41             Shareable,10-89           Hemker, Mark,13-10                  System,10-9 7           Heroix,14-21                        UWSS,10-9 F           Heuser-Hofmann, Eberhard,         IMAGELIB.OLB,10-18,  10-30<              Dr.,9-10                       ImageMagick,13-6?           Hobbyist,2-10                     IMAGENAME.DMP,10-28a9           Hour                              IMPLVER,14-38o;             Off By One,4-25,  4-30,         InfoServer,9-10c9                10-22                          Scribe,9-10 C           HP OpenVMS for Integrity          INFO-VAX,1-3,  1-4, 1-7 A              Servers                        Info-Zip,3-11,  13-26e;             See OpenVMS I64                 INITIALIZE,5-41rA           HP Renew,14-34                    INITIALIZE/ERASE,5-62_8           HP-UX,10-17                       Install,5-24?           HSG80,5-64                        INSTALL,10-8,  10-9c?           ht://Dig,13-13                    INSTALL utility,5-1tB           html,13-16                        Instruction sets,10-29I           HTML,10-16                        Integrity,2-14,  2-16, 14-33, 4           httpd,13-16                          14-34=           HTTP_SERVER,13-3                    Terminology,2-4rB           ______________________________    Integrity rx2600,14-62<           I                                 Integrity rx2620C           ______________________________      Office-Friendly,14-66 ;           I64,2-14,  14-25, 14-33             Quieter,14-66t=             Terminology,2-4,  14-33         Intel,2-14,  2-16r  3           IA-32,2-13,  2-15                 Interexm<             Terminology,2-4                   See User GroupJ           IA-64                             Interrrupt Priority Level %x0C6             Terminology,2-4                    Handler  ;                                               See IPC,15-18                       Index-10U i                                 Index        J           Inv Cmd,5-8                       ______________________________-           INVRECTYP,5-21                    KtJ           IO$_DIAGNOSE,7-1,  14-66          ______________________________6           IOC$READ_IO,14-39                 KA630,14-66           IOC$WRITE_IO,14-39                KA650,14-66           Iomega,14-56,  14-57              KA655,14-63           IPB.EXE,14-9                      Kb,2-26y:           IPC,15-18                         KB,2-25,  2-26?           IRC Client                        Kednos,2-11,  13-19 A             Mozilla,13-19                   Kerberos,5-54,  11-18 7           IRIG,4-9                          Kermit,13-3 B           ISO-9660,9-10,  14-23             Kernel mode code,10-294             Joliet extension,9-10           Keyboard:             Rock Ridge extension,9-10         Dvorak,11-10=           ISO-9660:1999,9-10                Key Mapping,11-10 4           ISVN                              ki,14-218             See DSPP                        Kilobit,2-26@           Itanium,2-14,  2-16, 14-25,       Kilobyte,2-25,  2-26=              14-33                          KI Products,14-21n4             Terminology,2-4                 Kits,2-8E                                             KVM switch,14-46,  14-47, 4           Itanium Processor Family             14-67  J             See Itanium                     ______________________________-           ITRC,1-1,  3-13, 5-32             LeJ             FTP ECO site,1-1,  5-32         ______________________________C             Support Forums,5-32             LAN$NODE_DATABASE,15-25 ?           ______________________________    LANCP,14-52,  14-53 @           J                                 LAVC$START_BUS,15-15?           ______________________________    LAVC$STOP_BUS,15-15e5           J2EE,13-20                        LBX,11-18r5           Jameco,14-62                      LCD,14-49rH           James,1-1                         LCD flat-panel display,14-478           Java,13-20                        Levitte,13-8A           JBC$COMMAND,5-33                  Lexical functions,8-3f<           JCL,7-3                           LHR,5-24,  10-279           JDK,2-8,  13-20                   lib$crc,10-32 ?           JetDirect,15-2                    lib$crc_table,10-32nF           Joliet ISO-9660 extension,        lib$find_image_symbol,10-9=              9-10                           lib$free_ef,11-12d<           Jones, David,13-3                 lib$get_ef,11-12@           Jouk,13-3                         lib$get_foreign,10-4?           Julian Day,4-1                    lib$get_symbol.,8-3 @           Jumpers,14-49                     lib$set_logical,10-5  J                                                                   Index-11    f                              Index        G           lib$set_symbol,8-3                LISP$DAYLIGHT_SAVING_TIME_Pl@           lib$sfree1_dd,10-11                  Logical Name,4-23H           lib$sget1_dd,10-11                LISP$TIME_ZONE Logical Name,3           LIB$SIGNAL,10-17                     4-23 ?           lib$spawn,10-10                   Little-Endian,10-17 4           lib$table_parse,10-15             LJK,2-117           lib$tparse,10-15                  LK201,14-46-7           lib$trim_filespec,9-4             LK401,14-4607           LIB.L32,10-14                     LK461,14-47r?           LIB.L64,10-15                     LK463,14-47,  14-62l7           LIB.MLB,10-30                     LK46W,14-47 7           LIB.R64,10-15                     LK471,14-47sH           LIB.REQ,10-14                     LMF,2-10,  2-12, 5-12, 10-8,9           License,2-12,  5-12, 10-8,           11-5, 12-5eE              11-5, 12-5                     LMF$DISPLAY_OPCOM_MESSAGEe@           License Unit Requirements            Logical Name,12-5=              Table,2-9, 5-51                LMF$LICENSE,15-25u9           Licensing,10-7                    LNM$GROUP,8-2 7           Licensing Programs                LNM$JOB,8-21;             Campus Software License         LNM$PROCESS,8-2w:                Grant,2-11                   LNM$SYSTEM,8-2?             Developers,2-12,  2-21          Loadable Image,10-9 B             DSPP,2-12,  2-21                LOAD_PWD_POLICY system=             Educational,2-11                   parameter,5-53 :             Hobbyist,2-10                   LocalFile,15-6=           Liebert,13-10                     Locked Files,9-17 8           Limited Hardware Release,         Logical Name:              10-27                            DCL$PATH,8-4F             See LHR                           DECW$IGNORE_WORKSTATION,5           linda,13-10                            11-5 ?           LINK                                DECW$KEYMAP,11-10 J             /NOSYSLIB,10-30                   LISP$DAYLIGHT_SAVING_TIME_P,5             /SYSEXE,10-30                        4-23 A           Linker                              LISP$TIME_ZONE,4-23 H             COMMON,10-6                       LMF$DISPLAY_OPCOM_MESSAGE,5             PSECT_ATTR,10-6                      12-5C@             SYMBOL_VECTOR,10-6                MAIL$TIMEZONE,4-23A             SYS$BASE_IMAGE,10-5               NOTES$TIMEZONE,4-23 ;             SYS.STB,10-5                      SYS$DISK,10-5,<             /SYSEXE,10-5                      SYS$LOGIN,8-10C           LINKER,10-18                        SYS$LOGIN_DEVICE,8-10 >           Linux shell,3-3,  3-7               SYS$SCRATCH,8-10  J                                               SYS$TIMEZONE_DAYLIGHT_SAVING6                                                  ,4-23                      Index-12  E  -                              Index        G           Logical Name (cont'd)             Mature Product Support,5-22 2             SYS$TIMEZONE_DIFFERENTIAL,      MAXBUFC                4-23                           system parameter,9-15 J             SYS$TIMEZONE_NAME,4-21,         MAXPROCESSCNT system parameter4                4-23                            ,5-103             TZ,4-21                         Mb,2-265:             UCX$NFS_TIME_DIFFERENTIAL,      MB,2-25,  2-264                4-23                         MBM,4-274             UCX$TDF,4-22                    MCOE,2-7:           Logical Names                     MD5,5-4,  5-468             Compared to DCL Symbols,8-2     Megabit,2-269           Logical Partitioning,14-8         Megabyte,2-25l:           LOGINOUT,5-10                     Megabytes,2-26<           lPars,14-8                        Menufinder,13-10B           lpd,15-2                          MESSAGE Compiler,10-16A           lpr,15-2                          MGBOOK Bookreader,3-1 5           LRA0:,12-3                        MGPCX,7-2l?           LTO-1,14-56                       microfortnight,2-2755           LURT,2-9,  5-51                   MIME,13-9 9           LVD,14-57                         Minicopy,5-64 :           164LX,14-28                       Minimerge,5-64;           Lynx,13-4,  13-5                  Mini-Merge,5-645?           ______________________________    Minor Version,10-27 9           M                                 Mirroring,9-2   B           ______________________________      See Volume Shadowing?           MA780,14-15                       MISC4,14-59,  14-61OF           MadGoat,5-40,  7-2, 13-2,         Mission Critical Operating:              13-14                             Environment6           MAIL$TIMEZONE Logical Name,         See MCOE8              4-23                           Mlucas,13-12D           MAIL10,6-3                        MMJ,14-57,  14-58, 14-605           MAIL7,6-1                         mmk,13-13_4           MAIL9,6-1                         MMOV,7-3G           Mail Count,6-1                    Modified Modular Jack,14-57 5           Maintenance Version,10-27           See MMJ8G           Majordomo,13-9                    MODPARAMS.DAT,15-26,  15-27 9           Major Version,10-27               Montagar,13-1 4           make,13-13                        MOP,15-67           Malmberg's Ftp Service,13-18      Mosaic,13-4 E           Management Processor              Mozilla,6-2,  13-4, 13-20 :             DECconnect MMJ Adapter,           Also see SWB<                14-62                          Composer,13-19  >                                               IRC Client,13-19B                                               Netnews Client,13-19  J                                                                   Index-13 1                                 Index        ;           MP,14-33                          NETOBJECT,15-251:             DECconnect MMJ Adapter,         NETPROXY,15-25J                14-62                        Netscape Navigator,6-2,  13-20E           MPEG,7-3                          Networking Dynamics,5-40, ;           mpi,13-10                            13-12, 15-111>           MS780,14-15                       New Mail Count,6-14           MSCP,15-14                        NIC,15-2B           MSCP$DISK,15-13                   NISCS_LOAD_PEA0 system>           MSCP$TAPE,15-13                      parameter,15-264           MSCP_LOAD system parameter,       NIST,4-95              15-13                          NOCLI,8-5 8           MTAACP,5-41                       NODECW,11-14:           MTEXCH,7-3                        NODEVICE,11-14:           MUA4224,5-34                      NOLICENSE,5-109           Multia,14-26                      NONEWMAIL,6-1oH           Multimedia Services,7-3           NOTES$TIMEZONE Logical Name,3           Multinet,15-3                        4-23n;           Multiprocessing                   NOTSAVESET,5-59 7             See ASMP and SMP                NOTSET,4-251;           mx,13-16                          17-Nov-1858,4-1-6           mxrn,13-16                        nPars,4-27;           MySQL,13-13                       NTP,4-10,  4-31PJ           ______________________________    ______________________________-           N                                 O J           ______________________________    ______________________________5           NAM$C_MAXRSS,9-3                  ODBC,9-15e<           NAML$C_MAXRSS,9-3                 ODS-2,9-3,  9-10<           NCL,15-6                          ODS-5,9-3,  9-10;           NCSA,13-4                         Office-Friendly5:           NCSC,5-61                           rx2620,14-66F           NCSC C2,5-54                      Ohio State University,13-3J           NCSC Class C2,5-10                OPA0:,5-10,  14-5, 14-6, 14-158           NET$DISABLE_DTSS,4-26             OpenECS,2-178           NET$PROXY,15-25                   OpenNTP,4-31;           NET1,15-1                         OpenVMS.Org,1-3A9           NET2,15-1                         OpenVMS Alpha =           NetBeans,2-8                        Terminology,2-40G           NetBSD,14-36                      OpenVMS Alpha Upgrades,5-16 7           Netnews Client                    OpenVMS AXP1=             Mozilla,13-19                     Terminology,2-4 ?           NETNODE_REMOTE,15-25              OpenVMS Galaxy,14-2 A           NETNODE_UPDATE,15-25              OPENVMS-HOBBYIST,2-10,C                                             OpenVMS I64,2-2,  14-33lE                                               Terminology,2-4,  14-33                       Index-14                                    Index        5           OpenVMS I64 Upgrades,5-19         Patch,7-4n  3           OpenVMS Upgrade                   Patches0  :             See Update, Upgrade and           See ECO kits9                Install                      PATHWORKS,5-423           OpenVMS VAX                       PB,2-25 I             Terminology,2-4                 PBXGB-AA PowerStorm 3D30,5-31eI           OpenVMS VAX Upgrades,5-20         PBXGB-CA PowerStorm 4D20,5-31 H           Opteron,2-14                      PBXGD-AE PowerStorm 350,5-31F           OSU,13-3                          PBXGK-BB PowerStorm 3D10T,3           OSU HTTPD Web Server,13-16           5-30 :           Outbuildings                      PC7XS-CA,14-476             See Time                        PCDISK,7-28           Overwrite,5-61                    PC Disks,7-25           ______________________________    PCF,11-18 =           P                                 PCSI,5-44,  10-284  8           ______________________________    PCSI Install9           Page                                See Installi8             Memory,2-25                     PCSI Upgrade9             Size,2-25                         See Upgrade 3           Pagelet                           PCX,7-2 :             defined,2-25                    PDF,3-1,  13-76           Pager Plus,15-11                  Peek,13-128           Page Size,14-2                    Pentium,2-15C           PAGE_SIZE,2-25                    Perl,2-8,  13-11, 13-23e9           Paging,15-11                      Petabyte,2-25$4           PAK,2-10,  2-12, 5-12, 10-8,      PGP,13-5J              11-5, 12-5                     PHYSICALPAGES system parameter4           PAKGEN,2-12,  10-8, 12-5             ,5-14B           PALcode,14-4,  14-16              PHYSICAL_MEMORY system=           PA-RISC,2-14                         parameter,5-14 5           $parse,9-4                        PINE,13-9 9           Parse Style,9-3                   pin-out,14-61B9           Partitioning                      Pioneer,14-65 5             Hard,14-8                       PIPE,8-10 6             Logical,14-8                    PL/I,13-19H             Soft,14-8                       Plextor,14-56,  14-57, 14-653             Virtual,14-8                    pm,11-8d  6           Partner Programs                  PMDF,15-11  4             See DSPP                        PMU,4-27G           Password                          POLYCENTER Software Product >             Dictionary attack,5-53             Install Utility6             Purdy Polynomial,5-54             See PCSI  J                                                                   Index-15                                   Index        J           Port,15-13                        ______________________________-           Postscript,10-16                  QsJ           POV-Ray,13-9                      ______________________________=           PowerStorm 300,5-31               $qio,10-9,  11-12 =           PowerStorm 350,5-31               QMAN$JOURNAL,5-33 =           PowerStorm 3D10T,5-30             QMAN$MASTER,15-25 :           PowerStorm 3D30,5-31,  14-49      QuickSpecs,3-48           PowerStorm 4D20,5-31,  14-49      QUORUM,15-187           PPP,15-4                          Quorum Disk-=           Preatorian Cluster,2-17             Shadowing,15-19 J           Pretty Good Privacy,13-5          ______________________________-           Printing                          R2J             DCPS,12-3                       ______________________________D             lpr,15-2                        Radeon 7500,5-32,  14-499             Parallel Port,12-3              RamPage,15-11 4             telnet,15-2                     RAS,15-4>           Prior Version Support,5-22        Raxco,2-11,  13-12  A           Privileged-mode code,10-29        Refurbished Equipment9  :           Process Dump,10-28                  See HP Renew/           Process Software,2-11,  13-2,     RGBRJ              15-3, 15-11                      synch-on-green,14-46,  14-67<           Product Authorization Key,        RIGHTSLIST,15-257              2-12, 5-12, 10-8, 11-5,        Rlogin,5-63 <              12-5                           RMS,9-15,  10-30>           Product Registration,10-2         RMS Journaling,9-2I           PRODUCT SHOW PRODUCT,5-45         RMS Sequential Record Format, 3           ProDVD,9-9                           9-16)B           ProGIS,7-2                        RMS_SEQFILE_WBH system=           Programming Examples                 parameter,5-57 8             See Examples                    Roadmap,2-159           Protected Image,10-9              robomon,14-21 I           Protected Subsystems,5-2          Rock Ridge ISO-9660 extension 4           PSECT_ATTR,10-6                      ,9-108           Purdy Polynomial                  Rocksoft,5-4  G             Password,5-54                   Royal Greenwich Observatory-  6           PURGE,5-66                          See Time6           $putmsg,10-5                      RRD42,9-138           pvm,13-10                         RS-232,14-598           PVS,5-22                          rx2600,14-628           PWIP,15-5                         rx2620,14-34C           Python,13-12                        Office-Friendly,14-66E;                                               Quieter,14-66T                      Index-16  I  9                              Index        E           RZDISK,14-55                      Self-extracting zip,13-26iI           RZTOOLS,5-62                      Sequential Record Format,9-162>           ______________________________    Serial Number,10-7G           S                                 SETBOOT,9-14,  14-20, 14-22+G           ______________________________    SET BOOTBLOCK,9-14,  14-20,94           S3 Switch,14-6                       14-229           SAIC,1-4,  13-1, 13-3             SETCLOCK,4-14 I           Saiga Systems,5-40                SET DEVICE/RESET=ERROR_COUNT,r3           Samba,5-4                            5-35 =           SAMBA,13-11                       SET FILE/CACHING_ E           SAO,4-1                              ATTRIBUTES=NO_CACHING,-2           SCACP,15-16                          9-9D           Scaliger                          SET PREFERRED_PATH,15-15G             Julius Caesar,4-2               SET PREFERRED_PATH command,w4           Scaliger, Joseph,4-2                 15-16G           Scribe                            SET PROCESS/PARSE_STYLE,9-3k8             InfoServer,9-10                 $SETTIM,4-25J           SCS,15-12,  15-13                 SET TIME,4-5,  4-7, 4-8, 4-13,9           SCSI,9-15,  14-2, 14-28,             4-25, 4-27_A              14-32, 14-35, 14-42, 14-49,    SET TIME/CLUSTER,4-13 I              14-53, 14-54, 14-55, 14-56,    SETTIME system parameter,4-4, 8              14-57, 14-65, 14-66               4-5, 4-28B           SCSI-2,9-6                        $set_system_event,4-135           SCSI_INFO,14-54                   SFX,13-26 9           SCSNODE system parameter,         Shadowing,9-2 ?              5-12, 5-14, 15-27                Quorum Disk,15-19 ?           SCSSYSTEMID system parameter,     Shareable image,5-1 @              5-14                           Shareable Image,10-8;           SDL,10-16                         shell,3-3,  3-77F           SDML,10-16                        SHOW MEMORY/CACHE command,3             See DECdocument,vi                 9-16 ;           Search Engine,13-13               Signature,14-2226           Sector                            SIMH,13-275             Disk,2-25                       SMB,13-11,@           Secure Shell,13-4                 smg$create_menu,10-4  B           Secure Web Browser                SMG$GET_TERM_DATA,12-1  E             See SWB                         Smithsonian Astrophysical >           Security,5-10,  5-61                 Observatory,4-15             Dictionary attack,5-53          SMP,14-15 6             NCSC C2,5-54                    SMTP,13-169             Password,5-53                   $sndjbc,10-10,5           Security MUP,5-3                  SNTP,4-31   J                                                                   Index-17                                   Index        <           SOAP,2-8,  13-9                   Storage (cont'd)<           SOC,3-4                             FAT Format,7-28           Soft Partitions,14-8                Floppy,7-2=           Software Resources Interna-         Free Space,12-3xJ              tional,2-11, 3-10, 13-27         IDE,7-1,  9-5, 14-28, 14-32,E           Sophos,5-4                             14-53, 14-54, 14-55, 6           SPIA,10-28                             14-57  ;           SPIU                                PC Format,7-2 D             See PCSI                          Remaining on Tape,12-3F           Spy,13-12                           SCSI,9-15,  14-2, 14-28,E           Spyglass,13-4                          14-32, 14-35, 14-42, E           SQP,2-8                                14-49, 14-53, 14-54,eD           SRI                                    14-55, 14-56, 14-578             Software Resources                SCSI-2,9-6<                International,2-11, 3-10,      Volume Set,9-77                13-27                        Stream,9-1639           SRI International,1-3             StreamLF,9-16aE           SRM,4-27,  14-15, 14-16           Subsystem Identifier,10-9s;             Acronym,14-4                    SUNY NCSB,13-18 <             System Reference Manual,        Supervisor,13-12=                14-4                         Supnik, Bob,13-27 3           SS$_DEBUG,10-17                   Support H           SS$_NOCLI,8-5                       Prior Version Support,5-22>           SSH,13-4                          SVGA,14-46,  14-675             FISH,13-4                       SWB,13-208;           SSL,2-8                           Swizzling,14-38 7             SSLeay,13-4                     164SX,14-28 F           SSLeay,13-4                       SYI$_PAGE_SIZE,2-25,  14-2F           Stark, Tim,13-27                  SYLOGICALS.COM,4-26,  8-6,3           STARLET.L32,10-14                    11-5(E           STARLET.L64,10-15                 SYLOGICALS.TEMPLATE,4-26, J           STARLET.R64,10-15                    5-39, 5-63, 6-1, 8-6, 15-253           STARLET.REQ,10-14                 Symbols H           Storage                             Compared to Logical Names,4             ATA,7-1,  9-5, 14-28, 14-32,         8-15                14-53, 14-54, 14-55,           DCL,8-1E?                14-57                        Symbol Substitution17             CD-R,14-56                        PIPE,8-105>             CD-R/RW,9-8,  9-11              SYMBOL_VECTOR,10-6E             CD-Recordable,9-9               Symmetric Multiprocessing 5             Disk Settings,14-49               See SMP @             DVD+R/RW,9-8,  9-11             synch-on-green,14-47             DVD-R/RW,9-8,  9-11              DVD-Recordable,9-9                      Index-18w 1                                 Index        I           Synch-on-green,14-46,  14-67      SYS$STARTUP:DTSS$STARTUP.COM, 3           sys$acm,5-54                         4-25nH           SYS$BASE_IMAGE,10-5               SYS$TIMEZONE.DAT,4-17,  4-24H           SYS$BASE_IMAGE.EXE,4-17           SYS$TIMEZONE_DAYLIGHT_SAVING@           sys$creprc,10-10                     Logical Name,4-23E           SYS$DIAGNOSTICS.SYS,9-14          SYS$TIMEZONE_DIFFERENTIAL @           SYS$DISK Logical Name,10-5           Logical Name,4-23E           SYS$DKDRIVER,14-65,  14-66        SYS$TIMEZONE_NAME Logical >           SYS$DNDRIVER,14-66                   Name,4-21, 4-23B           SYS$DQDRIVER,7-1,  9-5, 14-32,    SYS$TIMEZONE_RULE,4-19E              14-57, 14-64, 14-66            SYS$TIMEZONE_SRC.DAT,4-24g:           SYS$EFI.SYS,9-14,  14-9           sys$trnlnm,8-3=           sys$erapat,5-62                   SYS$WSDRIVER,11-398           SYS$EXAMPLES:DAYLIGHT_            SYS.STB,10-58              SAVINGS.COM,4-16, 4-18         SYSALF,15-257           SYS$EXAMPLES:GKTEST.C,14-66       SYSAP,15-13gE           sys$filescan,9-4                  SYSBOOT,5-7,  5-11, 15-21 7           sys$flush,9-2                     SYSGEN,5-11s8           sys$getdvi,10-2                   SYSLOG,13-107           sys$getenv,14-8                   System Disk1A           sys$getjpi,10-2                     VAXstation 3100,9-4 =           sys$getsyi,2-25,  10-2            System Image,10-94=           SYS$GKDRIVER,14-66                System parameters5=           SYS$LIB_C.TLB,10-23,  10-30         ALLOCLASS,15-27bA           SYS$LOGIN Logical Name,8-10         DEVICE_NAMING,15-21 B           SYS$LOGIN_DEVICE Logical Name       EXPECTED_VOTES,15-17B              ,8-10                            LOAD_PWD_POLICY,5-539           sys$parse,9-4                       MAXBUF,9-15 @           SYS$PIPE,8-10                       MAXPROCESSCNT,5-10=           SYS$PROCDMP,10-28                   MSCP_LOAD,15-13 C           SYS$PROTECTED_PROCDMP,10-28         NISCS_LOAD_PEA0,15-26g@           sys$putmsg,10-5                     PHYSICALPAGES,5-14B           sys$qio,10-9,  11-12                PHYSICAL_MEMORY,5-14B           SYS$REGISTRY,15-25                  RMS_SEQFILE_WBH,5-57H           SYS$SCRATCH Logical Name,8-10       SCSNODE,5-12,  5-14, 15-27>           SYS$SETBOOT.EXE,9-14,  14-20,       SCSSYSTEMID,5-14E              14-22                            SETTIME,4-4,  4-5, 4-28gF           sys$setddir,10-5                    TIMEPROMPTWAIT,4-4,  4-5>           SYS$SETTIM,4-25                     TMSCP_LOAD,15-13>           sys$set_system_event,4-19           UAFALTERNATE,5-9>           sys$sndjbc,10-10                    VAXCLUSTER,15-269                                               VOTES,15-17 G                                               WINDOW_SYSTEM,5-9,  11-5,,6                                                  11-14@                                               WRITESYSPARAMS,5-9  J                                                                   Index-19 i  9                              Index        5           Systems and Options Catalog,      TIE,13-25 0              3-4                            Time6           System Service,10-9                 ACTS,4-9C           SYSUAF,5-53,  15-25                 AlphaServer ES47,4-27 C             Bypass,5-10                       AlphaServer ES80,4-27 E             Corrupt,5-10                      AlphaServer GS1280,4-27 E           SYSUAFALT,15-25                     Clock Drift,4-12,  4-14 9           SYSUAFALT.DAT,5-10                  Dial-up,4-9 D           ______________________________      DST,4-25,  4-30, 10-22>           T                                   DTSS,4-10,  4-18G           ______________________________      Error modifying time,4-2556           TAP,15-11                           GMT,4-30<           TAPECOPY,7-3                        Greenwich,4-306           Tapes                               IPL,4-126             Compaction,12-4                   IRIG,4-98             Compression,12-4                  Julian,4-1A             Conversion,7-3                    Julian Calendar,4-2 =             EBCDIC,7-3                        Julian Date,4-1 <             Free Space,12-3                   Julian Day,4-16           tar,13-16,  13-17                   NIST,4-99           Target Systems,15-11                NOTSET,4-25 6           TB,2-25                             NTP,4-10J           tcgmsg,13-10                        Off By One Hour,4-25,  4-30,6           TCL,13-13                              10-22A           TCOPY,7-3                           Prime Meridian,4-30 ;           TCPIP$CONFIGURATION.DAT,5-13        SETCLOCK,4-14 C           TCQ,14-2                            SET TIME Command,4-25_6           TDF,4-17                            TDF,4-17=           TECsys,14-21                        TIMENOTSET,4-25 G           telnet,15-2                         Time service enabled,4-25 A           Telnet,5-63                         Timezone Rules,4-21 <           Telocator Alphanumeric              TODR,4-5,  4-7;              Protocol,15-11                   TOY,4-5,  4-7F6           Terabyte,2-25                       UT0,4-306           Terminal emulator                   UT1,4-306             VTstar,11-4                       UT2,4-30J           Terminal Server Manager,13-12       UTC,4-17,  4-25, 4-30, 10-22;           Test-Drive,2-17                   TIMENOTSET,4-25eA           Test Manager,13-23                TIMEPROMPTWAUT systemeA           Text,10-16                           parameter,4-4, 4-535           Text editor,13-17                 Timezones D           Text editors,3-3                    SYS$TIMEZONE_NAME,4-215           TFT2025,14-49                       TZ,4-21   F                                               zic compiler,4-19,  4-20                      Index-20a g  i                              Index        I           TMSCP,15-13,  15-14               Uniform Time Act of 1966,4-22i9           TMSCP_LOAD system parameter,      unixODBC,9-16 @              15-13                          UNIX shell,3-3,  3-77           TODR,4-5,  4-7                    unzip,14-23 7           Tomcat,2-8                        Update,5-23 8           Too Few Servers Detected,4-26     Upgrade,5-245           Touch,13-13                       UPS,13-10n8           Touch Technologies,vi             UPShot,13-10=           TOY Clock,4-5,  4-7               USB,14-62,  14-66 =           TPAMAC.REQ,10-15                  USB Keydisk,14-10 :           Trailing Edge,13-27               Used Equipment:           Tripp-Lite,13-10                    See HP Renew6           TrueType,11-19                    User Group7           TS10,13-27                          DECUS,1-9,;           TSM,13-12                           Encompass,1-999           TT2$M_DISCONNECT,5-63               Interex,1-9 I           TTF,11-19                         user-written system services, 2           TTY_DEFCHAR2,5-63                    5-14           TV,13-25                          UT0,4-304           TZ Logical Name,4-21              UT1,4-304           ______________________________    UT2,4-30;           U                                 UTC,4-17,  4-30 F           ______________________________    UTC$CONFIGURE_TDF.COM,4-16G           15 U.S.C 260a(a),4-22             UTC$TIMEZONE_SETUP.COM,4-162D           U.S. Design,9-11                  UTC$TIME_SETUP.COM,4-16,E           UAFALTERNATE,5-10                    4-17, 4-21, 4-22, 4-2379           UAFALTERNATE system parameter     uudecode,13-2-A              ,5-9                           uuencode,13-2,  13-16 ;           UCB,10-9                          UWSS,5-1,  10-95J           UCX$CONFIGURATION.DAT,5-13        ______________________________-           UCX$NFS_TIME_DIFFERENTIAL         V J              Logical Name,4-23              ______________________________=           UCX$TDF Logical Name,4-22         Vajhj, Arne,13-2 6           UDDI,2-8                          VAKSAT,7-2/           UEFI,14-33                        VAXB=           Ultrium 230,14-56                   Terminology,2-4l3           undelete,9-1                      VAX/VMS   =           Unified EFI                         Terminology,2-4e<             See UEFI                        VAX-11/782,14-158           Unified Extensible Firmware       VAXBACK,5-21F              Interface                      VAXcluster Console System,4             See UEFI                           14-21  J                                                                   Index-21 e  2                              Index        D           VAXCLUSTER system parameter,      VMS$TAPE_CL_DRIVER,15-13@              15-26                          VMS$VAXCLUSTER,15-13:           VAXCRTL.EXE,10-26                 VMS73_XFC,9-16:           VAX Emulator,13-27,  14-34        VMSINSTAL,5-45<           VAXstation 3100                   VMSINSTAL Update8             Console,9-4                       See Update;             Owner's Guide,14-41             VMSLICENSE,5-121A             System Disk Capacity,9-4        VMSMAIL_PROFILE,15-25-8           VAXstation 3520                   vmstar,13-16:             Service Guide,14-41             VMS_FLAGS,14-9E           VAXstation 3540                   VMS_LOADER.EFI,5-8,  14-9 ?             Service Guide,14-41             _VMS_V6_SOURCE,4-17lF           VCC_FLAGS,9-16                    Vols in Full XFC mode,9-16:           VCS,14-21                         Volume Set,9-7B           Veracity,5-4                      Volume Shadowing,15-27D           Version Numbering,10-27             Allocation Class,15-27<             Edit,10-27                        Full Copy,5-65=             Maintenance,10-27                 Full Merge,5-65 ;             Major,10-27                       Minicopy,5-64 <             Minor,10-27                       Minimerge,5-64H           Versions,5-66                     VOTES system parameter,15-17  C           Very Long Instruction Word        vPars,4-27,  14-2, 14-8   7             See VLIW                        VR260,14-46 7           VEST,13-19,  13-25                VR290,14-46_7           VFC,9-16                          VRC16,14-47 7           VGA,14-46,  14-67                 VRC21,14-47 7           vi,13-17                          VSXXX,14-464I           vile,13-17                        VTstar terminal emulator,11-4 4           vim,13-17                         VXT,11-3J           VIOC,9-16                         ______________________________-           VIOC Compatable Mode,9-16         W-J           Virtual Circuit,15-13             ______________________________8           Virtual Partitioning,14-8         w32time,4-31>           Virtual Terminal,5-63             Web Archives,14-507           VLIW,14-33                        Web Browsere  5           VMB,14-12                           See SWBa7           VMove,7-2                           CSWB,13-417           VMS$AUDIT_SERVER,15-25              Lynx,13-5p9           VMS$CLASS_SCHEDULE,15-25            Mosaic,13-41B           VMS$DISK_CL_DRIVER,15-13            Mozilla,13-4,  13-19;           VMS$OBJECTS,15-25                   Netscape,13-4 F           VMS$PASSWORD_HISTORY,15-25          Netscape Navigator,13-20#           VMS$PASSWORD_POLICY,15-25i                      Index-22                                    Index        ?           Web server                        XtAppAddInput,11-12e3             Apache,13-9                     xv,11-8_:             OSU,13-9                        X Windows,11-1C             Purveyor,13-9                   X Windows Terminal,11-3_J             WASD,13-9                       ______________________________-           Webserver,13-3                    Y4J           Web Server,13-16                  ______________________________4           Western Kentucky University,      Y2K,5-416              13-2                           yacc,13-168           WINDOW_SYSTEM                     Yamhill,2-14:             system parameter,11-5,          Year 2000,5-41J                11-14                        ______________________________-           WINDOW_SYSTEM system parameter    Z J              ,5-9                           ______________________________3           Wiring,14-61                      ZAP,7-4 D           WIZARD.ZIP,3-13                   zic compiler,4-19,  4-20@           WKU,13-2                          Zimmerman, Phil,13-5<           Wolf3D,13-16                      zip,9-17,  13-26=           WRITEBOOT,9-14                    Zip,14-56,  14-57   ?           WRITEBOOT.EXE,14-20                 Also see Info-Zip C           Write History Logging,5-64          Self-extracting,13-26$7           WRITESYSPARAMS system             ZMODEM,13-3                 parameter,5-9           WSDRIVER,11-3            WWW,13-4           www.archive.org,14-50f(           ______________________________           X (           ______________________________           X11,11-18            X11R5,11-18,           X11R6.6,11-18g           XDR,10-18            XFC,9-16           XLNperformance,5-40E           XLNsystems,5-40I            XML,2-8,  10-18, 13-11           XOFF,14-63           XON,14-63            XOR,5-45           XP1000,14-49           XPDF,3-1,  13-7            xpm,11-8  J                                                                   Index-23