                       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 significant H                    enhancements and new features added on OpenVMS Alpha.I                    OpenVMS I64 started with "feature parity" with OpenVMS_C                    Alpha at the V8.2 release, and OpenVMS Alpha andtJ                    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 present G                    within the shared source code pool, obviously.) Most ?                    applications can just be recompiled and run.M  3                    Some differences to be aware of:f  C                    o  The default double-precision floating type onaE                       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 formJ                       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 mayfF                       get different results. IEEE float types are also1                       available on OpenVMS Alpha.t  J                    o  The preferred floating point format on the Alpha and9                       on the IA-64 architectures is IEEE.a  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 atnI                       addresses which are exact multiples of their sizes.tI                       Quadword alignment will offer the best performance,pG                       especially for character values and those smallerAB                       than 32 bits. Compilers will naturally align  J                                                                       14-1               '                    Hardware InformationM        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 istF                       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, andcH                       see the documentation in the DEC C for OpenVMS VAXG                       manuals around migrating from VAX C to DEC C. (InbI                       addition to HP C, there have been open-source ports ;                       such as Gnu C available for OpenVMS.)e  A                    o  The page size on Alpha and IA-64 systems islE                       variable, but is at least 8 kilobytes. This candD                       have some effect on applications which use theI                       $CRMPSC system service as well as on the display ofrH                       available memory pages. The page size is availableE                       from $GETSYI using the SYI$_PAGE_SIZE itemcode.p  C                    There are also a number of manuals which discussnJ                    migration to OpenVMS Alpha and to OpenVMS I64 availableA                    in the OpenVMS documentation, both in the main I                    documentation and (depending on the age of the manuals C                    involved) in the archived documentation section.y  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. Salienti3                    additions include the following:   H                    o  64-bit addressing in OpenVMS Alpha V7.0 and later,)                       and on OpenVMS I64.c  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 laterd                      14-2     s          '                    Hardware Informationn        >                    Please see Section 14.4.5 for Intel Itanium                    terminology.e  D           __________________________________________________________C           14.2  Seeking performance information for Alpha (and VAX)d                 systems?  A                    HP makes a wide range of performance documentsME                    available through its FTP and WWW Internet serversn%                    (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-_-                    related product web pages:a  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_r                       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?p  E                    This section contains information on VAX and AlpharE                    consoles, and details related to console commands,r<                    serial lines, and configuration settings.      J                                                                       14-3 2  /          '                    Hardware Informationp      '           ______________________________G           14.3.1  What commands are available in the Alpha SRM console?l  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 sucheI                    as I/O redirection and floppy disk access are possible -                    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 :d  -                          >>> show * > env.dat 1                          >>> show conf > conf.dats;                          >>> cat env.dat > fat:env.dat/dva0H=                          >>> cat conf.dat > fat:conf.dat/dva0o  E                    3  You may use the SRM "ls" command to display thes-                       contents of the floppy.F  0                          >>> ls fat:env.dat/dva01                          >>> ls fat:conf.dat/dva0   C                    4  You can now transfer the FAT-format floppy to %                       another system.   '           _____________________________.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 Alphah<                    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 Alpha C                    hardware. PALcode is implemented using availableiD                    Alpha instructions and using the Alpha processor,E                    though PALcode operates in a mode which simplifiesaC                    programming. PALcode is also permitted access toPE                    processor-specific and otherwise internal featuresrG                    of a particular Alpha microprocessor implementation;oH                    microprocessor-specific features which are not easilyF                    accessable to operating system or application code.                      14-4  p  i          '                    Hardware Information       '           _____________________________iJ           14.3.3  Alpha COM ports and VAX console serial line information?  E                    This section contains information on the Alpha COMaH                    communication ports, and related settings, as well asJ                    on the VAX console bulkhead and VAX console serial line                    connection.  '           _____________________________.E           14.3.3.1  Which terminal device name is assigned to the COMw                     ports?  D                    COM2 is normally TTA0:. COM1 is normally TTB0: ifG                    the Alpha workstation is booted with the SRM consoleoH                    environment variable set to graphics, and is OPA0: if0                    the console is set to serial.  I                    On the DEC 2000 series (sometimes incorrectly known by J                    the name of the system as sold for Microsoft Windows NTG                    Alpha; as the DECpc 150 AXP series) on older OpenVMS G                    Alpha releases, COM1 through COM4 are known as OPA0:aH                    through OPA3:. On all current OpenVMS releases, theseG                    ports are serviced by the terminal driver and not byd/                    the console OPDRIVER driver.e  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 SHOWoG                    TERMINAL. (Device names can vary by OpenVMS version,eE                    as well as by the SRM console environment variableV                    selection.)  G                    For serial console hardware and related information, G                    and for pin-outs and related information, please seet2                    Section 14.3 and Section 14.26.  '           _____________________________eJ           14.3.3.2  Which serial port is the console on the MicroVAX 3100?  G                    Just to keep life interesting, the MicroVAX 3100 hasSD                    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) outputSF                    the results of the selftest in parallel with MMJ-1.I                    When the console is enabled to respond to BREAK, MMJ-30  J                                                                       14-5               '                    Hardware Informationi        I                    becomes the console port, and MMJ-1 will (confusingly) I                    output the results of selftest in parallel with MMJ-3.   '           _____________________________lJ           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, largely H                    for historical reasons-that enables one of the serialE                    lines as the system console device; as OPA0:. ThiswJ                    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 systemsoJ                    also have a similarly-labled S3 switch for selection of)                    the alternate console.   I                    The particular port that becomes the console can vary. G                    The printer MMJ connection is used on all VAXstationsD                    3100 series. On VAXstation II, the console DB9 isI                    used, rather than the graphics display. On most (all?) I                    AlphaStation series systems, typically the COM1 serialr,                    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.t  J                    For information on registering software license productG                    authorization keys (PAKs), please see Section 5.6.2.n  '           _____________________________ D           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-6e c  n          '                    Hardware InformationF        F                    There are three controls on the console bulkhead of!                    these systems:c  <                      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,a?                                       and auto-boot is enabled.-  H                      Three-position-rotary: power-up bootstrap behaviour/                        arrow: normal operation.n3                        face: language inquiry mode. <                        t-in-circle: infinite self-test loop.  G                      Eight-position-rotary: console baud rate selection G                        select the required baud rate; read at power-up.   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 serialnG                    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, seeo!                    Section 14.27.e  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 organizationtF                    to determine the nature of a processor problem. TheD                    particular countdown sequence varies by processorC                    type, consult the hardware or owner's manual for G                    the processor, or contact the local hardware service F                    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 controloF                    from the console program to the (booting) operating                    system.          J                                                                       14-7 r  r          '                    Hardware Informations      '           _____________________________ ?           14.3.4  What are Alpha console environment variables?e  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 othereF                    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:m  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 sortsVJ                    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.o  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 variables I                    is rather more involved, and not directly available to I                    application software operating outside of kernel-mode.                         14-8a a  s          '                    Hardware Information       '           _____________________________e8           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.   '           _____________________________l:           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 primaryOE                    bootstrap boot flags are largely parallel to thoseaE                    of OpenVMS Alpha (see Section 14.3.5.2, though thefI                    console and the console mechanisms used to specify the_I                    boot command, the boot flags, and boot command optionse&                    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 thee)                    EFI shell prompt, use:   -                    Shell> SET VMS_FLAGS "0,1"o  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 bootstrapE5                    selected by the following example:                       -flages 0,1  G                    For related information on managing EFI boot aliasesc@                    from OpenVMS I64, please see Section 14.3.10.  J                                                                       14-9    e          '                    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.e  J           ________________________________________________________________8           Table 14-1  I64 Conversational Bootstrap Flags  J                    _______________________________________________________J                    Bit_______Example_Mnemonic__________Description________  E                    0         0,1     CONV              Conversationalg@                                                        bootstrap  C                    1         0,2     DEBUG             Load SYSTEM_aI                                                        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 messages   D                    17        0,200000?                 Request for aE                                                        bootstrap from J           _____________________________________________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,30001p  '           _____________________________0<           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 imageFH                    APB.EXE. These flags control the particular behaviour$                    of the bootstrap.  &                    BOOT -FL root,flags                      14-10 d  p          '                    Hardware Informationr        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)r  C                    2       INIBPT            Stop at initial system_E                                              breakpoints if bit 1 setB8                                              (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 not A                                              have an image header   @                    6       NOTEST            Inhibit memory test  A                    7       SOLICIT           Prompt for secondaryD;                                              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 halt   E                    12      DEBUG_BOOT        Transfer to intermediate >                                              primary bootstrap  ?                    13      CRDFAIL           Mark CRD pages bad   H                    14      ALIGN_FAULTS      Report unaligned data traps9                                              in bootstrap   D                    15      REM_DEBUG         Allow remote high-level>                                              language debugger  I                    16      DBG_INIT          Enable verbose boot messages 9                                              in EXEC_INIT   J                    17      USER_MSGS         Enable subset of verbose bootE                                              messages (user messages)   F                    18      RSM               Boot is controlled by RSM  J                                                                      14-11 l  l          '                    Hardware Informationu      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 systemlJ                                              boot procedure, the bootstrapD                                              code solicits parameterE                                              and other input from the F                                              console terminal. If DIAGH                                              is set, then the diagnosticH                                              supervisor should enter itsJ                                              menu mode and prompt user forA                                              the devices to test.o  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               '                    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.F  I                    3       BBLOCK            Secondary boot from the boot_G                                              block. Secondary bootstrap_H                                              is a single 512-byte block,J                                              whose LBN is specified in R4.  G                    4       DIAG              Diagnostic boot. SecondarytH                                              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 imageyH                                              header. If the RPB$V_HEADERI                                              bit is not set, the image isuE                                              assumed to have no imageyC                                              header, and control isTI                                              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 a             '                    Hardware Informationh      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 to_H                                              tell VMB not to read a fileF                                              from the boot device thatG                                              identifies bad or reservediF                                              memory pages, so that VMBI                                              does not mark these pages asaF                                              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 memoryeC                                              is to be used. This istG                                              for tightly-coupled multi-gJ                                              processing. If the RPB$V_DIAGJ                                              bit is also enabled, then theI                                              Diagnostic Supervisor enters ?                                              its AUTOTEST mode.   F                    12      USEMPM            Specifies that multi-portE                                              memory should be used in I                                              addition to local memory, as H                                              though both were one single;                                              pool of pages.l  B                    13      MEMTEST           Specifies that a moreH                                              extensive algorithm be usedI                                              when testing main memory foruI                                              hardware uncorrectable (RDS)d4                                              errors.                          14-14               '                    Hardware Informationn      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 main4I                                              MS780 memory is insufficient C                                              for booting. This is a C                                              remnant of the support F                                              for the VAX-11/782 seriesF                                              system and its AsymmetricC                                              Multiprocessing (ASMP)fE                                              environment. Support forfH                                              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 VAX 6                    consoles tend to use the following:  &                      >>> BOOT/R5:flags  '           _____________________________SB           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 environmentaE                    variable to GRAPHICS to select the console displayk4                    output via the graphics display.)  F                    The DEC 3000 series has a jumper on the motherboardE                    for this purpose. Various older Alpha workstations I                    generally will not (automatically) bootstrap without adH                    keyboard connected, due to the self-test failure thatA                    arises when the (missing) keyboard test fails..  J                                                                      14-15 s             '                    Hardware Informations        I                    The usual settings for the console serial terminal (ordG                    PC terminal emulator acting as a serial console are:   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 system H                    consoles are capable of 57600 baud. See the COM2_BAUDI                    console environment variable, and ensure that you have 7                    current SRM firmware version loaded.d  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.r  J                    For information on registering software license productG                    authorization keys (PAKs), please see Section 5.6.2.f  @                    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?a  E                    This section discusses downloading and using Alphae>                    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.htmlo  G                    o  ftp://ftp.digital.com/pub/Digital/Alpha/firmware/o  R                    o  ftp://ftp.digital.com/pub/Digital/Alpha/firmware/readme.html                      14-16    _          '                    Hardware Informationr        G                    The latest and greatest firmware-if updated firmware J                    has been released after the most recent firmware CD was-                    distributed-is located at::  O                    widftp://ftp.digital.com/pub/Digital/Alpha/firmware/interim/t  F                    For information on creating Alpha bootable floppiesI                    containing the firmware, and for related tools, please +                    see the following areas:   W                    widftp://ftp.digital.com/pub/DEC/Alpha/firmware/utilities/mkboot.txtu  Z                    widftp://ftp.digital.com/pub/DEC/Alpha/firmware/utilities/mkbootarc.txt  Y                    widftp://ftp.digital.com/pub/DEC/Alpha/firmware/utilities/mkntboot.txt/  F                    The SROM firmware loader expects an ODS-2 formattedI                    floppy, see mkboot. As for which image to use, the ROMmG                    image uses a header and the file extension .ROM, andgE                    the SROM bootable floppy cannot use the .ROM file.i  G                    To check the firmware loaded on recent OpenVMS Alpha/,                    systems, use the command:  A                    $ write sys$output f$getsyi("console_version")eA                    $ write sys$output f$getsyi("palcode_version")a#                    SDA> CLUE CONFIG   C                    Also see Section 14.3.7.2. For information on HP E                    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.h  '           _____________________________mF           14.3.7.2  How do I reload SRM firmware on a half-flash Alpha                     system?e  E                    Some of the AlphaStation series systems are "half-NI                    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, F                    and then getting into the AlphaBIOS firmware updateH                    sequence, and then entering "update srm" at the apu->                    prompt.  J                                                                      14-17 a  S          '                    Hardware Information         J                    To shuffle the files, copy the target SRM firmware fileG                    (as200_v7_0.exe is current) to a blank, initialized,hG                    FAT-format floppy under the filename A:\FWUPDATE.EXEe  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.D  '           _____________________________hA           14.3.7.3  How do I switch between AlphaBIOS/ARC and SRMS                     consoles?t  G                    The specific steps required vary by system. You must C                    first ensure that the particular Alpha system isAH                    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.r  F                    A typical sequence used for switching over from theI                    AlphaBIOS graphics console to the SRM console follows:t  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 yourA                       changes.  -                    6  Power-cycle the system.g                      14-18 o  f          '                    Hardware Information         >                    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 are"G                    "half-flash" systems and do not support the presence H                    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 network E                    download, or from a firmware CD-ROM. Following the F                    normal AlphaBIOS or ARC firmware update sequence toG                    the APU prompt, and then explictly select the target F                    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-> updater                          -or-p'                        Apu-> update ARCA#                        Apu-> verifyt!                        Apu-> quito-                        Power-cycle the system   I                    Use the following sequence to specifically update (and I                    load) SRM from AlphaBIOS/ARC on a "half-flash" system:   '                        Apu-> update SRMr#                        Apu-> verify !                        Apu-> quitw-                        Power-cycle the system   I                    Use the following sequence to specifically update (and G                    load) the AlphaBIOS/ARC console from SRM on a "half- !                    flash" system:s  *                        >>> b -fl 0,A0 ddcu7                        BOOTFILE: firmware_boot_file.exel  '                        Apu-> update ARCh#                        Apu-> verifyA!                        Apu-> quit -                        Power-cycle the system>    J                                                                      14-19 e  l          '                    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 aeH                    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.y  G                    Using OpenVMS I64 and the EFI console, the bootblockiF                    structures are expected to be compatible with thoseE                    of Microsoft Windows and other Integrity operatingwJ                    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 selectED                    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 to49                    select AlphaBIOS/ARC, use the command:   (                       >>> set os_type NT  .                    and power-cycle the system.  =                    For information on acquiring firmware, seecG                    Section 14.3.7.1. For information on OpenVMS licenseTA                    PAKs (for hobbyist use) see Section 2.8.1. ForsA                    information on the Multia, see Section 14.4.1.o  J                    Information on enabling and using the failsafe firmwareI                    loader for various systems-this tool is available only I                    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 h  a          '                    Hardware Information         '                             F1   Ctrl/A '                             F2   Ctrl/Bd'                             F3   Ctrl/Ca'                             F4   Ctrl/Dr'                             F5   Ctrl/Et'                             F6   Ctrl/F '                             F7   Ctrl/Pi'                             F8   Ctrl/R '                             F9   Ctrl/T '                            F10   Ctrl/U '                         Insert   Ctrl/V '                         Delete   Ctrl/W '                      Backspace   Ctrl/H '                         Escape   Ctrl/[ '                         Return   Ctrl/M '                       LineFeed   Ctrl/J 8                       (Plus) +   upselect (some systems):                      (Minus) -   downselect (some systems)+                            TAB   down arrow )                       SHIFT+TAB  up arrow9  '           _____________________________ ,           14.3.8  Console Management Options  E                    Options to collect multiple consoles into a singlesG                    server are available, with both hardware options and G                    software packages that can provide advanced features $                    and capabilities.  G                    Some of the available console management options for                     OpenVMS:   5                    o  Heroix: http://www.robomon.com/   C                    o  KI Products: http://www.ki.com/products/clim/a  ?                    o  Global Maintech: http://www.globalmt.com/c  3                    o  TECsys: http://www.tditx.com/v  C                    o  CA: http://www.cai.com/products/commandit.htma  D                    Computer Associates is the owner of what was onceG                    known as the VAXcluster Console System (VCS) consolepI                    management package, and has integrated this capabilityt8                    into the CA management product suite.  J                                                                      14-21 t  /          '                    Hardware Information       '           _____________________________ 2           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 thetG                    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 williA                    resynchronize the boot aliases with the volumehJ                    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 signaturesrJ                    (if any) be preserved, and this will typically maintainA                    the validity of your EFI console boot aliases.c  '           _____________________________ C           14.3.10  Can OpenVMS access the EFI console Boot Aliases?b  I                    For access to the EFI console environment from OpenVMShG                    I64, see the BOOT_OPTIONS.COM command procedure, andeJ                    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.v  F                    For related information on boot aliases, please see$                    Section 14.3.5.1.  '           _____________________________b>           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 thenaF                    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.D                        14-22 F  w          '                    Hardware Informationf        I                    The HP Integrity Server website is accesssable via therH                    following URL, and the available services and supportI                    information there has links to the available platform-iJ                    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- E                    R or CD-RW disk. If you use CD writer software for D                    another platform, you will want to use the block,E                    binary, ISO or raw mode operations appropriate forlI                    the particular chosen recording package. The followingeC                    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,aD                       and navigate to the supporting information andG                       specifically to the Download Drivers and Softwaree                       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 availablesD                       and there are also various off-line diagnosticB                       images, choose the ISO-format firmware file.  E                    4  Read the directions for the firmware file, thencG                       download the ISO-format firmware (zip-compressed)kF                       file. A binary-mode FTP transfer should be used.  E                    5  Unzip the file into the corresponding .ISO dataeH                       file. Somewhat confusingly, the .ISO extension canE                       indicate either a block-oriented raw image of aoI                       disk, or a disk with the ISO-9660 volume structure. C                       In this case, the former is intended and thiscG                       file contains a a block copy or disk image of thekH                       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               '                    Hardware Informationt        D                    6  Use CDRECORD or other available recording toolE                       (please see Section 9.7 for related details) tonH                       burn a CD-R or CD-RW disk, specifying the ISO file;                       as the source for the burn operation.n  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 generatedeH                       directly on an Integrity CD-R/RW-capable drive, of                       course.   G                    9  Using the EFI shell, display the current firmware /                       version using the command                          info fw   D                   10  Exit the EFI shell and select the boot optionsC                       maintenance menu; create a boot alias for theoF                       removable media drive for the CD; for the newly-,                       created firmware disk.  E                   11  Boot it. Follow the directions displayed by the H                       firmware loader and related documentation, heedingC                       the release notes that were reviewed earlier.   E                   12  Perform a cold restart of the Integrity server.s  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?F  I                    For the list of boxes that are officially and formally C                    supported by OpenVMS Engineering, please see the >                    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 Informationa        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, somebodydD                    (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, therenA                    are platform-level differences even within thecE                    VAX and within the Alpha platforms- hardware-leveleI                    differences that can require moderate to extensive newhG                    coding within OpenVMS. Within a platform series, andhI                    particularly within Alpha platforms (and those few VAXiJ                    systems) that support Dynamic System Recognition (DSR),1                    OpenVMS can usually bootstrap.   A                    DSR is a mechanism by which OpenVMS can gather G                    platform-specific information, and DSR is the reasonhF                    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 SRMrG                    console code, and with platform non-volatile memory.S  E                    OpenVMS users with experience on older OpenVMS VAXpF                    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 7000eF                    model 800 being (mis)identified as a VAX 7000 modelE                    600 when bootstrapped on OpenVMS VAX V5.5-2. (ThiseF                    (mis)identification was the outcome of a deliberateI                    engineering effort to permit the VAX 7000 model 800 tonJ                    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 Information.        I                    on (byte-code interpreter compliant) PCI I/O hardware.tH                    ACPI tables provide the information that was formerlyI                    retrieved from DSR and from the SRM, and the byte-code J                    interpreter can (theoretically) permit at least limitedG                    operations with (compliant) PCI hardware, whether or H                    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, and G                    may or may not have sufficient performance for local H                    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 softwarelE                    drivers out onto the specific PCI hardware, and to E                    permit the same byte code to operate regardless ofaF                    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.o  '           _____________________________t&           14.4.1  on the Alpha Multia?  I                    Yes, there are a set of unsupported images that permit F                    specific OpenVMS Alpha versions to bootstrap on theE                    Multia UDB system. These images and the associated E                    instructions are available at the OpenVMS Freeware                     website:b  <                    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 OpenVMSsD                    on the Multia system include (but may well not be-                    limited to) the following:i  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 r  n          '                    Hardware InformationS        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.o  2                    o  The serial lines don't work.  I                    o  If you have a Multia with a PCI slot, you can't usea<                       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 seelG                       any OpenVMS updates, nor SRM console updates, nor "                       any support.  F                    o  Do not expect to see any new versions of OpenVMSI                       on the Multia nor on any other unsupported systems.aH                       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 distributedpJ                    with OpenVMS V7.2. (These images became available after*                    Freeware V4.0 shipped.)  E                    Other sources of information for OpenVMS on Multiao                    include:s  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 n  m          '                    Hardware Informationc      '           _____________________________y2           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 bootstrapoI                    OpenVMS. (The Aspen Durango II variant, specifically.)   E                    One problem has been generally reported: ATA (IDE) G                    bootstraps will fail; SCSI storage and a SCSI CD-ROM_&                    device is required.  -                    Also see Section 14.4.2.1.e  '           _____________________________12           14.4.2.1  on the NoName AXPpci33 system?  I                    Information on bootstrapping OpenVMS (using the MultiaoJ                    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.txti  <           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.m  :                    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 carda+                       supported by OpenVMS.i  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.o                      14-28               '                    Hardware Information         E                    o  Rumour has it that you have one of the AXPpci33 C                       motherboards with the PS/2 mouse and keyboarddC                       connectors and a VGA card (one that will work.E                       under DECwindows) and you can run DECwindows onh!                       the system.i  '           _____________________________ )           14.4.3  on the Alpha XL series?u                      No.  J                    OpenVMS Engineering does not formally support the AlphaH                    XL series, nor will OpenVMS (informally) bootstrap on'                    the Alpha XL series.h  G                    OpenVMS can not, will not, and does not bootstrap on H                    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.e  '           _____________________________ 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 areeF                    supported by OpenVMS. You must also ensure that you9                    have the most current firmware loaded.o  G                    Here are some salient differences within the variousn/                    Personal Workstation series:W  C                    o  The -a series was designed and was tested for G                       Windows NT use. Only. It is not supported for uset#                       with OpenVMS.   I                    o  The -au series was designed and tested for Windows, C                       OpenVMS, and Tru64 UNIX compatibility, and is 4                       considered a supported system.  J                                                                      14-29               '                    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.e  G                      o  The Miata MX5. The Miata MX5 variant has no USBaF                         ports and no on-board SCSI. The on-board IntelI                         SIO chipset is not supported by OpenVMS, and thus F                         OpenVMS cannot bootstrap ATAPI CD-ROM devices.  I                         That said, the Miata MX5 -a series typically camecI                         with DEC branded Adaptec 2940UW SCSI controllers, E                         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.   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-ROMhI                         are supported by OpenVMS. The Miata GL -a variantsE                         is need not be configured with an add-on SCSIpG                         controller, given both the ability to bootstrap.@                         from ATAPI CD-ROM and the on-board SCSI.  C                         Graphics and other I/O can and does vary byU                          package.  H                         Various of the Miata GL systems are supported by                          OpenVMS.  G                    For obvious reasons, most folks will prefer and will I                    select a Miata GL system, given the choice between theSJ                    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 p  M          '                    Hardware Informationf      '           _____________________________sF           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 onlyoJ                    for use with the Microsoft Windows NT operating system.  C                    On some of the "Whitebox" systems, the following_G                    sequence of console commands can potentially be usedlG                    to convert the system over to unsupported use by andoG                    for OpenVMS Hobbyist users. (But please note that if E                    you wish to attempt this, you must ensure that all E                    graphics and all I/O controllers in the system are J                    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 must I                    realize that the resulting Whitebox configuration will G                    be entirely unsupported and may or may not be stable                     and useful.)t  "                    set os_type vmsD                    cat nvram  ! too see what is in this, if anything                    edit nvram %                    10 set srm_boot on                     20 ea                    initm  E                    If your nvram has other contents, you will need to4E                    change the line numbers (10 and 20) to reflect thehJ                    contents of your configuration. To obtain documentationE                    on the commands of the console editor, enter the ? -                    command within the editor.t  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 supportedeE                    by OpenVMS, though the AlphaServer 800 series is aaJ                    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.   J                                                                      14-31 e  3          '                    Hardware Information       '           _____________________________ I           14.4.4.2  OpenVMS and Personal Workstation ATA (IDE) bootstrap?e  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 not4A                    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:   '                      SHOW CONFIGURATION   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-is,I                    expected to be included as part of the contents of theMB                    DQDRIVER directory on Freeware V5.0 and later.)  G                    Many of the -a series systems will include the Intel ;                    SIO, and thus cannot bootstrap from IDE.e  :                    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 theo2                    Intel Itanium Processor Family.  F                    The first release of OpenVMS I64 was V8.0, with theG                    first general or first production release of OpenVMSaI                    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 implementingsC                    the IA-64 architecture. IA-64 is the name of the.F                    Intel architecture implementing the VLIW (Very LongE                    Instruction Word) design known as EPIC (Explicitlyn3                    Parallel Instruction Computing).e                      14-32               '                    Hardware Information         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 HP H                    operating systems that runs on HP Integrity hardware.  I                    The Extensible Firmware Interface (EFI) is the name of G                    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.  '           _____________________________w>           14.4.5.1  Where can I get Intel Itanium information?  I                    Intel Itanium Processor Family and IA-64 Architecture,tA                    Hardware, Software, and related docoumentation .                    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-l6                       64/Downloads/archSysSoftware.pdf  9                    o  ftp://download.intel.com/design/IA- /                       64/Downloads/24870101.pdf   G                    Information on the classic Intel Extensible FirmwarecH                    Interface (EFI) (for IA-64) and of the multi-platformG                    Unified EFI (UEFI) console project documentation are 3                    available at the following URLs:o                      o  Intelt0                       http://developer.intel.com                      o  UEFI)                       http://www.uefi.orgo  >                    Please see Section 14.4.5 for Intel Itanium                    terminology.     J                                                                      14-33 e  F          '                    Hardware Information       D           __________________________________________________________I           14.5  What is the least expensive system that will run OpenVMS?   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 companiesoJ                    sell Alpha-powered systems and Alpha motherboards, someI                    of which will run (and can be purchased with) OpenVMS-SI                    see the OpenVMS Software Product Description (SPD) foryG                    details on the supported systems and configurations. F                    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-see .                    Section 14.4.1 for details.  C                    Used Itanium-based systems that a hobbyist couldcE                    likely use to bootstrap OpenVMS I64 have been seenyE                    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-nJ                    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. Seep6                    Section 13.12 for details on those.  ?                    Hobbyist-related hardware platform selectiontA                    information-various options and considerationsfB                    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/a                        14-34    i          '                    Hardware Information         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 thatdE                    (in the case of SCSI devices) it also specifically C                    supports 512-byte block transfers; no equivalent H                    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 I64e!                    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/H@                       Digital/info/semiconductor/literature/dsc-"                       library.html  +                    o  Alpha Systems Update:iC                       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 d  t          '                    Hardware Informationm        H                       OpenVMS typically uses SPD 25.01.xx, SPD 41.87.xx,'                       and SPD 82.35.xx.   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 available/                    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.html:  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 on F                    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 theaG                    execution of newer Alpha instructions on older AlphaaG                    microprocessors. (Instruction emulation capabilitiesnD                    are available for user-mode application code, andG                    are not available to device drivers or other similarq%                    kernel-mode code.)   A                    Alpha instructions are available in groups (ornI                    subsets). Obviously, there is the base instruction setiH                    that is available on all Alpha microprocessors. Then,F                    the following are the current instruction extension                      14-36 t  n          '                    Hardware Informationp        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.s  E                    o  floating-point and square root extension (FIX):lF                       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.W  C                    The typical instruction subset that provides theIF                    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=GENERIC   E                    The /ARCHITECTURE controls the maximum instruction E                    subset that the compiler will generally use, whileoI                    the /OPTIMIZE=TUNE controls both the instruction-levelvH                    scheduling and also the instructions generated insideG                    loops-any code resulting from /OPTIMIZE=TUNE that issF                    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 Alpha "                    microprocessor.  F                    Typically /OPTIMIZE=TUNE=GENERIC is the appropriateG                    choice for tuning, and the /ARCHITECTURE selects theaI                    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 the C                    emulation, but if /ARCHITECTURE is a significant E                    benefit, then the emulation might be a performanceI                    penalty.o  J                                                                      14-37               '                    Hardware Informationr        E                    Please see the OpenVMS Ask The Wizard area for the G                    source code of a (non-privileged) tool that looks atbF                    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.e  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.   D           __________________________________________________________'           14.9  What is byte swizzling?2  I                    "Swizzling" is the term used to describe the operationsD                    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 offsethJ                    into an address space by 5 (or 7 for one older system),I                    and ORing this into the base address. It then required_J                    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 thetG                    transfer was encoded into the address data. The datasG                    itself then had to be shifted into the correct "byte E                    lane" ; into the required offset position within af%                    longword transfer;o  I                    The EV56 microprocessor supports byte/word instruction I                    references in memory space, however only specific EV56oI                    systems can support byte/word accesses into I/O space;tF                    device drivers may or may not be able to utilize toE                    byte/word instructions to access device registers.tH                    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.c                      14-38               '                    Hardware Informatione        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.   I                    If a device driver uses CRAM or IOC$WRITE_IO/IOC$READ_ H                    IO, then OpenVMS will correctly process the swizzlingE                    requirements without requiring changes the driver; G                    OpenVMS will transparently swizzle and unswizzle thesE                    I/O space references, if needed for the particulareI                    target platform. (Access and use of these routines mayyG                    or may not be feasible within the requirements for a H                    particular device driver, with the decision typicallyG                    based on the target performance requirements and the G                    expected frequency of device references and thus the H                    expected frequency of calls to these or other similar                    routines.)n  E                    To use byte/word operations on MEMORY, you need toAH                    tell the compiler to use the EV56 or EV6 architectureB                    (/ARCHITECTURE=EV56). Memory operations did not?                    swizzle, but the compiler would do long/quadsD                    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 space I                    access across a range of Alpha systems such as is done J                    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 andeH                    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.e          J                                                                      14-39 n