SEARCH CONTACT US SUPPORT SERVICES PRODUCTS STORE
United States    
COMPAQ STORE | PRODUCTS | SERVICES | SUPPORT | CONTACT US | SEARCH
gears
compaq support options
support home
software & drivers
ask Compaq
reference library
support forum
frequently asked questions
support tools
warranty information
service centers
contact support
product resources
parts for your system
give us feedback
associated links
.
} what's new
.
} contract access
.
} browse patch tree
.
} search patches
.
} join mailing list
.
} feedback
.
patches by topic
.
} DOS
.
} OpenVMS
.
} Security
.
} Tru64 Unix
.
} Ultrix 32
.
} Windows
.
} Windows NT
.
connection tools
.
} nameserver lookup
.
} traceroute
.
} ping
OpenVMS VMS73_MANAGE-V0100 Alpha V7.3 MANAGE ECO Summary

TITLE: OpenVMS VMS73_MANAGE-V0100 Alpha V7.3 MANAGE ECO Summary Modification Date: 09-APR-2002 Modification Date: Not Applicable Modification Type: NEW KIT NOTE: An OpenVMS saveset or PCSI installation file is stored on the Internet in a self-expanding compressed file. For OpenVMS savesets, the name of the compressed saveset file will be kit_name.a-dcx_vaxexe for OpenVMS VAX or kit_name.a-dcx_axpexe for OpenVMS Alpha. Once the OpenVMS saveset is copied to your system, expand the compressed saveset by typing RUN kitname.dcx_vaxexe or kitname.dcx_alpexe. For PCSI files, once the PCSI file is copied to your system, rename the PCSI file to kitname.pcsi-dcx_axpexe, then it can be expanded by typing RUN kitname.pcsi-dcx_axpexe. The resultant file will be the PCSI installation file which can be used to install the ECO. Copyright (c) Compaq Computer Corporation 2002. All rights reserved. OP/SYS: OpenVMS Alpha V7.3 COMPONENT: MANAGE SOURCE: Compaq Computer Corporation ECO INFORMATION: ECO Kit Name: VMS73_MANAGE-V0100 DEC-AXPVMS-VMS73_MANAGE-V0100--4.PCSI ECO Kits Superseded by This ECO Kit: None ECO Kit Approximate Size: 960 Blocks Kit Applies To: OpenVMS Alpha V7.3 System/Cluster Reboot Necessary: Yes Rolling Re-boot Supported: Yes Installation Rating: INSTALL_3 3 : To be installed by customers experiencing the problems corrected. Kit Dependencies: The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: VMS73_UPDATE-V0100 In order to receive all the corrections listed in this kit, the following remedial kits should also be installed: None ECO KIT SUMMARY: An ECO kit exists for MANAGE on OpenVMS Alpha V7.3. This kit addresses the following problems: PROBLEMS ADDRESSED IN VMS73_MANAGE-V0100 KIT: o Customers have questioned why SYSMAN DO commands, issued from a local node, generate an ALTPRI audit alarm and set a priority of 7. For example: Message from user AUDIT$SERVER on NODE1 Security alarm (SECURITY) on NODE1, system id: 00000 Auditable event: Privilege failure Event information: ALTPRI not used to create process with elevated priority (RUN/PRIORITY, $CREPRC) Event time: 9-JUL-2001 14:49:12.18 PID: 21A00427 Process name: pname Username: uname Process owner: [gname,uname] Terminal name: TNA4: Image name: $40$DKA0:[SYS0.SYSCOMMON.] [SYSEXE]SYSMAN.EXE New priority: 7 Privileges missing: ALTPRI Customers do not understand why there is a request to create the process at priority 7. The subprocess is created at the lower priority and functions properly for a client who does not have the ALTPRI privilege. This change provides the following priority settings: o If the requester has ALTPRI, use current behavior, i.e. create the subprocess at priority 7. o If the requester does not have ALTPRI, create the subprocess at the requester default priority. o If default priority is greater than 7, create the subprocess at priority 7. This maintains the current priority settings on the subprocess creation and eliminates the unnecessary audit alarm. Images Affected: [SYSLIB]SMI$OBJSHR.EXE o SYSMAN commands fail on remote systems with insufficient privilege errors. The cause is that the SMISERVER process running on the node that reported the error does not have CMKRNL privilege. A restart of the SMISERVER fixes the problem. Images Affected: [SYSEXE]SMISERVER.EXE o The USERNAME of the SMISERVER process is not set back to the username of the starting process after a user exits SYSMAN. For example: Starting username: SYSTEM1>sho proc/id=20200218 9-MAR-2001 13:21:12.00 User: SYSTEM Process ID: 20200218 Node: SYSTEM1 Process name:"SMISERVER" SYSTEM1> >>> From another system: SYSTEM2> mc sysman set env/node=SYSTEM1/user=testusr Remote Password: %SYSMAN-I-ENV, current command environment: Individual nodes: SYSTEM1 At least one node is not in local cluster Username TESTUSR will be used on nonlocal nodes SYSMAN> do sho proc %SYSMAN-I-OUTPUT, command execution on node SYSTEM1 9-MAR-2001 13:22:46.81 User: TESTUSR Process ID: 202002E7 Node: SYSTEM1 Process name:"SMI$TESTUSR_1" SYSMAN> >>> SMISERVER process on SYSTEM1 before exiting SYSMAN on SYSTEM2 SYSTEM1>sho proc/id=20200218 9-MAR-2001 13:24:02.82 User: TESTUSR Process ID: 20200218 Node: SYSTEM1 Process name:"SMISERVER" SYSTEM1> >>> SMISERVER process on SYSTEM1 after exiting SYSMAN on SYSTEM2: SYSTEM1>sho proc/id=20200218 9-MAR-2001 13:26:06.02 User: TESTUSR Process ID: 20200218 Node: SYSTEM1 Process name:"SMISERVER" The username should be "SYSTEM". Images Affected: [SYSEXE]SMISERVER.EXE o This kit affects some tape devices (tape drives and robots) which are connected to Fibre Channel via an MDR (Modular Data Router). The affected tape devices have binary WWIDs that contain embedded byte values between 61h and 7Ah. For example, a WWID of 02000008:500E-09E0-0005-3072 (note the last byte value is 72h). These devices are detected during a SYSMAN IO FIND_WWID command, as verified by the WWID value recorded in SYS$SYSTEM:SYS$DEVICES.DAT. However, the devices do not configure if SYSMAN IO AUTOCONFIGURE is invoked immediately after the the SYSMAN IO FIND_WWID command. Only a reboot will result in configuring these devices. The purpose of this kit is to avoid this need for a reboot. Note: Similar issues can arise when using the SYSMAN IO REPLACE_WWID command. Images Affected: [SYSLIB]SMI$OBJSHR.EXE INSTALLATION NOTES: This kit requires a system reboot. Compaq 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. INSTALLATION INSTRUCTIONS: 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 VMS73_MANAGE /SOURCE=[location of Kit] The kit location may be a tape drive, CD, or a disk directory that contains the kit. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt SPECIAL INSTALLATION INSTRUCTIONS: o 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 definitions and commands: - $ DEFINE/SYS NO_ASK$BACKUP TRUE - $ DEFINE/SYS NO_ASK$REBOOT TRUE - Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=DEC/BASE=AXPVMS/VER=V1.0 - De-assign the logicals assigned For example, a sample command file to install the VMS73_MANAGE-V0100 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $! $ PROD INSTALL VMS73_MANAGE/PROD=DEC/BASE=AXPVMS/VER=V1.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit All trademarks are the property of their respective owners.



Files on this server are as follows:

dec-axpvms-vms73_manage-v0100--4.README
dec-axpvms-vms73_manage-v0100--4.CHKSUM
dec-axpvms-vms73_manage-v0100--4.pcsi-dcx_axpexe
vms73_manage-v0100.CVRLET_TXT

privacy and legal statement