Any boolean tests can be performed with 'COND=', but not so with 'IF
ELSE etc.' We have already discussed this in the past.
But please show me how 'IF ELSE ...' handles the following:
Execute STEPF if
- STEPA sets CC=04, STEPB sets CC=00, STEPC did not execute, STEPD sets
CC=08 and STEPE did not execute
or if
- STEPA sets CC=00, STEPB did not execute, STEPC sets CC=04, STEPD did
not execute and STEPE sets CC=00
or if
- STEPA did not execute, STEPB sets CC=00, STEPC sets CC=04, STEPD sets
CC=08 and STEPE sets either CC=04 or CC=08
otherwise do not execute STEPF.
'IF ELSE ...' is to 'COND=' as 'mouse' is to 'keyboard'.
Cheers, Chris Poncelet
Paul Gilmartin wrote:
On Thu, 20 Jan 2011 20:04:08 +0000, CM Poncelet wrote:
But one of the most useful purposes of COND= testing is
COND=(0,LE,<whatever>) ... which ensures the current jobstep will NOT
execute unless previous jobstep <whatever> did NOT execute. So 'NOT
logic' can still do what 'IF ELSE etc.' cannot. <g> CP
What am I missing? From:
Title: z/OS V1R12.0 MVS JCL Reference
Document Number: SA22-7597-14
17.1.4.5 Relational-Expression Keywords
...
^stepname.RUN
stepname.RUN=FALSE
Indicates that the relational expression tests that a
specific job step (stepname) did not start execution.
-- 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
----------------------------------------------------------------------
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
