It's veeeeery good that we have Messages and Codes, no doubt.
However sometimes after one read the explanation he could be completely
confused. I'm mean those meesages which suggest problems with OS CVOL
(I'm too young to remember it), or use terms completely incomprehensible
for beginners. No, not only beginners. Simple JCL mistake, i.e. MOD on
existing member results with error message which is descirbed using
well-known words like STOW, TTR, DEB, and suggest to use IEHPROGM (AFAIK
not good idea for SMS-managed datasets). There is no simple sentence
"probably duplicate member name", rather DCB Abend exit routine and
advice to use GTF.
In general, I would separate two kinds of message mess:
1. Historical terms, reasons, etc. Yes, sometimes the problem could be
caused by historical, unsupported 'thing' like VSAM space (in MVS), but
it could be clearly marked with some disclaimer "for dinosaurs only",
"unsupported obituaries" or other "museal problem".
2. Advanced language, no simple explanation. Maybe this language is the
only which fully described the nature of the problem, it would be good
idea to add some simple explanation for non-advanced users, even with
disclaimer it's simplification etc.
Just my $0.02
--
Radoslaw Skorupka
Lodz, Poland
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
