CA Workload Automation ESP Edition RUN/NORUN unexpected simulate results
Article ID: 4850
Updated On:
Products
Issue/Introduction
We are running CA WLA ESP edition 11.4 on z/OS 2.2. When doing a simulate from either the workstation or ISPF CSF we are getting unexpected results using RUN/NORUN.
When we reverse the RUN and NORUN statements and simulate for Sunday the WOB is selected and we believe it should NOT be.
Environment
Component:
Cause
The NORUN statement has to be coded after the RUN statement. You can see this as you have noticed in simulations. The key sentence here is if both are used the last one encountered is applied and used. This behavior has been known for quite some time. If NORUN is BEFORE the RUN statement, then the RUN criteria will be ignored, and the default RUN ANY will be applied. This is why it will run on Sunday.
Resolution
When both RUN and NORUN statements for a job are encountered, the last one that applies overrides. The NORUN statement should follow a RUN statement.
Additional Information
Additional information can be found in the CA Workload Automation ESP Edition Command Reference Guide.
https://docops.ca.com/ca-workload-automation-esp-edition/11-4/en/reference/commands
Feedback
