Tony B's strictures, which begin
| Exits are a good alternative when: 1. The skillful author | never retires, finds a better job, gets laid off, is | transferred, gets fired, wins the lottery, or ages. | 2. . . . are apposite; and it is easy to sympathize with the bad experiences they reflect. They are also generic. They are equally applicable to user-written SVC routines [discussed in chapter 23 immediately following chapter 22, Exit routines, in the z/OS MVS Authoriized Assembler Services Guide] and to much else. I spent most of yesterday replacing an old SVC, which was written by perhaps the 213th sharpest knife in the drawer, with some PC routines; and if I needed a litany about the quality of that SVC I could quote Tony on exits. Bad code is ubiquitous for a variety of familiar reasons, and I doubt that avoiding exits because they are often written badly and/or documented poorly would be helpful. Its effects will be like those of the usual American traffic engineer's no left turns sign: it will serve only to move the problem to another location. John Gilmore Ashland, MA 01721-1817 USA _________________________________________________________________ Windows Live™ Contacts: Organize your contact list. http://windowslive.com/connect/post/marcusatmicrosoft.spaces.live.com-Blog-cns!503D1D86EBB2B53C!2285.entry?ocid=TXT_TAGLM_WL_UGC_Contacts_032009 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
