What happens to jobs when CA WA DE stops or restarts
Article ID: 130386
Updated On:
Products
DSERIES- SERVER
CA Workload Automation DE - System Agent (dSeries)
Issue/Introduction
DE and job status during reboots and restarts.
How are jobs handled when DE shuts down or restarts?
How are jobs handled when DE shuts down or restarts?
Environment
CA Workload Automation DE R11.3 / R12.x
CA Workload Automation Agents
CA Workload Automation Agents
Resolution
When DE (manager) shuts down, it will simply clear all the connections and update the DB. During the shutdown it will stop taking updates from WA Agents.
This prevents from any DB inconsistencies about jobs and applications that may still be active.
The WA Agents will continue to ping the manager to provide any updates on the job. Even if manager is not reachable, the agent will keep trying. When the manager comes up again, it will again start taking updates from all the agents. The agents will update the manager on jobs that completed.
Missed events: Events will not trigger when the manager is down. Once it comes back up again, it will again start triggering the events.
E.g. An event, USER1.MYAPPL, is scheduled to run DAILY at 9 AM. DE server was rebooted around 8:55 and it came back up at 9:05 AM. Manager will then check all the events. It will immediately trigger the USER1.MYAPPL as it was suppose to run when it was down.
Frequently triggered (cyclic) events: If the manager was offline for extended period, then events that trigger every few minutes or hours may only trigger once. The manager cannot recalculate all the missed times.
E.g. An event, USER1.RUNEVERY10 is scheduled to run every 10 minutes. It runs at 10:00, 10:10, 10:20, 10:30 and so on. Let's say the manager was down from 9:55 to 10:35. When it comes back up, it will only trigger the last 'Next Scheduled Time', which will be 10:00. It cannot go back and calculate 10:10 to 10:30 event times. If the number of triggers are required, then manually trigger the event.
Events on hold or suspended will continue in that state even after a restart.
This prevents from any DB inconsistencies about jobs and applications that may still be active.
The WA Agents will continue to ping the manager to provide any updates on the job. Even if manager is not reachable, the agent will keep trying. When the manager comes up again, it will again start taking updates from all the agents. The agents will update the manager on jobs that completed.
Missed events: Events will not trigger when the manager is down. Once it comes back up again, it will again start triggering the events.
E.g. An event, USER1.MYAPPL, is scheduled to run DAILY at 9 AM. DE server was rebooted around 8:55 and it came back up at 9:05 AM. Manager will then check all the events. It will immediately trigger the USER1.MYAPPL as it was suppose to run when it was down.
Frequently triggered (cyclic) events: If the manager was offline for extended period, then events that trigger every few minutes or hours may only trigger once. The manager cannot recalculate all the missed times.
E.g. An event, USER1.RUNEVERY10 is scheduled to run every 10 minutes. It runs at 10:00, 10:10, 10:20, 10:30 and so on. Let's say the manager was down from 9:55 to 10:35. When it comes back up, it will only trigger the last 'Next Scheduled Time', which will be 10:00. It cannot go back and calculate 10:10 to 10:30 event times. If the number of triggers are required, then manually trigger the event.
Events on hold or suspended will continue in that state even after a restart.
Additional Information
Note: When an event triggers, it also calculates the 'Next Schedule Time' as per the schedule define in the Events Schedule.
E.g. An event is set to run every hour starting at 9:00 AM. When it triggers at 9:00 AM, it will also calculate the 'Next Schedule Time' for 10:00 AM. It will do the same at 10 AM and so on.
E.g. An event is set to run every hour starting at 9:00 AM. When it triggers at 9:00 AM, it will also calculate the 'Next Schedule Time' for 10:00 AM. It will do the same at 10 AM and so on.
Feedback
Yes
No
Powered by
