| Previous | Contents |
V7.3-2
OpenVMS support for resource affinity domains (RADs), also known as
NUMA support or awareness, has not been qualified in OpenVMS Alpha
Version 7.3-2 for the AlphaServer ES47/ES80/GS1280 systems. For more
information about RAD support, see the HP OpenVMS Alpha Partitioning and Galaxy Guide.
6.4.3 License Requirements
V7.3-2
AlphaServer ES47/ES80/GS1280 systems require a minimum of two OpenVMS
software licenses: one license for base support and one license for
dual SMP support for the first two processors. This is a change from
the previous way of licensing OpenVMS AlphaServer SMP systems. The dual
SMP licenses for OpenVMS are included with the CPU modules when you
purchase an OpenVMS system or when you purchase additional CPU modules
for an OpenVMS system.
6.4.4 STOP/CPU and Shutdown Behavior
V7.3-2
Because of hardware restrictions, any CPU on an AlphaServer ES47/ES80/GS1280 system with an attached I/O drawer cannot be stopped by using the DCL command STOP/CPU. In contrast, CPUs on these systems without an attached I/O drawer can be stopped with this command.
When the shutdown procedure is invoked on an ES47/ES80/GS1280 system with an attached I/O drawer, an error message such as the following might be displayed:
%SYSTEM-W-WRONGSTATE, CPU 5 is in the wrong state for the requested operation |
You can ignore such messages. The shutdown will complete correctly.
6.4.5 Setting Time at MBM
V7.3-2
You must set the correct time and date on the MBM of an AlphaServer
ES47/ES80/GS1280 system. If you do not, OpenVMS might display an
incorrect time and date.
6.5 AlphaServer GS Series Systems
This section contains release notes of general interest to most users
of the AlphaServer GS Series systems.
6.5.1 AlphaServer GS80/160/320 Systems: Device Restriction
Permanent Restriction
Only one set of the following devices found on the legacy bus adapter is configured and supported per partition in OpenVMS Alpha Version 7.3 or higher. These devices include:
If multiple legacy bus adapters exist, only the adapter that includes
the console port is configured and supported.
6.5.2 OpenVMS Galaxy License Enforcement
V7.3
In an OpenVMS Galaxy computing environment, the OPENVMS-GALAXY license units are checked during system startup and whenever a CPU reassignment between instances occurs.
If you attempt to start a CPU and there are insufficient OPENVMS-GALAXY
license units to support it, the CPU will remain in the instance's
configured set but it will be stopped. You can subsequently load the
appropriate license units and start the stopped CPU while the system is
running. This is true of one or more CPUs.
6.5.3 Installing Licenses
V7.3-1
Before you upgrade to Version 7.3-1 or higher, you should perform the following steps to ensure that the common license database can share license units among hard and soft partitions:
$ SHOW LICENSE /UNIT_REQUIREMENTS /CLUSTER |
The base OpenVMS license allows you to have only one interactive user login per physical system (not per partition). (However, you can always log in from OPA0: in each partition.) For additional interactive users, you will require additional license units. See your HP support representative to determine your needs. |
$ LICENSE REGISTER license-name /ISSUER=DEC - _$ /AUTHORIZATION=USA123456 - _$ /PRODUCER=DEC - _$ /UNITS=1050 - _$ /AVAILABLITY=H - _$ /OPTIONS=(NO_SHARE) - _$ /CHECKSUM=2-BGON-IAMA-GNOL-AIKO |
$ LICENSE MODIFY OPENVMS-ALPHA /INCLUDE=(NODEA, NODEB, NODEC) |
P00>>> P00>>>SHOW SYS_SERIAL_NUM sys_serial_num G2A105 |
If all partition consoles show a blank value for SYS_SERIAL_NUM, you must create a nonzero value of up to 12 characters. Ensure that the system serial number that you create is not used on any other AlphaServer GS80/160/320 on this OpenVMS Cluster. |
P00>>> P00>>>SET SYS_SERIAL_NUM G2A105 |
If your system is part of an OpenVMS Cluster that shares a common license database, anytime you reconfigure the number of hard or soft partitions on your AlphaServer GS80/160/320, you must make sure that all partitions have the same SYS_SERIAL_NUM. |
For partitionable machines that are sharing NO_SHARE licenses across partitions, it is possible to see the following error text on system bootup.
%LICENSE-E-NOAUTH, DEC OPENVMS-ALPHA use is not authorized on this node -LICENSE-F-EXCEEDED, attempted usage exceeds active license limits -LICENSE-I-SYSMGR, please see your system manager Startup processing continuing... |
This error text can be safely ignored. The text is displayed when
someone has logged into a system that is sharing the OPENVMS-ALPHA PAK
and they are then in use. This will be fixed in a future release.
6.5.4 AlphaServer GS60/GS60E/GS140 Multiple I/O Port Module Configuration Restriction
AlphaServer GS60/GS60E/GS140 configurations with more than a single I/O Port Module, KFTHA-AA or KFTIA-AA, might experience system failures.
When upgrading OpenVMS Galaxy and non-Galaxy AlphaServer 8200/8400 configurations with multiple I/O Port Modules to GS60/GS60E/GS140 systems, customers must install one minimum revision B02 KN7CG-AB EV6 CPU (E2063-DA/DB rev D01) module as described in Compaq Action Blitz # TD 2632.
For complete details about this restriction and its solution, refer to
Compaq Action Blitz # TD 2632.
6.6 AlphaStation 200/400: ISA_CONFIG.DAT Changes Required
V7.1
Customers configuring ISA devices on AlphaStation 200/400 Family systems must change their SYS$MANAGER:ISA_CONFIG.DAT file, so that the node information for each device appears at the end of each device description block.
For upgrades from OpenVMS Version 6.2 or 7.0 systems, this change must be made before starting the upgrade procedure. |
Table 6-1 shows the changes to the device description block.
| Before Version 7.1 | After Version 7.1 |
|---|---|
| [AUA0] | [AUA0] |
| NAME=AU | NAME=AU |
| NODE=3 | DRIVE=SYS$MSBDRIVER |
| DRIVER=SYS$MSBDRIVER | IRQ=9 |
| IRQ=9 | DMA=(0,1) |
| DMA=(0,1) | PORT=(388:4,530:8) |
| PORT=(388:4.530:8) | NODE=3 |
Customers using SYS$MANAGER:ISA_CONFIG.DAT files should read
Section A.7.
6.7 AlphaStation 255: PCI Configuration Restriction
V7.1
The OpenVMS Alpha operating system does not support PCI option cards configured in PCI slot 0 on any AlphaStation 255 series systems.
PCI slot 0 is the lowest physical PCI option slot on AlphaStation 255
series systems. The interrupt signal for this slot is shared with the
built-in Ethernet port. Because the OpenVMS Alpha operating system does
not currently permit PCI devices to share an interrupt line, a PCI
device installed in slot 0 will not function correctly or may cause
errors to occur with the built-in Ethernet port. As a result of this
restriction, AlphaStation 255 series systems support a maximum of two
PCI option cards, configured in slot 1 and slot 2.
6.8 ATI RADEON 7000 Graphics (I64 Only)
The following release notes pertain to using the embedded ATI RADEON 7000 graphics adapter on OpenVMS I64 systems.
Note: The resource requirements described in Section 6.9.1 also apply
to the embedded ATI RADEON 7000 graphics adapter.
6.8.1 I64 Graphics Support
V8.2
The only graphics option currently supported on OpenVMS I64 systems is the embedded RADEON 7000 PCI adapter.
The ATI RADEON 7500 PCI graphics adapter will be supported on OpenVMS
I64 Version 8.2 in the near future. Testing is currently in progress.
An announcement will be posted on the following website when support
for this graphics card is available:
6.8.2 Hardware Accelerated 3D Graphics Not Supported on RADEON 7000
V8.2
Hardware accelerated 3D (OpenGL) rendering is not supported on the
embedded Radeon 7000 PCI adapter.
6.9 ATI RADEON 7500 Graphics
V7.3-2
The following notes describe resource requirements, enhancements, fixes, and a few restrictions for ATI RADEON 7500 graphics. If you want to consult the HP DECwindows Motif for OpenVMS documentation set, in particular Managing DECwindows Motif for OpenVMS Systems, you can link to this document and others from the following website:
Note that starting with OpenVMS Version 8.2, the license to use 3D
support is included as part of the OpenVMS license. For details, refer
to Section 6.14.
6.9.1 Resource Requirements
Support for RADEON graphics requires the following system-wide resources:
In addition, each RADEON card requires the following:
The global sections are charged against the GBLSECTIONS system resource, and the 16+ megabytes of global memory are charged against the GBLPAGES and GBLPAGFIL resources.
For example, a single RADEON card requires the following:
These numbers equate to the following values:
| GBLSECTIONS | 5 |
| GBLPAGES | 33376 (GBLPAGES is in units of 512-byte pagelets.) |
| GBLPAGFIL | 2086 (GBLPAGFIL is in units of 8192-byte Alpha pages.) |
A 4-card configuration requires the following:
These numbers equate to the following values:
| GBLSECTIONS | 14 |
| GBLPAGES | 131728 (GBLPAGES is in units of 512-byte pagelets.) |
| GBLPAGFIL | 8233 (GBLPAGFIL is in units of 8192-byte Alpha pages.) |
V8.2
The shareable library SYS$LIBRARY:DECW$OPENGLSHR_RADEON.EXE has been
renamed to SYS$LIBRARY:DECW$MESA3DSHR_RADEON.EXE to reflect that this
library was built from the Mesa 3D code base. The API and functionality
remain the same as in previous releases. The logical name
DECW$OPENGLSHR is defined to point to the shareable library using the
new file specification.
6.9.3 Support Limitations
V7.3-2
The following functionality is not supported:
V8.2
At high resolutions (for example, 1920x1440 and 2048x1536) and high
refresh rates, and under heavy load conditions, video artifacts might
occur on some individual RADEON cards or monitors. If you see such
artifacts, try using a lower refresh rate.
6.9.5 OpenGL Supports IEEE Arithmetic Only
V8.2
The OpenGL library supports only IEEE floating point format; VAX
floating point is not supported. Use the /FLOAT=IEEE_FLOAT option to
compile applications.
6.9.6 DECwindows Server Hangs When Output Is Written to the Graphics Console (OPA0)
V8.2
If output is written to the graphics console (OPA0) after DECwindows has started, the DECwindows server hangs and the screen freezes. Pressing CTRL/F2 allows the DECwindows server to run again.
Instead of writing messages directly to OPA0, HP recommends using OPCOM and the Console Window application to display messages that normally would be written to the console. To enable this application, edit the command procedure SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM and add the following global symbol definition:
$ DECW$CONSOLE_SELECTION == "WINDOW" |
If you do not have SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM, you can create this command procedure from SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.TEMPLATE.
After editing SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM, restart DECwindows with the following command:
$ @SYS$MANAGER:DECW$STARTUP RESTART |
The RADEON 7500 graphics card has two video output ports: one for
digital and one for analog. The digital interface is not currently
supported. However, using a digital-to-analog adapter, you can plug an
analog monitor into the digital port and get the identical output that
you get using the analog port. If you use the digital port, the monitor
must be attached before the system is powered up in order for the port
to function correctly.
6.9.8 Boot Reset Recommendation (Alpha Only)
HP recommends that the console variable
boot_reset
be set to ON.
6.9.9 No Overlay Planes
Hardware overlay planes are not supported.
6.9.10 Single Colormap
The RADEON 7500 graphics controller supports only one hardware colormap. Keep this in mind if you change to the 8-bit color depth, where the default visual is PseudoColor. Attempting to use more than one PseudoColor colormap at a time causes colormap flashing.
3D (OpenGL) rendering is not supported on 8-bit PseudoColor visuals. (See also Section 6.9.16.) |
Applications should not install or deinstall colormaps themselves. The
window manager should perform these actions. However, the application
is responsible for providing the window manager with hints about which
colormaps to install or deinstall. You provide this information using
the Xlib function XsetWMColormapWindows(). This function sets the
WM_COLORMAP_WINDOWS property for a given window.
6.9.11 Single Bit Depth for All Windows
When you are using the RADEON 7500 card, all windows created on a
particular head must have the same bit depth. The RADEON 7500 card
supports bit depths of 8, 16, and 24 bits per pixel on any graphics
head, but once the DECwindows server establishes a bit depth on a
particular head, only windows or visuals with that bit depth can be
created.
6.9.12 Pixel Depth for Read/Write Color Map
By default, the RADEON 7500 provides a pixel depth of 24 planes with a read-only, TrueColor color map. Some applications, such as DECwindows Paint, require a read/write color map. If Paint is run with a read-only color map, it fails with the following error message:
Error: Visual Not Supported
Supported Visuals are {PseudoColor, GrayScale, StaticGray}
|
To use a read/write color map, edit the file SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM (or, if this file does not exist, create it from SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE) and add the following logical name definition to the file:
$ DEFINE/EXECUTIVE/SYSTEM/NOLOG DECW$SERVER_PIXEL_DEPTH 8,8,8,8,8,8,8,8 |
Then restart DECwindows using the following command:
$ @SYS$MANAGER:DECW$STARTUP RESTART |
This change sets the pixel depth to 8 planes (on up to 8 graphics
cards, which allows for a multiple-card configuration) and allows the
server to provide a PseudoColor visual.
6.9.13 Backing Store/Save Unders Not Supported for 3D Windows
The implementation of backing store and save unders in the RADEON 7500
X11 server does not support 3D windows.
6.9.14 Threads Restriction
The RADEON 7500 OpenGL library for OpenVMS is not thread safe. However,
OpenGL can be used in a multithreaded program if the use of OpenGL is
restricted to a single thread within the program.
6.9.15 No Support for Single Buffered Visuals
The RADEON 7500 DECwindows server exports only double buffered visuals.
For single buffering, users must select a double buffered visual and
call
glDrawBuffer( GL_FRONT )
in their application.
6.9.16 No 3D Support for Color Index Mode
Even though 8-bit visuals are supported for 2D operations when the
DECwindows server is started with bit depth = 8, OpenGL rendering is
not supported on 8-bit visuals.
6.9.17 Timer Mechanism
Under certain circumstances, it is possible for a process to be interrupted while it owns the hardware lock, resulting in an apparent DECwindows server hang.
A timer mechanism has been implemented to detect this situation and to rectify it by forcing an image exit in the suspended process --- or, in some instances, by deleting the process.
The timer mechanism can be configured using the following two logicals, which should be specified in the DECW$PRIVATE_SERVER_SETUP.COM file:
The default values are chosen to minimize the impact of the timer on the performance of graphics applications. If you want to reduce the length of time before the DECwindows server begins responding again, you can do so by decreasing the value of DECW$DRM_TIMER_PERIOD.
A process can be interrupted while holding the hardware lock under either of the following conditions:
If neither of these conditions is likely to occur in your configuration, you can disable the timer mechanism entirely by setting the timer period to zero:
$ DEFINE/SYSTEM DECW$DRM_TIMER_PERIOD 0 |
Whenever you change the value of DECW$DRM_TIMER_PERIOD, you must either restart the DECwindows server or reboot the system for the changes to take effect. To restart the DECwindows server, use the following command:
$ @SYS$STARTUP:DECW$STARTUP RESTART |
| Previous | Next | Contents |