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 < [email protected]> 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 > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
