From: Paul Winalski <paul.winalski@gmail.com>
To: Computer Old Farts Followers <coff@tuhs.org>
Subject: [COFF] Re: NOT DELETED 8 (OS/360)
Date: Fri, 8 Mar 2024 10:53:55 -0500 [thread overview]
Message-ID: <CABH=_VTC7ROP0qmFRJjmkN=67vpuw+oHivVUgAcb2Jz5UzbrBw@mail.gmail.com> (raw)
In-Reply-To: <CABH=_VQ8-ZOh7uad4ZGZQ8gYOp9QJE4yDhFWbM7qeGcmzR+R4w@mail.gmail.com>
The subject of obscure OS/360 error messages recalled to my mind the
beginner's guide for students and faculty that the Boston College
Computer Center wrote. They spent many pages explaining obtuse OS/360
error messages. My favorite line from that document is:
"Despite what you may have been taught in German class, there is no
such thing as a 'guten ABEND'."
-Paul W
next prev parent reply other threads:[~2024-03-08 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 6:57 [COFF] " Dave Horsfall
2024-03-08 12:09 ` [COFF] " Michael Kjörling
2024-03-08 14:40 ` steve jenkin
2024-03-08 15:05 ` Paul Winalski
2024-03-08 15:53 ` Paul Winalski [this message]
2024-03-11 5:35 ` Dave Horsfall
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='CABH=_VTC7ROP0qmFRJjmkN=67vpuw+oHivVUgAcb2Jz5UzbrBw@mail.gmail.com' \
--to=paul.winalski@gmail.com \
--cc=coff@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).