![[Compaq]](../../images/hp.gif)
![[Go to the documentation home page]](../../images/buttons/hp_bn_site_home.gif)
![[How to order documentation]](../../images/buttons/hp_bn_order_docs.gif)
![[Help on this site]](../../images/buttons/hp_bn_site_help.gif)
![[How to contact us]](../../images/buttons/hp_bn_comments.gif)
![[OpenVMS documentation]](../../images/hp_ovmsdoc_sec_head.gif)
| Document revision date: 31 July 2002 | |
|
|
|
|
|
|
| Previous | Contents | Index |
This chapter contains information on OpenVMS associated products.
For notes about using compilers, linkers, and run-time library
routines, see Chapter 5.
2.1 Layered Product Support
Information about layered product support is available in the Software Public Rollout Reports for OpenVMS. The Software Public Rollout Reports for OpenVMS list the availability of Compaq's software products shipping on the Software Products Library kits (CD-ROM consolidations) for OpenVMS Alpha and OpenVMS VAX.
The reports contain the product name and version, the operating system
version required to support the product, and the volume ship date for
the product. The information in these tables is continually evolving
and is subject to change. The reports are intended for public
distribution and are updated monthly. The information is not provided
in these release notes because of the changing nature of the
information.
2.2 Expectations in Using File-Name Case Sensitivity
V7.3-1
OpenVMS Alpha now supports the option of case-sensitive file name lookup. Case-blind file name lookup is the default behavior, and is the behavior in previous versions of OpenVMS.
This feature is a very significant change in behavior, and cannot be expected to work seamlessly with existing applications. Enabling case-sensitive file name lookup can break existing applications; disabling case-sensitive file name lookup restores the previous behavior. At the same time, case-sensitive operations can be critical in porting some applications (usually from UNIX) that either expect or depend on case sensitivity.
Case-sensitive operations do not work well when case is not preserved. OpenVMS ODS-2 volumes do not support preservation of case in file names. DCL will convert all command line parameters to uppercase, unless the process attribute PARSE_STYLE is set to EXTENDED. The DECC run-time library will modify case for file names unless the DECC$EFS_CASE_PRESERVE parameter is set.
Case sensitivity should be used where case sensitivity is important to the application, in environments that support case preservation. Avoid using case sensitivity with applications not known to support case sensitivity. For example, file names or file types coded into applications developed for a case-blind environment might not match the actual case of files they reference.
Case sensitivity applies to file operations. It is normally enabled as a process attribute (in DCL, SET PROCESS /CASE, or in an application with the SYS$SET_PROCESS_PROPERTIESW service). This attribute affects file system operations made through RMS services, such as $CREATE, $OPEN, and $SEARCH. File operations that use the ACP $QIO interface must code case sensitivity explicitly.
Case preservation affects how file names are stored in the file system. SET PROCESS/PARSE_STYLE determines whether DCL forces file names to uppercase or stores them as they are; similarly, the DECC run-time library and applications can choose to uppercase or preserve file names. With case preservation enabled, file names are put into the file system exactly as entered. However, mixed-case names used in case-blind operations behave very much like traditional uppercase-only file names.
See Section 5.6 for information on compiling C programs with the
case=sensitive
setting.
2.3 ACMS---Applications Not Starting
V7.3-1
ACMS V4.4A applications might fail to start and report "server died unexpectedly." The EXBYTLM error may be reported and increasing BYTLM does not help.
This problem is corrected in an ECO for ACMS V4.4A:
ACMS_U1_044.A
|
You can install the ECO patch on OpenVMS Alpha Version 7.3 and higher either prior to or after installing OpenVMS Alpha V7.3-1.
The problem will also be corrected in ACMS V4.4B, which is scheduled
for consolidated distribution in the Software Products Library for Q3
CY2002.
2.4 ACMS---IVP Failure Due to Server Aborting
V7.3-1
If you install ACMS V4.4A on OpenVMS Alpha V7.3-1, the Installation Verification Procedure (IVP) can fail, reporting that the "server died unexpectedly." This situation also involves EXBYTLM on the process, and increasing the BYTLM does not help.
This problem is corrected in an ECO for ACMS V4.4A called:
ACMS_U1_044.A
|
You can install the ECO patch on OpenVMS Alpha Version 7.3 and higher either prior to or after installing OpenVMS Alpha V7.3-1.
The problem will also be corrected in ACMS V4.4B, which is scheduled
for consolidated distribution in the Software Products Library for Q3
CY2002.
2.5 FMS---ECO Needed to Correct Installation Problem
V7.3-1
When you install FMS on OpenVMS Alpha, a problem occurs during the Sample Application Programs Installation. To correct it, install the following ECO patch after the installation of FMS:
DECFMSECO5024 |
V7.3
In OpenVMS Version 7.3, the time zone database has been updated as follows:
| Time Zone Name | Territory or State |
|---|---|
| Reykjavik | Iceland |
| Turkey | Turkey |
| Time Zone Name | Territory or State |
|---|---|
| Jerusalem | Israel |
| ROK | Republic of Korea |
| Time Zone Name | Territory or State |
|---|---|
| ACT | Australia Capital Territory |
| NSW | New South Wales |
| NT | Northern Territory |
| QLD | Queensland |
| SA | South Australia |
| TAS | Tasmania |
| VIC | Victoria |
| WA | Western Australia |
V7.3
Because of the addition of Extended File Support in OpenVMS Alpha
Version 7.2 you may notice changes in the handling of I/O runtime
diagnostics and RMS special registers on OpenVMS Alpha Version 7.2 and
higher. In particular, a long file name that produced RMS$_FNM under
versions of OpenVMS Alpha prior to Version 7.2 now produces RMS$_CRE on
OpenVMS Alpha Version 7.2 and higher. This difference is reflected in
I/O runtime diagnostics and RMS special registers. You do not need to
use the new ODS-5 support to see these RMS differences.
2.8 DECdfs
This section contains release notes pertaining to DECdfs for OpenVMS.
2.8.1 DECdfs Version 2.3-2 Required for OpenVMS Alpha Version 7.3-1
V7.3-1
To run DECdfs for OpenVMS on OpenVMS Alpha Version 7.3-1, you must install Version 2.3-2. If you install earlier versions of DECdfs on OpenVMS Alpha Version 7.3-1, your system will fail. DECdfs for OpenVMS Version 2.3-2 ships with OpenVMS Version 7.3-1.
DECdfs Version 2.3-1 or higher is required for OpenVMS Version 7.3. It
is recommended that earlier versions of OpenVMS also run at least
DECdfs Version 2.3-1 (see Section 2.8.2).
2.8.2 DECdfs Version 2.3-1 or Higher Recommended on Other Versions of Systems Running DECnet-Plus for OpenVMS
V7.3
DECdfs Version 2.3-1 or higher contains corrections for a number of connection-related issues when running on a system with DECnet-Plus --- particularly on systems with multiple network circuits. Therefore, DECdfs Version 2.3-1 or higher is highly recommended for any supported system running DECnet/OSI or DECnet-Plus.
In addition, DECdfs Version 2.3-1 added support for DECnet-over-IP
connections. For more information, please refer to the release notes in
SYS$HELP after the product installation.
2.9 New Versions of Availability Manager and DECamds Software
V7.3-1
To monitor OpenVMS Alpha Version 7.3-1 nodes, use one of the following:
These software versions are part of the OpenVMS Alpha Version 7.3-1 software kit.
The following software versions will not monitor OpenVMS Alpha Version 7.3-1 nodes:
V7.3-1
Perform the following tasks to enable Compaq DECforms Web Connector V3.0 to run on OpenVMS Version 7.3-1:
$ @sys$common:[JAVA$122.COM]JAVA$122_SETUP.COM |
This section contains release notes about DECram.
2.11.1 DECram Commands and Errors
V7.3-1
It is important to check for disk errors after issuing any DECram
command, because not all errors are returned to the user interface.
Errors specific to a device are sent to the system error log. Type SHOW
DEVICE MD at the DCL prompt to see if any device errors were generated
as a result of a DECram command. You will need to use an error log
analyzer tool to recover the error. Errors are logged in ASCII file
format; you can search for errors with an MD-E-FAILURE prefix in the
SYS$SYSROOT:[SYSERR]ERRLOG.SYS file.
2.11.2 DECram and Volume Shadowing
V7.3-1
DECram Version 3.1, using Volume Shadowing for OpenVMS, can shadow a
DECram disk to a physical disk. However, be aware that in the current
implementation of Volume Shadowing for OpenVMS, if the physical disk
goes away, you will be writing to a volatile disk. A mechanism that
will "freeze writes" if the physical disk goes away is
planned for a future release of Volume Shadowing for OpenVMS.
2.11.3 Earlier Versions of DECram
V7.3-1
DECram Version 3.1 runs on OpenVMS Alpha systems, including Galaxy configurations, running OpenVMS Alpha Version 7.2-1H1 or higher. DECram Version 3.1 and supporting documentation are included on the Software Products Library and the Online Documentation Library CD-ROMs.
DECram Version 2.5 runs on all versions of OpenVMS for both VAX and Alpha systems, including Version 7.3-1. Version 2.5, like Version 3.1, uses IOPOST_LOCAL postprocessing and allocates memory across Resource Affinity Domains (RADs).
Version 2.3 does not have the most recent corrections in device drivers.
The following table summarizes OpenVMS support for versions of DECram:
| DECram Version |
Supported on OpenVMS Alpha Versions |
Supported on OpenVMS VAX Versions |
|---|---|---|
| V3.1 | V7.2-1H1 and higher | No |
| V2.5 | All | All |
| V2.4 | V7.2-1 | V6.2--V7.3 |
| V2.3 | V6.2-1H3 | V5.5-2 |
The following sections contain release notes pertaining to the LDAP API.
2.12.1 The Routine ldap_get_option Returns Error -1 When ld Is NULL
V7.3
Using a value of NULL for the
ld
parameter in a call to
ldap_get_options()
results in an error of -1 being returned, rather than the routine
returning a set of global default data.
2.12.2 The Routine ber_flatten() Fails to Detect Mismatched Braces
V7.3
The routine
ber_flatten()
does not correctly detect the situation where '{' and '}' format
modifiers in a BerElement are incorrectly matched.
2.13 DECwindows Motif
This section contains release notes pertaining to the Compaq DECwindows
Motif for OpenVMS layered product.
2.13.1 System Parameter Values Required for Installation
V7.3-1
The installation procedure for DECwindows Motif for OpenVMS Version 1.2-6 can fail if the values for the GBLPAGES, FREE_GBLPAGES, and CLISYMTBL system parameters are set too low.
The installation fails with the following error:
%SYSTEM-W-NOSUCHFILE, no such file \sys$library:decw$xlibshr.exe\ |
If the installation fails, set these parameters to the minimum values shown in the following table, then reinstall the product.
| GBLPAGES | FREE_GBLPAGES | CLISYMTBL | |
|---|---|---|---|
| Alpha | 150000 | 92000 | 512 |
| VAX | 62000 | 47000 | 265 |
V7.3-1
Support for user-written network transports will be discontinued with the next release of DECwindows Motif for OpenVMS Alpha. Compaq DECwindows Motif for OpenVMS Alpha Version 1.3 will include significant changes in the transport interface to support multithreading and the communication needs of the Inter-Client Exchange (ICE) protocol, Font server, and Input Method server.
All existing transports (DECNET, TCPIP, and LOCAL) will remain available and function as expected. However, Compaq will no longer provide support for designing and implementing user-written transports based on the updated transport interface. As a result, the VMS DECwindows Transport Manual will be archived and the new libraries will not be documented or made available publicly.
If you have implemented a custom transport and want to migrate that
transport to the Compaq DECwindows Motif for OpenVMS Alpha Version 1.3
environment, contact your Compaq customer representative to develop a
migration strategy.
2.13.3 DECwindows Language Variants Not Available in Some Versions
V7.3
Language variants are not available for Compaq DECwindows Motif for
OpenVMS Version 1.2-6. The Japanese and German variants are available
for DECwindows Motif Version 1.2-5, and the Hebrew variant is available
for DECwindows Motif Version 1.2-4. Consult your Compaq support
representative for more information.
2.14 MultiNet Version 4.3
Users of Process Software MultiNet Version 4.3 (or earlier) who are also using DCE should install the UCXDRIVER-041_a043 (or higher) ECO from Process Software. MultiNet Version 4.4 includes the fix.
Refer to the following web site to obtain the most recent patch and any dependencies for your version and/or contact Process Software Technical Support:
V7.3
During installation of Open3D on OpenVMS Alpha Version 7.3 or higher, an older version of the SYS$LOADABLE_IMAGES:SYS$GYCDRIVER.EXE image is installed. Before you install Open3D on OpenVMS Alpha Version 7.3 or higher, perform one of the following tasks:
$ RENAME SYS$LOADABLE_IMAGES:SYS$GYCDRIVER.EXE;-1 ;0 |
V7.3
After upgrading OpenVMS, you should reinstall Compaq Pascal to produce new versions of STARLET.PAS and other definition files to match the upgraded system.
If you do not reinstall Compaq Pascal after upgrading OpenVMS, the
compiler on your system will still work correctly. However, STARLET.PAS
and the other definition files will not contain any new or corrected
definitions supplied by the OpenVMS upgrade.
2.17 DEC PL/I---RTL Support for OpenVMS
There is a known incompatibility between the PL/I RTL distributed with the OpenVMS operating system and the more recent PL/I RTL owned and distributed by Kednos Corporation. The older version shipped with the OpenVMS operating system may overwrite a newer version. The image in question is SYS$LIBRARY:DPLI$RTLSHR.EXE.
OpenVMS distributes the following version of the file, which can be identified by using the ANALYZE/IMAGE command:
Image Identification Information
image name: "DPLI$RTLSHR"
image file identification: "V4.0-6"
|
If you perform an ANALYZE/IMAGE command before upgrading to OpenVMS Version 7.3 or higher and find a newer version of DPLI$RTLSHR.EXE, you can either copy it and restore it after the upgrade or reinstall the PL/I kit afterward.
Any questions about DEC PL/I and VAX PL/I should be directed to Kednos Corporation at the following address:
Kednos Corporation
1051 Rodeo Road
Pebble Beach, CA. 93953
Phone: (831) 373-7003
Email: tom@kednos.com
V7.3-1
On all versions of OpenVMS 7.2-1 and above, Web-Based Enterprise Services (WEBES) 4.0 processes can fail with a stack overflow or bugcheck during installation, and during operation before the latest Service Pak is applied. This problem has not been observed on OpenVMS Alpha Version 7.3-1. Similar problems are possible with other multithreaded applications that use sockets and Java 2 Fast VM.
The following stack overflow and bugcheck messages resulted from attempts to run WEBES, Version 4.0 with Service Pack 1, 2, or 3 in this environment. The problem has been corrected in Service Pack 4 for WEBES Version 4.0.
%SYSTEM-F-STKOVF, stack overflow, PC=FFFFFFFF804830F8, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
0 0000000000000000 FFFFFFFF804830F8
PTHREAD$RTL 0 00000000000470D0 000000007BC130D0
0 FFFFFFFF800EE4B4 FFFFFFFF800EE4B4
0 0000000000000000 FFFFFFFF80081898
PTHREAD$RTL 0 00000000000470D0 000000007BC130D0
|
Further lines referencing PTHREAD$RTL follow:
%DECthreads bugcheck (version V3.15-267), terminating execution. % Reason: selected a non-ready thread -2 (0x0000000000261B40) state blocked % Running on OpenVMS V7.2-1 on AlphaServer 1200 5/533 4MB, 256Mb; 2 CPUs % The bugcheck occurred at 01-AUG-2001 13:39:20.48, running image % PEAKSI$CBL200:[SYS0.SYSCOMMON.COMPAQ.SVCTOOLS.][JRE.122.BIN]JAVA$JAVA.EXE;1 % in process 0000301A (named "_FTA14:"), under username "ISLANDS". AST % delivery is enabled for all modes; no ASTs active. Upcalls are enabled. % Multiple kernel threads are enabled. % The current thread sequence number is -2, at 0x00261B40 % Current thread traceback: % 0: PC 0x7BBEBB38, FP 0x0025F9A0, DESC 0x7BBCDBE8 % 1: PC 0x7BBE9F24, FP 0x0025FA70, DESC 0x7BBCD6A8 % 2: PC 0x7BBE7CDC, FP 0x0025FAE0, DESC 0x7BBCD788 % 3: PC 0x7BC12688, FP 0x0025FB80, DESC 0x7BBD2C10 % 4: PC 0x800EE48C, FP 0x0025FC10, DESC 0x80CC68C0 % 5: PC 0x800DABBC, FP 0x0025FC90, DESC 0x80CC4140 % 6: PC 0x7BC17578, FP 0x0025FCB0, DESC 0x7BBD30E0 % 7: PC 0x7BC0B5A8, FP 0x0025FCD0, DESC 0x7BBD1BB0 % 8: PC 0x7BC0A720, FP 0x0025FD00, DESC 0x7BBD1BE8 % 9: PC 0x7BBFD2FC, FP 0x0025FDA0, DESC 0x7BBD00A8 % 10: PC 0x7BBED504, FP 0x0025FFE0, DESC 0x7BBCE480 % 11: PC 0x00000000, FP 0x7AF73A60, DESC 0x7BBCC4B0 % 12: PC 0x848E3414, FP 0x7AF77B30, DESC 0x848E5CF0 % 13: PC 0x7B04552C, FP 0x7AF77BB0, DESC 0x7B01C330 % Bugcheck output saved to pthread_dump.log. %SYSTEM-F-IMGDMP, dynamic image dump signal at PC=000000007BBEBC98, PS=0000001B |
These messages are recorded in the following file:
SVCTOOLS_HOME:[LOGS]DESTA_DIR.LOG |
Workaround
The following procedure prevents this problem from occurring:
$ THREADCP/DISABLE=MULTI SVCTOOLS_HOME:[JRE.122.BIN]JAVA$JAVA.EXE $ PRODUCT REMOVE WEBES |
Do you want to add DESTA$STARTUP and DESTA$SHUTDOWN to system startup and shutdown procedures? [YES] |
$ THREADCP /DISABLE=MULTI SVCTOOLS_HOME:[JRE.122.BIN]JAVA$JAVA.EXE |
| Previous | Next | Contents | Index |
|
|
| privacy and legal statement | ||
| 6652PRO_002.HTML | ||