Removing Orphaned Dependency Records From AutoSys/Connect
Article ID: 106905
CA Workload Automation AE - Business Agents (AutoSys)CA Workload Automation AE - Scheduler (AutoSys)CA Workload Automation Agent
On occasion, the DEPLIST in AutoSys/Connect will show dependency records that are no longer configured within any job in WAAE. What is the best way to remove these orphaned records?
Release: Component: ATSYS
Through use of the DELDEP operator command orphan dependencies can be removed from the Unicenter AutoSys Connect dependency array. This alleviates the need to recycle Unicenter AutoSys Connect to remove the orphan dependencies.
The operator command syntax is as follows:
name Is the name of the dependency to be deleted. Valid dependency names can be derived from the DEPLIST operator command. The dependency name can be masked.
type Is the dependency type of the dependency to be deleted. Valid types are “AD,” “SJ,” “**” or “*.” The “**” type indicates a batch interface (ATCJxxx) dependency. The “*” indicates the delete will occur for all dependency types for a given node.
node Is the remote node currently registered with Unicenter AutoSys Connect.
id Is the unique identifier assigned by Unicenter AutoSys Connect when the remote node registered.
The id of a remote node can be determined through execution of the AGTLIST or the STATUS(CCI) operator command. If the id is not specified it defaults to a value of “1”. If the agent node for the dependency being deleted does not exist in the Unicenter AutoSys Connect agent array, specify “0” as the id and Unicenter AutoSys Connect will prompt at the operator console for the 20-character node application name of the dependency.
Output messages are directed to the operator console providing a status of the command.