From: segaloco via TUHS <tuhs@tuhs.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Bell COBOL Environment?
Date: Thu, 13 Jul 2023 19:02:16 +0000 [thread overview]
Message-ID: <pWmLRW7VpFE32jHYpoVI0_BJh8AyaGTy_u2wCaxS5RAWvJvaTSo6NGAp7LIOG_Ll1ghrWszx8v4jC5NcDzpZJxIxigIvrlKevUAO7zMs6jg=@protonmail.com> (raw)
Reading through [1], there are documents offered by AT&T for the "Level II COBOL" system, which some further research indicates is a product from Convergent (same folks as the UNIX PC.) There's also the LPI-COBOL which appears to be a Language Processor Inc. product.
Are these the earliest AT&T endorsed COBOL solutions for UNIX or were there other efforts either promoted by Bell or even perhaps developed locally that were in any use before this version? Or otherwise is there any other family of ubiquitous UNIX COBOL tools that was in use in the 70s and early 80s, before the timeframe of this document?
Additionally is anyone aware of any surviving code or binaries of either of these or other, earlier efforts at COBOL on UNIX? I have no goal for this information in mind yet, but just gathering details at this point. Thanks all!
- Matt G.
[1] - http://bitsavers.org/pdf/att/000-111_ATT_Documentation_Guide_Nov87.pdf
next reply other threads:[~2023-07-13 19:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 19:02 segaloco via TUHS [this message]
2023-07-13 20:34 ` [TUHS] " Clem Cole
2023-07-13 20:50 ` Arrigo Triulzi via TUHS
2023-07-13 21:41 ` Kenneth Goodwin
2023-07-13 23:02 ` Clem Cole
2023-07-13 23:19 ` KenUnix
2023-07-13 21:42 ` Jon Forrest
2023-07-13 22:35 ` segaloco via TUHS
2023-07-13 23:20 ` Warner Losh
2023-07-14 0:20 ` Bakul Shah
2023-07-14 1:16 ` Alan D. Salewski
2023-07-14 1:05 ` David Arnold
2023-07-14 1:45 ` Clem Cole
2023-07-14 2:14 ` Dan Cross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='pWmLRW7VpFE32jHYpoVI0_BJh8AyaGTy_u2wCaxS5RAWvJvaTSo6NGAp7LIOG_Ll1ghrWszx8v4jC5NcDzpZJxIxigIvrlKevUAO7zMs6jg=@protonmail.com' \
--to=tuhs@tuhs.org \
--cc=segaloco@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).