From: David Arnold <davida@pobox.com>
To: segaloco <segaloco@protonmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Bell COBOL Environment?
Date: Fri, 14 Jul 2023 11:05:08 +1000 [thread overview]
Message-ID: <FBB44944-DB07-420A-A37E-FC81D2C6C9FE@pobox.com> (raw)
In-Reply-To: <jM9VnbNYQhLaC8aOAM1YUWeWQ824ureo_F2I8-yCx639Qej60ce1g8kU3dPP1Ov-qO0798MSZBFaxJ19Iqp3rN7O5PjaSregi89V_wb1VXs=@protonmail.com>
> On 14 Jul 2023, at 08:36, segaloco via TUHS <tuhs@tuhs.org> wrote:
…
> 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,
I think that’s fair, and certainly true of the COBOL system I knew (late 80s).
For us, a move to Unix would have been a complete re-architect, re-code, and replacement of basically all hardware. 3270 terminals, LU6.2 networking, CICS transaction monitor, ISAM datasets, all the batch jobs and their JCL, to say nothing of the two (redundant) 3090’s and the sea of DASD, monster printers, etc. The retraining or replacement of staff would have been overwhelming as well.
The closest I could get was writing some CICS transactions in C, but it wasn’t worth the uphill battle.
The only solution was to be acquired by a more modern company and throw the lot out!
d
next prev parent reply other threads:[~2023-07-14 1:05 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
2023-07-14 0:20 ` Bakul Shah
2023-07-14 1:16 ` Alan D. Salewski
2023-07-14 1:05 ` David Arnold [this message]
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=FBB44944-DB07-420A-A37E-FC81D2C6C9FE@pobox.com \
--to=davida@pobox.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).