             '                    Time and Timekeeping       D           __________________________________________________________;           4.8  Using w32time or an SNTP as a time provider?   J                    No standards-compliant NTP or SNTP server is reportedlyF                    capable of synchronizing with the Microsoft Windows$                    w32time services.  D                    Further, NTP clients are not generally capable of5                    synchronizing with an SNTP server.   C                    Open Source (Free) NTP servers (qv: OpenNTP) are H                    available for Microsoft Windows platforms, and TCP/IPD                    Services and third-party packages all provide NTPD                    servers for OpenVMS, and NTP and SNTP clients can1                    synchronize with these srvers.t                                                            J                                                                       4-31 s  h                    J                    _______________________________________________________  0           5        System Management Information      D           __________________________________________________________*           5.1  What is an installed image?  B                    The term "install" has two distinct meanings inH                    OpenVMS. The first relates to "installing a product",I                    which is done with either the SYS$UPDATE:VMSINSTAL.COM ?                    command procedure or the POLYCENTER Software_E                    Installation (PCSI) utility (PRODUCT command). The C                    second meaning relates to the use of the INSTALL_;                    utility, which is what concerns us here.   E                    The INSTALL utility is used to identify to OpenVMSiD                    a specific copy of an image, either executable orG                    shareable, which is to be given some set of enhancedSB                    properties. For example, when you issue the SETF                    PASSWORD command, the image SYS$SYSTEM:SETP0.EXE isG                    run. That image needs to have elevated privileges tou(                    perform its function.  G                    The other important attribute is /SHARED. This meansiI                    that shareable parts of the image (typically read-only J                    code and data) are loaded into memory only once and areH                    shared among all users on a system. Executable imagesH                    can be installed /SHARED as well as shareable libraryH                    images. (The term "shareable" has dual meanings here,G                    too. See the OpenVMS Programming Concepts Manual for $                    further details.)  H                    It's important to note that there is no such thing asF                    "installing a shareable image with privileges". TheI                    INSTALL utility will let you do it, but the privilegesnJ                    you specify will be ignored. To have a callable routineF                    run with enhanced privileges that are not availableE                    to its caller, you must construct your routines asrD                    "user-written system services" (UWSS) and installC                    the shareable image with the /PROTECT qualifier.nG                    See the OpenVMS Programming Concepts Manual for moreTI                    information on user-written system services. Note alsoeH                    that in many cases the need to grant privileges to an  J                                                                        5-1               0                    System Management Information        G                    image can be replaced with the use of the "Protected I                    Subsystems" feature that grants a rights identifier to I                    an image. See the OpenVMS Guide to System Security for 7                    information on Protected Subsystems.e  D           __________________________________________________________7           5.2  Are there any known viruses for OpenVMS?   E                    Viruses and worms are common on personal computerseB                    because the operating systems involved, such asC                    the Microsoft MS-DOS, Windows 95, Windows 98 andeC                    Windows ME variants, do not particularly protecteB                    the operating system or the file system againstD                    hostile action by programs. Microsoft Windows NT,G                    Windows 2000 and Windows XP do implement protectionsrF                    for specific configurations and do implement memoryE                    protection models, but many users of these systemsiF                    choose to operate with full adminstrator access andG                    thus the available protections are entirely defeatedlF                    and entirely not relevent, and any program that canH                    activate itself or can cause the user to activate theJ                    code can subvert the operating system and take over theJ                    hardware, at which point the malicious code can do mostH                    anything it wishes, including hiding copies of itselfJ                    in other programs or in the file system, redistributingI                    itself via mail, IM, or network connections, or can be H                    used as a zombie in staging attacks on other systems.  F                    This is less likely with multi-user systems such asD                    OpenVMS, Unix, Linux, MVS and other platforms forI                    various reasons. First, the operating system runs in a F                    privileged mode in memory that is protected againstD                    modification by normal user programs. Any programD                    cannot simply take over the hardware as it can onF                    operating systems without security and particularlyD                    without memory page protections. Secondly, multi-D                    user systems can be set up so that non-privilegedF                    programs cannot modify system programs and files onH                    disk, and this is normal for most installations. BothJ                    of these protection schemes mean that traditional viralF                    infections don't work on these OSes. Third, typicalF                    applications and configurations tend to prevent theC                    uncontrolled execution of untrusted code as part F                    of received mail messages or web access; one of the                      5-2 r             0                    System Management Information        C                    central vulnerabilities of the Microsoft WindowsoF                    platform involves its intentionally easy ability toD                    dynamically (and transparently) activate code andD                    macros that are embedded within mail messages and%                    within data files.t  J                    It is possible for OpenVMS and other multi-user systemsH                    to become infected by viruses or worms, but to do so,F                    the program containing the virus must be run from aI                    user account that has amplified privileges. So long asiH                    the system administrator is careful that only trustedD                    applications are run from such accounts (and thisE                    is generally the case) and so long as there are no E                    OpenVMS system security breaches (due to maliciouseF                    operator activity, OpenVMS errors, or errors withinD                    trusted and privileged product packages) there isG                    no of modifications to the operating system or other >                    protected files from the virus or the worm.  F                    The FAQ maintainer is aware of a few (and very old)E                    DECnet worms that have affected OpenVMS systems onsG                    DECnet networks ("WANK" was one), but is aware of not?                    OpenVMS viruses that are loose in the field.s  C                    To protect against viruses and other attempts ataC                    system interference or misuse, please follow thetJ                    security recommendations in the OpenVMS Guide to SystemE                    Security. Additionally, you will want to keep yourdF                    OpenVMS ECOs current and you will want to apply allG                    mandatory ECO kits and any security MUPs for OpenVMSwE                    and OpenVMS products, and you will want to keep toeG                    OpenVMS releases with Prior Version Support (PVS) oraE                    with Current Version Support. (This is obviously atI                    general system maintenance recommendation, in additionmE                    to being a good system security recommendation-newdH                    security features and capabilities are implemented inI                    more recent OpenVMS releases, for instance. Details on F                    PVS releases are available over in Section 5.10.6.)B                    You may also want to consider optional softwareG                    products which can monitor your system for intrusiontI                    or infection attempts. Computer Associates (CA) offersmF                    various products in this area, as to other vendors.    J                                                                        5-3               0                    System Management Information        H                    Rocksoft offers the Veracity data integrity tool (forG                    info, send mail to demo@rocksoft.com). MD5 tools are G                    also available; see Section 5.30 for details on MD5.   C                    Tools to scan OpenVMS file systems for Microsoft B                    Windows infections are and have been available,E                    including a commercial package from Sophos , and a5D                    port of the open source Clam Antivirus scanner atE                    http://www.clamav.net/ and with an OpenVMS port aty?                    http://fafner.dyndns.org/~alexey/clamav.zip.o  C                    These scanning tools are particularly useful for H                    systems running Samba or Advanced Server (PATHWORKS),G                    as these servers tend to have a higher population ofeF                    files intended for Microsoft Windows systems users,D                    and as common virus and worm attacks can find andJ                    infect files on the file shares that these products canJ                    provide. These infections do not target OpenVMS itself,H                    though the OpenVMS server (and any other platform andH                    any other server capable of storing files for WindowsE                    systems) can silently host files containing common 0                    Microsoft Windows infections.  D           __________________________________________________________7           5.3  Sources of OpenVMS security information?e  J                    Where can I get information on OpenVMS system security?  6                    o  http://www.hp.com/go/openvms/doc  S                    o  http://www.blacksheepnetworks.com/security/resources/openvms/   D           __________________________________________________________8           5.4  How do I mount an ISO-9660 CD on OpenVMS?  H                    ISO-9660 support was added in the following releases:  &                    o  OpenVMS VAX V6.0  &                    o  OpenVMS AXP V1.5  H                    An add-on ISO-9660 kit was also available for OpenVMSH                    VAX V5.5, V5.5-1, V5.5-2, and V5.5-2H4. This requiresH                    the installation of the F11CD kit from the InfoServerF                    CD, from the Consolidated Distribution CD under theI                    InfoServer area, or the F11CD ECO kit. (Upgrades to V6 7                    and later are strongly recommended.)                       5-4 M  A          0                    System Management Information        I                    By default, OpenVMS senses the specific type of media. G                    If you are working with dual-format media-media that G                    uses both the ODS-2 and ISO-9660 formats on the same G                    CD-ROM-then MOUNT will first detect and then defaultIH                    to the ODS-2 format. If you wish to override this andE                    explicitly mount the media using ISO-9660, use theA                    command:   L                    $ MOUNT/MEDIA_FORMAT=CDROM  device-name[:] [volume-label]  D                    In most circumstances, you will not need nor will@                    you want to include an explicit /MEDIA_FORMATJ                    specification. For further information, please refer toJ                    the OpenVMS MOUNT Utility Manual. Particularly note theI                    information on the MOUNT /MEDIA_FORMAT and /UNDEFINED_n"                    FAT qualifiers.  D                    The MOUNT /UNDEFINED_FAT qualifier is of interestC                    because ISO-9660 media can be mastered on a widecC                    variety of operating system platforms, and these E                    platforms do not necessarily support the semantics I                    needed for files containing predefined record formats.UG                    The /UNDEFINED_FAT allows you to specify the defaultoG                    attributes for files accessed from volumes using thei#                    ISO-9660 format./  >                    An example which works for most CD-ROMs is:  V                    $ MOUNT/MEDIA_FORMAT=CDROM/UNDEFINED_FAT=STREAM:2048 DUA0: FREEWARE  E                    This particular MOUNT command forces access to theuH                    CD-ROM media using the ISO-9660 volume structure, andG                    the use of the MOUNT /UNDEFINED_FAT qualifier causestG                    any file whose file attributes are "undefined" to befJ                    returned with "stream" attributes with a maximum record                    length 2048.   B                    On OpenVMS, the ISO-9660 format is (internally)G                    considered to be the ODS-3 file structure, while therH                    High Sierra extensions to the standard are consideredA                    to be the ODS-4 file structure. The Rock Ridge E                    extensions are not currently available on OpenVMS.     J                                                                        5-5 e             0                    System Management Information        F                    For details on ODS-1 and ODS-2 file specifications,E                    see Kirby McCoy's VMS File System Internals Manual F                    (published by Digital Press, but potentially out of#                    print), and see:f  B                    o  http://pdp-11.trailing-edge.com/www/ods1.txt  B                    o  Look for the Freeware V5.0 directory ODS2 at<                       http://www.hp.com/go/openvms/freeware/  D           __________________________________________________________;           5.5  How do I extract the contents of a PCSI kit?   J                    A growing number of OpenVMS products are being providedH                    in PCSI (POLYCENTER Software Installation) kits whichI                    are installed using the PRODUCT INSTALL command. ThesegH                    are alternatives to or replacement for VMSINSTAL kitsG                    which were BACKUP savesets. PCSI kits are not BACKUPrI                    savesets and are structured differently from VMSINSTAL                     kits.  C                    If you want to extract product files from a PCSIeG                    kit, create a directory into which the kit should beY:                    expanded and use the following command:  G                    $ PRODUCT COPY prodname /SOURCE=[where-the-kit-is] - F                        /DEST=[destination-directory] /FORMAT=REFERENCE  B                    A PCSI kit file has a file specification of the"                    following form:  6                    DEC-VAXVMS-FORTRAN-V0603-141-1.PCSI  E                    In this example, "FORTRAN" is the "prodname". PCSI C                    will expand the kit files into the directory you G                    specify and subdirectories beneath such as [SYSEXE], F                    [SYSLIB], etc., reflecting the eventual destinationC                    of files found there. Most of the actual product F                    files (images, etc.) will be in the subdirectories.E                    In the top-level directory will be a file with the4J                    file type PCSI$DESCRIPTION that specifies where variousH                    files should go. For more details, see the POLYCENTERG                    Software Installation Developer's Guide for OpenVMS,]I                    which can be found in the OpenVMS documentation on the <                    Consolidated Online Documentation CD-ROM.                      5-6 l  (          0                    System Management Information      D           __________________________________________________________9           5.6  Emergency (Conversational) System Startup?   F                    If you need to perform system management operationsD                    on an OpenVMS system and cannot access the systemB                    through normal means-the password on the SYSTEMA                    username was forgetten and no other privilegedOF                    usernames are available, or one or more core systemD                    product authorization key (PAK) software licensesE                    are unavailable or expired-then you must perform al8                    conversational (emergency) bootstrap.  &                    Here are the steps:  G                    1  Halt the system. Exactly how this is done depends D                       on the specific system model: Depending on theI                       model, this can involve pressing the <HALT> button,eG                       entering <CTRL/P> on the console, or pressing theu1                       <BREAK> key on the console.   E                    2  At the console prompt, use a console command to D                       boot into the SYSBOOT utility. (SYSBOOT allowsH                       conversational changes to system parameters.) (TheE                       console syntax for the conversational bootstrapdH                       varies by system model and by system architecture-D                       this typically involves specifying a flag withH                       the lowest bit set. See Section 14.3.5 for related,                       details.) For example:  E                       On VAX, use one of the following three commandsBE                       depending on the particular model of VAX systemg                       involved:                          B/R5:1                       B/1o                       @GENBOO                          On Alpha:m  "                       b -flags 0,1  E                       If your system has a non-zero system root (such G                       as root SYSE, shown here), you will have to use aa<                       console command such as the following:  J                                                                        5-7    e          0                    System Management Information                               On VAX:                           B/E0000001#                       B/R5:E0000001pC                       @<console media procedure name varies widely>f                         On Alpha:r  "                       b -flags e,1  J                       On the IA-64 architecture systems, you can establishG                       and manage an EFI boot alias for a conversational D                       bootstrap as discussed in Section 14.3.5.1 andG                       in Section 14.3.10, or you can use VMS_LOADER.EFI I                       interactively as shown here. Of the core mechanisms G                       discussed in Section 14.3.5.1, the following uses F                       an EFI Shell command to perform a conversationalE                       bootstrap of root SYSE via the partition devicehG                       fsn:. There are alternative mechanisms available.   <                       fsn:\efi\vms\vms_loader.efi -flags e,1  B                       If your Alpha system has a hardware passwordG                       (various systems support a password that preventseH                       unauthorized access to the console), you will needF                       to know theis password and will need to enter itH                       using the LOGIN or similar command at the console.G                       If you get an "Inv Cmd" error trying to perform aaG                       conversational bootstrap, and you do not have the1E                       hardware console password for the console LOGIN F                       command, you are stuck-you will need to call forF                       hardware service for assistance in resetting theG                       hardware console password. The implementation andtH                       the syntax used for the console password mechanism2                       does vary by implementation.  F                    3  Once at the SYSBOOT prompt, request that OpenVMSH                       read the system startup commands directly from theE                       system console, that the window system (if any)wG                       not be started, and that OpenVMS not record thesecH                       particular parameter changes for subsequent system                       reboots:                        5-8 h  o          0                    System Management Information        '                       SET/STARTUP OPA0: )                       SET WINDOW_SYSTEM 0 *                       SET WRITESYSPARAMS 0                       CONTINUE  G                    4  At the $ prompt, the system will now be accepting J                       startup commands directly from the console. Type the1                       following two DCL commands:u                         $ SPAWN +                       $ @SYS$SYSTEM:STARTUP   F                    5  You should now see the dollar ($) prompt of DCL.  I                       The result of these two commands will be the normal D                       system startup, but you will be left logged inF                       on the console, running under a fully privilegedI                       username. Without the use of the SPAWN command, youeE                       would be logged out when the startup completes.   E                       Perform the task(s) required, such as resetting F                       the password on the SYSTEM username as describedI                       in Section 5.6.1 or registering one or more license G                       product authorization keys (PAKs) as described in $                       Section 5.6.2.  G                    6  Once you log out of this session, the system will H                       complete the startup and can be used normally. YouF                       can choose to reboot the system, but that is not                        necessary.  C                    Some system managers will suggest a method using D                    the UAFALTERNATE system parameter rather than theD                    SET/STARTUP OPA0: command shown. This approach isH                    not always available and is accordingly less commonlyH                    recommended, as there can easily be an alternate userD                    authorization database (SYS$SYSTEM:SYSUAFALT.DAT)G                    configured on the system. With a system manager thateF                    has configured an alternate SYSUAFALT.DAT file, theF                    UAFALTERNATE method will fail-well, assuming you doH                    not know the password of a privileged username stored3                    within SYSUAFALT.DAT, of course.c    J                                                                        5-9 l  n          0                    System Management Information        G                    The UAFALTERNATE system parameter is used to triggernG                    what is sometimes known as the console backdoor. ThefH                    OPA0: system console is critical to system operationsF                    and system security, and will allow access when theF                    SYSUAF system authorization database is unavailableG                    or corrupted, when core product license PAKs are notlI                    registered, expired or disabled (NOLICENSE errors), or I                    in various other cases of system failures. All this is H                    in addition to the role of the console in the displayD                    of certain system-critical event messages. AccessG                    to the OPA0: console has a security exposure that is F                    equivalent to direct access to the system hardware.  C                    When LOGINOUT detects an error (such as a SYSUAF C                    corruption, by a missing SYSUAF, missing product,F                    licenses, or other trigger), it will prevent accessF                    to the OpenVMS system from all terminals except theC                    system console. The OPA0: system console will begD                    allowed access, and the resulting process will beF                    fully privileged. Resetting the UAFALTERNATE systemI                    parameter-in the absence of an alternate SYSUAF systemsI                    authorization database-will cause the console backdoordE                    to be opened simply because LOGINOUT cannot locatecC                    SYS$SYSTEM:SYSUAFALT.DAT. When the authorizationeE                    database cannot be located, access will be grantedl)                    from the console only.d  C                    For further information on emergency startup ands@                    shutdown, as well as for the official OpenVMSJ                    documentation on how to change the SYSTEM password fromF                    the console in an emergency, please see the OpenVMSG                    System Manager's Manual in the OpenVMS documentationY                    set.h  D                    For information and recommendations on setting upE                    OpenVMS system security, please see the NCSC Class F                    C2 appendix of the Guide to OpenVMS System SecurityA                    manual, also in the OpenVMS documentation set.   J                    You can also use the conversational bootstrap techniqueG                    shown earlier (the steps until SET/STARTUP) to altersE                    various system parameters, as well. At the SYSBOOTs?                    prompt, you can enter new parameters values:                       5-10  O  V          0                    System Management Information        %                    SHOW MAXPROCESSCNTe                    SET . 64                     CONTINUEd  D                    The <.> is a shorthand notation used for the last@                    parameter examined within SYSGEN and SYSBOOT.  '           _____________________________ D           5.6.1  I've forgotten the SYSTEM password - what can I do?  D                    If you have forgotten or do not have the password@                    for the SYSTEM username, you must perform theH                    conversational bootstrap as described in Section 5.6,F                    and must enter the following commands once you have1                    reached the dollar ($) prompt:   S                    $ SET DEFAULT SYS$SYSTEM:  ! or wherever your SYSUAF.DAT resides_-                    $ RUN SYS$SYSTEM:AUTHORIZEt6                    MODIFY SYSTEM /PASSWORD=newpassword                    EXITt  @                    You have now reset the password on the SYSTEM                    username.  '           _____________________________ B           5.6.2  My product licenses have expired - what can I do?  G                    If you have a system with no licenses for OpenVMS or I                    for OpenVMS users and thus cannot log into the OpenVMSrF                    system normally, you should be able to log into theF                    console serial terminal-this is the terminal deviceE                    known as OPA0:-and perform the commands necessary.T  I                    For systems that are not configured with an accessable F                    console serial terminal-as can be the case with howB                    some DECwindows workstations are configured-youF                    must log in over the network or from a local serialB                    connection. If you cannot log in over a networkE                    connection (SET HOST, telnet, etc) or from anotheriE                    local serial terminal connection, you will have tonI                    halt the system and perform a conversational bootstrapnC                    as described in Section 5.6. You must then entereE                    licensing-related commands once the conversationalf?                    bootstrap has reached the dollar ($) prompt.o  J                                                                       5-11 o             0                    System Management Information        F                    Use the following DCL command to invoke a menu thatJ                    allows you to manage and to register new or replacement                     license PAKs:  +                    $ @SYS$UPDATE:VMSLICENSE   J                    You have now registered the license PAKs. Direct use ofH                    the DCL commands LICENSE and SHOW LICENSE and such is,                    also obviously available.  B                    If you wish to connect a serial console on yourG                    DECwindows workstation, please see Section 14.3.3.3,eD                    Section 14.3.6, Section 11.10, and Section 14.17.  H                    For information on troubleshooting DECwindows, please$                    see Section 11.5.  D           __________________________________________________________B           5.7  How do I change the node name of an OpenVMS System?  B                    The first step is to get a BACKUP of the systemE                    disk before making any changes-use the system diskdH                    backup procedures as documented in the OpenVMS SystemG                    Management Manual, making sure to use the proceduresr@                    and commands appropriate for the system disk.  H                    Changing the node name involves a number of steps-theJ                    node name tends to be imbedded in a number of different0                    data files around the system.  G                    o  Update the SCSNODE in MODPARAMS.DAT, and then run-D                       AUTOGEN as far as the SETPARAMS phase. (Do not"                       reboot yet.)  D                    o  Modify the DECnet node name. (NETCONFIG is theD                       DECnet Phase IV tool, and NET$CONFIGURE is the(                       DECnet-Plus tool.)  H                    o  Modify the host node name on the various queues inF                       the queue database. (each queue has a host name,I                       and it defaults to the SCS node name of the queue's E                       host system. See the command INIT/QUEUE/ON=node E                       for information.) Site-specific startup commandCE                       procedures can explicitly specify the (local or G                       even the current) node on the /ON parameter in an 3                       INIT/QUEUE/START/ON= command.t                      5-12                0                    System Management Information        C                    o  Modify the node name saved in any application I                       databases, or any local node-conditional operations G                       present in the site-specific system startup, etc. H                       (SEARCH for the node name, specifying all types of                       files.)e  I                    o  Use the AUTHORIZE utility command RENAME/IDENTIFIERaC                       to rename the SYS$NODE_oldnodename rightslist D                       identifier to match the new node name. (Do notE                       change the binary value of this identifier, and,4                       do not delete the identifier.)  F                       If you have erroneously deleted or duplicate theG                       identifier, you can locate existing references to H                       the binary identifier value using the Freeware DFUG                       package, and specifically the commands SEARCH/ACEdI                       and /OWNER. You must (re)create the correctly-namedeE                       identifier using the binary value that is oftendG                       stored in various Access Control List Entry (ACE) H                       structures and object owner fields associated withF                       files and objects present in the OpenVMS system.  G                    o  Reset any license PAKs that are restricted to the 9                       old node name to the new node name.A  J                    o  If the node name is part of a disk volume label, see#                       Section 5.13.i  F                    o  Reboot the node or-if in a VMScluster-reboot theG                       whole VMScluster. (This tends to catch any errorss#                       immediately.)i  H                    o  Modify the IP node name. (The TCP/IP Services toolF                       is UCX$CONFIG prior to V5.0, and is TCPIP$CONFIGC                       in V5.0 and later releases.) Note that TCP/IP C                       Services ties the IP host name to the currenteG                       SCSNODE value within its UCX$CONFIGURATION.DAT oreG                       TCPIP$CONFIGURATION.DAT database. Thus if SCSNODEuG                       is changed, the IP host name reconfiguration must.G                       occur, and the required reconfiguration can occur D                       only after a system reboot. Accordingly, it isC                       best to perform the TCP/IP Services host nameT<                       reconfiguration step after the reboot.  J                                                                       5-13 D  o          0                    System Management Information        H                    There are likely a few other areas where the nodenameJ                    will be stored. Local procedures and data files are oneG                    such example, and various sites will have the system I                    name loaded in the operator control panel via the OCP_ I                    TEXT console environment variable available at the SRM ;                    prompt on some Alpha systems is another.   F                    If the system is configured in a VMScluster and youG                    change either the SCSNODE or the SCSSYSTEMID-but noteF                    both values-then you will have to reboot the entireD                    VMScluster. (The VMScluster remembers the mappingC                    between these two values, and will assume that alD                    configuration problem has occured if a mismatchedE                    pair appears, and will refuse to let a node with as8                    mismatched pair join the VMScluster.)  G                    To calculate the correct SCSSYSTEMID value, multiply C                    the DECnet Phase IV area number by 1024, and addlD                    the DECnet Phase IV node number. For example, theI                    SCSSYSTEMID value for a DECnet node with address 19.22d7                    is 19478. ((19 * 1024) + 22 = 19478)o  E                    This may well have missed one or two configurationlI                    tools (or more!) that are needed at your site-the node J                    name tends to get stored all over the place, in layered5                    products, and in local software...e  >                    Also see Section 15.6.3 and Section 15.6.4.  D           __________________________________________________________C           5.8  Why doesn't OpenVMS see the new memory I just added?   F                    When adding memory to an OpenVMS system, you shouldH                    check for an existing definition of the PHYSICALPAGESC                    (OpenVMS VAX) or PHYSICAL_MEMORY (OpenVMS Alpha) F                    parameter in the SYS$SYSTEM:MODPARAMS.DAT parameterH                    database, use a text editor to reset the value in theF                    file to the new correct value as required, and then1                    perform the following command:n  @                    $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT FEEDBACK  A                    This AUTOGEN command will reset various systemiF                    parameters based on recent system usage (FEEDBACK),D                    and it will reset the value for the PHYSICALPAGESF                    parameter to the new value. It will also reboot the"                    OpenVMS system.                      5-14o e  w          0                    System Management Information        H                    PHYSICALPAGES and PHYSICAL_MEMORY can also be used toH                    deliberately lower the amount of memory available forF                    use by OpenVMS. This ability can be useful in a fewH                    specific circumstances, such as testing the behaviourC                    of an application in a system environment with aeH                    particular (lower) amount of system memory available.  I                    PHYSICALPAGES and PHYSICAL_MEMORY can be set to -1 (on J                    OpenVMS Alpha) or (better and simpler) the entry can beH                    removed from the MODPARAMS.DAT file, to indicate that7                    all available memory should be used.   D           __________________________________________________________C           5.9  How do I change the text in a user's UIC identifier?e  <                    The text translations of the numeric UserE                    Identification Code (UIC) are based on identifiersEF                    present in the OpenVMS rightslist. Documentation onH                    this area is included in the _Guide to OpenVMS System$                    Security_ manual.  E                    To control the identifiers shown for a user's UIC,_G                    you use AUTHORIZE. Each user has an associated group J                    identifier, and an identifier specific to the user. And6                    each user should have a unique UIC.  G                    To alter the text of a user or group identifier, uset$                    commands such as:  -                    $ RUN SYS$SYSTEM:AUTHORIZEi:                    UAF> rename/ident oldgroupid newgroupid9                    UAF> rename/ident olduserid  newuseridh  H                    If you should find yourself missing an identifier forH                    a particular user, you can add one for the user's UIC+                    using a command such as:c  B                    UAF> add/ident/value=uic=[group,user] newuserid  D                    The UIC user identifier text is assigned when theH                    username is created, and is the text of the username.F                    The UIC group group identifier is assigned when theF                    first username is created in the UIC group, and theF                    text is based on the account name specified for theE                    first user created in the group. The value of thissH                    identifier is [groupnumber, 177777]. To add a missing@                    group identifier, use an asterisk as follows:  J                                                                       5-15 m             0                    System Management Information        @                    UAF> add/ident/value=uic=[group,*] newgroupid  I                    You may find cases where an identifier is missing fromtF                    time to time, as there are cases where the creationE                    of a UIC group name identifier might conflict withsC                    an existing username, or a user identifier might:I                    conflict with an existing group identifier. When these-I                    conflicts arise, the AUTHORIZE utility will not create H                    the conflicting group and/or user identifier when the'                    username is created.   I                    You can can add and remove user-specified identifiers, C                    but you should avoid changing the numeric valuestG                    associated with any existing identifiers. You should F                    also avoid reusing UICs or identifiers when you addG                    new users, as any existing identifiers that might beRJ                    present on objects in the system from the old user willH                    grant the same access to the new user. Please see the/                    security manual for details.s  D           __________________________________________________________;           5.10__What_are_the_OpenVMS_version upgrade paths?e  9           5.10.1  OpenVMS Alpha Upgrade (or Update) Pathsi  1                                              Note   D                       Upgrade path information here has occasionallyC                       been found to be wrong. Information here does G                       not reflect cluster rolling upgrade requirements; D                       see Section 5.10.4 for related rolling upgradeC                       information; versions permissible for rollingtE                       upgrades can be and often are more constrained.lB                       When upgrade information here conflicts withD                       the official documentation, please assume thatD                       the information here is wrong. Corrections and;                       updates to this material are welcome.                                   5-16                0                    System Management Information                            From V1.0,e/                        you can upgrade to V1.5.r*                    From V1.5, or V1.5-1H1,/                        you can upgrade to V6.1.h                    From V6.1, /                        you can upgrade to V6.2.m&                    From V6.1, or V6.2,/                        you can upgrade to V7.0. <                    From V6.1, V6.2, V6.2-1H(1,2,3), or V7.0,/                        you can upgrade to V7.1.                     From V6.2,tI                        you can update to V6.2-1H1, V6.2-1H2, or V6.2-1H3. J                    From V6.2, V6.2-1H(1,2,3), V7.1, V7.1-1H(1,2), or V7.2,!                        to V7.2-1.t*                    From V6.2, ... or V7.2,+                        to V7.2-1H1, to 7.3.mA                    From V7.1, you can update to V7.1-1H(1,2), ...u+                        to V7.2-1H1, to 7.3.oA                    From 7.2, 7.2-1, 7.2-1H1, 7.2-2, 7.3 or 7.3-1,c0                        you can upgrade to V7.3-2C                    From V7.3, V7.2-2, V7.2-1H1, V7.2-1, and V7.1-2,60                        you can upgrade to V7.3-1                    From V7.3-1,,<                        you can upgrade to V7.3-2 or to V8.2.)                    From V7.3-1 or V7.3-2,t/                        you can upgrade to V8.2.1'                    From V7.3-2 or V8.2, /                        you can upgrade to V8.3.   G                    Some typical OpenVMS Alpha upgrade (or update) paths                     are:t                          J                                                                       5-17 u  n          0                    System Management Information        I                    V1.0 -> V1.5 -> V6.1 -> (V6.2, V7.0, V7.1, V7.2, V7.3)3E                    V1.5-1H1 -> V6.1 -> (V6.2, V7.0, V7.1, V7.2, V7.3) #                    V6.2 -> V6.2-1H3 !                    V6.2 -> V7.2-1e                    V6.2 -> V7.3S)                    V6.2-1H(1,2,3) -> V7.1e+                    V6.2-1H(1,2,3) -> V7.2-1 9                    V6.2 through 7.1-1H2 inclusive -> V7.3 !                    V7.1 -> V7.1-2 !                    V7.1 -> V7.2-1s)                    V7.1-1H(1,2) -> V7.1-2 )                    V7.1-1H(1,2) -> V7.2-17#                    V7.1-2 -> V7.3-1 #                    V7.2 -> V7.2-1H1 )                    V7.2 -> V7.3 -> V7.3-1 +                    V7.2-1 -> (V7.3, V7.3-1)-3                    V7.2-2 -> (V7.3, V7.3-1, V7.3-2) +                    V7.3 -> (V7.3-1, V7.3-2) +                    V7.3-1 -> (V7.3-2, V8.2) )                    V7.3-2 -> (V8.2, V8.3)   H                    Note that OpenVMS Alpha V7.0 does not include supportH                    for hardware and/or configurations first supported inJ                    OpenVMS Alpha V6.2-1H1, V6.2-1H2, or V6.2-1H3; one must;                    upgrade to OpenVMS Alpha V7.1, or later.   C                    One cannot update directly to a V6.2-1Hx Limited G                    Hardware Release (LHR) from any release prior to the D                    baseline V6.2 release. The same prohibition holdsC                    for performing updates directly to V7.1-1Hx fromiG                    any release prior to V7.1-this is not supported, andsF                    does not produce the expected results. The LHR kitsG                    can, however, be directly booted and can be directlylI                    installed, without regard to any operating system thate7                    might be present on the target disk.l  I                    Users of OpenVMS Alpha V7.1-1H1, V7.1-1H2, V7.2-1H1 oriG                    other hardware are encouraged to upgrade to the nextxH                    available non-hardware-release, and should preferablyI                    upgrade to the current or to a supported OpenVMS Alphai                    release.o                          5-18a e  r          0                    System Management Information        D                    OpenVMS Alpha updates for LHRs (through V7.1-1Hx)E                    require the use of VMSINSTAL for the update. These2J                    LHR releases use PCSI for the installation, but not forI                    the update. Non-LHR releases use PCSI for installs andr                    upgrades.  C                    OpenVMS Alpha V7.1-2 and later use PCSI for LHRsrC                    and for OpenVMS upgrades and for all OpenVMS ECO G                    kit installations; V7.1-2 and later use upgrades andSH                    not updates. VMSINSTAL OpenVMS ECO kits (updates) areG                    not used on OpenVMS Alpha V7.1-2 and later; prior to I                    V7.1-2, VMSINSTAL-based ECO (update) kits are used forN                    OpenVMS.i  '           _____________________________ +           5.10.2  OpenVMS I64 Upgrade Paths   1                                              NoteO  D                       Upgrade path information here has occasionallyC                       been found to be wrong. Information here doesdG                       not reflect cluster rolling upgrade requirements;eD                       see Section 5.10.4 for related rolling upgradeC                       information; versions permissible for rolling E                       upgrades can be and often are more constrained.0B                       When upgrade information here conflicts withD                       the official documentation, please assume thatD                       the information here is wrong. Corrections and;                       updates to this material are welcome.                       From V8.2, 8                        you can upgrade to V8.2-1 or V8.3                    From V8.2-1,n.                        you can upgrade to V8.3  J                    Some typical OpenVMS I64 upgrade (or update) paths are:  )                    V8.2 -> V8.2-1 -> V8.3o  D                    OpenVMS I64 V8.2 is the first production release.D                    OpenVMS I64 V8.0 and V8.1 were intended for earlyH                    adopters of OpenVMS on Integrity servers, and are not8                    considered to be production releases.  J                                                                       5-19               0                    System Management Information        G                    To utilize OpenVMS I64 V8.2, you must perform a full-E                    installation of V8.2. No supported upgrade path tooH                    V8.2 is available from previous releases; there is noF                    upgrade from OpenVMS I64 E8.2, nor from the earlier)                    V8.1 or V8.0 releases.b  '           _____________________________ 3           5.10.3  OpenVMS VAX Release Upgrade Paths-  1                                              Notee  D                       Upgrade path information here has occasionallyC                       been found to be wrong. Information here doesNG                       not reflect cluster rolling upgrade requirements;rD                       see Section 5.10.4 for related rolling upgradeC                       information; versions permissible for rollingsE                       upgrades can be and often are more constrained.nB                       When upgrade information here conflicts withD                       the official documentation, please assume thatD                       the information here is wrong. Corrections and;                       updates to this material are welcome.   O                    From V5.0 through V5.4-3 inclusive, one can upgrade to V5.5.dM                    From V5.5, V5.5-1, or V5.5-2HW, one can upgrade to V5.5-2.oI                    From V5.5, V5.5-1, or V5.5-2, one can upgrade to V6.0.dK                    From V5.5-2, V5.5-2H4, or V6.0, one can upgrade to V6.1. ?                    From V6.0, or V6.1, one can upgrade to V6.2. ?                    From V6.1, or V6.2, one can upgrade to V7.0.dE                    From V6.1, V6.2, or V7.0, one can upgrade to V7.1. R                    From V6.1, one can upgrade to V7.3 (with VAXBACK ECO for V6.1).  >                    Some typical OpenVMS VAX upgrade paths are:  E                    V5.x -> V5.5 -> V6.0 -> V6.2 -> (V7.1, V7.2, V7.3) %                    V5.5-2HW -> V5.5-2 G                    V5.5-2, or V5.5-2H4 -> V6.1 -> (V6.2, V7.0, or V7.1)0@                    V6.1 -> V6.1 with VAXBACK ECO -> (V7.2, V7.3)                    V6.2 -> V7.20                    V6.2 -> V7.3   J                    Note that OpenVMS VAX V6.0 does not include support forH                    hardware and/or configurations first added in OpenVMSF                    VAX V5.5-2H4, one must upgrade to OpenVMS VAX V6.1.  J                    Note that OpenVMS VAX V5.5-2HW is a pre-release versionI                    of V5.5-2. Any system running it should be upgraded to0$                    V5.5-2, or later.                      5-20)               0                    System Management Information        H                    If you attempt a direct upgrade from OpenVMS VAX V6.1D                    to V7.2 or later without having first applied theH                    VAXBACK ECO kit to your V6.1 system, you will receive$                    an error message:  G                    %BACKUP-E-INVRECTYP, invalid record type in save sety  C                    and the upgrade will fail. Acquire and apply theaI                    VAXBACK ECO kit for OpenVMS VAX V6.1. OpenVMS VAX V6.2eH                    and later do not require an application of an ECO for0                    an upgrade to V7.2 and later.  '           _____________________________p7           5.10.4  OpenVMS Cluster Rolling Upgrade Paths   F                    Rolling Upgrades permit the OpenVMS Cluster and theD                    applications to remain available while individualG                    systems are being upgraded to a new OpenVMS release.   B                    Rolling Upgrades require multiple system disks.  ?                    OpenVMS Cluster Rolling Upgrades for OpenVMSO@                    Alpha, OpenVMS I64 and OpenVMS VAX may (will)D                    have architecture-specific, or additional upgradeG                    requirements or prerequisites, and have requirementseI                    around which versions and architectures of OpenVMS canhH                    coexist within a OpenVMS Cluster than what are listed                    here.  G                    For specific details on Rolling Upgrades, please see F                    the OpenVMS Upgrade and Installation Manual for theG                    particular release, and the OpenVMS Software ProducthC                    Descriptions for OpenVMS and for OpenVMS Clustere                    software:  9                    o  http://h18000.www1.hp.com/info/spd/a  H                       OpenVMS typically uses SPD 25.01.xx, SPD 41.87.xx,'                       and SPD 82.35.xx.   F                    for further details on the Rolling Upgrade, and for'                    support information.V    J                                                                       5-21 a  t          0                    System Management Information      '           _____________________________ 1           5.10.5  OpenVMS VAX Manual Organization/  F                    The documentation for older releases of OpenVMS VAXF                    was comprised of various platform-specific manuals,F                    manuals that include instructions that are specificD                    to installing and upgrading on the particular VAXB                    platform. These older manuals can be useful forD                    learning platform- or console-specific operationsE                    or requirements for the particular (and older) VAXl                    platform.  H                    There is far less console command syntax, and consoleI                    storage media variability, among the more recent AlphamH                    and Integrity processors. The newer platform operatorD                    and management interfaces are far more consistent-                    across the platform lines.   '           _____________________________oA           5.10.6  OpenVMS Product Version and Support Informationp  E                    For information on Prior Version Support (PVS) and C                    Mature Product Support (including information on D                    support end dates for OpenVMS and various layeredC                    products), please see the support resources link H                    available at the main OpenVMS website or the services@                    links available at the main services website:  3                    o  http://www.hp.com/go/openvms/   3                    o  http://www.hp.com/go/servicesF  H                    And see the following links, with the caveat that theC                    direct "/hps" links shown here may become stale:o  :                    o  http://www.hp.com/hps/os/os_pvs.html  ;                    o  http://www.hp.com/hps/os/os_ovms.html   I                    For information on the supported and required versions H                    of layered products, and the minimum required layeredJ                    product versions for various configurations, please seeF                    the Software Rollout Report (SWROLL), available at:  B                    o  http://h71000.www7.hp.com/openvms/os/swroll/  I                    For additional related information, see Section 2.6.1.l                      5-22t /  w          0                    System Management Information        E                    For information on the release history of OpenVMS,rE                    including information on the code names of variousr3                    releases and the major features:   G                    o  http://www.openvms.compaq.com/openvms/os/openvms- *                       release-history.html  G                    Additional release history information, as well as aSH                    variety of other trivia, is available in the VAX 20th$                    anniversary book:  L                    o  http://www.openvms.compaq.com/openvms/20th/vmsbook.pdf  '           _____________________________ ;           5.10.7  OpenVMS Alpha and I64 Upgrade Terminologyh  C                    OpenVMS Alpha and OpenVMS I64 use the POLYCENTERoJ                    Software Product Install Utility, occasionly refered toG                    as SPIU and rather more commonly known as PCSI. PCSI I                    is a component of the OpenVMS operating system, and is G                    available on OpenVMS VAX, OpenVMS Alpha, and OpenVMSc                    I64.s  D                    The following terms apply to OpenVMS Alpha and toE                    OpenVMS I64 Upgrades and Installations using PCSI:S  J                    o  UPDATE: Typically used for Limited Hardware ReleasesF                       (LHR) releases. Performed via VMSINSTAL. AppliesG                       only to the OpenVMS release that the LHR is basednJ                       on, or to an intermediate LHR. (eg: V7.1-1H2 appliesD                       only to V7.1-1H1 and to V7.1, not to any otherE                       releases.) LHRs within a series are cumulative, H                       containing all files and features of previous LHRs)                       in the same series.d  E                       VMSINSTAL-based Updates and VMSINSTAL-based ECOfG                       kits are not generally used to upgrade OpenVMS oneI                       releases of OpenVMS Alpha V7.1-2 and later, nor aretH                       thse used on OpenVMS I64; only PCSI-based UpgradesH                       and Installs are used. VMSINSTAL remains availableI                       for other uses and other products; for upgrades anduJ                       installations of products other than OpenVMS itself.    J                                                                       5-23    i          0                    System Management Information        I                    o  UPGRADE: Performed via PCSI. Upgrades can typically E                       be applied directly to a release-specific range F                       of earlier OpenVMS releases. The product releaseI                       documentation specifies the prior OpenVMS releases; A                       if your release is not one of the specified D                       releases, you will have to perform one or moreG                       additional upgrades (through intermediate OpenVMS J                       releases) to reach one of the prerequisite releases.  H                    o  INSTALL: Performed via PCSI. With an installation,D                       no existing version of the operating system isI                       assumed present, nor are any files from any copy ofsJ                       the operating system might be present preserved, andJ                       the entire contents of the target disk are destroyed0                       via a disk initialization.  E                    o  PRESERVE: Performed via PCSI. Otherwise similariD                       to an installation, this option skips the diskE                       reinitialization. User files on the target diskoH                       are preserved. Any existing operating system files7                       on the target disk are clobbered.   I                    o  LHR: Limited Hardware Release. LHRs are specific toeJ                       and are targeted at new hardware configurations, andJ                       are not shipped to customers with support contracts.H                       At least one LHR kit must be specifically acquiredE                       when purchasing new hardware, new hardware thatdF                       is not (yet) supported by any mainline (non-LHR)F                       release. LHRs have an "H" in the OpenVMS version>                       string, indicating a "Hardware" release.  J                       You will not generally want to continue using an LHRI                       once a subsequent OpenVMS release is available; youaG                       will want to upgrade off the LHR at your earliestu"                       convenience.  J                    For minimum OpenVMS versions for various platforms, see                     Section 2.12.                                5-24  e             0                    System Management Information      D           __________________________________________________________J           5.11  Why do I have a negative number in the pagefile reservable                 pages?  C                    Seeing a negative number in the reservable pagesrH                    portion of the SHOW MEMORY/FULL command can be normalF                    and expected, and is (even) documented behaviour. AF                    pagefile with a negative number of reservable pagesI                    is overcommitted, which is generally goodness assuming_I                    that every process with reserved pages does not try tovH                    occupy all of the reserved pagefile space at the same                    time.  E                    To understand how the pagefile reservation process J                    works, think about how a traditional bank operates whenI                    accepting customer deposits and making loans. It's thenI                    same idea with the pagefile space. There is less moneyiJ                    in the bank vault than the total deposits, because muchF                    of the money has been loaned out to other customersG                    of the bank. And the behaviour parallels that of the I                    pagefile down to the problems that a "run on the bank" G                    can cause for banking customers. (Though there is no C                    deposit insurance available for pagefile users.)   D                    If all of the running applications try to use theJ                    reserved space, the system manager will need to enlargeH                    the pagefile or add one or more additional pagefules.  >                    To determine if the pagefile is excessivelyD                    overcommitted, watch for "double overcommitment"-F                    when the reservable space approaches the negatationB                    of the available total space-and watch that theG                    total amount of free space available in the pagefilerJ                    remains adequate. If either of these situations arises,;                    additional pagefile storage is required.o  H                    Additional pagefile information: Additional pagefilesF                    can typically be created and connected on a runningJ                    OpenVMS system. New processes and new applications willJ                    tend to use the new pagefile, and existing applicationsH                    can be restarted to migrate out of the more congestedI                    pagefiles. Pagefiles are generally named PAGEFILE.SYS,,E                    and multiple pagefiles are generally configured on G                    separate disk spindles to spread the paging I/O load C                    across the available disk storage. When multiple I                    pagefiles are present on recent OpenVMS versions, each   J                                                                       5-25               0                    System Management Information        I                    pagefile file should be configured to be approximately >                    the same total size as the other pagefiles.  D                    For additional information on pagefile operationsB                    and related commands, see the system managementD                    and performance management manuals in the OpenVMS%                    documentation set.   F                    With OpenVMS V7.3 and later, the displays have beenB                    changed and these negative values are no longer                    visible.i  D           __________________________________________________________B           5.12  Do I have to update layered products when updating                 OpenVMS?  G                    The Software Public Rollout Reports for OpenVMS list E                    the current and future availability of HP software E                    products shipping on the OpenVMS Software ProductslH                    Library kits (CDROM consolidations) for OpenVMS AlphaI                    and/or OpenVMS VAX. Specifically, the required minimum_;                    versions for product support are listed..  D                    Comprehensive Public Rollout Information, listingJ                    previous product versions as well as currently shippingE                    versions, has been compiled into a separate set ofsF                    reports. The product information is grouped to show,                    Operating System support.  F                    You may or may not be able to use older versions ofH                    local applications, third-party products, and variousH                    HP OpenVMS layered products with more recent versionsF                    of OpenVMS. User-mode code is expected to be upwardG                    compatible. Code executing in a privileged processorlE                    mode-typically either executive or kernel mode-mayoD                    or may not be compatible with more recent OpenVMS                    versions.  F                    These Software Rollout (SWROLL) Reports are updated)                    regularly. Please see:o  B                    o  http://h71000.www7.hp.com/openvms/os/swroll/  >                    For related information, see Section 2.6.1.                      5-26     m          0                    System Management Information      D           __________________________________________________________;           5.13  How do I change the volume label of a disk?   I                    Dismount the disk, and mount it privately. If the disk)J                    is mounted by more than one node in an OpenVMS Cluster,G                    dismount it from all other nodes. If this disk is an J                    OpenVMS system disk, shut down all other nodes that are/                    bootstrapped from this disk.a  I                    Issue the SET VOLUME/LABEL command, specifying the new_                    label.   F                    On OpenVMS V6.0 and later, issue the following PCSIG                    command to reset the label information stored within J                    the PCSI database to reflect the new disk volume label:  =                    $ PRODUCT REGISTER VOLUME old-label device   I                    Locate any references in the system startup (typically H                    including the disk MOUNT commands) and any DISK$labelB                    references in application files, and change the,                    references appropriately.  B                    If this is a system disk (for the host or for aF                    satellite), also check the DECnet MOP or LANCP bootJ                    database, as well as any references to the disk created*                    by CLUSTER_CONFIG*.COM.  H                    If Compaq Analyze is in use, check the system startupB                    procedures for the Compaq Analyze tool. CertainG                    versions of Compaq Analyze will record specific disk ?                    volume labels within the startup procedures.   2                    Remount the disk appropriately.  D           __________________________________________________________4           5.14  How can I set up a shared directory?  G                    To set up a shared directory-where all files createdoD                    in the directory are accessible to the members ofI                    specified group of users-you can use an access control 0                    list (ACL) and an identifier.  D                    The following also shows how to set up a resourceF                    identifier, which further allows the disk resourcesH                    to be charged to the specified identifier rather thanF                    each individual user. (If you don't want this, thenH                    omit the attributes option on the identifier creationG                    and omit the entry added in the disk quota database.a  J                                                                       5-27               0                    System Management Information        A                    Add an identifier using the AUTHORIZE utility:   D                    ADD/IDENTIFER/ATTRIBUTES=RESOURCE groupidentifier  G                    Grant the identifier to each user in the group using                     AUTHORIZE:t  <                    GRANT/IDENTIFIER groupidentifier username  I                    If disk quotas are in use, add an entry via SYSMAN for                     each disk:   2                    DISKQUOTA ADD groupidentifier -<                      /PERMQUOTA=pq/OVERDRAFT=od/DEVICE=ddcu:  I                    Set the shared directory to have an ACL similar to theRG                    following using the SET SECURITY (V6.0 and later) ort<                    SET ACL (versions prior to V6.0) command:  9                    (DEFAULT_PROTECTION,S:RWED,O:RWED,G,W)e@                    (IDENTIFIER=groupidentifier,OPTIONS=DEFAULT,-6                      ACCESS=READ+WRITE+EXECUTE+DELETE)1                    (IDENTIFIER=groupidentifier, --6                      ACCESS=READ+WRITE+EXECUTE+DELETE)<                    (CREATOR,ACCESS=READ+WRITE+ACCESS+DELETE)  H                    If there are files already resident in the directory,I                    set their protections similarly. (The OPTIONS=DEFAULT,o@                    DEFAULT_PROTECTION, and CREATOR ACEs apply to                     directories.)  C                    The default protection mask is used to establishIG                    the default file protection mask, this mask does not J                    prevent the users holding the specified groupidentifierJ                    from accessing the file(s), as they can access the fileF                    via the explicit identifier granting access that is&                    present in the ACL.  D                    For further information, see the OpenVMS Guide toG                    System Security Manual, specifically the sections onoB                    ACLs and identifiers, and resource identifiers.                          5-28o               0                    System Management Information      D           __________________________________________________________@           5.15  Why do I get extra blank pages on my HP Printer?  H                    For information on configuring telnet print symbiont,I                    on device control libraries such as SYSDEVCTL.TLB, andsJ                    for ways of dealing with the extra blank pages that canG                    arise on various HP printers, please see the OpenVMSoH                    Ask The Wizard area, starting particularly with topic                    (1020):  H                    o  http://www.hp.com/go/openvms/wizard/ (retired; use"                       ITRC forums)  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the availablenF                    ATW Wizard.zip archive, please see Section 3.8. ATWF                    has been superceded (for new questions) by the ITRCD                    discussion forums; the area remains available for                    reference.   D                    There are a variety of discussions of this and ofF                    related printing topics in the Ask The Wizard area,/                    in addition to topic (1020).   )                    Also see Section 5.34.a  D           __________________________________________________________F           5.16  Drivers and Configuration of New Graphics Controllers?  ?                    This section contains information on varioushG                    graphics controllers supported by OpenVMS Alpha, and F                    specifically information on where and how to obtainF                    device drivers for specific early OpenVMS releases-E                    device drivers for controllers are integrated intotB                    and shipped with OpenVMS Alpha, but versions ofH                    these device drivers are sometimes made available for5                    specific earlier OpenVMS releases.s  '           _____________________________ )           5.16.1  The ELSA GLoria SynergyA  I                    On OpenVMS Alpha V7.1-2, V7.2, and V7.2-1, acquire thebF                    appropriate GRAPHICS PCSI kit, and all prerequisite$                    OpenVMS ECO kits:  4                    o  VMS712_GRAPHICS-V0300 or later  3                    o  VMS72_GRAPHICS-V0100 or later   J                                                                       5-29               0                    System Management Information        4                    o  VMS712_GRAPHICS-V0300 or later  J                    The ELSA GLoria Synergy is the PBXGK-BB; the PowerStormF                    3D10T. Please ensure you have the most current ECOsE                    for this and other graphics controllers installed;7G                    check for and install the current GRAPHICS kit. (SeeoH                    Section 4.3.2 for some unexpectedly related details.)  H                    On OpenVMS Alpha V7.2-1, the files necessary for thisF                    graphics controller are located in the distribution$                    CD-ROM directory:  ,                    DISK$ALPHA0721:[ELSA.KIT]  A                    Also check for any available (later) ECO kits.   C                    An earlier kit (ALP4D20T01_071) (for V7.1, V7.1- F                    1H1, and V7.1-1H2) was once available, but has beenC                    superceded and is not recommended. Use of V7.1-2 F                    or later (and use of one the above GRAPHICS kits as<                    required) is typically the best approach.  F                    OpenVMS V7.2-2 and later mainline releases directly*                    support the controller.  G                    Additional information is available in topics (3419)l9                    and (5448) in the Ask The Wizard area:   H                    o  http://www.hp.com/go/openvms/wizard/ (retired; use"                       ITRC forums)  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the available.F                    ATW Wizard.zip archive, please see Section 3.8. ATWF                    has been superceded (for new questions) by the ITRCD                    discussion forums; the area remains available for                    reference.r  I                    Support for the ELSA GLoria Synergy is integrated intoe6                    all current OpenVMS Alpha releases.                            5-30o n  e          0                    System Management Information      '           _____________________________ 0           5.16.2  PowerStorm 300, PowerStorm 350  @                    The PowerStorm 300 is the PBXGD-AC, while the2                    PowerStorm 350 is the PBXGD-AE.  G                    For support of the PowerStorm 300 and PowerStorm 350 J                    graphics controllers, acquire and install the following&                    available ECO kits:  ,                    For OpenVMS Alpha V7.1-2:  =                    o  DEC-AXPVMS-VMS712_P350-V0100-4 or later   A                    o  DEC-AXPVMS-VMS712_GRAPHICS-V0300-4 or later0  ,                    For OpenVMS Alpha V7.2-1:  =                    o  DEC-AXPVMS-VMS721_P350-V0100-4 or laterr  A                    o  DEC-AXPVMS-VMS721_GRAPHICS-V0300-4 or laterS  D                    Support for the PowerStorm 300 and PowerStorm 350I                    series graphics controllers is integrated into current *                    OpenVMS Alpha releases.  '           ______________________________2           5.16.3  PowerStorm 3D30, PowerStorm 4D20  F                    PowerStorm 3D30 (PBXGB-AA), PowerStorm 4D20 (PBXGB-H                    CA) information is available in Ask The Wizard topics*                    including topic (2041):  H                    o  http://www.hp.com/go/openvms/wizard/ (retired; use"                       ITRC forums)  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the available_F                    ATW Wizard.zip archive, please see Section 3.8. ATWF                    has been superceded (for new questions) by the ITRCD                    discussion forums; the area remains available for                    reference.c      J                                                                       5-31               0                    System Management Information      '           _____________________________            5.16.4  Radeon 7500a  I                    Install the current GRAPHICS ECO kit for OpenVMS AlphavI                    V7.2-2 or V7.3-1 for support of the Radeon 7500 series 4                    PCI and AGP graphics controllers.  F                    Support for this controller (without an ECO kit) isG                    first integrated into and available in OpenVMS Alpha E                    V7.3-2. (Please do always install the most currentaH                    GRAPHICS ECO kit whenever one is available, however.)  D           __________________________________________________________C           5.17  How can I acquire OpenVMS patches, fixes, and ECOs?t  G                    You can acquire and download kits containing OpenVMS.H                    fixes (ECOs) for various releases, as well as relatedD                    support information, via the ITRC support center:  -                    o  http://www.itrc.hp.com/s  <                    o  ftp://ftp.itrc.hp.com/openvms_patches/  E                    Some systems with Internet firewalls may/will have_E                    to use passive mode FTP to access the above sites.pJ                    Assuming recent/current versions of the TCP/IP Services=                    package, the DCL FTP command necessary is:s  F                    $ DIRECTORY/FTP/ANONYMOUS/PASSIVE ftp.itrc.hp.com::  I                    You can subscribe to an email notification list at ther                    ITRC site.   H                    For a list of OpenVMS ECO kits recently released, you                    can use:/  J                    o  http://Eisner.DECUS.org/conferences/OpenVMS-patches_                        new_1.HTML  E                    Examples and ECO kit installation instructions areeB                    included in the cover letter. For ECO kit emailD                    notifications, lists of available ECO kits, coverG                    letters and other associated documentation, look in:R  -                    o  http://www.itrc.hp.com/V  <                    o  ftp://ftp.itrc.hp.com/openvms_patches/  G                    For additional information, please see Section 5.17.e                      5-32e .  L          0                    System Management Information        F                    Do NOT attempt to install a VMSINSTAL-based OpenVMSC                    ECO kit on OpenVMS Alpha V7.1-2 and later. WhilevE                    VMSINSTAL itself remains available, it is not used G                    for OpenVMS Alpha ECO kits starting in OpenVMS Alpha F                    V7.1-2. OpenVMS Alpha V7.1-2 and later use PCSI for$                    OpenVMS ECO kits.  I                    See Section 5.30 for information on ECO kit checksums.S  D           __________________________________________________________9           5.18  How do I move the queue manager database?O  B                    To move the location of the queue database, the?                    SYS$QUEUE_MANAGER.QMAN$QUEUES and SYS$QUEUE_ J                    MANAGER.QMAN$JOURNAL files, to a disk that is fast(er),J                    has plenty of free space, and that is not heavily used.F                    If the queue database is on a (busy) OpenVMS systemD                    disk, you can and probably should move it off the7                    system disk to another disk spindle.   .                    To move the queue database:  H                    1  Checkpoint the journal file. This reduces the fileJ                       size to the in-memory database size. This will cause&                       the noted delay.  2                       $ RUN SYS$SYSTEM:JBC$COMMAND+                       JBC$COMMAND> DIAG 0 7u  ,                    2  Stop the queue manager  2                       $ STOP/QUEUE/MANAGER/CLUSTER  J                    3  Backup the .QMAN$QUEUES and .QMAN$JOURNAL files from6                       the present location for safety.  V                       $ backup SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$*  DISK:[DIR]  D                    4  Create a new directory for the queue database.F                       Insure that this disk is accessible to all nodesI                       that can run the queue manager. If the /ON list foreF                       the queue manager is "/ON=(*)", the disk must be;                       available to all nodes in the clusterA  3                       $ CREATE/DIR fast_disk:[qman]n  J                                                                       5-33 E  M          0                    System Management Information        J                    5  Copy the .QMAN$QUEUES and .QMAN$JOURNAL files to the#                       new directory   Z                       $ copy SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$*  fast_disk:[qman]  4                    6  Delete the old queue database.  L                       $ DELETE SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$*;*  C                    7  Restart the queue manager pointing to the new                        location  <                       $ START/QUEUE/MANAGER fast_disk:[qman]  D           __________________________________________________________B           5.19  How do I delete an undeletable/unstoppable (RWAST)                 process?  E                    "Undeleteable" jobs are usually "undeleteable" foreG                    a reason-this can track back to insufficient processSH                    quotas, to a kernel-mode error in OpenVMS or a third-A                    party device driver, or to other odd problems.   F                    These undeletable jobs typically become of interestF                    because they are holding onto a particular resourceF                    (eg: tape drive, disk drive, communications widget)C                    that you need to use... If the particular devicebE                    supports firmware, ensure that the device firmwarenI                    is current - TQK50 controllers are known for this when E                    working with old firmware. (That, and the infamouseG                    "MUA4224" firmware bug.) If this device has a drivereD                    ECO kit available, acquire and apply it... If theI                    particular relevant host component has an ECO, acquiree                     and apply it.  G                    Useful tools include SDA (to see what might be goingeG                    on) and DECamds (which increase and thus potentially F                    fix quota-related problems). (nb: Applications with>                    quota leaks will obviously not stay fixed.)  J                    If the stuck application is BACKUP, ensure you have theI                    current BACKUP ECO and are directly following the V7.1aJ                    or (better) V7.2 or later process quota recommendationsI                    for operator BACKUP accounts. Quota details are in the 3                    OpenVMS System Manager's Manual.t                      5-34                0                    System Management Information        G                    If the firmware and ECO levels are current, the best J                    approach is to take a system crashdump, and pass a copyH                    of the dump file along to whomever is maintaining theH                    device driver for the particular device/widget/driverF                    involved, with any details on how you got into thisB                    situation. (The reboot involved with taking the?                    crashdump will obviously clear the problem.)n  I                    There was some kernel-mode code (typically for OpenVMSbF                    VAX) that can reset the device ownership field, butE                    that is rather obviously only an interim solution-tD                    the real fix is avoiding the loss of the IRP, theG                    process quota leak, or whatever else is "jamming up"g-                    this particular process...e  D           __________________________________________________________2           5.20  How do I reset the error count(s)?  I                    The system reboot is the only supported approach prior F                    to V7.3-2, but a reboot is obviously undesirable inE                    various situations-there is presently no supportedrI                    mechanism to reset error counts once the error(s) haveoE                    been logged on these older releases. On V7.3-2 andt6                    later, you can use the DCL command:  1                    $ SET DEVICE/RESET=ERROR_COUNTo  E                    As for an unsupported approach-and be aware of theiD                    potential for triggering a system crash, you needE                    to determine the system address of the error countaG                    field. For a device, this is at an offset within theeE                    device's UCB structure. On VAX, the field is at andI                    offset symbolically defined as UCB$W_ERRCNT. On Alpha, H                    this field's offset is symbolically defined as UCB$L_H                    ERRCNT. The former is a word in size; the latter is a                    longword.  J                    You now need to locate the system address of the UCB$%_F                    ERRCNT field of the device you wish to reset. EnterF                    SDA. In the following, you will see designations inI                    {} separated by a /. The first item in braces is to beyH                    used on the VAX and the second item should be used on.                    an Alpha. (ie. {VAX/Alpha})  J                                                                       5-35    n          0                    System Management Information        #                    $ ANALYZE/SYSTEMEE                    SDA>  READ SYS${SYSTEM/LOADABLE_IMAGES}:SYSDEF.STBSC                    SDA>  ! SHOW DEVICE the device with the error(s) ,                    SDA>  SHOW DEVICE <ddnc:>6                    SDA>  EVALUATE UCB+UCB${W/L}_ERRCNTL                    Hex = hhhhhhhh   Decimal = -dddddddddd         UCB+offset  D                    Record the hexadecimal value 'hhhhhhhh' returned.  I                    You can now exit from SDA and $ RUN SYS$SHARE:DELTA or ?                    do what I prefer to do, issue the following:   1                    SDA> SPAWN RUN SYS$SHARE:DELTA   D                    On both VAX and Alpha, the DELTA debugger will beF                    invoked and will ident- ify itself. On Alpha, thereB                    will be an Alpha instruction decoded. For thoseG                    unfamiliar with DELTA, it does not have a prompt andaJ                    only one error message-Eh? (Well, for sake of argument,J                    there might be another error produced on the console ifI                    you're not careful. This second error is more commonly ,                    known as a system crash.)  =                    If you are on a VAX, enter the command: [Wn  =                    If you are on Alpha, enter the command: [Lh  E                    These set the prevailing mode to word and longwordA@                    respectively. Remem- ber the UCB${W/L)_ERRCNT                    differences?a  ,                    Now issue the command 1;M  3                    DELTA will respond with 00000001   I                    You are now poised to ZAP the error count field. To dokI                    so you need to en- ter the system address and view itshG                    contents. The format of the command to do this is ofn                    the form:  !                    IPID:hhhhhhhh/a  J                    For an IPID, use the IPID of the SWAPPER process. It is#                    always: 00010001   A                    Thus, to ZAP the error count, you would enter:L  %                    00010001:hhhhhhhh/                       5-36e o  P          0                    System Management Information        F                    When you enter the / SDA will return the content ofG                    the address hhhhhhhh. This should be the error count G                    (in hexadecimal) of the device in question. If it is J                    not, you did something wrong and I'd suggest you type aI                    carriage return and then enter the command EXIT to get H                    out of DELTA. Regroup and see where your session went                    awry.  F                    If you entered your address correctly and the errorJ                    count was returned as in the following example, you can                    proceed.   D                    00010001:80D9C6C8/0001   ! output on VAX, 1 error  J                    00010001:80D9C6C8/00000001   ! output on Alpha, 1 error  I                    You can now ZAP the error count by entering a zero and 9                    typing a carriage return. For example:e  N                    00010001:80D9C6C8/0001 0<return>   ! output on VAX. 1 error  T                    00010001:80D9C6C8/00000001 0<return>   ! output on Alpha, 1 error  C                    Now type the command EXIT and a carriage return.   4                    Alternatively, reboot the system.  D           __________________________________________________________I           5.21  How do I find out if the tape drive supports compression?r  I                    For various SCSI-based MK-class magnetic tape devices:   E                    $ Devdepend2 = F$GETDVI("$n$MKcxxx:","DEVDEPEND2") *                    $ Comp_sup = %X00200000*                    $ Comp_ena = %X00400000D                    $ IF (Devdepend2.AND.Comp_sup).EQ.Comp_sup THEN -?                        WRITE SYS$OUTPUT "Compression supported" D                    $ IF (Devdepend2.AND.Comp_ena).EQ.Comp_ena THEN -=                        WRITE SYS$OUTPUT "Compression enabled"n  D           __________________________________________________________G           5.22  Can I copy SYSUAF to another version? To VAX? To Alpha?E  @                    The format of the SYSUAF.DAT, RIGHTSLIST, andI                    associated files are upward-compatible, and compatiblesD                    across OpenVMS VAX, OpenVMS Alpha and OpenVMS I64H                    systems. (This compatibility is a a basic requirementF                    of mixed-version OpenVMS Cluster configurations andE                    OpenVMS upgrades-for specific support information,_  J                                                                       5-37               0                    System Management Information        E                    please see the OpenVMS Cluster rolling upgrade and C                    mixed-version requirements.) That said, it's the H                    contents of the SYSUAF and RIGHTSLIST files that will.                    make this more interesting.  G                    The same basic steps necessary for moving RIGHTSLISTpF                    and SYSUAF files to another node are rather similarE                    to the steps involved in merging these files in anaJ                    OpenVMS Cluster-see the appendix of the OpenVMS ClusterI                    documentation for details of merging files. (You mighthJ                    not be merging the contents of two (or more) files, butH                    you are effectively merging the contents of the files7                    into the target system environment.)G  "                    Considerations:  H                    o  applications often hold SYSUAF or RIGHTSLIST open,F                       meaning a system reboot is often the best way to)                       activate new files.   F                    o  the meanings of the RESTRICTED and CAPTIVE flagsI                       settings on the UAF entries have changed over time.t  J                    o  the new NET$PROXY.DAT file that is initially createdJ                       based on the contents of the NETPROXY.DAT during theE                       OpenVMS VAX V6.1 upgrade and during the OpenVMSFD                       Alpha V6.2 upgrade. This file is maintained in1                       parallel with NETPROXY.DAT.a  J                    o  the RIGHTSLIST identifier values and UIC values thatG                       end up scattered around the target system must bedJ                       rationalized with the contents of the new RIGHTSLIST'                       and SYSUAF files.e  G                    The lattermost case-resolving the identifier values-nG                    is often the most interesting and difficult part. If I                    you find that an identifier value (or identifier name)tF                    from the source RIGHTSLIST collides with that of anE                    identifier existing on the target system, you musthE                    first determine if the two identifiers perform theoH                    same function. In most cases, they will not. As such,E                    you will have to find and chance all references tonF                    the identifier value(s) (or name(s)) to resolve the                    "collision".h                      5-38i t