OpenVMS VMS721_UPDATE-V0200 Update Alpha V7.2-1 ECO Summary
TITLE: OpenVMS VMS721_UPDATE-V0200 Update Alpha V7.2-1 ECO Summary
New Kit Date : 30-MAY-2001
Modification Date: Not Applicable
Modification Type: Updated Kit Supersedes the following kits
VMS721_ACRTL-V0300 VMS721_BACKUP-V0100
VMS721_CLIUTL-V0100 VMS721_CPU2208-V0200
VMS721_DDTM-V0100 VMS721_DEBUG-V0100
VMS721_DELETE-V0100 VMS721_DQCONFIG-V0200
VMS721_DRIVER-V0200 VMS721_F11X-V0200
VMS721_FIBRE_SCSI-V0400 VMS721_GRAPHICS-V0400
VMS721_IIDRIVER-V0100 VMS721_IPC-V0100
VMS721_LAN-V0200 VMS721_LIBRTL-V0100
VMS721_LOADSS-V0100 VMS721_MANAGE-V0100
VMS721_MIME-V0100 VMS721_MOUNT96-V0200
VMS721_PTHREAD-V0300 VMS721_QMAN-V0100
VMS721_RMS-V0100 VMS721_RPC-V0100
VMS721-RTPAD-V0100 VMS721-SHADOWING-V0500
VMS721_SYS-V0900 VMS721_SYSLOA-V0100
VMS721_UPDATE-V0100
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-dcx_axpexe.pcsi, then it can
be expanded by typing RUN kitname-dcx_axpexe.pcsi. The resultant
file will be the PCSI installation file which can be used to install
the ECO.
Copyright (c) Compaq Computer Corporation 2000, 2001. All rights reserved.
OP/SYS: OpenVMS Alpha V7.2-1
COMPONENT: System
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VMS721_UPDATE-V0200
DEC-AXPVMS-VMS721_UPDATE-V0200--4.PCSI
ECO Kits Superseded by This ECO Kits:
VMS721_ACRTL-V0300 VMS721_BACKUP-V0100
VMS721_CLIUTL-V0100 VMS721_CPU2208-V0200
VMS721_DDTM-V0100 VMS721_DEBUG-V0100
VMS721_DELETE-V0100 VMS721_DQCONFIG-V0200
VMS721_DRIVER-V0200 VMS721_F11X-V0200
VMS721_FIBRE_SCSI-V0400 VMS721_GRAPHICS-V0400
VMS721_IIDRIVER-V0100 VMS721_IPC-V0100
VMS721_LAN-V0200 VMS721_LIBRTL-V0100
VMS721_LOADSS-V0100 VMS721_MANAGE-V0100
VMS721_MIME-V0100 VMS721_MOUNT96-V0200
VMS721_PTHREAD-V0300 VMS721_QMAN-V0100
VMS721_RMS-V0100 VMS721_RPC-V0100
VMS721-RTPAD-V0100 VMS721-SHADOWING-V0500
VMS721_SYS-V0900 VMS721_SYSLOA-V0100
VMS721_UPDATE-V0100
ECO Kit Approximate Size: 173856 Blocks
Kit Applies To: OpenVMS Alpha V7.2-1
System/Cluster Reboot Necessary: Yes
Rolling Re-boot Supported: Yes
Installation Rating: INSTALL_1
1 - To be installed on all systems running
the listed version(s) of OpenVMS.
Kit Dependencies:
The following remedial kit(s) must be installed BEFORE
installation of this kit:
VMS721_PCSI-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 System Components on OpenVMS Alpha V7.2-1. This
kit addresses the following problems:
PROBLEMS ADDRESSED IN VMS721_UPDATE-V0200 KIT
o The VMS721_UPDATE-V0200 kit is a consolidation of Version
7.2-1 ECO kits that have been released since the release of
the VMS721_UPDATE-V0100 kit. The following ECO kits are
included:
VMS721_ACRTL-V0300 VMS721_BACKUP-V0100
VMS721_CLIUTL-V0100 VMS721_CPU22308-V0200
VMS721_DDTM-V0100 VMS721_DEBUG-V0100
VMS721_DELETE-V0100 VMS721_DQCONFIG-V0200
VMS721_DRIVER-V0200 VMS721_F11X-V0200
VMS721_FIBRE_SCSI-V0400 VMS721_GRAPHICS-V0400
VMS721_IIDRIVER-V0100 VMS721_IPC-V0100
VMS721_LAN-V0200 VMS721_LIBRTL-V0100
VMS721_LOADSS-V0100 VMS721_MANAGE-V0100
VMS721_MIME-V0100 VMS721_MOUNT96-V0200
VMS721_PTHREAD-V0300 VMS721_QMAN-V0100
VMS721_RMS-V0100 VMS721_RPC-V0100
VMS721-RTPAD-V0100 VMS721-SHADOWING-V0500
VMS721_SYS-V0900 VMS721_SYSLOA-V0100
VMS721_UPDATE-V0100
Following are the problems addressed by the above kits. Note
that the problems addressed in the VMS721_UPDATE-V0100 kit can
be found in a separate file,
[SYSHLP]VMS721_UPDATE-V0100_CVRLET.TXT.
PROBLEMS ADDRESSED IN KIT VMS721_ACRTL-V0300:
o After installation of previous CRTL ECO kits, user sees:
%LINK-I-DATMISMCH, creation date of in shareable
image SYS$COMMON:[SYSLIB]DECC$SHR.EXE;1
differs from date of in shareable image library
SYS$COMMON:[SYSLIB]IMAGELIB.OLB
Previous ECO kits did not correctly replace DECC$SHR.EXE in
the system IMAGELIB.OLB, which resulted in this message.
This change is Alpha only.
o The linker reported multiple definitions when linking programs
referencing the following symbols.
This was because C$ERRNO was not inserted in STARLET.OLB for
Selective search.
o C$_SIG0
o C$_SIGN
o C$_SIGPIPE
o C$_SIGCHLD
o C$_HOST_NOT_FOUND
o C$_TRY_AGAIN
o C$_NO_RECOVERY
o C$_NO_DATA
o C$_NO_ADDRESS
o C$_NO_TCP
o C$_NOSYSSHR
o C$_EXIT1
o C$_EXIT255
o C$_ILLSYSTDF
o C$_QSORT2BIG
This was a problem with previous CRTL ECO kits.
This change is Alpha only.
o Function mktime()'s algorithm locked thread specific data,
which didn't need to be done. This change uses stack
allocated data, and improves performance.
o Function open() had unnecessary calls to SYS$GETJPI. These
were removed.
o Several problems in function mmap() and munmap() were
addressed.
- Calling function mmap() could result in memory corruption,
when specifying specific addresses in parameter addr.
Under complex conditions the CRTL sometimes allocated
internal memory needed by the CRTL for mmap() related
routines in the address space mapped, which could result
in memory corruption.
This change is Alpha only.
- Function mmap(), with parameter addr set to 0, now returns
the first available chunk of memory from the freelist (if
any). It previously returned a "best fit" chunk from the
freelist.
This change is Alpha only.
- Function munmap() would sometimes fail when releasing
memory allocated with MAP_ANON. This is because it
wrongly tried to deassign a file channel that was not
associated with the memory range.
- Function mmap() was incorrectly specifying global memory
when MAP_ANON is specified.
Change will only do this with flag MAP_SHARED specified.
o Function gettimeofday() now sets errno and vaxc$errno
appropriately if UTC time functions fail because of a system
service failure.
o In UNIX mode, getcwd() returns uppercase for the device.
This problem was introduced in CRTL kits VMS721_ACRTL-V0200
and VMS721H1_ACRTL-V0100.
Case preservation in files names was introduced in
VMS721_ACRTL-V0200. This only applies to files saved or
reported from ODS-5 devices. The case of the logical name or
device name was preserved using this same rule.
Problems Addressed in VMS721_ACRTL-V0200:
o The Compaq C RTL functions which make calls to RMS have been
modified to better support ODS-5 disks. This is an extensive
set of changes throughout the RTL to support case preservation,
long file names, and non-standard file name characters. The
default behavior of the RTL has not changed.
The Compaq C RTL supports case preservation in file names on
ODS level 5 disks. This applies when creating or reporting
file names. By default, this feature is disabled. To enable
this feature define the logical name DECC$EFS_CASE_PRESERVE to
"ENABLE". If file names are all in upper case, define
DECC$EFS_CASE_SPECIAL to "ENABLE" to convert the names into
lower case when reporting the name in UNIX style. If file
names are not all in upper case, then the case is preserved.
Most C RTL functions now accept long OpenVMS-style file names
as arguments. For OpenVMS Alpha Version 7.2, some basic
Compaq C RTL I/O functions (creat, stat, and the functions
from the open family of functions) were enhanced to accept
long OpenVMS-style file names for an ODS-5 device.
In this ECO kit, all other Compaq C RTL functions, except
chdir and the functions from the exec family of functions,
were also enhanced to accept long OpenVMS-style file names for
an ODS-5 device.
All C RTL functions that accept or report full file
specifications will process file specifications up to 4095
bytes long, subject to the rules defined for the media format.
For file specifications in OpenVMS format, there are no
special restrictions. In situations where a full file
specification cannot be reported because the buffer is too
short, the function attempts to report the abbreviated name.
There are restrictions with UNIX file names. Names containing
special characters, such as multiple periods, caret, or
multinational characters, may be rejected. A function call
may report failure if the output buffer is not large enough to
receive the full name. For OpenVMS-style names, the reported
name would contain an FID-abbreviated name. There is no
representation of FID-abbreviated names defined for UNIX.
o The Compaq C RTL was enhanced to allow interpreting the
leading part of a UNIX-style file specification as either a
subdirectory name or a device name.
The translation of the UNIX-style file name "foo/bar" to the
OpenVMS-style file name "foo:bar" was the only translation in
previous versions OpenVMS. It remains the default.
To request translation of the UNIX-style name "foo/bar" to the
OpenVMS-style name "[.foo]bar", DEFINE the following logical
name to any value:
$ DEFINE DECC$DISABLE_TO_VMS_LOGNAME_TRANSLATION ENABLE
To return to the default file-name translation, DEASSIGN the
logical name. The logical name is checked only once per image
activation, not on a file-by-file basis.
o The file creation functions (fopen, open, creat) have been
corrected to not inherit file attributes if a directory by the
same name exists for the file being created. For example,
creating a file named "foo." in a directory which contained a
"foo.dir" would incorrectly inherit file attributes from this
directory file.
o The stat function no longer puts the wrong values into
st_?time members of the stat structure. More precisely,
during daylight savings time the values of st_?time are no
longer one hour ahead from file creation/modification time
reported by the $DIRECTORY command.
o Nonquoted command-line arguments passed to C and C++ programs
(argv arguments) can now optionally have their case preserved,
rather than being lowercased as in previous versions. By
default, this feature is disabled.
To enable this case preservation feature, define the logical
name DECC$ARGV_PARSE_STYLE to "ENABLE" and set the
process-level DCL parse style flag to "EXTENDED" in the
process running the program. Enabling this feature also
ensures that the image name returned in argv[0] is also
case-preserved.
o The time functions time, ftime, gettimeofday and getclock
would fail for a TDF (time differential factor) of -13 hours,
the value required in New Zealand. According to the U.S.
Naval Observatory information the valid range for the TDF is
-13.75 to +13, inclusive. The C RTL now allows this full
range.
o The _malloc64 function was corrected to allow initialization
of this function in a threadsafe manner. Prior to this
change, if the first call occurs after the program has created
multiple threads and more than one thread calls the _malloc64
routine, an access violation may occur.
o In the previous ECO kit, a change was introduced to the
function strptime() for XPG5-compatibility to handle
expressions for the 2-digit year format %y when the century
was not specified. The requirement is for 2-digit years in
the range 0-68 to be treated as 21st century and years in the
range 69-99 as 20th century. The 2-digit years in the range
69-99 were incorrectly being treated as 21st century.
o The execlp and execvp functions were unconditionally prefixing
the file specification of the image to be run in the child
process with "VAXC$PATH:" string. When passed a fully
qualified file specification, this would result in an invalid
file specification.
o The behavior of lseek() and fseek() at positions beyond the
end of data in a file were not conforming to the POSIX/ANSI
standard. The file was being physically null padded on disk
even though the standard only requires this null padding if
data is actually written at this point. In the case reported
by the user, seeking to the end of a file by using a large
offset would take a long time and may exhaust available disk
space. To get the POSIX behavior, you must define
DECC$POSIX_SEEK_STREAM_FILE as "ENABLE". The default behavior
is unchanged.
o The Compaq C RTL was enhanced to open all files for shared
access as if the "shr=del,get,put,upd" option was specified in
the open* or creat call. To enable this feature, define the
logical name DECC$FILE_SHARING to the value "ENABLE". The
value is case-insensitive and is checked only once per image
activation, not on a file-by-file basis.
o The Compaq C RTL was failing when the amount of data written
to a pipe exceeded the buffer size of that pipe. The RTL now
breaks the large write into a sequence of writes whose size is
the size of the underlying mailbox used to implement pipes.
o The opendir function now accepts ".." to be equivalent to both
"../" and "[-]".
o A problem was reported that the RTL could hang if exit were
called while threads were continuing to do I/O. Analysis
showed that the hang was caused by a thread holding the lock
necessary to close the file and the exit handler blocking on
this lock. The change implemented was to not attempt to close
files whose locks were currently in use.
o When a stream file is extended using ftruncate() it is
documented that the extended area will be filled with zeroes.
This is now done correctly. Prior to this change, the file
was not extended.
o The documentation of the select function states that it
returns either when a socket is ready to be read or written,
when the timeout period expires, or when exceptions occur. It
was not properly terminating when an exception occurred. This
problem was corrected by dynamically linking to and calling an
abort function in the socket library. A complete correction
to interrupting the select function will also require an ECO
kit from the Compaq TCP/IP product which includes this new
abort function.
o The fstat function was corrected to not access violate when
called with stdin, stdout, stderr, or a directory specification.
o The chdir function was not well-behaved when the calling
program passed an argument which was a search list logical.
The chdir function was unconditionally changing the logical
sys$disk to the first member of the search list was
effectively dropping the remaining members. The change in
behavior is seen as a step in the right direction, but there
are plans for more work in this area.
o The stat functions were not correctly handling files which
were not directories but did use a .dir extension. This
problem was discovered when porting a UNIX application which
used a .dir extension to store application specific information.
o The RTL functions which process file specifications were not
correctly processing files which contained a hyphen character.
The RTL was incorrectly assuming that hyphens were only
allowed to specify a relative directory path.
Problems Addressed in VMS721_ACRT-V0100:
o The getenv() function has been corrected to check for a CLI
symbol only when called in user access mode. While DEC C RTL
is a user-mode run time library, we decided to correct getenv()
in order to make the library more robust. This is because
calling CLI from within exec or kernel mode may result in an
access violation.
With this fix, when called from inner access mode, the
getenv() function will search only the C environment list and
VMS logical names.
This fix does not mean, however, that the user-mode only
restriction was lifted. It is still unsupported to call the
DEC C RTL functions, including getenv(), in any access mode
other than in user-mode.
o The strptime() function has been modified to comply with
X/Open CAE Specification System Interfaces and Headers Issue 5
(commonly known as XPG5). In XPG5, it was changed how the
strptime() function processes the "%y" directive for a
two-digit year within the century if no century is specified.
According to XPG5, for the "%y" directive when a century is
not otherwise specified, values in the range 69-99 refer to
years in the twentieth century (1969 to 1999 inclusive) while
values in the range 00-68 refer to years in the twenty-first
century (2000 to 2068 inclusive). Essentially, for the "%y"
directive, strptime() became a "pivoting" function with 69
being a pivoting year.
Before this change, the strptime() function was always
interpreting two-digit year with no century as a year within
the twentieth century.
With the current ECO kit, XPG5-compliant strptime() becomes a
default strptime() function in the DEC C RTL. However, for
compatibility reasons, the previous "non-pivoting" XPG4-compliant
strptime() function was retained.
The "pivoting" is controlled by the DECC$XPG4_STRPTIME logical
name. Defining this logical name prior to invoking the
application (any equivalence string) will cause the DEC C RTL
to use the "non-pivoting" flavor of strptime(). Also,
"non-pivoting" strptime() can be called directly as
decc$strptime_xpg4() function.
While there is an easy way to disable "pivoting" by just
defining a logical name, you should be aware that if the
application ceases to work correctly due to the change in the
strptime() function, it almost certainly means, that there is
a Y2K problem in the application. Y2K-safe applications
should not be affected by the change in strptime().
o The stat() function has been corrected to process file
specifications such as "foo:[000000]" where foo is defined as
a concealed device like the following:
$ define/trans=(conc) foo device:[bar.]
Prior to this fix, the stat() function would fail for such a
file specification with errno set to ENOENT (No such file or
directory).
o Both flavors of system() function were corrected to ensure
that the function always returns the correct status.
The POSIX-compliant system() function has been corrected to
always return status corresponding to the signal which
terminated the child process if the child process was
terminated due to receiving a signal.
Prior to this fix, there was a small timing window when the
function could return the status corresponding to the child
process completion code even in the case when the child
process was terminated by a signal.
The Non-POSIX system() function has been corrected to always
return the VMS completion code of the child process.
Prior to this fix, there was a small timing window when the
function could return the status from LIB$SPAWN() instead of
the completion code of the child process.
None of these problems were ever reported by a customer.
o Opendir() and readdir() functions have been corrected to
process directories on a remote node specified using the
following DECnet file specification:
nodename"username password"::device:[directory]
Prior to this fix, opendir() could fail with errno set to
ENOTDIR (Not a directory). In the case when opendir() could
successfully open the directory, readdir() function could
return incorrect file names.
o Times() and clock() functions have been modified to be both
thread-safe and AST-reentrant.
Prior to this change, these functions belonged to the class of
functions which are thread safe, but not AST-reentrant (see
section 1.7.2 Multithread Restrictions in the DEC C RTL
Reference Manual).
The change in the reentrancy status of the times() and clock()
functions will be reflected in the next release of the Manual.
o The stat() function no longer fails due to the failure of the
mktime() function.
It was reported that the stat() function fails for a file
created on April 4th 1999 at 2:04 a.m. EST which is the
"missing hour" in the transition from standard to daylight
saving time in Eastern time zone.
The failure was due to the failure of the mktime() function to
process the "missing hour" (stat() calls mktime() to fill
st_?time members of the stat structure with UTC time).
While the mktime() function was not fixed, the stat() function
was corrected to handle the failure of mktime() and set st_?time
fields correctly even if mktime() fails.
Note, that, strictly speaking, "missing hour" is an invalid
input for mktime(): there is no such time as "April 4th 1999
2:04 a.m.", for example, in Eastern time zone. Given the
possibility of calling mktime() with invalid time, the stat()
function, probably, should not have used mktime() in the first
place or at least should have been prepared for mktime() failure.
o The CRTL I/O subsystem was enhanced to lift eight nested
directory levels restriction for an ODS-5 device. It affects
such DEC C RTL functions as access, mkdir, opendir, rmdir, and
stat.
The following program example shows different VMS and UNIX-style
deep directory specifications.
#include
#include
#include
#include
#include
#include
#define DIM(_s) (sizeof(_s) / sizeof(_s[0]))
/*
** we assume presence of root$ concieled device:
**
** define/NoLog/Tran=(Conceal,Terminal) root$
** node$dka0:[000000.]
**
*/
static char *filename[] = {
"node$dka0:[w.x.y.z.a.b.c.d.e.f.g.h.i.j]", /* (1) */
"node$dka0:[w.x.y.z.a.b.c.d.e.f.g.h.i]j.dir", /* (2) */
"root$/w/x/y/z/a/b/c/d/e/f/g/h/i/j", /* (3) */
};
main()
{
struct stat s;
int i;
char *name;
for(i=0; i < DIM(filename); ++i) {
name = filename[i];
if ( mkdir(name,0) == -1 )
printf("%d? mkdir(): %s\n", i+1, strerror(errno));
if ( stat(name,&s) )
printf("%d? stat(): %s\n", i+1, strerror(errno));
else if ( !S_ISDIR(s.st_mode) )
printf("%d? stat(): %s\n", i+1, "not a directory???");
if ( !opendir(name) )
printf("%d? opendir(): %s\n", i+1, strerror(errno));
if ( access(name,F_OK) == -1 )
printf("%d? access(): %s\n", i+1, strerror(errno));
if ( rmdir(name) == -1 )
printf("%d? rmdir(): %s\n", i+1, strerror(errno));
}
}
Please note, that the DEC C RTL still does not support mixed
UNIX/VMS-style file names coded using extended ODS-5 syntax
like "doc/foo.bar.bar", "~foo^.bar" and "./tmp/foo.bar.b^_ar".
o The select() function has been corrected to return failure
status if either invalid file descriptor or file descriptor
not associated with a socket is found in one of the specified
file descriptor sets. In case of invalid file descriptor, the
select() function sets errno to EBADF. In case of a file
descriptor not associated with a socket, the function sets
errno to ENOTSOCK.
Failure with errno set to EBADF is the standard requirement
for the select() function. Failure with errno set to ENOTSOCK
is because currently the select() function can operate only on
sockets.
Prior to this fix, the function was setting errno as described
above, but otherwise was ignoring invalid file descriptors and
file descriptors not associated with sockets.
The old behavior can be requested by defining the logical name
DECC$SELECT_IGNORES_INVALID_FD prior to invoking the application
(any equivalence string).
o The bug in printf() "engine" introduced in ALPACRT07_071 kit
has been fixed. The bug was that when minimal field width or
precision specified in the format directive was greater than
1024, the "engine" could write beyond the end of allocated
internal conversion buffer. It could happen only in X_FLOAT
floating point mode (/L_DOUBLE_SIZE=128, which is the default
on Alpha). The bug affected all functions from the printf()
family of functions.
o The problem commonly known as the "Y2038 bug" has been fixed.
The C run-time library time functions which access the current
time using the VMS time functions have been corrected to
handle times after 19-Jan-2038 3:14:07. Data type time_t is
defined on VMS as an unsigned 32-bit integer. However, some
of the functions which retrieve current time from the system
and convert it to time_t format were using signed arithmetic.
This fix affects the functions:
o decc$fix_time()
o time()
o ftime()
o gettimeofday()
o getclock()
With this fix, DEC C RTL time functions will handle times
successfully until 07-Feb-2106 06:28:15.
o The printf() family of functions have been enhanced to perform
better when the calling application has exhausted available
memory.
o The file access functions have been corrected to process file
names on UNIX systems over DECnet. The file name for a file
on a UNIX system accessed over DECnet was being converted to
uppercase, even when the name was enclosed in double quotes.
This problem was introduced on OpenVMS V7.2 and also affects
OpenVMS V7.1-2 and OpenVMS V7.2-1. File names of the form
node::"dir/name" are now processed correctly.
PROBLEMS ADDRESSED IN VMS721_BACKUP-V0100 KIT:
o Backup may abort during a /IMAGE operation of an ODS5 disk
with an RMS-F-SYN error.
Images Affected: [SYSEXE]BACKUP.EXE
[SYSLIB]BACKUPSHR.EXE
o BACKUP is looping with a WAITIDLEBCB error after a fatal drive
error. See the partial error message below:
%BACKUP-E-FATALERR, fatal error on _$2$MUA561:[]DISK$REPSET2.BCK;
-SYSTEM-F-DATALOST, data lost
%SLS-E-BACKUPFAIL, backup directive failed
%BACKUP-F-ABORT, operator requested abort on fatal error
%BACKUP-F-WAITIDLEBCB, attempted wait on idle buffer
%BACKUP-F-WAITIDLEBCB, attempted wait on idle buffer
%BACKUP-F-WAITIDLEBCB, attempted wait on idle buffer
%BACKUP-F-WAITIDLEBCB, attempted wait on idle buffer
%BACKUP-F-WAITIDLEBCB, attempted wait on idle buffer
%BACKUP-F-WAITIDLEBCB, attempted wait on idle buffer
%BACKUP-F-WAITIDLEBCB, attempted wait on idle buffer
This may also result in an ACCVIO.
Images Affected: [SYSEXE]BACKUP.EXE
[SYSLIB]BACKUPSHR.EXE
o Process quota values may cause BACKUP to ACCVIO. No quota
related messages are displayed.
Images Affected: [SYSEXE]BACKUP.EXE
[SYSLIB]BACKUPSHR.EXE
o The following %BACKUP-F-PARSE error occurs when BACKUP has an
input-specifier that is somewhat lengthy and includes a
wildcard file specification with an implicit device and
directory.
%BACKUP-F-PARSE, error opening NET*.*;*
-RMS-F-SYN, file specification syntax error
where NET.*.*;* is the wildcard file specification in the
input-specifier.
The above error will occur whenever the following BACKUP
command is issued:
$ BACKUP SYS$SYSTEM:NET*.*;*,SYS$SYSTEM:SYSUAF.DAT,RIGHTSLIST.DAT -
TAPEDRIVE:SAVESET.BCK
It appears that this is a positional problem since if the
wildcard file specification appears at the beginning of the
input-specifier, the problem is avoided. For example, the
following BACKUP command will work successfully:
$ BACKUP SYS$SYSTEM:NET*.*;*,SYS$SYSTEM:SYSUAF.DAT,RIGHTSLIST.DAT -
TAPEDRIVE:SAVESET.BCK
Images Affected: [SYSEXE]BACKUP.EXE
[SYSLIB]BACKUPSHR.EXE
o When the BACKUP utility prompts for a new tape, certain
invalid replies will abort the backup with a LIB-F-INPSTRTRU
error.
For the error to occur, a blank followed by a single letter
must be entered, e.g., " y" or " r". BACKUP then repeats the
prompt. If the user types the full response, i.e., "yes" or
"restart", the following error message displays:
%BACKUP-F-ABORT, operator requested abort on fatal error
-LIB-F-INPSTRTRU, input string truncated
Images Affected: [SYSEXE]BACKUP.EXE
[SYSLIB]BACKUPSHR.EXE
o Backup cannot write journal records large enough to include
longer filenames, which are allowed with ODS5 and the extended
character set. Attempts to use long filenames results in a
'%BACKUP-F-INVBJLSIZ, invalid record size in BACKUP journal'
error.
Images Affected: [SYSEXE]BACKUP.EXE
[SYSLIB]BACKUPSHR.EXE
o A /LIST/FULL operation does not include a 'seconds' output
field for file dates.
Images Affected: [SYSEXE]BACKUP.EXE
[SYSLIB]BACKUPSHR.EXE
o A CREDIRERR error status does not remove files from
post-processing when performing a BACKUP/DELETE operation.
Images Affected: [SYSEXE]BACKUP.EXE
[SYSLIB]BACKUPSHR.EXE
o A %BACKUP-W-NOFILES message may be received when backup is run
from a search list and <...> is used instead of [...] as the
syntax for a directory file specification.
Images Affected: [SYSEXE]BACKUP.EXE
[SYSLIB]BACKUPSHR.EXE
o After upgrading to OpenVMS Alpha 7.2, a BACKUP command
specifying a /LABEL of more than six characters fails with:
%BACKUP-F-INVQUAVAL, value 'ISNAPBL023' invalid for /LABEL
qualifier
Images Affected: [SYSEXE]BACKUP.EXE
[SYSLIB]BACKUPSHR.EXE
o Provide a /NOUNLOAD qualifier fro BACKUP to carry over through
continuation volumes of a tape volume set. Before this fix,
there was no way to specify /NOUNLOAD in BACKUP, so
controlling continuation volumes was not possible.
UNLOAD/NOUNLOAD keywords have been added to the RELEASE_TAPE
qualifier, with UNLOAD as the default. On the command line,
the entry will look like the following:
$BACKUP/RELEASE_TAPE=NOUNLOAD !NOUNLOAD the volume
$BACKUP/RELEASE_TAPE=UNLOAD !UNLOAD the volume
$BACKUP/RELEASE_TAPE !UNLOAD (Default)
Images Affected: [SYSEXE]BACKUP.EXE
[SYSLIB]BACKUPSHR.EXE
o An incremental BACKUP RESTORE causes a BACKUP-E-INCDELERR
error and loops continuously when attempting to perform a
directory tree delete on a specific DIR filespec. The
following text is an example of the message syntax:
%BACKUP-E-INCDELERR, error deleting
$4$DUA1:[WINDATA.NETSCAPE.CACHE]CACHE.DIR;1
-SYSTEM-W-NOSUCHFILE, no such file
Images Affected: [SYSEXE]BACKUP.EXE
[SYSLIB]BACKUPSHR.EXE
o The loss of compaction may occur on a tape device after
upgrading to OpenVMS V7.2-1. This could happen in several
ways. Appending of savesets to a tape volume may lead to loss
of the compaction attribute for tape device or it may not be
correctly enabled at the start of a tape volume. Also, use of
generic SCSI tape devices may not honor the compaction device
attribute after a tape label overwrite or on the initialization
of continuation volumes.
Images Affected: [SYSEXE]BACKUP.EXE
[SYSLIB]BACKUPSHR.EXE
o Files with an 8388698 (4 Gb.) contiguous block size could not
be copied disk to disk correctly using BACKUP. However, a
file maybe saved correctly if sent to a tape saveset,
depending upon the /blocksize value in the command line.
Images Affected: [SYSEXE]BACKUP.EXE
[SYSLIB]BACKUPSHR.EXE
o A RMS-F-SYN error occurs when a UIC (user identification code)
is specified in the BACKUP command line. 'RMS-F-SYN, file
specification syntax error' is reported when the BACKUP
command line is supplied with a UIC format for a directory
filespec. For example: disk:[0,0] rather than disk:[000000].
Images Affected: [SYSEXE]BACKUP.EXE
[SYSLIB]BACKUPSHR.EXE
o Intermittent ACCVIOs occur on a tape volume switch (continuation
volumes). Depending on a number of resource issues (the number
of queued I/Os [QIOs], the number of files open, or sent but
failing QIOs) when a tape volume switch is needed, an ACCVIO may
occur just after the new tape volume is requested.
Images Affected: [SYSEXE]BACKUP.EXE
[SYSLIB]BACKUPSHR.EXE
o Compaction is not enabled, if BACKUP is called with the API.
Running BACKUP interactively or through batch jobs, however,
enables compaction and it functions acceptably with remedia
images.
Images Affected: [SYSEXE]BACKUP.EXE
[SYSLIB]BACKUPSHR.EXE
Problems Addressed In VMS721_CLIUTL-V0100:
o Issuing two different SET DEVICE commands can crash a system
at NSA$SIZE_NSAB. This is due to invalid argument counts in
the two $CMKRNL calls.
Images Affected: [SYSEXE]SET.EXE
o A DCL (Digital command language) $ SHOW CLUSTER command will
hang on startup on cluster-nodes with many SCS ports, e.g.,
CIPCA, CIXCD, MC:... or Pxx0: devices, if the
virtual-circuit (PB$ path-block) count exceeds four times the
SCS-node count. An "SCS-node" is defined as any SCS-speaking
node, such as HSJxx/HSCxx Storage Controllers, RFxx DSSI disk
controllers, or VMS nodes, etc.
Images Affected: [SYSEXE]SHWCLSTR.EXE
o SHOW LOGICAL allocates virtual address space based on pagesize
rather than pagelet size for Alpha only. De-allocation of
used virtual memory was incorrect.
Images Affected: [SYSEXE]SHOW.EXE
o The system STARTUP process will hang in a loop waiting for the
AUDIT_SERVER process to start, if the $SET AUDIT/SERVER=START
command fails.
Images Affected: [SYSEXE]SETAUDIT.EXE
o Add a new /CONTENTION_POLICY qualifier to SET RMS_DEFAULT to
address locking fairness issues.
The new Alpha global buffer read-mode lock support introduced
in V7.2-1H1 is functionally compatible with both VAX and older
Alpha releases. Operations in mixed clusters produce correct
results. However, there is a locking fairness issue that may
arise with mixed cluster operations.
In a mixed cluster environment with very high contention for
specific buckets, it is possible for accesses to write-shared
files on nodes using read-mode bucket locking to dominate
access to a bucket. Nodes without this support might be
unable to access the bucket for a protracted period of time.
It is also possible to observe comparable behavior on all
OpenVMS versions when dealing with accesses to write-shared
files without global buffers enabled -- even on a standalone
system. A similar fairness issue between lock conversions and
new lock requests may be observed in which the new lock
requests may remain ungranted for an extended period of time.
This kit provides an interface for RMS support for a new
option to improve fairness under high contention conditions
for write-shared files. The option is controlled using the
/CONTENTION_POLICY qualifier to the DCL command SET
RMS_DEFAULT. The option may be set at a process or system
level. Since selecting this option may noticeably increase
locking overhead and since many applications will never
encounter this issue, the default system behavior leaves this
option disabled. A future lock management enhancement should
make this fairness workaround unnecessary for later releases.
The following are valid PROCESS keywords (/SYSTEM not
specified) for SET RMS_DEFAULT/CONTENTION_POLICY:
NEVER Never use the higher overhead option
to improve fairness for any write-shared
files accessed by this process; minimal overhead.
SOMETIMES Use this option for fairer bucket
access (but higher overhead) to any
write-shared files with global buffers
enabled that are accessed by this process.
ALWAYS Use this option for fairer bucket
access (but higher overhead) to all
write-shared files accessed by this process.
SYSTEM_DEFAULT (Default) Use system setting. Note
that this keyword is disallowed with
/SYSTEM.
The following are valid SYSTEM keywords (/SYSTEM specified):
NEVER (Default) Never use the higher
overhead option to improve fairness
for any write-shared files accessed
on the system; minimal overhead.
SOMETIMES Use this option for fairer bucket
access (but higher overhead) to any
write-shared files with global
buffers enabled that are accessed
on the system.
ALWAYS Use this option for fairer bucket
access (but higher overhead) to all
write-shared files accessed on the system.
Images Affected: [SYSEXE]SET.EXE
o Add infrastructure needed to support external hook: SET
RMS_DEFAULT/QUERY_LOCK.
Images Affected: [SYSEXE]SET.EXE
[SYSEXE]SHOW.EXE
[SYSMSG]CLIUTLMSG.EXE
o If a user attempts to use the SET FILE command to set global
buffers or statistics on a file that is already accessed by
another user, the following error message is displayed:
%SET-E-READERR, error reading
-SYSTEM-W-ACCONFLICT, file access conflict
This is an issue with 24x7 sites in which users may want to
tune or analyze the performance of live files.
Images Affected: [SYSEXE]SET.EXE
o The SHOW DEVICE command, when used for multipath devices,
displays the host name of the primary path rather than that of
the current path.
Images Affected: [SYSEXE]SHOW.EXE
o The SHOW command can fail with a 'Virtual address space full'
error.
Images Affected: [SYSEXE]SHOW.EXE
PROBLEMS ADDRESSED IN VMS721_CPU2208-V0200 KIT:
o The VMS721_DS20E-V0100 and VMS721_CPU2208-V0100 remedial kits
contained common images. The VMS721_CPU2208-V0200 kit simply
combines these two kits. If you have already installed the
VMS721_DS20E-V0100 and VMS721_CPU2208-V0100 remedial kits
there is no need to install this VMS712_CPU2208-V0200 kit.
PROBLEMS ADDRESSED IN VMS721_CPU2208-V0100 KIT:
o The VMS Correctable Error Throttling Notification (CETN) does
not subscribe to the Regatta PFMS 3.1 specifications as follows:
1. Throttling on to throttling-off cycling does not operate
with automatic 5 minute intervals.
2. Throttling-on threshold is not set at 4 correctable events
within a 2 second timing window.
3. Reboot initialization CETN event status is not provided.
4. CETN event throttle-on (Set) and throttle-off (Clear) bits
are not set to their correct states.
Images Affected: [SYS$LDR]SYS$CPU_ROUTINES_2208.EXE
[SYS$LDR]SYS$CPU_ROUTINES_2508.EXE
o Allow mixed CPU operation in support of field replacements.
This allows field replacement of CPUs without having to
replace all the CPUs in the system.
Images Affected: [SYS$LDR]SYS$CPU_ROUTINES_2208.EXE
o A potential data inconsistency has been identified on some
systems (referenced below) during qualification testing of
an unreleased graphics software kit. This error has only
occurred in a highly stressful technical validation environment.
Compaq does not expect customers to experience this problem, but
in an effort to provide the highest level of customer service, we
recommend that users with the following systems install the
DEC-AXPVMS-VMS721_CPU2208-V0100-4.PCSI (or later) or
DEC-AXPVMS-VMS712_CPU2208-V0100-4.PCSI (or later) remedial kits:
AlphaServers AlphaStations
------------------- --------------------------------------
Compaq AlphaServer Compaq AlphaStation ES40
ES40
Compaq AlphaServer Compaq AlphaStation XP900
DS10
Compaq AlphaServer Compaq AlphaStation XP1000
DS10L
Compaq AlphaServer Compaq AlphaStation 21264 PCI/ISA SBC
DS20
Compaq AlphaServer Compaq AlphaStation DS20E
DS20E
For OpenVMS Version 7.2-1H1, this fix is also included in the
DEC-AXPVMS-VMS721H1_UPDATE-V0300 (or later) remedial kit.
Images Affected: [SYS$LDR]SYS$CPU_ROUTINES_2208.EXE
[SYS$LDR]SYS$CPU_ROUTINES_2508.EXE
NEW FUNCTIONALITY ADDRESSED IN VMS721_DS20E_ES40-V0100 KIT:
o This kit provides OpenVMS Version 7.2-1 support for the Compaq
AlphaServer DS20E. The DS20E is a follow-on to the Compaq
AlphaServer DS20. This kit includes the following OpenVMS support
on the DS20E:
o Server management
o 3X-DEPVD-AA PCI adapter
o IDE CD-ROM and boot and runtime
Image(s) Affected: [SYS$LDR]SYS$CPU_ROUTINES_2208.EXE
[SYS$LDR]SYS$IIDRIVER.EXE
[SYSEXE]SYS$SMHANDLER.EXE
o On Compaq AlphaServer DS20E systems, you cannot use the
following system routines to perform I/O tribyte reads and
writes:
o IOC$READ_PCI_CONFIG
o IOC$WRITE_PCI_CONFIG
o IOC$READ_IO
o IOC$WRITE_IO
If a device driver calls any of these system routines with a
length of three, you must use one of the following methods
instead-depending on your I/O cards characteristics:
For IOC$READ_IO and IOC$READ_PCI_CONFIG:
o Use a longword read, and mask out the byte.
o Do a combination of word and byte reads, and append the
data.
For IOC$WRITE_IO and IOC$WRITE_PCI_CONFIG:
o Read a longword, modify the tribyte, and rewrite the
longword.
Note that AlphaServer 8200/8400 and GS60/140 systems with
Alpha 21264 CPUs support tribyte reads and writes.
o I/O to Unaligned Words in PCI Space is Not Allowed
This note applies to Compaq AlphaServer DS20E systems. When
device drivers call the IOC$CRAM_CMD, IOC$READ_IO, and
IOC$WRITE_IO system routines with the IOC$K_WORD or
IOC$K_WORD_LANED parameters, the I/O address must be on a
natural, word-aligned boundary. (In other words, the I/O
address must be an even number). If the I/O address is an odd
number, these system routines return SS$_BADPARAM.
Use AUTOGEN with Feedback to Resize ERLBUFFERPAGES for FRU
Configuration Error Log Entry
The FRU configuration tree provided by the Compaq AlphaServer
DS20E console firmware is not copied to the errorlog file if
the SYSGEN parameter ERLBUFFERPAGES is not large enough. Use
the following command to run AUTOGEN with the FEEDBACK option
to automatically calculate the correct setting of
ERLBUFFERPAGES and resize the SYS$ERRORLOG.DMP file for the
configuration error log entry.
$ @SYS$UPDATE:AUTOGEN SAVPARAMS REBOOT FEEDBACK
o Server Management Event Handler Driver and Process on
Compaq AlphaServer
DS20E OpenVMS Alpha Version 7.1-2 automatically starts the
Server Management Event handler driver and process on Compaq
AlphaServer DS20E systems. The SMHANDLER process spends most
of the time in the hibernate state. When a Server Management
Event occurs, an interrupt is delivered to the system specific
handler, which parses the exception frame and notifies
SMDRIVER that an event has occurred. The driver then delivers
an AST to the SMHANDLER process with the event type. The
SMHANDLER process reports signaled events in the process log
file SYS$MANAGER:SMHANDLER.LOG and with an OPCOM message.
Additional information about the event is recorded in the
system error log file.
The SMHANDLER process may produce one of following new system
error messages:
o %SMHANDLER-S-STARTUP, server management event handler
startup
o %SMHANDLER-W-RFF, redundant fan failure detected
o %SMHANDLER-W-RPS, redundant power supply failure detected
o %SMHANDLER-W-TEMP, warning temperature exceeded
To correct the problem, the system manager should schedule a
system shutdown at a convenient time and request Compaq Field
Service to replace the failing hardware component. In the
meantime, the system will continue, but without the protection
of the redundant hardware.
o DS20E Support for the 3X-DEPVD-AA PCI Adapter and TCP/IP for
OpenVMS
TCP/IP for OpenVMS Version 4.2 does not support the new
3X-DEPVD-AA PCI adapter on the AlphaServer DS20E. Prior to
running UCX$CONFIG procedures, use the following command to
manually configure TCP/IP with the new ethernet adapter:
_$ /INTERNET_INTERFACE=I /TYPE=(ETHERNET,CLUSTER) -
_$ /INTERNET_INTERFACE=I /TYPE=(ETHERNET,CLUSTER) -
_$ /DESCRIPTION=INTEL_ETHERNET
Check with your Compaq support representative if you have
further questions on TCP/IP and the 3X-DEPVD-AA PCI adapter.
o P2v (JIB CARD) graphics support
This change adds P2V chip support to the P2A code used on ELSA.
This functionality is only used if you are using a P2V graphics
adaptor
Image(s) Affected: [SYS$LDR]SYS$GZVDRIVER.EXE
[SYSEXE]SYS$CONFIG.DAT
o Creating an OpenVMS Galaxy on an AlphaServer ES40 System
This Section describes the requirements and procedures for creating
an OpenVMS Galaxy computing environment on an AlphaServer ES40.
For complete information about the Galaxy Software Architecture on
OpenVMS Alpha, refer to the OpenVMS Alpha Galaxy Guide (Order
number: AA-REZQB-TE). The most recent version is always available
at
http://www.openvms.digital.com:8000/
For complete information about AlphaServer ES40 systems, see the
AlphaServer ES40 Owners Guide (Order number: EK-ES240-UG.A01).
Image(s) Affected: [SYSEXE]GCU.EXE
[SYSMGR]GALAXY.GCR
[SYS$LDR]SYS$CPU_ROUTINES_2208.EXE
[SYS$LDR]SYS$CPU_ROUTINES_2508.EXE
[SYSEXE]SYS$SMHANDLER.EXE
To create an OpenVMS Galaxy on an AlphaServer ES40 system:
1. Read the Release Notes chapter in the OpenVMS Alpha Galaxy
Guide.
2. Read the configuration and hardware requirements.
3. Perform the steps described below.
o Before You Start
In addition to the information in the Release Notes chapter in
the OpenVMS Alpha Galaxy Guide, you must also be familiar with
the following configuration and hardware requirements:
o Two-instance maximum
You can run a maximum of two instances of OpenVMS on an
AlphaServer ES40.
o Console firmware
To create an OpenVMS Galaxy environment on AlphaServer
ES40 systems, you must download the latest version of the
V5.5-xx console firmware from the following location:
http://ftp.digital.com/pub/Digital/Alpha/firmware/interim/ES40/
o AlphaServer ES40 clock
An AlphaServer ES40 has one clock. For an OpenVMS Galaxy,
this means that you cannot run the two instances at
different times. Also, the SET TIME command affects both
instances. Note that this may not become evident until a
number of hours have passed.
o Console ports
COM1 (lower) is the console port for instance 0.
COM2 (upper) is the console port for instance 1.
Unlike creating an OpenVMS Galaxy on an AlphaServer 8400,
you do not need additional hardware for the second
console. COM-2 is used for this purpose.
o CPUs
CPU0 must be the primary for instance 0.
CPU1 must be the primary for instance 1.
CPUs 2 and 3 are optional secondary CPUs that can be migrated.
For an example of the CPU environment variable settings on
an AlphaServer ES40.
o I/O adapters
PCI Hose 0 (PCI0) belongs to instance 0 (upper 4 PCI slots)
PCI Hose 1 (PCI1) belongs to instance 1 (lower 6 PCI slots)
Note that PCI0 contains an embedded ISA controller.
o Storage controllers
You will need one storage controller (such as a KZPSA) per
instance. For each instance, this can go to a separate
Storagework box or to the same box for running as a SCSI
cluster.
o Network cards
If each instance needs network access, a network card
(such as a DE500) is required for each instance.
One card each goes in PCI0 and PCI1.
o Memory Granularity Restrictions
Private memory must start on a 64MB boundary.
Shared memory must start on an 8MB boundary.
All instances except the last must have a multiple of 64MB.
Step 1: Confirm the AlphaServer ES40 Configuration
Use the SHOW CONFIG command to make sure that the AlphaServer
ES40 you are using to create an OpenVMS Galaxy environment
meets the requirements described.
At the console prompt, enter the following command:
P00>>>show config
The console displays information similar to the following
example:
Firmware
ARC Console: v5.70
PALcode: OpenVMS PALcode V1.61-2
Tru64 UNIX PALcode V1.54-2
Serial Rom: V2.2-F
RMC Rom: V1.0
RMC Flash Rom: T2.0
Processors
CPU 0 Alpha 21264-4 500 MHz 4MB Bcache
CPU 1 Alpha 21264-4 500 MHz 4MB Bcache
CPU 2 Alpha 21264-4 500 MHz 4MB Bcache
CPU 3 Alpha 21264-4 500 MHz 4MB Bcache
Core Logic
Cchip DECchip 21272-CA Rev 9(C4)
Dchip DECchip 21272-DA Rev 2
Pchip 0 DECchip 21272-EA Rev 2
Pchip 1 DECchip 21272-EA Rev 2
TIG Rev 10
Memory
Array Size Base Address Intlv Mode
--------- ---------- ---------------- ----------
0 4096Mb 0000000000000000 2-Way
1 4096Mb 0000000100000000 2-Way
2 1024Mb 0000000200000000 2-Way
3 1024Mb 0000000240000000 2-Way
10240 MB of System Memory
Slot Option Hose 0, Bus 0, PCI
1 DAPCA-FA ATM622 MMF
2 DECchip 21152-AA Bridge to Bus 2, PCI
3 DEC PCI FDDI fwb0.0.0.3.0 00-00-F8-BD-C6-5C
4 DEC PowerStorm
7 Acer Labs M1543C Bridge to Bus 1, ISA
15 Acer Labs M1543C IDE dqa.0.0.15.0
dqb.0.1.15.0
dqa0.0.0.15.0 TOSHIBA CD-ROM XM-6302B
19 Acer Labs M1543C USB
Option Hose 0, Bus 1, ISA
Floppy dva0.0.0.1000.0
Slot Option Hose 0, Bus 2, PCI
0 NCR 53C875 pkd0.7.0.2000.0 SCSI Bus ID 7
1 NCR 53C875 pke0.7.0.2001.0 SCSI Bus ID 7
dke100.1.0.2001.0 RZ1BB-CS
dke200.2.0.2001.0 RZ1BB-CS
dke300.3.0.2001.0 RZ1CB-CS
dke400.4.0.2001.0 RZ1CB-CS
2 DE500-AA Network Con ewa0.0.0.2002.0 00-06-2B-00-0A-58
Slot Option Hose 1, Bus 0, PCI
1 NCR 53C895 pka0.7.0.1.1 SCSI Bus ID 7
dka100.1.0.1.1 RZ2CA-LA
dka300.3.0.1.1 RZ2CA-LA
2 Fore ATM 155/622 Ada
3 DEC PCI FDDI fwa0.0.0.3.1 00-00-F8-45-B2-CE
4 QLogic ISP10x0 pkb0.7.0.4.1 SCSI Bus ID 7
dkb100.1.0.4.1 HSZ50-AX
dkb101.1.0.4.1 HSZ50-AX
dkb200.2.0.4.1 HSZ50-AX
dkb201.2.0.4.1 HSZ50-AX
dkb202.2.0.4.1 HSZ50-AX
5 QLogic ISP10x0 pkc0.7.0.5.1 SCSI Bus ID 7
dkc100.1.0.5.1 RZ1CB-CS
dkc200.2.0.5.1 RZ1CB-CS
dkc300.3.0.5.1 RZ1CB-CS
dkc400.4.0.5.1 RZ1CB-CS
6 DECchip 21154-AA Bridge to Bus 2, PCI
Slot Option Hose 1, Bus 2, PCI
4 DE602-AA eia0.0.0.2004.1 00-08-C7-91-0A-AA
5 DE602-AA eib0.0.0.2005.1 00-08-C7-91-0A-AB
6 DE602-TA eic0.0.0.2006.1 00-08-C7-66-80-9E
7 DE602-TA eid0.0.0.2007.1 00-08-C7-66-80-5E
Step 2: Install OpenVMS Alpha Version 7.2-1
No special installation procedures are required to run OpenVMS
Galaxy software. Galaxy functionality is included in the base
operating system and can be enabled or disabled using the
console command and system parameter values described later in
this chapter.
If your AlphaServer ES40 is not part of a SCSI cluster, you
must install OpenVMS Version 7.2-1 on two system disks-one
disk for each instance.
If your AlphaServer ES40 is part of a SCSI cluster with a
cluster-common system disk, install OpenVMS Version 7.2-1 on
one system disk.
For more information about installing the OpenVMS Alpha
operating system, see the OpenVMS Alpha Version 7.2 Upgrade
and Installation Guide.
Step 3: Upgrade the Firmware
To upgrade the firmware, use one of the following procedures:
Copy the firmware file to MOM$SYSTEM on a MOP-enabled server
that is accessible to the AlphaServer ES40. Enter the
following commands on the console:
P00>>> boot -fl 0,0 ewa0 -fi {firmware filename}
UPD> update srm*
Or, use the following commands:
P00>>> BOOT -FLAGS 0,A0 cd_device_name
.
.
.
Bootfile: {firmware filename}
.
.
.
Step 5: Initialize the System and Start the Console
Devices
1. Initialize the system and start the Galaxy firmware by
entering the following commands:
P00>>> init
P00>>> lpinit ! same as galaxy command
After the self-test completes, the Galaxy command will
start the console on instance 1.
Note that when the I/O bus is divided between the two
Galaxy partitions, the port letter of a device might
change. For example, a disk designated as DKC300 when the
AlphaServer ES40 is a single system could become DKA300
when it is configured as partition 0 of the OpenVMS
Galaxy.
2. Configure the console for instance 1.
3. Configure the system root, boot device, and other related
variables.
The following example settings are from an OpenVMS
Engineering system. Change these variables to meet the
needs of your own environment.
Instance 0
P00>>> set boot_osflags 12,0
P00>>> set bootdef_dev dka0
P00>>> set boot_reset off !!! must be OFF !!!
P00>>> set ewa0_mode twisted
Instance 1
P01>>> set boot_osflags 11,0
P01>>> set bootdef_dev dkb200
P01>>> set boot_reset off !!! must be OFF !!!
P01>>> set ewa0_mode twisted
4. Boot instance 1 as follows:
P01>>> boot
Once instance 1 is booted, log in to the system account
and edit the SYS$SYSTEM:MODPARAMS.DAT file to include the
following line:
GALAXY=1
Confirm that the SCSNODE and SCSSYSTEMID SYSGEN parameters
are correct. Run AUTOGEN as follows to configure instance
1 as a Galaxy member, and leave the system halted:
$ @SYS$UPDATE:AUTOGEN GETDATA SHUTDOWN INITIAL
5. Boot instance 0 as follows:
P00>>> boot
Once instance 0 is booted, log in to the system account
and edit the SYS$SYSTEM:MODPARAMS.DAT file to include the
following line:
GALAXY=1
Confirm that the SCSNODE and SCSSYSTEMID SYSGEN parameters
are correct. Run AUTOGEN as follows to configure instance
0 as a Galaxy member, and leave the system halted:
$ @SYS$UPDATE:AUTOGEN GETDATA SHUTDOWN INITIAL
6. Prepare the Galaxy to come up automatically upon
initialization or power cycle of the system. Set the
AUTO_ACTION environment variable on both instances to
RESTART.
P00>>> set auto_action restart
P01>>> set auto_action restart
7. Initialize the Galaxy again by entering the following
commands at the primary console:
P00>>> init
When the console displays the following confirmation
prompt, type Y:
Do you REALLY want to reset all partitions? (Y/N)
Alternatively, you could power-cycle your system, and the
Galaxy with both instances should bootstrap automatically.
Congratulations! You have created an OpenVMS Galaxy.
PROBLEMS ADDRESSED IN VMS721_DS20E_ES40 KIT
o The EXTENDED_ID flag in the SYS$CONFIG.DAT file is used to
allow full 64-bit ID checking on PCI devices. This will be
used for LAN and ATM devices to ensure that the device is a
qualified device.
A problem in the LOOKUP_ID code causes the ID mask to be
extended to 64-bits the first time the flag is seen, and it is
never reduced back to 32-bits for non-extended IDs. This
causes a failure to find some disk devices at boot, and
prevents booting.
The user sees an error that a device on the boot command line
could not be found, and the system halts.
Image(s) Affected: [SYS$LDR]EXEC_INIT.EXE
o When the 680 handler issued the code 22Bh to SYS$SMHANDLER it
did not display a message.
Image(s) Affected: [SYSEXE]SYS$SMHANDLER.EXE
PROBLEMS ADDRESSED IN VMS721_DDTM-V0100 KIT
o The TP_SERVER process consumes CPU cycles,
eventually leading to a SSRVEXCEPT System crash at
insruction INSQUEL.
Images Affected: [SYSEXE]TPSERV.EXE
o A system crashes with the following DDTMBUG bugcheck
at offset SYS$TRANSACTION_SERVICES_NPRO+00D10:
DDTMBUG, DDTM has detected an invalid XPCB$V_EVENT_INPROG
Images Affected: [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE
PROBLEMS ADDRESSED IN VMS721_DEBUG-V0100 KIT
o The DEBUG command SHOW SYMBOL X in Y can fail. See
the example below of a C file with a module name
'DEBUG_SUB':
typedef float F32;
F32 gsum;
F32 gbat;
void debug_sub (void);
void debug_sub()
{
gbat = gsum + gbat;
return;
}
Here, the DEBUG command "SHOW SYMB g* in DEBUG_SUB
will fail.
Depending upon how the code is compiled, i.e.,
compiler version and/or compilation switches, the
global symbol table entry for the routine
'debug_sub' can be upper- or lower-case. If it is
lower-case, this command works fine.
If the global symbol table entry for the routine
'debug_sub' is upper-case, then DBG$STA_GETSYMBOL
(via LOOKUP_GBL called from DBG$STA_LOOKUP_GBL)
matches the global symbol table entry and then finds
and returns the corresponding non-global description
of 'debug_sub' in the DSTs.
Images Affected: [SYSLIB]DEBUGSHR.EXE
PROBLEMS ADDRESSED IN VMS721_DELETE-V0100 KIT
o The PURGE/CONFIRM command(s) across the network does not
prompt with file names. See example below:
>>USER GO> Purge TEST1:: /Confirm
>> DELETE ? [N]:
>> DELETE ? [N]:
>> DELETE ? [N]:
If one file name is purged, the user is then prompted for
other file names. See example below:
>>USER GO> Purge TEST1:: /Confirm
>> DELETE ? [N]:
>> DELETE ? [N]:
>> DELETE ? [N]:
>> DELETE ? [N]: y
>> DELETE 0""::SYS$SPECIFIC:[FAL$SERVER]NET$SERVER.LOG;4301 ? [N]:
Images Affected: [SYSEXE]DELETE.EXE
o A network purge incorrectly deletes all files with the same
name(s), even if the files are in different directories. See
the test sample below:
$ pu/log/noconf 0"system password"::disk1:[test...]*.txt
%PURGE-I-FILPURG, 0"system password"::DISK1:[TEST.A]1.TXT;1
deleted (0 blocks)
%PURGE-I-FILPURG, 0"system password"::DISK1:[TEST.C]1.TXT;2
deleted (0 blocks)
%PURGE-I-FILPURG, 0"system password"::DISK1:[TEST.C]1.TXT;1
deleted (0 blocks)
%PURGE-I-FILPURG, 0"system password"::DISK1:[TEST.C]3.TXT;1
deleted (0 blocks)
%PURGE-I-TOTAL, 4 files deleted (0 blocks)
Images Affected: [SYSEXE]DELETE.EXE
Problems Addressed in VMS721_DQCONFIG-V0200:
o Use of a CD-ROM on a high performance Alpha system may cause
the PCI bus on the system to hang.
Images Affected: [SYS$LDR]SYS$DQDRIVER.EXE
Problems Addressed in VMS721_DQCONFIG-V0100:
o When a system that includes IDE/ATA or ATAPI drives is booted
from one of these devices, a second unit on the same IDE bus
will not autoconfigure. For example, if system boot is from
DQA0:, drive DQA1: will not be auto-configured. Currently, the
only systems affected are the DS10/VS10/XP90.
Images Affected: [SYS$LDR]SYS$ICBM.EXE
o ES40 machines crash when a KZPAC is installed in Hose 0 and an
attempt is made to mount a CD-ROM. This problem is also seen,
to a lesser degree, on other platforms.
Images Affected: [SYS$LDR]SYS$DQDRIVER.EXE
o Remove DMA support on the following platforms:
+ DPWS-xxxau
+ XP1000
+ DS20
+ DS20E
+ SMARTengine 21264/Alpha PCI/ISA SBC
Images Affected: [SYS$LDR]SYS$DQDRIVER.EXE
PROBLEMS ADDRESSED IN VMS721_DRIVER-V0200 KIT:
o When a user attempts to create a directory on an IDE disk
deuie larger than 30 GB, the system crashes with a UNXSIGNAL
bugcheck at OTS$REM_UL_C+000B4 (a divide-by-0 crash).
Crashdump Summary Information:
------------------------------
Bugcheck Type: UNXSIGNAL, Unexpected signal name in ACP
Current Process: face - 407
Current Image: $14$DKB0:[SYS4.SYSCOMMON.][SYSEXE]CREATE.EXE
Failing PC: FFFFFFFF.80007268 OTS$REM_UL_C+000B8
Failing PS: 10000000.00000000
Module: SYS$BASE_IMAGE (Link Date/Time:
29-DEC-1999 03:52:51.75)
Offset: 00005268
Images Affected: [SYS$LDR]SYS$DQDRIVER.EXE
o The system cannot play audio CDs.
Images Affected: [SYS$LDR]SYS$DQDRIVER.EXE
o A second instance of a GALAXY can not be booted. Also
observed are repeated Bus Addressable Pool (BAP) errors with
subsequent AUTOGEN runs.
Images Affected: [SYS$LDS]SYS$DQDRIVER.EXE
o Not all DRcu:: disks are seen by all cluster members.
Images Affected: [SYS$LDR]SYS$DRDRIVER.EXE
o V7.2-1 systems will not be able to access Fibre Channel tapes
which are served by systems running verions of VMS later than
V7.2-1H1. This change allows this access.
Images Affected: [SYS$LDR]SYS$TUDRIVER.EXE
[SYS$LDR]SYS$DUDRIVER.EXE
o BACKUP between a V7.2-1 client and a V7.1 TMSCP served tape
fails with POSITERR and IVDENS errors.
Images Affected: [SYS$LDR]SYS$TUDRIVER.EXE
[SYS$LDR]SYS$TUDRIVER.EXE
o A MOUNT/FOR/NOASSIST/DENSITY=6250 command can be is issued for
devices such as TA90 and TZ88. These commands make no sense
for these devices but c ustomers have command files, that
issue this command, without regard to the type of drive. Wehn
sucha command file runs, the process or tape device will hang.
Images Affected: [SYS$LDR]SYS$TUDRIVER.EXE
o A system can crash with an INVEXCEPTN bugcheck when a UCB
(unit control block) was served prematurely.
Crashdump Summary Information:
------------------------------
Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL
Current Process: NULL
Current Image:
Failing PC: FFFFFFFF.8022C8AC
SCS$MSCP_CHECK_SERVICE_C+0085C
Failing PS: 10000000.00000804
Module: MSCP
Offset: 000028AC
Images Affected: [SYS$LDR]SYS$DRDRIVER.EXE
o DRA devices can not be served to the cluster because not all
DRcu:: disks are seen by all cluster members. For example,
MOUNT/CLUSTER $1$DRA0: will not fail or signal an error.
Images Affected: [SYS$LDR]SYS$DRDRIVER.EXE
Problems Addressed in VMS721_DRIVER-V0100:
o IRP (I/O request packets) exit packets are not logged if
FAST_PATH is enabled.
Images Affected: [SYS$LDR]SYS$DUDRIVER.EXE
o A tape device hangs following MOUNT-F-SERIOUSEXCP errors. The
tape device encounters a SEREXCP condition, which could be
related to bad media being cycled through a tape library.
Images Affected: [SYS$LDR]SYS$TUDRIVER.EXE
o The system can crash with an INVEXCEPTN in SYS$DUDRIVER.
Images Affected: [SYS$LDR]SYS$DUDRIVER.EXE
[SYS$LDR]SYS$TUDRIVER.EXE
o Fix two DUDRIVER FAST_PATH checks.
1. Change the testing of IRP$M_SHDIO from IRP$L_STS to
IRP$L_STS2.
2. Change the "obsolete modifiers" constant from ^X180 to
^80, since ^X100 is a IO$M_MSCPMODIFS bit.
These fixes ensure FAST_PATH is used in all appropriate
instances.
Images Affected: [SYS$LDR]SYS$DUDRIVER.EXE
o The system can experience an invalid exception bugcheck in
DUDRIVER.
Images Affected: [SYS$LDR]SYS$DUDRIVER.EXE
[SYS$LDR]SYS$TUDRIVER.EXE
o Update the DQDRIVER to provide an IO$_DIAGNOSE interface to
ATAPI devices, similar to the capabilities afforded in
DKDRIVER for SCSI devices.
Images Affected: [SYS$LDR]SYS$DKDRIVER.EXE
o An INVPTEFMT bugcheck occurred in IO_ROUTINE_MON.EXE. See the
dump summary below:
Crash Time: 10-APR-2000 17:41:30.51
Bugcheck Type: INVPTEFMT, Invalid page table entry format
Node: WILD11 (Cluster)
CPU Type: Compaq AlphaServer ES40
VMS Version: X700-FT1
Current Process: NULL
Current Image:
Failing PC: FFFFFFFF.800CB0EC IOC_STD$PTETOPFN_C+0008C
Failing PS: 38000000.00000804
Module: IO_ROUTINES_MON (Link Date/Time: 1-APR-2000
00:01:45.84)
Offset: 000050EC
Images Affected: [SYS$LDR]SYS$PBDRIVER.EXE
o An INVEXCEPTN crash occurs @SYS$PBDRIVER+13088. A call to
delete a shared memory region results in a NOWAIT error, and
contacting the virtual address (VA) of the region ultimately
results in the crash. See the partial dump below:
------------------------------
Crash Time: 15-MAY-2000 08:55:51.89
Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL
Node: WILD5 (Cluster)
CPU Type: Compaq AlphaServer GS160 6/731
VMS Version: X70V-SSB
Current Process: NULL
Current Image:
Failing PC: FFFFFFFF.80481088 SYS$PBDRIVER+13088
Failing PS: 20000000.00000804
Module: SYS$PBDRIVER (Link Date/Time: 5-MAY-2000 23:36:55.31)
Offset: 00013088
Boot Time: 15-MAY-2000 08:41:35.00
System Uptime: 0 00:14:16.89
Crash/Primary CPU: 08/08
System/CPU Type: 2308
Saved Processes: 23
Pagesize: 8 KByte (8192 bytes)
Physical Memory: 8192 MByte (67108864 PFNs, memory)
Images Affected: [SYS$LDR]SYS$PBDRIVER.EXE
o A tape device can hang following MOUNT-F-SERIOUSEXCP errors.
BHAK$ mount/over=id $90$MUA2:
%MOUNT-F-SERIOUSEXCP, serious exception detected by TMSCP controller
BHAK$ sho dev /full mua2
Images Affected: [SYS$LDR]SYS$TUDRIVER.EXE
o After failover, MSCP-served disks hang in MNTVER (MOUNT
VERIFY). See a portion of an OPERCRASH dump below:
- On the EBJB19:: client, check device $1$DGA2014:
[WILD3$DGA2014 (WILD5$DGA2014)]
Device status: 08265810 ONLINE,valid,unload,mntverip,
Device status: 08265810 ONLINE,valid,unload,mntverip,
Process (index=22) "O-2-BAD" stuck in LEF on this disk.
B400222 0022 O-2-BAD SYSTEM LEF 4
Images Affected: [SYS$LDR]SYS$DUDRIVER.EXE
o BACKUP/MED=COMPACTION to an HSJ-based TZ87 fails with an
SS-F-IVDENS (invalid density) error.
Images Affected: [SYS$LDR]SYS$TUDRIVER.EXE
o A MOUNT command issued on V7.1 client for an Alpha V7.2-1,
TMSCP served HSJ/TZ88 device fails with a MOUNT-F_VOLIN (MOUNT
violation) error.
Images Affected: [SYS$LDR]SYS$TUDRIVER.EXE
o The MOUNT/MED=COMPACTION command issued from a client does not
enable compaction on TMSCP-served SCSI tape devices.
Images Affected: [SYS$LDR]SYS$TUDRIVER.EXE
o An INIT/MED=NOCOMP command to a SUPER-DLT (TZXX) drive, does
not go into non-compacted mode. See example below:
BTANKA> init/media=comp $255$MKC600: test
BTANKA> sh dev/fu $255$MKC600:
Magtape $255$MKC600: (DAVID3), device type COMPAQ DLT8000, is
ONLINE, file-oriented device, available to cluster, error
logging is enabled, controller supports compaction (compaction
disabled).
Error count 0 Operations completed 1339
Owner process "" Owner UIC [SYSTEM]
Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:R,W
Reference count 0 Default buffer siz 2048
Density DLT8000 Format Normal-11
Host name "DAVID3" Host type, avail Digital Personal
WorkStation, yes
Allocation class 255
Volume status:no-unload on dismount, beginning-of-tape, odd parity.
BTANKA>
Images Affected: [SYS$LDR]SYS$TUDRIVER.EXE
o A satellite system cannot boot when its allocation class is
the same as the allocation class of the system disk, yet
different from the allocation class of the MSCP disk server.
The system will crash with an MSCPCLASS bugcheck after 5
minutes. SDA shows references to disk with an allocation
class of the server.
Crash Time: 14-MAR-2000 17:00:14.02
Bugcheck Type: MSCPCLASS, Fatal error detected by MSCP class
driver
Node: TSTPC3 (Cluster)
CPU Type:
VMS Version: V7.2-1
Current Process: SWAPPER
Current Image:
Failing PC: FFFFFFFF.81C49B90 SYS$DUDRIVER+09B90
Failing PS: 18000000.00000804
Module: SYS$DUDRIVER (Link Date/Time: 28-MAY-1999
23:19:57.92)
Offset: 00009B90
Images Affected: [SYS$LDR]SYS$DUDRIVER.EXE
o A process or system hangs with file I/Os stalled and the class
driver data block (CDDB) stuck in a single stream mode.
Images Affected: [SYS$LDR]SYS$DUDRIVER.EXE
[SYS$LDR]SYS$TUDRIVER.EXE
Problems Addressed in VMS721_F11X-V0200:
o The system crashed at F11BXQP+11F54 with an XQPERR bugcheck
while running Storage Library System (SLS) backup. A portion
of a sample dump appears below:
Dump taken on 21-JUN-1999 20:57:45.45
XQPERR, Error detected by file system XQP
Time of system crash: 21-JUN-1999 20:57:45.45
Version of system: OpenVMS (TM) VAX Version V7.1
System Version Major ID/Minor ID: 1/0
VAXcluster node: PMSA04, a VAX 7000-830
Crash CPU ID/Primary CPU ID: 02/00
Bitmask of CPUs active/available: 00000007/00000007
CPU bugcheck codes:
CPU 02 -- XQPERR, Error detected by file system XQP
2 others -- CPUEXIT, Shutdown requested by another CPU
CPU 02 reason for Bugcheck: XQPERR, Error detected by file system XQP
Process currently executing on this CPU: SYSBAK_C059
Current image file: DSA947:[SLS$FILES_VAX.][SYSTEM]VMSBUXX.EXE;4
Current IPL: 0 (decimal)
CPU database address: 862A4000
MPB address: 8B32BF00
General registers:
R0 = 00000002 R1 = 0000000C R2 = 8A69CE90 R3 = 00000000
R4 = 00000002 R5 = 0000023C R6 = 7FE8F9A8 R7 = 00000001
R8 = 7FE8FA40 R9 = 800083F4 R10 = 7FE8FA64 R11 = 7FE8FA60
AP = 7FE8F334 FP = 7FE8F2FC SP = 7FE8F2C8 PC = 862F8D58
PSL = 00000004
Processor registers:
P0BR = BD0FB400 SBR = 1EF80400 ASTLVL = 00000001
P0LR = 00001025 SLR = 003FFF00 SISR = 00000000
P1BR = BCD2D800 PCBB = 562FF420 ICCS = 80000080
P1LR = 001FEDC7 SCBB = 1EF53200 SID = 17000201
LDEV = 00018008 LBER = 00000000 LCNR = 00000001
LCON0 = 1F000004 LCON1 = 00000000 TOUR = 00000000
LBECR0 = 0044003A LBECR1 = 00009120 LMODE = 000332A4
LMERR = 00000000 BIU_STAT = F00E1070 BIU_ADDR = 00000298
MMESTS = 1C008000 TBSTS = 800001D0 PCSTS = FFFFF800
ISP = 862A6200
KSP = 7FE8F2C8
ESP = 7FFE9800
SSP = 7FFECA44
USP = 7FDBAFD4
No spinlocks currently owned by CPU 02
SDA> ex/inst @pc-30;30
F11BXQP+11F28: BSBB F11BXQP+11F81
F11BXQP+11F2A: BNEQ F11BXQP+11F43
F11BXQP+11F2C: BBS #03,18(R2),F11BXQP+11F46
F11BXQP+11F31: PUSHL R2
F11BXQP+11F33: CALLS #01,F11BXQP+00B0E
F11BXQP+11F3A: MOVL R2,R0
F11BXQP+11F3D: JSB F11BXQP+122EE
F11BXQP+11F43: BRW F11BXQP+1205C
F11BXQP+11F46: BBC #05,18(R2),F11BXQP+11F4F
F11BXQP+11F4B: BUGW #05CC
F11BXQP+11F4F: BBC #02,18(R2),F11BXQP+11F58
F11BXQP+11F54: BUGW #05CC
F11BXQP+11F58: MOVL @30(SP),R0
SDA> ex/inst @pc-30;30
8A69CEA8: 0000000E "...."
=1110 so bit 2 is set so we don't jump around the bugchk
Process index: 005B Name: SYSBAK_C059 Extended PID: 2120BC5B
----------------------------------------------------------------
Images Affected: [SYS$LDR]F11BXQP.EXE
[SYS$LDR]F11BXQP.STB
o A directory of a directory file that is greater than 127
blocks can cause a false SS$_ENDOFFILE (EOF) to be reported.
Images Affected: [SYS$LDR]F11BXQP.EXE
[SYS$LDR]F11BXQP.STB
o A process would sometimes hang and would not be able to be
deleted when writing to a sequential file. The process
appeared to have a 'lost' I/O outstanding, when in fact, the
I/O was on the file control block (FCB) high water mark (HWM)
wait queue waiting for other I/Os to complete.
Images Affected: [SYS$LDR]F11BXQP.EXE
[SYS$LDR]F11BXQP.STB
o The ancillary control process START_ACP MOUNT routine
bugchecked with a NOTUCBRVT during the mounting of a jukebox
device. A portion of the dump appears below:
Dump taken on 27-OCT-1999 21:54:33.46
NOTUCBRVT, Not UCB pointer in RVT
Version of system:OpenVMS (TM) Alpha Operating System, Version V7.2
VMScluster node: APOLLO, a AlphaServer 8400 5/440
Process currently executing on this CPU: BATCH_2730
Current image file: DSA20:[SYS0.SYSCOMMON.][SYSEXE]VMOUNT.EXE
Current IPL: 2 (decimal)
MOUNT routine START_ACP tripped over the following RVT because
RVT$L_REFC (00000002) is not equal to the number of UBC's in
RVT$L_UCBLST (one):
SDA> format @r1
FFFFFFFF.821A3F00 RVT$L_STRUCLKID 5E05FD3C
FFFFFFFF.821A3F04 RVT$L_REFC 00000002
FFFFFFFF.821A3F08 RVT$W_SIZE 00C0
FFFFFFFF.821A3F0A RVT$B_TYPE 0E
FFFFFFFF.821A3F0B RVT$B_NVOLS 0A
FFFFFFFF.821A3F0C RVT$T_STRUCNAME 31
FFFFFFFF.821A3F0D 353939
FFFFFFFF.821A3F10 20203031
FFFFFFFF.821A3F14 20202020
FFFFFFFF.821A3F18 RVT$T_VLSLCKNAM 31
FFFFFFFF.821A3F19 353939
FFFFFFFF.821A3F1C 20203031
FFFFFFFF.821A3F20 20202020
FFFFFFFF.821A3F24 RVT$L_BLOCKID 3B076C2F
FFFFFFFF.821A3F28 RVT$B_ACB 00
FFFFFFFF.821A3F29 0000000
FFFFFFFF.821A3F2C 00000000
FFFFFFFF.821A3F30 20000000
FFFFFFFF.821A3F34 00010001
XQP$DEQBLOCKER
FFFFFFFF.821A3F3C 821A3F00
FFFFFFFF.821A3F40 00000000
FFFFFFFF.821A3F44 00000000
FFFFFFFF.821A3F48 00000000
FFFFFFFF.821A3F4C RVT$L_TRANS 00000001
FFFFFFFF.821A3F50 RVT$L_ACTIVITY 00000001
FFFFFFFF.821A3F54 RVT$A_RVTVCB 8164E240
RVT$L_UCBLST
RVT$C_LENGTH
SDA> show stack /long (.+rvt$l_ucblst);4*(@(.+rvt$b_nvols))&ff
FFFFFFFF.821A3F54 8164E240
FFFFFFFF.821A3F58 00000000
FFFFFFFF.821A3F5C 00000000
FFFFFFFF.821A3F60 00000000
FFFFFFFF.821A3F64 00000000
FFFFFFFF.821A3F68 00000000
FFFFFFFF.821A3F6C 00000000
FFFFFFFF.821A3F70 00000000
FFFFFFFF.821A3F74 00000000
FFFFFFFF.821A3F78 00000000
Images Affected: [SYS$LDR]F11BXQP.EXE
o An exception, which leads to an INVEXCEPTN bugcheck, occurs in
XQP routine INS_LIMBO or TRIM_LIMBO. The footprint is a
corrupt limbo queue (EXE$GQ_LIMBOQ) and the exception occurs
during a VAX_INSQUE or VAX_REMQUE.
Images Affected: [SYS$LDR]F11BXQP.EXE
[SYS$LDR]F11BXQP.STB
o If a window control block (WCB) list in routine MARK_INCOMPLETE
becomes corrupted, the system can crash with a NOTWCBWCB bugcheck.
Images Affected: [SYS$LDR]F11BXQP.EXE
[SYS$LDR]F11BXQP.STB
o After removing a file control block (FCB) from the limbo
queue, two bugchecks were improperly added to REM_LIMBOQ.
These two XQPERR bugchecks have been removed.
1. If the queue is empty, then bugcheck if the FCB reference
count is 1 (accounting for FID_TO_SPEC).
2. If the queue is not empty, then bugcheck if the FCB
reference count is not 1 or decrement EXE$GL_LIMBOLEN.
Both bugchecks have since been removed.
Images Affected: [SYS$LDR]F11BXQP.EXE
o Make INVSECURESTATE "Invalid state detected by security
subsystem" bugcheck FATAL.
Images Affected: [SYS$LDR]F11BXQP.EXE
o Separator pages for print jobs which are created via COPY to a
spooled device do not include the complete file specification.
The current length calculation includes the file name, but not
the device name and null directory specification.
Images Affected: [SYS$LDR]F11BXQP.EXE
o The system can crash with an XQPERR bugcheck in routine
RES_SEQ_MISMATCH. The error message is "'Found a stale
referenced or non-directory FCB in FCB queue'.
Images Affected: [SYS$LDR]F11BXQP.EXE
o The system can crash with an XQPERR bugcheck in routine
MAKE_DEACCESS. The error message is "deaccess conversion
failed". In one instance, the APPEND command was used to
update files and/or create new files.
Images Affected: [SYS$LDR]F11BXQP.EXE
o The system can crash with an XQPERR bugcheck at offset
UPDATE_INDX_C+000C8 A crash summary follows below:
Crash Time: 2-MAY-2000 18:08:04.93
Bugcheck Type: XQPERR, Error detected by file system XQP
Node: CSUPR3 (Cluster)
CPU Type: AlphaServer 8400 5/625
VMS Version: V7.2-1
Current Process: KELLYS
Current Image: DSA0:[SYS2.SYSCOMMON.][SYSEXE]RENAME.EXE
Failing PC: FFFFFFFF.BF636BBC UPDATE_INDX_C+000C8
Failing PS: 00000000.00000000
Module: F11BXQP (Link Date/Time: 13-MAR-2000 21:14:54.58)
Offset: 00020BBC
Boot Time: 30-APR-2000 15:42:27.00
System Uptime: 2 02:25:37.93
Crash/Primary CPU: 00/00
System/CPU Type: 0C05
Saved Processes: 122
Pagesize: 8 KByte (8192 bytes)
Physical Memory: 4096 MByte (524288 PFNs, contiguous memory)
Dumpfile Pagelets: 521595 blocks
Dump Flags: olddump,writecomp,errlogcomp,dump_style
Dump Type: compressed,selective,dosd
EXE$GL_FLAGS: poolpging,init,bugdump,savedump
Paging Files: 5 Pagefiles and 1 Swapfile installed
Stack Pointers:
KSP = 00000000.6C588F40 ESP = 00000000.7FFA6000
SSP = 00000000.7FFAC100
USP = 00000000.6C437B30
General Registers:
R0 = 00000000.00000012 R1 = 00000000.000005B0 R2 = FFFFFFFF.BF66D3D0
R3 = 00000000.6C580012 R4 = FFFFFFFF.BE75A600 R5 = 00000000.00000024
R6 = 00000000.6C589724 R7 = 00000000.00000032 R8 = 00000000.6C589724
R9 = 00000000.6C589C60 R10 = 00000000.6C589724 R11 = 00000000.6C589968
R12 = 00000000.6C589A8C R13 = 00000000.6C58984C R14 = 00000000.6C589C9C
R15 = 00000000.6C589758 R16 = 00000000.000005B4 R17 = 00000000.00000001
R18 = 00000000.00000012 R19 = 00000000.00000000 R20 = 00000000.00000001
R21 = 00000000.6C580000 R22 = 00000000.00000012 R23 = FFFFFFFF.BE75A602
R24 = 00000000.00000012 AI = 00000000.FF000000 RA = FFFFFFFF.BF636B90
PV = FFFFFFFF.8D0AA3A0 R28 = FFFFFFFF.FFFFFE01 FP = 00000000.6C588F40
PC = FFFFFFFF.BF636BC0 PS = 00000000.00000000
---------------------
Images Affected: [SYS$LDR]F11BXQP.EXE
Problems Addressed in VMS721_F11X-V0100:
o An XQPERR bugcheck in LOCKERS can occur when the retry limit
on the F11B$x lock is reached.
This problem can occur when the owner of the $x lock is
running at a high process process priority and a number of
processes that are in a clustered system are also trying to
validate this lock, but at a lower process priority.
Image(s) Affected - [SYS$LDR]F11BXQP.EXE
o After releasing the current process's IPL/Fork lock, a
system can crash with an SPLACQERR bugcheck
Image(s) Affected - [SYS$LDR]F11BXQP.EXE
o A directory file becomes "corrupt" and DUMP/DIRECTORY
displays a block similar to the following:
Virtual block number 3574 (00000DF6), 512 (0200) bytes
0000 Directory Entry:
0000 Size: 508
0002 Version limit: 32767
0004 Type: 0 (FID)
0005 Name count: 24
0006 Name: COSLR1201_01_JUPICC2.LIS
001E Version: 7859 FID: (40993,5,0)
0026 Version: 7858 FID: (40990,1,0)
002E Version: 7857 FID: (40988,3,0)
...
01E6 Version: 7802 FID: (40455,1,0)
01EE Version: 7801 FID: (40454,1,0)
01F6 Version: 32767 FID: (16744447,65535,0)
01FE End of records (-1)
The directory shuffle code creates the above erroneous
directory entry for the following reasons:
1. So that a new directory buffer will have a valid
structure (this allows VALIDATE_DIRBLK to write
the block to disk); and
2. The entry will be spotted as incorrect (via VERIFY)
if the system crashes in the middle of this shuffle.
After the directory block (with the erroneous directory entry)
is written to disk, the bad entry is removed. A subsequent
call to READ_BLOCK assumes that the block comes from the
buffer cache and not from disk. Under heavy load, this
assumption may not be true as the directory block may have
been kicked out of the cache.
Image(s) Affected - [SYS$LDR]F11BXQP.EXE
o XQP DELETE code accepts an FCB (File Control Block) off the
limbo queue if not IO$V_DELETE. This prevents the
invalidation of VIOC cache blocks as the result of a RENAME
operation. This causes a large amount of XQP (FCB) and VIOC
(CFCB) non-paged pool usage as well as XQPERR bugchecks.
Image(s) Affected - [SYS$LDR]F11BXQP.EXE
o Under the following circumstances,
1. A directory with multiple headers (e.g., from a large ACL)
is deleted on one node (A) in a cluster; and
2. the directory had been previously accessed on another node
(B) in the cluster,
The files created with the previously deleted headers in step
1 would show up on node B with the error:
%SYSTEM-F-NOSUCHFILE, no such file.
Image(s) Affected - [SYS$LDR]F11BXQP.EXE
Problems Addressed in VMS721_FIBRE_SCSI-V0400:
o The DEC-AXPVMS-VMS721_FIBRE_SCSI-V0300--4.PCSI kit did not
include the SYS$PKADRIVER.EXE image. This image was shipped
with the superseded kit, DEC-AXPVMS-VMS721_FIBRE_SCSI-V0200--4.PCSI
and should have been carried forward and included in the
DEC-AXPVMS-VMS721_FIBRE_SCSI-V0300--4.PCSI kit.
Images Affected: [SYS$LDR]SYS$PKADRIVER.EXE
Problems Addressed in VMS721_FIBRE_SCSI-V0300:
o PKQ_WATCHDOG would lose timed out I/Os, which would cause
SHADDETINCON or SHADBOOTFAIL bugchecks or cause other system
hangs.
Images Affected: [SYS$LDR]SYS$PKQDRIVER.EXE
o A system can crash with an INCONSTATE bug check in
SYS$FGEDRIVER. See crashdump summary below:
Crashdump Summary Information:
------------------------------
Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL
Current Process: NULL
Current Image:
Failing PC: FFFFFFFF.803E3560 SYS$FGEDRIVER+03560
Failing PS: 08000000.00000804
Module: SYS$FGEDRIVER (Link Date/Time: 3-SEP-2000
01:20:59.17)
Offset: 00003560
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
o A system could crash with an INCONSTATE bugcheck during an
adapter reset.
Crashdump Summary Information:
------------------------------
Bugcheck Type: INCONSTATE, Inconsistent I/O data base
Current Image: CTM_HIGH_IO_ALPHA_32.EXE
Failing PC: FFFFFFFF.9B184B8C SYS$FGEDRIVER+0AB8C
Failing PS: 38000000.00000804
Module: SYS$FGEDRIVER (Link Date/Time: 19-AUG-2000
02:12:10.74)
Offset: 0000AB8C
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
o A system could crash with an INVEXCEPTN at
@FG$MAILBOX_ATTENTION_C+000A0.
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
o A system could crash with an INCONSTATE bug check in
SYS$FGEDRIVER while performing FibreChannel I/O.
Crashdump Summary Information:
------------------------------
Bugcheck Type: INCONSTATE, Inconsistent I/O data base
Current Process: NULL
Current Image:
Failing PC: FFFFFFFF.9B1187DC SYS$FGEDRIVER+087DC
Failing PS: 38000000.00000804
Module: SYS$FGEDRIVER Link Date/Time: 19-AUG-2000
02:12:10.74)
Offset: 000087DC
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
o Enable OpenVMS to recognize the ESL9198DLX (LVD) tape library.
In PK$NEGOIATE, which is called by PK$INIT_STDT, the
connection parameters were not being properly set, even though
PK$SEND_COMMAND used these parameters.
Images Affected: [SYS$LDR]PKWDRIVER.EXE
o Access to disks can be lost during a DRM failover.
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
o A system could crash with an INVEXCEPTN bugcheck in
@SYS$DKDRIVER+B534 just after issuing a MOUNT command to a
FibreChannel disk volume that has a 'Persistent reserved' set.
Crashdump Summary Information:
------------------------------
Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL
Current Process: NULL
Current Image:
Failing PC: FFFFFFFF.9999B534 SYS$DKDRIVER+0B534
Failing PS: 38000000.00000804
Module: SYS$DKDRIVER (Link Date/Time: 19-AUG-2000
01:53:24.81)
Offset: 0000B534
Images Affected: [SYS$LDR]SYS$DKDRIVER.EXE
[SYS$LDR]SYS$MKDRIVER.EXE
o Multipath failovers may cause "INVEXCEPTN, Exception while
above ASTDEL" system crashes.
Images Affected: [SYS$LDR]SYS$DKDRIVER.EXE
[SYS$LDR]SYS$MKDRIVER.EXE
o The system can crash with an INCONSTATE bugcheck in
SYS$PGADRIVER, if there is a change in the Fabric, such as
pulling a cable on the switch.
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
o A hang can occur during boot in STACONFIG after reporting a
driver is offline due to "Insufficient Non-paged Pool for
INIT."
Images Affected: [SYS$LDR]SYS$PKQDRIVER.EXE
o A system can crash with an INVEXCEPTN bugcheck during error
processing.
Images Affected: [SYS$LDR]SYS$DKDRIVER.EXE
Problems Addressed in VMS721_FIBRE_SCSI-V0200:
o The image generation for the SMI$OBJSHR.EXE image was
incorrect. This led to the new image not being installed on
the system.
Images Affected: [SYSLIB]SMI$OBJSHR.EXE
Problems Addressed in VMS721_FIBRE_SCSI-V0100:
o An error is not returned when an illegal density is specified.
Add the TLZ10 to the SCSI device table to ensure that accurate
density checking is performed.
Images Affected: [SYS$LDR]SYS$MKDRIVER.EXE
o When sending an inquiry command to a device on the SCSI bus,
if the phase transition timeout value is greater than 300
seconds, the SCSI class driver returns an SS$_BADPARAM error
condition and aborts the IO.
Images Affected: [SYSLDR]SYS$DKDRIVER.EXE
[SYSLDR]SYS$GKDRIVER.EXE
[SYSLDR]SYS$MKDRIVER.EXE
o A "cancelled" write can still be done, possibly corrupting
data.
Images Affected: [SYS$LDR]SYS$DKDRIVER.EXE
[SYS$LDR]SYS$PKCDRIVER.EXE
[SYS$LDR]SYS$PKEDRIVER.EXE
[SYS$LDR]SYS$PKJDRIVER.EXE
[SYS$LDR]SYS$PKQDRIVER.EXE
[SYS$LDR]SYS$PKSDRIVER.EXE
[SYS$LDR]SYS$PKTDRIVER.EXE
[SYS$LDR]SYS$PKWDRIVER.EXE
[SYS$LDR]SYS$PKZDRIVER.EXE
o The FibreChannel driver executes INCONSTATE bugchecks.
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
[SYS$LDR]FC$GLOBALS.STB
[SYSLIB]FC$SDA.EXE
o During the boot sequence, if ELS requests come in after
PGADRIVER has initiated the connect ULP$CONNECT sequence to
the lower layer, but before the connect sequence has
completed, an ACCVIO system crash may occur.
Images Affected: [SYS$LDR]SYS$PGADRIVER.EXE
o An INCONSTATE bugcheck occurs while booting.
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
o INCONSTATE or INVEXCEPTN bugchecks can occur at boot time.
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
o The SCSI port goes offline with a fatal CNTRLR error.
Images Affected: [SYS$LDR]SYS$PKQDRIVER.EXE
o Multiple errors occur when running the PKQDRIVER in the HSOF
distribution media. Re-installing a PKQDRIVER older version
of HSOF eliminates the problem(s).
Images Affected: [SYS$LDR]PKQDRIVER.EXE
o An unnecessary mount verification when HSZ Unit Attention
informational messages are received.
Images Affected: [SYS$LDR]SYS$DKDRIVER.EXE
o Excessive disk error counts.
Images Affected: [SYS$LDR]SYS$DKDRIVER.EXE
o The following problems are being corrected:
+ The erase page can be corrupted, causing an INCONSTATE
crash
+ Multiple alignment faults.
+ System can crash when running low on map registers
Images Affected: [SYS$LDR]SYS$PKQDRIVER.EXE
o During a boot, if the connection limit on the FibreChannel
storage unit (e.g., HSG80 has a limit of 64 entries) is reached,
the driver configuration will fail without any error message.
If the system is trying to boot from a FibreChannel disk on one
of these storage devices, the whole system will hang during the
boot.
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
[SYSMSG]SYSMSG.EXE
o The system may crash whenever MSCP multipath failover is used.
Images Affected: [SYS$LDR]DKDRIVER.EXE
[SYS$LDR]MKDRIVER.EXE
PROBLEMS ADDRESSED IN VMS721_FIBRECHAN-V0300 KIT
o A system may hang during boot time while trying to INIT the
FibreChannel adapter.
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
o Enable larger I/O transfer capacity for PGADRIVER.
Images Affected: [SYS$LDR]SYS$PKADRIVER.EXE
o On a large cluster that has many FibreChannel Adapters, a
system may hang at boot time when the FibreChannel driver is
being initialized.
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
o A system may crash on bootup with an INCONSTATE bugcheck at
SYS$FGEDRIVER+0829C.
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
o A cascaded fibre switch cable pull hangs the server node in a
non-functional state. If the system disk is accessed through
the hung link, the system itself will eventually hang.
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
[SYS$LDR]SYS$PKADRIVER.EXE
[SYS$LDR]FC$GLOBALS.STB
[SYSLIB]FC$SDA.EXE
o An INCONSTATE crash could occur at SYS$FGEDRIVER+8400 and/or
at SYS$PKADRIVER+0A208.
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
[SYS$LDR]SYS$PKADRIVER.EXE
[SYS$LDR]FC$GLOBALS.STB
[SYSLIB]FC$SDA.EXE
o A disk could hang on a Fibrechannel adapter. The FibreChannel
units are hung because the link through which they are
accessed is stuck in a non-functional state. If the system
disk is accessed through the stuck link, the system itself
will eventually hang.
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
[SYS$LDR]SYS$PKADRIVER.EXE
[SYS$LDR]FC$GLOBALS.STB
[SYSLIB]FC$SDA.EXE
o An INVEXCEPTN can occur at SYS$FGEDRIVER+0722.
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
[SYS$LDR]SYS$PKADRIVER.EXE
[SYS$LDR]FC$GLOBALS.STB
[SYSLIB]FC$SDA.EXE
o A rapid portDisable/portEnable of a fiber switch cascade
causes looping PLOGIs from HSG80. This is only seen when
there is some disruption to the FibreChannel link or when a
stream of portDisable/portEnable commands are issued to the
Brocade switch.
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
[SYS$LDR]SYS$PKADRIVER.EXE
[SYS$LDR]FC$GLOBALS.STB
[SYSLIB]FC$SDA.EXE
o A system crash occurs in SYS$FGEDRIVER at FG$FREE_UCTX.
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
[SYS$LDR]SYS$PKADRIVER.EXE
[SYS$LDR]FC$GLOBALS.STB
[SYSLIB]FC$SDA.EXE
o A CPUSPINWAIT crash can occur in SYSTEM_SYNCHRONIZATION_MIN.
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
[SYS$LDR]SYS$PKADRIVER.EXE
[SYS$LDR]FC$GLOBALS.STB
[SYSLIB]FC$SDA.EXE
o Requests hang leaving no room in the request ring to issue an
abort IOCB.
Images Affected: [SYS$LDR]SYS$PKADRIVER.EXE
[SYS$LDR]SYS$FGEDRIVER.EXE
[SYS$LDR]FC$GLOBALS.STB
[SYSEXE]FC$SDA.EXE
o An Emulex adapter delivered interrupts for a response ring
which had not been configured. This caused the driver to
reference a non-existent structure indexed by ring number and
resulted in an INVEXCEPTN/ACCVIO crash.
Images Affected: [SYS$LDR]SYS$PKADRIVER.EXE
[SYS$LDR]SYS$FGEDRIVER.EXE
[SYS$LDR]FC$GLOBALS.STB
[SYSEXE]FC$SDA.EXE
o Batch jobs hang when doing I/O to disk operations behind HSG80
cards.
Images Affected: [SYS$LDR]SYS$PKADRIVER.EXE
[SYS$LDR]SYS$FGEDRIVER.EXE
[SYS$LDR]FC$GLOBALS.STB
[SYSEXE]FC$SDA.EXE
o The HSG60 card and follow-on devices were not supported. As a
result, INVALID INQUIRY errors were logged. This fix adds the
necessary support.
Images Affected: [SYS$LDR]SYS$DKDRIVER.EXE
o Add support for the Emulex LP9000 adapter, the next generation
of the Emulex FibreChannel adapter. This adapter is 100%
backward compatible with the LP8000.
Images Affected: [SYS]SYS$CONFIG.DAT
Problems Addressed in the VMS721_FIBRECHAN-V0200 Kit:
o This change updates the configuration file to allow the LP8000
version of the KGPSA adapter to be recognized by OpenVMS.
Before this change, only the LP7000 is recognized.
Images Affected: [SYSEXE]SYS$CONFIG.DAT
o OpenVMS hangs if a system is booted with a loopback connector
in place on an Emulex LP7000 or LP8000 adapter
Images Affected:
- [SYS$LDR]SYS$PGADRIVER.EXE
- [SYS$LDR]SYS$FGEDRIVER.EXE
o It is possible for data corruption to occur when removing a
cable (or disabling a port) between switches in a fabric with
cascaded switches. Because the link which is disrupted has
fabric-wide scope, it is impossible to predict which hosts or
devices might see the corruption. The pattern of corruption
seen has usually been misplaced data, meaning that a portion
of the data for a given I/O request has appeared in the
correct buffer but at the wrong offset in that buffer
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
[SYS$LDR]SYS$PGADRIVER.EXE
[SYS$LDR]FC$GLOBALS.STB
[SYSLIB]FC$SDA.EXE
o When removing a cable (or disabling a port) between switches
in a fabric with cascaded switches, it is possible to hang a
system which is doing I/O to a device in the fabric. It is
actually individual I/O requests which get hung, the result of
the link not transitioning to the UP state correctly. This
can show up as the loss of one or more paths to a multi-path
device (depending on how many links/paths are affected). In
the worst case, all paths to a FibreChannel system disk will
be lost resulting in a system hang.
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
[SYS$LDR]SYS$PGADRIVER.EXE
[SYS$LDR]FC$GLOBALS.STB
[SYSLIB]FC$SDA.EXE
o A system may hang during FibreChannel configuration when a
KGPSA is connected to a Pleiades-II switch.
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
[SYS$LDR]SYS$PGADRIVER.EXE
[SYS$LDR]FC$GLOBALS.STB
[SYSLIB]FC$SDA.EXE
o When large I/O transfers are done under a heavy I/O load (e.g.,
running Backup or doing a shadow set copy), excessive Medium
Offline and Mount Verify messages are seen on a Turbolaser
system. Mount Verification is performed often enough to have
a serious impact on performance.
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
[SYS$LDR]SYS$PGADRIVER.EXE
[SYS$LDR]FC$GLOBALS.STB
[SYSLIB]FC$SDA.EXE
o It is possible to cause a DOUBLEDEALO crash on a system when
removing a cable (or disabling a port) between switches in a
fabric with cascaded switches. This crash can occur even if
the system is idle at the time. The crash will only happen if
a particular LP7000 or LP8000 sees more than 10 other ports on
the fabric. The number of ports an adapter sees can be
determined as follows:
- There is always one NULL port
- There are 2 ports on the switch to which the adapter is
directly connected
- There is one port for each multi-bus HSG80 port connected
to the same fabric (not necessarily the same switch)
- There is one port for each other FibreChannel adapter
connected to the same fabric, even if these other adapters
are in the same system.
This same probelm can also cause an invalid exception system
crash.
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
[SYS$LDR]SYS$PGADRIVER.EXE
[SYS$LDR]FC$GLOBALS.STB
[SYSLIB]FC$SDA.EXE
o An invalid exception system crash during boot can occur on a
system with an adapter which has failed initialization.
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
[SYS$LDR]SYS$PGADRIVER.EXE
[SYS$LDR]FC$GLOBALS.STB
[SYSLIB]FC$SDA.EXE
Problems Addressed in the VMS721_FIBRECHAN-V0100 Kit:
o A system hang may occur after a FibreChannel switch unit is
removed or a FibreChannel switch port is disabled.
The problem was caused by not restarting the driver's Queue
Manager after setting STDT state to SS$_MEDOFL.
o A single-CPU system may hang or a CPUSPINTWAIT crash (SMP)
may occur when a heavy I/O load is running to FibreChannel
devices.
o A single-CPU system hang and an SMP-system CPUSPINWAIT crash
may occur when a QUEUE FULL is seen while a target is paused and
the target times out.
o An INCONSTATE crash may occur after a FibreChannel link disruption
such as rebooting or power cycling the FibreChannel switch.
o An INCONSTATE bugcheck or corruption may occur, most often on
Turbolaser, but potentially on any FibreChannel transfer which
requires the use of map registers.
Black Hole and Erase Pattern pages are not being mapped into
the Direct DMA window properly, and are not being mapped with
map registers when necessary.
o Machine check crashes can occur while running FibreChannel
hardware.
The FibreChannel adapter CSRs need to be mapped into PCI
memory space instead of PCI I/O space.
o Under heavy load, FC disks enter mount verification, then exit
mount verification after a short delay. This can reduce
performance, and disrupt the desired path selection.
Multipath polling is done with an ordered SCSI command. This
unnecessarily requires the issuing node to single-stream its
I/O to the device, and for all outstanding I/O from other
nodes to complete before the polling I/O completes. This
causes commands to timeout. The solution is to use an
unordered SCSI command for multipath polling.
New Functionality Addressed in VMS721_GRAPHICS-V0400:
o PowerStorm 300/350 OpenVMS Graphics Support
This kit provides support for the PowerStorm 300/350 Graphics
adapter. Specific information about this support can be found
in the P300_350_README file. This file is available in the
following formats:
o Text : P300_350_README.TXT
o Acrobat Reader : P300_350_README.PDF
o HTML : P300_350_README.HTML
These files can be found in SYS$COMMON:[SYSHLP]
o New ELSA GLoria Synergy DDX image
A new device dependent X server image is provided to improve
performance on EV6 (21264) based platforms containing ELSA
Gloria Synergy graphics modules. A new procedure,
SYS$MANAGER:DECW$DEVICE_CONFIG_P2.COM, is executed automatically
during DECwindows startup. The new procedure will, on appropriate
platforms, define a logical name that will redirect the server to
use the new P2 device dependent X code, DECW$SERVER_DDX_P2.EXE.
DECW$SERVER_DDX_GZ.EXE will continue to be used on older platforms
containing ELSA GLoria Synergy graphics modules.
Image(s) Affected: [SYSLIB]DECW$SERVER_DDX_P2.EXE
Problems Addressed in VMS721_GRAPHICS-V0400:
o With PowerStorm 300/350 graphics adapter(s), XGetImage on
8-plane visuals returned incorrect image data if the specified
width was not a multiple of eight.
Images Affected: [SYSLIB]DECW$SERVER_DDX_GB.EXE
o On systems containing PowerStorm 300/350 graphics adapters,
under certain conditions of 3D-application load, the address
space of the DECwindows server would grow without limit,
eventually exhausting the supply of page table entries (PTEs)
resulting in a "not enough core" message being displayed.
Images Affected: [SYSLIB]DECW$SERVER_DIX.EXE
[SYSLIB]DECW$OPENGLPEERRI.EXE
o Failure to create a 3D rendering context (e.g., due to
resource exhaustion) is no longer a fatal server error with
PowerStorm 300/350 adapter(s).
Images Affected: [SYSLIB]DECW$OPENGLPEERRI.EXE
[SYSLIB]DECW$SERVER_DDX_GB.EXE
o PowerStorm 300/350 multi-head initialization problems on
systems running at 667 MHz or faster have been solved.
Images Affected: [SYS$LDR]SYS$GBDRIVER.EXE
o With PowerStorm 300/350 adapter(s), the Store Colors operation
on 8-plane PseudoColor windows could result in incorrect
colors if the array of color values did not denote a
consecutive range of pixel values.
Images Affected: [SYS$LDR]SYS$GBDRIVER.EXE
o The 1600 x 1200 @60 Hz video mode now works with PowerStorm
300/350 adapter(s).
Images Affected: [SYS$LDR]SYS$GBDRIVER.EXE
o Fast systems with PowerStorm 300/350 adapter(s) and large
memory (667 MHz and above) sometimes crash when graphics
operations are attempted while the system is already
handling a heavy load of non-graphics I/O.
Images Affected: [SYS$LDR]SYS$GBDRIVER.EXE
o A system crash due to a page fault with the IPL set too high
has been fixed in the PowerStorm 300/350 driver.
Images Affected: [SYS$LDR]SYS$GBDRIVER.EXE
o Xserver on Elsa Gloria Synergy crashes with the following
message in DECW$SERVER_0_ERROR.LOG:
Images Affected: [SYSLIB]DECW$SERVER_DDX_P2.EXE
o Clipped text was incorrectly displayed with ELSA Gloria
Synergy graphics modules. This occurred when scrolling
horizontally within a text box (e.g., using Netscape). When
enough text is typed into a text box to cause the field to
scroll to the left, the text is corrupted or not displayed.
Images Affected: [SYSLIB]DECW$SERVER_DDX_GZ.EXE
o A 3rd party middleware product called GMS has missing text on
the ELSA Gloria Synergy card.
Images Affected: [SYSLIB]DECW$SERVER_DDX_GZ.EXE
o An invalid exception ("INVEXCEPTN, Exception while above
ASTDEL") bugcheck will sometimes occur while booting with an
ELSA Gloria Synergy card installed.
Images Affected: [SYS$LDR]SYS$GZDRIVER.EXE
[SYS$LDR]SYS$GZVDRIVER.EXE
o During startup, DECwindows prints an error saying that
decw$fs-errors.log cannot be purged from SYS$SYSTEM.
Images Affected: [SYSMGR]DECW$STARTSERVER.COM
o A memory leak in the SYS$WSDRIVER (the pseudo display device
driver) has been fixed.
Images Affected: [SYS$LDR]SYS$WSDRIVER.EXE
o The server crashed when no TCP/IP license was available.
Images Affected: [SYSLIB]DECW$TRANSPORT_TCPIP.EXE
o Multiple network interfaces are now supported.
Images Affected: [SYSLIB]DECW$TRANSPORT_TCPIP.EXE
o The following font server problems have been fixed:
+ The X11 server crashed with %SYSTEM-F-ASTFLT if given an
unavailable Multiple network interfaces are now
supported.server node.
+ The X11 server would hang if the font server aborted or
restarted, or if there were significant network delays
enroute to/from the font server.
+ The X11 server crashed if a client with an active font
server request terminated.
+ Font server connection problems were not reported in the
X11 server log.
+ The font server sometimes stopped accepting connections.
+ The font server crashed when clients using DHCP made
requests.
+ Font server clients experienced problems if the font
server was idle for approximately ten minutes or longer.
+ The font server could not be restarted until five minutes
after it had terminated; it would report "address in use"
for the TCP/IP socket.
Images Affected: SYS$LIBRARY:DECW$SERVER_DIX.EXE
SYS$SYSTEM:DECW$XFS.EXE
SYS$SYSTEM:FSLSFONTS.EXE
SYS$SYSTEM:FSINFO.EXE
New Functionality Addressed in VMS721_P350-V0100:
o This kit provides software support for the Compaq PowerStorm
300/350 Graphics controller. Please see the Cover Letter or
Release Notes associated with this kit for complete installation
instructions for both the hardware and software.
Problems Addressed in VMS721_GRAPHICS-V0300:
o A reboot on a DPWS 5/500, 5/600 or 5/433 system with a
PowerStorm 4D10T card will crash. The system, must be shut
down, a console init done, and then booted.
Image(s) Affected: [SYS$LDR]SYS$GZDRIVER.EXE
[SYS$LDR]SYS$GZVDRIVER.EXE
o The PowerStorm 4D10T card displays video "noise". This noise
is most visible on certain backgrounds, such as the root weave
pattern that is drawn on secondary heads.
Image(s) Affected: [SYS$LDR]SYS$GZDRIVER.EXE
[SYS$LDR]SYS$GZVDRIVER.EXE
o When using a large window, the screen can become corrupted,
especially when moving large windows.
Image(s) Affected: [SYSLIB]DECW$SERVER_DDX_GZ.EXE
o When using text editing (DECW$NOTEPAD as an example), the
I-bar text cursor would corrupt text when moved with the
cursor keys.
Image(s) Affected: [SYSLIB]DECW$SERVER_DDX_GZ.EXE
o A number of problems have been reported on the TGA2:
1. The cursor would occasionally not display on any head
beyond the second screen when using 24-planes, and moving
the cursor between screens.
2. When switching screens, a stale cursor occasionally was
left behind on the last screen.
3. A warm restart after a halt or crash would bugcheck in
GYCDRIVER.
4. When switching screens quickly, the cursor would
occasionally be mis-positioned on the wrong screen.
5. DMA was not disabled for systems with > 1GB or when behind
a bridge.
Image(s) Affected: [SYS$LDR]SYS$GYCDRIVER.EXE
[SYS$LDR]SYS$INDRIVER.EXE
PROBLEMS ADDRESSED IN VMS721_IIDRIVER-V0100 KIT:
o The system can crash with an INVEXCEPTN bugcheck at
SYS$IIDRIVER+021A0.
Images Affected: [SYS$LDR]SYS$IIDRIVER.EXE
o The device error counter was eroneously incremented when
expected bus errors occurred.
Images Affected: [SYS$LDR]SYS$IIDRIVER.EXE
Problems Addressed in VMS721_IPC-V0100:
o IPC (inter-process communication) DISCONNECT does not fail
outstanding requests.
Images Affected: [SYS$LDR]SYS$IPC_SERVICES.EXE
o Massive non-paged pool corruption leads to various crashes and
hangs.
Images Affected: [SYS$LDR]SYS$IPC_SERVICES.EXE
o POOLCHECK bugchecks when a longword corruption contains zeroes.
Images Affected: [SYS$LDR]SYS$IPC_SERVICES.EXE
o Using a stale TLCB$L_TVCB field caused an ACCVIO system crash.
Images Affected: [SYS$LDR]SYS$IPC_SERVICES.EXE
o An ACCVIO crash occurred in SSRV$OpenAssociation.
Images Affected: [SYS$LDR]SYS$IPC_SERVICES.EXE
o CPUSPINWAIT crashes occur
Images Affected: [SYS$LDR]SYS$IPC_SERVICES.EXE
o An INCONSTATE crash occurs in SYSIPC$SUBS/ipc$$remove_lcb due
to a failed validity check.
Images Affected: [SYS$LDR]SYS$IPC_SERVICES.EXE
FUNCTIONALITY ADDRESSED IN VMS721_LAN-V0200 KIT
o The 3X-DAPBA-FA and the 3X-DAPCA-FA are PCI based ATM adapters for
Alpha-based systems that provide high performance PCI-to-ATM
capability. The 3X-DAPBA-FA adapter offers a 155 Mbps fiber
connection; the 3X-DAPCA-FA adapter offers a 622 Mbps fiber
connection.
The datalink drivers for these adapters function in a new OpenVMS
ATM environment. The new OpenVMS ATM environment is fully
compatible with the existing legacy ATM support and allows both ATM
environments to be configured on a single system. Additionally,
the LANCP management interface is the same for both ATM
environments. The following images/files support the new OpenVMS
ATM environment:
Images Affected: [SYS$LDR]SYS$LAN.EXE
[SYS$LDR]SYS$LAN_CSMACD.EXE
[SYS$LDR]SYS$LAN_ATM.EXE
[SYS$LDR]SYS$LAN_ATM4.EXE (new)
[SYS$LDR]SYS$$ELDRIVER4.EXE (new)
[SYS$LDR]SYS$$HWDRIVER4.EXE (new)
[SYSEXE]SYS$CONFIG.DAT
[SYSEXE]LANCP.EXE
[SYSEXE]LANACP.EXE
Adapter Requirements:
These adapters require a great deal of non-paged pool, and
therefore, care should be taken when configuring them. The
following restrictions apply to these adapters:
+ For each 3X-DAPBA-FA adapter, Compaq recommends increasing
the SYSGEN parameter NPAGEVIR by 3000000.
+ For each 3X-DAPCA-FA adapter, Compaq recommends increasing
NPAGEVIR by 6000000.
To perform the above chagnes, add the ADD_NPAG_VIR parameter to
MODPARAMS.DAT and then run AUTOGEN. For example, on a system
with two 3X-DAPBA-FAs and one 3X-DAPCA-FA, you would add the
following line to MODPARAMS.DAT:
ADD_NPAG_VIR = 12000000
Adapter Restrictions:
o The adapter cannot be located on a PCI bus that is located
behind a PCI-to-PCI bridge. Systems that have this
configuration are the following:
+ Digital Personal AlphaWorkstation 600
+ AlphaStation 1000A
+ COMPAQ Professional Workstation XP1000
+ AlphaServer 2000 and 2100
o Classical IP is not supported with these new adapters.
o SDA does not correctly identify these new ATM/FORE adapters.
They are identified as "unknown adapters." This will be fixed
in a subsequent support release.
For additional information about the 3X-DAPBA-FA PCI HE155 ATM and
3X-DAPCA-FA PCI HE622 ATM adapters, refer to the following URL:
http://www.digital.com/alphaserver/products.html
o Support has been added for unlimited chained transmit segments to
LAN drivers. Support for this functionality is a performance
enhancement for both IPv4 and IPv6.
Images Affected: [SYS$LDR]SYS$ERDRIVER.EXE
[SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
[SYS$LDR]SYS$FXDRIVER.EXE
[SYS$LDR]SYS$ESDRIVER.EXE
[SYS$LDR]SYS$HCDRIVER.EXE
[SYS$LDR]SYS$HWDRIVER.EXE
[SYS$LDR]SYS$FADRIVER.EXE
[SYS$LDR]SYS$FCDRIVER.EXE
[SYS$LDR]SYS$FRDRIVER.EXE
[SYS$LDR]SYS$EXDRIVER.EXE
[SYS$LDR]SYS$FWDRIVER.EXE
[SYS$LDR]SYS$EWDRIVER.EXE
Problems Addressed In VMS721_LAN-V0200:
o A system can experience multiple DEMFA hardware errors
resulting in loss of the network connection to that system.
Images Affected: [SYS$LDR]SYS$FXDRIVER.EXE
o A System can crash when an INVEXCEPTN bugcheck at
SYS$FRDRIVER+11F50 when attempting to use a LAN UCB (unit
control block) after it has been deassigned.
Images Affected: [SYS$LDR]SYS$LAN.EXE
[SYS$LDR]SYS$LAN_CSMACD.EXE
[SYS$LDR]SYS$LAN_FDDI.EXE
[SYS$LDR]SYS$LAN_ATM.EXE
[SYS$LDR]SYS$LAN_TR.EXE
o If the LANCP command SET DEV/MIN=n/MAX=n is used to set the
minimum and maximum receive buffers to the same value, the
DEGPA LAN driver ([SYS$LDR]SYS$EW1000A.EXE) may steadily lose
pool in 5k byte increments until pool is exhausted. This
generally results in a system crash.
Images Affected: [SYS$LDR]SYS$EW1000A.EXE
o After entering a STOP/IP/ISA1 command from within the TCPWare
management interface, a NETDLLERR crash occurs in LSB$L_XMTCNT
-1
Images Affected: [SYS$LDR]SYS$EZDRIVER.EXE
o A packet is delayed from processing in the DE500 receive ring.
The packet is completely done, but it does not get processed
until another packet is received. As a result, the connection
is dropped.
Images Affected: [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
[SYS$LDR]SYS$EWDRIVER.EXE
o APB translates WWIDs specified in BOOTED_DEV and DUMP_DEV to
determine the disk's unit number. APB does not perform this
function for WWID0.
Images Affected: [SYSEXE]APB.EXE
o During the processing of a recursive bugcheck, the DUMP_DEV
variable appears to have changed after being verified. The
change then re-directed the dump write from the correct DOSD
disk to the system disk.
Images Affected: [SYSEXE]APB.EXE
[SYSEXE]DEBUG_APB.EXE
o A 'Kernel stack not valid' bugcheck occurs during shutdown.
Images Affected: [SYS$LDR]SYS$EW1000A.EXE
o On some systems, the PCI FDDI adapter (the DEFPA) halts with a
fatal hardware error. When the driver attempts to restart the
DEFPA, the driver detects either a parity error being reported
by the DEFPA, or it detects a command failure, which prevents
the driver from getting the DEFPA restarted successfully.
Images Affected: [SYS$LDR]SYS$FWDRIVER.EXE
[SYS$LDR]SYS$FRDRIVER.EXE
[SYS$LDR]SYS$FADRIVER.EXE
o The LAN Device Characteristics block (LDC) contains the device
line speed, which applications may use to determine how fast
the device is running. The Token Ring driver sets the line
speed at 16, even if driver is set to 4 megabits. The change
enables the driver to set the speed in the LDC to 4 or 16
megabits, whenever a new speed is determined.
Images Affected: [SYS$LDR]SYS$IWDRIVER.EXE
[SYS$LDR]SYS$IRDRIVER.EXE
[SYS$LDR]SYS$ICDRIVER.EXE
o A multitude of data overruns causes very poor network
performance when running from a DE504 in ES40 to a DE602 in
GS160.
Images Affected: [SYS$LDR]SYS$EIDRIVER.EXE
o The system can crash when an interrupt occurs after
deallocating the buffer.
Images Affected: [SYS$LDR]SYS$LAN.EXE
[SYS$LDR]SYS$LAN_CSMACD.EXE
[SYS$LDR]SYS$LAN_FDDI.EXE
[SYS$LDR]SYS$LAN_TR.EXE
[SYS$LDR]SYS$LAN_ATM.EXE
[SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
[SYSEXE]LANCP.EXE
o CSMACD can crash when executing an NCL script.
Images Affected: [SYS$LDR]SYS$EWDRIVER.EXE
[SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
[SYS$LDR]SYS$EIDRIVER.EXE
[SYS$LDR]SYS$FWDRIVER.EXE
[SYS$LDR]SYS$FCDRIVER.EXE
[SYS$LDR]SYS$FRDRIVER.EXE
[SYS$LDR]SYS$FADRIVER.EXE
[SYS$LDR]SYS$EW1000A.EXE
[SYS$LDR]SYS$ELDRIVER.EXE
[SYSEXE]SYS$CONFIG.DAT
[SYSEXE]LANCP.EXE
o The LAN device line speeds are displayed incorrectly with
NISCACP.
Images Affected: [SYS$LDR]SYS$EWDRIVER.EXE
[SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
[SYS$LDR]SYS$EIDRIVER.EXE
[SYS$LDR]SYS$FWDRIVER.EXE
[SYS$LDR]SYS$FCDRIVER.EXE
[SYS$LDR]SYS$FRDRIVER.EXE
[SYS$LDR]SYS$FADRIVER.EXE
[SYS$LDR]SYS$EW1000A.EXE
[SYS$LDR]SYS$ELDRIVER.EXE
[SYSEXE]SYS$CONFIG.DAT
[SYSEXE]LANCP.EXE
o An INVEXCEPTN crash can occur in the SYS$EW1000A driver
following a SET HOST/LAT command.
Images Affected: [SYS$LDR]SYS$EWDRIVER.EXE
[SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
[SYS$LDR]SYS$EIDRIVER.EXE
[SYS$LDR]SYS$FWDRIVER.EXE
[SYS$LDR]SYS$FCDRIVER.EXE
[SYS$LDR]SYS$FRDRIVER.EXE
[SYS$LDR]SYS$FADRIVER.EXE
[SYS$LDR]SYS$EW1000A.EXE
[SYS$LDR]SYS$ELDRIVER.EXE
[SYSEXE]SYS$CONFIG.DAT
[SYSEXE]LANCP.EXE
o Increase the buffer_limit, from 100k to 500k, in the LANACP
startup command file to allow LANACP to start MOP on more LAN
devices without failure.
Images Affected: [SYS$STARTUP]LAN$STARTUP.COM
o The DE425 does not function on systems that do not have
mapping registers.
Images Affected: [SYS$LDR]SYS$ERDRIVER.EXE
PROBLEMS ADDRESSED IN VMS721_LAN-V0100 KIT
o Add support for XP1000 embedded Ethernet adapter.
Add support for the COMPAQ Professional Workstation XP1000
embedded Ethernet adapter.
The ADAPTER_NAME field in the COMPAQ Professional Workstation
XP1000 embedded Ethernet SROM is blank. Since, the boot and
runtime drivers are only aware of this field being blank for
the Digital Personal Workstation, these drivers will see the
COMPAQ Professional Workstation XP1000 as a Digital Personal
Workstation. The COMPAQ Professional Workstation XP1000 and
Digital Personal Workstation embedded Ethernets are not
programmed in the same way.
o Autonegotiation fails.
When the Tulip bootdriver determines that a 21143 chip is
present it checks the EEPROM to further identify the
controller type. If the EEPROM does not further identify the
controller, the driver checks if the system type is a Digital
Personal Workstation. If it is, the MAU type is determined
and the controller is programmed accordingly. The XP-1000
platform does not identify the controller in the EEPROM and is
not a Digital Personal Workstation so the bootdriver was
returning OFFLINE on a network boot.
Problems Addressed in VMS721_LIBRTL-V0100:
o A memory leak occurs when using LIB$FIND_FILE/LIB$FIND_FILE_END
with long file names (flags=LIB$M_FIL_LONG_NAMES).
Images Affected: [SYSLIB]LIBRTL.EXE
[SYSLIB]LIBRTL_INSTRUMENTED.EXE
o A synchonization failure occurs for multithread programs using
the DEC C RTL routine malloc and free with "long" pointers (P2
space heap routines). These DEC C RTL routines in turn use
the LIBRTL Routines LIB$VM_MALLOC_64 and LIB$VM_FREE_64.
Symptoms could be varied, including "%LIB-F-MEMALRFRE, memory
already free" errors.
For an application to see this problem it would have to have
the following characteristics:
1. Call the DEC C RTL routines malloc and free
2. Be multithreaded
3. Be compiled with the /POINTER_SIZE=LONG and
/REENTRANCY=MULTITHREAD switches
4. Be linked /THREADS_ENABLE=(MULTIPLE_KERNEL_THREADS,UPCALLS)
5. Run on a multiprocessor system with kernel threads
enabled.
Note that programs using the "normal" P0 heap routines are not
affected by this problem.
Images Affected: [SYSLIB]LIBRTL.EXE
[SYSLIB]LIBRTL_INSTRUMENTED.EXE
o The LIB$CREATE_DIR RTL routine is documented to accept 64 bit
parameters. However, passing a 64 bit descriptor to the
routine fails with a LIB$_INVSTRDES error or passing a 64 bit
address may result in an SS$_ACCVIO error.
Images Affected: [SYSLIB]LIBRTL.EXE
[SYSLIB]LIBRTL_INSTRUMENTED.EXE
o A program can fail with the following error:
%LIB-W-ILLRECTYP, illegal record type (nnn)
%TRACE-W-TRACEBACK, symbolic stack dump follows
followed by:
%SYSTEM-F-ACCVIO, access violation, reason mask=00,
virtual address=0000000000000008, PC=nnnnnnnnnnnnnnnn,
PS=0000001B
if the program:
1. Is created that is directly linked with a shareable image
2. Calls LIB$FIND_IMAGE_SYMBOL to find an entry point in the
same shareable image
3. The program is executed and the user creates a new version
of the shareable image while the program is executing
Images Affected: [SYSLIB]LIBRTL.EXE
[SYSLIB]LIBRTL_INSTRUMENTED.EXE
o LIB$FIND_IMAGE_SYMBOL fails to locate symbols for images whose
record attributes have been altered.
This has been seen with DCOM as follows:
$ mcr DCOM$COMREGEDT
%SYSTEM-F-ACCVIO, access violation, reason mask=00,
virtual address=0000000000000008, PC=0000000000B43348,
PS=0000001B
Improperly handled condition, image exit forced.
Signal arguments: Number = 0000000000000005
Name = 000000000000000C
0000000000000000
0000000000000008
0000000000B43348
000000000000001B
Images Affected: [SYSLIB]LIBRTL.EXE
[SYSLIB]LIBRTL_INSTRUMENTED.EXE
o LIB$FIND_IMAGE_SYMBOL fails for images on disks whose device
names are more than 13 characters - which generally means a 3
digit unit number.
Images Affected: [SYSLIB]LIBRTL.EXE
[SYSLIB]LIBRTL_INSTRUMENTED.EXE
o In the case of a $ PRINT [X]FOO.PRF,;-1 command, LIB$FIND_FILE
may fail to find the second file (;-1). This problem may be
seen with certain DCL commands, such as PRINT, and with user
application calls to LIB$FIND FILE when LIB$M_FIL_LONG_NAMES
and the "multiple" flags are set (bits 1 and 2 of the flags
argument).
Images Affected: [SYSLIB]LIBRTL.EXE
[SYSLIB]LIBRTL_INSTRUMENTED.EXE
o A failure to unwind properly occurs when a large amount of
stack space is being used. This could result in an improperly
handled condition error, or a bad stack notification, or other
error.
Images Affected: [SYSLIB]LIBRTL.EXE
[SYSLIB]LIBRTL_INSTRUMENTED.EXE
PROBLEMS ADDRESSED IN VMS721_LOADSS-V0100 KIT
o A call to $CREATE_USER_PROFILE can randomly return an
SS$_ACCVIO error for requests that do not pass a USERNAME
parameter.
Images Affected: [SYSLIB]SECURESHRP.EXE
o $PERSONA_CREATE requests for users with large numbers of
rights (greater than 124) would fail with a BADBLOADR error.
Images Affected: [SYSLIB]SECURESHR.EXE
PROBLEMS ADDRESSED IN VMS721_MANAGE-V0100 KIT
o The SYSMAN security profile is supposed to be identical on all
nodes in a cluster that uses the same security environment.
However, users have noticed that SYSMAN may use the
authorization privileges from the UAF (use authorization file)
instead of the locally set privileges on SOME nodes.
Images Affected: [SYSLIB]SMI$SHR.EXE
Problems Addressed In VMS721_MIME-V0100:
o The following problems were corrected in this MIME release:
1. Memory corruption occurred when using the OpenVMS MIME
utility, especially when repeatedly opening and closing
UUencoded files.
2. When composing a simple, single-part, MIME text message
(with no attachments), the READ command would display
properly until the file was saved, closed, and re-opened
for reading. Then. extra headers for a text attachment
would appear in the MIME header area, which resulted in an
error:
%MIME-E-OPNFILERR, 'error opening file'
3. When using MIME to compose messages, the resulting MIME
file did not have its MIME message boundary parameter
string properly quoted. The string is part of the
'Content-Type:' multipart-mixed header field.
Consequently, the message may not be read correctly.
4. An ANALYZE/RMS error would occur, if used on the zero
allocated block file created, but never written to, by
composing a MIME 'NEW' Message.
5. Attachments can be removed, but not saved, for READ only
messages. This behavior should not be allowed for READ
only messages.
6. An ACCVIO error can occur when MIME attempts to display
the VIEWER error message. This occurs when a MIME file is
opened for which no viewer exists.
7. Multiple memory leaks occur when repeatedly opening and
closing UUencoded files. This excessive use of memory
resources may not be readily apparent to the user.
8. Extraneous files can be left behind by MIME, if the user
performs a QUIT command, or after prompting and answering
'no' to a file save operation on EXIT.
9. The OPEN MIME command with the /NEW qualifier would fail,
which is redundant with the NEW command. This was
removed.
10. The MIME command OPEN would continue to parse for multiple
files (up to eight), if none were specified with the OPEN
command. The operation would usually fail with the
following errors:
%RMS-E-FNF, file not found
%MIME-W-NOMSGOPEN, No currently active message
11. Multiple error messages with the same error would be
returned, if the file which was attempted to be opened was
not found.
12. If one NEW MIME message that is writeable was closed, and
a NEW one specified, the old data file could display from
the previous edit session. MIME was not cleaning up files
during a close and not freeing memory.
13. File types (extensions), their Content-type/subtype and
their encoding scheme optionally defined in
MIME$FILETYPES.DAT file was not being read properly, nor
would it allow error recovery. Also, an error message may
not display when the file had errors.
14. Sometimes informational messages get overwritten when MIME
exits with the DCL prompt.
MIME HELP (MIME$HELP.HLB) and MIME commands (MIMECMD.CLD) were
updated to reflect the above changes.
Images Affected: [SYSEXE]MIME.EXE
[SYSHLP]MIME$HELP.HLB
Problems Addressed In VMS721_MOUNT96-V0200:
o Initialize VCB$L_BLOCKFACT to be at least 1, so that the XQP
does not incur 'divide by zero' and UNXSIGNAL bugchecks.
Images Affected: [SYSLIB]MOUNTSHR.EXE
[SYSEXE]VMOUNT.EXE
o When mounting a CD that was created from a disk that was
larger than the CD itself, a check that compares the volume
size, cluster factor and block count fails with a
%MOUNT-F-FILESTRUCT error.
Images Affected: [SYSLIB]MOUNTSHR.EXE
[SYSEXE]VMOUNT.EXE
Problems Addressed in VMS721_MOUNT96-V0100:
o The density of a tape is not initialized correctly, if no
density is supplied and compaction is disabled.
Images Affected: [SYSLIB]MOUNTSHR.EXE
[SYSEXE]VMOUNT.EXE
o Irregular errors have been reported from SYSINIT when trying
to MOUNT the system disk which can lead to a system crash.
All crashes have been seen only during STARTUP.
Images Affected: [SYSEXE]SYSINIT.EXE
o If a batch job issues a SPWAN/NOWAIT MOUNT command, and then
exits while the MOUNT is in operator assist wait, the result
is that the subprocess hangs in MOUNT in LEF and the main
process in RWAST waiting for the subprocess to exit.
Images Affected: [SYSLIB]MOUNTSHR.EXE
o When MOUNTing bound volume sets which are also shadow set
members, MOUNT-F-INCONSET and MOUNT-I-DOVOLSET occur on
certain devices.
Images Affected: [SYSLIB]MOUNTSHR.EXE
[SYSEXE]VMOUNT.EXE
o The /DENSITY qualifier is quietly ignored when used with some
tape devices. Many customers continue to use the /DENSITY
qualifier on tape drives that do not support any specific
density. Rather, they support various forms of compaction.
This has led to confusion about what the drive should or
should not be doing.
This change simply reports the SS$_IVDENS warning message if
/DENSITY was supplied and the device driver could not process
it correctly. Note that the MOUNT will continue and the
default compaction characteristics will be used.
Images Affected: [SYSLIB]MOUNTSHR.EXE
[SYSEXE]VMOUNT.EXE
PROBLEMS ADDRESSED IN VMS721_PTHREAD-V0300 KIT:
o Applications that disable ASTs (asynchronous system traps) may
hang.
Images Affected: [SYSLIB]PTHREAD$DBGSHR.EXE
[SYSLIB]PTHREAD$RTL.EXE
Problems Addressed in VMS721_PTHREAD-V0200:
o When a kernel thread is not needed, it will go idle within a
null thread. There are circumstances in which the thread
cannot be revived. As a result, the user threads would have
one less kernel thread to utilize for remaining work.
Images Affected: [SYSLIB]PTHREAD$RTL.EXE
[SYSLIB]PTHREAD$DBGSHR.EXE
o A request to wake an idle (hibernating) null thread can be
ignored. This can lead to an application hang, if the
application logic requires the kernel thread, on which the
null thread would have run, to execute prior to other parts of
the application.
Images Affected: [SYSLIB]PTHREAD$RTL.EXE
[SYSLIB]PTHREAD$DBGSHR.EXE
o A deadlock can occur when a thread running on one virtual
processor (VP) blocks while holding an internal lock associated
with a different VP.
Images Affected: [SYSLIB]PTHREAD$RTL.EXE
[SYSLIB]PTHREAD$DBGSHR.EXE
o Applications that do frequent, short-duration, timed waits may
affect overall performance.
Images Affected: [SYSLIB]PTHREAD$RTL.EXE
[SYSLIB]PTHREAD$DBGSHR.EXE
o On a system with more than 16 CPUs, a threaded image can crash
during initialization.
Images Affected: [SYSLIB]PTHREAD$RTL.EXE
[SYSLIB]PTHREAD$DBGSHR.EXE
Problems Addressed in VMS721_PTHREAD-V0100:
o A customer's application, when run with upcalls enabled, can die
with an ACCVIO. This is the result of a stack overflow while
running the application's exit handling routine.
o When a thread calls pthread_exit() the entire process is
incorrectly terminated by a %CMA-F-EXIT_THREAD error instead of
simply terminating the calling thread.
o Pagefault Completion Errors
Pagefault completions accumulate (as observed via the "pthread show
-u" command to SDA), with the corresponding waiting threads having
been, apparently, unblocked without consuming (i.e., freeing) the
completions. Also, sometimes threads are found waiting indefinitely
for completions (although this effect was never successfully reproduced
in-house), while other, mismatched completions remain pending.
o Reduced performance and/or process threads hang.
PROBLEMS ADDRESSED IN VMS721_QMAN-V0100 KIT
o The Queue Manager ACCVIOs following a $SUBMIT/USER command.
See partial error message below:
----------------------------------------------------------------
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
address=89A666CC, PC=88ABB2E7, PSL=0BC00004
----------------------------------------------------------------
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
address=83ADD7CC, PC
=83164AE7, PSL=0BC00004
%%%%%%%%%%% OPCOM 3-MAY-2000 10:39:53.18 %%%%%%%%%%%
Message from user JOB_CONTROL on AV7000
%JBC-E-QMANDEL, unexpected queue manager process termination
Images Affected: [SYSEXE]QMAN$QUEUE_MANAGER.EXE
o When an unprivileged user attempts to access a queue and is
denied access, the event is neither alarmed nor audited.
Images Affected: [SYSEXE]SUBMIT.EXE
o When submitting a job to a queue, there is an option to retain
the job in the batch queue for a specified time after its
completion. However, this SUBMIT/RETAIN=UNTIL command does
not function properly.
Images Affected: [SYSEXE]SUBMIT.EXE
o Batch jobs with no corresponding processes can exist on a
system.
Images Affected: [SYSEXE]JBC$JOB_CONTROL.EXE
Problems Addressed in VMS721_RMS-V0100:
o RMS: Put or update to an indexed file may ACCVIO.
A LDQ (load quad) instruction generated by the Bliss-64
compiler (default quadword alignment) may result in an attempt
being made to read or write 4 bytes beyond the end of an RMS
internal buffer which ends exactly on a page boundary with an
adjacent inaccessible page.
The process may either:
+ Terminate (if SYSGEN parameter BUGCHECKFATAL not enabled)
with an access violation (ACCVIO); or
+ Crash the system (if BUGCHECKFATAL enabled) with a
SSRVEXCEPT ACCVIO.
There are too many variables (for example, bucket size, number
of buffers, record location, number of keys) to predict in
advance that a file is vulnerable to this problem. However,
we do know that the right combination of conditions must be
rare since the problem has been dormant for several releases.
It was introduced with the conversion of several Bliss-32 RMS
modules to Bliss-64 as part of the support for 64-bit
addresses added to Alpha V7.0.
This fix is included in the next release after OpenVMS Alpha
V7.2-1H1.
o Mark the Buffer Descriptor as busy for asynch
multistreamed block IO autoextends.
Performing multistreamed asynchronous Block IO to a
sequential file could result in random data corruption
and/or sporadic SS$_BADPARAM errors if an autoextend
occurs.
This fix is included in the next release after OpenVMS
Alpha V7.2-1.
o Fix for potential application (or system) hang associated
with global buffer hashing interlock.
This kit includes fixes for two problems with the global
buffer hashing interlock implementation that have the
potential of blocking the progress of other processes and
thus inducing an application hang:
+ Close potential window when a process is deleted.
Expand the interlocked instruction for one bit to
include whole quadword so that modify of both
interlock and pid gets done as an atomic operation.
Otherwise, a process could be deleted after it had
set the interlock but before its pid had been
assigned, which could result in there being no way to
detect that an interlock was held by a nonexistent
process.
+ Vary the timer delay before each retry for a process
waiting for an interlock to be released. With
sufficient contention, it was found that the system
timer processing at IPL 8 could block progress for
the process currently holding the interlock when
expiration times were all restricted to 1 Msec.
This fix is included in the next release after OpenVMS
Alpha V7.2-1.
o Correct the resultant directory string size in NAML for
remote file specifications.
The size of the resultant directory string in a NAML
block structure was being set incorrectly when parsing
remote file specifications.
This fix is included in the next release after OpenVMS
Alpha V7.2-1.
o Correction for processes exiting with RMS IORNDN
non-fatal bugcheck.
Processes may disappear with RMS IORNDN non-fatal
bugchecks when an EXIT is requested by an Executive-mode
application (such as ACMS). This is a very small timing
window, so processes with a large number of files
increases the probability of the problem occurring.
If the SYSGEN parameter BUGCHECKFATAL is not enabled,
then the process will be terminated; if it is enabled,
then the system will crash with a RMSBUG (R2=FFFFFFF0,
IORNDN) bugcheck.
This fix is included in the next release after OpenVMS
Alpha V7.2-1.
o Fix RUF bugcheck when SS$_CURTIDCHANGE returned.
The system may crash with a RUF, Fatal error detected by
Recovery Unit Facility bugcheck. R0 in the crash has the
error code:
SDA> e/cond r0
SYSTEM-F-CURTIDCHANGE, already a change to the process
default transaction in progress
This fix is included in the next release after OpenVMS
Alpha V7.2-1.
o Support for SET RMS_DEFAULT /CONTENTION_POLICY to address
locking fairness issues.
The new Alpha global buffer read-mode lock support
introduced in V7.2-1H1 is functionally compatible with
both VAX and older Alpha releases. Operations in mixed
clusters produce correct results. However, there is a
locking fairness issue that may arise with mixed cluster
operations.
In a mixed cluster environment with very high contention
for specific buckets, it is possible for accesses to
write-shared files on nodes using read-mode bucket
locking to dominate access to a bucket. Nodes without
this support might be unable to access the bucket for a
protracted period of time.
It is also possible to observe comparable behavior on all
OpenVMS versions when dealing with accesses to
write-shared files without global buffers enabled -- even
on a standalone system. A similar fairness issue between
lock conversions and new lock requests may be observed in
which the new lock requests may remain ungranted for an
extended period of time.
This kit includes support in RMS for a new option to
improve fairness under high contention conditions for
write-shared files, but selecting this option may
noticeably increase locking overhead. The option may be
set at a process or system level. Since many
applications will never encounter this issue, the default
system behavior leaves this option disabled. A future
lock management enhancement should make this fairness
workaround unnecessary for later releases.
The option is controlled using the /CONTENTION_POLICY
qualifier to the DCL command SET RMS_DEFAULT. The
following are valid PROCESS keywords (/SYSTEM not
specified):
NEVER Never use the higher overhead option
to improve fairness for any write-shared
files accessed by this process; minimal
overhead.
SOMETIMES Use this option for fairer bucket
access (but higher overhead) to any
write-shared files with global buffers
enabled that are accessed by this
process.
ALWAYS Use this option for fairer bucket
access (but higher overhead) to all
write-shared files accessed by
this process.
SYSTEM_DEFAULT (Default) Use system setting. Note
that this keyword is disallowed with
/SYSTEM.
The following are valid SYSTEM keywords (/SYSTEM specified):
NEVER (Default) Never use the higher
overhead option to improve fairness
for any write-shared files accessed on
the system; minimal overhead.
SOMETIMES Use this option for fairer bucket
access (but higher overhead) to any
write-shared files with global
buffers enabled that are accessed
on the system.
ALWAYS Use this option for fairer bucket
access (but higher overhead) to all
write-shared files accessed on the
system.
In addition to the RMS image, modifications to the
following images are required:
- [SYSEXE]SET.EXE
- [SYSEXE]SHOW.EXE
- [SYSMSG]CLIUTLMSG.EXE
- replacement of modified SET.CLD in
[SYSLIB]DCLTABLES.EXE
These modified images are available in the
VMS721_CLIU-V0100 kit. The interface to this new
functionality is not available until this CLIUTL kit is
installed. Until the CLIUTL TIMA kit is available and
installed, the default of NEVER for the CONTENTION_POLICY
option cannot be overridden.
o Fix to prevent large cluster factor giving 63-block
bucket.
When running EDIT/FDL, the calculated bucket sizes are
always rounded up to the closest disk-cluster boundary,
with a maximum bucket size of 63. This can cause
problems when the disk-cluster size is large, but the
"natural" bucket size for the file is small, because the
bucket size is rounded up to a much larger value than
required. Larger bucket sizes increase record and bucket
lock contention, and can seriously impact performance.
This fix is included in the next release after OpenVMS
Alpha V7.2-1.
o Prevent callable CONVERT from producing ACCVIO on
repeated calls.
The CONVERT utility may return an access violation and/or
sort_on errors when it is repeatedly invoked from within
an application utilizing the callable interface.
Additionally, an invalid file structure may be created
when the callable interface is invoked repeatedly from
within an application.
This fix is included in the next release after OpenVMS
Alpha V7.2-1.
o Correction for CONVSHR SORT_ON and invalid alternate key
structures.
Three issues with the CONVERT utility have been
addressed:
+ Attempts to CONVERT a prologue 3 indexed file with
greater than 3 keys (key 3 and above) and with the
primary key being segmented with the segments not in
ascending order, results in invalid key structures
being generated for key 3 and above.
+ Using the callable interface to convert multiple
files, results in a SORT_ON error if any previous
file contains no records and has at least one
alternate key defined.
+ Using the /SECONDARY qualifier with values greater
than eight results in invalid alternate key
structures being generated.
This fix is included in the next release after OpenVMS
Alpha V7.2-1.
o Prevent ISI error on close from CONVERT/RECLAIM.
CONVERT/RECLAIM reports the following error during image
rundown:
"%RMS-F-ISI, invalid internal stream identifier (ISI) value"
This fix is included in the next release after OpenVMS
Alpha V7.2-1.
o Fix %CONVERT-I-SEQ errors converting sequential file.
Attempts to convert a sequential file to an indexed
format may report %CONVERT-I-SEQ errors despite convert's
invocation of the SORT utility. These errors may be
reported if any of the input file's records are shorter
than the primary key's highest segment.
This fix is included in the next release after OpenVMS
Alpha V7.2-1.
o Expand statistic display fields for Convert.
The record count and/or bucket counts displayed by the
statistics function and ^T function of Convert were
previously limited to 8 digits. This resulted in a field
of "*"s being displayed when greater than 8 digits were
required for displaying.
This fix is included in the next release after OpenVMS
Alpha V7.2-1.
o Prevent RMS-F-AID errors converting multiple input files.
Converting multiple indexed input files with different
area attributes can result in an RMS-F-AID, invalid area
ID.
This fix is included in the next release after OpenVMS
Alpha V7.2-1.
o Correct propagation of LRL value to output file.
The convert of a file could potentially leave the LRL
field for the output file as zero despite the value
existing for the input file. This is inconsistent with
previous versions of CONVERT. The LRL value is required
for some file organizations.
This fix is included in the next release after OpenVMS
Alpha V7.2-1.
PROBLEMS ADDRESSED IN VMS721_RPC-V0100 KIT
o The user is granted the option of setting the dump
logical - DCE$DUMP_DAEMONS. Based on the user's
preference, code in DCE$RPC_STARTUP.COM has been
suitably modified to include the dump facility.
Images Affected: [SYSMGR]DCE$RPC_STARTUP.COM
o Add a check for the logical DCE$MAX_USERS and modify
the RPCD daemon quotas accordingly.
Images Affected: [SYSMGR]DCE$RPC_STARTUP.COM
o DCE server processes such as DCE$SECD and DCE$CDSD,
as well as user written DCE servers sporadically
abort with SS$_ACCVIO when hit with a fast burst of
client request activity.
Images Affected: [SYSLIB]DCE$LIB_SHR.EXE
o The DCE$RPCD daemon generated thousands of error
messages and logged them into the DCE$RPCD.OUT file
as:
(rpc) *** FATAL ERROR (receive_dispatch) Unexpected exception
raised at CNRCVR.C;2\587 ***
(rpc) *** FATAL ERROR (rpc__cn_network_receiver) Unexpected
exception is raised at CNRCVR.C;2\398 ***
Images Affected: [SYSLIB]DCE$LIB_SHR.EXE
o A process using DCE RPC services aborts with a
bugcheck similar to the one below:
DECthreads bugcheck (version V3.15-262), terminating execution.
% Reason: mutex 0x00000000005DD868 :0 ref. overflow on lock
Images Affected: [SYSLIB]DCE$LIB_SHR.EXE
o A new logical has been defined to allow customers to
have the DCE daemon files produce process dumps.
The logical name DCE$DUMP_DAEMONS can be defined
prior to dce startup to add the /DUMP qualifier to
the daemon process. Process dumps can only be
reliably produced and read on Alpha V7.2-1 systems.
You must install special debugger kit ADB073 on your
V7.2-1 for the DCE dumps to be usable. Please
contact your Compaq support representative to a copy
of the ADB073 kit.
Images Affected: [SYSMGR]DCE$RPC_STARTUP.COM
[SYSMGR]DCE$SETUP.COM
PROBLEMS ADDRESSED IN VMS721_RTPAD-V0100 KIT:
o The system can crash with a KRNLSTAKNV bugcheck.
Images Affected: [SYS$LDR]SYS$CTDRIVER.EXE
o A bugcheck occurs in CTDRIVER during a cancel I/O process.
Images Affected: [SYS$LDR]SYS$CTDRIVER.EXE
Problems Addressed in VMS721_SHADOWING-V0500:
o Correction for DCL SHOW display errors.
After the VMS721_SHADOWING-V400 kit has been installed, a
user-mode ACCVIO or formatting display errors may occur with
various DCL SHOWs (e.g., SHOW DEVICE, SHOW MEMORY,SHOW
TERMINAL, SHOW WORK, SHOW NET).
Images Affected: [SYSMSG]CLIUTLMSG.EXE
Problems Addressed in VMS721_SHADOWING-V0400:
o The PCSI generation number on the SYS$SHDRIVER.EXE was missing
a digit, causing the image to not install over the previous
SYS$SHDRIVER.EXE image.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
New Functionality Included in the VMS721_SHADOWING-V0300 Kit:
o This kit contains new command features intended for use in
OpenVMS clusters that span multiple sites. An example of how
to apply the new commands will be found after they are
described.
+ DISMOUNT
1. /FORCE_REMOVAL ddcu:
If connectivity to a device has been lost and the
virtual unit is in mount verification, this switch
causes the member to be expelled immediately from the
shadow set. If you omit this qualifier, the device
is not dismounted until mount verification completes.
Note, that this qualifier cannot be used in conjunction
with the /POLICY=MINICOPY (=OPTIONAL) qualifier.
The device specified must be a member of a shadow set
that is mounted on this node.
+ SET DEVICE
1. /FORCE_REMOVAL ddcu:
If connectivity to a device has been lost and the
virtual unit is in mount verification, this qualifier
causes the member to be expelled from the shadow set
immediately.
If the shadow set is not currently in mount
verification, no immediate action is taken. If
connectivity to a device has been lost but the virtual
unit is not in mount verification, this qualifier lets
you flag the member to be expelled from the shadow
set, as soon as it does enter mount verification.
The device specified must be a member of a shadow set
that is mounted on this node.
2. /MEMBER_TIMEOUT=xxxxxx ddcu:
Specifies the time out value to be used for a member
of a shadow set.
The value supplied by this qualifier overrides the
SYSGEN parameter SHADOW_MBR_TMO for this specific
device. The value can be different for different
members of the same shadow set.
The valid range for xxxxxx is 1 to 16,777,215 seconds.
The device specified must be a member of a shadow set
that is mounted on this node.
3. /MVTIMEOUT=yyyyyy DSAnnnn:
Specifies the mount verification time out value to be
used for this virtual unit.
The value supplied by this qualifier overrides the
SYSGEN parameter MVTIMEOUT for this specific virtual
unit.
The valid range for yyyyyy is 1 to 16,777,215 seconds.
The device specified must be a virtual unit that is
mounted on this node.
4. /READ_COST=zzz ddcu:
The valid range for zzz is 1 to 4,294,967,295 units.
The device specified must be a member of a virtual
unit that is mounted on this node.
This qualifier allows you to modify the default 'cost'
assigned to each member of a virtual unit, so that
reads are biased or prioritized toward one member
versus another.
The shadowing driver assigns default READ_COST values
to shadow set members when each member is initially
mounted. The default value depends on the device
type, and its configuration relative to the system
mounting it. There are default values for a DECRAM
device; a directly connected device in same physical
location; a directly connected device in a remote
location; a DECram served device; and for other served
devices.
The value supplied by this qualifier overrides the
default assignment. The shadowing driver adds the
current queue depth of the shadow set member to the
READ_COST value and does the read operation to the
member with the lowest value.
Different systems in the cluster can assign different
costs to each shadow set member. Reads requested for
virtual units from a system at Site 1 are performed
from a member that is also at Site 1. Reads requested
for the same virtual unit from Site 2 can read from
the member located at Site 2.
If the /SITE command qualifier has been specified, the
shadowing driver will take site values into account,
when it assigns default READ_COST values. Note, that
to have the shadowing driver determine if a device is
in the category of "directly connected device in a
remote location," the /SITE command qualifier must be
have been applied to both the virtual unit and that
device.
5. /SITE={nnn, logical_name} {ddcu: DSAnnnn:}
Qualifier indicates to the shadowing driver the site
location of the shadow set member or of the virtual
unit. Prior to using this qualifier, you may define
the site location in the SYLOGICALS.COM command
procedure, to simplify its use.
The valid range for nnn is 1 through 255.
The following example shows the site locations defined,
followed by the use of the /SITE qualifier:
$ DEFINE/SYSTEM/EXEC ZKO 1
$ DEFINE/SYSTEM/EXEC LKG 2
$!
$! At the ZKO site ...
$ MOUNT/SYSTEM DSA0/SHAD=($1$DGA0:,$1$DGA1:) TEST
$ SET DEVICE/SITE=ZKO DSA0:
$!
$! At the LKG site ...
$ MOUNT/SYSTEM DSA0/SHAD=($1$DGA0,$1$DGA1) TEST
$ SET DEVICE/SITE=LKG DSA0:
$!
$! At both sites, the following would be used:
$ SET DEVICE/SITE=ZKO $1$DGA0:
$ SET DEVICE/SITE=LKG $1$DGA1:
6. /COPY_SOURCE {ddcu:,DSAnnnn:}
Controls whether one or both source members of a
virtual unit are used as the source for read data
during full copy operations, when a third member is
added to the virtual unit. This only affects copy
operations that do not use DCD operations.
HSG80 controllers have a read-ahead cache, which
significantly improves single disk read performance.
Copy operations, normally alternate reads from the two
source members, which effectively nullifies the
benefits of the read-ahead cache.
This qualifier lets you force all reads from a single
source member for the copy operation.
If the virtual unit is specified, then all reads for
full copy operations will be performed from whichever
disk is the current 'master' member, regardless of
physical location of the disk.
If a member of the virtual unit is specified, then
that member will be used as the source of all copy
operations. This allows you to choose a local source
member, rather than a remote master member.
7. /ABORT_VIRTUAL_UNIT DSAnnnn:
To use this qualifier, the virtual unit must be in
mount verification. When you specify this qualifier,
the virtual unit aborts mount verification immediately
on the node from which the qualifier is issued. This
qualifier is intended to abort mount verification when
it is known that the unit cannot be recovered. Note,
that after this command completes, that the virtual
unit must still be dismounted using the following
command:
DISMOUNT/ABORT DSAnnnn
o Use of the new DISMOUNT and SET command qualifiers.
The following diagram depicts a typical multi-site cluster
using fibre channel, and it will be used to illustrate what
steps need to be taken to manually recover one site, when the
site-to-site storage interconnect fails. Note that with
current Fibre Channel support, neither site can use the MSCP
server to regain a path to the DGA devices.
To prevent the shadowing driver from automatically recovering
virtual units, from connection-related failures, two steps
must be taken prior to any failure occurring:
1. Every device that is a member of a multi-site shadow set
must have its time out set to a very high value, using the
$ SET DEVICE /MEMBER_TIMEOUT= x ddcu: command. Use of
this command will override the SHADOW_MBR_TMO value, which
would normally be used for a shadow set member. A value
for x of 259200 would be a seventy-two hour wait time.
2. Every multi site virtual unit will also have to have its
mount verification time out raised to a high value, using
the $ SET DEVICE /MVTIMEOUT = y command. The "y" value
should always be greater than the "x" value. Use of this
command will override the MVTIMEOUT value, which would
normally be used for the virtual unit. A value for y of
259260 would be a seventy-three hour wait time.
3. Every virtual unit and every shadow set member must have a
site qualifier. As was noted above, doing so will ensure
that the read cost is correctly set. The other critical
factor in doing this involves three member shadow sets.
When they are being used, the site qualifier will ensure
that the master member of the shadow set will be properly
maintained.
In this example, DSA42 is made up of $1$DGA1000 and $1$DGA2000
<><><><><><><><><><><> LAN <><><><><><><><><><><>
Site A Site B
| |
F.C. SWITCH <><><><> XYZZY <><><><> F.C. SWITCH
| |
HSG80 <><> HSG80 HSG80 <><> HSG80
| |
$1$DGA1000 --------- DSA42 --------- $1$DGA2000
This diagram illustrates that systems at Site A or Site B have
direct access to all devices at both sites via Fibre Channel
connections. XYZZY is a theoretical point between the two
sites. If that point were to break, each site could access
different "local" members of DSA42 without error. For the
purpose of this example, Site A will be the sole site chosen
to retain access to the virtual unit. The following actions
must be taken, as shown, to recover the virtual unit at that
site.
On Site A:
$ DISMOUNT /FORCE_REMOVAL= $1$DGA2000:
Once that command has completed, the virtual unit will be
available for use at site A, only.
On Site B:
$ SET DEVICE /ABORT_VIRTUAL_UNIT DSA42:
Once the command completes, the virtual unit status will be
MntVerifyTimeout. Next, issue the following command to free
up the virtual unit:
$ DISMOUNT/ABORT DSA42:
These steps need to be taken for all affected multi-site
virtual units.
Problems Addressed in VMS721_SHADOWING-V0300:
o An INVEXCPETN crash occurs in SHIN$RESTORE_WLE_ENTRY when
a write completes to a multi-member shadowset.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o A SHADDETICON occurs after removing or adding a shadowset
member.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o The removal of the master member of a shadowset can cause
data corruption.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o The system crashes when SS$_VALNOTVALID errors occur in
MERGE_SIGNAL.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o SHOW LOGICAL returns a %LIB-F-INSVIRMEM error.
Images Affected: [SYS$LDR]SHOW.EXE
Problems Addressed in VMS721_SHADOWING-V0200:
o Multipath secondary UCBs cannot be shadow set members. The
multipath disk would be immediately removed from the shadow
set and an OPCOM message would be issued. Since MOUNT retries
this operation a number of times, even with /NOASSIST, the
failure would be repeated a number of times.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o Disabling a FibreChannel cascade connection corrupts a
shadowset member. When the cascade connection is broken, two
nodes can only see their local FC device. They enter
Mountverifaction. One node will throw out its remote member
and continue using the last member. The other node will then
throw out its remote member, i.e., the disk that has just been
used by the first node. This causes the first node to have
zero members and the second node continues with a member that
did not get the last set of writes.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o Disabling a FibreChannel cascade connection results in an
INVEXCPTN crash.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o The SHADOWSET goes MOUNTVERIFYTIMEOUT and cannot be remounted.
The process attempting the remount hangs.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o The Master Member SCB hangs until MVTIMEOUT expires.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
Problems Addressed in VMS721_SHADOWING-V0100:
o When a copy operation that interrupts a merge operation is
terminating, it finds that there are no members marked for the
merge and the thread crashes the system with a SHADDETINCON
bug check.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
[SYSEXE]SHADOW_SERVER.EXE
o SHOW DEVICES shows zero percent merged status although the
shadow set status does not indicate that a merge is required.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
[SYSEXE]SHADOW_SERVER.EXE
o Bit 16 in SHADOW_SYS_DISK can be set by the user to eliminate
using remote members of the shadowset for reads. Occasionally,
use of bit 16 fails to eliminate remote members from being used.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
[SYSEXE]SHADOW_SERVER.EXE
o A CPUSPINWAIT bug check can occur if the read of the SCB of
a shadow set member cannot pass the checksum test.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
[SYSEXE]SHADOW_SERVER.EXE
o DCD (Disk Copy Data) will not always be initiated properly.
During an assisted copy operation, if the source member was
dismounted or otherwise removed from the shadow set, the
connection to the controller would not clean up correctly.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
[SYSEXE]SHADOW_SERVER.EXE
o A full copy operation that is interrupted for a mini-merge
will not complete the full copy operation correctly.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
[SYSEXE]SHADOW_SERVER.EXE
o Typing incorrect commands results in a system crash.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
[SYSEXE]SHADOW_SERVER.EXE
o When two disks are added to a shadowset in the same mount
command, the copies are done sequentially instead of in
parallel. This causes the copies to take twice as long as
they should.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
[SYSEXE]SHADOW_SERVER.EXE
PROBLEMS ADDRESSED IN VMS721_SYS-V0900 KIT
o Revert back to the original OpenVMS soft affinity algorithm
because the new algorithm will not function properly on the
SCC hardware.
Images Affected: [SYS$LDR]PROCESS_MANAGEMENT.EXE
[SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
[SYS$LDR]SYS$BASE_IMAGE.EXE
[SYSEXE]SYSBOOT.EXE
[SYSEXE]SYSGEN.EXE
[SYSEXE]SYSMAN.EXE
[SYSEXE]SMISERVER.EXE
o A system could crash with a CPUSPINWAIT bugcheck waiting for
the POOL spinlock. This occurs when the primary CPU, which
holds the Pool spinlock, is executing the routine
EXE$TRIM_LISTS and a second CPU attempts to get the Pool
spinlock; the second CPU causes the crash when it times out.
Further, SHOW MEM/POOL/FULL will indicate that there are
thousands of blocks in the variable list.
This crash will happen only if either the SYSGEN parameter
NPAG_GENTLE or NPAG_AGGRESSIVE is set to a number smaller than
100 (the default case).
Images Affected: [SYS$LDR]SYSTEM_PRIMITIVES.EXE
[SYS$LDR]SYSTEM_PRIMITIVES_MON.EXE
o The effect of a SET SECURITY/OBJECT=DEVICE command can be
propagated to the wrong device(s) in a cluster for MK, DK, and
DG devices.
Images Affected: [SYSLIB]IOGEN$SHARE.EXE
[SYS$LDR]SYS$BASE_IMAGE.EXE
[SYS$LDR]IO_ROUTINES.EXE
[SYS$LDR]IO_ROUTINES_MON.EXE
o The system crashes with a DELCONPFN bugcheck in
MMG$DEL_CONTENTS_PFN8. The crash occurs during process
rundown. See highlights of the crash summary below:
Crashdump Summary Information:
------------------------------
Bugcheck Type: DELCONPFN, Fatal error in delete contents of
PFN
Current Process:
Current Image:
Failing PC: FFFFFFFF.80067764
MMG$DEL_CONTENTS_PFN_C+00204
Failing PS: 38000000.00000800
Module: SYSTEM_PRIMITIVES_MIN (Link Date/Time:
28-MAY-1999 23:29:3 2.00)
Offset: 00031764
Images Affected: [SYS$LDR]SYS$VM.EXE
o A system can crash with a KRNLSTACKNV bugcheck during heavy
I/O activity, such as BACKUP. Forcing the stack out shows
interaction between SYS$DKDRIVER and IO_ROUTINES filling up
the KPB stack, usually with some interrupt topping off the
stack.
Images Affected: [SYS$LDR]IO_ROUTINES.EXE
[SYS$LDR]IO_ROUTINES_MON.EXE
o The AST code for image rundown incorrectly deletes sKASTs when
searching the AST queues for AST addresses in the P0 and P2
space. The causes the system to hang in a LEF state because a
request sKAST is dismissed without execution.
Images Affected: [SYS$LDR]IMAGE_MANAGEMENT.EXE
o Disks with page or swap files installed do not get dismounted
during a system shutdown.
Images Affected: [SYSEXE]OPCCRASH.EXE
[SYS$LDR]IO_ROUTINES.EXE
[SYS$LDR]IO_ROUTINES_MON.EXE
[SYS$LDR]SYS$VM.EXE
o On Single CPU systems, the CPU runs two processes in the
current state, which results in an INCON_SCHED, 'Inconsistent
scheduling' bugcheck. See highlights from the dump summary
below:
Crashdump Summary Information:
Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL
Current Process: BROKER
Current Image: DSA360:[BROKER_U.AXP.][P]
BROKER_EDITOR_U.EXE;85
Failing PC: FFFFFFFF.800C3B98 SCH$QEND_C+00038
Failing PS: 10000000.00000704
Module: PROCESS_MANAGEMENT (Link Date/Time:
29-DEC-1999 04:09:20.9
Offset: 00007B98
Images Affected: [SYS$LDR]SYS$VM.EXE
o An INVEXCEPTN bugcheck occurs at SCH$QEND_C+38 while getting
the address of the process alignment fault reporting
information, CTL$GL_REPORT_USER_FAULTS. See highlights from
the Crashdump summary information below:
Crashdump Summary Information:
Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL
Current Process: BROKER
Current Image: DSA360:[BROKER_U.AXP.][P]BROKER_EDITOR_U.EXE;85
Failing PC: FFFFFFFF.800C3B98 SCH$QEND_C+00038
Failing PS: 10000000.00000704
Module: PROCESS_MANAGEMENT (Link Date/Time: 29-DEC-1999
Images Affected: [SYS$LDR]SYS$VM.EXE
o A multi-threaded process hangs with all threads suspended
except one that is spinning in a loop using CPU time.
Images Affected: [SYSLIB]SYS$SSISHR.EXE
Problems Addressed in VMS721_SYS-V0800:
o In the VMS721_SYS-V0700 kit, the SDA$SHARE image was placed in
the [SYSEXE] directory. It should be placed in the [SYSLIB]
directory.
Images Affected: [SYSLIB]SDA$SHARE.EXE
Problems Addressed in VMS721_SYS-V0700:
o The system can crash with an INCONSTATE bugcheck in CACHE$MOUNT.
This occurs when a process, usually RAID$SERVER, is attempting to
mount a disk, usually a member of a Raid set. It appears as if
the volume is being mounted twice and the INCONSTATE bugcheck
occurs.
Images Affected: [SYS$LDR]SYS$VCC.EXE
o An INCONSTATE bugcheck can occur during a RAID unbind operation.
Images Affected: [SYS$LDR]SYS$VCC.EXE
o A BLKASTCNT crash occurred with Pathworks enqueuing many
locks, all with blocking ASTs (asynchronous system traps).
The crash occurred when one of the locks was dequeued.
Images Affected: [SYS$LDR]LOCKING.EXE
o The code to verify that a page can be deleted from a process'
virtual address space was too restrictive. If a page had an
elevated reference count, and the process had direct I/O
out-tanding, VMS would not allow deletion of the page. This
could occur in the following instances:
- If the reference count is only 1 (2 for an active global
page).
- If the page is a buffer object page.
- If the page does not belong to a buffer object for the
process.
- If the page is owned by a privileged mode (exec or kernel)
and can only be accessed from privileged mode.
RMS is now using "system buffer objects" for files with global
buffers. This causes RMS to hang when it attempts to close
such a file if the process has direct I/O outstanding. Some
processes, like MULTINET can have direct I/Os and can be
outstanding for a long time.
This ECO enables the deletion of a page from a process'
virtual address space even though the page reference count is
elevated.
Images Affected:
- [SYS$LDR]SYS$VM.EXE
- [SYS$LDR]SYS$VM.STB
o Restructure $GETJPI inter-process PSB references.
+ a $SHOW SYSTEM/FULL" command displays the UIC of all
processes (except interactive process) as [0,0]. $GETJPI
shows the correct UIC's except swapper.
+ A system can crash with a SSRVEXCEPT bugcheck in module
PROCESS_MANAGEMENT_MON (SYSTEM_CHECK=1) at offset 0000F4B4.
Images Affected:
- [SYS$LDR]PROCESS_MANAGEMENT.EXE
- [SYS$LDR]PROCESS_MANAGEMEN_MON.EXE
Problems Addressed in VMS721_SYS-V0600:
o A System can crash with a KRNLSTAKNV, 'Kernel stack not
valid', error.
Images Affected:
- [SYS$LDR]PROCESS_MANAGEMENT.EXE
- [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
o Unnecessary and unwanted path switches can occur on multipath
devices. Under certain circumstances, if a user executes a
manual path switch of one member of a shadow set, the
requested path switch takes place. However, the other
member(s) of the shadow set switch paths as well. Further, if
the user attempts to switch the other member(s) back, the
other memebers will switch, but the originally switched member
will then switch back to the unwanted path.
Another symptom of this problem is that a transient error
condition on a multipath device can cause a path switch, even
though the current path is still valid.
This problem can occur if a multipath disk device is
simultaneously online, i.e., connected, on more than one path.
This configuration is created:
+ If two Fibre Channel cables are attached to the two host
FibreChannel ports on an HSG80 controller.
+ If two or more FibreChannel host bus adapters on the same
OpenVMS host system connect to the same fabric, i.e., the
same FibreChannel switch or into a set of cascaded
switches.
+ If two parallel SCSI buses are connected to the two host
ports on an HSZ80 controller.
Images Affected: [SYS$LDR]MULTIPATH_MON.EXE
o A cross process $GETJPI request for security profile (persona)
information, which includes network privileges and rights, can
lead to a SSRVEXCEPT system crash. See crashdump summary
below:
===================CRASH DUMP INFORMATION=====================
XENON1>
**** OpenVMS (TM) Alpha Operating System X6ZG-FT1 - BUGCHECK ****
** Bugcheck code = 000003C4: SSRVEXCEPT, Unexpected system service exception
** Crash CPU: 00 Primary CPU: 00 Active CPUs: 00000003
** Current Process = NETACP
** Current PSB ID = 00000001
** Image Name = $2$DKA100:[SYS0.SYSCOMMON.][SYSEXE]NETACP.EXE;1
**** Starting compressed selective memory dump at 20-MAR-2000 15:39...
.................................................................
...Complete ****
halted CPU 0
halt code = 5
HALT instruction executed
PC = ffffffff800acae4
Crashdump Summary Information:
------------------------------
Crash Time: 20-MAR-2000 15:39:49.18
Bugcheck Type: SSRVEXCEPT, Unexpected system service exception
Node: XENON1 (Cluster)
CPU Type: COMPAQ AlphaServer DS20E 500 MHz
VMS Version: X6ZG-FT1
Current Process: NETACP
Current Image: $2$DKA100:[SYS0.SYSCOMMON.][SYSEXE]NETACP.EXE;1
Failing PC: FFFFFFFF.8011657C EXE_STD$CHECK_IMAGE_NAME_C+0033C
Failing PS: 00000000.00000000
Module: PROCESS_MANAGEMENT_MON(Link Date/Time: 13-MAR-2000 13:54:01.61)
Offset: 0001057C
Boot Time: 17-MAR-2000 12:28:35.00
System Uptime: 3 03:11:14.18
Crash/Primary CPU:00/00
System/CPU Type: 2208
Saved Processes: 29
Pagesize: 8 KByte (8192 bytes)
Physical Memory: 512 MByte (65536 PFNs, contiguous memory)
Dumpfile Pagelets:105419 blocks
Dump Flags: olddump,writecomp,errlogcomp,dump_style
Dump Type: compressed,selective,shared_mem
EXE$GL_FLAGS: poolpging,init,bugdump
Paging Files: 1 Pagefile and 0 Swapfiles installed
Images Affected:
- [SYS$LDR]PROCESS_MANAGEMENT.EXE
- [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
o A REPLY/USER= and/or SUBMIT/NOTIFY command crashes the system
with a SSRVEXCEPT in the cluster system process (CSP). See
the crashdump summary below:
Crashdump Summary Information:
------------------------------
Crash Time: 17-APR-2000 11:15:38.40
Bugcheck Type: SSRVEXCEPT, Unexpected system service exception
Node: COBRA3 (Cluster)
CPU Type: DEC 4000 Model 620
VMS Version: X706-FT1
Current Process: CLUSTER_SERVER
Current Image: DSA2:[SYS0.SYSCOMMON.][SYSEXE]CSP.EXE;2
Failing PC: FFFFFFFF.80137920 CHECKITEM_C+00AC0
Failing PS: 0C000000.00000200
Module: PROCESS_MANAGEMENT_MON (Link Date/Time:
9-APR-2000 04:37:48.31)
Offset: 00037920
********************************************
Images Affected:
- [SYS$LDR]IO_ROUTINES.EXE
- [SYS$LDR]IO_ROUTINES_MON.EXE
o A non-privileged user can access jobs in a batch queue,
regardless of the queue protections. See the comparative
examples below:
$ show queue/full/all unhf_sys$batch ! from privileged account
Batch queue UNHF_SYS$BATCH, idle, on UNHF::
/BASE_PRIORITY=3 /CPUMAXIMUM=00:30:00 /JOB_LIMIT=3/OWNER=[SYSTEM]
/PROTECTION=(S:M,O:D,G,W:RS) /WSEXTENT=32768 /WSQUOTA=16384
(IDENTIFIER=[SIS_DEVEL,BANNER_SCT],ACCESS=READ+SUBMIT+MANAGE)
Entry Jobname Username Status
----- ------- -------- ------
2719 DUMMY B_JOHNSTONE Holding
Submitted 1-APR-2000 09:16:27.00 /KEEP
/LOG=$1$DUA233:[B_JOHNSTONE].LOG; /NOTIFY /NOPRINT/PRIORITY=100
/RESTART=UNHF_SYS$BATCH
File: _$1$DUA321:[B_JOHNSTONE.COM]DUMMY.COM;10
3182 DUMMY B_JOHNSTONE Holding
Submitted 1-APR-2000 14:15:28.41 /KEEP
/LOG=$1$DUA233:[B_JOHNSTONE].LOG; /NOPRINT /PRIORITY=100
/RESTART=UNHF_SYS$BATCH
File: _$1$DUA321:[B_JOHNSTONE.COM]DUMMY.COM;10
$show queue/full/all unhf_sys$batch !from non-privileged account
Batch queue UNHF_SYS$BATCH, idle, on UNHF::
/BASE_PRIORITY=3 /CPUMAXIMUM=00:30:00 /JOB_LIMIT=3/OWNER=[SYSTEM]
/PROTECTION=(S:M,O:D,G,W:RS) /WSEXTENT=32768 /WSQUOTA=16384
(IDENTIFIER=[SIS_DEVEL,BANNER_SCT],ACCESS=READ+SUBMIT+MANAGE)
Entry Jobname Username Status
----- ------- -------- ------
2719 no privilege Holding
3182 DUMMY B_JOHNSTONE Holding
Submitted 1-APR-2000 14:15:28.41 /KEEP
/LOG=$1$DUA233:[B_JOHNSTONE].LOG; /NOPRINT /PRIORITY=100
/RESTART=UNHF_SYS$BATCH
File: _$1$DUA321:[B_JOHNSTONE.COM]DUMMY.COM;10
$
In this example, the user can see entry 3182, as well as
security information, but cannot see entry 2719.
This also generates the following security alarm:
%%%%%%%%%%% OPCOM 1-APR-2000 15:38:36.66 %%%%%%%%%%%
(from node UNHA at 1-APR-2000 15:38:36.67)
Message from user AUDIT$SERVER on UNHA
Security alarm (SECURITY) on UNHA, system id: 1028
Auditable event: Object access
Event time: 1-APR-2000 15:38:36.65
PID: 2040C464
Source PID: 21012416
Username: R_KENNEY$
Process owner: [R_KENNEY$]
Object class name: QUEUE
Object name: UNHF_SYS$BATCH
Object owner: [0,0]
Object protection: SYSTEM:M, OWNER:D, GROUP:, WORLD:RS
Access requested: READ
Status: %SYSTEM-F-NOPRIV, insufficient privilege or
object protection violation
Images Affected:
- [SYS$LDR]SECURITY.EXE
- [SYS$LDR]SECURITY_MON.EXE
o A batch process can abort with SS$_IVCHNLSEC during image
activation. The batch process aborts with the following
error:
%RDB-E-UNAVAILABLE, Oracle Rdb is not available on yoursystem
-RDB-I-TEXT, Error activating image DSA0:[SYS1.SYSCOMMON.][SYSLIB]
RDMPRV.EXE, Invalid channel for create and map section
Images Affected: [SYS$LDR]SYS$VM.EXE
o A problem with the $TRNLNM code path for INTERLOCKED
translations can cause the service to exit without releasing
the logical name mutex. If the $TRNLNM request or any
subsequent kernel mode system service request made by that
process exits with an error status, the system will crash with
a MTXCNTNZ bugcheck.
If no kernel mode system service request made by that process
exits with an error status, the system will eventually hang,
with some processes in MUTEX wait trying to acquire the
logical name mutex. If some of those processes have already
acquired other mutexes, such as the I/O database mutex and
GSD mutex, there may be other processes in MUTEX wait trying
to acquire those mutexes.
The $TRNLNM bug is exercised by a fairly unusual combination
of circumstances and is more likely to be seen on an SMP system.
Images Affected: [SYS$LDR]LOGICAL_NAMES.EXE
o If a dump is being written to a DOSD disk and a recursive
bugcheck occurs during the processing of a recursive bugcheck,
the dump_dev variable is changed after being verified. The
change redirected the dump write from the correct DOSD disk to
the system disk.
(OUTPUT FROM CONSOLE)
**** MASTER MEMBER UNIT NUMBER OF SYSTEM DISK SHADOW SET IS 502
**** SEARCHING DEVICES LISTED IN DUMP_DEV FOR A VALID DUMP FILE
CHECKING ENTRY #01 IN DUMP_DEV...
%%%% MSCP 1 2 0 13 219 EF00 6601095, DUD219.13.0.2.1
...DUMP_DEV ENTRY #01 IS A VALID DUMP DEVICE
%%%% MSCP 0 2 0 10 502 EF00 6601095 DU 4200100AF138 HSL10B, DUA502.10.0.2.0
**** ACCESSING SYSTEM DISK VIA ORIGINAL BOOT PATH
Note the change in the mass storage control protocol (MSCP)
unit.
Images Affected:
- [SYSEXE]APB.EXE
- [SYSEXE]DEBUG_APB.EXE
- [SYS$LDR]EXCEPTION.EXE
- [SYS$LDR]EXCEPTION_MON.EXE
o Make system buffer objects available for Record Management
Services (RMS) locking and make MAXBOBxxx parameters obsolete.
Images Affected:
- [SYS$LDR]SYS$VM.EXE
- [SYS$LDR]SYS$BASE_IMAGE.EXE
o Executing POSIX on OpenVMS V7.2 or later will crash the
system.
Images Affected:
- [SYS$LDR]PROCESS_MANAGEMENT.EXE
- [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
o The following remote signal handling problems are fixed:
+ A process exits with a supervisor mode ACCVIO at PC =
EXE$REFLECT_C+A30.
+ A program can exit unexpectedly.
+ An ACCVIO occurs at EXE$POWERAST_C+F8 when a program is
calling kill() or $sigprc() to signal another process.
Images Affected:
- [SYS$LDR]EXCEPTION.EXE
- [SYS$LDR]EXCEPTION_MON.EXE
- [SYS$LDR]PROCESS_MANAGENMENT.EXE
- [SYS$LDR]PROCESS_MANAGENMENT_MON.EXE
- [SYS$LDR]IMAGE_MANAGEMENT.EXE
o The incorrect value is calculated in the IEEE handler's e_mult
and e_divt routines. See examples of the failing test results
below:
******** Test fp_mul_s ********
d1 = 2.350989e-38 (0xffffff)
d2 = 5.000000e-01 (0x3f000000)
intermediate result = 1.175494e-38 (0x800000)
result = -1.175494e-38 (0x80800000)
expected result = -0.0 or 0.0
d1 = 2.350989e-38 (0xffffff)
d2 = -5.000000e-01 (0xbf000000)
intermediate result = -1.175494e-38 (0x80800000)
result = 1.175494e-38 (0x800000)
expected result = 0.0
******** Test fp_div_s ********
d1 = 2.350989e-38 (0xffffff)
d2 = 2.000000e+00 (0x40000000)
intermediate result = 1.175494e-38 (0x800000)
result = -1.175494e-38 (0x80800000)
expected result = -0.0 or 0.0
Images Affected: [SYS$LDR]EXCEPTION.EXE
o Batch jobs take longer to process and hang in the local event
flag (LEF) state. AUTOGEN recommends using a higher value for
LNM%HASHTBL, which has previously been constrained by a
maximum value of 8192.
Images Affected:
- [SYSEXE]SYSBOOT.EXE
- [SYSEXE]SYSGEN.EXE
- [SYSEXE]SYSMAN.EXE
Problems Addressed in VMS721_SYS-0500:
o Provides support for the LP9000 adapter, the next generation
of the Emulex FibreChannel adapter.
Images Affected: [SYSEXE]SYS$CONFIG.DAT
o If a subprocess exists with a different security profile, a
call to $DELPRC could stall, leaving the process in RWAST
state.
Images Affected: [SYS$LDR]PROCESS_MANAGEMENT.EXE
[SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
[SYS$LDR]PROCESS_MANAGEMENT.STB
[SYS$LDR]PROCESS_MANAGEMENT_MON.STB
o After the installation of the VMS72_SYS-V0200 remedial kit,
the SET RIGHTS/DISABLE/PROCESS command will not remove the
specified right from the process rightslist.
Images Affected: [SYS$LDR]SECURITY.EXE
[SYS$LDR]SECURITY_MON.EXE
[SYS$LDR]SECURITY.STB
[SYS$LDR]SECURITY_MON.STB
o The system would crash with an ACCVIO in the exception
handling code because a register was not being restored
properly.
Images Affected: [SYS$LDR]EXCEPTION.EXE
[SYS$LDR]EXCEPTION_MON.EXE
[SYS$LDR]EXCEPTION.STB
[SYS$LDR]EXCEPTION_MON.STB
o After upgrading from V7.1 or V7.1-2 to V7.2 or V7.2-1, some
processes may periodically hang in HIBernation state, when
they should be awaken.
Images Affected: [SYS$LDR]SECURITY.EXE
[SYS$LDR]SECURITY.STB
o Attempting to read from EXEC mode results in an ACCVIO and the
deletion of the user's process.
Images Affected: [SYS$LDR]LOCKING.EXE
[SYS$LDR]LOCKING.STB
o A file sent to a spooled device could cause the system to
crash with a system service exception (SSRVEXCPT). This
problem only occurs when SYSTEM_CHECK is set to 1, which
causes the IO_ROUTINES_MON.EXE image to be used. This would
not occur, if the device was not spooled.
Images Affected: [SYS$LDR]IO_ROUTINES.EXE
[SYS$LDR]IO_ROUTINES_MON.EXE
[SYS$LDR]IO_ROUTINES.STB
[SYS$LDR]IO_ROUTINES_MON.STB
o A below normal value rounds up to an in-range value in the
ADDT, SUBT, and DIVT routines.
Images Affected: [SYS]EXCEPTION.EXE
[SYS]EXCEPTION_MON.EXE
[SYS]EXCEPTION.STB
[SYS]EXCEPTION_MON.STB
o Preserve the sign value, if the result from running an ADDT,
SUBT or DIVI routine is a denormal value rather than a zero
value, where the sign is always set to positive.
Images Affected: [SYS$LDR]EXCEPTION.EXE
[SYS$LDR]EXCEPTION_MON.EXE
[SYS$LDR]EXCEPTION.STB
[SYS$LDR]EXCEPTION_MON.STB
o As a result, I/O monitoring tools, such as MONITOR_DISK/ITEM=QUEUE_LENGT,
would report erroneous and increasing values for some multipath devices,
even when there was actually no active I/O on the device.
Images Affected: [SYS$LDR]IO_ROUTINES.EXE
[SYS$LDR]IO_ROUTINES[_MON].EXE
[SYS$LDR]MULTIPATH.EXE
[SYS$LDR]MULTIPATH_MON.EXE
[SYS$LDR]IO_ROUTINES.STB
[SYS$LDR]IO_ROUTINES[_MON].STB
[SYS$LDR]MULTIPATH.STB
[SYS$LDR]MULTIPATH_MON.STB
o The system crashes with an invalid address in R0 at
NSA$AUDIT_EVENT_C+00008. The dump stack will have several
entries from logical name support (LNMSUB).
Images Affected: [SYS$LDR]LOGICAL_NAMES.EXE
[SYS$LDR]LOGICAL_NAMES.STB
o Convert $ENQ requests may be queued in the wrong order on the
conversion queue.
Images Affected: [SYS$LDR]LOCKING.EXE
[SYS$LDR]LOCKING.STB
o Documentation states that a process joins the system and
default group resource domains when created. At present, the
process only joins the system domain. The first $ENQ will
result in the process joining the default group domain.
Images Affected: [SYS$LDR]LOCKING.EXE
[SYS$LDR]LOCKING.STB
o One of the inputs to the SCH$CHANGE_CUR_PRIORITY routine is
the CPU db address. This is the address of the CPU that
executes changing the priority of a particular process. On
occasion, the input is from a different CPU and the
SCH$CHANGE_CUR_PRIORITY routine reads the input incorrectly.
Images Affected: [SYS$LDR]PROCESS_MANAGEMENT.EXE
[SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
[SYS$LDR]PROCESS_MANAGEMENT.STB
[SYS$LDR]PROCESS_MANAGEMENT_MON.STB
Problems Addressed in VMS721_SYS-V0400:
o VMS721_SYS-V0300 kit did not include all images
The VMS721_SYS-V0300 kit did not include all the images necessary
to correct the problems.
Images Affected: [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
Problems Addressed in VMS721_SYS-V0300:
o Redefining logical name tables may lead to a system crash.
Redefining a logical name table, such as LNM$TEMPORARY_MAILBOX, to
a process-private logical name table may lead to a system crash if
the process also creates a mailbox with a logical name. The crash
would typically occur when the CLUSTER_SEVER process was the
current process.
Images Affected: [SYS$LDR]LOGICAL_NAMES.EXE
Problems Addressed in VMS721_SYS-V0200:
o Third party access checks are failing.
Third party access checks are failing after all rights are removed
and new rights are added using Grant/Revoke_id services.
Images Affected: [SYS$LDR]SECURITY.EXE
[SYS$LDR]SECURITY.STB
[SYS$LDR]SECURITY_MON.EXE
[SYS$LDR]SECURITY_MON.STB
o Identifiers are being ignored on user accounts.
When granting identifiers to a user, access to a queue that had
previously worked was no longer working. This is shown below:
$ submit/user=USER1/nolog SYS$SYSDEVICE:[USER1]test/que=USER1$test
%SUBMIT-F-CREJOB, error creating job
-JBC-E-NOPRIV, insufficient privilege or queue protection violation
$
$ uaf grant/id ID1 USER1
%UAF-I-GRANTMSG, identifier ID1 granted to USER1
$
$ submit/user=USER1/nolog SYS$SYSDEVICE:[USER1]test/que=USER1$test
Job TEST (queue USER1$TEST, entry 7) started on USER1$TEST
$
$ uaf grant/id ID2 USER1
%UAF-I-GRANTMSG, identifier ID2 granted to USER1
$
$ submit/user=USER1/nolog SYS$SYSDEVICE:[USER1]test/que=USER1$test
Job TEST (queue USER1$TEST, entry 8) started on USER1$TEST
$
$ uaf grant/id ID3 USER1
%UAF-I-GRANTMSG, identifier ID3 granted to USER1
$
$ submit/user=USER1/nolog SYS$SYSDEVICE:[USER1]test/que=USER1$test
Job TEST (queue USER1$TEST, entry 9) started on USER1$TEST
$
$ uaf grant/id ID4 USER1
%UAF-I-GRANTMSG, identifier ID4 granted to USER1
$
$ submit/user=USER1/nolog SYS$SYSDEVICE:[USER1]test/que=USER1
$test
%SUBMIT-F-CREJOB, error creating job
-JBC-E-NOPRIV, insufficient privilege or queue protection violation
Images Affected: [SYS$LDR]SECURITY.EXE
Problems Addressed in VMS721_SYS-V0100:
o Prevent System Crash
This fix prevents a system crash on OpenVMS V7.2-1
Images Affected: [SYS$LDR]PROCESS_MANAGEMENT.EXE
[SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
Problems Addressed in VMS721_SYSLOA-V0100:
o Two nodes can crash with a Lock Manager bugcheck.
Images Affected: [SYS$LDR]SYS$CLUSTER.EXE
o A remote $GETJPI command fails with a BADBUFLEN error.
Images Affected: [SYS$LDR]SYS$CLUSTER.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 VMS721_UPDATE /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
All trademarks are the property of their respective owners.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
dec-axpvms-vms721_update-v0200--4.README
dec-axpvms-vms721_update-v0200--4.CHKSUM
dec-axpvms-vms721_update-v0200--4.pcsi-dcx_axpexe
vms721_update-v0200.CVRLET_TXT
