1. CCC - CODASYL COBOL COMMITTEE and ANSI (was: OO COBOL - What if ???
2. OO-COBOL for Unisys IX (was: If you were inventing CoBOL...)
This is a misunderstanding. OO-COBOL is not a preprocessor for UCOB. At
least according to the manuals, you could use OO-COBOL _instead_ of UCOB, and
providing all the extensions like Embedded SQL, DMS access, and IBM Tape
processing.
The PC produces intermediate code which is sent to the host and is
processed there by @OCOB, with an O, not by @UCOB. @OCOB produces an Omnibus
which could be directly @XQTed or @LINKed.
The transfer of this intermediate code from the NT-workstation to the
host is done automatically by the workstation program.
Probably the compiler licenced from Hitachi is to much tied into WinNT
that it can easily be ported to OS/1100.
Also, I think that a workstation based editor can be more productive --
OO-COBOL comes with a COBOL editor with syntax highlighting, and I doubt that
this can be done as effectively with @IPF. See Vol. 4 of the OO-COBOL manuals
(publication number 7851 5855-001).
Yours,
L. Willms
------------------------------ all rights reserved ------------------------
3. OO Design Kernels: Fusing OO Cells + OO Life Blood
4. Support Open & GCC-COBOL (was: New Cobol compiler written in Cobol)
6. Thoughts on teaching OO concepts to COBOL programmers
8. IBM, OO COBOL and related IBM products (was: Reasonably pricedCOBOL products
9. OO and "mainframes" (was: If you were inventing CoBOL...)
10. Parallelism between computer science and experience WAS: SQL wrapper in OO cobol
11. S013-C0 while compiling OO COBOL program using a job step.
12. OT Golf WAS CoBOL moved to OO
13. IBM COBOL & REENTRANT code (was: Confessions of an "OO Foreigner"
14. XML and OO COBOL