When it has been determined that an agent is no longer needed in the Workload Automation DE environment, it should be removed entirely from the configuration. To accomplish this in an effective and efficient manner, follow these steps:
Note: If you leave the agent software in place on the agent and for whatever reason, someone or some automated process restarts the agent, it will continuously make attempts to contact the scheduler. This is unnecessary traffic that could eventually lead to a negative impact on scheduler performance. The same can be said for job definitions. If jobs try to kick off against an agent that no longer exists, the job will go into a SUBERROR state with a status of "The specified Agent SOME_AGT does not exist in the topology." This will continue to occur and could have a negative impact on performance and system availability if the jobs begin to build up in the system.