Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
ALPBASR03_062 Alpha V6.2x BASIC Run-Time Library ECO Summary
Copyright (c) Compaq Computer Corporation 1996, 1999. All rights reserved.
Modification Date: 18-MAY-1999
Modification Type: New Kit
This kit supersedes ALPBASR02_070 for
OpenVMS Alpha V6.2x only.
PRODUCT: OpenVMS Alpha
COMPONENT: BASIC Run-Time Library (BASRTL)
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: ALPBASR03_062
ECO Kits Superseded by This ECO Kit: ALPBASR02_070 (For OpenVMS
Alpha V6.2, V6.2-1H1, V6.2-1H2
and V6.-2-1H3)
ALPBASR01_070
ALPBASR02_062
ALPBASR01_062
ECO Kit Approximate Size: 1152 Blocks
Kit Applies To: OpenVMS Alpha V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3
System/Cluster Reboot Necessary: No
Installation Rating: INSTALL_3
3 - To be installed on all systems running
the listed versions of OpenVMS which
are experiencing the problems described.
Kit Dependencies:
The following remedial kit(s) must be installed BEFORE
installation of this kit:
None
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 DEC$BASRTL.EXE OpenVMS Alpha V6.2 through
V6.2-1H3. This kit addresses the following problems:
Problems address in ALPBASR03_062:
o The BASIC function DATE$() formats the year as only two
digits.
o An incorrect SCAFACINT message appears when ASTs are used.
o A BASIC output routine, when run in BATCH, does not properly
account for international characters (high-bit-on). This
problem causes a variety of strange output, depending on how
many such characters are being printed. For example, if the
command
PRINT STRING$(999%,ASCII("é"))
is run in batch (BASIC V3.4), the error "%BAS-F-MEMMANVIO,
Memory management violation" occurs.
o Under DEC BASIC with DEC$BASRTL V01-017, error #35, "Memory
Management Violation", is incorrectly issued when a second
open statement is used to connect an I/O stream to a remote
file already opened. The correct error would be error #12,
"Fatal System I/O Failure".
Below is an example for a file to be opened twice over the
network, so that a secondary access to the same data is
created.
Assume that "ixfile" is a logical name defined to point to a
file on another node. The second open statement returns BASIC
ERR=35, which cannot be trapped, so the program must abort.
MAP (ixfile) STRING the_item
! First, create a sample file.
OPEN "ixfile" FOR OUTPUT AS FILE #1, INDEXED FIXED, &
PRIMARY KEY the_item, MAP ixfile
CLOSE #1
! Open the newly created file.
OPEN "ixfile" FOR INPUT AS FILE #1, INDEXED FIXED, &
ACCESS READ, ALLOW MODIFY, MAP ixfile
! Attempt to open the same file and connect an I/O stream to
the remote file ! already opened (ERR=35 will result)
OPEN "ixfile" FOR INPUT AS FILE #2, INDEXED FIXED, ACCESS &
READ, ALLOW MODIFY, MAP ixfile, CONNECT #1
o Under some conditions, a traceback list from a fatal error in
a DEC BASIC program indicates some incorrect line numbers.
Also, certain I/O failures report the wrong error code due to
an I/O error recovery problem.
NOTE:
In order to get the full effect of this fix, the
ALPTRAC02_062 kit should be installed.
Problems addressed in ALPBASR02_070 for OpenVMS Alpha V6.2x:
o A BASIC program may ACCVIO or hang in an infinite loop in
DEC$BASRTL if AST calls a BASIC routine.
Problems addressed in ALPBASR01_070:
o The last build got a link warning from another facility.
Problems addressed in ALPBASR02_062:
o Did not properly account for linked chain of XABs, some of
which needed virtual memory to be freed.
Problems addressed in ALPBASR01_062:
o Matrix multiply of D-Float types always produces integer
results.
o The lib$signal of an error produced a fatal and aborted
program, preventing other handlers' recovery.
o Lib$signal caused program to lose local dynamic store, and
execute incorrect code.
RELATED ARTICLES:
Detailed articles describing the problems listed above may exist in
the OPENVMS and BASIC database. To view these articles, open the
appropriate product database and perform a query using either of the
following search strings: 'ALPBASR03_062' or 'ALPBASR'.
ECO KIT ORDERING INSTRUCTIONS:
If after an evaluation you wish to obtain this kit, request it
electronically using the appropriate Advanced Electronic Services
(AES) Service Tool. If you are not familiar with how to request
kits electronically, open the DIA, WIS or DSNLINK database and
review the article entitled:
[AES] How To Electronically Request ECO Kits Using Service Tools
INSTALLATION NOTES:
The system does not need to be rebooted after this kit is installed.
However, if you have other nodes in your OpenVMS VMScluster, they
should be rebooted or you should install this kit on each system in
order to make use of the new image(s).
==========================================================================
| Table of Kit Image Information |
+----------------------------+----------+-----------------+--------------+
| | Overall | Image File | Image Link |
| Image Name | Checksum | Identification | Date/Time |
+----------------------------+----------+-----------------+--------------+
| DEC$BASRTL.EXE | 30FE8EC5 | V01-020 | 5-FEB-1999 |
| | | 16:16:36.06 |
+----------------------------+----------+-----------------+--------------+
|
