On 21 Nov 2010 17:42:19 -0800, in bit.listserv.ibm-main you wrote: >On Fri, 19 Nov 2010 22:42:10 -0800, Edward Jaffe ><[email protected]> wrote: > >> >>According to the SHARE requirements data base, this requirement was >submitted >>nearly 18 years ago in March 1993. See what you can do... >> > >Ed, > >The biggest challenge is likely to be the limited resource in TSO (the IKJ >component), but I'll see what I can do... It certainly wouldn't hurt to >resubmit >it as part of the SHARE requirements clean-up.
In general, if a message doesn't specifically tell you what is wrong, it is useless. Back in the 1980s I justified the effort in going to MVS SP 1.3.3 (from 1.3.2 IIRC) because at that level the error message finally told people WHICH symbol was not defined in the procedure. As a semi-retired person who can't justify the cost of going to SHARE (No contracts or revenue and no system to apply information to), I would urge a general requirement that any message must show the erroneous data (duplicate symbol, etc.) in the message. Further the requirement should state that any message that does not contain the specific information needed to isolate the problem highlighted (actual erroneous value, statement number, etc.) is aparable and maybe automatically escalates at 6 month intervals. Clark Morris > >W. Kevin Kelley -- IBM POK Lab -- z/OS Core Technical Development > > >---------------------------------------------------------------------- >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 ---------------------------------------------------------------------- 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
