The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: segaloco <segaloco@protonmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Bell COBOL Environment?
Date: Thu, 13 Jul 2023 17:20:01 -0600	[thread overview]
Message-ID: <CANCZdfo+s67AGWz1fVrhP=RufLcz6F=4yf-YpJUVhynu+SbMCw@mail.gmail.com> (raw)
In-Reply-To: <jM9VnbNYQhLaC8aOAM1YUWeWQ824ureo_F2I8-yCx639Qej60ce1g8kU3dPP1Ov-qO0798MSZBFaxJ19Iqp3rN7O5PjaSregi89V_wb1VXs=@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 2595 bytes --]

Yes. And the need for COBOL also was mirrored in the micro world of the
time (at least the early 80s). Every micro with enough power seemed to have
a COBOL, but all of the offerings dried up before long because although
COBOL was a 'no brainer must have' for business, selling it into this new
market proved to be too hard. At least that's the impression I was left
with at the time, and also what the professors that taught my 'language
survey' course said about it...  You can take the raw code, but the
underlying environment and services just weren't there, so the raw code
turned out to be useless most of the time (I also got some $ re-writing a
few hundred lines of COBOL business logic for a local business that found
that easier for a company that had, as luck would have it, a PDP-11
database written in FORTRAN running on RT-11 or RSTS/E).

Warner

On Thu, Jul 13, 2023 at 4:36 PM segaloco via TUHS <tuhs@tuhs.org> wrote:

> The conclusion I'm coming to from what has been said thus far is that
> people who were moving from COBOL and the mainframe world to UNIX didn't
> have as much of a need for COBOL.  Since that transition often involved
> change in enough other aspects of an operation, moving to UNIX with the
> same COBOL applications just wasn't the path to success for most folks, as
> opposed to folks deeply invested in FORTRAN.  Would that be a fair
> characterization?
>
> Thanks for the feedback by the way, one of the matters I'm trying to suss
> out is what a typical COBOL environment on UNIX would've looked like back
> when, and what it sounds like is a COBOL environment on UNIX was anything
> but typical.
>
> - Matt G.
> ------- Original Message -------
> On Thursday, July 13th, 2023 at 2:42 PM, Jon Forrest <nobozo@gmail.com>
> wrote:
>
> You’re thinking of Sybase. That’s where the name “SqlServer” came from.
> Sybase sold a source code license to Microsoft that included the right to
> use the name.
>
> (I was a developer at Sybase in the VMS group in the late 1980s and early
> 1990s)
>
> Jon
>
> Sent from my iPhone
>
> On Jul 13, 2023, at 1:35 PM, Clem Cole <clemc@ccc.com> wrote:
>
> 
> Matt - I never had direct (user) experience with it.  Ireleases. 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.
>
>
>

[-- Attachment #2: Type: text/html, Size: 3707 bytes --]

  reply	other threads:[~2023-07-13 23:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13 19:02 [TUHS] " segaloco via TUHS
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 [this message]
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
2023-07-14  8:46 Paul Ruizendaal via TUHS

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='CANCZdfo+s67AGWz1fVrhP=RufLcz6F=4yf-YpJUVhynu+SbMCw@mail.gmail.com' \
    --to=imp@bsdimp.com \
    --cc=segaloco@protonmail.com \
    --cc=tuhs@tuhs.org \
    /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).