In a message dated 7/29/2008 3:25:25 A.M. Central Daylight Time, [EMAIL PROTECTED] writes: >>Suppose someone who does not know that proc X is used by 10 other jobs with >>overriding DDs in them decides to rearrange the DD statements within proc X. >Why ever would anyone do that? Possible reasons: 1. When I create JCL, I put my DD statements in alphabetic order by ddname within each step. It helps me find one later if I need to. My JCL is not used by others, so I am free to reorder my own DD statements according to whim. Someone with the same desire to alphabetize everything may cluelessly reorder a proc that others use without understanding the repercussions of what he is doing. 2. People make mistakes regardless of how clueless or anal retentive they are. Maybe somebody is editing a proc, accidentally deletes a DD statement, then realizes his mistake, recreates the now missing DD statement, and puts it in the wrong place because he doesn't remember exactly where it was in relation to the 20 or 30 other DD statements and he doesn't know that exact placement may be critically important. 3. Why would anyone ever do anything stupid? Never. Does that mean that stupid things never happen? 4. My program can never get to this point in the logic, so I don't need any code here to handle this situation. 5. As Donald Rumsfeld said, "Stuff happens." Bottom line: software and procedures should be bullet-proof enough to survive situations that occur for reasons that make no sense to those of us who are rational, competent, wise, and blessed with huge amounts of experience. Bill Fairchild Rocket Software
**************Get fantasy football with free live scoring. Sign up for FanHouse Fantasy Football today. (http://www.fanhouse.com/fantasyaffair?ncid=aolspr00050000000020) ---------------------------------------------------------------------- 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
