When force completing a job in CA7, the Autosys Connect job that was waiting for its success condition (JOBNAME_ONE_to_JOBNAME_TWO) did not trigger.
Does force completing a failed mainframe job create the correct SMF record to kick off any dependent Autosys jobs? Does Autosys only take into account a successfull run with a return code of 0 to kick off a dependency?
Autosys Connect is not keeping track correctly of L2JOBCMP event in ENF.
WORKLOAD AUTOMATION CA 7 EDITION v.11.3
CA Workload Automation AE - Scheduler (AutoSys) (WORKLOAD AUTOMATION AE)
1. First step is to verify the L2JOBCMP event in ENF by issuing the command : F ENF,EVENT . If it does not display a number of registered passed events that means that it is not tracked.
2. In the startup parms of Autosys Connect *PURGE_FAILED_JOBDEP(Y) was changed to PURGE_FAILED_JOBDEP(N,CA7). After this change, the event L2JOBCMP is correctly tracked by Autosys Connect.
Test plan :