On Mon, Jul 6, 2009 at 9:20 PM, Skip Robinson <[email protected]>wrote:
> While not a 'programming interface' as such, message text figures > prominently in all automation products I know of, including IBM's. Great > pains are taken to inform customers of text changes via 'AO' System Hold > records. There have been many requirements over the years for IBM to > provide programmatic interfaces that don't rely on messages. Some of these > have been implemented to one degree or another, but messages are still the > cornerstone of automation. > And while I understand the theology that says "We won't define messages as an API because then we couldn't improve them", it's kind of ironic when you work in Other Environments that don't use message headers, so you get (for example) a dialog box that says "Frambling the glornitz" and you *don't even know what application is telling you that*, much less whether you should care/worry/do something. And God forbid something breaks: you wind up Googling for the message, hoping that someone else who has figured it out actually typed in the correct text so you get a match! ---------------------------------------------------------------------- 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
