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.
. . JO.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] Paul Gilmartin <paulgboul...@aim .COM> To Sent by: IBM [email protected] Mainframe cc Discussion List <[email protected] Subject .edu> Messages as Programming Interfaces 07/06/2009 06:07 PM Please respond to IBM Mainframe Discussion List <[email protected] .edu> It is my understanding that IBM discourages the use of message texts as programming interfaces. Can anyone point me to a clear statement of this in IBM documentation? (Notwithstanding that IBM is very reluctant to change messages lest that disrupt automated operations.) Thanks, gil ---------------------------------------------------------------------- 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
