Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
VMS73_MANAGE-V0200 Alpha V7.3 MANAGE ECO Summary
Copyright (c) Compaq Computer Corporation 2002. All rights reserved.
New Kit Date: 25-JUN-2002
Modification Date: Not Applicable
Modification Type: Updated Kit Supersedes VMS73_MANAGE-V0100
OP/SYS: OpenVMS Alpha V7.3
COMPONENT: MANAGE
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VMS73_MANAGE-V0200
DEC-AXPVMS-VMS73_MANAGE-V0200--4.PCSI
ECO Kits Superseded by This ECO Kit: VMS73_MANAGE-V0100
ECO Kit Approximate Size: 992 Blocks
Kit Applies To: OpenVMS Alpha V7.3
System/Cluster Reboot Necessary: No
Rolling Re-boot Supported: Information not available
Installation Rating: INSTALL_1
1 : To be installed by all customers.
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-V0200 KIT:
o After issuing a $MC SYSMAN IO SHOW DEVICE command on a system
with many BG devices, the system can crash with a SSRVEXCEPT
bugcheck at SMI$IOGEN_C+00924. The crash occurs because the
reserved buffer is too small (16384 bytes)
Crash Dump Summary
------------------
Bugcheck Type: SSRVEXCEPT, Unexpected system service
exception
Current Process: FIELD
Current Image: $1$DGA3101:[SYS6.SYSCOMMON.]
[SYSEXE]SYSMAN.EXE
Failing PC: 00000000.000DD460 SMI$IOGEN_C+00910
Failing PS: 10000000.00000203
Module: SMI$OBJSHR
Offset: 0003B460
Images Affected: [SYSLIB]SMI$OBJSHR.EXE
o This change generally enhances the handling of Fibre Channel
tape bridges and in particular, allows SCSI tapes to be
configured behind a Network Storage Router.
Images Affected: [SYSLIB]SMI$OBJSHR.EXE
[SYSLIB]IOGEN$FIBRE_CONFIG.EXE
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
RELATED ARTICLES:
Detailed articles describing the problems listed above may exist in
the OPENVMS database(s). To view these articles,
open the appropriate product database and perform a query using either
of the following search strings: 'VMS73_MANAGE-V0200' or
'VMS73_MANAGE'.
ECO KIT ORDERING INSTRUCTIONS:
If after an evaluation you wish to obtain this kit, request it
electronically using the appropriate Advanced Electronic Services
(AES) Service Tool. If you are not familiar with how to request
kits electronically, open the DIA, WIS or DSNLINK database and
review the article entitled:
[AES] How To Electronically Request ECO Kits Using Service Tools
INSTALLATION NOTES:
No reboot is necessary after successful installation of the kit.
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-V0200 /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
- Add the following qualifiers to the PRODUCT INSTALL
command and add that command to the DCL procedure.
/PROD=DEC/BASE=AXPVMS/VER=V2.0
- De-assign the logicals assigned
For example, a sample command file to install the
VMS73_MANAGE-V0200 kit would be:
$
$ DEFINE/SYS NO_ASK$BACKUP TRUE
$!
$ PROD INSTALL VMS73_MANAGE/PROD=DEC/BASE=AXPVMS/VER=V2.0
$!
$ DEASSIGN/SYS NO_ASK$BACKUP
$!
$ exit
All trademarks are the property of their respective owners.
==========================================================================
| Table of Kit Image Information |
+----------------------------+----------+-----------------+--------------+
| | Overall | Image File | Image Link |
| Image Name | Checksum | Identification | Date/Time |
+----------------------------+----------+-----------------+--------------+
| IOGEN$FIBRE_CONFIG.EXE | 208E0738 | X-16A1 | 14-MAY-2002 |
| | | 06:53:40.68 |
+----------------------------+----------+-----------------+--------------+
| SMI$OBJSHR.EXE | 528B0209 | X40-A8 | 14-MAY-2002 |
| | | 07:04:33.78 |
+----------------------------+----------+-----------------+--------------+
| SMISERVER.EXE | 186FE6FE | X01-15 | 14-MAY-2002 |
| | | 07:12:19.03 |
+----------------------------+----------+-----------------+--------------+
|
