Why does 'if-then-else' logic in a processor with 'stepname.rc' syntax generate a false unexpectedly ?

book

Article ID: 17921

calendar_today

Updated On:

Products

CA Bind Analyzer for DB2 for z/OS CA Detector CA SQL-Ease for DB2 for z/OS CA Sysview Performance Management Option for DB2 for z/OS CA Database Detector for DB2 for z/OS CA Plan Analyzer for DB2 for z/OS CA Subsystem Analyzer for DB2 for z/OS CA PanAudit Plus CA Easytrieve Report Generator CA PAN/SQL CA Endevor Software Change Manager (SCM) CA Endevor Software Change Manager - Natural Integration (SCM) CA Endevor Software Change Manager - ECLIPSE Plugin (SCM) CA Endevor Software Change Manager - Enterprise Workbench (SCM) CA 2E

Issue/Introduction

Question:

If a processor step is excluded by 'if-then-else' logic and the same named step completes with RC=0, why does the test for stepname.RC = 0 return a false ?

Solution:

Use unique stepnames in a processor. If a processor step is excluded by if-then-else logic, then the same stepname completes with RC=0, the test for stepname.RC = 0 will return a false. The use of non-unique stepnames can have unpredictable results. 

Environment

Release: ENDAE.00200-15.1-Endevor-Software Change Manager
Component: