Hi James,
We are are a Mainframe shop, and we have CA Workload Automation (ESP) running on our Mainframe.
I have created a Powershell wrapper that we call directly from ESP to launch our jobs on the CAPA server instead of the built-in CAPA scheduler.
This way we have the jobs monitored by our 24/7 command center and I don't really have to worry about it.
However, for one of my processes (Unix server patching) I actually wrote a C# service that runs on the CAPA server and monitors the patching jobs against a list of 'known to be active' jobs contained in a dataset.
If the dataset shows that the job is active, the service then does a web-service call to CAPA to validate the actual state of the job, and updates the job status accordingly.
That way I can catch if a job aborted (or was cancelled) as I wasn't able to trap some of those errors within the error handling routines of CAPA itself.
We are also using Microsoft SCOM to monitor the state of the CAPA services, and that the webservices are responding.
Not sure if that helps you out, but thought I would add my $0.05
(Up from $0.02 since we don't have pennies in Canada anymore)
Ian