OSF-AXP DCARTL211 DEC OSF/1 AXP V2.0, V3.0 COBOL RTL ECO Summary
Copyright (c) Digital Equipment Corporation 1994. All rights reserved.
OP/SYS: DEC OSF/1
COMPONENT: DEC COBOL Run-Time Library for DEC OSF/1 Systems
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: DCARTL211
ECO Kits Superseded by This Kit: None
ECO Kit Approximate Size: 2620 Blocks (tar file)
Kit Applies To: DEC OSF/1 V2.0, V3.0
System Reboot Necessary: No
ECO KIT SUMMARY:
An ECO kit exists for the DEC COBOL Run-Time Library on DEC OSF/1 V2.0
through V3.0. This kit addresses the following problems:
o If you declare the FILE STATUS variable within a record such
that its characters span two quadwords, the second character of
the variable is not updated after the execution of an I-O verb.
o If your application contains any extended ACCEPT or DISPLAY
statements and your application displays escape sequences when
the cursor is in the lower right corner of the screen, you may
see the screen scroll unexpectedly.
In an attempt to correct this problem, this release of the DEC
COBOL Run Time Library no longer advances to the next line when
the cursor is past the rightmost column of the screen and the
src-item begins with an escape sequence.
o If your application performs an ACCEPT WITH CONVERSION of a
JUSTIFIED data item, the resulting value is not
right-justified.
o When your application mixes OPEN INPUT and OPEN OUTPUT
operations on multiple-reel, multiple-file tapes without the
use of the MULTIPLE FILE TAPE syntax, the potential exists to
corrupt files.
The sequence of events which cause this corruption to occur are
as follows:
- your application performs an OPEN INPUT of a file which
spans multiple reels
- when the current reel is not the last reel, the file is
closed with NO REWIND
- the next operation on the tape drive is an OPEN OUTPUT NO
REWIND
- a tape swap is performed, and the file is created at the
beginning of the tape, overwriting the contents of the
existing file
o If you open a non-indexed file in OUTPUT mode, the resulting
file access does not grant write access to group.
o Files open in INPUT mode no longer acquire a record lock during
a READ operation no matter what ALLOWING clause is specified.
This is consistent with automatic record locking; with DEC
Cobol and VAX Cobol behavior on OpenVMS; and with X/Open record
locking concepts.
Related to the above item, for INDEXED files, ALLOWING READERS
has always been unsupported on this platform and was always
treated as "NO OTHERS". Now it is downgraded to "ALLOWING ALL"
if the file is opened in INPUT mode.
o READ operations for INDEXED files do not detect a locked record
when a lock is not requested (ALLOWING ALL or WITH NO LOCK). A
hard lock condition only occurs if a lock is requested (e.g.
ALLOWING NO OTHERS, WITH LOCK, automatic). Detecting a lock
should not be dependent on requesting a lock.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
dcartl211_cobotl_rtl.README
dcartl211.CHKSUM
dcartl211.tar
|
