|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: system PRIVILEGED account (root
nfsserver.support.compaq.com)Date: Tue Jun 26 2001 - 04:30:36 CDT
*******************************************************************************
* *
* This is an update to an existing patch... *
* *
* Online links can be found at *
* http://ftp.support.compaq.com/patches/public/vms/axp/v7.2-1/dec-axpvms-vms721_update-v0300--4.README
*******************************************************************************
TITLE: OpenVMS VMS721_UPDATE-V0300 Update Alpha V7.2-1 ECO Summary
New Kit Date : 26-JUN-2001
Modification Date: Not Applicable
Modification Type: Updated Kit
NOTE: An OpenVMS saveset or PCSI installation file is stored
on the Internet in a self-expanding compressed file.
For OpenVMS savesets, the name of the compressed saveset
file will be kit_name.a-dcx_vaxexe for OpenVMS VAX or
kit_name.a-dcx_axpexe for OpenVMS Alpha. Once the OpenVMS
saveset is copied to your system, expand the compressed
saveset by typing RUN kitname.dcx_vaxexe or kitname.dcx_alpexe.
For PCSI files, once the PCSI file is copied to your system,
rename the PCSI file to kitname-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-V0300
DEC-AXPVMS-VMS721_UPDATE-V0300--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-V0200
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-V0300 KIT
o The VMS721_UPDATE-V200 kit installed graphics drivers in
[SYSEXE]. They should have been placed in [SYS$LDR].
Images Affected: [SYS$LDR]SYS$GBDRIVER.EXE
[SYS$LDR]SYS$GZDRIVER.EXE
[SYS$LDR]SYS$GZVDRIVER.EXE
[SYS$LDR]SYS$HWDRIVER4.EXE
[SYS$LDR]SYS$LAN_ATM4.EXE
[SYS$LDR]SYS$MCDRIVER.EXE
[SYS$LDR]SYS$MKDRIVER.EXE
[SYS$LDR]SYS$PKADRIVER.EXE
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 <date> <time> in shareable
image SYS$COMMON:[SYSLIB]DECC$SHR.EXE;1
differs from date of <date> <time> 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 <dirent.h>
#include <errno.h>
#include <stat.h>
#include <stdio.h>
#include <string.h>
#include <unistd.h>
#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 <file>
-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*
<power-cycle system>
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-D