OpenVMS Frequently Asked Questions (FAQ), Part 1/9

OpenVMS Frequently Asked Questions (FAQ), Part 1/9

Post by Hoff Hoffm » Sat, 05 Jul 2003 02:09:19

                   The OpenVMS Frequently Asked Questions(FAQ)


                   This document contains answers to many common questions
                   on the OpenVMS operating system, and covers OpenVMS,
                   and OpenVMS running on Itanium, Alpha, and VAX

                   Revision/Update Information   OpenVMS V7.3-1

                   Revision/Update Information:  Revision Date/June 2003




                PREFACE                                                  i

                OPENVMS FAQ                                            iii

          CHAPTER 1  INTRODUCTION                                      1-1

                1.1   WHAT CORE OPENVMS URLS DO YOU NEED TO KNOW?      1-1

                1.2   WHAT ARE THE OPENVMS USENET NEWSGROUPS?          1-2
                1.2.1     What is the scope of the comp.os.vms
                          newsgroup?                                   1-2
                1.2.2     What newsgroups carry VMS-related
                          information?                                 1-2
                1.2.3     What newsgroup archives are available?       1-3
                1.2.4     What is the INFO-VAX mailing list?           1-3
            How do I subscribe to or unsubscribe from
                             INFO-VAX?, 1-4

                1.3   WHAT IS [N]ETIQUETTE?                            1-5

                1.4   WHAT OPENVMS USER GROUP(S) ARE AVAILABLE?        1-8

                1.5   OPENVMS SUPPORT, QUESTIONS AND COMMENTS?         1-9
                1.5.1     Corporate contacts for OpenVMS Business
                          Issues?                                      1-9
                1.5.2     OpenVMS Ambassadors?                        1-10
                1.5.3     Contact for OpenVMS Marketing Issues and
                          Questions?                                  1-10
                1.5.4     Contact URLs for OpenVMS Technical
                          Issues?                                     1-10



          CHAPTER 2  GENERAL INFORMATION                               2-1

                2.1   WHAT IS OPENVMS? WHAT IS ITS HISTORY?            2-1

                      OPENVMS?                                         2-2
                2.2.1     How do I port from VMS to OpenVMS?           2-3

                2.3   WHICH IS BETTER, OPENVMS OR UNIX?                2-3

                      OPENVMS?                                         2-4

                      AVAILABLE?                                       2-4

                2.6   IN WHAT LANGUAGE IS OPENVMS WRITTEN?             2-6

                2.7.1     Questions asked by Hobbyist OpenVMS
                          licensees?                                   2-7
                2.7.2     OpenVMS Educational and CSLG licenses?       2-8
                2.7.3     How do I obtain or transfer an OpenVMS
                          license?                                     2-8

                      SYMBOL?                                          2-8

                2.9   WHY HASN'T OPENVMS BEEN PORTED TO INTEL (IA-32)
                      SYSTEMS?                                         2-9

                      SYSTEMS?                                         2-9

                2.11  WHAT VERSION OF OPENVMS DO I NEED?              2-10



                2.12  HOW CAN I SUBMIT OPENVMS FREEWARE?              2-11

                2.13  PORTING APPLICATIONS TO OPENVMS?                2-12

                      DEVELOPERS?                                     2-13

                      SCHEDULING, ETC?                                2-14

          CHAPTER 3  DOCUMENTATION                                     3-1

                      MANUALS?                                         3-1

                      AVAILABLE?                                       3-1

                      NUMBERS?                                         3-5

                      TEXT FILE?                                       3-6

                      ADDRESS?                                         3-6

                      INTERNALS?                                       3-6

                      OPENVMS?                                         3-7
                3.7.1     Tutorial Websites?                           3-7
                3.7.2     Books and Tutorials?                         3-9



                3.8   WHAT OPENVMS MAILING LISTS ARE AVAILABLE?       3-10

                      ABOUT?                                          3-12

                      DOCUMENTATION?                                  3-13

          CHAPTER 4  TIME AND TIMEKEEPING                              4-1

                4.1   UTC VS GMT VS VS UT1/UT1/UT2 TDF? WHAT ARE THESE
                      ACRONYMS?                                        4-1

                      PLEASE?                                          4-2
                4.2.1     Details of the OpenVMS system
                          time-keeping?                                4-4
            VAX hardware time-keeping details..., 4-4
           TOY clock, 4-4
           EXE$GQ_SYSTIME, 4-4
           EXE$GQ_TODCBASE, 4-4
           EXE$GL_TODR, 4-4
            Alpha hardware time-keeping

read more »


OpenVMS Frequently Asked Questions (FAQ), Part 1/9

Post by Hoff Hoffm » Sat, 05 Jul 2003 02:11:00

                   General Information

                   standards such as POSIX, which provides many features
                   of UNIX systems.

                   For those versions with POSIX, an OpenVMS license
                   allows you to install and run POSIX for OpenVMS at
                   no additional charge; all you need is the media and
                   documentation which can be found on the Consolidated
                   Distribution and On-Line Documentation CD-ROMs. Support
                   for the POSIX package on more recent OpenVMS releases
                   is not available, various parts of POSIX such as calls
                   from the API are being integrated more directly into
                   OpenVMS. For more information on POSIX for VMS see
                   question SOFT2

                   What became confusing is that the OpenVMS name was
                   introduced first for OpenVMS AXP V1.0 causing the
                   widespread misimpression that OpenVMS was for Alpha
                   AXP only, while "regular VMS" was for VAX. In fact,
                   the official name of the VAX operating system was
                   changed as of V5.5, though the name did not start to be
                   actually used in the product until V6.0.

                   The proper names for OpenVMS on the two platforms
                   are now "OpenVMS VAX" and "OpenVMS Alpha", the latter
                   having superseded "OpenVMS AXP".

          2.2.1  How do I port from VMS to OpenVMS?

                   You already did. Wasn't that easy? Please see
                   Section 2.2 for details.

          2.3  Which is better, OpenVMS or UNIX?

                   This question comes up periodically, usually asked by
                   new subscribers amd new posters who are long-time UNIX
                   or Linux users. Sometimes, the question is ignored
                   totally; other times, it leads to a long series of
                   repetitive messages that convince no one and usually
                   carry little if any new information. Please do everyone
                   a favor and avoid re-starting this perpetual, fruitless


                   General Information

                   That said, OpenVMS and the better implementations of
                   UNIX are all fine operating systems, each with its
                   strengths and weaknesses. If you're in a position where
                   you need to choose, select the one that best fits your
                   own requirements, considering, for example, whether or
                   not the layered products or specific OS features you
                   want are available.

          2.4  Is HP continuing funding and support for OpenVMS?


                   Active development of new OpenVMS releases is underway,
                   as well as the continuation of support.

                   Please see the following URLs for details, roadmaps,
                   and related information:






          2.5  What OpenVMS CD-ROM distribution kits are available?

                   Various distributions are available.

                   For information on the available part numbers
                   and current products (OpenVMS distribution kits,
                   media, documentation, etc) and associated licensing
                   information, please see the OpenVMS Software Product
                   Description (SPD), available at:

                      OpenVMS typically uses SPD 25.01.xx and/or SPD


                   General Information

                   The CD-ROMs listed in Table 2-1 contain just the
                   OpenVMS Alpha operating system. These are bootable,
                   and can be used to run BACKUP from CD-ROM.

          Table 2-1  OpenVMS Media Kits


                   QA-MT1AP-H8       OpenVMS Alpha V6.1-1H2 hardware
                                     release CD-ROM

                   QA-MT1AG-H8       OpenVMS Alpha V6.2-1H3 hardware
                                     release CD-ROM

                   QA-MT1AD-H8       OpenVMS Alpha V7.1-1H1 hardware
                                     release CD-ROM

                   QA-MT1AR-H8       OpenVMS Alpha V7.1-2 maintenance
                                     release CD-ROM

                   QA-MT1AT-H8       OpenVMS Alpha V7.2-1 maintenance
                                     release CD-ROM

                   QA-MT1AU-H8       OpenVMS Alpha V7.2-1H1 hardware

                   The table Table 2-2 contains the consolidated ECO
                   distribution kit subscriptions, and these provide sites
                   with eight updates of the current ECO kits per year:

          Table 2-2  OpenVMS ECO Kits


                   QT-3CQAA-C8       OpenVMS Alpha


                   The OpenVMS VAX and OpenVMS Alpha source listings
                   CD-ROM sets listed in Table 2-3 include the source
                   listings of most of OpenVMS, and these CD-ROM sets
                   are invaluable for any folks working directly with
                   OpenVMS internals, as well as folks interested in
                   seeing examples of various programming interfaces.


                   General Information

          Table 2-3  OpenVMS Source Listings CD-ROM Kits


                   QB-MT1AB-E8       OpenVMS Alpha Source Listings CD-ROM

                   QT-MT1AB-Q8       OpenVMS Alpha Source Listings CD-ROM

                   QB-001AB-E8       OpenVMS VAX Source Listings CD-ROM

                   QT-001AB-Q8       OpenVMS VAX Source Listings CD-ROM

          2.6  In what language is OpenVMS written?

                   OpenVMS is written in a wide variety of languages.

                   In no particular order, OpenVMS components are
                   implemented using Bliss, Macro, Ada, PLI, VAX and DEC
                   C, Fortran, UIL, VAX and Alpha SDL, Pascal, MDL, DEC
                   C++, DCL, Message, and Document. And this is certainly
                   not a complete list. However, the rumor is NOT true
                   that an attempt was made to write pieces of OpenVMS in
                   every supported language so that the Run-Time Libraries
                   could not be unbundled. (APL, BASIC, COBOL and RPG are
                   just some of the languages NOT represented!)

                   There are a large variety of small and not-so-small
                   tools and DCL command procedures that are used as part
                   of the OpenVMS build, and a source code control system
                   capable of maintaining over a hundred thousand source
                   files across multiple parallel development projects,
                   and overlapping releases.

          2.7  Obtaining and Transfering OpenVMS licensees?

                   The following sections describe hobbyist and
                   educational license programs, as well as information on
                   commercial licenses and transfers.

                   For information on the available commercial OpenVMS
                   licenses and for information on license transfers,
                   please see Section 2.7.3. For information on the
                   licensing implementation, troubleshooting licensing


                   General Information

                   problems, on the License Unit Requirements Table
                   (LURT), and other related details, please see
                   Section 5.38.

          2.7.1  Questions asked by Hobbyist OpenVMS licensees?

                   If you are a member of an HP-recognized user group
                   (eg: Encompass, Enterex, DECUS), and are considering
                   acquiring and using a VAX or Alpha system

read more »


OpenVMS Frequently Asked Questions (FAQ), Part 1/9

Post by Hoff Hoffm » Sat, 05 Jul 2003 02:12:10

                   Time and Timekeeping

          4.4  Managing Timezones, Timekeeping, UTC, and Daylight Savings?

                   You will want to use the command procedure:

                   o  SYS$MANAGER:UTC$TIME_SETUP.COM

                   to configure the OpenVMS Timezone Differential Factor
                   (TDF) on OpenVMS V6.0 and later. Select the BOTH
                   option. This configures the OpenVMS TDF settings,
                   though it may or may not configure the TDF and the
                   timezone rules needed or used by other software
                   packages. Please do NOT directly invoke the following
                   command procedures:

                   o  SYS$MANAGER:UTC$CONFIGURE_TDF.COM ! do not directly

                   o  SYS$MANAGER:UTC$TIMEZONE_SETUP.COM ! do not directly

                   TCP/IP Services V5.0 and later use the OpenVMS TDF,
                   UTC, and timezone support. Earlier versions use a TDF
                   mechanism and timezone database that is internal to the
                   TCP/IP Services package. Also on the earlier versions,
                   the TDF must be manually configured within TCP/IP
                   Services, in addition to the OpenVMS configuration
                   of the TDF.

                   DECnet-Plus in V7.3 and later uses the OpenVMS TDF,
                   UTC, and timezone support, and displays its timezone
                   prompts using UTC$TIME_SETUP.COM. Earlier versions use
                   a TDF TDF mechanism, timezone database, and automatic
                   switch-over that is internal to the DECnet-Plus
                   package. Also on earlier versions, the TDF must be
                   configured within the DECnet-Plus DECdtss package, in
                   addition to the OpenVMS configuration of the TDF.

                   Application code using HP C (formerly Compaq C,
                   formerly DEC C) will use the OpenVMS UTC and TDF
                   mechanisms when the C code is compiled on OpenVMS V7.0
                   and later (and when the macro _VMS_V6_SOURCE is NOT
                   defined). HP C does NOT use the OpenVMS UTC and TDF
                   mechanisms when the C code is compiled on OpenVMS
                   releases prior to V7.0, or when the preprocessor
                   declaration _VMS_V6_SOURCE is declared.


                   Time and Timekeeping

                   DCE DTSS TDF details TDB.

                   In OpenVMS Alpha V6.1, V6.2, and V6.2-1Hx, the TDF
                   value is written to SYS$BASE_IMAGE.EXE. With OpenVMS
                   Alpha V7.0 and later and with OpenVMS VAX V6.0 and
                   later, SYS$SYSTEM:SYS$TIMEZONE.DAT contains the TDF.
                   This means that OpenVMS Alpha systems will need to have
                   the TDF value reset manually-usually within SYSTARTUP_
                   VMS.COM-on reboots prior to V7.0.

                   During OpenVMS Bootstrap, the SYSINIT module reads
                   SYS$TIMEZONE.DAT to acquire the TDF for use in the
                   system global cell EXE$GQ_TDF. This is done to ensure
                   that the system boots with a valid TDF (a value which
                   may be zero). The UTC system services get the TDF
                   from this cell. These services, as well as the HP C
                   RTL, must have a valid TDF. (Prior to OpenVMS V7.3,
                   if either DECnet-Plus or DECnet/VAX Extensions is
                   configured and run, the image DTSS$SET_TIMEZONE.EXE
                   is invoked and can override the TDF and timezone rule
                   settings from SYSINIT or from UTC$TIME_SETUP.COM-
                   this image runs even if DTSS is disabled. If the
                   settings do not match (due to inconsistencies in
                   timezone specification in UTC$TIME_SETUP.COM and
                   NET$CONFIGURE.COM), DTSS will reset the values to match
                   its definitions.)

                   Prior to OpenVMS V7.3, daylight savings time switchover
                   is handled automatically only when DCE DTSS or DECnet-
                   Plus DTSS is in use. In V7.3, OpenVMS can be configured
                   to automatically switch over to daylight savings
                   time, and also generates an event that interested
                   applications can use to detect the switch-over between
                   standard time and daylight time.

                   The manual switchover between daylight savings time
                   and standard time is correctly accomplished via the
                   SYS$EXAMPLES:DAYLIGHT_SAVINGS.COM command procedure

                   Note: NTP (alone) does NOT provide automatic switch-

                   Note: The DST switch-over does NOT drift the time
                   value; the switch-over applies the entire difference as
                   a unit.


                   Time and Timekeeping

                   If you switch the TDF or daylight savings time setting,
                   you will also want to restart or reconfigure any time-
                   sensitive applications (those not using the time
                   differential factor (TDF) change event available in
                   V7.3 and later). Examples of these applications include
                   the need to restart the NFS client and (yes) NTP. (NTP
                   will want to try to "drift" the time (see Section 4.3),
                   and will find the daylight savings time switch-over to
                   be far too large to "drift". Hence the NTP restart.)
                   You can also use the (undocumented) TCP/IP Services
                   (prior to V5.0) commands:

                   SET TIME/DIFF=[positive or negative TDF integer]
                   GENERATE TIME

                   to reset the value of the logical name UCX$TDF.

                   Prior to V7.3, the command:

                   $ SETTZ :== $SYS$SYSTEM:DTSS$SET_TIMEZONE
                   $ SETTZ MODIFY

                   can be used to modify the settings of the SYS$TIMEZONE_
                   SYS$TIMEZONE_NAME system logical names based on the

                   The following are other TDF-related logical names
                   used/available on OpenVMS systems, with typical
                   Daylight Savings and Standard Settings for the US
                   Eastern Time (ET) timezone.

                   $ DEFINE/SYSTEM/EXECUTIVE LISP$TIME_ZONE 05   ! Constant
                   $ DEFINE/SYSTEM/EXECUTIVE LISP$TIME_ZONE 05   ! Constant
                       'f$integer(f$element(0," ",f$logical("notes$timezone"))/-100)'


                   Time and Timekeeping

                   For information on ZIC and related tools used to manage
                   the OpenVMS Timezone database, please see the DEC C
                   Run-time Library Utilities Reference Manual-though the
                   title would imply otherwise, this particular manual
                   is part of the OpenVMS documentation set, and not
                   part of the HP C (formerly Compaq C, formerly DEC C)
                   documentation set.

          4.4.1  How to troubleshoot TDF problems on OpenVMS?

                   This is an OpenVMS Alpha system prior to V7.0 and the
                   startup is not invoking the procedure:


                   This is an OpenVMS system prior to V6.0, where there is
                   no OpenVMS TDF nor UTC available.

                   The version of the application does not use the OpenVMS
                   TDF. This includes TCP/IP Services prior to V5.0,
                   applications using HP C built on or targeting OpenVMS
                   prior to V7.0, and systems using the DECnet-Plus DTSS
                   mechanisms prior to the release associated with OpenVMS
                   V7.3. (DCE TDF TBD.)

                   If you should find either of the following two
                   timezone-related database files located in



                   These two files are in an erroneous location and must
                   be recreated in the correct directory:


                   If the DCL command:


                   shows these files in SYS$SPECIFIC:[SYSEXE], then delete
                   them and use SYS$MANAGER:UTC$TIME_SETUP.COM to

read more »


OpenVMS Frequently Asked Questions (FAQ), Part 1/9

Post by Hoff Hoffm » Sat, 05 Jul 2003 02:13:08

                   System Management Information

          5.24  INITIALIZE ACCVIO and ANSI tape label support?

                   A change was made (back in 1988) to (as it was then
                   known) VAX/VMS V5.1-1 that added support for the then-
                   new ANSI X3.27-1987 magnetic tape label standard. Prior
                   to the ANSI X3.27-1987 standard, the date field in the
                   ANSI HDR1 record permits dates only as far as the end
                   of Year 1999. With ANSI X3.27-1987, dates through Year
                   1999 and dates from Years 2000 to 2099 are permitted.

                   Versions of INIT.EXE and MTAACP.EXE from VAX/VMS
                   releases prior to V5.1-1 will potentially have problems
                   properly processing ANSI magnetic tapes when Y2K and
                   later dates are involved-the DCL INITIALIZE command is
                   known to encounter access violation (ACCVIO) errors.

                   The available solutions include upgrades, or setting
                   the date back. Direct initialization of the tape with
                   the new headers (via $qio) is also clearly possible,
                   though the limitation within the old MTAACP.EXE magtape
                   ACP image is not nearly so easy to bypass.

          5.25  How do I recover from INSVIRMEM errors?

                   Prior to OpenVMS Alpha V7.0 and on all OpenVMS VAX
                   releases, VIRTUALPAGECNT and PGFLQUOTA limit the amount
                   of virtual address space that is available to each

                   Further limiting the amount of address space is the
                   size of system space (S0 and S1 space). On OpenVMS
                   Alpha versions prior to V7.0 and on all OpenVMS VAX
                   releases, VIRTUALPAGECNT and MAXPROCESSCNT together
                   determine the size of the page table data structures
                   that occupy large tracts of system space. When no
                   system virtual address space is available for the stuff
                   that needs it-this includes the page tables, non-paged
                   pool, and various other structures-then the values of
                   VIRTUALPAGECNT and MAXPROCESSCNT cannot be increased.

                   In OpenVMS Alpha V7.0 and later, the page table data
                   structures have been moved out of S0 and S1 space and
                   into page table space. In OpenVMS Alpha V7.2 and later,
                   certain large data structures found in non-paged pool
                   (eg: lock management structures) have been moved into


                   System Management Information

                   64-bit space, thus freeing up room in non-paged pool
                   and in S0 and S1 space (where non-paged pool resides)
                   while also permitting much larger data structures.

          5.26  How can I prevent a serial terminal line from initiating a

                   In SYSTARTUP_VMS.COM, issue the command:


                   This will prevent any unsolicited terminal input on
                   ddcu:, and this unsolicited input is what triggers
                   JOB_CONTROL to start up LOGINOUT on the terminal. Once
                   LOGINOUT starts up on the serial line, you can see
                   interesting behaviour (eg: audits, process creations,
                   etc) as LOGINOUT tries to "chat" with whatever device
                   is hooked onto the remote end of the serial terminal

          5.27  How does PCSI use the image BUILD_IDENT field?

                   The (undocumented) build ident field in an OpenVMS
                   Alpha image header is 16 bytes long, and is used as
                   a counted string of 0-15 characters (ie, as an .ASCIC
                   string, a string with the character count in byte 0)
                   and was originally introduced to provide information
                   for use by VMSINSTAL patch kits to determine whether an
                   image should be replaced or not.

                   Starting with OpenVMS Alpha V7.1-2, OpenVMS Engineering
                   uses the PCSI utility to package and install ECO kits
                   for OpenVMS. PCSI uses the generation attribute (a
                   32-bit unsigned integer) specified for files in the
                   product description file (PDF) of a PCSI kit as the
                   basis for performing file conflict detection and
                   resolution. When a product is installed, PCSI modifies
                   the build ident field of Alpha image headers to store
                   an encoded form of the generation number. It also looks
                   at the build ident field of previously installed images
                   to obtain the generation information for those files as
                   input to the file conflict processing algorithm. (Only
                   images have this field, obviously.)


                   System Management Information

                   PCSI interprets the build ident field of a previously
                   installed image as follows:

                   o  if the string length is 15, the 5th character is
                      a hyphen, and the last ten characters are a ten
                      digit number with leading zeros, then the last ten
                      characters are treated as a valid generation number.

                   o  for V7.1-2 through V7.2-1, inclusive, if the above
                      test fails, the information is obtained from the
                      PCSI product database.

                   o  in releases after V7.2-1 and with current PCSI ECO
                      kits, if the above test fails, an invalid generation
                      number is treated as 0000000000 so that the ECO kit
                      will simply replace the image rather than assuming
                      the PCSI database is in error.

                   So, what will you see in the image identification
                   displayed via the ANALYZE/IMAGE command?

                   For an image that has been built as part of an OpenVMS
                   Engineering system build, you will generally see a
                   build ID string in the format "X6TE-SSB-0000"-X6TE is
                   the build number for the OpenVMS Alpha V7.2-1 release.
                   This id format is used within the OpenVMS system build,
                   and can generally only be seen associated with images
                   that have not yet been processed via PCSI.

                   During the installation of V7.2-1, PCSI will modify
                   the image header to have a build ident string of
                   "X6TE-0050120000". During installation of an ECO
                   kit containing this image with a generation number
                   of 50130052, for example, PCSI would determine that
                   50130052 is greater than 50120000, and will replace the
                   existing image on the target disk with the version of
                   the image included in the ECO kit.


                   System Management Information

          5.28  How can I tell what software (and version) is installed?

                   There is unfortunately no consistent nor single way to
                   make this determination-this is one of the reasons that
                   a move to PCSI installations is underway.

                   On OpenVMS Alpha, you can use VMSINSTAL.HISTORY and
                   PRODUCT SHOW PRODUCT to determine what packages have
                   been installed via the VMSINSTAL and PCSI tools,

                   To see which OpenVMS Alpha ECO kits have been applied,
                   look in VMSINSTAL.HISTORY on OpenVMS Alpha prior to
                   V7.1-2, and use PRODUCT SHOW PRODUCT/FULL on OpenVMS
                   Alpha V7.1-2 and later.

                   On OpenVMS VAX, you can use PRODUCT SHOW PRODUCT and
                   (for software that is installed via VMSINSTAL on V7.3
                   and later) in VMSINSTAL.HISTORY.

                   For products installed on OpenVMS VAX prior to V7.3
                   using VMSINSTAL, there is no reliable way to determine
                   what products have been installed. If the product
                   provides a RELEASE_NOTES file (as many do), you
                   can look for the list of these files via DIRECTORY
                   SYS$HELP:*.RELEASE_NOTES. Again, this approach is NOT
                   reliable: some kits do not provide release notes, some
                   system managers will install only the release notes,
                   some system managers will delete release notes, and
                   release notes for multiple versions can be present.

                   On most packages, you can generally use ANALYZE/IMAGE
                   on one of the core images, looking at the image
                   identification area. Some of the product-specific
                   mechanisms available are:

read more »


OpenVMS Frequently Asked Questions (FAQ), Part 1/9

Post by Hoff Hoffm » Sat, 05 Jul 2003 02:14:04


                   NOTE: All ATA-related disk sizes listed in this section
                   are stated in units of "disk (base ten) gigabytes" (1
                   GB = 10^9 bytes) and NOT in units of "software (base
                   two) gigabytes" (1 GB = 2^30 (1073741824.) bytes. See
                   Section 14.26.

                   Be aware that larger disks that are using an extension
                   of SCSI-2- disks that are using a mode page field
                   that the SCSI-2 specifications normally reserved for
                   tape devices-to permit a larger disk volume size will
                   require a SCSI driver update for OpenVMS, and this
                   change is part of V7.1-2 and later, and also part of
                   ALPSCSI07_062 and later. (These larger disks disks
                   will typically report a DRVERR, or will see the volume
                   size "rounded down".) SCSI disks larger than 16777216
                   blocks cira 8.455 GB (base ten); 8GB (base two) require
                   this ECO, or require the use of OpenVMS Alpha V7.1-2 or

                   Applications written in C can be limited to file
                   sizes of two gigabytes and less, as a result of the
                   use of longword values within C file operations, and
                   specifically off_t. This restriction is lifted in
                   OpenVMS V7.3-1 and later, and with the application of
                   the C ECO kits available for specific earlier releases.
                   The use of a longword for off_t restricts applications
                   using native C I/O to file sizes of two gigabytes or
                   less, or these applications must use native RMS or XQP
                   calls for specific operations.

                   Also see Section 14.14, Section 14.26.

          9.6  What is the maximum file size, and the RMS record size

                   RMS can store individual files of a size up to the
                   maximum supported volume size. Under OpenVMS V6.0 and
                   later, the volume size and the RMS maximum file size
                   limit is 2**31 * 512 bytes-one terabyte (1 TB).

                   "Use a volume set to provide a large, homogeneous
                   public file space. You must use a volume set to create
                   files that are larger than a single physical disk
                   volume. (The file system attempts to balance the load



                   on the volume sets, for example, by creating new files
                   on the volume that is the least full at the time.)"

                   "You can add volumes to an existing volume set at any
                   time. The maximum number of volumes in a volume set is

                   The RMS formats-sequential, relative, and indexed-
                   are limited by the one terabyte maximum volume size.
                   RMS relative files are further limited to a number of
                   records that will fit in 32 bits-4 billion records.
                   Sequential and indexed formats do not have a record

                   Also see Section 10.14, Section 14.26.

          9.7  How do I write CD-Recordable or DVD media on OpenVMS?

                   How to create CD-R, CD-RW, DVD-R, DVD+R, DVD-RW, or
                   DVD+RW media on OpenVMS?

                   o  Acquire a comparatively recent SCSI-based or ATA
                      (IDE) CD-R or DVD-R/RW or DVD+R/RW drive. Older
                      drives can be problematic, while newer drives are
                      readily available, cheap and very fast.

                   o  Get LDDRIVER from the Freeware. Versions of LDDRIVER
                      are latent in OpenVMS Alpha V7.3-1 and later. (Look
                      within SYS$MANAGER:CDRECORD.COM for details.)

                   o  Get CDRECORD or CDWRITE or other similar recording
                      tool. (CDRECORD and CDWRITE are freely available,
                      though versions are not on the Freeware V5.0
                      distribition; the URLs are referenced later in this
                      section). Versions of CDRECORD are latent in OpenVMS
                      Alpha V7.3-1 and later.

                   o  Build the contents of the disk on the LD device

                   o  Use the CDRECORD or CDWRITE or other tool to record
                      the contents of the LD partition directly onto the
                      CD-R or CD-RW media.



                   Alternatively, consider the following command on
                   OpenVMS Alpha V7.3-1 and later:


                   While folks have had success getting PC-based CD-R/RW
                   or DVD-R/RW or DVD+R/RW tools to work with OpenVMS
                   partitions, it is far easier and more reliable to use
                   the OpenVMS-based versions of these tools and directly-
                   attached devices.

                   More details: Creation of CD recordable or DVD
                   recordable media under OpenVMS typically involves
                   one of two approaches: the use of the optional CD-R
                   (`Scribe') capabilities available for the InfoServer or
                   other "offline" hardware packages (PC-based packages
                   will be included in this), or the use of a host-based
                   package such as the CDRECORD or CDWRITE13_VMS or other
                   utilities, OpenVMS ports of common open-source tools
                   made available by Dr. Eberhard Heuser-Hofmann and

                   OpenVMS can read ODS-2, ODS-5, and ISO-9960 format
                   CD-ROMs. (If you are very careful, you can create a
                   dual-format CD-R; a CD-R with both ODS-2 and ISO-9660
                   or both ODS-5 and ISO-9660 or both.)

                   InfoServer hardware configurations are no longer
                   available from HP, but may potentially be acquired
                   through other means; as used equipment.


                   Additional information is available at the following








                   U.S. Design offers a package that includes the tools
                   necessary to create a CD or DVD-R with either ISO-9660
                   or ODS-2 format, for standalone CD-R/RW, DVD-R, or
                   DVD+R/RW drives, for recent OpenVMS versions. Details
                   are available at:


          9.7.1  CD and DVD notation, terminology?

                   CD-ROM is pre-recorded Compact Disk media, and is
                   the original and oldest CD format. The original CD
                   media was physically stamped, a recording process that
                   is now largely reserved to the highest-volume media
                   reproduction requirements.

                   CD-R is CD Recordable, a write-once storage medium
                   that can be read by all but the oldest of CD drives;
                   a format which can be read and often even recorded by
                   most CD-RW drives.

                   CD-RW is CD ReWritable, a format which is readable by
                   many CD drives and by most CD-R drives, and with media
                   that can be recorded and re-recorded by CD-RW drives.

                   CD media recording speeds are listed as multiples of
                   150 kilobytes per second, so a 10X drive records at
                   1500 kilobytes (1.5 megabytes) per second. 600 MB (70
                   minutes) and 700 MB (80 minutes) recording capacities
                   are both widely available. The minutes designation is
                   derived from the traditional audio-format recording
                   capacity of the particular media.

                   DVD-R/RW is the older of two common Digital Versatile
                   Disk recording formats, and the DVD-R Recordable or
                   DVD-RW ReWritable media can be read by many DVD drives.
                   As with CD-R formats in older CD drives, older DVD
                   and particularly first-generation DVD players may have
                   problems reading this media format.

                   DVD+R/RW is the newer of the two common Digital
                   Versatile Disk recording formats, and the DVD+R
                   Recordable or DVD+RW ReWritable media can be read
                   by many DVD drives. Akin to DVD-R/RW media, older



                   and particularly first-generation DVD drives can have
                   problems reading this media format.

read more »


OpenVMS Frequently Asked Questions (FAQ), Part 1/9

Post by Hoff Hoffm » Sat, 05 Jul 2003 02:15:07


                   o  The system parameter WINDOW_SYSTEM is not set to
                      1. While this was a common way for system managers
                      to disable the DECwindows server startup, it is
                      not particularly reliable as DECwindows can now
                      "correct" this setting.

                      If you really do not want an OpenVMS system with
                      workstation hardware to bootstrap and configure
                      itself as a workstation, add the following
                      definition to SYLOGICALS.COM:


                   o  You may not have a valid DECwindows Motif license
                      loaded. To check for the two most common types of
                      Motif product authorization keys (PAKs), use the
                      following DCL commands:

                      $ LICENSE LIST DW-MOTIF/FULL
                      $ LICENSE LIST NET-APP-SUP*/FULL

                      and examine the information displayed. Make sure
                      that one of these licenses is present, valid and

                   o  Check that the DECW$PRIVATE_SERVER_SETUP.COM is
                      correct for the graphics controller in use. For

                      The following is from the 9FX Vision 330 Owners
                      Guide, EK-V330G-OG pg 2-9. Place the following in
                      DECW$PRIVATE_SERVER_SETUP.COM, creatibng .COM from
                      .TEMPLATE if necessary. Locate the DECW$PRIVATE_
                      SERVER_SETUP.COM file in SYS$SPECIFIC:[SYSMGR] or
                      in SYS$COMMON:[SYSMGR] as appropriate; the former
                      file is used for this system within a cluster
                      configuration, and the latter is used for all
                      systems that do not also have a local copy of this
                      file in SYS$SPECIFIC:[SYSMGR].

                      $ DECW$XSIZE_IN_PIXELS == xvalue
                      $ DECW$YSIZE_IN_PIXELS == yvalue
                      $ DEFINE/SYSTEM DECW$SERVER_REFRESH_RATE rate_in_Hz

                      Also see Section 11.12. Details of the PowerStorm
                      3D30 and 4D20 settings are available in the OpenVMS
                      Ask The Wizard area.



          11.7  How do I set the title on a DECterm window?

                   If you are creating a new DECterm window, check


                   If you want to change the title of an existing window,
                   use the following control sequences, where <esc> is the
                   ANSI escape code, value decimal 27, and "text label" is
                   what you want to display:

                   To set the DECterm title, send:

                   ]21;text label<esc>\

                   To set the icon label, send:

                   ]2L;text label<esc>\

                   To set both the DECterm title and icon to the full
                   device name:

                   $  esc[0,7] = 27
                   $  fulldevnam = F$Edit(F$GetDVI("TT","FULLDEVNAM"),"UPCASE,COLLAPSE")
                   $  write sys$output esc+ "]21;" + fulldevnam + esc + "\"
                   $  write sys$output esc+ "]2L;" + fulldevnam + esc + "\"

                   You can also change the title and the icon using the
                   Options-Window... menu.

                   Also see Section 12.1 and Section 8.11.

          11.8  How do I customize DECwindows, including the login screen?

                   To customize various DECwindows Motif characteristics
                   including the defaults used by the SET DISPLAY command,
                   the DECwindows login screen background logo used
                   (the default is the DIGITAL, Compaq, or HP logo),
                   various keymaps, the FileView defaults, session manager
                   defaults, the DECwindows login processing, DECwindows
                   log file processing, and various other DECwindows
                   attributes, see the example file:




                   This example template file is typically copied over
                   to the filename SYS$COMMON:[SYS$STARTUP]DECW$PRIVATE_
                   APPS_SETUP.COM and then modified to meet site-specific

                   Additionally, various X tools such as xsetroot, bitmap
                   and xrdb-some these can be useful in customizing the
                   appearance of an application or of the DECwindows Motif
                   display-are provided in the DECW$UTILS: area.

                   When using DECwindows V1.2-4 and later on OpenVMS
                   Alpha, the default desktop is the Common Desktop
                   Environment (CDE). You can select your preferred
                   desktop (CDE or DECwindows Motif) when logging in,
                   or you can change the default to the DECwindows
                   Motif desktop using the DCL symbol decw$start_new_
                   desktop in the DECwindows private application setup
                   command procedure. See SYS$STARTUP:DECW$PRIVATE_APPS_
                   SETUP.TEMPLATE for further details, and how to create

                   Note that with DECwindows CDE, the root window is
                   no longer visible by default. The root window is
                   hidden behind the "backdrop" window of the current
                   CDE workspace. To make the root window visible, use the
                   CDE style manager selection "backdrop none", and use
                   information such as that in the OpenVMS FAQ to set the
                   root window.

                   To add a new backdrop to the DECwindows CDE
                   environment, the backdrop must first be in or be
                   converted into X11 pixmap format. (This conversion
                   is often possible using tools such as xv.) Then (if
                   necessary) create the default backdrop directory
                   SYS$COMMON:[CDE$DEFAULTS.USER.BACKDROPS]. Place the
                   X11 pixmap file containing the desired image into the
                   backdrops directory, ensure that it has a filename
                   extension of .PM. (The xv default filename extension
                   for the X11 pixmap file is .XPM, while CDE expects
                   only to see files with .PM.) Now invoke the CDE style
                   manager and select a new backdrop. You will find
                   your image will be placed at the end of the list of
                   backdrops available.



          11.9  Why doesn't XtAppAddInput() work on OpenVMS?

                   Yes, XtAppAddInput()  does work on OpenVMS. The MIT
                   definition of the X Windows call XtAppAddInput()
                   includes platform-specific arguments.

                   On platforms where C is the typically the primary
                   programming language for the platform, the file
                   descriptor mask is one of the arguments to the
                   XtAppAddInput()  call.

                   On OpenVMS, the platform-specific arguments to this
                   call include an event flag and an IOSB, as these are
                   the traditional OpenVMS constructs used to synchronize
                   the completion of asynchronous operations. While it
                   would be easier to port non-OpenVMS C code that calls
                   XtAppAddInput()  over to OpenVMS if the arguments
                   included the C file descriptor, this would make the
                   call unusable from other OpenVMS languages, and would
                   make it extremely difficult to use OpenVMS features
                   such as ASTs and sys$qio calls.

                   One restriction on the event flag: the event flag
                   chosen must be from event flag cluster zero. When using
                   the traditional lib$get_ef and lib$free_ef calls to
                   allocate and deallocate event flags, you must first
                   explicitly call lib$free_ef to free up some event flags
                   in event flag cluster zero. Please see the event flag
                   documentation for specific details on these calls and
                   for specific event flags that can be freed in event
                   flag cluster zero.

                   Here is some example code that covers calling this
                   routine on OpenVMS:



                       m->InputID = XtAppAddInput(
                           the_callback, 1 );
                       if ( !((int) m->InputID ))

read more »


OpenVMS Frequently Asked Questions (FAQ), Part 1/9

Post by Hoff Hoffm » Sat, 05 Jul 2003 02:16:10

                   Finding and using Software

          13.12  Where can I get Zip, Unzip, self-extracting zip, etc?

                   Many packages are provided in ZIP, GZIP, or BZIP2
                   format, which requires you to acquire the associated
                   unzip tool to unpack it. You can get ZIP and UNZIP and
                   related and similar tools from the following areas:










                   or you can request the FILESERV_TOOLS package from the
                   e-mail server.

                   Beware: The [000TOOLS...] pre-built
                   versions of ZIP on the OpenVMS Freeware V4
                   CD-ROM will erroneously return BILF errors on OpenVMS
                   V7.2 and later. Use of the source on the Freeware V4
                   to rebuild the ZIP image(s), or acquiring a pre-built
                   ZIP image from one of the above areas can avoid this.
                   The pre-built version of ZIP on the Freeware V4 kit is
                   older than the included ZIP sources, and it contains a
                   latent bug.]

                   Directions for creaating and using the sfx self-
                   extracting zip file compression mechanism are available
                   in the unzip kit that is available at:





                   Finding and using Software

                   If you want to build the zip images for yourself (eg:
                   for an older OpenVMS version), pull over the entire
                   contents of:


                   and invoke LINK.COM.

                   HP OpenVMS Engineering uses a tool known as FTSV
                   for creating self-extracting compressed files using
                   the OpenVMS DCX compression tools, as seen with
                   various OpenVMS ECO (patch) kits. sfx provides better
                   compression than does DCX. The FTSV and its related
                   FTSO package have only limited availability outside HP,
                   and are not standard products.

          13.13  Are VAX Hardware Emulators Available?

                   Software-based emulators of the VAX architecture and
                   for specific VAX hardware platforms are available from
                   various sources:

                   o  SRI CHARON-VAX

                   o  Tim Stark's TS10

                   o  Bob Supnik's Trailing Edge

                   VAX emulators that operate on PC systems and/or on
                   OpenVMS Alpha systems are available. For information
                   on an alternative to using a VAX emulator- on the
                   available DECmigrate VAX executable image translator-
                   please see Section 13.11.



          14       Hardware Information

          14.1  What are the OpenVMS differences among VAX, Alpha, and

                   In terms of software, very few. As of OpenVMS V6.1,
                   the VAX and Alpha platforms are very close to "feature
                   parity". OpenVMS on IA-64 is expected to have "feature
                   parity" with OpenVMS Alpha, and is based on the same
                   source pool. Most applications can just be recompiled
                   and run. Some differences to be aware of:

                   o  The default double-precision floating type on
                      OpenVMS Alpha is VAX G_float, whereas on VAX it
                      is usually D_float. D_float is available on Alpha,
                      but D_float values are converted to G_float for
                      computations and then converted back to D_float when
                      stored. Because the G_float type has three fewer
                      fraction bits than D_float, some applications may
                      get different results. IEEE float types are also
                      available on OpenVMS Alpha.

                   o  The preferred floating point format on Alpha and
                      IA-64 is IEEE.

                   o  Data alignment is extremely important for best
                      performance on Alpha. This means that data items
                      should be allocated at addresses which are exact
                      multiples of their sizes. Quadword alignment will
                      offer the best performance, especially for character
                      values and those smaller than 32 bits. Compilers
                      will naturally align variables where they can and
                      will issue warnings if they detect unaligned data

                   o  HP C is the only C compiler HP offers on OpenVMS
                      Alpha, and is a direct descendant of Compaq C and
                      DEC C on OpenVMS Alpha. HP C is compatible with DEC
                      C on OpenVMS VAX, but is somewhat different from
                      the older VAX C compiler most people are familiar


                   Hardware Information

                      with. Read up on the /EXTERN_MODEL and /STANDARD
                      qualifiers to avoid the most common problems. In
                      additon to HP C, there are open-source ports such as
                      Gnu C available for OpenVMS.

                   o  The page size on Alpha and IA-64 systems is
                      variable, but is at least 8 kilobytes. This can
                      have some effect on applications which use the
                      $CRMPSC system service as well as on the display of
                      available memory pages. The page size is available
                      from $GETSYI(SYI$_PAGE_SIZE).

                   There are also a number of manuals which discuss
                   migration to OpenVMS Alpha available on the
                   documentation CD-ROM media, both in the main
                   documentation and in the archived documentation

                   On more recent OpenVMS Alpha versions, OpenVMS Alpha
                   has begun to add features and support not available on
                   OpenVMS VAX. Salient new areas include the following:

                   o  64-bit addressing in OpenVMS Alpha V7.0 and later

                   o  Multi-host SCSI support (SCSI TCQ) in V6.2 and later

                   o  PCI support (platform-dependent)

                   o  OpenVMS Galaxy support in V7.2 and later

          14.2  Seeking performance information for Alpha (and VAX)

                   HP makes a wide range of performance documents
                   available through its FTP and WWW Internet servers
                   (see Section 3.2).

                   The following contain information on current Alpha and
                   VAX products:



                   The following sites contain information on various
                   retired VAX and Alpha products:



                   Hardware Information


                   Also see CPU2000:



          14.3  Console Commands, Serial Lines, and Controls?

                   This section contains information on VAX and Alpha
                   consoles, and details related to console commands,
                   serial lines, and configuration settings.

          14.3.1  What commands are available in the Alpha SRM console?

                   In addition to the normal BOOT commands and such (see
                   Section for some details) and the normal

read more »


OpenVMS Frequently Asked Questions (FAQ), Part 1/9

Post by Hoff Hoffm » Sat, 05 Jul 2003 02:17:17

                   Hardware Information

          14.24  Problem - My LK411 sends the wrong keycodes or some keys
                 are dead

                   Check the firmware revision on the keyboard. Hardware
                   revision B01 introduced an incompatability with the
                   device driver which causes the keyboard to not be
                   recognized correctly. There is a patch available to
                   fix this problem: [AXPDRIV06_061] - the fix is also
                   included in OpenVMS V6.2. The rev A01 keyboard, and the
                   LK450 should work without problems.

                   If you are working from another operating system
                   platform, please see the DECxterm tool and related
                   information on OpenVMS Freeware V5.0.

          14.25  Which DE500 variant works with which OpenVMS version?

                   Ensure you have a version of the Alpha SRM console
                   with support for the DE500 series device. Apply ALL
                   mandatory ECO kits for the OpenVMS version in use, and
                   also apply the CLUSIO, ALPBOOT, and ALPLAN kits, and
                   apply any available ALPCPU ECO kit for the platform.

                   o  DE500-XA
                      auto-detection, no auto-negotiation,
                      OpenVMS V6.2-1H1 and ALPBOOT ECO, also V7.0 and
                      later and ECO.
                      Device hardware id 02000011 and 02000012.
                      Component part number 54-24187-01

                   o  DE500-AA
                      auto-detection, auto-negotiation,
                      OpenVMS V6.2 and ALPBOOT and ALPLAN ECOs, or V7.1
                      and later and ECO.
                      Device hardware id 02000020 and 20000022.
                      Component part number 54-24502-01

                   o  DE500-BA
                      auto-detection, auto-negotiation,
                      OpenVMS V6.2-1H3 and CLUSIO, ALPBOOT, ALPLAN and
                      ALPCPU ECOs, or V7.1-1H1 or later and ECO.
                      Device hardware id 02000030 (check connector, vs
                      DE500-FA) (other values on old Alpha SRM firmware)
                      Component part number 54-24602-01


                   Hardware Information

                   o  DE500-FA (100 megabit fibre optic Ethernet)
                      OpenVMS V7.1-1H1 and later
                      Device hardware id 02000030 (check connector, vs
                      DE500-BA) (other values possible on old Alpha SRM
                      Component part number 54-24899-01

                   To check the DE500 device hardware id from OpenVMS, use
                   the following command:

                   $ ANALYZE/SYSTEM
                   SDA> SHOW LAN/DEVICE=EWcu:

                   The "hardware id" will be displayed.

                   To set the DE500 speed via the Alpha SRM console
                   environment variable:

                      EWx0_MODE setting           Meaning
                      --------------------------  --------------------------------
                      Twisted-Pair                10 Mbit/sec, nofull_duplex
                      Full Duplex, Twisted-Pair   10 Mbit/sec, full_duplex
                      AUI                         10 Mbit/sec, nofull_duplex
                      BNC                         10 Mbit/sec, nofull_duplex
                      Fast                        100 Mbit/sec, nofull_duplex
                      FastFD (Full Duplex)        100 Mbit/sec, full_duplex
                      Auto-Negotiate              Negotiation with remote device

                   To override the console setting and use LANCP:

                   $ RUN SYS$SYSTEM:LANCP
                   LANCP> SET DEV EWA0/SPEED=10
                   LANCP> SET DEV EWA0/SPEED=100/full_duplex

                   Fast Ethernet (100Base, 100 megabit) controllers
                   such as the DE500 series have a pair of connections
                   available-while traditional Ethernet (10Base, 10
                   megabit) is inherently a half-duplex protocol, Fast
                   Ethernet can be configured to use one or both of the
                   available connections, depending on the controller.
                   Fast Ethernet can thus be half- or full-duplex
                   depending on the configuration and the capabilities
                   of the network controller and the Ethernet network
                   plant. Some Fast Ethernet controllers can also operate
                   at traditional Ethernet speeds, these controllers are
                   thus often refered to as 10/100 Ethernet controllers.


                   Hardware Information

          14.26  Third-party disk/tape/controllers/SCSI/widgets on

                   A wide variety of third-party widgets-SCSI and ATA
                   (IDE) disks and tapes, graphics controllers, etc-are
                   obviously widely available and are used on various

                   If you purchase third-party "generic" SCSI or ATA
                   (IDE) storage devices, you and your device vendor
                   will be responsible for the testing and the support
                   of the devices. In general, you can expect that Compaq
                   will address non-standards-compliance problems within
                   OpenVMS (changes that will also not prevent operations
                   with other supported devices, of course), but you
                   and/or the device vendor and/or the device manufacturer
                   are responsible for finding and fixing problems in
                   the particular third-party device and or controller

                   In particular, realize that neither SCSI nor ATA (IDE)
                   is a particularly standard interface, these interfaces
                   tend to be a collection of optionally-implemented and
                   standardized interface features. You should not and can
                   not simply assume that all SCSI nor ATA (IDE) storage
                   devices are interchangeable. If you want to try to use
                   a generic SCSI device, use V6.2 or later, or (better)
                   V7.1-2 or later. If you wish to try to use ATA (IDE),
                   use OpenVMS V7.1-2 or later.

                   On older OpenVMS releases, see the disk capacity limits
                   (Section 9.5).

                   With SCSI disks on releases prior to V6.2, ensure
                   that you have the ARRE and ARWE settings configured
                   correctly (disabled). (If not, you will see DRVERR
                   fatal drive errors and error log entries.)

                   Some SCSI disks set the medium type byte as part of
                   the SCSI size field-this is a SET CAPACITY extension to
                   SCSI specs. This problem also applies to VAX V7.1 and


                   Hardware Information

                   Disks with SCSI disk sizes past 8.58 GB and/or with
                   the SET CAPACITY extension require ALPSCSI07 ECO or the
                   OpenVMS Alpha V7.1-2 or later release. (See Section 9.5
                   for further details.)

                   Based on the displays of the (undocumented)
                   SYS$ETC:SCSI_INFO tool; this tool is present in OpenVMS
                   V6.2 and later:

                       Issuing 6-byte MODE SENSE QIOW to get current values for page 01h
                              Page Code ................. 01h
                              Page Name ................. Read-Write Error Recovery
                              Saveable .................. Yes
                              Size ...................... 10
                              Hex Data .................. E6 08 50 00 00 00 08 00
                                                          00 00

                   The E6 indicates that the AWRE and ARRE bits are set,
                   and this is not acceptable on OpenVMS versions prior to
                   V6.2. Further along in the SCSI_INFO display, if you
                   also see:

                       Issuing 6-byte MODE SENSE QIOW to get changeable values for page 81h
                              Page Code ................. 01h
                              Page Name ................. Read-Write Error Recovery
                              Saveable .................. Yes
                              Size ...................... 10
                              Hex Data .................. C0 08 50 00 00 00 08 00
                                                          00 00

                   The C0 value means that the AWRE and ARRE values can
                   be changed on this particular SCSI device. (This is
                   not always the case.) Use RZDISK from the OpenVMS
                   Freeware, and reset the E6 flag byte to hexadecimal
                   26 (or whatever the remaining mask when you remove bits
                   C0) on page one.

                   Each SCSI and ATA (IDE) host contains non-trivial
                   SCSI and IDE driver software, and each device contains
                   equally non-trivial firmware- taken together with the
                   mechanical and electronic

read more »


OpenVMS Frequently Asked Questions (FAQ), Part 1/9

Post by Hoff Hoffm » Sat, 05 Jul 2003 02:18:23


          1858                              ATW,3-12,  3-13, 5-21, 5-22,
            17-Nov-1858,4-2                    5-23, 5-31, 8-6, 9-3, 10-2,
          2000                                 10-4, 10-7, 10-9, 10-17,
          __Year,5-33___________________       10-22, 10-26, 15-1, 15-2,

          A                                    15-3, 15-24
          ______________________________    AUTOGEN,5-10
          Access Control List Entry,5-9     Automatic Foreign Command,8-1
          ACCVIO,5-33                       AVI,7-2
          ACE,5-9                           awk,13-14
          ACTS,4-8                          ______________________________
          Agnew, Jim,14-29                  B
          Allocation Class                  ______________________________
            Fibre Channel,15-25             Backdrops,11-9
            Non-Zero,15-24,  15-25          BACKUP/IGNORE=INTERLOCK,5-48
            Volume Shadowing,15-24          Bad Block Handling,9-3
          ALLOCLASS system parameter,       BADLIB,13-20
             15-25                          BADTYPSTR,13-20
          AlphaPC 164LX,14-18               bash,13-16
          AlphaPC 164SX,14-18               Batch,13-19
          AMASK,14-25                       BB_WATCH,4-6
          Ambassador,1-10                   BC16E,14-46,  14-47
          AMD,2-9                           BCC08,14-47
          ANSI C,10-19                      BCKTRNSFAIL,15-5
          AP,10-6                           Berryman, Mark,1-4,  13-3
          Apache,13-8                       Bi-Endian,10-18
          ar,13-14                          Big-Endian,10-18
          Archie,13-7                       BIND,15-6
          ARCH_DEFS.REQ,10-16               bison,13-14
          Argument Pointer,10-6             Block
          ARRE,14-40,  14-41, 14-43           Disk,14-43
          ARWE,14-40,  14-41, 14-43         BN24H,14-46
          ASAP                              BN24J,14-46
            See DSPP                        BNC,14-35
          Ask The Wizard,3-12,  3-13,       BNU Bookreader,3-1
             5-21, 5-22, 5-23, 5-31,        Bookreader
             8-6, 9-3, 10-2, 10-4, 10-7,      BNU,3-1
             10-9, 10-17, 10-22, 10-26,     Browser,13-4
             15-1, 15-2, 15-3, 15-24        Byers, Robert Alan,13-8
          ATA,7-1,  9-5



          bzip2,13-25                       Columbia University,13-3
          ______________________________    COMMON,10-6
          C                                 Compaq,5-32
          ______________________________    Compaq Secure Web Browser,
          C,10-19,  10-26                      13-17
            Compaq C Compiler,10-19,        Composer
               10-26                          Mozilla,13-17
            DEC C Compiler,10-19,  10-26    Computer Associates,13-17
            Device Drivers,10-23            console,14-11
            HP C Compiler,10-19,  10-26     Console
            VAX C Compiler,10-19              VAXstation 3100,9-4
          CA,13-17                          Contrl,13-11
          Caesar                            COPY,10-9
            Julius,4-3                      CPAN,13-24
          CalTech,13-8                      cpio,13-14
          Carrier Sense Multiple Access,    $creprc,10-9
             with Collision Detect,         CSA
             14-49                            See DSPP
          CD                                CSLG,2-8
            Recording,9-7,  14-43           CSMA/CD,14-49
          CD-Audio,7-1                      CSWB,13-17
          CD Player,7-1                     ______________________________
          CD-R,9-7,  13-9, 14-43            D
          CD-R/RW,9-7,  9-9                 ______________________________
          CDRECORD,9-7,  14-43              Dachtera, David J.,13-8
          CD-RW,9-7,  13-9, 14-43           DATMISCH,10-19
          CDWRITE,9-7                       Daylight Savings Time,4-2,
          CGI,13-19                            4-12, 4-17, 10-23
          CHARON-VAX,13-26                  DAYLIGHT_SAVINGS.COM,4-12
          cli$get_value,10-4                DB9,14-45,  14-47
          Clock                             DCL
            TODR,4-5,  4-7                    PIPE,13-22
            TOY,4-5,  4-7                   DCL$PATH Logical Name,8-1

          Clockmeister, Ulysses T.          DCL1,8-1
            See Time                        DCL10,8-7
          Cluster                           DCL11,8-7
            Disk,14-43                      DCL12,8-8
          Cluster Load Balancing,15-14      DCL3,8-2
          Cluster Terminology,15-12         DCL4,8-2
          CMA$RTL.EXE,10-26                 DCL5,8-3
          CMS,13-20                         DCL6,8-4
          $cmsupr,12-4                      DCL7,8-5



          DCL8,8-6                          DECwindows,11-1
          DCL9,8-6                          DELETE
          DCPS,12-3                           Undelete,9-1
          DCX,13-26                         Descriptor,10-10
          DDB,10-9                          Deutsch,1-2
          Debugger                          Device Driver,10-8
            Signalling SS$_DEBUG,10-18      Device Drivers
          DEC-423,14-45                       C,10-23
          DECalert,15-10                      Floating Point,10-23
          DECC$CRTL.EXE,10-26               DEVICE_NAMING system parameter
          DECconnect,14-45                     ,15-20
          DECdns,15-6                       DFU,9-1,  9-4, 13-12
          DECevent,5-32                     DIAGNOSE,5-32
          DECmigrate,7-3,  13-24, 13-26     DIGITAL Network Products Group
          DECnet,14-49                         ,14-33
            Asynchronous,14-49              Digital Synergy,13-8
            DECNET_REGISTER,15-5            Digital Versatile Disk,9-9
            MOP,15-6                        Disk
          DECprint,12-3                       Block,14-43
          DECthreads,10-26                    Cluster,14-43
          DECUS,1-8                           Sector,14-43

            See User Group                  Disk Mirroring,9-2
            Hobbyist Licenses,2-7             See Volume Shadowing
          DECUServe,1-3                     Disks
          DECUS Software Library,13-3         ATA,7-1,  9-5
          DECW$CDPLAYER,7-1                   Bad Block Handling,9-3
          DECW$IGNORE_WORKSTATION             CD-R,14-42
             Logical Name,11-7                CD-R/RW,9-7,  9-9
          DECW1,11-1                          CD-Recordable,9-7
          DECW10,11-8                         DVD+R/RW,9-7,  9-9
          DECW11,11-10                        DVD-R/RW,9-7,  9-9
          DECW12,11-11                        FAT Format,7-2
          DECW13,11-11                        Floppy,7-2
          DECW14,11-12                        IDE,7-1,  9-5, 14-40, 14-43
          DECW15,11-14                        Jumpers,14-37
          DECW16,11-15                        MSCP,9-3
          DECW17,11-15                        PC Format,7-2
          DECW2,11-3                          SCSI,9-3,  9-11, 14-37,
          DECW3,11-3                             14-43
          DECW4,11-4                          SCSI-2,9-6
          DECW5,11-4                          Volume Set,9-7
          DECW6,11-5                          Zip,14-42



          Disk Shadowing,9-2                ECO kits,5-25
          DJE Systems,13-8                  EFI,14-22
          DNPG,14-33                        EIA-232,14-45
          DNS,15-6                          ELSA GLoria Synergy,5-22
          DOC1,3-1                          elvis,13-15
          DOC10,3-6                         Encompass
          DOC11,3-7                           See User Group
          DOC12,3-13                          Hobbyist Licenses,2-7
          DOC13,3-10                        Encompasserve,1-3
          DOC14,3-12                        Encompass Software Library,
          DOC2,3-1                             13-3
          DOC4,3-6                          Endian-ness,10-18
          DOC5,3-6                          Engineering Software,7-2
          DOC6,3-5                          Ensoniq,7-2
          DOCUMENT,10-17                    Enterex
          DQDRIVER,7-1,  9-5, 14-43           Hobbyist Licenses,2-7
          Driver                            EPIC,14-21
            Device,10-8                     $erapat,5-51
          DRVERR,14-40,  14-43              Ergonomic Solutions,15-10
          DSPP,2-8,  2-13                   Error analysis,5-32
          DST,4-2,  4-12, 4-17, 10-23       ETAPE,7-3
          DTSS,4-9                          Ethernet,14-49
            DTSS$CLERK,4-18                 Event Flags,11-10
            Too Few Servers Detected,       EWS,11-3
               4-19                         EXE$GL_TICKLENGTH,4-10
          DTSS$CLERK,4-18                   EXE$GL_TIMEADJUST,4-10
             ,4-17                          EXE$GQ_SAVED_HWCLOCK,4-6
          DTSS$NTP_PROVIDER.C,4-9           EXE$GQ_SYSTIME,4-4,  4-6
          DTSS$SET_TIMEZONE.EXE,4-14        EXE$GQ_TDF,4-14
          DTSS$UTC_STARTUP.COM,4-17         EXE$GQ_TODCBASE,4-4
          DVD+R,9-9,  13-9                  EXE$SETTIME,4-4
          DVD+R/RW,9-7                      Executable Image,10-8
          DVD+RW,13-9                       EXPECTED_VOTES system

read more »