=========================================================================
M I C R O F O C U S
V4.1.10
Running Under The DG/UX
Operating System Version R4.11MU03
On The AViiON
=========================================================================
RELEASE NOTES
=============
TABLE OF CONTENTS
=================
INTRODUCTION
ON-DISK DOCUMENTATION
MACHINE REQUIREMENTS
PRINTED DOCUMENTATION
ERRORS FIXED
RESTRICTIONS
KNOWN ERRORS
KNOWN ERRORS IN RELATED SOFTWARE
ENVIRONMENT-DEPENDENT INFORMATION
INTRODUCTION
============
These release notes describe errors and restrictions found in the
software, and give information that was not available when the books
were printed.
Where an entry arose from a problem or enhancement request that has a
reference number, the number is given, to enable Product Support to help
you more quickly if you call. These numbers are called Product
Discrepancy Report (PDR) numbers.
This document is updated at each maintenance release. Entries made at
earlier releases are included if they still relate to the current
release. Subsection headings show the releases when the entries were
first included. Within each subsection, entries are grouped by component,
but there can be more than one group of entries for the same component.
ON-DISK DOCUMENTATION
=====================
Features that are new since the base release of V3.2, and all early
release features, are summarized in the on-disk document called "New
Features".
Information that was not available when the books were produced is given
as follows:
- Where practicable, changes are given as updates to the text of the
books, in the document "Documentation Update Notes".
- Larger changes are documented in separate documents called on-disk
supplements, listed in the document "Supplementary Information".
- Other changes are given in the document "Supplementary Information".
Together with this document, these are called release notes. They are
updated at every maintenance release. Their filenames are:
readme.1 Main Release Notes
dun.1 Documentation Update Notes
sup.1 Supplementary Information
features.1 New Features
MACHINE REQUIREMENTS
====================
o The DG/UX operating system Version R4.11MU03
o AViiON
o The system utilities needed by the various phases of cob, which are
ar nm ld cc as
o At least 5 megabytes of temporary disk space for a single user
The disk space needed increases by the combined size of the
$COBDIR/coblib/libcobol.a file and the COBOL source file for each
additional user.
The temporary disk space that a user needs can increase significantly
during SORT or MERGE operations, as these can create temporary work files
related to the size of the files being sorted or merged.
Temporary work files are put in the directory specified by the
system-defined TMPDIR environment variable. If TMPDIR is not set, the
system default temporary directory is used (as defined by the value of
P_tmpdir in stdio.h).
PRINTED DOCUMENTATION
=====================
Object COBOL V4.1 for UNIX has the following printed manuals:
o Getting Started (Issue 1, August 1996)
o Object COBOL User Guide (Issue 4, August 1996)
o Object COBOL Character Tools (Issue 1, August 1996)
o Dialog System Character Mode User Guide (Issue 5, September 1994)
o Master Index & Glossary (Issue 5, August 1996)
o Programmer's Guide to Writing Programs (Issue 2)
o Programmer's Guide to Creating User Interfaces (Issue 2)
o Programmer's Guide to File Handling (Issue 2)
o Programmer's Guide to Communications (Issue 2)
o OO Programming with Object COBOL (Issue 3)
o DCE Programmer's Guide and Reference (Issue 1)
o Compatibility Guide (Issue 3, April 1993)
o Language Reference (Issue 15, May 1995)
o Language Reference - Additional Topics (Issue 15, May 1995)
o Error Messages (Issue 11, May 1995)
o Pocket Guide (Issue 9, August 1996)
ERRORS FIXED
============
V4.1 is an upgrade to V4.0. This section lists errors fixed since
the base release V4.0.07.
V4.1.10
=======
Enhanced ACCEPT/DISPLAY - Errors fixed
--------------------------- V4.1.10 --
o The prompt character did not appear in mixed/Kanji fields that
contained trailing Kanji spaces.
o An ACCEPT with NOECHO from a panel was displayed the text.
o The wrong (non-Kanji) space character was used in DBCS environments.
o Moving to the start of a mixed field containing Kanji using the
Backtab key caused field corruption when Kanji was entered.
o Backspacing in a PIC N field inserted an ASCII space instead of a
Kanji space.
o Deleting Kanji characters in a mixed field moved a Kanji space into
the right-hand end instead of an ASCII space.
File Handler - Errors Fixed
---------------- V4.1.10 --
o DELETE FILE on an ESDS sequential file left the .idx part behind.
o READs on files assigned to CON did not always work correctly.
Intrinsic Functions - Errors fixed
----------------------- V4.1.10 --
o The SINE/COSINE/TANGENT functions gave inaccurate results for certain
angles. This has been corrected so that the results of these
functions for angles in the range +/- (2* PI) are accurate to 14
decimal places.
Windowing Syntax - Errors fixed
-------------------- V4.1.10 --
o The Windowing Preprocessor produced misaligned code when it
encountered an inline ("*>") comment on the same line as a COPY
statement. When animating, the source displayed was misaligned and
copyfiles were unexpanded.
Compiler (Syntax Check Phase) - Errors fixed
--------------------------------- V4.1.10 --
o Checking a program with either FLAG or FLAGSTD directives along with
the FLAGAS directive sometimes caused an erroneous error message on a
negative-valued COMP-2 item.
o A missing period after a paragraph-name receives no warning message
with OSVS set. This was a OSVS mainframe compatibility issue.
o Sometimes the wrong logic flow occured for an EVALUATE statement when
running generated code.
o The limit for the maximum length of filenames (including path) in the
OUTDD and INDD directives was too small. It has been increased to 80
characters.
o A program using CALL <dataname) syntax and compiled with directives
CHARSET(EBCDIC) and FOLDCALLNAME(UPPER) did not execute correctly at
run time.
o You did not get an error message if an item referenced in the
DEPENDING ON clause of a RECORD VARYING phrase of a file description
entry was defined outside the Working-Storage Section and Linkage
Sections.
o Use of both WRITE ... ADVANCING and WRITE ... POSITIONING on the same
file was allowed with OSVS set. This was a OSVS mainframe
compatibility issue.
o The message given when a specified directives file was not found was
unclear.
Intrinsic Functions - Errors fixed
----------------------- V4.1.10 --
o The SINE, COSINE and TANGENT functions gave inaccurate results for
certain angles. This has been fixed so that for angles in the range
+/- (2* PI) these functions are accurate to 14 decimal places.
Windowing Syntax - Errors fixed
-------------------- V4.1.10 --
o If you comnpiled a program using the windowing preprocessor Window1,
and an error was found in the windowing syntax, a spurious character
appeared in column 73 of the erroneous source line when it was
displayed to the console.
V4.1.06
=======
Compiler (Syntax Check Phase) - Errors fixed
--------------------------------- V4.1.06 --
o A floating point data item with a VALUE 0 clause was erroneously
flagged as being non-mainframe compatible.
o A program containing redefinitions of external data items sometimes
received an erroneous flag saying that the Data Division size had
exceeded the limit.
o In a program checked with CHARSET(EBCDIC), reading a line sequential
file that had an ASCII CODE-SET clause on its File Description
gave corrupted data.
o When the COMP-6 clause was used on a group item, it was not inherited
correctly in all elementary items of groups within that group.
o When using the concatenation character "&" on literals in VALUE
clauses, you could not concatenate them to a total length greater
than 160 bytes (the correct maximum is 2048 bytes).
o An ACCEPT of a subscripted numeric data item gave incorrect results.
o An INITIALIZE statement with qualified data items hung during
checking if its syntax was wrong.
Enhanced ACCEPT/DISPLAY - Errors fixed
--------------------------- V4.1.06 --
o (This would affect you only when using an add-on product.)
When debugging a CICS application using MF370 Animator, an error
200 was reported and the run terminated, when inputting a numeric
from the keypad for the MF370 Animator.
File Handler - Errors Fixed
---------------- V4.1.06 --
o A file status 9/65 was given on DOS if you tried to open a file a
second time in the same run unit, even though you had a LOCK MODE
clause. This happened only if you didn't have share.exe loaded.
o A file status 2/1 was returned if creating a duplicate prime key on
an indexed files who access mode was dynamic. This has been
corrected so that a 2/2 status is returned.
o The wrong record was deleted when prime key the allowed
duplicate values.
o Corruption could occur if keychecking was switched off and the key
definition specified didn't contain the prime key.
o The maximum file-size checks were wrong. This has been corrected so
that the maximum file size is 2 Gig, or 1 Gig if the file is shared.
o If calling EXTFH using the CALL interface, you had to set the current
record length when writing to a fixed length compressed file.
o An indexed file could be corrupted if key checking was switched off,
and two or more clients opened the file at the same time with
different key definitions.
Run-time System - Errors Fixed
------------------- V4.1.06 --
o When key checking is enabled and a duplicate key condition was
encountered a 2/1 error was returned instead of a 2/2 error.
o A unlock record operation caused the current record pointer to
be updated.
o When attempting cross-session animation of a program started by
CBL_EXEC_RUN_UNIT, the Animator could not connect to the started
process.
Windowing Syntax - Errors fixed
-------------------- V4.1.06 --
o The COBOL Windowing syntax preprocessor Window1 did not correctly
handle Tab characters (X"09") in the sourcefiles of copyfiles. This
made checking terminate on meeting a Tab.
Compiler (Syntax Check Phase) - Errors fixed
--------------------------------- V4.1.06 --
o The compiler directive FOLDCALLNAME(LOWER) erroneously mapped system
calls (CBL_ calls) to lowercase, resulting in RTS error 173 ("Called
program file not found in drive/directory") on case-sensitive
operating systems.
o The syntax READ ... INTO <fd-area> was not flagged correctly with
respect to mainframe compatibility.
o A MOVE statement involving a sliding subscripted floating point item
caused a protection violation when executed.
o The directives COPYEXT and OSEXT did not work with null extensions.
o The compiler looped when compiling a program that broke the system
limit for procedure division size. Syntax error 15 ("Procedure
Division too large") was continually produced during the loop.
o The syntax LABEL RECORD IS <item> where item was non-unique was
erroneously flagged as a severe error. This was a OSVS mainframe
compatibility issue.
o The compiler erroneously rejected the use of a non-imperative
statement in the ELSE clause of an ON statement. This was an OSVS
mainframe compatibility issue.
Intrinsic Functions - Errors Fixed
----------------------- V4.1.06 --
o FUNCTION SUM(parameter(ALL)) did not handle tables with more than 255
elements.
O FUNCTION REVERSE did not work for PIC N items (DBCS).
V4.0.20
=======
File handler - Errors Fixed
---------------- V4.0.20 --
o Writing a record longer than 4K to a printer could cause a protection
violation.
o Tab characters on 8-byte boundaries were expanded wrongly in line
sequential files.
o Files could be corrupted when using Fileshare V2 if two or more files
were involved in a transaction, and deletes were being committed, and
one file had a maximum key length > 248 bytes.
Fileshare Version 2 - Errors Fixed
----------------------- V4.0.20 --
o Fileshare Server could hang if started as a background process having
specified the -b Fileshare option.
o Calls to FSMGR with function-code of 2 or 3 could result in
abnormal termination or a hang.
o If a Fileshare log file name, a Fileshare database reference file
name, or a Fileshare password file name was longer than 63
characters, the Fileshare Server could hang on startup when trying to
display it.
Compiler (Syntax Check Phase) - Errors fixed
--------------------------------- V4.0.20 --
o Mainframe compatibility problem. Syntax error message 1002
("Continuation character invalid at this point") had a different
severity to that in IBM VS COBOL II.
o The MOVE statement did not work correctly when the source was
alphanumeric and the target a subscripted floating point item.
o A program that had an END-PERFORM statement but no matching PERFORM
received a correct S-level error message, but also caused some
spurious flagging on following statements.
o An ACCEPT statement with screen items USING subscripted floating
point items did not work correctly.
o The WRITETHROUGH Compiler directive had to be set globally for the
whole program. You can now set it on individual files.
o A Micro Focus-format ACCEPT statement with the RM directive was
erroneously receiving S-level syntax error messages.
o Mainframe compatibility problem. The handling of a comment-entry
after a PROGRAM-ID header was not compatible with IBM OS/VS COBOL.
o Mainframe compatibilty problem. The run-time behavior of an
abbreviated IF statement was not compatible with IBM OS/VS COBOL.
o A comparison of index-names to non-integer data-items was erroneously
accepted. This has been corrected so that it is rejected with a
S-level error message.
o The clause:
ASSIGN <file> to <reserved-word>
allowed in a SELECT statement when the ASSIGN(EXTERNAL) directive is
used, was not being flagged as a Micro Focus extension.
o Mainframe compatibility problem. Comment-entries that would be
allowed in the Identification Division by IBM mainframe compilers
were being rejected.
o With the ERRLIST directive set, the program listing could be laid out
badly because of SKIP, EJECT, or TITLE statements. This has been
corrected so that these statements are ignored if ERRLIST is set.
o If both the ODOOSVS and PROTECT-LINKAGE directives were set, the
program sometimes accessed wrong parts of sliding items in the
Linkage Section.
o Mainframe compatibility problem. Certain COMPUTE ... ROUNDED
statements would give results incompatible with IBM mainframe
compilers when ARITHMETIC(VSC2) was set.
o In a Format 2 (table) SORT, illegal keys were not always rejected
o CSI information was sometimes missing for lines immediately preceding
lines modified by an Integrated Preprocessor.
Run-time System - Errors Fixed
------------------- V4.0.20 --
o When performing a STEP NEXT operation on a C-ISAM after opening the
file you did not get the first record.
o When an OPEN I-O was performed on a C-ISAM file for which more than
the maximum key parts was defined, an incorrect error status was
returned. You will now be returned the correct status of 9/78.
o The byte-stream call CBL_CREATE_FILE did not perform name mapping
correctly.
o Trying to OPEN OUTPUT a nonexistent file via a symbolic link failed.
V4.0.16
=======
Compiler (Syntax Check Phase) - Errors fixed
--------------------------------- V4.0.16 --
o A DISPLAY statement with multpile operands of both PIC X
and PIC G items did not execute correctly at run time.
o The checker was producing incorrect intermediate code for
MOVE statements that had a subscripted source and multiple
targets - with one of those targets being a floating point
item. This resulted in an RTS 114 error at run-time.
o The use of the REDEFINES syntax in a File Description entry
was not being rejected under OSVS mainframe emulation. This
is now correctly flagged as being non-OSVS conforming.
o When using the CURSOR IS <data-item> clause in the SPECIAL-NAMES
paragraph the item may NOT be declared in the LINKAGE SECTION.
This code was being erroneously accepted by the checker - but
is now correctly rejected.
o The syntax 'DISPLAY UPON SYSERR' may only take one operand.
The checker was incorrectly accepting the syntax with
multiple operands and causing unexpected run-time bahaviour.
This syntax is now correctly rejected.
o The Compiler was erroneously accepting EXIT SECTION syntax when
not in a section and EXIT PARAGRAPH syntax when not in a
paragraph. Both these cases now receive severe errors.
o The DEPENDING ON data-item in a file description entry
should only get updated on a sucessful READ. The checker
was erroneously updating this item for all READS.
o The checker now produces a warning message if you use the
INITIATE verb for a report writer name, but miss out an OPEN
statement.
o The OSVS compiler allows PAGE LIMIT ARE and PAGE LIMITS IS.
Checker now accepts this syntax.
o The RETURN statement has a compulsory AT END clause, which was
not being errored when missing. A 585-E Imperative statement missing
error message is now given.
File Handler - Errors Fixed
---------------- V4.0.16 --
o Data was sometimes corrupted when you committed a delete operation
in a transaction using Fileshare V2.
o Opening a null file sometimes caused reads from a non-null file to
continually read the same record.
o An status of 0/0 was sometimes incorrectly returned when writing a
variable-length relative record whose record length was too long to
fit in a file. The correct status of 4/4 is now returned.
o Operation code 0006 was slow if any external filehandling modules
were not linked into an executable file.
o It was not possible to open null indexed files.
o Operation code 0006 on variable-length sequential and relative files
did not set the format field in the FCD. This field is now set to 3.
o When calling Extfh, a read on a sequential file necessitated that the
maximum record length field be set or the record could not be read.
You now only need to set this field when opening the file.
o File corruption sometimes occurred if the IDXDATBUF environment
variable was set when rewriting records in a transaction when using
Fileshare V2. This sometimes lead to a substantial increase in the
size of the files.
o It was not possible to open sequential or relative null files.
o It was not possible to read a fixed-length non-compressed file if you
opened it as a compressed file.
o The current record length was not returned after a read from a
sequential file.
o Unnecessary file seeks sometimes occurred when writing a line
sequential record. This had an adverse effect on performance.
o Opening a heap file caused the physical file to be accessed
unnecessarily.
o Unpredictable behavior occurred when performing Extfh opcode 006 on
an empty C-ISAM file.
o If you performed a READ NEXT operation that resulted in end-of-file,
a subsequent READ PREVIOUS operation failed to read the previous
record.
o If you opened a non-existent file with I-O OPTIONAL, closing the
file, reopening it, then reading a record from it returned
end-of-file.
Indexed File Maintenance Tool - Errors Fixed
--------------------------------- V4.0.16 --
o It was not possible to rebuild LEVEL II V1 index files.
Run-time System - Errors Fixed
------------------- V4.0.16 --
o When an attempt was made to create a file that already existed as a
directory a file locked status was given. This situation will now
cause a 3/7 error to be returned.
o Setting the COBCONFIG tuneable isam_open_key_check to TRUE did not
ensure that all differences in key definitions would be detected.
RESTRICTIONS
============
This section lists restrictions in the current release.
V4.1.10
=======
Compiler - Restrictions
-----------------------
o When using the cob command to compile C programs, the "-Xt" option
is passed to the cc compiler during compilation via the $COBDIR/cobopt
file. This file can be modified if this option is undesirable.
V4.1.06
=======
Common Communications Interface - Restrictions
----------------------------------- V4.1.06 --
o The CCIView trace facility documented in the chapter "CCIView Trace
Facility" of the "Programmer's Guide to Communications" is not
available in this release.
o The CCI module CCIASYNC documented in the chapter "Common
Communications Interface" of the "Programmer's Guide to
Communications" is not available in this release.
V4.0.20
=======
V4.0.16
=======
COBSQL - Restrictions
---------- V4.0.16 --
o COBSQL creates an intermediate file using the same basename as the
source file you supply, adding an extension of .cbl. As a result, if
the source file you supply has the extension .cbl, COBSQL overwrites
it.
Intrinsic Functions - Restrictions
----------------------- V4.0.16 --
o Most intrinsic functions are evaluated using floating-point
operations. These give accuracy of only about 15 significant digits.
Even digits within this range may become meaningless if, for
instance, the difference between two similar numbers is taken as part
of the evaluation.
V4.0.07
=======
Session Recorder, Screens Compare Utility - Restrictions (Toolbox only)
--------------------------------------------- V4.0.07 --
o The Welcome screen containing copyright notices, software version
numbers, and information on how you can access help screens and the
Maphelp facility is not displayed.
See the appendix "UNIX Key Usage Chart" in your Object COBOL User
Guide for details on key mappings.
KNOWN ERRORS
============
This section lists known errors in the current release.
V4.0.20
=======
Windowing Syntax - Known Errors
-------------------- V4.0.20 --
o The Window1 preprocessor (COBOL Windowing Syntax for Text-Based
Systems) cannot handle a copyfile that is terminated by Ctrl-Z or
contains no terminator on the last record. If your text-windowing
application uses such copyfiles the compilation will loop.
V4.0.07
=======
Object COBOL Development Environment Menu System - Known Errors
---------------------------------------------------- V4.0.07 --
o Exiting a function accessed from the Alt or Ctrl menu returns you to
the main Development Environment menu rather than to the Alt or Ctrl
menu.
KNOWN ERRORS IN RELATED SOFTWARE
================================
This section lists known errors in related software affecting the current
release.
V4.0.07
=======
ENVIRONMENT-DEPENDENT INFORMATION
=================================
This section gives information that on your environment supersedes that
in the books.
V4.1.06
=======
V4.0.07
=======
DBCS Transparency Support - Environment-dependent Information
-------------------------------------------------- V4.0.07 --
o For details on using DBCS Transparency Support, see the on-disk
document dbcst.1.
DCE Support - Environment-dependent Information
------------------------------------ V4.0.07 --
o DCE is not supported on this environment.
Installing - Environment-Dependent Information
----------------------------------- V4.0.07 --
o The default path of the directory containing the COBOL system tools
(such as the Compiler and the Generator) is /opt/lib/cobol. You
can set the environment variable COBDIR to specify a different path.
Memory Management - Environment-dependent Information
------------------------------------------ V4.0.07 --
o Use of the malloc() routine from the UNIX library libmalloc.a is not
supported on this environment. Therefore, do not use "-lmalloc" as an
argument to cob or to the system linker when linking with COBOL
objects. Instead, you should use the malloc() from libc.a, which is
the default.
=========================================================================
Micro Focus and Animator are registered trademarks of Micro Focus
Limited.
Object COBOL and Panels Version 2 are trademarks of Micro Focus Limited.
IBM, OS/2 and AIX are registered trademarks of International Business
Machines Corporation.
Microsoft and Windows are trademarks of Microsoft Corporation.
UNIX is a registered trademark of X/Open Company Limited.
SCO is a trademark of The Santa Cruz Operation, Inc.
=========================================================================
@(#)Vrn/readme.1/////07/25Apr97/nrV
Copyright (C) 1992-96 Micro Focus Limited