From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HTML_FONT_LOW_CONTRAST,HTML_MESSAGE,MAILING_LIST_MULTI, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 7858 invoked from network); 13 Jul 2023 20:35:02 -0000 Received: from minnie.tuhs.org (50.116.15.146) by inbox.vuxu.org with ESMTPUTF8; 13 Jul 2023 20:35:02 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id E7A9442A69; Fri, 14 Jul 2023 06:34:55 +1000 (AEST) Received: from mail-ua1-x931.google.com (mail-ua1-x931.google.com [IPv6:2607:f8b0:4864:20::931]) by minnie.tuhs.org (Postfix) with ESMTPS id DE7C442A68 for ; Fri, 14 Jul 2023 06:34:44 +1000 (AEST) Received: by mail-ua1-x931.google.com with SMTP id a1e0cc1a2514c-7996e265b4dso285823241.2 for ; Thu, 13 Jul 2023 13:34:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ccc.com; s=google; t=1689280483; x=1691872483; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=0q8uBhBI22oYYGOL3NtYXLs08q/TyXiE9sGgchmoTm4=; b=q9k33nxvSFidzqM7ZfUXtCdeKuvo3P9QrGxuwHAPH4OscKkw7scRWSUj6xxzQWT2Cw oXzFPdu3bVf/iOqSY1U8jE0rUNNpqzPFs+Q1n6C86UP5NJuPv6BI3qCqWU0ALkpeAOuW pItVYR4PiDE4qvfZCYTQjtt4AIHfuIWsC6Vy0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689280483; x=1691872483; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=0q8uBhBI22oYYGOL3NtYXLs08q/TyXiE9sGgchmoTm4=; b=avyGSQFJEoO5SMW5U0a+7SnzaPI63tuyD+DXhPC2VSHvd268ScR9yy//bm7PEaYac9 EG7J0jDgl545vbfipRKOiOBNBDd66ThaJpqH4d4hVmutVCrd2bj2xX2hLqp3aGgaD+LV kstkpQg5Yxzj0T8ee9Bk87SKOLhcs3L83E9ig/EgQMkNeinPXr6l3Kxemy0l7tL8ZaeY mKrzdrgPxS16x7VNobJFXGk+NdGNQVlm9GGYNPHCKuCekL3ox8wI/p0fHdVDlWA4rZnL jeHlhFDtEcTZ8izLlNpSB6W5/A0PIURGFAxGmLcndMuBK+86BIAZtT94q22Ft2bb0Fdi 0nnQ== X-Gm-Message-State: ABy/qLYgFsvjLLGguNzyV1GrME7g9Lxw6uTrTOCF3BzrOILgwbcBdO02 PGZNZiZOKb51ZDMGGYzM/ynji1VDQGEbrEYcWflTk69ejYDukG+cA5s= X-Google-Smtp-Source: APBJJlFxTGEkjyKFavutSeHoICeI7Azm5fjr5b9j3YQL9tbUtNjfM3/TZ5r+HDYqGZm6JwGV+idXzV6wsEOV5EQ3kMQ= X-Received: by 2002:a05:6102:147:b0:443:6457:10e with SMTP id a7-20020a056102014700b004436457010emr1940125vsr.7.1689280483515; Thu, 13 Jul 2023 13:34:43 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Clem Cole Date: Thu, 13 Jul 2023 16:34:06 -0400 Message-ID: To: segaloco Content-Type: multipart/alternative; boundary="00000000000025792206006443a2" Message-ID-Hash: VHP2UNE4BFHNPUPHJD5DXFW2E4SPBICT X-Message-ID-Hash: VHP2UNE4BFHNPUPHJD5DXFW2E4SPBICT X-MailFrom: clemc@ccc.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: The Eunuchs Hysterical Society X-Mailman-Version: 3.3.6b1 Precedence: list Subject: [TUHS] Re: Bell COBOL Environment? List-Id: The Unix Heritage Society mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --00000000000025792206006443a2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Matt - I never had direct (user) experience with it. I saw a demo of LPI's product at a trade show. It might have run on Ultrix, but if it did, I have no memory of it being in the test suite we used for releases. Also, I do not remember if LPI-Colbol was attached to a specific DB implementation or not. In those days, there were a number of them besides Ingres - Informix, IBM's DB2, and one that started with an S - which later was sold to Microsoft to become SQL-server to name a few, and that may have been part of it. But there were bundled applications for different markets (running a dentist's office, car dealership, store, restaurant, *etc*..) that ran on small UNIX boxes and used those DBs. What I remember was that only a few firms were offering Cobol for UNIX (I think that IBM, DEC, DG, and maybe NCR had them from previous OSses), but the new generation of UNIX boxes did not - although 3rd parties like LPI sometimes offered them. Since it looks like AT&T is naming it/offering it with their product, that is another example of AT&T management missing the market. AT&T's management (Charlie Brown) was interested in going after IBM and probably thought that Cobol was important if they sold to IBM shops= . The problem was that except for some really large 'Big Blue' places that never bothered tossing out Cobol (like Wall Street and some insurance companies --* i.e.* early IBM computer users), I always thought that writing *new code in Cobol or trying to port old code *was not done that often because the firms that were switching from Mainframes to UNIX were generally tossing out their homegrown applications at the same time and replacing the entire suite with something like SAP, BAAN, or Oracle APS that were networked, well integrated into things like PCs, used ASCII, *etc*. - *i.e*. using the replacement as the time to really upgrade their entire back office and possibly moving away from Big Blue based - which was not cost-effective (particularly for smaller firms). Another point was the Big 8 accounting firms started offering services that used the minis and UNIX boxes with SAP/BAAN/Oracle APS). Finally, I may miss remembering WRT to LPR-Cobol, but it was similar to today's Java in that it compiled into an interpreter. Plus, the impression I always had was that it was not designed for practical large-scale use or performance. BTW: this is a different behavior from the scientific world. From mini to supercomputers, in most cases, scientific users could not toss out their scientific computing tools and replace them with COTS alternatives (*i.e*., no firm like SAP, BAAN or Oracle providing "packaged" solutions for a bank or business). But since most of the production apps being used came with sources or the few that were commercial (Cadum, CATIA, Ansys *etc*..), it was possible to recompile and move things - so people did or the IVSs did. Even today, as one of my former colleagues put it, any sr computer system manager that ignores Fortran will eventually get fired for incompetence as it is still #1. =E1=90=A7 =E1=90=A7 On Thu, Jul 13, 2023 at 3:02=E2=80=AFPM segaloco via TUHS w= rote: > Reading through [1], there are documents offered by AT&T for the "Level I= I > 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 70= s > 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 > --00000000000025792206006443a2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Matt - I never had direct (user) experience=C2=A0with i= t.=C2=A0 I saw a demo of LPI's product at a trade show.=C2=A0 It might = have run on Ultrix, but if it did, I have no memory of it being in the test= suite we used for releases. Also, I do not remember if LPI-Colbol was atta= ched to a specific DB implementation or not.=C2=A0 In those days, there wer= e a number of them besides Ingres - Informix, IBM's DB2, and one that s= tarted with an S - which later was sold to Microsoft to become SQL-server t= o name a few, and that may have been part of it.=C2=A0 But there were bundl= ed applications for different markets (running a dentist's office, car = dealership, store, restaurant, etc..) that ran on small UNIX boxes a= nd used those DBs.

What I remember was that only a few= firms were offering Cobol for UNIX (I think that IBM, DEC, DG, and maybe N= CR had them from previous=C2=A0OSses), but the new generation of UNIX boxes= did not - although 3rd parties like LPI sometimes offered them.=C2=A0 Sinc= e it looks like AT&T is naming it/offering it with their product, that = is another example=C2=A0of AT&T management missing the market.=C2=A0 AT= &T's management (Charlie Brown) was interested in going after IBM a= nd probably thought that Cobol was important if they sold to IBM shops.

The problem was that except for some really large 'Bi= g Blue' places that never bothered tossing out Cobol (like Wall Street = and some insurance companies -- i.e. early IBM computer users), I al= ways thought that writing new code in Cobol or trying to port old cod= e was not done that often because the firms that were switching fro= m Mainframes to UNIX were generally tossing out their homegrown application= s at the same time and replacing the entire suite with something like SAP, = BAAN, or Oracle APS=C2=A0that were networked, well integrated into things l= ike PCs, used ASCII, etc.=C2=A0- i.e. using the replacement a= s the time to really upgrade their entire back office and possibly moving a= way from Big Blue based - which was not cost-effective (particularly for sm= aller firms).=C2=A0 =C2=A0Another point was the Big 8 accounting firms star= ted offering services that=C2=A0used the minis and UNIX boxes with SAP/BAAN= /Oracle APS).=C2=A0 Finally, I may miss remembering WRT to LPR-Cobol, but i= t was similar to today's Java in that it compiled into an interpreter.= =C2=A0 Plus, the impression I always had was that it was not designed for p= ractical large-scale use or performance.

BTW: this is = a different behavior from the scientific world.=C2=A0 From mini to supercom= puters, in most cases, scientific users could not toss out their scientific= =C2=A0computing tools and replace them with COTS alternatives (i.e.,= no firm like SAP, BAAN or Oracle providing "packaged" solutions = for a bank or business). But since most of the=C2=A0production apps being u= sed came with sources or the few that were commercial (Cadum, CATIA, Ansys = etc..), it was possible to recompile and move things - so people did= or the IVSs did.=C2=A0 Even today, as one of my former colleagues=C2=A0put= it, any sr computer system manager that ignores Fortran will eventually ge= t fired for incompetence as it is still=C2=A0#1.=C2=A0=C2=A0
3D""=E1=90= =A7
3D""=E1=90=A7

On Thu, Jul 13, 2023 at 3:02=E2=80= =AFPM segaloco via TUHS <tuhs@tuhs.org> wrote:
Reading through [1], there are documents offered by AT&= ;T for the "Level II COBOL" system, which some further research i= ndicates is a product from Convergent (same folks as the UNIX PC.)=C2=A0 Th= ere'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 t= here other efforts either promoted by Bell or even perhaps developed locall= y that were in any use before this version?=C2=A0 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?=C2=A0 I have no goal for= this information in mind yet, but just gathering details at this point.=C2= =A0 Thanks all!

- Matt G.

[1] - http://bitsavers.org/pdf= /att/000-111_ATT_Documentation_Guide_Nov87.pdf
--00000000000025792206006443a2--