There are 2 other files named cbl12c.bwr in the archive. Click here to see a list.
COBOL.BWR -- Beware file for COBOL-74 version 12C
COPYRIGHT (C) 1985 BY
DIGITAL EQUIPMENT CORPORATION, MAYNARD, MASS.
THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE USED AND COPIED
ONLY IN ACCORDANCE WITH THE TERMS OF SUCH LICENSE AND WITH THE
INCLUSION OF THE ABOVE COPYRIGHT NOTICE. THIS SOFTWARE OR ANY OTHER
COPIES THEREOF MAY NOT BE PROVIDED OR OTHERWISE MADE AVAILABLE TO ANY
OTHER PERSON. NO TITLE TO AND OWNERSHIP OF THE SOFTWARE IS HEREBY
THE INFORMATION IN THIS SOFTWARE IS SUBJECT TO CHANGE WITHOUT NOTICE
AND SHOULD NOT BE CONSTRUED AS A COMMITMENT BY DIGITAL EQUIPMENT
DIGITAL ASSUMES NO RESPONSIBILITY FOR THE USE OR RELIABILITY OF ITS
SOFTWARE ON EQUIPMENT WHICH IS NOT SUPPLIED BY DIGITAL.
COBOL.BWR -- Beware file for COBOL-74 version 12C Page 2
1. Differences between 12B and 12C
COBOL-74 has been changed to conform to the standard so that if a file
is opened for I/O the file must already exist. The file will no
longer be created.
The default for WRITE without any advancing information is different
between COBOL-68 and COBOL-74. This is not a change, but the COBOL-74
documentation has been changed to correctly state that the default is
AFTER ADVANCING 1 LINE.
2. Extra carriage-return problem
To comply with Federal regulations for a FIPS certified compiler the
following "feature" had to be provided. In general, if a record was
written with WRITE AFTER ADVANCING and the next record was written
with WRITE BEFORE ADVANCING, then the first record must be overprinted
by the next record. In particular, if the last record in file-1 was
written with WRITE AFTER ADVANCING and the first record in file-2 was
written with WRITE BEFORE ADVANCING and file-2 was output to the same
device (e.g. a LPT:) immediately after file-1, then the last record
of file-1 must be overprinted by the first record of file-2. The FCTC
has a test which does just that.
Clearly we need an extra carriage-return between the two records. The
two choices were, put it at the front of the BEFORE ADVANCING file, or
at the end of the AFTER ADVANCING file. We chose the latter since we
believe it is the less common case (even though it is the default in
COBOL-74) and an extra carriage-return will do less harm at the end of
If, for some reason, you do not wish this "feature" then you can edit
CBLIO.MAC to remove it. At location NOXCR. replace the current
instruction by a JFCL. Note that we cannot support this change as it
violates the Federal standard.
3. COBOL-74 old REL files
At the REL file level if anyone keeps COBOL REL files except in a LINK
library file), the only problem is with COBOL-74 and COBDDT. The
compiler output of Debug paragraph names was changed to be identical
with COBOL-68. This means that COBDDT V12C would display an incorrect
paragraph name for a COBOL-74 paragraph compiled with COBOL-74 V12A.
We do not think that this is a problem since people tend to recompile
before debugging, and working library files should not need to be
debugged again. In any case all that has to be done is to recompile.
4. COBOL 12A and COBDDT 12C incompatibility
Except for the above-mentioned problem, all programs compiled with
version 12A of COBOL can be debugged with COBDDT 12C with no problems.
However, COBDDT 12C supports qualification of variables by specifying
the filename (e.g. "DISPLAY A IN FILE-1"). This is a feature of
COBDDT 12C which was not supported by COBDDT 12A, and compiler support
needed to be implemented. Thus you cannot use this new feature of
COBOL.BWR -- Beware file for COBOL-74 version 12C Page 3
COBDDT 12C until you recompile the program module using COBOL 12C.
COBOL.BWR -- Beware file for COBOL-74 version 12C Page 4
[End of CBL12C.BWR]