======================================================================= HP OpenVMS Update kit for Alpha and VMS84A_UPDATE-V0500 Release Notes ======================================================================= 1 KIT NAME: VMS84A_UPDATE-V0500 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_1 : To be installed by all customers. This installation rating, based upon current CLD information, is provided to serve as a guide to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement) 2.2 Reboot Requirement: Reboot Required. HP strongly recommends that a reboot is performed immediately after kit installation to avoid system instability. If you have other nodes in your OpenVMS cluster, they must also be rebooted in order to make use of the new image(s). If it is not possible or convenient to reboot the entire cluster at this time, a rolling re-boot may be performed. 2.3 Version(s) of OpenVMS to which this kit may be applied: OpenVMS for Alpha Servers V8.4 2.4 New functionality or new hardware support provided: - HP StorageWorks LTO-5 Ultrium Tape Drives. For additional information, see the following website: http://h18006.www1.hp.com/storage/tapestorage/index.html?psn=storage 3 KITS SUPERSEDED BY THIS KIT: - VMS84A_UPDATE-V0400 - VMS84A_MUP-V0100 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS84A_PCSI-V0200 4.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: - None. 5 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS84A_UPDATE-V0500 KIT 5.1 New functionality addressed in this kit 5.1.1 Addition of the OpenVMS C RTL decc$get_channel() API function The OpenVMS C RTL decc$get_channel() API function is introduced to obtain the channel number for sockets and mailbox that are opened by the fopen() call. The decc$get_channel() API function verifies the following: i) The fab$l_dev of the fab structure has the flag DEV$M_MBX set and returns fab$l_stv, which includes the mailbox channel number. ii) The issocket of the FCB structure is set and returns the fcb->channel, which includes the socket channel number. The syntax for the decc$get_channel() API function is: unsigned short int decc$get_channel(__FILE *fp) Arguments: FILE * Returns : unsigned short int The decc$get_channel () API returns the channel number: 1) (fab$l_stv) for mailbox if the fab$l_dev has DEV$M_MBX set. 2) (fcb->channel) for socket if fcb->issocket is set. On failure, the decc$get_channel() API returns 0 with errno set to EINVAL. To use decc$get_channel() function, declare the following in your application: extern unsigned short int decc$get_channel(__FILE *fp); Images Affected: - [SYSLIB]DECC$SHR_EV56.EXE 5.1.2 ACME LDAP - multiple redundant directory servers support The Authentication Credentials Management Extensions (ACME) Lightweight Directory Access Protocol (LDAP) can now be configured to search multiple redundant directory servers for user authentication. ACME LDAP tries to connect to a set of directory servers, in a sequence, until it receives a successful connection. This is useful when the first directory server is not reachable or inactive. The LDAP user's login into the OpenVMS system is not blocked and users are authenticated against the next directory server that is active. The "bind_timeout" directive is a new directive included in this release. To provide multiple redundant servers, the "server", "bind_timeout", and "ca_file" (optional) directive must be updated in the LDAP configuration file. For more information, see Section "Editing LDAP Configuration file" in the SYS$HELP:ACMELDAP_STD_CONFIG_INSTALL.PDF. Images Affected: - [SYSLIB]SYS$STARLET_C.TLB - [SYSLIB]LDAP$SHR.EXE - [SYSLIB]LDAPACME$LDAP-STD_ACMESHR.EXE - [SYSHLP]ACMELDAP_STD_CONFIG_INSTALL.PDF - [SYSHLP]ACMELDAP_STD_CONFIG_INSTALL.TXT - [SYS$STARTUP]LDAPACME$CONFIG-STD.INI_TEMPLATE 5.1.3 New triple DES example added in ENCRYPT$EXAMPLES A new example file ENCRYPT$EXAMPLES:ENCRYPT_3DES.C is provided. The example file uses the Data Encryption Standard (DES) APIs to encrypt and decrypt data in 3DES by using 64-bits of data at a time. For more information, see the comments in the ENCRYPT$EXAMPLES:ENCRYPT_3DES.C file. Images Affected: - [SYSHLP.EXAMPLES.ENCRYPT]ENCRYPT_3DES.C - [SYSHLP.EXAMPLES.ENCRYPT]ENCRYPT$EXAMPLES.TXT 5.1.4 Improvements to cluster communication (PEdriver) 5.1.4.1 Cluster over IP (IPCI) improvements - Transmit window The default transmit window for an IP channel has been increased from 8 to 128. This results in better throughput using an IP channel. - Line speed for IP interface In the Cluster over IP environment, the MCR SCACP SHOW IP_INTERFACE command now displays the correct line speed value for the IP interface. ' Images Affected: - [SYS$LDR]SYS$PEDRIVER.EXE - [SYS$LDR]SYS$PEDRIVER.STB - [SYS$LDR]SYS$PEDRIVER_MON.EXE - [SYS$LDR]SYS$PEDRIVER_MON.STB 5.2 Problems addressed in this kit 5.2.1 MACRO compiler generates incorrect debugging information 5.2.1.1 Problem Description: MACRO compiler generates incorrect debugging information for certain variables. When you try to access these variables, the debugger displays an error message. This problem has been fixed. Images Affected: - [SYSEXE]MACRO.EXE Quix cases reporting this problem: None. 5.2.1.2 Work-arounds: None. 5.2.4 Maximum limit for the IMGREG_PAGES SYSGEN parameter is modified 5.2.4.1 Problem Description: Currently, the maximum permissible value for the IMGREG_PAGES SYSGEN parameter is set to 131072 pages. Setting the IMGREG_PAGES SYSGEN parameter to 131072 pages occupies all of the P1 space and denies memory required for other structures. This renders the system unbootable. This problem has been fixed. The maximum limit for the IMGREG_PAGES SYSGEN parameter is now modified to 80000 pages. Images Affected: - [SYS$LDR]SYS$BASE_IMAGE.EXE - [SYSLIB]SDA$SHARE.EXE - [SYSEXE]SYSGEN.EXE - [SYSEXE]SYSBOOT.EXE - [SYSEXE]SYSMAN.EXE - [SYSEXE]SMISERVER.EXE Quix cases reporting this problem: QXCM1000943395 5.2.4.2 Work-arounds: None. 5.2.5 OpenVMS crashes during boot due to a mouse event 5.2.5.1 Problem Description: An event generated by the mouse such as scrolling the mouse wheel while a USB mouse is being plugged-in or while DECwindows is starting up, might cause a system crash. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$IKUDRIVER.EXE - [SYS$LDR]SYS$IMUDRIVER.EXE Quix cases reporting this problem: QXCM1000898776 5.2.5.2 Work-arounds: None. 5.2.6 Potential system crash while booting if bit 7 of MMG_CTLFLAGS is enabled 5.2.6.1 Problem Description: On OpenVMS Alpha systems, setting bit 7 in the MMG_CTLFLAGS SYSGEN parameter causes a system crash on boot. HP recommends you clear bit 7 in MMG_CTLFLAGS SYSGEN parameter to 0 in both the ACTIVE and CURRENT SYSGEN databases. A footprint of the possible crash due to this problem is as follows: Crash Time: 1-JAN-2010 00:00:00.00 Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL VMS Version: V8.4 Current Process: Current Image: Failing PC: FFFFFFFF.80073F58 MMG_STD$SUBSECREFL_C+00488 Failing PS: 30000000.00001F00 Module: SYSTEM_PRIMITIVES_MIN (Link Date/Time: 3-SEP-2010 12:17:39.74) Offset: 0003FF58 : Failing Instruction: MMG_STD$SUBSECREFL_C+00488: LDL R28,#X00D8(R1) : SDA> sho param mmg_ctlflags ! bit 7 is set Parameter Variable Address Value (decimal) --------------- ------------------ -------- -------- ---------- MMG_CTLFLAGS MMG$GB_CTLFLAGS 81812BC0 83 131 This problem has been fixed. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB Quix cases reporting this problem: QXCM1001075945 5.2.6.2 Work-arounds: None. 5.2.7 AUTOGEN changes to handle a target disk of size in the range of 1 TiB to 2 TiB 5.2.7.1 Problem Description: DCL supports 32-bit operations. However, the 32nd bit is a sign extension bit. On a disk with size greater than 1 TiB, the number of free blocks on the disk is represented as a negative value by DCL. This results in many of the checks in AUTOGEN to fail and print invalid error messages with respect to available free space on the disk even when there is sufficient free space available on the disk. AUTOGEN has been modified to handle this situation as a part of the update to support 2 TiB volumes. Images Affected: - [SYSUPD]AUTOGEN.COM Quix cases reporting this problem: None. 5.2.7.2 Work-arounds: None. 5.2.8 Unable to access a directory with Unicode characters in the directory name 5.2.8.1 Problem Description: An attempt to access a directory with Unicode characters in the directory name, fails with the following error message: $ dir [.^U3042] %DIRECT-E-OPENIN, error opening SYS$SPECIFIC:[SYSMGR.TMP.KANJIDIR.^U3042]*.*;* as input RMS-E-DNF, directory not found -SYSTEM-W-NOSUCHFILE, no such file $ This problem has been fixed. Images Affected: - [SYS$LDR]RMS.EXE Quix cases reporting this problem: None. 5.2.8.2 Work-arounds: None. 5.2.9 SEARCH/NOWARN is unable to suppress unresolved symbolic link errors 5.2.9.1 Problem Description: When the DCL command SEARCH with /NOWARN qualifier is issued on a symbolic link pointing to a non-existing file, the SEARCH/NOWARN command is unable to suppress the "RMS-E-FNF, file not found" error message. For example, $DIR/LINK LINK.DAT Directory SYS$SYSDEVICE:[DOC] LINK.DAT;1 -> file.txt 0 Total of 1 file. $ SEARCH/NOWARN LINK.DAT "HELLO WORLD" %SEARCH-W-OPENIN, error opening SYS$SYSDEVICE:[DOC]LINK.DAT;1 as input -RMS-E-FNF, file not found This problem has been fixed. Images Affected: - [SYSEXE]SEARCH.EXE Quix cases reporting this problem: None. 5.2.9.2 Work-arounds: None. 5.2.10 FLT SHOW TRACE/SUMMARY report is misleading for process space PC value(s) 5.2.10.1 Problem Description: The FLT SHOW TRACE/SUMMARY report is misleading for process space PC value(s) because the symbolization of the PC value(s) reflects the current System Dump Analyzer (SDA) process context. Two new qualifiers, /INDEX and /IDENT, are now added to summarize the fault trace information for a particular process: FLT SHOW TRACE/SUMMARY/INDEX= FLT SHOW TRACE/SUMMARY/IDENT= With these new features, FLT SHOW TRACE/SUMMARY can summarize the FLT trace information specific to a process based on PID or index. This problem has been fixed. Images Affected: - [SYS$LDR]FLT$DEBUG.EXE - [SYSLIB]FLT$SDA.EXE Quix cases reporting this problem: QXCM1000858646, QXCM1000952887 5.2.10.2 Work-arounds: None. 5.2.11 Image Activation fails with insufficient privilege or object protection violation 5.2.11.1 Problem Description: When multiple jobs are running in parallel, image activation fails with insufficient privilege or object protection violation for the installed image as follows: %DCL-W-ACTIMAGE,error activating image XXX -CLI-E-IMGNAME, image file DEV:[XXX.][SYSLIB]XXX.EXE -SYSTEM-F-NOPRIV, insufficient privilege or object protection violation This problem has been fixed. Images Affected: - [SYS$LDR]SYS$VM.EXE - [SYS$LDR]SYS$VM.STB Quix cases reporting this problem: QXCM1001050875 5.2.11.2 Work-arounds: None. 5.2.12 The SMISERVER process crashes when it invokes a request on a remote node 5.2.12.1 Problem Description: In a cluster environment, account errors such as "%LOGIN-F-DISUSER, account is disabled" are displayed and the SMISERVER aborts with a process dump. This occurs when there are different User Authorization Files (UAFs) in a cluster and if the currently used account is set to DISUSER. $ MCR SYSMAN SET ENVIRONMENT/CLUSTER %SYSMAN-I-ENV, current command environment: Clusterwide on local cluster Username SAHOO will be used on nonlocal nodes SYSMAN> DO SHOW TIME %SYSMAN-I-OUTPUT, command execution on node NODE1 17-SEP-2010 19:29:32.19 %SYSMAN-I-OUTPUT, command execution on node NODE2 %SYSMAN-I-NODERR, error returned from node NODE2 -SMI-E-ABORT, SMI Server has aborted This problem has been fixed. Images Affected: - [SYSEXE]SMISERVER.EXE Quix cases reporting this problem: QXCM1000999438 5.2.12.2 Work-arounds: None. 5.2.13 Problem opening an RMS indexed file with a large number of global buffers 5.2.13.1 Problem Description: When a large number of global buffers are specified on a Record Management Services (RMS) indexed file, the RMS system service SYS$CONNECT fails with the error codes -RMS-F-CRMP and RMS-F-DME as primary and secondary status respectively. For example, $ SET FILE/GLOBAL_BUFFER=COUNT=1270400 TEST$DISK:[FOO]SYSUAF.DAT $ TYPE TEST$DISK:[FOO]SYSUAF.DAT %TYPE-W-OPENIN, error opening TEST$DISK:[FOO]SYSUAF.DAT;1 as input -RMS-F-CRMP, CRMPSC system service failed to map global buffers -RMS-F-DME, dynamic memory exhausted A high-level language file open request, such as OPEN in FORTRAN, also exhibits this problem, as the operation internally includes a call to SYS$CONNECT, on a file with the same RMS global buffer attributes. This problem has been fixed. Images Affected: - [SYS$LDR]RMS.EXE Quix cases reporting this problem: QXCM1001062201 5.2.13.2 Work-arounds: None. 5.2.14 Use of DCL commands or RTL routines that SPAWN sub-processes may experience an infinite loop or process hang 5.2.14.1 Problem Description: A parent process can spawn sub-processes with either the WAIT or NOWAIT option. If the sub-process is spawned with the WAIT option, the parent process waits for the completion of the sub-process. Sometimes a sub-process can terminate normally or abnormally even before the parent process gets into the WAIT state. This condition leads to the parent process waiting for the sub-process indefinitely. This may be seen when using DCL commands such as SPAWN and PIPE, or programs that use the LIB$SPAWN RTL routine. For more information, see the customer advisory at: http://h41302.www4.hp.com/km/saw/view.do?docId=emr_na-c02584511 This problem has been fixed. Images Affected: - [SYSEXE]DCL.EXE Quix cases reporting this problem: QXCM1001056367, QXCM1001078968 5.2.14.2 Work-arounds: None. 5.2.15 The COPY command might display an incorrect progress report 5.2.15.1 Problem Description: Pressing CTRL/T when using COPY command to append a large number of input files to an output file, displays an incorrect progress report (0% completed). For example, $ COPY TEST.LOG;* TEST.NEW DRWHO::SYSTEM 14:54:47 COPY CPU=00:04:29.78 PF=1431975 IO=806207 MEM=170 Copying: DSA15:[CARRD]TEST.LOG;18033 (0% completed) 0 blocks copied of 4294447434 This problem has been fixed. Images Affected: - [SYSEXE]COPY.EXE Quix cases reporting this problem: QXCM1000975987 5.2.15.2 Work-arounds: None. 5.2.16 After executing STOP/QUEUE/RESET, the queue manager crashes 5.2.16.1 Problem Description: Attempting to delete a non-existing job entry after executing STOP/QUEUE/RESET causes the queue manager to crash with the following messages that are reported to the operator console and log: %%%%%%%%%%% OPCOM 22-OCT-2010 13:51:32.06 %%%%%%%%%%% Message from user SYSTEM on CLT94C %QMAN-F-BADLOGIC, internal logic error detected at PC 00111070 %%%%%%%%%%% OPCOM 22-OCT-2010 13:51:32.74 %%%%%%%%%%% Message from user SYSTEM on CLT94C %JBC-E-QMANDEL, unexpected queue manager process termination This problem has been fixed. Images Affected: - [SYSEXE]QMAN$QUEUE_MANAGER.EXE Quix cases reporting this problem: QXCM1001079988 5.2.16.2 Work-arounds: None. 5.2.17 The "Default" value for the SYSTEM_CHECK system parameter is set to 1 after installing the VMS84A_UPDATE-V0400 kit 5.2.17.1 Problem Description: After installing the VMS84A_UPDATE-V0400 kit on OpenVMS Alpha servers Version 8.4, the "Default" value of the SYSTEM_CHECK system parameter is set to 1. However, certain operations (such as running AUTOGEN) cause the SYSTEM_CHECK "Default" value to be moved to the "Current" value. If this occurs, the system will run using a value of 1. For most installations, this is not the desired value and can cause performance slowdowns. This problem has been fixed. Images Affected: - [SYSEXE]SYSBOOT.EXE - [SYSEXE]SYSGEN.EXE Quix cases reporting this problem: QXCM1001082915 5.2.17.2 Work-arounds: None. 5.2.18 AUTOGEN prints an UNDSYM warning message 5.2.18.1 Problem Description While running AUTOGEN, the following warning message might be displayed: "%DCL-W-UNDSYM, undefined symbol - check validity and spelling" This problem has been fixed. Images Affected: - [SYSUPD]AUTOGEN.COM Quix cases reporting this problem: QXCM1001084583 5.2.18.2 Work-arounds: None. 5.2.19 Memory leak in the LDAP API library 5.2.19.1 Problem Description: While testing the ACME LDAP external authentication under stressed condition, memory leaks were identified to be originating from LDAP$SHR.EXE. This problem has been fixed. Images Affected: - [SYSLIB]LDAP$SHR.EXE Quix cases reporting this problem: None. 5.2.19.2 Work-arounds: None. 5.2.20 Performance issues during login of users using ACME LDAP 5.2.20.1 Problem Description: When a large number of users try to login at the same time, the users who try to login after a few minutes see a blank screen and timeout messages. If an LDAP connection to the directory server is slow, the users will get blank screen and timeout messages. These problems have been fixed. Images Affected: - [SYSLIB]LDAPACME$LDAP-STD_ACMESHR.EXE Quix cases reporting this problem: QXCM1001020715, QXCM1000904720 5.2.20.2 Work-arounds: None. 5.2.21 Autostarting ACME_SERVER does not load the LDAP ACME Agent 5.2.21.1 Problem Description: Even after defining the LDAPACME$INIT logical in the ACME$START.COM with a "/SYSTEM/EXECUTIVE" qualifier, on autostart of the ACME_SERVER process, the logical is defined with only a /SUPERVISOR_MODE access. The LDAP ACME agent will not load if the LDAPACME$INIT logical is not defined with a /SYSTEM/EXECUTIVE. This problem has been fixed. Images Affected: - [SYSEXE]ACME_SERVER.EXE Quix cases reporting this problem: None. 5.2.21.2 Work-arounds: None. 5.2.22 Unable to capture enough diagnostic using existing SYS$EXAMPLES:LDAP_EXAMPLE.C 5.2.22.1 Problem Description: The SYS$EXAMPLES:LDAP_EXAMPLE.C file currently do not support passing bind_dn, bind_password, port_security and ca_file parameters, thus limiting the amount of diagnostic that can be captured. The new LDAP_EXAMPLE.C is modified to accept new parameters specific to bind_dn, bind_password, port_security and ca_file. For more information, see the comments in the SYS$EXAMPLES:LDAP_EXAMPLE.C file. This problem has been fixed. Images Affected: - [SYSHLP.EXAMPLES]LDAP_EXAMPLE.C Quix cases reporting this problem: QXCM1001019671 5.2.22.2 Work-arounds: None. 5.2.23 ACME LDAP local user mapping fails 5.2.23.1 Problem Description: The LDAP local mapping does not work on some systems and user login fails due to search logic failures. This problem has been fixed. Images Affected: - [SYSLIB]LDAPACME$LDAP-STD_ACMESHR.EXE Quix cases reporting this problem: None. 5.2.23.2 Work-arounds: None. 5.2.24 Infoserver boot/installation process hangs if the specified service is unavailable or inaccessible 5.2.24.1 Problem Description: If the specified service is unavailable or inaccessible, the Infoserver boot/installation process hangs without displaying any error message. This has been fixed and now the Infoserver boot/installation process displays the following error message on the console: - If the service is unavailable, it displays the following message: "Unable to proceed further. Specified service is not available." - If the service is available, but connection to the service encountered a failure, it displays the following message: "Connection to the specified service is failed. Unable to continue." This problem has been fixed. Images Affected: - [SYS$LDR]SYS$DADDRIVER.EXE Quix cases reporting this problem: None. 5.2.24.2 Work-arounds: None. 5.2.25 MONITOR SET DEFAULT/NODE command can lead to an ACCVIO 5.2.25.1 Problem Description: When the MONITOR SET DEFAULT command is used with the /NODE qualifier to specify the default node and further monitoring is initiated, it ACCVIOs with the following footprint: $ MONITOR MONITOR> set defa/node=XYZ MONITOR> monitor proc %NONAME-W-NOMSG, Message number 00000000 %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000000000004F56, PC=FFFFFFFF80A98978, PS=0000001B This Problem has been fixed. Images Affected: - [SYSEXE]MONITOR.EXE Quix cases reporting this problem: QXCM1000750590 5.2.25.2 Work-arounds: None. 5.2.26 Exception loop in threads library 5.2.26.1 Problem Description: When an unhandled exception causes a threaded application to run down, if the exit handler encounters a wait, the threads library could cause the application to hang. Images Affected: - [SYSLIB]PTHREAD$RTL.EXE - [SYSLIB]PTHREAD$DBGSHR.EXE Quix cases reporting this problem: QXCM1001078843 5.2.26.2 Work-arounds: None. 5.2.27 MC LANCP SHOW DEVICE/COUNTERS displays the incorrect value for the last link transition date 5.2.27.1 Problem Description: A system counter holds the value of time elapsed since the system is up and running. When the value of time elapsed exceeds 249 days, the last link transition time is displayed as a future date. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$LAN_CSMACD.EXE Quix cases reporting this problem: QXCM1001019545 5.2.27.2 Work-arounds: None. 5.2.28 SHOW DEVICE/CHARACTERISTICS displays the incorrect status for jumbo frames 5.2.28.1 Problem Description: After enabling jumbo frames for a device using the MC LANCP SET DEVICE/JUMBO command, SHOW DEVICE/CHARACTERISTICS displays the jumbo frames status as disabled. In effect, the jumbo frames functionality is still enabled, which can be verified by the output of the SHOW DEVICE/INTERNAL command. There is no functionality breakage, this is only a display error. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$EW5700.EXE - [SYS$LDR]SYS$EWXFRAME.EXE Quix cases reporting this problem: QXCM1001048562 5.2.28.2 Work-arounds: None. 5.2.29 System crashes while initializing EIDRIVER 5.2.29.1 Problem Description: While initializing EIDRIVER, the system might crash. This is because the interrupt service routine attempts to provide receive buffers, which are not fully initialized to the device. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$EIDRIVER.EXE Quix cases reporting this problem: QXCM1001046157 5.2.29.2 Work-arounds: None. 5.2.30 OpenVMS C RTL stat() API function on SHADOWSET device results in ACCVIO 5.2.30.1 Problem Description: The OpenVMS C RTL stat() API function tries to find the "$" character in a loop; to retrieve the node name from the device name, without a boundary check. Because the SHADOWSET device naming convention does not include a node name, the loop does not terminate, which leads to an ACCVIO. This problem has been fixed. Images Affected: - [SYSLIB]DECC$SHR.EXE - [SYSLIB]DECC$SHR_EV56.EXE (for Alpha only) Quix cases reporting this problem: QXCM1001078785, QXCM1001083404 5.2.30.2 Work-arounds: None. 5.2.31 SYSMAN fails with the LIB-F-INSEF error message 5.2.31.1 Problem Description: SYSMAN fails with the following error message if the execution of DO commands on the remote nodes in a cluster is repeatedly aborted by a ^C interrupt: %SYSMAN-I-NODERR, error returned from node... -LIB-F-INSEF, insufficient event flags This problem has been fixed. Images Affected: - [SYSLIB]SMI$SHR.EXE Quix cases reporting this problem: None. 5.2.31.2 Work-arounds: None. 5.2.32 VMS84A_UPDATE-V0400: Boot failure on Alpha 5.2.32.1 Problem Description: The VMS84A_UPDATE-V0400 kit contains the APB.EXE image. When VMS84A_UPDATE-V0400 kit is installed, installation (upgrade) procedure for the above kit replaces the APB.EXE on the target disk but does not update the target disk’s boot block to point to the new version of OpenVMS Alpha primary bootstrap file. This may lead to a condition where the system boots with an old APB.EXE which may lead to system hang or leave the system in an unbootable state. The VMS84A_UPDATE-V0500 kit provides a solution to this and update the bootblock as a part of its INSTALL and UNINSTALL procedure. Images Affected: - [SYSEXE]APB.EXE Quix cases reporting this problem: QXCM1001104488 5.2.32.2 Work-arounds: None. 6 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed by previously released VMS84A_UPDATE patch kits can be found in the following files: o VMS84A_UPDATE-V0100.RELEASE_NOTES o VMS84A_UPDATE-V0400.RELEASE_NOTES o VMS84A_MUP-V0100.RELEASE_NOTES Before kit installation, these files can be extracted from the kit via the following commands: o To extract all release notes files at once use: PRODUCT EXTRACT RELEASE_NOTES VMS84A_UPDATE /VERSION=V5.0 - [/file=destination_directory] o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS84A_UPDATE /VERSION=V5.0 - /SELECT=release_note_name[/DESTINATION=destination_directory] The names of individual RELEASE_NOTES files in the kit can be found with: PRODUCT LIST VMS84A_UPDATE /VERSION=V5.0 /SELECT = *.RELEASE_NOTES 7 KNOWN PROBLEMS AND LIMITATIONS This section describes the known problems and limitations in this patch kit. 0 Installing OpenVMS from InfoServer with duplicate services may fail with a crash Installing OpenVMS from InfoServer crashes intermittently with the "PROCGONE" bugcheck, if the requested service is hosted by multiple servers in the same LAN. Workaround: Delete or rename the duplicate service name from one of the servers. 0 The account records for batch jobs, terminated through $ STOP/QUEUE/RESET command on a batch queue, show identical values for start and finish times and hence show zero values for Elapsed and Processor times. The accounting records also show zero values in the PID and Resource fields such as Page Faults, Direct IO, and so on. These accounting records are followed by complete and correct records for the same jobs. However, these records do not show the batch queue or entry number for those jobs. A footprint of the possible accounting record is as follows: Username: ALEX UIC: [ALEX] Account: APC Finish time: 28-OCT-2010 17:55:54.99 Process ID: 00000000 Start time: 28-OCT-2010 17:55:54.99 . . . . . . . . . . Posix UID: Posix GID: Queue entry: 12 Final status code: 000480EC Queue name: FDAY Job name: LOOP Final status text: %JBC-F-QUERESET, job aborted during execution because queue was reset . . . . . . . . . . BATCH Process Termination ------------------------- Username: ALEX UIC: [ALEX] Account: APC Finish time: 28-OCT-2010 17:56:00.03 Process ID: 2021CD29 Start time: 28-OCT-2010 17:55:42.14 . . . . . . . . . Posix UID: -2 Posix GID: -2 (%XFFFFFFFE) Queue entry: Final status code: 000480EC Queue name: Job name: Final status text: %JBC-F-QUERESET, job aborted during execution because queue was reset 0 Calls to LIB$FIND_IMAGE_SYMBOL sometimes fail with an ACCVIO while replacing shareable images installed with shared address data This problem can be found in applications where the shareable images are activated using LIB$FIND_IMAGE_SYMBOL while the shareable images are being replaced with modified images or identical images using the following commands: a. INSTALL/REMOVE - deletes the KFE b. INSTALL/ADD - allocates a KFE, which can be the same KFE 0 SHOW DEVICE command displays asterisks for the FREEBLOCKS field The SHOW DEVICE command displays asterisks for the FREEBLOCKS field when the freeblocks count is a number greater than 9 digits (approximately greater than 476 GB). The field that displays freeblocks count is limited to 9 characters long so that the output of the SHOW DEVICE command does not wrap around the last character to the next line if the terminal display width is set to 80. In such cases, the freeblocks count can be obtained in blocks using SHOW DEVICE/FULL command or in bytes using 'SHOW DEVICE/UNIT=BYTES'. Alternatively, you can use the lexicals as shown in the examples. Example-1: $ FREEBLOCKS = F$GETDVI("$1$DKB200:","FREEBLOCKS") $ STR_FREEBLOCKS = F$FAO("!ZL",FREEBLOCKS) $ SHOW SYMBOL FREEBLOCKS FREEBLOCKS = -1187997808 Hex = B9309790 Octal = 27114113620 $ SHOW SYMBOL STR_FREEBLOCKS STR_FREEBLOCKS = "3106969488" Example-2: $ STR_FREEBLOCKS = F$CUNITS(F$GETDVI("$1$DKB200:","FREEBLOCKS")) $ SHOW SYMBOL STR_FREEBLOCKS STR_FREEBLOCKS = "1.44TB" 0 Issues with RMS Multi Block Count (MBC) value greater than 127 Some issues have been observed with some MBC values greater than 127, a feature that was introduced in VMS84A_UPDATE-V0400. Contact your HP support representative for the V8.4 patch kit that resolves this issue. 0 SYSMAN I/O AUTO CONFIGURATION displays an error message related to SRDRIVER SYSMAN displays the following error message when it performs I/O AUTO CONFIGURATION of related devices: %IOGEN-E-LOADERR, error configuring device SRA0, driver SYS$SRDRIVER.EXE -RMS-E-FNF, file not found This error message appears on OpenVMS Version 8.2 and later Alpha configurations, and can be ignored. 8 DOCUMENTATION ERRATA This section describes corrections and additions to the online help and various manuals in the OpenVMS documentation set. 0 In the HP OpenVMS System Management Utilities Reference Manual: M-Z and online help, the RAD_SUPPORT system parameter must be read as: RAD_SUPPORT enables RAD-aware code to be executed on systems that support Resource Affinity Domains (RADs). For example, AlphaServer GS160 systems and Integrity cell-based servers, BL8x0c i2 server blades, or rx2800 i2 servers. An RAD is a set of hardware components (CPUs, memory, and I/O) with common access characteristics. Bits are defined in the RAD_SUPPORT parameter as follows: RAD_SUPPORT (default is 207 for Alpha and 109446674473 for Integrity servers) 0 In the HP OpenVMS Cluster Systems: Appendix A, the following changes must be made to Table A-1 Adjustable Cluster System Parameters. - For the NISCS_PORT_SERV system parameter, the last paragraph in the description column must read: You can also enable the VC use of compression by setting bit 2 of the NISCS_PORT_SERV system parameter. The /NOCOMPRESSION qualifier does not override compression enabled by setting bit 2 of NISCS_PORT_SERV. For more information, see the SCACP utility chapter, and NISCS_PORT_SERV in the HP OpenVMS System Management Utilities Reference Manual and the HP OpenVMS Availability Manager User’s Guide. - For the NISCS_MAX_PKTSZ system parameter, the fourth paragraph in the description column must read: PEDRIVER uses NISCS_MAX_PKTSZ to compute the maximum amount of data to transmit in any LAN or IP packet: LAN packet size <= (LAN header (padded Ethernet format) + NISCS_MAX_PKTSZ + NISCS checksum (only if data checking is enabled) + LAN CRC or FCS) 0 In the HP OpenVMS System Management Utilities Reference Manual: A-L and online help, the following changes must be made to the BACKUP command description in Chapter 7: - The /REPAIR qualifier description must be replaced with the following: Helps BACKUP to reset the RMS file attributes (RFM and MRS) of a save set file which can get modified while the save set is transferred through World Wide Web (WWW), copied using FTP or compressed and uncompressed using ZIP. You can use the /REPAIR qualifier to repair the save set attributes only while restoring or listing the save set. Example: 1. BACKUP/REPAIR ATT_MOD.BCK/SAVE [.SOURCE] This command first repairs the modified attributes of the save set file ATT_MOD.BCK and then restores its content to the [.SOURCE] directory. 2. BACKUP/REPAIR ATT_MOD.BCK/SAVE /LIST This command first repairs the modified attributes of the save set file ATT_MOD.BCK and then lists its content. 9 FILES PATCHED OR REPLACED: o [SYSEXE]ACC.EXE (new image) Image Identification Information image name: "ACC" image file identification: "X-25" image file build identification: "XCAV-0100000002" link date/time: 12-AUG-2010 17:19:08.45 linker identification: "A13-04" Overall Image Checksum: 2391518027 o [SYSEXE]APB.EXE (new image) Image Identification Information image name: "APB" image file identification: "X-8" image file build identification: "XCBS-0100000003" link date/time: 4-NOV-2010 16:26:06.57 linker identification: "A13-04" Overall Image Checksum: 4164445007 o [SYSEXE]AUDIT_SERVER.EXE (new image) Image Identification Information image name: "AUDIT_SERVER" image file identification: "X-13" image file build identification: "XCB1-0100000002" link date/time: 20-AUG-2010 21:42:11.34 linker identification: "A13-04" Overall Image Checksum: 1515549930 o [SYSEXE]BACKUP.EXE (new image) Image Identification Information image name: "BACKUP" image file identification: "V8.4" image file build identification: "XCBF-0100000002" link date/time: 30-SEP-2010 10:29:11.92 linker identification: "A13-04" Overall Image Checksum: 2101832595 o [SYSLIB]BACKUPSHR.EXE (new image) Image Identification Information image name: "BACKUPSHR" image file identification: "V8.4" image file build identification: "XCBF-0100000002" link date/time: 30-SEP-2010 10:28:32.17 linker identification: "A13-04" Overall Image Checksum: 355264886 o [SYSEXE]CDU.EXE (new image) Image Identification Information image name: "CDU" image file identification: "A01-13" image file build identification: "XCB1-0100000002" link date/time: 20-AUG-2010 21:42:11.16 linker identification: "A13-04" Overall Image Checksum: 1604991716 o [SYSMSG]CLIUTLMSG.EXE (new image) Image Identification Information image name: "CLIUTLMSG" image file identification: "X-3" image file build identification: "XCAV-0100000002" link date/time: 12-AUG-2010 17:19:26.79 linker identification: "A13-04" Overall Image Checksum: 3781906529 o [SYSLIB]CLUE$SDA.EXE (new image) Image Identification Information image name: "CLUE$SDA" image file identification: "X-69" image file build identification: "XCB1-0100000002" link date/time: 20-AUG-2010 21:42:30.55 linker identification: "A13-04" Overall Image Checksum: 2590862970 o [SYSEXE]COPY.EXE (new image) Image Identification Information image name: "COPY" image file identification: "A01-10" image file build identification: "XCB1-0100000002" link date/time: 20-AUG-2010 21:42:14.21 linker identification: "A13-04" Overall Image Checksum: 392042001 o [SYSEXE]DBGHK$HOST_KERNEL.EXE (new image) Image Identification Information image name: "DBGHK$HOST_KERNEL" image file identification: "V8.4-000" image file build identification: "XCAV-0100000002" link date/time: 12-AUG-2010 17:20:51.21 linker identification: "A13-04" Overall Image Checksum: 110068107 o [SYSEXE]DBGHK$PRCDUMP_KERNEL.EXE (new image) Image Identification Information image name: "DBGHK$PRCDUMP_KERNEL" image file identification: "V8.4-000" image file build identification: "XCAV-0100000002" link date/time: 12-AUG-2010 17:20:56.01 linker identification: "A13-04" Overall Image Checksum: 909569334 o [SYSEXE]DBGHK$SYSDUMP_KERNEL.EXE (new image) Image Identification Information image name: "DBGHK$SYSDUMP_KERNEL" image file identification: "V8.4-000" image file build identification: "XCAV-0100000002" link date/time: 12-AUG-2010 17:20:53.98 linker identification: "A13-04" Overall Image Checksum: 873575257 o [SYSLIB]DCE$LIB_SHR.EXE (new image) Image Identification Information image name: "DCE$LIB_SHR" image file identification: "DCE V3.2-100310" image file build identification: "0100000002" link date/time: 10-MAR-2010 23:25:13.67 linker identification: "A11-50" Overall Image Checksum: 371914871 o [SYSEXE]DCL.EXE (new image) Image Identification Information image name: "DCL" image file identification: "X-54" image file build identification: "XCBS-0100000003" link date/time: 4-NOV-2010 16:25:50.31 linker identification: "A13-04" Overall Image Checksum: 1032540179 o [SYSLIB]DEBUG.EXE (new image) Image Identification Information image name: "DEBUG" image file identification: "V8.4-000" image file build identification: "XCAV-0100000002" link date/time: 12-AUG-2010 17:19:25.56 linker identification: "A13-04" Overall Image Checksum: 3856736407 o [SYSLIB]DEBUGSHR.EXE (new image) Image Identification Information image name: "DEBUGSHR" image file identification: "V8.4-000" image file build identification: "XCBN-0100000003" link date/time: 21-OCT-2010 10:07:40.06 linker identification: "A13-04" Overall Image Checksum: 2699630038 o [SYS$LDR]FLT$DEBUG.EXE (new image) Image Identification Information image name: "FLT$DEBUG" image file identification: "X-5" image file build identification: "XCBN-0100000003" link date/time: 21-OCT-2010 10:07:28.40 linker identification: "A13-04" Overall Image Checksum: 2043710971 o [SYSLIB]FLT$SDA.EXE (new image) Image Identification Information image name: "FLT$SDA" image file identification: "X-8" image file build identification: "XCBN-0100000003" link date/time: 21-OCT-2010 10:07:34.97 linker identification: "A13-04" Overall Image Checksum: 3957470943 o [SYSEXE]DEBUG_APB.EXE (new image) Image Identification Information image name: "DEBUG_APB" image file identification: "X-8" image file build identification: "XCBS-0100000003" link date/time: 4-NOV-2010 16:26:09.52 linker identification: "A13-04" Overall Image Checksum: 1106621595 o [SYSLIB]DEC$BASRTL.EXE (new image) Image Identification Information image name: "DEC$BASRTL" image file identification: "V01-036" image file build identification: "XCBN-0100000003" link date/time: 21-OCT-2010 10:05:30.46 linker identification: "A13-04" Overall Image Checksum: 1876297888 o [SYSLIB]DEC$FORRTL.EXE (new image) Image Identification Information image name: "DEC$FORRTL" image file identification: "V01-07.004" image file build identification: "XCAV-0100000002" link date/time: 12-AUG-2010 17:18:41.90 linker identification: "A13-04" Overall Image Checksum: 3321776091 o [SYSLIB]DECC$SHR.EXE (new image) Image Identification Information image name: "DECC$SHR" image file identification: "V8.4-00" image file build identification: "XCC2-0100000003" link date/time: 5-DEC-2010 16:38:37.71 linker identification: "A13-04" Overall Image Checksum: 410862002 o [SYSLIB]PE$SDA.EXE (new image) Image Identification Information image name: "PE$SDA" image file identification: "X-23" image file build identification: "XCBS-0100000003" link date/time: 4-NOV-2010 16:26:27.27 linker identification: "A13-04" Overall Image Checksum: 1504662251 o [SYSLIB]PTHREAD$DBGSHR.EXE (new image) Image Identification Information image name: "PTHREAD$DBGSHR" image file identification: "V3.22-094" image file build identification: "XCBS-0100000003" link date/time: 4-NOV-2010 16:23:24.13 linker identification: "A13-04" Overall Image Checksum: 1859838283 o [SYSLIB]DECC$SHRP.EXE (new image) Image Identification Information image name: "DECC$SHRP" image file identification: "V8.4-00" image file build identification: "XCAV-0100000002" link date/time: 12-AUG-2010 17:18:01.73 linker identification: "A13-04" Overall Image Checksum: 2248854783 o [SYSLIB]DECC$SHR_EV56.EXE (new image) Image Identification Information image name: "DECC$SHR_EV56" image file identification: "V8.4-00" image file build identification: "XCC2-0100000003" link date/time: 5-DEC-2010 16:38:51.99 linker identification: "A13-04" Overall Image Checksum: 1789943599 o [SYSEXE]DIRECTORY.EXE (new image) Image Identification Information image name: "DIRECTORY" image file identification: "A10-02" image file build identification: "XCAV-0100000002" link date/time: 12-AUG-2010 17:19:19.49 linker identification: "A13-04" Overall Image Checksum: 2164620518 o [SYSLIB]EDTSHR.EXE (new image) Image Identification Information image name: "EDTSHR" image file identification: "1-050" image file build identification: "XCB1-0100000002" link date/time: 20-AUG-2010 21:41:31.49 linker identification: "A13-04" Overall Image Checksum: 2097770807 o [SYSEXE]ERRFMT.EXE (new image) Image Identification Information image name: "ERRFMT" image file identification: "X-22" image file build identification: "XCB1-0100000002" link date/time: 20-AUG-2010 21:42:25.46 linker identification: "A13-04" Overall Image Checksum: 1431279388 o [SYS$LDR]EXCEPTION.EXE (new image) Image Identification Information image name: "EXCEPTION" image file identification: "X-5" image file build identification: "XCB5-0100000002" link date/time: 3-SEP-2010 12:17:00.50 linker identification: "A13-04" Overall Image Checksum: 2366108338 o [SYS$LDR]EXCEPTION_MON.EXE (new image) Image Identification Information image name: "EXCEPTION_MON" image file identification: "X-5" image file build identification: "XCB5-0100000002" link date/time: 3-SEP-2010 12:17:02.78 linker identification: "A13-04" Overall Image Checksum: 3955912341 o [SYS$LDR]EXEC_INIT.EXE (new image) Image Identification Information image name: "EXEC_INIT" image file identification: "X-217" image file build identification: "XCB5-0100000002" link date/time: 3-SEP-2010 12:17:06.30 linker identification: "A13-04" Overall Image Checksum: 1805033882 o [SYS$LDR]F11BXQP.EXE (new image) Image Identification Information image name: "F11BXQP" image file identification: "XQP V84R_10 CB5" image file build identification: "XCB5-0100000002" link date/time: 3-SEP-2010 12:17:14.77 linker identification: "A13-04" Overall Image Checksum: 2732703855 o [SYSEXE]F11CACP.EXE (new image) Image Identification Information image name: "F11CACP" image file identification: "X-13" image file build identification: "XCAV-0100000002" link date/time: 12-AUG-2010 17:19:20.78 linker identification: "A13-04" Overall Image Checksum: 2191974481 o [SYSEXE]F11DACP.EXE (new image) Image Identification Information image name: "F11DACP" image file identification: "X-13" image file build identification: "XCAV-0100000002" link date/time: 12-AUG-2010 17:19:23.99 linker identification: "A13-04" Overall Image Checksum: 605696227 o [SYS$LDR]IMAGE_MANAGEMENT.EXE (new image) Image Identification Information image name: "IMAGE_MANAGEMENT" image file identification: "X-5" image file build identification: "XCB5-0100000002" link date/time: 3-SEP-2010 12:17:08.97 linker identification: "A13-04" Overall Image Checksum: 1938994611 o [SYSLIB]IMGDMP.EXE (new image) Image Identification Information image name: "IMGDMP" image file identification: "X-71" image file build identification: "XCAV-0100000002" link date/time: 12-AUG-2010 17:19:13.52 linker identification: "A13-04" Overall Image Checksum: 1564542292 o [SYSEXE]INDICTMENT_SERVER.EXE (new image) Image Identification Information image name: "INDICTMENT_SERVER" image file identification: "X-9" image file build identification: "XCB1-0100000002" link date/time: 20-AUG-2010 21:42:32.67 linker identification: "A13-04" Overall Image Checksum: 2897706956 o [SYSEXE]INSTALL.EXE (new image) Image Identification Information image name: "INSTALL" image file identification: "X-34" image file build identification: "XCB1-0100000002" link date/time: 20-AUG-2010 21:42:28.06 linker identification: "A13-04" Overall Image Checksum: 4154725847 o [SYSLIB]IOGEN$FIBRE_CONFIG.EXE (new image) Image Identification Information image name: "IOGEN$FIBRE_CONFIG" image file identification: "X-39" image file build identification: "XCB9-0100000002" link date/time: 15-SEP-2010 15:19:55.36 linker identification: "A13-04" Overall Image Checksum: 2349266099 o [SYSLIB]IOGEN$ISA_CONFIG.EXE (new image) Image Identification Information image name: "IOGEN$ISA_CONFIG" image file identification: "X-21" image file build identification: "XCAJ-0100000000" link date/time: 20-JUL-2010 17:55:00.69 linker identification: "A13-04" Overall Image Checksum: 3463612006 o [SYSLIB]IOGEN$SCSI_CONFIG.EXE (new image) Image Identification Information image name: "IOGEN$SCSI_CONFIG" image file identification: "X-14" image file build identification: "XCAV-0100000002" link date/time: 12-AUG-2010 17:18:27.58 linker identification: "A13-04" Overall Image Checksum: 4103955023 o [SYS$LDR]IO_ROUTINES.EXE (new image) Image Identification Information image name: "IO_ROUTINES" image file identification: "X-5" image file build identification: "XCB5-0100000002" link date/time: 3-SEP-2010 12:17:17.24 linker identification: "A13-04" Overall Image Checksum: 1796246509 o [SYS$LDR]IO_ROUTINES_MON.EXE (new image) Image Identification Information image name: "IO_ROUTINES_MON" image file identification: "X-5" image file build identification: "XCB5-0100000002" link date/time: 3-SEP-2010 12:17:20.69 linker identification: "A13-04" Overall Image Checksum: 2499921824 o [SYSEXE]LANCP.EXE (new image) Image Identification Information image name: "LANCP" image file identification: "X-92" image file build identification: "XCBH-0100000003" link date/time: 1-OCT-2010 15:57:24.51 linker identification: "A13-04" Overall Image Checksum: 1452987136 o [SYSLIB]LBRSHR.EXE (new image) Image Identification Information image name: "LBRSHR" image file identification: "A09-31" image file build identification: "XCB1-0100000002" link date/time: 20-AUG-2010 21:41:19.96 linker identification: "A13-04" Overall Image Checksum: 3327249269 o [SYSLIB]LCK$SDA.EXE (new image) Image Identification Information image name: "LCK$SDA" image file identification: "X-28" image file build identification: "XCAV-0100000002" link date/time: 12-AUG-2010 17:19:37.31 linker identification: "A13-04" Overall Image Checksum: 521585203 o [SYSLIB]LIBRTL.EXE (new image) Image Identification Information image name: "LIBRTL" image file identification: "X01-001" image file build identification: "XCB5-0100000002" link date/time: 3-SEP-2010 12:15:38.09 linker identification: "A13-04" Overall Image Checksum: 2113900129 o [SYSLIB]LIBRTL_INSTRUMENTED.EXE (new image) Image Identification Information image name: "LIBRTL_INSTRUMENTED" image file identification: "X01-001" image file build identification: "XCB5-0100000002" link date/time: 3-SEP-2010 12:17:17.20 linker identification: "A13-04" Overall Image Checksum: 2385463033 o [SYS$LDR]LOCKING.EXE (new image) Image Identification Information image name: "LOCKING" image file identification: "X-5" image file build identification: "XCB5-0100000002" link date/time: 3-SEP-2010 12:17:23.62 linker identification: "A13-04" Overall Image Checksum: 3596746574 o [SYS$LDR]LOGICAL_NAMES.EXE (new image) Image Identification Information image name: "LOGICAL_NAMES" image file identification: "X-5" image file build identification: "XCB5-0100000002" link date/time: 3-SEP-2010 12:17:26.69 linker identification: "A13-04" Overall Image Checksum: 802664343 o [SYSEXE]MACRO.EXE (new image) Image Identification Information image name: "MACRO" image file identification: "50-120-5-48F8P" image file build identification: "XCBJ-0100000003" link date/time: 11-OCT-2010 14:43:50.84 linker identification: "A13-04" Overall Image Checksum: 3542312022 o [SYSEXE]MSA$UTIL.EXE (new image) Image Identification Information image name: "MSA$UTIL" image file identification: "X-28" image file build identification: "XCBN-0100000003" link date/time: 21-OCT-2010 10:09:39.31 linker identification: "A13-04" Overall Image Checksum: 1224771675 o [SYS$LDR]MSCP.EXE (new image) Image Identification Information image name: "MSCP" image file identification: "X-5" image file build identification: "XCB5-0100000002" link date/time: 3-SEP-2010 12:17:24.26 linker identification: "A13-04" Overall Image Checksum: 716146991 o [SYSLIB]PKM$SDA.EXE (new image) Image Identification Information image name: "PKM$SDA" image file identification: "X-29" image file build identification: "XCAJ-0100000001" link date/time: 20-JUL-2010 17:56:36.91 linker identification: "A13-04" Overall Image Checksum: 1741041729 o [SYS$LDR]PROCESS_MANAGEMENT.EXE (new image) Image Identification Information image name: "PROCESS_MANAGEMENT" image file identification: "X-5" image file build identification: "XCC2-0100000003" link date/time: 5-DEC-2010 16:44:39.77 linker identification: "A13-04" Overall Image Checksum: 155401199 o [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE (new image) Image Identification Information image name: "PROCESS_MANAGEMENT_MON" image file identification: "X-5" image file build identification: "XCC2-0100000003" link date/time: 5-DEC-2010 16:44:47.73 linker identification: "A13-04" Overall Image Checksum: 3798839628 o [SYS$LDR]RMS.EXE (new image) Image Identification Information image name: "RMS" image file identification: "X-51" image file build identification: "XCC2-0100000003" link date/time: 5-DEC-2010 16:42:53.19 linker identification: "A13-04" Overall Image Checksum: 2571334982 o [SYSLIB]SDA$SHARE.EXE (new image) Image Identification Information image name: "SDA$SHARE" image file identification: "X-2" image file build identification: "XCBN-0100000003" link date/time: 21-OCT-2010 10:07:22.66 linker identification: "A13-04" Overall Image Checksum: 3108765768 o [SYS$LDR]SECURITY.EXE (new image) Image Identification Information image name: "SECURITY" image file identification: "X-5" image file build identification: "XCB5-0100000002" link date/time: 3-SEP-2010 12:16:59.26 linker identification: "A13-04" Overall Image Checksum: 1686461950 o [SYS$LDR]SECURITY_MON.EXE (new image) Image Identification Information image name: "SECURITY_MON" image file identification: "X-5" image file build identification: "XCB5-0100000002" link date/time: 3-SEP-2010 12:17:01.26 linker identification: "A13-04" Overall Image Checksum: 1640832507 o [SYSEXE]SET.EXE (new image) Image Identification Information image name: "SET" image file identification: "X01-13" image file build identification: "XCAV-0100000002" link date/time: 12-AUG-2010 17:20:59.30 linker identification: "A13-04" Overall Image Checksum: 1302304967 o [SYSEXE]SETSHOSHADOW.EXE (new image) Image Identification Information image name: "SETSHOSHADOW" image file identification: "X-02" image file build identification: "XCAV-0100000002" link date/time: 12-AUG-2010 17:19:33.43 linker identification: "A13-04" Overall Image Checksum: 2596836008 o [SYSEXE]SHADOW_SERVER.EXE (new image) Image Identification Information image name: "SHADOW_SERVER" image file identification: "X-28" image file build identification: "XCBN-0100000003" link date/time: 21-OCT-2010 10:07:08.44 linker identification: "A13-04" Overall Image Checksum: 1990159889 o [SYS$LDR]SHELL16K.EXE (new image) Image Identification Information image name: "SHELL16K" image file identification: "X-5" image file build identification: "XCB5-0100000001" link date/time: 3-SEP-2010 12:17:10.68 linker identification: "A13-04" Overall Image Checksum: 1609726599 o [SYS$LDR]SHELL32K.EXE (new image) Image Identification Information image name: "SHELL32K" image file identification: "X-5" image file build identification: "XCB5-0100000001" link date/time: 3-SEP-2010 12:17:13.11 linker identification: "A13-04" Overall Image Checksum: 2215740186 o [SYS$LDR]SHELL64K.EXE (new image) Image Identification Information image name: "SHELL64K" image file identification: "X-5" image file build identification: "XCB5-0100000001" link date/time: 3-SEP-2010 12:17:15.19 linker identification: "A13-04" Overall Image Checksum: 2530902772 o [SYS$LDR]SHELL8K.EXE (new image) Image Identification Information image name: "SHELL8K" image file identification: "X-5" image file build identification: "XCB5-0100000001" link date/time: 3-SEP-2010 12:17:07.98 linker identification: "A13-04" Overall Image Checksum: 1609658050 o [SYSEXE]SHOW.EXE (new image) Image Identification Information image name: "SHOW" image file identification: "X-16" image file build identification: "XCBJ-0100000003" link date/time: 11-OCT-2010 14:45:14.10 linker identification: "A13-04" Overall Image Checksum: 1321820687 o [SYSEXE]SHWCLSTR.EXE (new image) Image Identification Information image name: "SHWCLSTR" image file identification: "X-27" image file build identification: "XCAV-0100000002" link date/time: 12-AUG-2010 17:20:51.71 linker identification: "A13-04" Overall Image Checksum: 3691447028 o [SYSLIB]SMGSHR.EXE (new image) Image Identification Information image name: "SMGSHR" image file identification: "SMG$ X1.0-001" image file build identification: "XCAV-0100000002" link date/time: 12-AUG-2010 17:17:56.45 linker identification: "A13-04" Overall Image Checksum: 2443299505 o [SYSEXE]SMPUTIL.EXE (new image) Image Identification Information image name: "SMPUTIL" image file identification: "X-30" image file build identification: "XCAJ-0100000000" link date/time: 20-JUL-2010 17:55:56.68 linker identification: "A13-04" Overall Image Checksum: 826998097 o [SYSEXE]SORTMERGE.EXE (new image) Image Identification Information image name: "SORTMERGE" image file identification: "V08-013" image file build identification: "XCAV-0100000002" link date/time: 12-AUG-2010 17:19:22.61 linker identification: "A13-04" Overall Image Checksum: 1739502933 o [SYSLIB]SORTSHR.EXE (new image) Image Identification Information image name: "SORTSHR" image file identification: "V08-013" image file build identification: "XCAV-0100000002" link date/time: 12-AUG-2010 17:18:19.15 linker identification: "A13-04" Overall Image Checksum: 3334401897 o [SYS$LDR]SYS$BASE_IMAGE.EXE (new image) Image Identification Information image name: "SYS$BASE_IMAGE" image file identification: "ALPHA XCB9-J2I" image file build identification: "XCBN-0100000003" link date/time: 21-OCT-2010 10:01:55.53 linker identification: "A13-04" Overall Image Checksum: 1219189599 o [SYS$LDR]SYS$CLUSTER.EXE (new image) Image Identification Information image name: "SYS$CLUSTER" image file identification: "X-5" image file build identification: "XCB5-0100000002" link date/time: 3-SEP-2010 12:17:27.03 linker identification: "A13-04" Overall Image Checksum: 677450865 o [SYS$LDR]NET$CSMACD.EXE (new image) Image Identification Information image name: "CSMACD - NETWORK MANAGEMENT" image file identification: "X-17" image file build identification: "XCBJ-0100000003" link date/time: 11-OCT-2010 14:44:00.44 linker identification: "A13-04" Overall Image Checksum:685346428 o [SYS$LDR]SYS$CLUSTER_MON.EXE (new image) Image Identification Information image name: "SYS$CLUSTER_MON" image file identification: "X-5" image file build identification: "XCB5-0100000002" link date/time: 3-SEP-2010 12:17:30.38 linker identification: "A13-04" Overall Image Checksum: 1918586812 o [SYS$LDR]SYS$DKDRIVER.EXE (new image) Image Identification Information image name: "SYS$DKDRIVER" image file identification: "X-9" image file build identification: "XCB5-0100000002" link date/time: 3-SEP-2010 12:17:15.63 linker identification: "A13-04" Overall Image Checksum: 208541283 o [SYS$LDR]SYS$DNDRIVER.EXE (new image) Image Identification Information image name: "SYS$DNDRIVER" image file identification: "X-41" image file build identification: "XCB5-0100000002" link date/time: 3-SEP-2010 12:17:40.87 linker identification: "A13-04" Overall Image Checksum: 1519077608 o [SYS$LDR]SYS$DZCDRIVER.EXE (new image) Image Identification Information image name: "SYS$DZCDRIVER" image file identification: "X-7" image file build identification: "XCB5-0100000002" link date/time: 3-SEP-2010 12:17:43.17 linker identification: "A13-04" Overall Image Checksum: 1094281188 o [SYS$LDR]SYS$GHDRIVER.EXE (new image) Image Identification Information image name: "SYS$GHDRIVER" image file identification: "DW V8.4-100720" image file build identification: "0100000000" link date/time: 20-JUL-2010 18:13:56.84 linker identification: "A13-04" Overall Image Checksum: 4022599038 o [SYS$LDR]SYS$IPC_SERVICES.EXE (new image) Image Identification Information image name: "SYS$IPC_SERVICES" image file identification: "V1.3-X03E-XCB5" image file build identification: "XCB5-0100000002" link date/time: 3-SEP-2010 12:17:24.52 linker identification: "A13-04" Overall Image Checksum: 1634353172 o [SYS$LDR]SYS$LASTDRIVER.EXE (new image) Image Identification Information image name: "SYS$LASTDRIVER" image file identification: "X-5" image file build identification: "XCB5-0100000001" link date/time: 3-SEP-2010 12:17:26.96 linker identification: "A13-04" Overall Image Checksum: 3819113016 o [SYS$LDR]SYS$PEDRIVER.EXE (new image) Image Identification Information image name: "SYS$PEDRIVER" image file identification: "X-6" image file build identification: "XCBS-0100000003" link date/time: 4-NOV-2010 16:26:34.83 linker identification: "A13-04" Overall Image Checksum: 478088569 o [SYS$LDR]SYS$PEDRIVER_MON.EXE (new image) Image Identification Information image name: "SYS$PEDRIVER_MON" image file identification: "X-6" image file build identification: "XCBS-0100000003" link date/time: 4-NOV-2010 16:26:42.77 linker identification: "A13-04" Overall Image Checksum: 1461096988 o [SYSEXE]SEARCH.EXE (new image) Image Identification Information image name: "SEARCH" image file identification: "X02-08" image file build identification: "XCBN-0100000003" link date/time: 21-OCT-2010 10:07:27.65 linker identification: "A13-04" Overall Image Checksum: 3106643945 o [SYS$LDR]SYS$EHCIDRIVER.EXE (new image) Image Identification Information image name: "SYS$EHCIDRIVER" image file identification: "X-28" image file build identification: "XCBN-0100000003" link date/time: 21-OCT-2010 10:07:48.92 linker identification: "A13-04" Overall Image Checksum: 2152367943 o [SYS$LDR]SYS$OHCIDRIVER.EXE (new image) Image Identification Information image name: "SYS$OHCIDRIVER" image file identification: "X-20" image file build identification: "XCBN-0100000003" link date/time: 21-OCT-2010 10:07:44.69 linker identification: "A13-04" Overall Image Checksum: 1875954831 o [SYS$LDR]SYS$UHCIDRIVER.EXE (new image) Image Identification Information image name: "SYS$UHCIDRIVER" image file identification: "X-8" image file build identification: "XCBN-0100000003" link date/time: 21-OCT-2010 10:07:53.69 linker identification: "A13-04" Overall Image Checksum: 1961001296 o [SYS$LDR]SYS$PKMDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKMDRIVER" image file identification: "X-118" image file build identification: "XCB5-0100000001" link date/time: 3-SEP-2010 12:17:40.36 linker identification: "A13-04" Overall Image Checksum: 3396507273 o [SYS$LDR]SYS$PKRDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKRDRIVER" image file identification: "X-65" image file build identification: "XCB5-0100000000" link date/time: 3-SEP-2010 12:17:37.25 linker identification: "A13-04" Overall Image Checksum: 3565748034 o [SYS$LDR]SYS$PKWDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKWDRIVER" image file identification: "X-45" image file build identification: "XCB9-0100000002" link date/time: 15-SEP-2010 15:21:09.77 linker identification: "A13-04" Overall Image Checksum: 3622071972 o [SYSLIB]SYS$SETBOOTSHR.EXE (new image) Image Identification Information image name: "SYS$SETBOOTSHR" image file identification: "SB V6.0-1" image file build identification: "XCAV-0100000002" link date/time: 12-AUG-2010 17:18:27.45 linker identification: "A13-04" Overall Image Checksum: 3604781320 o [SYS$LDR]SYS$SHDRIVER.EXE (new image) Image Identification Information image name: "SYS$SHDRIVER" image file identification: "X-5" image file build identification: "XCBN-0100000003" link date/time: 21-OCT-2010 10:07:27.07 linker identification: "A13-04" Overall Image Checksum: 653214514 o [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE (new image) Image Identification Information image name: "SYS$TRANSACTION_SERVICES" image file identification: "V2.1-X035-XCBF" image file build identification: "XCBF-0100000002" link date/time: 30-SEP-2010 10:29:27.21 linker identification: "A13-04" Overall Image Checksum: 1299705589 o [SYS$LDR]SYS$VM.EXE (new image) Image Identification Information image name: "SYS$VM" image file identification: "X-5" image file build identification: "XCBJ-0100000003" link date/time: 11-OCT-2010 14:43:58.52 linker identification: "A13-04" Overall Image Checksum: 3089276074 o [SYS$LDR]SYS$XFCACHE.EXE (new image) Image Identification Information image name: "SYS$XFCACHE" image file identification: "V1.0" image file build identification: "XCBF-0100000002" link date/time: 30-SEP-2010 10:29:28.81 linker identification: "A13-04" Overall Image Checksum: 1133593120 o [SYS$LDR]SYS$XFCACHE_MON.EXE (new image) Image Identification Information image name: "SYS$XFCACHE_MON" image file identification: "V1.0" image file build identification: "XCBF-0100000002" link date/time: 30-SEP-2010 10:29:30.61 linker identification: "A13-04" Overall Image Checksum: 2933823045 o [SYSEXE]SYSBOOT.EXE (new image) Image Identification Information image name: "SYSBOOT" image file identification: "X-154" image file build identification: "XCBS-0100000003" link date/time: 4-NOV-2010 16:25:57.25 linker identification: "A13-04" Overall Image Checksum: 766353956 o [SYSEXE]SYSMAN.EXE (new image) Image Identification Information image name: "SYSMAN" image file identification: "X01-22" image file build identification: "XCBS-0100000003" link date/time: 4-NOV-2010 16:26:06.36 linker identification: "A13-04" Overall Image Checksum: 1121567359 o [SYSEXE]SMISERVER.EXE (new image) Image Identification Information image name: "SMISERVER" image file identification: "X01-15" image file build identification: "XCBS-0100000003" link date/time: 4-NOV-2010 16:26:10.16 linker identification: "A13-04" Overall Image Checksum: 1687683309 o [SYS$LDR]SYS$DADDRIVER.EXE (new image) Image Identification Information image name: "SYS$DADDRIVER" image file identification: "X-5" image file build identification: "XCBS-0100000003" link date/time: 4-NOV-2010 16:26:08.62 linker identification: "A13-04" Overall Image Checksum: 3034307844 o [SYSEXE]SYSGEN.EXE (new image) Image Identification Information image name: "SYSGEN" image file identification: "X-5" image file build identification: "XCBS-0100000003" link date/time: 4-NOV-2010 16:25:49.92 linker identification: "A13-04" Overall Image Checksum: 1344308627 o [SYS$LDR]SYSGETSYI.EXE (new image) Image Identification Information image name: "SYSGETSYI" image file identification: "X-5" image file build identification: "XCB5-0100000001" link date/time: 3-SEP-2010 12:17:28.02 linker identification: "A13-04" Overall Image Checksum: 2044115320 o [SYSEXE]SYSINIT.EXE (new image) Image Identification Information image name: "SYSINIT" image file identification: "X-124" image file build identification: "XCAJ-0100000000" link date/time: 20-JUL-2010 17:55:59.30 linker identification: "A13-04" Overall Image Checksum: 2060004122 o [SYS$LDR]SYSLDR_DYN.EXE (new image) Image Identification Information image name: "SYSLDR_DYN" image file identification: "X-5" image file build identification: "XCB5-0100000002" link date/time: 3-SEP-2010 12:17:32.61 linker identification: "A13-04" Overall Image Checksum: 2131854017 o [SYSMSG]SYSMGTMSG.EXE (new image) Image Identification Information image name: "SYSMGTMSG" image file identification: "X-4" image file build identification: "XCB1-0100000002" link date/time: 20-AUG-2010 21:42:29.25 linker identification: "A13-04" Overall Image Checksum: 1126095940 o [SYS$LDR]SYSTEM_DEBUG.EXE (new image) Image Identification Information image name: "SYSTEM_DEBUG" image file identification: "X-2" image file build identification: "XCB5-0100000002" link date/time: 3-SEP-2010 12:17:11.59 linker identification: "A13-04" Overall Image Checksum: 3605204096 o [SYS$LDR]SYSTEM_PRIMITIVES.EXE (new image) Image Identification Information image name: "SYSTEM_PRIMITIVES" image file identification: "X-5" image file build identification: "XCBZ-0100000003" link date/time: 28-NOV-2010 18:16:59.19 linker identification: "A13-04" Overall Image Checksum: 1794197873 o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE (new image) Image Identification Information image name: "SYSTEM_PRIMITIVES_MIN" image file identification: "X-5" image file build identification: "XCBZ-0100000003" link date/time: 28-NOV-2010 18:17:08.68 linker identification: "A13-04" Overall Image Checksum: 1833468848 o [SYS$LDR]SYSTEM_SYNCHRONIZATION.EXE (new image) Image Identification Information image name: "SYSTEM_SYNCHRONIZATION" image file identification: "X-5" image file build identification: "XCB5-0100000001" link date/time: 3-SEP-2010 12:17:08.82 linker identification: "A13-04" Overall Image Checksum: 4173996484 o [SYS$LDR]SYSTEM_SYNCHRONIZATION_MIN.EXE (new image) Image Identification Information image name: "SYSTEM_SYNCHRONIZATION_MIN" image file identification: "X-5" image file build identification: "XCB5-0100000001" link date/time: 3-SEP-2010 12:17:06.51 linker identification: "A13-04" Overall Image Checksum: 2808588854 o [SYS$LDR]SYSTEM_SYNCHRONIZATION_UNI.EXE (new image) Image Identification Information image name: "SYSTEM_SYNCHRONIZATION_UNI" image file identification: "X-5" image file build identification: "XCB5-0100000001" link date/time: 3-SEP-2010 12:17:10.71 linker identification: "A13-04" Overall Image Checksum: 671639113 o [SYSLIB]VMS$FORMAT_AUDIT_SYSTEM.EXE (new image) Image Identification Information image name: "VMS$FORMAT_AUDIT_SYSTEM" image file identification: "X-19" image file build identification: "XCB1-0100000002" link date/time: 20-AUG-2010 21:42:13.98 linker identification: "A13-04" Overall Image Checksum: 2193586585 o [SYSLIB]VMS$VMS_ACMESHR.EXE (new image) Image Identification Information image name: "VMS$VMS_ACMESHR" image file identification: "01" image file build identification: "0100000002" link date/time: 12-AUG-2010 17:19:30.22 linker identification: "A13-04" Overall Image Checksum: 667466310 o [SYSEXE]VMSHELP.EXE (new image) Image Identification Information image name: "VMSHELP" image file identification: "X-4" image file build identification: "XCAV-0100000002" link date/time: 12-AUG-2010 17:19:17.85 linker identification: "A13-04" Overall Image Checksum: 265710098 o [SYS$LDR]PRF$DEBUG.EXE (new image) Image Identification Information image name: "PRF$DEBUG" image file identification: "X-5" image file build identification: "XCB5-0100000000" link date/time: 3-SEP-2010 12:17:35.60 linker identification: "A13-04" Overall Image Checksum: 149464405 o [SYSLIB]PRF$SDA.EXE (new image) Image Identification Information image name: "PRF$SDA" image file identification: "X-27" image file build identification: "XCAJ-0100000000" link date/time: 20-JUL-2010 17:56:08.90 linker identification: "A13-04" Overall Image Checksum: 3123939281 o [SYS$LDR]SYS$EW57711.EXE (new image) Image Identification Information image name: "SYS$EW57711DRIVER" image file identification: "X-12" image file build identification: "XCBH-0100000003" link date/time: 1-OCT-2010 15:57:30.44 linker identification: "A13-04" Overall Image Checksum: 2771442553 o [SYS$LDR]SYS$EW57711_MON.EXE (new image) Image Identification Information image name: "SYS$EW57711DRIVER_MON" image file identification: "X-12" image file build identification: "XCBH-0100000003" link date/time: 1-OCT-2010 15:57:30.99 linker identification: "A13-04" Overall Image Checksum: 1268676271 o [SYS$LDR]SYS$ER57711.EXE (new image) Image Identification Information image name: "SYS$EW57711DRIVER" image file identification: "X-12" image file build identification: "XCBH-0100000003" link date/time: 1-OCT-2010 15:57:30.44 linker identification: "A13-04" Overall Image Checksum: 2771442553 o [SYS$LDR]SYS$ER57711_MON.EXE (new image) Image Identification Information image name: "SYS$EW57711DRIVER_MON" image file identification: "X-12" image file build identification: "XCBH-0100000003" link date/time: 1-OCT-2010 15:57:30.99 linker identification: "A13-04" Overall Image Checksum: 1268676271 o [SYSLIB]SPL$SDA.EXE (new image) Image Identification Information image name: "SPL$SDA" image file identification: "X-43" image file build identification: "XCAJ-0100000000" link date/time: 20-JUL-2010 17:56:24.58 linker identification: "A13-04" Overall Image Checksum: 4163157597 o [SYS$LDR]LNM$DEBUG.EXE (new image) Image Identification Information image name: "LNM$DEBUG" image file identification: "X-5" image file build identification: "XCB5-0100000002" link date/time: 3-SEP-2010 12:17:35.49 linker identification: "A13-04" Overall Image Checksum: 1140144652 o [SYSLIB]LNM$SDA.EXE (new image) Image Identification Information image name: "LNM$SDA" image file identification: "X-13" image file build identification: "XCAV-0100000002" link date/time: 12-AUG-2010 17:19:39.30 linker identification: "A13-04" Overall Image Checksum: 2949620956 o [SYSLIB]USB$SDA.EXE (new image) Image Identification Information image name: "USB$SDA" image file identification: "X-32" image file build identification: "XCBN-0100000003" link date/time: 21-OCT-2010 10:08:35.50 linker identification: "A13-04" Overall Image Checksum: 560487016 o [SYSEXE]AGEN$FEEDBACK.EXE (new image) Image Identification Information image name: "AGEN$FEEDBACK" image file identification: "X-32" image file build identification: "XCB5-0100000002" link date/time: 3-SEP-2010 12:17:04.98 linker identification: "A13-04" Overall Image Checksum: 3091689329 o [SYS$LDR]SYS$LAN_CSMACD.EXE (new image) Image Identification Information image name: "SYS$LAN_CSMACD" image file identification: "X-9" image file build identification: "XCBD-0100000003" link date/time: 22-SEP-2010 17:17:39.67 linker identification: "A13-04" Overall Image Checksum: 2460221791 o [SYSEXE]ACME_SERVER.EXE (new image) Image Identification Information image name: "ACME_SERVER" image file identification: "X-42" image file build identification: "XCBD-0100000003" link date/time: 22-SEP-2010 17:16:53.65 linker identification: "A13-04" Overall Image Checksum: 3721762803 o [SYSLIB]LDAP$SHR.EXE (new image) Image Identification Information image name: "LDAP$SHR" image file identification: "LDAP V2.0-05000" image file build identification: "XCBD-0100000003" link date/time: 22-SEP-2010 17:16:22.74 linker identification: "A13-04" Overall Image Checksum: 3204503728 o [SYSLIB]LDAPACME$LDAP-STD_ACMESHR.EXE (new image) Image Identification Information image name: "LDAPACME$LDAP-STD_ACMESHR" image file identification: "LDAP-STD V01.05" image file build identification: "0100000003" link date/time: 21-OCT-2010 10:06:49.25 linker identification: "A13-04" Overall Image Checksum: 3083057069 o [SYS$LDR]SYS$EIDRIVER.EXE (new image) Image Identification Information image name: "SYS$EIDRIVER" image file identification: "X-61" image file build identification: "XCBD-0100000003" link date/time: 22-SEP-2010 17:17:37.39 linker identification: "A13-04" Overall Image Checksum: 3012825678 o [SYSEXE]LANACP.EXE (new image) Image Identification Information Image name: "LANACP" image file identification: "X-29" image file build identification: "XCBH-0100000003" linker identification: "Linker I02-37" Link Date/Time: 1-OCT-2010 15:57:24.88 Overall Image Checksum: 3155825851 o [SYS$LDR]SYS$EW5700.EXE (new image) Image Identification Information Image name: "SYS$EW5700DRIVER" image file identification: "X-95" image file build identification: "XCBH-0100000003" linker identification: "Linker I02-37" Link Date/Time: 1-OCT-2010 15:57:26.84 Overall Image Checksum: 2382029740 o [SYS$LDR]SYS$EWXFRAME.EXE (new image) Image Identification Information Image name: "SYS$EWXFRAMEDRIVER" image file identification: "X-35" image file build identification: "XCBH-0100000003" linker identification: "Linker I02-37" Link Date/Time: 1-OCT-2010 15:57:29.70 Overall Image Checksum: 3807533552 o [SYSLIB]LIBOTS.EXE (new image) Image Identification Information Image name: "LIBOTS" image file identification: "LIBOTS V1.5-00" image file build identification: "XCBN-0100000003" linker identification: "A13-04" Link Date/Time: 21-OCT-2010 10:02:17.09 Overall Image Checksum: 149607965 o [SYSEXE]LMF.EXE (new image) Image Identification Information Image name: "LMF" image file identification: "X-26" image file build identification: "XCBJ-0100000003" linker identification: "A13-04" Link Date/Time: 11-OCT-2010 14:43:50.58 Overall Image Checksum: 2525624595 o [SYSLIB]SMI$OBJSHR.EXE (new image) Image Identification Information Image name: "SMI$OBJSHR" image file identification: "X40-A9" image file build identification: "XCBS-0100000003" linker identification: "A13-04" Link Date/Time: 4-NOV-2010 16:26:00.38 Overall Image Checksum: 452069436 o [SYSLIB]SMI$SHR.EXE (new image) Image Identification Information Image name: "SMI$SHR" image file identification: "X01-04" image file build identification: "XCBS-0100000003" linker identification: "A13-04" Link Date/Time: 4-NOV-2010 16:25:54.55 Overall Image Checksum: 3201613706 o [SYS$LDR]SYS$FGEDRIVER.EXE (new image) Image Identification Information Image name: "SYS$FGEDRIVER" image file identification: "X-70A4A51" image file build identification: "XCBZ-0100000003" linker identification: "A13-04" Link Date/Time: 28-NOV-2010 18:17:37.88 Overall Image Checksum: 1983586570 o [SYS$LDR]TR$DEBUG.EXE (new image) Image Identification Information Image name: "TR$DEBUG" image file identification: "X-5" image file build identification: "XCBJ-0100000003" linker identification: "A13-04" Link Date/Time: 11-OCT-2010 14:44:03.92 Overall Image Checksum: 2957709594 o [SYSLIB]TR$SDA.EXE (new image) Image Identification Information Image name: "TR$SDA" image file identification: "X-18" image file build identification: "XCBJ-0100000003" linker identification: "A13-04" Link Date/Time: 11-OCT-2010 14:44:04.22 Overall Image Checksum: 2124325022 o [SYSEXE]MONITOR.EXE (new image) Image Identification Information Image name: "MONITOR" image file identification: "X-26" image file build identification: "XCBN-0100000003" linker identification: "A13-04" Link Date/Time: 21-OCT-2010 10:07:20.97 Overall Image Checksum: 773564010 o [SYSLIB]ICC$SDA.EXE (new image) Image Identification Information Image name: "ICC$SDA" image file identification: "X-2" image file build identification: "0100000003" linker identification: "A13-04" Link Date/Time: 21-OCT-2010 10:06:52.22 Overall Image Checksum: 2585436272 o [SYSLIB]PTHREAD$RTL.EXE (new image) Image Identification Information Image name: "PTHREAD$RTL" image file identification: "V3.22-094" image file build identification: "XCBS-0100000003" linker identification: "A13-04" Link Date/Time: 4-NOV-2010 16:23:20.91 Overall Image Checksum: 406519346 o [SYSEXE]QMAN$QUEUE_MANAGER.EXE (new image) Image Identification Information Image name: "QMAN$QUEUE_MANAGER" image file identification: "X-3" image file build identification: "XCBS-0100000003" linker identification: "A13-04" Link Date/Time: 4-NOV-2010 16:25:37.85 Overall Image Checksum: 1084996441 o [SYS$LDR]SYS$IKUDRIVER.EXE (new image) Image Identification Information Image name: "SYS$IKUDRIVER" image file identification: "DW V8.4-101104" image file build identification: "0100000003" linker identification: "A13-04" Link Date/Time: 4-NOV-2010 17:16:13.42 Overall Image Checksum: 4081161880 o [SYS$LDR]SYS$IMUDRIVER.EXE (new image) Image Identification Information Image name: "SYS$IMUDRIVER" image file identification: "DW V8.4-101104" image file build identification: "0100000003" linker identification: "A13-04" Link Date/Time: 4-NOV-2010 17:16:48.33 Overall Image Checksum: 4081161880 o [SYS$LDR]SYS$MKDRIVER.EXE (new image) Image Identification Information Image name: "SYS$MKDRIVER" image file identification: "X-15" image file build identification: "XCBS-0100000003" linker identification: "A13-04" Link Date/Time: 4-NOV-2010 16:26:11.90 Overall Image Checksum: 3106054952 o [SYSEXE]APB_BOOTP.EXE (new image) o [SYSUPD]AUTOGEN.COM (new file) o [SYSLIB]BACKUP.CLD (new file) o [SYSMGR]CLUSTER_CONFIG.COM (new file) o [SYSMGR]CLUSTER_CONFIG_LAN.COM (new file) o [SYS$LDR]COPY.CLD (new file) o [SYS$LDR]EXCEPTION.STB (new file) o [SYS$LDR]EXCEPTION_MON.STB (new file) o [SYS$LDR]EXEC_INIT.STB (new file) o [SYS$LDR]F11BXQP.STB (new file) o [SYS$LDR]IMAGE_MANAGEMENT.STB (new file) o [SYS$LDR]IO_ROUTINES.STB (new file) o [SYSLIB]IO_ROUTINES_MON.STB (new file) o [SYSLIB]LIB.MLB (new file) o [SYSLIB]LIBRTL.STB (new file) o [SYS$LDR]LIBRTL_INSTRUMENTED.STB (new file) o [SYS$LDR]LOCKING.STB (new file) o [SYS$LDR]LOGICAL_NAMES.STB (new file) o [SYS$LDR]PROCESS_MANAGEMENT.STB (new file) o [SYS$LDR]PROCESS_MANAGEMENT_MON.STB (new file) o [SYS$LDR]SECURITY.STB (new file) o [SYS$LDR]SECURITY_MON.STB (new file) o [SYSEXE]SHELL8K.STB (new file) o [SYSLIB]SHUTDOWN.COM (new file) o [SYS$LDR]STARLET.MLB (new file) o [SYS$LDR]SYS$CLUSTER.STB (new file) o [SYS$LDR]SYS$CLUSTER_MON.STB (new file) o [SYS$LDR]SYS$LIB_C.TLB (new file) o [SYS$LDR]SYS$PEDRIVER.STB (new file) o [SYS$LDR]SYS$PEDRIVER_MON.STB (new file) o [SYS$LDR]SYS$SHDRIVER.STB (new file) o [SYS$LDR]SYS$STARLET_C.TLB (new file) o [SYS$LDR]SYS$VM.STB (new file) o [SYS$LDR]SYS$XFCACHE.STB (new file) o [SYS$LDR]SYSGETSYI.STB (new file) o [SYS$LDR]SYSLDR_DYN.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB (new file) o [SYS$LDR]SYSTEM_SYNCHRONIZATION.STB (new file) o [SYS$LDR]SYSTEM_SYNCHRONIZATION_MIN.STB (new file) o [SYS$LDR]SYSTEM_SYNCHRONIZATION_UNI.STB (new file) o [SYS$STARTUP]VMS$CONFIG-050_SHADOW_SERVER.COM (new file) o [SYSEXE]VMS$DEVICE_STARTUP.COM (new file) o [SYSUPD]VMSINSTAL.COM (new file) o [SYSEXE]INS_STARTUP.COM (new file) o [SYS$LDR]SHELL16K.STB (new file) o [SYS$LDR]SHELL32K.STB (new file) o [SYS$LDR]SHELL64K.STB (new file) o [SYS$LDR]SYS$IPC_SERVICES.STB (new file) o [SYSLIB]STARLET.REQ (new file) o [SYSLIB]STARLET.R64 (new file) o [SYSLIB]BASIC$STARLET.TLB (new file) o [SYSLIB]STARLETPAS.TLB (new file) o [SYSLIB]STARLETSD.TLB (new file) o [SYSLIB]LIBRTL.DSF (new file) o [SYSEXE]AXPVMS$PCSI_INSTALL_MIN.COM (new file) o [SYSMSG]VMSINSTAL_LANGUAGE.COM (new file) o [SYSHLP]MSGHLP$LIBRARY.MSGHLP$DATA (new file) o [SYS$LDR]PRF$DEBUG.STB (new file) o [SYS$LDR]SYS$PKRDRIVER.STB (new file) o [SYS$LDR]SYS$LASTDRIVER.STB (new file) o [SYS$LDR]SYS$PKMDRIVER.STB (new file) o [SYS$LDR]LNM$DEBUG.STB (new file) o [SYS$LDR]SYSTEM_DEBUG.STB (new file) o [SYS$LDR]SYS$DNDRIVER.STB (new file) o [SYS$LDR]SYS$DZCDRIVER.STB (new file) o [SYS$LDR]MSCP.STB (new file) o [SYS$LDR]SYS$DKDRIVER.STB (new file) o [SYS$LDR]RMS.STB (new file) o [SYSHLP]UAFHELP.HLB (new file) o [SYS$LDR]SYS$PKWDRIVER.STB (new file) o [SYSLIB]SYS$STARLET_C.TLB (new file) o [SYS$LDR]SYS$LAN_CSMACD.STB (new file) o [SYS$LDR]SYS$EIDRIVER.STB (new file) o [SYSHLP.EXAMPLES]LDAP_EXAMPLE.C (new file) o [SYSHLP]ACMELDAP_STD_CONFIG_INSTALL.PDF (new file) o [SYSHLP]ACMELDAP_STD_CONFIG_INSTALL.TXT (new file) o [SYS$STARTUP]LDAPACME$CONFIG-STD.INI_TEMPLATE (new file) o [SYSHLP.EXAMPLES.ENCRYPT]ENCRYPT_3DES.C (new file) o [SYS$LDR]SYS$EW5700.STB (new file) o [SYSHLP.EXAMPLES.ENCRYPT]ENCRYPT$EXAMPLES.TXT (new file) o [SYS$LDR]SYS$FGEDRIVER.STB (new file) o [SYS$LDR]SYS$PEDRIVER.STB (new file) o [SYS$LDR]TR$DEBUG.STB (new file) o [SYS$LDR]FLT$DEBUG.STB (new file) o [SYS$LDR]SYS$EHCIDRIVER.STB (new file) o [SYS$LDR]SYS$OHCIDRIVER.STB (new file) o [SYS$LDR]SYS$UHCIDRIVER.STB (new file) o [SYSHLP]MAILHELP.HLB (new file) o [SYSHLP]MSA_UTIL_HELP.HLB (new file) o [SYSEXE]SHADOW_SERVER.STB (new file) o [SYSLIB]DECC$RTLDEF.TLB (new file) o [SYS$LDR]SYS$DADDRIVER.STB (new file) o [SYS$LDR]SYS$IKUDRIVER.STB (new file) o [SYS$LDR]SYS$IMUDRIVER.STB (new file) o [SYS$LDR]SYS$MKDRIVER.STB (new file) o [SYS$LDR]SYS$XFCACHE_MON.STB (new file) o [SYSUPD]ANALYZE.hlp (new file) o [SYSUPD]BACKUP.hlp (new file) o [SYSUPD]CRTL.hlp (new file) o [SYSUPD]DCLDICT.hlp (new file) o [SYSUPD]LIBRARY.hlp (new file) o [SYSUPD]SYSTEM.hlp (new file) o [SYSUPD]UTIL_ROUTINES.hlp (new file) o [SYS$LDR]NET$CSMACD.STB (new file) 10 INSTALLATION INSTRUCTIONS 10.1 Test/Debug Image Loss In the course of debugging problems reported to OpenVMS Engineering, customers may be given debug or point-fix images to install. Typically, these images do not have the same image generation flags contained in images released via the OpenVMS remedial patch process. Because of this, any debug or point-fix image that is in the SYS$COMMON area, will be replaced by any image of the same name installed by this kit. If this occurs, you will lose any functionality that is provided by the replaced image. If you wish to retain these debug or point-fix images, you can take the following steps: o Prior to installing this kit, move the test/debug image(s) to be saved to the SYS$SPECIFIC area. o During kit installation, you will be asked if you wish to delete the image(s) in SYS$SPECIFIC. You should answer NO for each image that you want to keep. o After installation completes, but before rebooting the system (if required), move the image(s) from SYS$SPECIFIC back to SYS$COMMON. 10.2 Compressed File This kit is provided as a Self Extracting ZIPEXE kit. To expand this file to the installable .PCSI file, run the file with the following command: $ RUN VMS84A_UPDATE-V0500.ZIPEXE 10.3 Installation Command Install this kit with the POLYCENTER Software installation utility by logging into the SYSTEM account, and typing the following at the DCL prompt: PRODUCT INSTALL VMS84A_UPDATE[/SOURCE=location of Kit] Note that this kit will install with the /SAVE_RECOVERY_DATA option turned on. Using this qualifier will allow easy removal of the kit from the system in the event of problems. If you wish to disable this option you must use the /NOSAVE_RECOVERY_DATA qualifier on the PRODUCT INSTALL command. The /SAVE_RECOVERY_DATA qualifier is optional but highly recommended. Using this qualifier will allow easy removal of the kit from the system in the event of problems. The kit location may be a tape drive, CD, or a disk directory that contains the kit. The /SOURCE qualifier is not needed if the PRODUCT INSTALL command is executed from the same directory as the kit location. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt. 10.4 Scripting of Answers to Installation Questions During installation, this kit will ask and require user response to several questions. If you wish to automate the installation of this kit and avoid having to provide responses to these questions, you must create a DCL command procedure that includes the following logical name definitions and commands: o To avoid the BACKUP question, define the following: $ DEFINE/SYS NO_ASK$BACKUP TRUE o To save replaced files as *.*_OLD define the following logical name as YES. If you do not wish to save replaced files, define the logical name as NO. Note that if you use the /SAVE_RECOVERY_DATA qualifier (recommended) on the PRODUCT INSTALL command all replaced files will be saved as part of that operation. There is no need to also save files as *.*_OLD: $ DEFINE/JOB ARCHIVE_OLD NO o Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=DEC/BASE=AXPVMS/VER=V5.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS84A_UPDATE-V0500 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS84A_UPDATE/PRODUCER=DEC/BASE=AXPVMS/VER=V5.0" $! $ DEASSIGN/SYS NO_ASK$BACKUP $! $ exit $! 11 COPYRIGHT AND DISCLAIMER: (C) Copyright 2011 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP and/or its subsidiaries required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Neither HP nor any of its subsidiaries shall be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for HP products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY THIS PATCH IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE EXTENT PERMITTED BY APPLICABLE LAW. IN NO EVENT WILL HP BE LIABLE FOR ANY LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, WITH RESPECT TO ANY PATCH MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.