If expressed that way, I have no choice but to accept that "BANANA"
overrides SYSDA - although that is not the interpretation of 'override'
I am referring to.
If expressed as "BANANA" prevails over SYSDA, then I disagree - because
"BANANA" would fail with a JCL error and would therefore not prevail.
Tom Marchant wrote:
On Wed, 3 Aug 2011 12:06:31 +0100, CM Poncelet wrote:
NO NO NO again. What I did was prove by 'reductio ad absurdum' that if
the premiss/assertion "On input, the order of override priority is
program DCB -> JCL DCB -> dataset attributes" is true then its
consequences are absurd: therefore the premiss/assertion is false.
Please note that, at the beginning, I did say "What I *would* expect
..." and not "What I expect ..."
To finish this off. It is *not* valid to argue that 'this' overrides
'that', if 'this' having overridden 'that' results in 'this' not working
unless it happens to be equal to 'that' - where 'this' and 'that' can be
any permissible values, with no imposed conditions or constraints.
If I understand what you are trying to say, consider this. Suppose you
have some JCL like this:
//TESTPROC PROC UNIT=SYSDA
//SETP1 EXEC PGM=IEFBR14
//DD1 DD DISP=(NEW,DELETE),UNIT=&UNIT,SPACE=(TRK,1)
// PEND
By your logic, if you code
// EXEC PROC=TESTPROC,UNIT=BANANA
"BANANA" does not override SYSDA for the unit because it causes a JCL
error.
----------------------------------------------------------------------
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
