Explanation of ENDED_VANISHED status

Products

• CA Automic Workload Automation - Automation Engine
• CA Automic One Automation

Issue/Introduction

Job shows ENDED_VANISHED in the Activities Window.  What does the ENDED_VANISHED status mean?

 

If the Agent runs across a status change or an erroneous attempt to retrieve the status while checking a Job (rarely occurs), the Job's status cannot clearly be determined.

Resolution

Investigation

 

The 'Job Messenger Program' runs at the beginning and ending of each job for the OS/390 Executor, which is how Automic detects the start and end of jobs. If the appropriate DD statements have been included, this enables the 'Job Messenger Program' to establish a TCP/IP connection and communicate the status of a job to the Executor.

 

When a JCL-error occurs, the 'Job Messenger Program' does not run and the Executor is not updated on a job's status. The job is not active any more due to the JCL-error; however, its final status is not reported back to Executor as "ENDED" by the Job Messenger. The Executor reports a status of "ENDED_VANISHED" to the Automic server for this job. The Post-Process tab can be used for reading the report and adjusting the end status to something more useful to you.

 

Solution

 

The parameter vanishedretry= in the Agent's .ini that may be used to specify how many times the Agent retries to check the status before it reports the status "ENDED_VANISHED".

 

Information on this parameter can be found in the Documentation

 

Another option is to change the status of the job based on what is found in the Report