             0                    System Management Information        E                    If you encounter a collision, changing both of the B                    identifier binary values (or names) involved inE                    the collision to new and unique values can prevent C                    security problems if you should miss a couple of F                    identifiers embedded somewhere on the target systemF                    during the whole conversion process-rather than theD                    wrong alphanumeric value for the identifier beingE                    displayed, you'll simply see the binary format forgE                    the identifier displayed, and no particular access)E                    will be granted. And any DCL commands or such that H                    reference the old alphanumeric name will fail, ratherJ                    than silently (and potentially erroneously) succeeding.  J                    Similar requirements exist for UIC values, as these tooH                    tend to be scattered all over the system environment.G                    Like the binary identifier values, you will find UIC J                    values associated with disks, ACLs, queues, and various$                    other structures.  G                    For a list of the various files shared in an OpenVMSaC                    Cluster and that can be involved when relocatinglF                    an environment from one node to another (or mergingH                    environments into an OpenVMS Cluster), please see theH                    SYLOGICALS.TEMPLATE file included in OpenVMS V7.2 and"                    later releases.  G                    Procedures to extract the contents of a (potentially F                    corrupt) queue database are provided on the OpenVMSE                    Freeware (V5) and can be used to combine two queuetC                    databases together while shuffling files betweenn)                    OpenVMS Cluster hosts.   J                    For related discussions of splitting a cluster into twoJ                    or for removing a node from cluster (political divorce,I                    etc), see topics (203), (767), (915) and others in then'                    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 ITRC  J                                                                       5-39               0                    System Management Information        D                    discussion forums; the area remains available for                    reference.o  D           __________________________________________________________9           5.23  How do I delete (timeout) idle processes?   F                    There is no such command integrated within OpenVMS,F                    though there are (optional) timers available withinJ                    certain terminal servers and similar devices, and thereG                    is an integrated time-of-day mechanism that provides ?                    control over when a user can access OpenVMS.   E                    As for available tools, there are DECUS, freeware,_I                    and third-party tools known variously as "idle process I                    killers" (IPK) or "terminal timeout" programs, as well J                    as various other names. Examples include: Saiga SystemsE                    Hitman, Watchdog, MadGoat Watcher (via the MadGoat H                    site or the OpenVMS Freeware), Kblock, the NetworkingE                    Dynamics tool known as Assassin, and the Zap tool. I                    Also available is the XLNperformance system management ,                    utility, from XLNsystems.  A                    A related package (for DECwindows sessions) ist                    xtermlock.   D                    If the forgetful users are in an application menuG                    environment, the menu can potentially be extended to +                    provide this capability.)  D           __________________________________________________________C           5.24  Do I need a PAK for the DECevent (HP Analyze) tool?N  D                    DECevent and HP (Compaq) Analyze are available toH                    customers with support contracts. The PAK is requiredI                    only for the advanced functions of DECevent, the basicrE                    bits-to-text translation of the error log does notcE                    require a license PAK. Ignore the prompt, in otheriI                    words. (The PAK should be available to you if you have_H                    a hardware support contract or warrantee, and the PAKE                    enables the use of the advanced error analysis and >                    notification capabilities within DECevent.)  C                    Please see the following website for details and &                    downloads: Analyze)  =                    o  http://www.compaq.com/support/svctools/q                      5-40t p  p          0                    System Management Information        D                    Also see the tool that is available on V7.3-2 and                    later.   &                    $ ANALYZE/ERROR/ELV  D           __________________________________________________________>           5.25  INITIALIZE ACCVIO and ANSI tape label support?  F                    A change was made (back in 1988) to (as it was thenI                    known) VAX/VMS V5.1-1 that added support for the then- J                    new ANSI X3.27-1987 magnetic tape label standard. PriorI                    to the ANSI X3.27-1987 standard, the date field in the2H                    ANSI HDR1 record permits dates only as far as the endI                    of Year 1999. With ANSI X3.27-1987, dates through Year H                    1999 and dates from Years 2000 to 2099 are permitted.  C                    Versions of INIT.EXE and MTAACP.EXE from VAX/VMS J                    releases prior to V5.1-1 will potentially have problemsG                    properly processing ANSI magnetic tapes when Y2K and I                    later dates are involved-the DCL INITIALIZE command is G                    known to encounter access violation (ACCVIO) errors.   G                    The available solutions include upgrades, or setting H                    the date back. Direct initialization of the tape withG                    the new headers (via $qio) is also clearly possible, J                    though the limitation within the old MTAACP.EXE magtape=                    ACP image is not nearly so easy to bypass.   D           __________________________________________________________7           5.26  How do I recover from INSVIRMEM errors?n  E                    Prior to OpenVMS Alpha V7.0 and on all OpenVMS VAXuJ                    releases, VIRTUALPAGECNT and PGFLQUOTA limit the amountE                    of virtual address space that is available to eachs                    process.   F                    Further limiting the amount of address space is theE                    size of system space (S0 and S1 space). On OpenVMS_F                    Alpha versions prior to V7.0 and on all OpenVMS VAXF                    releases, VIRTUALPAGECNT and MAXPROCESSCNT togetherG                    determine the size of the page table data structures,D                    that occupy large tracts of system space. When noJ                    system virtual address space is available for the stuffI                    that needs it-this includes the page tables, non-pagedeH                    pool, and various other structures-then the values ofH                    VIRTUALPAGECNT and MAXPROCESSCNT cannot be increased.  J                                                                       5-41               0                    System Management Information        G                    In OpenVMS Alpha V7.0 and later, the page table data H                    structures have been moved out of S0 and S1 space andJ                    into page table space. In OpenVMS Alpha V7.2 and later,H                    certain large data structures found in non-paged poolH                    (eg: lock management structures) have been moved intoG                    64-bit space, thus freeing up room in non-paged pool H                    and in S0 and S1 space (where non-paged pool resides)E                    while also permitting much larger data structures.   D           __________________________________________________________J           5.27  How can I prevent a serial terminal line from initiating a                 login?  ;                    In SYSTARTUP_VMS.COM, issue the command:   =                    $ SET TERMINAL/NOTYPEAHEAD/PERMANENT ddcu:   F                    This will prevent any unsolicited terminal input onE                    ddcu:, and this unsolicited input is what triggers I                    JOB_CONTROL to start up LOGINOUT on the terminal. Once E                    LOGINOUT starts up on the serial line, you can see H                    interesting behaviour (eg: audits, process creations,H                    etc) as LOGINOUT tries to "chat" with whatever deviceG                    is hooked onto the remote end of the serial terminal                     line.  D           __________________________________________________________>           5.28  How does PCSI use the image BUILD_IDENT field?  E                    The (undocumented) build ident field in an OpenVMS F                    Alpha image header is 16 bytes long, and is used asH                    a counted string of 0-15 characters (ie, as an .ASCICG                    string, a string with the character count in byte 0) G                    and was originally introduced to provide information J                    for use by VMSINSTAL patch kits to determine whether an3                    image should be replaced or not.L  J                    Starting with OpenVMS Alpha V7.1-2, OpenVMS EngineeringH                    uses the PCSI utility to package and install ECO kitsE                    for OpenVMS. PCSI uses the generation attribute (asF                    32-bit unsigned integer) specified for files in theF                    product description file (PDF) of a PCSI kit as theC                    basis for performing file conflict detection and I                    resolution. When a product is installed, PCSI modifies H                    the build ident field of Alpha image headers to storeJ                    an encoded form of the generation number. It also looksJ                    at the build ident field of previously installed images                      5-42i d  t          0                    System Management Information        J                    to obtain the generation information for those files asI                    input to the file conflict processing algorithm. (Onlyc6                    images have this field, obviously.)  H                    PCSI interprets the build ident field of a previously.                    installed image as follows:  F                    o  if the string length is 15, the 5th character isE                       a hyphen, and the last ten characters are a tensH                       digit number with leading zeros, then the last tenJ                       characters are treated as a valid generation number.  H                    o  for V7.1-2 through V7.2-1, inclusive, if the aboveF                       test fails, the information is obtained from the,                       PCSI product database.  H                    o  in releases after V7.2-1 and with current PCSI ECOJ                       kits, if the above test fails, an invalid generationI                       number is treated as 0000000000 so that the ECO kiteH                       will simply replace the image rather than assuming4                       the PCSI database is in error.  D                    So, what will you see in the image identification;                    displayed via the ANALYZE/IMAGE command?   I                    For an image that has been built as part of an OpenVMSwE                    Engineering system build, you will generally see alH                    build ID string in the format "X6TE-SSB-0000"-X6TE isI                    the build number for the OpenVMS Alpha V7.2-1 release.mJ                    This id format is used within the OpenVMS system build,H                    and can generally only be seen associated with images=                    that have not yet been processed via PCSI.   F                    During the installation of V7.2-1, PCSI will modifyC                    the image header to have a build ident string ofeC                    "X6TE-0050120000". During installation of an ECO"E                    kit containing this image with a generation number2F                    of 50130052, for example, PCSI would determine thatJ                    50130052 is greater than 50120000, and will replace theH                    existing image on the target disk with the version of5                    the image included in the ECO kit.7  H                    Ranges of PCSI generation numbers for various OpenVMSF                    releases are included in Table 5-1. The use of xxxxF                    indicates a range of generations is available, fromI                    0000 to 9999, inclusive. The format of, the particulare  J                                                                       5-43 e  e          0                    System Management Information        F                    operation of, and the assignment of PCSI generation?                    numbers is subject to change without notice.S  J           ________________________________________________________________+           Table 5-1  PCSI Generation Numbern  J                    _______________________________________________________                    Generation J                    Number____________Generation_Source____________________  +                    0040100000        V7.1-2f  0                    004011xxxx        V7.1-2 ECOs  )                    0050100000        V7.2   .                    005011xxxx        V7.2 ECOs  +                    0050120000        V7.2-1_  0                    005013xxxx        V7.2-1 ECOs  -                    0050140000        V7.2-1H1   2                    005015xxxx        V7.2-1H1 ECOs  +                    0050160000        V7.2-2   0                    005017xxxx        V7.2-2 ECOs  )                    0060000000        V7.3   .                    006001xxxx        V7.3 ECOs  +                    0060020000        V7.3-10  0                    006003xxxx        V7.3-1 ECOs  +                    0060100000        V7.3-2   0                    006011xxxx        V7.3-2 ECOs  )                    0070040000        V8.2   .                    007005xxxx        V8.2 ECOs  +                    0070060000        V8.2-11  J           _________007007xxxx________V8.2-1_ECOs__________________________  D           __________________________________________________________H           5.29  How can I tell what software (and version) is installed?  I                    There is unfortunately no consistent nor single way to J                    make this determination-this is one of the reasons that<                    a move to PCSI installations is underway.                      5-44                0                    System Management Information        F                    On OpenVMS Alpha, you can use VMSINSTAL.HISTORY andG                    PRODUCT SHOW PRODUCT to determine what packages have C                    been installed via the VMSINSTAL and PCSI tools,T                     respectively.  I                    To see which OpenVMS Alpha ECO kits have been applied,oF                    look in VMSINSTAL.HISTORY on OpenVMS Alpha prior toG                    V7.1-2, and use PRODUCT SHOW PRODUCT/FULL on OpenVMS *                    Alpha V7.1-2 and later.  G                    On OpenVMS VAX, you can use PRODUCT SHOW PRODUCT and H                    (for software that is installed via VMSINSTAL on V7.33                    and later) in VMSINSTAL.HISTORY.t  F                    For products installed on OpenVMS VAX prior to V7.3I                    using VMSINSTAL, there is no reliable way to determineSD                    what products have been installed. If the productB                    provides a RELEASE_NOTES file (as many do), youE                    can look for the list of these files via DIRECTORYPH                    SYS$HELP:*.RELEASE_NOTES. Again, this approach is NOTI                    reliable: some kits do not provide release notes, someYG                    system managers will install only the release notes,7F                    some system managers will delete release notes, andF                    release notes for multiple versions can be present.  H                    On most packages, you can generally use ANALYZE/IMAGEB                    on one of the core images, looking at the imageD                    identification area. Some of the product-specific,                    mechanisms available are:  2                    o  DQS DQS$VERSION logical name  "                    o  C CC/VERSION  %                    o  C++ CXX/VERSION   7                    o  TCP/IP TCPIP SHOW VERSION command   D           __________________________________________________________C           5.30  What file checksum tools are available for OpenVMS?   H                    The undocumented (prior to V8.2) DCL command CHECKSUMJ                    is the usual means, and provides a rather simple-mindedF                    checksum suitable to detect basic file corruptions.G                    Starting with V8.2, additional algorithms beyond the 4                    classic XOR scheme are available.  J                                                                       5-45 _  _          0                    System Management Information        E                    One of the most common schemes beyond the CHECKSUMnG                    XOR scheme is MD5, and information and a source codesC                    example are available via the MD5 RFC. Pre-builtlH                    versions of MD5 are available at the OpenVMS FreewareF                    website ( http://www.hp.com/go/openvms/freeware/ ),J                    and on the OpenVMS Freeware V8.0 distribution. Also seeJ                    the CHECKSUM/ALGORITHM=MD5 command available on OpenVMS"                    V8.2 and later.  H                    The OpenVMS Alpha ECO (patch) kit checksums availableH                    at the ECO website are determined using the following(                    DCL command sequence:  5                    $ CHECKSUM kitname.pcsi-dcx_axpexea2                    $ SHOW SYMBOL CHECKSUM$CHECKSUM  H                    See Section 5.17 for information on acquiring OpenVMS$                    ECO (patch) kits.  D           __________________________________________________________C           5.31  What (and where) is the OpenVMS Management Station?(  C                    For information and current kits for the OpenVMSrI                    Management Station (OMS), a PC-based tool that permits ?                    you to manage an OpenVMS system, please see:   K                    o  http://www.openvms.compaq.com/openvms/products/argus/1  D           __________________________________________________________B           5.32  How to determine current disk fragmentation level?  ;                    The HP OpenVMS Disk File Optimizer (DFO)eC                    defragmentation package provides a fragmentation G                    monitoring tool, and a DFO product authorization key H                    (PAK) is not required for the fragmentation reporting                    tool:  -                    $ DEFRAG SHOW/VOLUME ddcu:r  E                    The DFU tool available on the OpenVMS Freeware can_?                    generate a report on the disk fragmentation:e  $                    DFU> REPORT ddcu:                      5-46i    O          0                    System Management Information      D           __________________________________________________________H           5.33  SYSBOOT-I-FILENOTLOC, Unable to locate SYS$CPU_ROUTINES?  G                    A message at the OpenVMS Alpha bootstrap such as theL                    following:   :                    %SYSBOOT-I-FILENOTLOC, Unable to locate.                      SYS$CPU_ROUTINES_1C02.EXE=                    %SYSBOOT-E-LDFAIL, failed to load execlet, &                      status = 00000910  F                    indicates that the particular OpenVMS Alpha releaseG                    does not contain support for the target platform. InEH                    this case, OpenVMS does not recognize Alpha family 1CH                    member 02 as a supported platform. A later version ofH                    OpenVMS might support the platform, or there might beF                    no support on any release. Ensure that you have theH                    most current firmware, and review the minimum version1                    requirements for the platform.e  G                    The execlet load failure and other similar bootstrapgI                    status values can often be decoded using either of theA(                    following techniques:                      $ exit %x910 5                    %SYSTEM-W-NOSUCHFILE, no such filee                    $  )                    $ x = f$message(%x910)r"                    $ show symbol x=                      X = "%SYSTEM-W-NOSUCHFILE, no such file"v                    $  -                    Also see Section 14.4.4.1.   D           __________________________________________________________E           5.34  How can I customize the DCPS device control for a new                  printer?  J                    To customize DCPS for an otherwise unsupported printer,6                    you can try the following sequence:  G                    o  Extract the most closely-associated setup modules ?                       from the existing device control library, F                       DCPS$DEVCTL.TLB. (For instance, you can probablyA                       extract and use the HP LaserJet 4000 series G                       definitions for the HP LaserJet 4050 series. Each C                       printer will vary, please consult the printer D                       documentation for specifics and requirements.)  J                                                                       5-47 u  o          0                    System Management Information        =                    o  rename each extracted setup module to a $                       corresponding:  )                       LPS$$UNRECOGNIZED_*   J                    o  Insert all of the above-renamed setup modules into aJ                       newly-created device control library specific to the"                       new printer:  -                       $ LIBRARY/TEXT/CREATE - >                           SYS$COMMON:[SYSLIB]HP4050_DEVCTL.TLB,                           LPS$$UNRECOGNIZED*  G                       The above assumes the filename HP4050_DEVCTL.TLB, (                       alter as required.  F                    o  Set up your DCPS startup procedures to include a7                       search-list logical name such as:   B                       $ DEFINE/SYSTEM/EXECUTIVE DCPS_HP4050_LIB  -:                           SYS$LIBRARY:HP4050_DEVCTL.TLB, -5                           SYS$LIBRARY:DCPS$DEVCTL.TLBO  E                    o  Supply DCPS_HP4050_LIB as the library parameterEA                       in the queue startup for this printer, thisEB                       is the P3 parameter to the command procedure;                       SYS$STARTUP:DCPS$EXECUTION_QUEUE.COM.   C                    o  The HP4050_DEVCTL library may/will need to be G                       recreated and modules re-edited and replaced with D                       each DCPS upgrade, particularly if any modulesH                       are updated in the original library. You will alsoG                       want to determine if the upgraded version of DCPSt?                       directly supports the particular printer.t  D                    o  To customize the processing of file extensionsG                       within DCPS (to enable or disable graybar output,eF                       for instance), use the information available in:  K                       SYS$LIBRARY:DCPS$FILE_EXTENSION_DATA_TYPE.DAT_DEFAULTs  4                    to create your own site-specific:  @                    SYS$LIBRARY:DCPS$FILE_EXTENSION_DATA_TYPE.DAT  )                    Also see Section 5.15.                       5-48t l  p          0                    System Management Information      D           __________________________________________________________D           5.35  Why do $GETDEV MOUNTCNT and SHOW DEVICE mount counts                 differ?   E                    MOUNTCNT returns the local mount count, while SHOWs?                    DEVICE returns the cluster-wide mount count.   D           __________________________________________________________@           5.36  What software is needed for Postscript printers?  D                    The NorthLake PrintKit (www.nls.com) and DECprintF                    Supervisor (DCPS) are common choices for support of2                    Postscript printers on OpenVMS.  )                    o  http://www.nls.com/   H                    o  http://www.openvms.compaq.com/openvms/Print/print_#                       sw_prods.html-  A                    You may also require the installation of an IP_#                    transport stack.   E                    Also please see Section 15.2.2 and Section 15.2.3.e  D           __________________________________________________________A           5.37  How do I remove a PCSI-installed patch (ECO) kit?P  D                    You cannot PRODUCT REMOVE a PCSI patch (ECO) kit.  I                    In order to remove an ECO kit, PCSI would have to havenD                    copies of all the other version of the files fromF                    all other patches and products that previously wereH                    installed. This can clearly involve a large number ofG                    files and a large archive of old file versions and a_G                    substantial quantity of disk space. While removal is F                    clearly theoretically possible, it is not currently                    implemented.r  G                    The following is the supported mechanism to remove al"                    PCSI patch kit.  H                    1  Execute a PRODUCT SHOW PRODUCT product-name. /FULLJ                       command. The "maintenance" column (132 column width)H                       shows the patches that have been installed. Keep a+                       copy of this listing.p  J                    2  Acquire kits for all of the maintenance kits listed.  G                    3  Re-install the prior FULL version of the product.eI                       This will remove all patch kits, setting to product 3                       back to "original" condition.   J                                                                       5-49 "  l          0                    System Management Information        I                    4  Re-install all the patches in the list from step 1, H                       except those patches which you have determined you"                       do not want.  E                    The above information also applies to PCSI PARTIALl                    kits.  D           __________________________________________________________H           5.38  SYSINIT-E, error mounting system device, status=0072832C  B                    This message can arise during an OpenVMS system                    bootstrap...   V                    %MOUNT-F-DIFVOLMNT, different volume already mounted on this device  C                    For details and further information, use the DCL.                    command:o  2                    $ HELP/MESSAGE /STATUS=%X72832C  D           __________________________________________________________/           5.39  Resolving License PAK Problems?r  F                    The PAK release date, the PAK termination date, andH                    the PAK version are the usual culprits when a licenseH                    product authorization key (PAK) check failure occurs.  H                    The PAK termination date is the date when the license#                    PAK will expire.o  F                    The PAK release date is the date of the most recentD                    release date of the software package that will beH                    permitted by the particular license PAK. (The releaseG                    date check is analogous to a product version check.)tD                    The PAK version indicates the most recent product<                    version that is permitted by the license.  G                    Having multiple license PAKs registered (and active)wI                    can also cause problems if an expired PAK gets loaded.mH                    You will want to DISABLE license PAKs you do not wish"                    to have loaded.  H                    Other problems include a failure to register each PAKI                    in all license databases throughout a multiple-system-iH                    disk cluster, with a consistent set of /INCLUDE lists@                    specified across each of the duplicated PAKs.                      5-50c e             0                    System Management Information        F                    Additionally, you could have an invalid LMF$LICENSEC                    logical name defined. (If no LMF$LICENSE logicalhG                    name is defined, the standard license database named <                    SYS$SYSTEM:LMF$LICENSE.LDB will be used.)  C                    You can display license failures by defining the *                    following logical name:  C                    $ DEFINE/SYS/EXEC LMF$DISPLAY_OPCOM_MESSAGE TRUE   =                    Enable your terminal as a license operator B                    (REPLY/ENABLE=LICENSE), define the LMF$DISPLAY_G                    OPCOM_MESSAGE logical name, and then try the failing D                    operation again. You should see one or more OPCOM&                    messages displayed.  I                    If you have the LMF$DISPLAY_OPCOM_MESSAGE logical name F                    defined, you can (will?) see spurious license checkD                    failures-various products will check for multipleH                    licenses, and a few products will check for PAKs thatG                    either have not yet been or will not be issued. OncecI                    you figure out which license has failed, you will want 1                    to deassign this logical name.s  1                                              Notee  G                       That there are no license check failures does notaG                       indicate that the particular product or operation D                       or use is permissible per applicable licensing?                       agreements. Please consult the applicableaD                       agreement(s) for licensing-related information'                       and requirements.i  C                    To register a license PAK on a DECwindows system F                    when DECwindows cannot start (because of an expiredH                    license or other licensing problem), follow the stepsE                    outlined in section Section 5.6 up through the userF                    of the AUTHORIZE command. In place of the AUTHORIZEI                    command, use the console to register the license PAKs.fJ                    Also see Section 12.4 for licensing and troubleshooting                    information.a  E                    For information on licensing and on the numbers ofcJ                    license units required for various products and variousH                    platforms, the License Unit Requirements Table (LURT)#                    is available at:   J                                                                       5-51    c          0                    System Management Information        C                    o  http://www.compaq.com/products/software/info/   D           __________________________________________________________4           5.40  Changing the OpenVMS Version Number?  J                    Fool your friends, baffle your enemies, run the OpenVMSH                    version of your choice! Instantly back-port all thoseD                    useful new OpenVMS features to an ancient OpenVMS                    version!   ,                    On OpenVMS Alpha systems:  5                    $ SET DEFAULT SYS$COMMON:[SYS$LDR].                    $ RUN SYSVER                     REPLACE V9.9_                    WRITE                    $ EXITn  C                    How does SYSVER work? SYSVER looks for SYS$BASE_s>                    IMAGE.EXE within the default directory, andE                    updates the version string stored within. And yes,eI                    obviously, SYS$BASE_IMAGE.EXE resides in the directory (                    SYS$COMMON:[SYS$LDR].  *                    On OpenVMS VAX systems:  5                    $ set default SYS$COMMON:[SYS$LDR] 8                    $ copy SYS.EXE SYS.EXE_IN-CASE-I-FAIL"                    $ patch SYS.EXE1                    define sys$gq_version=800044b8Y!                    set mode asciiE*                    !examine sys$gq_version,                    !examine sys$gq_version+44                    deposit sys$gq_version   = "V9.9"4                    deposit sys$gq_version+4 = "    "                    update.                    exit                     $ Exit   :                    Then reboot the system at your leisure.                            5-52N S  -          0                    System Management Information      D           __________________________________________________________E           5.41  How to prevent users from choosing obvious passwords?q  G                    To prevent users from selecting obvious passwords on F                    OpenVMS, you will want to use the reserved passwordI                    (password screening) mechanism. Effectively, you mergeTD                    your list of reserved passwords into the existingJ                    reserved words database maintained by OpenVMS. (You canH                    also then require all users to reset their passwords-F                    via the pre-expired password mechanism-thus forcingE                    users to select new passwords.) For details on the I                    password screening mechanism, of the reserved password G                    database (VMS$PASSWORD_DICTIONARY.DATA), and details D                    of how to merge your list of prohibited passwordsG                    into the database, please see the associated chapternE                    in the OpenVMS security manual. For details of thedC                    password expiration mechanism, see the AUTHORIZEr1                    command qualifier /PWDEXPIRED.r  I                    You can also implement a site-specific password filter C                    with the information provided in the back of theTD                    OpenVMS Programming Concepts manual. The passwordG                    filter permits you to establish particular and site-sF                    specific password requirements. For details, pleaseC                    see the system parameter LOAD_PWD_POLICY and thecG                    programming concepts manual, and see the examples inRE                    SYS$EXAMPLES:. (Examples and documentation on V7.3oE                    and later reflect both platforms, the examples arekF                    found only on OpenVMS VAX kits on earlier releases.J                    The capabilities have existed on both the VAX and Alpha0                    platforms for some time now.)  B                    To verify current passwords, you can also use aH                    technique known to system crackers as the "dictionaryJ                    attack" - the mechanism that makes this attack somewhatJ                    more difficult on OpenVMS is the hashing scheme used onH                    OpenVMS, and the file protections used for the SYSUAFJ                    authorization database. Given a dictionary of words andH                    the unprotected contents of the SYSUAF file, a searchI                    for obvious passwords can be performed. Interestingly, G                    a "dictionary attack" also has the unfortunate side- I                    effect of exposing the password to the user-while this F                    is clearly the goal of a system cracker, authorizedH                    privileged and non-privileged system users should not  J                                                                       5-53               0                    System Management Information        G                    know nor have access to the (cleartext) passwords of                     other users.s  D                    Accordingly, OpenVMS does not store the cleartestE                    password. Further, OpenVMS uses a password hashinglJ                    algorithm, not an encryption algorithm. This means thatJ                    storage of a cleartext password is deliberated avoided,I                    and the cleartext value is deliberately very difficulteF                    to obtain. The hash is based on a Purdy Polynomial,G                    and the hash itself includes user-specific values in I                    addition to the password, values that make the results <                    of the password hash unique to each user.  I                    Regardless of the use of a password hashing scheme, if J                    a copy of your password file should become available toH                    a system cracker, you will want to force all users to1                    use new passwords immediately.n  E                    If you should require a user to verify a password,rF                    use the username, the user's salt value (this valueD                    is acquired via $getuai) and the user's specifiedG                    cleartext password, and compare the resulting hasheddE                    value (using a call to $hash_password) against thehH                    saved hashed password value (this value also acquiredF                    via $getqui). For reasons of security, avoid savingG                    a cleartext password value in any data files, and dooG                    not maintain the cleartext password in memory longerlH                    than required. (Use of sys$acm on V7.3-1 and later is                     recommended.)  A                    Kerberos authentication (client and server) isnF                    available on OpenVMS V7.3 and later. Integration ofG                    Kerberos support into various Compaq and into third-i.                    party products is expected.  A                    External authentication is available in V7.3-1 D                    and later, with support for user-written external6                    authentication in V7.3-2 and later.  C                    If you are simply looking for OpenVMS access and D                    the SYSTEM and all other privileged passwords areI                    forgotten or otherwise unavailable, please see sectionrD                    Section 5.6 and/or the OpenVMS documentation set.  H                    Also please see the NCSC C2 guidelines in the OpenVMS#                    security manual.                       5-54t r  e          0                    System Management Information      D           __________________________________________________________?           5.42__Please_help_me_with_the OpenVMS BACKUP utility?d  8           5.42.1  Why isn't BACKUP/SINCE=BACKUP working?  J                    If you are seeing more files backed up than previously,I                    you are seeing the result of a change that was made toiJ                    ensure BACKUP can perform an incrementation restorationC                    of the files. In particular, if a directory fileII                    modification date changes, all files underneath it are_I                    included in the BACKUP, in order to permit incrementaldC                    restoration should a directory file get renamed.   '           _____________________________aJ           5.42.1.1  Why has OpenVMS gone through the agony of this change?  D                    When a directory is renamed, the modified date isE                    changed. When the restoration needs to restore thecI                    directory and its contents, and the restoration shouldlG                    not result in the restoration of the older directory J                    name when a series of incremental BACKUPs are restored.H                    Thus an incremental BACKUP operation needs to pick up&                    all of the changes.  E                    Consider performing an incremental restoration, tonD                    test the procedures. This testing was how OpenVMSC                    Engineering found out about the problem that wasnB                    latent with the old BACKUP selection scheme-theB                    old incremental BACKUP scheme would have missedG                    restoring any files under a renamed directory. Hence F                    the change to the selection mechanisms mentioned in"                    Section 5.42.1.  '           _____________________________r>           5.42.1.2  Can you get the old BACKUP behaviour back?  I                    Yes, please see the /NOINCREMENTAL qualifier availabletD                    on recent OpenVMS versions (and ECO kits). Use ofF                    this qualifier informs BACKUP that you are aware ofE                    the limitations of the old BACKUP behaviour arounde1                    incremental disk restorations.n        J                                                                       5-55 _  _          0                    System Management Information      '           _____________________________a>           5.42.2  What can I do to improve BACKUP performance?  @                    Use the documented commands in the manual forE                    performing incremental BACKUPs. Use the documented G                    incremental procedures. Don't try to use incremental 9                    commands in a non-incremental context.   G                    Also consider understanding and then using /NOALIAS, J                    which will likely be a bigger win than will anything toJ                    do with the incremental BACKUPs, particularly on systemD                    disks and any other disks with directory aliases.  H                    See the OpenVMS documentation for additional details.  H                    Ignoring hardware performance and process quotas, theJ                    performance of BACKUP during a disk saveset creation is6                    typically limited by three factors:  )                    1  Default extend sizeb  E                       The default behavior can have poor performance,eC                       as the extend operation can involve extensiveaH                       additional processing and I/O operations. ConsiderI                       changing the default extend value on the volume, ord8                       change the extend for the process:  ,                       $ set rms/extend=65000  $                    2  Output IO size  G                       The default IO size for writing an RMS sequential F                       file is 32 blocks, an increase from the value ofI                       16 blocks used on earlier versions. Setting this to H                       the maximum of 127 can reduce the number of IOs by+                       almost a factor of 4:a  )                       $ set rms/block=127   G                       Note that the performance might be better on somedI                       controllers if the block count is a multiple of 4 -                        e.g. 124  7                    3  Synchronous writes to the saveset   F                       Starting with OpenVMS V7.3, you can now persuadeF                       RMS to turn on write-behind for sequential filesI                       opened unshared. (Please see the V7.3 release notesaI                       or more recent documentation for details.) EnablingeF                       the write-behind operations involves setting theD                       dynamic system parameter RMS_SEQFILE_WBH to 1.                      5-56     3          0                    System Management Information        F                       This parameter is dynamic, and it can be enabledG                       and disabled without a reboot, and changes in itsuF                       setting can and will directly effect the runningJ                       system. In order to get the full benefit from write-F                       behind operations, you also need to increase theG                       RMS local buffer count from the default of 2 to a J                       larger number. Raising the value to 10 is probably a?                       reasonable first estimate for this value.l  -                       $ run sys$system:sysmanr+                       PARAMETERS USE ACTIVE 6                       PARAMETERS SET RMS_SEQFILE_WBH 1-                       PARAMETERS WRITE ACTIVE                        EXIT@                       $ SET RMS/BUFFER=10/EXTEND=65000/BLOCK=127N                       $ BACKUP source-specification ddcu:[dir]saveset.bck/SAVE  '           _____________________________t8           5.42.3  Why is BACKUP not working as expected?  C                    First, please take the time to review the BACKUP$E                    documentation, and particularly the BACKUP command F                    examples. Then please download and install the mostI                    current BACKUP eco kit. Finally, please please set theEJ                    process quotas per the System Management documentation.B                    These steps tend to resolve most problems seen.  A                    BACKUP has a very complex interface, and therepC                    are numerous command examples and extensive usereH                    documentation available. For a simpler user interfaceC                    for BACKUP, please see the documentation for the '                    BACKUP$MANAGER tool.U  E                    As for recent BACKUP changes, oddities, bugs, etc:o  I                    o  A change made in OpenVMS V6.2 WILL cause more filestE                       to be included into a file-based BACKUP saveseteE                       using /SINCE=BACKUP as all files underneath anynE                       directory with a sufficiently recent (selected)bG                       date will be included in the saveset. This changeeF                       was deliberate and intentional, and was mandatedE                       by the need to provide a functional incrementalo"                       restoration.  J                                                                       5-57 i             0                    System Management Information        E                       Without the inclusion of these apparently-extraaG                       files, an incremental saveset can NOT be reliablyu                       restored.   D                    o  As part of the OpenVMS V6.2 change, the /SINCEF                       command-without the specification of the =BACKUPF                       keyword-selected more files than it should have.F                       This is a bug. This bug has been remedied in theI                       OpenVMS BACKUP source code and in some of (all of?) *                       the BACKUP ECO kits.  >                    When working with BACKUP, you will want to:  E                    o  Ensure you have your process quotas set per thefF                       recommendations in the OpenVMS System ManagementH                       documentation. Deviation from these values can andF                       will lead to access violation (ACCVIO) and other)                       untoward behaviour.   J                    o  Get the current BACKUP ECO kit and install it BEFORE?                       you attempt to troubleshoot any problems.n  G                    o  Learn about the /NOINCREMENTAL (new) and /NOALIASoE                       (V6.2 and later) command qualifiers. The formernH                       qualifier returns to the pre-V6.2 behaviour of theG                       /SINCE file selection mechanism, while the latter E                       (specified with /IMAGE) reduces the replication H                       of files on system disks and other disks with fileJ                       alias and directory alias entries. Both of these canG                       reduce the numbers of files that will be selected 9                       and thus included into the saveset.e  F                       Learn what /IGNORE=INTERLOCK means. This commandG                       probably does not provide what you think it does-eG                       those file system interlocks that this command iscH                       ignoring were implemented for a reason, after all.G                       Ignoring these interlocks can lead to missed datatH                       and potentially to corruptions to individual filesH                       stored within the output saveset, corruptions thatE                       may or may not be reported. For details on this F                       BACKUP command qualifier, please see the Ask The*                       Wizard topic (2467).                        5-58                0                    System Management Information        =                    When working with the BACKUP callable API:d  J                    o  Build your applications with the most current BACKUPH                       API available. Changes made to the V7.1-2 and V7.2H                       API were incompatible with the V7.1 and V7.2-1 andG                       later APIs, and this incompatibility was repaired I                       via a BACKUP ECO kit. Do NOT build your application F                       with the versions of the BACKUP API that shippedJ                       with V7.1-2 and V7.2, as these are incompatible withF                       the BACKUP API constants that were used on other                       versions.C  '           _____________________________ 8           5.42.4  How do I fix a corrupt BACKUP saveset?  I                    BACKUP savesets can be corrupted by FTP file transferseF                    and by tools such as zip (particularly when the zipF                    tool has not been asked to save and restore OpenVMSF                    file attributes or when it does not support OpenVMSH                    file attributes; use the zip "-V" option), as well as2                    via other means of corruptions.  H                    If you have problems (eg: NOTSAVESET errors) with theG                    BACKUP savesets after unzipping them or after an FTPyG                    file transfer, you can try restoring the appropriateu5                    saveset attributes using the tool:n  1                    $ BACKUP/LIST saveset.bck/SAVE )                    Listing of save set(s)t  R                    %BACKUP-F-NOTSAVESET, saveset.bck/SAVE is not a BACKUP save setT                    $ @SRH:[UTIL]RESET_BACKUP_SAVESET_FILE_ATTRIBUTES.COM saveset.bck1                    $ BACKUP/LIST saveset.bck/SAVE )                    Listing of save set(s)   1                    Save set:          saveset.bcko.                    Written by:        username                    ...  E                    This tool is available on the OpenVMS Freeware (in G                    the [000TOOLS] directory). The Freeware is availablePF                    at various sites-see the Freeware location listingsH                    elsewhere in the FAQ-and other similar tools are also2                    available from various sources.  J                                                                       5-59    e          0                    System Management Information        F                    In various cases, a SET FILE/ATTRIBUTES command canJ                    also be used. As the parameters of this command must beG                    varied as the target BACKUP saveset attributes vary,o4                    this approach is not recommended.  I                    Also see the "SITE VMS", /FDL, and various other file-rJ                    attributes options available in various FTP tools. (NotF                    all available FTP tools support any or all of these                    options.)  G                    Browser downloads (via FTP) and incorrect (binary orsF                    ascii FTP transfer modes) are notorious for causingG                    RMS file corruptions and particularly BACKUP saveset D                    corruptions. You can sometimes help encourage theG                    browser to select the correct FTP transfer type code !                    (via RFC1738):o  A                    o  ftp://host/urlname.ext;type=i ! request ftpl+                       image/binary transfer   A                    o  ftp://host/urlname.ext;type=a ! request ftps)                       ascii/text transfere  J                    You can also often configure the particular web browserF                    to choose the appropriate transfer mode by default,C                    based on the particular file extensions, using aeI                    customization menu available in most web browsers. You H                    can select that the specific file extentions involvedJ                    use the FTP binary transfer mode, which will reduce the.                    number of corruptions seen.  '           _____________________________uC           5.42.5  How do I write a BACKUP saveset to a remote tape?   G                    How to do this correctly was described at DECUS longbG                    ago. On the OpenVMS host with the tape drive, createo3                    the following SAVE-SET.FDL file:                       RECORDh8                            FORMAT                  fixed7                            SIZE                    8192e                          5-60c u  o          0                    System Management Information        1                    Then create BACKUP_SERVER.COM:e                      $ !R                    $ ! BACKUP_SERVER.COM - provide remote tape service for BACKUP.                    $ !                    $ set noon '                    $ set rms/network=16 ,                    $ allocate mka500 tapedevE                    $ mount/nounload/over:id/block=8192/assist tapedevZC                    $ convert/fdl=SAVE-SET sys$net tapedev:save-set. ,                    $ dismount/unload tapedev                    $ stop/id=0  G                    On the node where you want to do the backup, use the                     DCL command:p                      $ backup -C$                        srcfilespec -K                        node"user pwd"::"task=backup_server"/block=8192/save   F                    One area which does not function here is the volumeH                    switch; multi-reel or multi-cartridge savesets. SinceG                    the tape is being written through DECnet and RMS and E                    the magtape ACP, BACKUP won't see the media switchyH                    and will split an XOR group across the reel boundary.E                    BACKUP might well be willing to read such a multi- F                    reel or multi-cartridge saveset (directly, not overE                    the net) as the XOR blocks are effectively ignoreduI                    until and unless needed for error recovery operations.eI                    BACKUP likely will not be able to perform an XOR-based @                    recovery across reel or cartridge boundaries.  I                    Unfortunately BACKUP can't read tapes over the network.D                    because the RMS file attributes on a network taskE                    access look wrong; the attributes reported includev+                    variable length records.o  '           _____________________________ =           5.42.6  How to perform a DoD security disk erasure?   ?                    Sometimes refered to as disk, tape, or mediaaG                    declassification, as formatting, as pattern erasure, C                    or occasionally by the generic reference of datawG                    remanence. Various references to the US Deparment ofkJ                    Defence (DoD) or NCSC "Rainbow Books" documentation are-                    also seen in this context.   J                                                                       5-61 c  t          0                    System Management Information        G                    While this erasure task might initially appear quitepG                    easy, basic characteristics of the storage media andeF                    of the device error recovery and bad block handlingH                    can make this effort far more difficult than it might$                    initially appear.  F                    Obviously, data security and sensitivity, the costsB                    of exposure, applicable legal or administrativeB                    requirements (DoD, HIPPA or otherwise), and theG                    intrinsic value of the data involved are all centralsH                    factors in this discussion and in the decision of theI                    appropriate resolution, as is the value of the storages%                    hardware involved.t  C                    With data of greater value or with data exposure F                    (sometimes far) more costly than the residual valueI                    of the disk storage involved, the physical destruction B                    of the platters may well be the most expedient,G                    economical, and appropriate approach. The unintendedsI                    exposure of a bad block containing customer healthcareoF                    data or of credit card numbers can quite be costly,G                    of course, both in terms of the direct loss, and the D                    longer-term and indirect costs of such exposures.  F                    Other potential options include the Freeware RZDISKE                    package, the OpenVMS INITIALIZE/ERASE command (and,E                    potentially in conjunction with the $erapat systemeC                    service) and OpenVMS Ask The Wizard (ATW) topicsaG                    including (841), (3926), (4286), (4598), and (7320).cD                    For additional information on sys$erapat, see theF                    OpenVMS Programming Concepts manual and the OpenVMSH                    VAX examples module SYS$EXAMPLES:DOD_ERAPAT.MAR. SomeH                    disk controllers and even a few disks contain supportG                    for data erasure. Some DSSI Disk ISEs, for instance.s  D                    For the prevention of casual disk data exposures,C                    a generic INITIALIZE/ERASE operation is probably7?                    sufficient. This is not completely reliable,aE                    particularly if the data is valuable, or if legal,tA                    administrative or contractual restrictions are_E                    stringent-there may well be revectored blocks thatsG                    are not overwritten or not completely overwritten bySI                    this erasure, as discussed above, and these blocks candH                    obviously contain at least part of most any data thatI                    was stored on the disk - but this basic disk overwritea                      5-62u l  f          0                    System Management Information        H                    operation is likely sufficient to prevent the typical+                    information disclosures.   C                    You will want to consult with your site security I                    officer, your corporate security or legal office, with E                    HP Services or your prefered service organization, E                    or with a firm that specializes in erasure or data I                    declassification tasks. HP Services does traditionallye@                    offer a secure disk declassification service.  '           _____________________________ 9           5.42.7  How to enable telnet virtual terminals?u  D                    To enable virtual terminal support for telnet andA                    rlogin devices, add the following logical name 3                    definitions into SYLOGICALS.COM:   B                    $ DEFINE/SYSTEM/EXECUTIVE TCPIP$RLOGIN_VTA TRUEB                    $ DEFINE/SYSTEM/EXECUTIVE TCPIP$TELNET_VTA TRUE  I                    See SYS$STARTUP:SYLOGICALS.TEMPLATE for details on the 6                    typical contents of SYLOGICALS.COM.  I                    In SYSTARTUP_VMS.COM, ensure that a command similar toe,                    the following is invoked:  a                    $ SYSMAN IO CONNECT VTA0/NOADAPTER/DRIVER=SYS$LOADABLE_IMAGES:SYS$TTDRIVER.EXEY  J                    In MODPARAMS.DAT, add the following line or (if alreadyH                    present) mask the specified hexidecimal value into anJ                    existing TTY_DEFCHAR2, and perform a subsequent AUTOGEN+                    with an eventual reboot:L  )                    TTY_DEFCHAR2 = %X20000U  2                    This value is TT2$M_DISCONNECT.  F                    On older TCP/IP Services-versions prior to V5.0-youB                    will have to perform the following UCX command:                      $ UCX4                    UCX> SET CONF COMM/REMOTE=VIRTUAL    J                                                                       5-63    e          0                    System Management Information      '           _____________________________ ;           5.42.7.1  Volume Shadowing MiniCopy vs MiniMerge?T  F                    MiniMerge support has been available for many yearsG                    with OpenVMS host-based volume shadowing, so long ashH                    you had MSCP controllers (eg: HSC, HSJ, or HSD) whichH                    supported the Volume Shadowing Assist known as "Write$                    History Logging".  B                    If you are interested in mini-merge and similarE                    technologies, please see the Fibre Channel webpageu7                    and the information available there:   B                    o  http://www.openvms.compaq.com/openvms/fibre/  C                    Mini-Merge support was originally intended to be F                    controller-based and was expected with HSG80 seriesJ                    storage controllers and was expected to require ACS 8.7,                    and OpenVMS Alpha V7.3-1.  D                    Host-based Mini-Merge (HBMM) is now available forE                    specific OpenVMS releases via a shadowing ECO kit,tF                    and is also present in OpenVMS V8.2 and later. HBMMI                    applies to the HSG80 series and-like host-based volume I                    shadowing-to most other (all other?) supported storagee                    devices.   E                    The following sections describe both Mini-Copy and G                    Mini-Merge, and can provide a basis for discussions.   '           _____________________________             5.42.7.1.1  Mini-Copy?  I                    A Shadowing Full Copy occurs when you add a disk to anpG                    existing shadowset using a MOUNT command; the entiresE                    contents of the disk are effectively copied to therF                    new member (using an algorithm that goes through inF                    127-block increments and reads one member, comparesH                    with the target disk, and if the data differs, writesD                    the data to the target disk and loops back to theC                    read step, until the data is equal for that 127-sF                    block section). (This is one of the reasons why theG                    traditional recommendation for adding new volumes todF                    a shadowset was to use a BACKUP/PHYSICAL copy of anF                    existing shadowset volume, simply because the readsJ                    then usually matched and thus shadowing usually avoided,                    the need for the writes.)                      5-64t               0                    System Management Information        G                    If you warn OpenVMS ahead of time (at dismount time) I                    that you're planning to remove a disk from a shadowset B                    but re-add it later, OpenVMS will keep a bitmapE                    tracking what areas of the disk have been modified H                    while the disk was out of the shadowset, and when youH                    re-add it later with a MOUNT command OpenVMS only hasI                    to update the areas of the returned disk that the bit- G                    map indicates are now out-of-date. OpenVMS does this H                    with a read source / write target algorithm, which isG                    much faster than the shenanigans the Full Copy does, I                    so even if all of the disk has changed, a Mini-Copy is +                    faster than a Full Copy.o  '           _____________________________d!           5.42.7.1.2  Mini-Merge?n  F                    A Shadowing Merge is initiated when an OpenVMS nodeI                    in the cluster (which had a shadowset mounted) crashesMH                    or otherwise leaves unexpectedly, without dismountingI                    the shadowset first. In this case, OpenVMS must ensureCI                    that the data is identical, since Shadowing guaranteesnD                    that the data on the disks in a shadowset will beJ                    identical. In a regular Merge operation, Shadowing usesJ                    an algorithm similar to the Full Copy algorithm (exceptE                    that it can choose either of the members' contents H                    as the source data, since both are considered equallyJ                    valid), and scans the entire disk. Also, to make thingsF                    worse, for any read operations in the area ahead ofG                    what has been merged, Shadowing will first merge the H                    area containing the read data, then allow the read to                    occur.   B                    A Merge can be very time-consuming and very I/OH                    intensive. If a node crashes, the surviving nodes canF                    query to determine what exact areas of the disk theF                    departed node was writing to just before the crash,H                    and thus Shadowing only needs to merge just those fewF                    areas, so this tends to take seconds, as opposed toI                    potentially requiring many minutes or even hours for ar&                    regular full Merge.        J                                                                       5-65 s  i          0                    System Management Information      D           __________________________________________________________;           5.43  Please explain DELETE/ERASE and File Locks?   D                    DELETE/ERASE holds the file lock and also holds aG                    lock on the parent directory for the duration of theiF                    erasure. This locking can obviously cause an accessC                    conflict on either the file or on the directory- E                    it might well pay to rename files into a temporaryeF                    directory location before issuing the DELETE/ERASE,G                    particularly for large files and/or for systems withLD                    multiple overwrite erase patterns in use; for anyH                    systems where the DELETE/ERASE erasure operation will                     take a while.  D           __________________________________________________________'           5.44  Managing File Versions?y  A                    Some applications will automatically roll filerE                    version numbers over, and some will require manualRJ                    intervention. Some will continue to operate without theI                    ability to update the version, and some will be unable I                    to continue. Some sites will specifically (attempt to) H                    create a file with a version of ;32767 to prevent the5                    creation of additional files, too.l  D                    To monitor and resolve file versions, you can use&                    commands including:  6                    $ SET FILE/VERSION_LIMIT=n filename>                    $ SET DIRECTORY/VERSION_LIMIT=n [directory]  E                    And you can also monitor file version numbers, and I                    can report problems with ever-increasing file versions G                    to the organization(s) supporting the application(s) H                    generating files with ever-increasing version numbersA                    for details on potential problems, and for any G                    recommendations on resetting the version numbers for E                    the particular product or package. If required, of]                    course.  F                    The following pair of DCL commands-though obviouslyC                    subject to timing windows- can be used to renametG                    all the versions of a file back down to a contiguousg6                    sequence of versions starting at 1:  4                    $ RENAME file.typ;*   RENAME.TMP;2                    $ RENAME RENAME.TMP;* file.typ;                      5-66o               0                    System Management Information        H                    The key to the success of this RENAME sequence is theH                    specification of (only) the trailing semicolon on theC                    second parameter of each of the RENAME commands.   E                    You may also see the numbers of files reduced withiF                    DELETE commands, with multiple directories, or withA                    PURGE commands such as the following examples:5  '                    $ PURGE/BEFORE="-2-"S,                    $ PURGE/BEFORE="TODAY-2-"#                    $ PURGE/KEEP=10"t  H                    You can use DFU (Freeware) to quickly and efficientlyD                    scan for all files with large(r) version numbers:  2                    DFU SEARCH/VERSION=MINIMUM=nnnn  D                    If you are creating or supporting an application,G                    selecting temporary or log file filenames from amongmH                    a set of filenames-selecting filenames based on time,E                    on process id, on the day of week, week number, or J                    month, on the f$unique lexical (V7.3-2 and later), etc-H                    is often useful, as this approach more easily permitsG                    on-line adjustments to the highest file versions and C                    easily permits on-line version compression using D                    techniques shown above. With differing filenames,D                    you are less likely to encounter errors resultingE                    from files that are currently locked. You can alsoeG                    detect the impending version number limit within theeH                    application, and can clean up older versions and roll@                    the next file version creation to ;1 or such.  (                    Also see Section 9.4.  D           __________________________________________________________5           5.45  Host-based Volume Shadowing and RAID?   J                    Host-based Volume Shadowing (HBVS) is Disk Mirroring is                     RAID Level 1.  D                    HBVS is capable of shadowing devices of different>                    geometries, of different block counts (withE                    dissimilar device shadowing; allowing for mixtureseD                    of hardware) and-with dynamic volume expansion-ofE                    growing volumes on the fly, and HBVS is capable of G                    shadowing/mirroring/raid-1 operations across clusterHD                    configurations up to the full span-please see the  J                                                                       5-67 d  e          0                    System Management Information        B                    Cluster SPD for the current supported span; theF                    supported span limit is currently multiple hundredsG                    of kilometers-of a cluster. HBVS can be layered onto 7                    controller (hardware) RAID, as well.s  I                    For information on host-based striping, please see thee-                    StorageWorks RAID product.                                                                                               5-68r i                       J                    _______________________________________________________  &           6        Information on Mail      D           __________________________________________________________J           6.1  MAIL keeps saying I have new messages, but I don't. What do                I do?  J                    if you see the %MAIL-W-NONEWMAIL, no new messages errorG                    reported when MAIL indicates you have messages, then D                    the NEWMAIL count has become skewed from reality.  D                    The count of new mail messages is kept separatelyC                    from your mail folder, and is stored in VMSMAIL__E                    PROFILE.DATA. It sometimes happens that this count F                    differs from what is stored in your mail folder. IfD                    this arises, invoke MAIL and repeatedly enter theF                    READ/NEW command (or press the keypad hyphen key onG                    an LK-compatible keyboard) until you see no new mailoG                    messages. Then enter the command one more time. Thise3                    will resynchronize the counters.n  G                    If you are operating in a cluster and find your mailpC                    counts inconsistent across cluster members, youriJ                    customer is likely missing a definition of the VMSMAIL_D                    PROFILE logical name-and is probably also missingE                    definitions of other logical names associated with E                    other shared files-or has one or more inconsistentnI                    definitions of this and likely of other logical names.n  C                    For details on the configuration data files thatm>                    must be shared within a cluster, please seeE                    SYS$STARTUP:SYLOGICALS.TEMPLATE on V7.2 and later.o  D           __________________________________________________________=           6.2  How do I send or read attachments in VMS MAIL?a  F                    Is there any way to send or read mail with files as(                    attachments from VMS?      J                                                                        6-1 s             &                    Information on Mail        I                    Not directly with the OpenVMS MAIL facility, but thereL-                    are several other options:   H                    o  Install PINE, available commercially from InnosoftF                       or free from Andy Harper. With PINE you can bothE                       send and receive MIME messages, if you have thea4                       appropriate viewers available.  /                      o  http://www.process.com/s  G                      o  http://www.agh.cc.kcl.ac.uk/files/vms/pine-vms/   >                      o  ftp://ftp2.kcl.ac.uk/pub/vms/pine-vms/  G                    o  If you are working from an X Windows display, youlJ                       can use the OpenVMS version of Netscape Navigator orJ                       Mozilla. The mail download protocol chosen to accessH                       the mail server from the Navigator or Mozilla mailH                       client can be POP or IMAP, with the former causingH                       messages to be downloaded while the latter permitsF                       messages to be retained on the mail server. Most8                       folks prefer IMAP for this reason.  G                    o  MPACK/MUNPACK. To send a MIME mail, construct theiH                       message with attachments manually using MPACK. YouJ                       cannot send the resulting file directly through MAILI                       because an extra blank header line will be insertedcH                       between your message and the OpenVMS MAIL headers,J                       which will cause the message to appear as plain textG                       in most mail programs. Some TCP/IP stacks provide I                       a work around for this problem, and if that doesn't E                       work, you should generally be able to force the F                       message directly into the SMTP port of your mail?                       machine. Examples of both methods are in:e  Q                      o  http://saf.bio.caltech.edu/pub/software/openvms/mmail.com   C                       To read a MIME mail message, open it in MAIL, E                       extract it to a file, then use MUNPACK to break 5                       out and decode the attachments.   G                       MPACK/MUNPACK tools are also available on OpenVMSt$                       Freeware V5.0.  D                    o  With OpenVMS V7.2 and later, use the MIME tool,                       supplied with OpenVMS.                      6-2 s  b          &                    Information on Mail      D           __________________________________________________________4           6.3  How can I block SMTP mail relay spam?  G                    Use the anti-spam capabilities present in the TCP/IP 8                    Services V5.1 and later SMTP servers.  "                    Use a firewall.  G                    On earlier TCP/IP Services releases, some simple DCL F                    can reportedly prevent relay SMTP spam. Use the UCXG                    command SHOW SERVICE SMTP/FULL to find the directory E                    containing the UCX$SMTP_RECV_STARTUP.COM file, and ,                    insert the following DCL:             $       !U           $       ! Block spam.s           $       ! P           $       MY_ADDRESS_LONG[0,32]=F$INTEGER(F$TRNLNM("SYS$REM_NODE")-"::")R           $       MY_ADDRESS=F$FAO("!UB.!UB.!UB.!UB",F$CVUI(0,8,MY_ADDRESS_LONG),-M                    F$CVUI(8,8,MY_ADDRESS_LONG),F$CVUI(16,8,MY_ADDRESS_LONG),- 2                    F$CVUI(24,8,MY_ADDRESS_LONG))'">           $       MY_ADDRESS_REVERSE=F$FAO("!UB.!UB.!UB.!UB",-N                    F$CVUI(24,8,MY_ADDRESS_LONG),F$CVUI(16,8,MY_ADDRESS_LONG),-M                    F$CVUI(8,8,MY_ADDRESS_LONG),F$CVUI(0,8,MY_ADDRESS_LONG))'" S           $       WRITE SYS$OUTPUT F$TIME()+" "+F$TRNLNM("SYS$REM_NODE")+MY_ADDRESS D           $       UCX SHOW HOST 'MY_ADDRESS_REVERSE'.INPUTS.ORBS.ORG!           $       IF $STATUS.EQ.1A           $       THEN?           $         WRITE SYS$OUTPUT "SPAM from relay rejected"O           $         EXIT           $       ENDIF"I           $       UCX SHOW HOST 'MY_ADDRESS_REVERSE'.SPAMSOURCES.ORBS.ORG1!           $       IF $STATUS.EQ.1            $       THENA           $         WRITE SYS$OUTPUT "SPAM source relay rejected"            $         EXIT           $       ENDIF_           $       ! !           $       ! Run receiver.E           $       ! 6           $       run sys$system:ucx$smtp_receiver.exe           $       goto exit       J                                                                        6-3 N  "                    J                    _______________________________________________________  +           7        Information on Utilities       D           __________________________________________________________;           7.1  How do I play an audio CD on my workstation?   F                    If you've installed the DECwindows examples, you'llD                    find DECW$CDPLAYER.C, .DAT, .EXE, .UIL, and .UID.F                    Copy the .UID and .DAT files to DECW$USER_DEFAULTS:B                    (typically SYS$LOGIN:), define the logical nameF                    DECW$CD_PLAYER to be the device name of your CD-ROMI                    drive (eg. DKA400:), give yourself PHY_IO and DIAGNOSE_F                    privileges, and run the .EXE. (These privileges areG                    required, as the access to the CD-related extensionssG                    will require the use of the privilege-protected IO$_.D                    DIAGNOSE I/O function code.) You can also installF                    the image with these privileges. See the source forH                    additional details - note that the comments regardingG                    the need for SYSGEN CONNECT are no longer applicableS/                    (at least as of VMS V5.5-2).X  D                    There's also SYS$EXAMPLES:CDROM_AUDIO.C and .EXE,E                    a non-Motif program, available on OpenVMS VAX, andtC                    DECW$EXAMPLES:DECW$CDPLAYER.* on OpenVMS VAX andn!                    OpenVMS Alpha.   E                    The standard OpenVMS ATA (IDE) SYS$DQDRIVER device A                    driver does not support the necessary does not C                    support the necessary IO$_DIAGNOSE function codeS@                    that is required for access to audio CD mediaD                    commands (on OpenVMS versions prior to V7.3), but@                    an updated SYS$DQDRIVER device driver (sourceB                    code and all) with this capability and with theC                    source code of an updated DECW$CDPLAYER CD audionF                    player is available on the OpenVMS Freeware websiteA                    (www.hp.com/go/openvms/freeware/, look for thesD                    directory /dqdriver/), and these updates are alsoE                    included on OpenVMS Freeware V5.0, and OpenVMS ECOeC                    kits containing newer versions of the driver areRE                    available. Freeware V6.0 has a version of DQDRIVERbF                    that is newer than that of the OpenVMS Alpha V7.3-2  J                                                                        7-1 w  i          +                    Information on Utilities,        J                    release, with additional capabilities and with improved%                    error diagnostics.S  D                    OpenVMS Alpha V7.3 and later include a version ofH                    SYS$DQDRIVER with the necessary IO$_DIAGNOSE support.  D           __________________________________________________________C           7.2  How do I access a Microsoft Windows floppy disk from                 OpenVMS?   G                    The HP Advanced Server (formerly known as PATHWORKS) B                    for OpenVMS product includes an unsupported andH                    undocumented utility called PCDISK, and this tool canH                    read and write various Microsoft MS-DOS and MicrosoftG                    Windows FAT-format diskettes, and can usually access_I                    FAT-format volumes written by other operating systems.   G                    ProGIS in Germany sells a product called VMove which I                    supports DOS files on many different device types. For A                    more information, send mail to info@progis.de.   C                    Engineering Software has a product called VAKSAT H                    which will read, write, and erase files on MS-DOS FATG                    diskettes. Available for both VAX and Alpha. Contact ;                    ed@cityscape.co.uk for more information.g  E                    MadGoat PC Exchange (PCX) is a utility for copying G                    files to and from MS-DOS and Microsoft Windows (FAT)iH                    format diskettes under OpenVMS, using an RX23 (3.5"),H                    RX26 (3.5"), or RX33 (5.25") diskette drive. For 3.5"H                    diskettes, high-density disks can be read or written;H                    double-density disks are read-only. Only high-density3                    disks are supported on the RX33.e  -                    o  http://www.madgoat.com/x  F                    The Freeware package WINFX is available on Freeware?                    V6.0, and can read the FAT volume structure.   <                    o  http://www.hp.com/go/openvms/freeware/                            7-2 k  e          +                    Information on Utilitiesn      D           __________________________________________________________E           7.3  How do I play sound files on an AlphaStation? DECsoundd                doesn't work.  F                    Various of the more recent AlphaStation systems useH                    a different sound board (Microsoft Sound System) thanE                    the earlier DEC 3000 series systems, and DECsound,oC                    as supplied by DECwindows Motif, doesn't support G                    this board nor this interface. HP offers an optional_C                    product, Multimedia Services (MMOV) for OpenVMS:   9                    o  http://h18000.www1.hp.com/info/spd/   H                       OpenVMS typically uses SPD 25.01.xx, SPD 41.87.xx,'                       and SPD 82.35.xx.e  J                    which provides a replacement for DECsound for this cardJ                    as well as many other features (an AVI and MPEG player,/                    video capture support, etc.)   ;                    Ensoniq sound support is also available.   D           __________________________________________________________9           7.4  How do I read IBM EBCDIC tapes on OpenVMS?   J                    Most (all?) IBM EBCDIC-based systems can read and writeD                    ANSI-labeled ASCII magtapes. Fixed-length recordsF                    (MOUNT /FOREIGN /BLOCKSIZE=512 /RECORDSIZE=512, forE                    one-block records) and the DCL COPY command can beoI                    used to transfer fixed-record-size text files out ontooG                    tape media, or to read from fixed-record tape media._G                    Please consult the IBM documentation for the details J                    and command syntax needed when reading and writing ANSIF                    media using IBM JCL or other applicable IBM command                    language.  I                    There exists various freeware around (TAPECOPY, ETAPE, G                    TCOPY, MTEXCH) that can read and write EBCDIC tapes.eC                    Visit the Encompasserve (DECUS) website software E                    archives search engine and search for "EBCDIC" forl                    details.h  0                    o  http://www.encompassus.org  B                    OpenVMS does not include an integrated tool forG                    EBCDIC tape processing, but does provide a character E                    conversion API useful within application programs.   J                                                                        7-3               +                    Information on Utilities         +                    One source for ETAPE is:h  <                    o  http://www.ualr.edu/ftp/vms/ETAPE_SRC/  G                    The OpenVMS Freeware V5.0 distribution included this '                    ETAPE tool, as well.   D           __________________________________________________________6           7.5  How can I patch an OpenVMS Alpha image?  7                    Using the OpenVMS Freeware tool ZAP:   H                    o  Look for the RMS_TOOLS directory on Freeware V5.0:<                       http://www.hp.com/go/openvms/freeware/  C                    tell ZAP to read a block (bucket) of information G                    based on the virtual block number (VBN), using X for G                    hexadecimal. Dump yourself into the OpenVMS debugger_H                    with R2 pointing into the buffer, EXAMINE/INSTRUCTIONI                    as needed, alter the buffer as required, GO to get outZG                    of the debugger and back into ZAP, and use the ZAP We6                    command to write the updated block.                                                                7-4    o                    J                    _______________________________________________________             8        DCL Details      D           __________________________________________________________5           8.1  DCL Symbols and OpenVMS Logical Names?   J                    DCL symbols are programming-style variables implementedD                    within the DCL command interpreter, and these areC                    used both for programming and to provide command B                    verb synonyms. Symbols are local to the commandE                    interpreter operating within a particular process, J                    and are not shared. Lists of symbols can be copied intoG                    subprocesses during a subprocess creation operation,mE                    but these symbols are neither copied back into theiD                    parent process when the subprocess exits, nor are8                    symbols ever shared across processes.  D                    Symbols can be specified in and utilized in basicH                    mathematical operations, and bit-level operations areF                    available with the f$cvsi and f$cvui bit extractionB                    lexical functions, and with the square-bracketsF                    notation for bit insertion (see Section 8.13 for anG                    example), and with bitwise operators. Symbols are ofbH                    two basic types, STRING and INTEGER, and these (or anJ                    undefined symbol) can be differentiated with the f$typeF                    lexical function. DCL symbols can also be used as aI                    mechanism to abbreviate a DCL command verb, or an easyn9                    way to invoke a DCL command procedure.-  B                    Symbols can have local or global scope within aE                    process, and scope is affected by nested proceduremG                    calls and DCL constructs such as CALL and SET SCOPE, D                    but such discussions are beyond the scope of this                    section.   G                    OpenVMS Logical names can store device names, device E                    and directory specifications, rooted or searchlist H                    specifications, and full filenames. Logical names canE                    also store arbitrary data, but there are no nativesI                    mathematical or bitwise operators available. AnalogousDE                    to DCL symbols, process-local logical names can be H                    copied into subprocesses during a subprocess creation  J                                                                        8-1  