Well, I wrote an article on my internal company blog, recently. It was
exactly about messages and codes.
People couldn't believe in some statements:
1. Every message has its own ID. Fortunately readers agreed that msg ID
is far better than "Oops! Something went wrong, try again later".
2. Every message is documented, and there is "Messages and Codes"
bookshelf. And there are books and even bookshelves. And it was
available from Internet for 20+ years.
3. Every message ID has prefix which clearly describes that it comes
from CICS, DB2, RACF... (DFH, DSN, ICH...)
4. Message description in the book is more than "Something is wrong. Try
again later".
5. Return code has meaning. It is more than "zero vs non-zero" RC.
I wish I could put here some pictures with funny/annoying Windows
messages here. ;-)
--
Radoslaw Skorupka
Lodz, Poland
W dniu 10.06.2020 o 22:02, Steve Smith pisze:
I take this example as merely an example. IBM & the software industry are
notoriously bad at getting these right.
At one end, you have "Oops, something went wrong." -- Windows 10 (and
yeah, the day I started using Windows 10).
At the other, IDC3009I. Sheesh.
Counter to those, the IMS message doesn't seem quite so bad... it's
(presumably) accurate, and fairly precise. You could argue it could be
worded more simply, or that it should provide the detailed codes.
In my experience, messages get very little attention or quality review.
I'm sure it varies a lot.
sas
On Wed, Jun 10, 2020 at 3:50 PM Paul Gilmartin <
0000000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
On Wed, 10 Jun 2020 17:02:40 +0000, Frank Swarbrick wrote:
Here's a quote from a message I posted to this list in 2009:
"I have a very basic one to complain about:
DFS0929I BLDL FAILED FOR MEMBER --DDMPPSZ
This really means that the specified PSB DDMPPSZ is not in the specified
IMS library. Why can't it just say that? As an application programmer do
I really need to know that BLDL means, well, whatever it means?
The practice was established over a half century ago when every programmer
could be presumed to have at least a superficial knowledge of the entire
OS/360
reference library. And storage was too precious to support elaborate
messages.
That time has passed.
The practice persists.
-- gil
======================================================================
Jeśli nie jesteś adresatem tej wiadomości:
- powiadom nas o tym w mailu zwrotnym (dziękujemy!),
- usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś
na dysku).
Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać
tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza)
tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać
karze.
mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950
Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st.
Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 0000025237,
NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na
01.01.2020 r. wynosi 169.401.468 złotych.
If you are not the addressee of this message:
- let us know by replying to this e-mail (thank you!),
- delete this message permanently (including all the copies which you have
printed out or saved).
This message may contain legally protected information, which may be used
exclusively by the addressee.Please be reminded that anyone who disseminates
(copies, distributes) this message or takes any similar action, violates the
law and may be penalised.
mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950
Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital
City of Warsaw, 12th Commercial Division of the National Court Register, KRS
0000025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN
169.401.468 as at 1 January 2020.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
