Connect Showing Dependencies in DEPLIST That Do Not Exist


Article ID: 102298


Updated On:


CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) CA Workload Automation Agent


When running a DEPLIST in AutoSys Connect, it shows dependencies originating from AutoSys that no longer exist. The dependencies on CA7 jobs that were once contained in AutoSys job definitions were removed some time back.


There were still records of the dependencies left in the ujo_ext_job table in the AutoSys database. Because of this, they were staying in the DEPLIST on the Connect side.


Component: ATSYS


Using the CA7 job name from the DEPLIST, run the following query to confirm that no other jobs contain a dependency on the CA7 job...

select count(*) from ujo_job_cond where cond_job_name='<CA7_JOBNAME>';

If this results in a non-zero count, there are other jobs that still contain the dependency and no action should be taken. However, if this query produces a zero count, then it is safe to manually remove the leftover records in ujo_ext_job with the following sql...

delete from ujo_ext_job where ext_job_name='<CA7_JOBNAME>';