In a recent note, Gerhard Postpischil said: > Date: Wed, 5 Oct 2005 08:59:02 -0400 > > > I'm wondering about a few things, since this does not do what you said > you wanted. The code will change a job with any program name beginning > with IOLQ (e.g., IOLQTEST, IOLQFAKE). If this is your intent, it would > be easier to maintain as > CLC =C'IOLQ',3(R6) > For some reason, it's very customary to code the variable on the left and the constant on the right. (Does this arise from word order in English sentences? Might it be otherwise for native speakers of other languages?) I sometimes work with code by a colleague who prefers the opposite convention. Cognitive dissonance.
But you suggest a valid reason, here, for placing the constant on the left. > change confers an advantage on the characteristics, in this case a savvy > user might sneak in a dummy step (e.g. // EXEC IOLQ,COND=(EQ,4091) or > some such). > This test might branch the wrong way in extraordinary circumstances. Why not, instead, "// EXEC IOLQ,COND=(0,LE)"? (Hmm. Constant on the left. But that's OK because the other comparand is elided.) A colleague once tried to suppress a job step with "COND=ONLY". A prior step ABENDed. In my code. He blamed me. I accepted responsibility for the ABEND, but not for the data set overwritten by his naive JCL coding. -- gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- 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
