____________________________________________________
OpenVMS AXP Version 1.5 Release Notes Addendum
Order Number: AV-PZ27A-TE
May 1993
This document describes features, changes, and
restrictions that apply to the OpenVMS AXP Version
1.5 operating system.
Revision/Update Information: This is a new manual.
Software Version: OpenVMS AXP Version 1.5
Digital Equipment Corporation
Maynard, Massachusetts
________________________________________________________________
May 1993
The information in this document is subject to change
without notice and should not be construed as a commitment
by Digital Equipment Corporation. Digital Equipment
Corporation assumes no responsibility for any errors that
may appear in this document.
The software described in this document is furnished under
a license and may be used or copied only in accordance with
the terms of such license.
No responsibility is assumed for the use or reliability
of software on equipment that is not supplied by Digital
Equipment Corporation or its affiliated companies.
© Digital Equipment Corporation 1993.
All Rights Reserved.
The following are trademarks of Digital Equipment
Corporation: Alpha AXP, AXP, CDA, DEC, DECmigrate, DECnet,
DECthreads, DECwindows, Digital, HSC, InfoServer, LAT,
OpenVMS, TURBOchannel, UETP, VAX, VAX COBOL, VAX DOCUMENT,
VMS, VMScluster, the AXP logo, and the DIGITAL logo.
The following are third-party trademarks:
Adobe, Display PostScript, and PostScript are registered
trademarks of Adobe Systems Incorporated.
Motif, and OSF/1 are registered trademarks of the Open
Software Foundation, Inc.
X Window System is a common law trademark of MIT.
All other trademarks and registered trademarks are the
property of their respective holders.
ZK6315
This document was prepared using VAX DOCUMENT, Version 2.1.
_________________________________________________________________
Contents
Preface................................................... v
1 OpenVMS AXP Version 1.5 Release Notes
1.1 Console and PALcode Revisions Supported By
OpenVMS AXP Version 1.5....................... 1-1
1.2 AUTOGEN ...................................... 1-3
1.2.1 AUTOGEN Tuning Problem.................... 1-3
1.2.2 SETPARAMS Phase - Behavior Change......... 1-4
1.3 BACKUP Command - /EXACT_ORDER Qualifier Not
Supported .................................... 1-4
1.4 DEC C RTL Known Problems...................... 1-4
1.5 DECmigrate.................................... 1-5
1.6 DECthreads (CMA).............................. 1-5
1.7 New Support for DECwindows Motif Layered
Product Customers............................. 1-5
1.8 DEFTA TURBOchannel FDDI Adapter Supported..... 1-6
1.9 Unique Device Unit Numbers Required -
Restriction................................... 1-7
1.10 Documentation Error - Default Linker Behavior
Is /NATIVE_ONLY............................... 1-7
1.11 F$FILE_ATTRIBUTES Lexical Function Returns
Incorrect Value............................... 1-7
1.12 Intense File System Activity Related to LEF
Hangs......................................... 1-8
1.13 Image Activator Length Comparison Problem..... 1-9
1.14 InfoServer Notes.............................. 1-10
1.14.1 InfoServer System BOOT Command Change..... 1-10
1.14.2 Accessing ISO 9660 CDs Served Through the
InfoServer................................ 1-10
1.14.3 InfoServer Installation - Change in
Service Name.............................. 1-10
1.15 Change in LAT Behavior........................ 1-11
iii
1.16 LIB$FIND_IMAGE_SYMBOL Routine................. 1-12
1.17 LIBRARIAN Operation Failure................... 1-13
1.18 MACRO-32 Compiler Problems.................... 1-13
1.19 Performance Degradation Due to Insufficient
Swap File Space............................... 1-15
1.20 PMAZB Adapter - Limited Support Available..... 1-16
1.21 RZ24L 245MB SCSI Fixed-Disk Drive Supported... 1-16
1.22 Standalone BACKUP from ESEnn Device Results in
System Halt................................... 1-16
1.23 System Disks Connected to HSC Devices ........ 1-17
1.24 System Management Utility (SYSMAN) Problem.... 1-17
1.25 UETP Test Package - FDDI Devices Not Supported
.............................................. 1-17
1.26 Upgrade Procedure - Rebooting After Phase 1
.............................................. 1-18
1.27 Translated VAX COBOL Programs Supported....... 1-18
1.28 VOID Kits Included on OpenVMS AXP Version 1.5
CD............................................ 1-18
1.28.1 Memory Exhaustion Problem on Clustered
Systems................................... 1-19
1.28.2 PEDRIVER Update Kit....................... 1-19
Tables
1-1 Console and PALcode Revisions Supported by
Version 1.5 .............................. 1-2
1-2 System Parameters......................... 1-9
iv
_________________________________________________________________
Preface
This manual describes features and restrictions of the
OpenVMS AXP Version 1.5 operating system. These notes
contain information that supplements the OpenVMS AXP
Version 1.5 Release Notes.
Intended Audience
This manual is intended for general users, system managers,
developers, and programmers who use the operating system.
It is especially useful for those who are about to install
the operating system.
Associated Information
For a list of additional documents that are available in
support of this version of OpenVMS AXP, refer to the CD-ROM
booklet and the Overview of OpenVMS Documentation.
Conventions
In this manual, every use of OpenVMS AXP means the OpenVMS
AXP operating system, every use of OpenVMS VAX means the
OpenVMS VAX operating system, and every use of OpenVMS
means both the OpenVMS AXP operating system and the OpenVMS
VAX operating system.
The following conventions are also used in this manual:
V1.x A margin note beneath each heading
indicates the OpenVMS AXP version in which
the note was first published. All notes
identified with the V1.0 margin note also
apply to OpenVMS AXP Version 1.5.
v
Ctrl/x A sequence such as Ctrl/x indicates that
you must hold down the key labeled Ctrl
while you press another key or a pointing
device button.
. A vertical ellipsis indicates the omission
. of items from a code example or command
. format; the items are omitted because
they are not important to the topic being
discussed.
[ ] In format descriptions, brackets indicate
optional elements. You can choose one,
none, or all of the options. (Brackets
are not optional, however, in the syntax
of a directory name in an OpenVMS file
specification, or in the syntax of a
substring specification in an assignment
statement.)
boldface text Boldface text represents the introduction
of a new term or the name of an argument,
an attribute, or a reason.
Boldface text is also used to show user
input in Bookreader versions of the
manual.
italic text Italic text emphasizes important
information, indicates variables, and
indicates complete titles of manuals.
Italic text also represents information
that can vary in system messages (for
example, Internal error number), command
lines (for example, /PRODUCER=name), and
command parameters in text.
UPPERCASE TEXT Uppercase text indicates a command, the
name of a routine, the name of a file, or
the abbreviation for a system privilege.
numbers All numbers in text are assumed to
be decimal, unless otherwise noted.
Nondecimal radixes-binary, octal, or
hexadecimal-are explicitly indicated.
vi
1
_________________________________________________________________
OpenVMS AXP Version 1.5 Release Notes
The following notes contain information that supplements
the OpenVMS AXP Version 1.5 Release Notes.
1.1 Console and PALcode Revisions Supported By OpenVMS AXP
Version 1.5
V1.5 The console and PALcode versions supported by the OpenVMS
AXP Version 1.5 operating system differ from those that
were supported by OpenVMS AXP Version 1.0.
Table 1-1 shows the console and PALcode revisions that
are supported by the OpenVMS AXP Version 1.5 operating
system. The console and PALcode upgrades must be performed
before you upgrade an OpenVMS AXP Version 1.0 system to
Version 1.5. The supported console and PALcode versions are
contained on the Alpha AXP Systems Firmware Update CD that
is included in your OpenVMS AXP Version 1.5 distribution
kit.
Although the minimum revision levels required to boot
OpenVMS AXP Version 1.5 have been left at the supported
Version 1.0 revision levels, significant fixes have been
included in the Version 1.5 supported levels. OpenVMS
AXP Version 1.5 is not supported on console and PALcode
revision levels lower than those shown in Table 1-1.
1-1
OpenVMS AXP Version 1.5 Release Notes
1.1 Console and PALcode Revisions Supported By OpenVMS AXP Version 1.5
Table 1-1 Console and PALcode Revisions Supported by
__________Version_1.5______________________________________
Console PALcode
System_____________Version__________Version________________
DEC 3000 Model 2.4 5.41
300
DEC 3000 Model 2.4 5.41
400
DEC 3000 Model 2.4 5.41
500
DEC 4000 3.0 5.41
DEC 7000/10000 2.2 (for EV4 5.41
pass 2)
2.3 (for EV4
___________________pass_3)_________________________________
The troubleshooting guidelines that follow contain
information that can help you determine the proper action
to take when minimum console and PALcode revision levels
are not present on your system.
Troubleshooting Guideline - During an Upgrade
If a message similar to the following is displayed at the
beginning of the OpenVMS AXP Version 1.5 upgrade procedure,
it means that the PALcode and console must be upgraded:
PALcode revision 5.18 is below required minimum of 5.25
The upgrade procedure then aborts. At this point, you must
upgrade the console and PALcode versions using the firmware
CD included in your distribution kit. After you upgrade the
console and PALcode, restart the upgrade procedure.
Troubleshooting Guidelines - While Booting Version 1.5
The following guidelines apply to messages that may be
displayed while booting a Version 1.5 system:
o If a message similar to the following is displayed, it
means you are attempting to boot an OpenVMS AXP Version
1.5 system on hardware whose revision levels are below
the versions shown in Table 1-1:
1-2
OpenVMS AXP Version 1.5 Release Notes
1.1 Console and PALcode Revisions Supported By OpenVMS AXP Version 1.5
APB-F-PALREV, PALcode revision 4.33 is below required minimum of 5.25
PLEASE UPDATE YOUR PALcode
UNABLE TO CONTINUE
After the message is displayed, the boot procedure
aborts. Use the firmware CD included in your
distribution kit to upgrade the console and PALcode
versions. After upgrading the console and PALcode
versions, reboot your system.
o If a message similar to the following is displayed, it
means your console and PALcode revision levels equal or
exceed the minimum bootable versions but are still below
the supported versions listed in Table 1-1. Digital
does not support systems that contain console or PALcode
revisions not listed in Table 1-1.
APB-W-PALREV, PALcode revision 5.25 is below supported minimum of 5.41
PLEASE UPDATE YOUR PALcode
Although the system continues to boot, you should
use the firmware CD included in your distribution
kit to upgrade the console and PALcode versions. This
allows you to take advantage of improvements and fixes
contained in the latest versions.
1.2 AUTOGEN
V1.5 The following sections describe a problem and a change in
behavior.
1.2.1 AUTOGEN Tuning Problem
V1.5 AUTOGEN may incorrectly set the system parameter PFCDEFAULT
to 128 on satellite nodes in a cluster. This can increase
the number and size of paging I/Os to the boot node.
To prevent this problem, insert the following line in the
SYS$SYSTEM:MODPARAMS.DAT file before you run AUTOGEN:
PFCDEFAULT=64
1-3
OpenVMS AXP Version 1.5 Release Notes
1.2 AUTOGEN
1.2.2 SETPARAMS Phase - Behavior Change
V1.5 The AUTOGEN SETPARAMS phase behaves differently on an
OpenVMS AXP system than it does on an OpenVMS VAX system.
On OpenVMS VAX, the AUTOGEN SETPARAMS phase resets all
system parameters to their default values. AUTOGEN then
modifies some or all of those values by using data gathered
in feedback mode or by using user-supplied data contained
in the MODPARAMS.DAT file. If no modification is made, the
default value is used the next time the system boots.
On OpenVMS AXP, the AUTOGEN SETPARAMS phase uses the values
from the current system image; values are not reset to
their defaults. Current values are used, except for those
that are explicitly modified by AUTOGEN.
For more information about how AUTOGEN uses default
values, see the AUTOGEN Help topic EXECUTION-TYPE, INITIAL
subtopic.
1.3 BACKUP Command - /EXACT_ORDER Qualifier Not Supported
V1.5 The OpenVMS AXP Version 1.5 Release Notes manual
incorrectly states that the /EXACT_ORDER qualifier for
the BACKUP command is available. The /EXACT_ORDER qualifier
is unavailable in OpenVMS AXP Version 1.5.
1.4 DEC C RTL Known Problems
V1.5 The following problems exist in the DEC C RTL in OpenVMS
AXP Version 1.5:
o The C RTL loses carriage-control information when it
reads from mailboxes. As a result, information that
is read from a mailbox has no line breaks or carriage
returns; the original lines are concatenated.
o When an application sets the reentrancy mode to AST, the
C RTL always enables asynchronous system traps (ASTs)
during a file open operation. To make your application
disable ASTs, place SYS$SETAST(0) calls after every
file open call and after the first I/O operations to the
stdin, stdout, and stderr functions (that is, when the
C RTL performs a file open operation to initialize the
stdio device). This problem does not occur in any other
reentrancy mode.
1-4
OpenVMS AXP Version 1.5 Release Notes
1.5 DECmigrate
1.5 DECmigrate
V1.5 DECmigrate Version 1.1 software generates translated images
that are executable on OpenVMS AXP Version 1.5 or later.
This version of DECmigrate does not support OpenVMS AXP
Version 1.0. Images translated by DECmigrate Version 1.0
are executable on all versions of the OpenVMS AXP system.
1.6 DECthreads (CMA)
V1.5 A potential problem occurs between the DECthreads software
and the DEC C RTL when a C program that calls LIB$FIND_
IMAGE_SYMBOL dynamically activates DECthreads or another
shareable image that depends on DECthreads. This problem
may result in an access violation inside CMA$RTL in a call
from DECC$SHR.
To work around this problem, link the image that calls
LIB$FIND_IMAGE_SYMBOL against CMA$RTL.
Dynamically activating DECthreads or shareable images that
depend on DECthreads does not work under all circumstances.
Several software facilities contain code whose behavior
is conditional upon the presence or absence of threads at
the time that these facilities are initialized. If any of
these facilities are in use by a program, threads cannot
be safely brought into the process after execution begins
because these facilities cannot respond to the change. An
attempt to bring threads in at this stage typically causes
the program to abort. Other unpredictable behavior, such as
access violations, may result instead of program abortion.
1.7 New Support for DECwindows Motif Layered Product Customers
V1.5 With the release of OpenVMS AXP Version 1.5, the following
features of the DECwindows Motif Version 1.1 layered
product are now available:
o Bindings
Bindings (including Motif bindings) and header file
support for Ada and Pascal are now available.
o TCP/IP
In addition to DECnet and local transports, TCP/IP
is now available through UCX to allow OpenVMS AXP
clients to connect to other displays that use TCP/IP,
1-5
OpenVMS AXP Version 1.5 Release Notes
1.7 New Support for DECwindows Motif Layered Product Customers
including OpenVMS VAX and AXP workstations, DEC OSF/1
workstations, third-party systems, and X terminals. Of
course, OpenVMS AXP workstation displays can also accept
connections from these clients (except for X terminals)
via TCP/IP.
o Adobe Display PostScript server extension
Display PostScript lets users display PostScript files
with the CDA Viewer; programmers can now include Display
PostScript commands in applications to rotate and scale
fonts, display curves, and display graphics on alternate
coordinate systems.
o Tailoring for DECwindows server files
Users can now tailor DECwindows server files on or off
their systems to manage disk space more effectively;
additional tailoring support for DECwindows files will
be available in a future release of the DECwindows Motif
layered product.
o PEX (PHIGS extensions) and multibuffering extensions
PEX and multibuffering extensions are now available
in the DEC Open3D product to support three-dimensional
drawing operations.
o Font server renderer
The X11 R5 display server now includes a font server
renderer that supports the use of font servers to access
fonts. You can thus distribute font files on systems
other than the system on which the display server is
running.
o Scalable outline fonts
Scalable outline fonts are now supported by the X11 R5
display server. These fonts are distributed with the
other DECwindows fonts.
1.8 DEFTA TURBOchannel FDDI Adapter Supported
V1.5 The DEFTA TURBOchannel FDDI adapter is fully supported on
DEC 3000 systems running OpenVMS AXP Version 1.5.
1-6
OpenVMS AXP Version 1.5 Release Notes
1.9 Unique Device Unit Numbers Required - Restriction
1.9 Unique Device Unit Numbers Required - Restriction
V1.5 In a dual-architecture cluster, all disk device unit
numbers within an allocation class must be unique. For
example, suppose an existing disk within the cluster is
named $5$DUA10. When you add another disk device to the
same allocation class (even if it is on another disk
controller or another device type), the new disk device
must be given a unit number other than 10.
1.10 Documentation Error - Default Linker Behavior Is
/NATIVE_ONLY
V1.5 Migrating to an OpenVMS AXP System: Recompiling and
Relinking Applications, the OpenVMS Linker Utility Manual,
and the description of the BAD_LINK message in the Help
Message database in the OpenVMS System Messages and
Recovery Procedures Reference Manual mistakenly describe
/NONATIVE_ONLY to be the default behavior of the linker.
The /NATIVE_ONLY qualifier to the LINK command directs
the linker not to pass along the procedure signature block
(PSB) information, created by the compilers, in the image
it is creating. This is the default behavior of the linker.
PSB information is necessary if the image you are creating
in the link operation calls translated VAX images (but
not if translated VAX images call it). To include PSB
information in the image, you must compile the original
program sources with the appropriate compiler switch (as
indicated by the compiler documentation) and specify the
/NONATIVE qualifier when linking the program's object
modules. The image activator uses the PSB information in
the image to create jacket routines, which allow native AXP
images to work with translated VAX images.
1.11 F$FILE_ATTRIBUTES Lexical Function Returns Incorrect Value
V1.5 When you use the STORED_SEMANTICS item code with the
F$FILE_ATTRIBUTES lexical function, an incorrect ASCII
string is returned. Digital expects to fix this problem in
a future release of the OpenVMS AXP operating system.
1-7
OpenVMS AXP Version 1.5 Release Notes
1.12 Intense File System Activity Related to LEF Hangs
1.12 Intense File System Activity Related to LEF Hangs
V1.5 VMScluster systems may hang when all the following
conditions are met:
o File system activity is extremely high (open, close,
extend, truncate, and delete functions).
o All of the file system activity occurs on one volume,
and the volume is full.
o All of this activity occurs across several VMScluster
nodes.
o At least one VMScluster node has small XQP buffer
caches.
This problem is frequently seen when heavily loaded UETP
testing is conducted on recently configured systems.
To work around this problem, increase the setting of the
system parameters listed in Table 1-2. The variable n
represents the maximum number of processes expected in a
system.
1-8
OpenVMS AXP Version 1.5 Release Notes
1.12 Intense File System Activity Related to LEF Hangs
Table_1-2_System_Parameters________________________________
System_Parameter____Value__________________________________
ACP_MAPCAHCE Greater than n
ACP_DIRCACHE Greater than (nx2)
ACP_HDRCACHE Greater than (nx3)
ACP_DINDXCACHE______Greater_than_n_________________________
Digital expects to address this problem in a future release
of the OpenVMS operating system.
1.13 Image Activator Length Comparison Problem
V1.5 In rare circumstances, you can build a correct image with
the OpenVMS linker and receive the following error message
when you try to run the image:
IMGACT-F-BAD_FIXUPVEC, the fixup vector contains inconsistent data
The message occurs because a length comparison in the image
activator is off by 1 byte. The failure happens when the
necessary fixup information exactly fills the area of the
image allocated for that purpose.
To work around this problem, take any actions that slightly
change the amount of fixup information that is generated.
For instance, in the linker options file that is used to
generate the image, you can add a reference to a shareable
image that is not otherwise shown in the linker map, as
shown in the following example:
SYS$SHARE:LIBOTS.EXE/SHARE
Make sure that the shareable image you specify is present
on all machines that will run the program. Therefore,
choose an image that is part of the operating system
distribution kit or one that you provide yourself. You
can reduce overhead by choosing a very simple image that
does not refer to other images.
Digital expects to fix this problem in a future release.
1-9
OpenVMS AXP Version 1.5 Release Notes
1.14 InfoServer Notes
1.14 InfoServer Notes
V1.5 The following notes pertain to the InfoServer.
1.14.1 InfoServer System BOOT Command Change
V1.5 If you use the InfoServer system to install the OpenVMS AXP
Version 1.5 operating system on a DEC 4000 system, add the
following item to the BOOT command:
-START 0
The following example shows a complete BOOT command:
>>> BOOT -FL 0,0 -FI APB_015 -START 0 lan-device-name
1.14.2 Accessing ISO 9660 CDs Served Through the InfoServer
V1.5 The OpenVMS AXP InfoServer client software can access
InfoServer services in the ODS_2 name space only. However,
when an ISO 9660 CD is placed in an InfoServer device, a
service is automatically created for only the ISO_9660 name
space.
To permit access to an ISO 9660 CD by the client software,
you must create an ODS_2 service for the CD. See the
InfoServer System Operations Guide for complete information
about how to create the ODS_2 service.
1.14.3 InfoServer Installation - Change in Service Name
V1.5 If you are using the InfoServer to install OpenVMS AXP
Version 1.5, the default InfoServer service name displayed
by the installation procedure is incorrect. The system
prompts you to enter the InfoServer service name and
displays the default name OPENVMSALPHA015. Do not use the
default name.
Instead, enter OPENVMSAXP15 for the InfoServer service
name, as shown in the sample display in the OpenVMS AXP
Version 1.5 Upgrade and Installation Manual.
1-10
OpenVMS AXP Version 1.5 Release Notes
1.15 Change in LAT Behavior
1.15 Change in LAT Behavior
V1.5 After you enter the LATCP CREATE LINK /DECNET command, the
following message may be displayed:
%SYSTEM-F-BADPARAM, bad parameter value
This may indicate that the SCSSYSTEMID system parameter
is set to an illegal value. Use the following formula when
setting this parameter:
(1024 * a) + n
In the formula, a is the DECnet area, and n is the DECnet
node number.
When you use the /DECNET qualifier with the LATCP CREATE
LINK command, be sure that the value of the SCSSYSTEMID
system parameter is within the range of 1025 to 65535,
as determined by the formula above. The value for this
parameter should match the results obtained by using the
formula. If the value is outside the range of 1025 to
65535, the LAT protocol is unable to start.
When you use the /NODECNET qualifier, the LAN device driver
code decides what address to use. The decision is based on
the following criteria:
o If SCSSYSTEMID is set to 0 but DECnet is already running
on an Ethernet controller, the LAN device code allows
the LAT software to use the same address as DECnet (AA-
00-04-00-xx-xx).
o If SCSSYSTEMID is set to 0 and DECnet is not running,
the 08-00-2B-xx-xx-xx address is used.
o If the setting for SCSSYSTEMID is the same as the DECnet
node number and DECnet is not running, the LAN device
code forces LAT to use the AA-00-04-00-xx-xx address.
Restriction
If DECnet is configured on the system (or if the system
is part of a cluster), SCSSYSTEMID may contain a nonzero
value. Normally this is not a problem unless the system has
two or more LAN controllers connected to the same logical
LAN.
1-11
OpenVMS AXP Version 1.5 Release Notes
1.15 Change in LAT Behavior
For example, if your system has an FDDI controller and
an Ethernet controller, your site may be configured so
that the FDDI ring attached to the FDDI controller and
the Ethernet segment attached to the Ethernet controller
are bridged by a 10/100 LAN bridge (FDDI-to-Ethernet). In
this configuration, it is impossible to run LAT over both
controllers.
In such a configuration, you must run LAT and DECnet over
the same controller if SCSSYSTEMID is not 0. If you fail
to do so, DECnet starts first, which in turn causes the
LAT startup on the other controller to fail. This failure
occurs because LAT startup tries to use the AA-00-04-00-
xx-xx address (the DECnet LAN address); however, because
DECnet is already using this address on another controller,
the data link layer prevents the LAT startup from using
that address. (In a single logical LAN, all data link
addresses must be unique. Because both controllers try
to use the same address, it is no longer unique.)
Using the following command to create the LAT link also
fails because the LAN driver tries to use the address based
on SCSSYSTEMID:
LATCP> CREATE LINK LAT$LINK_2 /NODECNET
If SCSSYSTEMID is set to 0, configuring LAT and DECnet on
different controllers is possible. However, in a cluster
environment, SCSSYSTEMID cannot be set to 0.
1.16 LIB$FIND_IMAGE_SYMBOL Routine
V1.5 The LIB$FIND_IMAGE_SYMBOL routine sometimes uses an
incorrect value as the base address of an image's symbol
vector, resulting in an access violation. This occurs when
both of the following conditions are met:
o The image being referenced by LIB$FIND_IMAGE_SYMBOL was
installed using the /RESIDENT qualifier.
o The image being referenced by LIB$FIND_IMAGE_SYMBOL was
already activated, and the initial activation of the
image was not performed by LIB$FIND_IMAGE_SYMBOL. (That
is, activation was done by direct call to SYS$IMGACT.)
1-12
OpenVMS AXP Version 1.5 Release Notes
1.16 LIB$FIND_IMAGE_SYMBOL Routine
Use either of the following methods to work around this
problem:
o Reinstall the image being referenced, but do not specify
the /RESIDENT qualifier.
o Activate the uninstalled copy of the image, not the
installed copy. To do this, define a logical name for
the image being referenced, as shown in the following
example for the DPML$SHR image:
$ DEFINE DPML$SHR SYS$LIBRARY:DPML$SHR.EXE;
Note that you must include a semicolon after the file
type in the file specification.
1.17 LIBRARIAN Operation Failure
V1.5 The OpenVMS AXP LIBRARIAN sometimes does not inform you
of errors during compression, data reduction, or data
expansion operations. This problem occurs if the account
or process in which the LIBRARIAN is running has a low
PGFLQUOTA process quota. Operation failure is not readily
apparent because the $PUTMSG system service always returns
a status of SS$_NORMAL, even when the system service fails.
However, when a failure occurs, the LIBRARIAN returns a
status other than success.
To work around this problem, run the compression, data
reduction, or data expansion operation in an account with
a PGFLQUOTA process quota greater than 23000. In addition,
ensure that your command procedures check the return status
from the LIBRARY command.
1.18 MACRO-32 Compiler Problems
V1.5 The following problems exist in the MACRO-32 Compiler.
Their occurrence, although extremely rare, results in
incorrect code generation.
o The first problem concerns the use of indexed addressing
mode as the base address in variable bit-field
instructions. If the compiler's optimizer determines
that it can compute the base address once and reuse
1-13
OpenVMS AXP Version 1.5 Release Notes
1.18 MACRO-32 Compiler Problems
it in a nearby bit-field instruction that uses the
identical operand, it may use the wrong indexing mode.
In the following example, the compiler combines the
two address references to (R5)[R1] but erroneously uses
longword context rather than byte context for the index
operation, thus accessing the wrong memory location:
BBS #2, (R5)[R1], 10$
INSV #1, #3, #8, (R5)[R1]
Note that this problem occurs only if both instructions
are variable bit-field instructions. Eliminate this
error by specifying /OPT=NOADDR when you compile the
module that contains this code.
o The second problem concerns read references from
identical memory operands that are separated by a
write reference to another memory location. The write
reference should prevent the compiler from attempting
to combine the read references and to cache the value
in a register. The write reference may refer to the same
location, or to an overlapping location, in a way that
cannot be detected by the compiler. For example, suppose
that at run time, R4 and R5 have the same value in the
following code:
MOVL 4(R4), R8
MOVW #1, 6(R5)
PUSHL 4(R4)
The PUSHL instruction may use the same value fetched for
the MOVL instruction, even though MOVW changed the value
in memory.
The problem of optimizing two read operations across a
write operation occurs very infrequently and is unlikely
to cause a run-time error. If this problem causes a run-
time error, eliminate the error by specifying /OPT=NOREF
when compiling the module that contains this code.
1-14
OpenVMS AXP Version 1.5 Release Notes
1.19 Performance Degradation Due to Insufficient Swap File Space
1.19 Performance Degradation Due to Insufficient Swap File Space
V1.5 Performance may degrade on systems using large working sets
if the swap file space is insufficient.
Configurations with large process working sets that run
under heavy load conditions must have adequate swap file
space. Processes can be swapped out with a working set size
up to the value of WSQUOTA. The I/O that is issued to swap
out the process can be as large as the setting for WSQUOTA
and requires this much space in the swap file. (WSQUOTA is
a process parameter that you can adjust using the Authorize
utility.)
To provide adequate swap file space, periodically run
AUTOGEN with the FEEDBACK option. When running AUTOGEN,
make sure that:
o The system has been up long enough to have run a typical
load (at least 24 hours).
o There is no hard-coded SWAPFILE value in the
SYS$SYSTEM:MODPARAMS.DAT file. (A hard-coded SWAPFILE
value prevents AUTOGEN from sizing the swap files
correctly.)
AUTOGEN resizes swap files provided there is adequate
space on the volumes containing the swap files. If there
is insufficient space, AUTOGEN recommends swap file sizes.
Use swap file sizes at least as large as those recommended
by AUTOGEN. If the swap file sizes need to be increased
and insufficient free space exists on the volume containing
the swap files, perform one of the following steps after
AUTOGEN finishes:
o Free up space on the volume, and increase the swap file
size to at least the value recommended by AUTOGEN.
o Move the swap files to a volume with sufficient space.
Make sure that the swap files are at least as large as
those recommended by AUTOGEN.
o Add another swap file. The total space in all swap files
must be at least as large as the total size recommended
by AUTOGEN.
1-15
OpenVMS AXP Version 1.5 Release Notes
1.20 PMAZB Adapter - Limited Support Available
1.20 PMAZB Adapter - Limited Support Available
V1.5 The OpenVMS AXP Version 1.5 Release Notes manual and the
OpenVMS AXP Version 1.5 Upgrade and Installation Manual
state that the TURBOchannel PMAZB adapter is supported in
OpenVMS AXP Version 1.5.
The PMAZB adapter is supported in OpenVMS AXP Version 1.5
for data devices only. No support is provided for OpenVMS
AXP Version 1.5 system disks that are connected to PMAZB
adapters.
1.21 RZ24L 245MB SCSI Fixed-Disk Drive Supported
V1.5 The RZ24L 245MB SCSI fixed-disk drive is fully supported on
DEC 3000 Model 300 and Model 300L systems running OpenVMS
AXP Version 1.5.
1.22 Standalone BACKUP from ESEnn Device Results in System Halt
V1.5 Booting standalone BACKUP from an ESE52, ESE56, or ESE58
device sometimes fails with a system halt, especially
when there are a large number of devices configured on
the system. BACKUP issues a message indicating "Kernel
stack not valid."
To work around this problem, boot standalone BACKUP
conversationally, and set KSTACKPAGES to 16, as shown in
the following example:
>>>B -FL E,1 DUA20
.
.
.
SYSBOOT> SET KSTACKPAGES 16
SYSBOOT> CONTINUE
.
.
.
$
1-16
OpenVMS AXP Version 1.5 Release Notes
1.23 System Disks Connected to HSC Devices
1.23 System Disks Connected to HSC Devices
V1.5 Digital recommends that you use high-priority HSC
requestors when connecting system disks to HSC devices.
Refer to the HSC User Guide for information about requestor
priorities.
1.24 System Management Utility (SYSMAN) Problem
V1.5 When the system management environment is set clusterwide
with the /CLUSTER qualifier, entering the following SYSMAN
command sometimes causes a hang:
SYSMAN> DO SHOW DEVICE device-name
This hang is caused by a communication failure between the
process spawned by the DO command and the remote SMISERVER
process on one of the AXP nodes in the cluster.
To work around this problem, press Ctrl/C to return to
the SYSMAN> prompt. Delete the remote SMISERVER process
on the node that did not respond. You can then restart the
SMISERVER process with the following command:
$ @SYS$SYSTEM:STARTUP SMISERVER
If the DO SHOW DEVICE device-name command hangs on the
next attempt, press Ctrl/C to return to the SYSMAN>
prompt. Delete and then restart the SMISERVER process on
the unresponsive node. Log in to the node that stopped
responding, and enter the DO SHOW DEVICE device-name
command.
Digital expects to fix this problem in a future release of
the OpenVMS AXP operating system.
1.25 UETP Test Package - FDDI Devices Not Supported
V1.5 The UETP test package does not support the following FDDI
devices:
DEFZA
DEFTA
DEFAA
1-17
OpenVMS AXP Version 1.5 Release Notes
1.26 Upgrade Procedure - Rebooting After Phase 1
1.26 Upgrade Procedure - Rebooting After Phase 1
V1.5 If you are upgrading your system to Version 1.5 of the
OpenVMS AXP operating system, be sure you enter the correct
boot command before beginning Phase 2 of the upgrade
procedure, as described in this section.
After the upgrade procedure finishes restoring and purging
files during Phase 1, the system shuts down. The OpenVMS
AXP Version 1.5 Upgrade and Installation Manual incorrectly
states that, at this point in the procedure, you should
reboot the partially upgraded OpenVMS AXP Version 1.5
system from the original system root (SYS0).
Instead, you must reboot from the [SYSF] directory by
entering the boot command in the following format, where
ddcu is the device name for your system disk. (You can omit
the system disk device name if your system supports only
one device.)
>>> BOOT -FLAGS F,0 ddcu
If you encounter a problem booting, perform a
conversational boot by entering the command in the
following format instead:
>>> BOOT -FLAGS F,1 ddcu
1.27 Translated VAX COBOL Programs Supported
V1.5 The OpenVMS AXP Version 1.5 operating system supports the
execution of translated VAX COBOL programs compiled with
the VAX COBOL Version 5.0 compiler (or earlier compilers).
Programs compiled with the VAX COBOL Version 5.1 compiler
are not supported by the OpenVMS AXP Version 1.5 operating
system.
1.28 VOID Kits Included on OpenVMS AXP Version 1.5 CD
V1.5 The following sections describe two updates that must
be applied to OpenVMS VAX Version V5.5-2 systems. Both
update save sets are located in the [VAX_KIT] directory
on your OpenVMS AXP Version 1.5 CD. You must reboot your
VAX systems in order to apply these fixes. These update
kits are required for AXP and VAX system compatibility in a
dual-architecture VMScluster environment.
1-18
OpenVMS AXP Version 1.5 Release Notes
1.28 VOID Kits Included on OpenVMS AXP Version 1.5 CD
1.28.1 Memory Exhaustion Problem on Clustered Systems
V1.5 Memory exhaustion occurs on VMScluster systems when a
SYSAP that exists on a VAX machine is not running on the
AXP nodes. To address this problem, an update kit named
VAXSYSL09_U2055 is located in the [VAX_KIT] directory
on your OpenVMS AXP Version 1.5 CD. A new SYS$LOADABLE_
IMAGES:SYS$SCS.EXE image is supplied with the kit.
Installation Instructions
Use the VMSINSTAL utility to install this update kit. Log
in to the SYSTEM account, and enter the following command:
$ @SYS$UPDATE:VMSINSTAL VAXSYSL09_U2055 [save-set location]
The save-set location can be a tape drive or a disk
directory that contains the kit save set.
1.28.2 PEDRIVER Update Kit
V1.5 The PEDRIVER update kit addresses the following problems:
o A problem that manifests itself as anything from slow
performance to broken virtual circuits (which may result
in VAXport crashes).
o The XQDRIVER (for the DELQA and the DEQTA devices) does
not report the correct number of receive buffers to
PEDRIVER. (XQDRIVER is required for proper operation of
PEDRIVER.)
The update kit, named VAXLAVC02_U2055, is located in the
[VAX_KIT] directory on your OpenVMS AXP Version 1.5 CD.
The following files were patched or replaced:
o [SYS$LDR]PEDRIVER.EXE (new image)
o [SYS$LDR]XQDRIVER.EXE (new image)
o [SYSEXE]SDA.EXE (new image)
o [SYSEXE]SCSDEF.STB (new file)
o [SYSEXE]PEDRIVER.STB (new file)
o [SYSLIB]LIB.MLB (replaces $PEMCOMPDEF and $PEMCLSTDEF
macros)
1-19
OpenVMS AXP Version 1.5 Release Notes
1.28 VOID Kits Included on OpenVMS AXP Version 1.5 CD
o [SYSHLP.EXAMPLES]LAVC$FAILURE_ANALYSIS.MAR (new file)
________________________ Note ________________________
Various internal structures changed as a result of the
fixes to PEDRIVER. The System Dump Analyzer utility
(SDA) and the SCS and PEDRIVER symbol tables are
included in this kit to allow proper SDA operation.
This also necessitated a change in [SYSLIB]LIB.MLB.
______________________________________________________
Installation Instructions
Use the VMSINSTAL utility to install this update kit. Log
in to the SYSTEM account, and enter the following command:
$ @SYS$UPDATE:VMSINSTAL VAXLAVC02_U2055 [save-set location]
1-20