I have a lot of jobs that get SQL -911 DB2 contentions. I would like to see if UC4 can scan the sysout to capture the -911 code and then if that SQL code is there, do the auto restart for the job. Is this something that is possible to do?
You can use a filter object that scans for SQL-911 and once the result is found activates the job again, or use PREP_PROCESS_REPORT and utilize RESTART_UC_OBJECT.
Certainly should be able to. But I don't think your DBA staff would be happy about filling their error logs with -911 errors.
When we still had a Mainframe and DB2 with its -911 failures, I nipped this problem in the bud by scheduling my collision events so they can't run at the same time. At the time I was using the CA-Zeke scheduler and something it calls a "resource" rule, but the same solution is available with CA-Automic and its SYNC object.
The concept is simple once you get it down. You create a SYNC for each DB2 table you are having problems with (e.g. SYNC.DB2.TABLE1, SYNC.DB2.TABLE2). Every task that needs to use TABLE1 must have SYNC.DB2.TABLE1 attached to it, and this connection can be customized to either choose "START_EXCLUSIVE" or "START_SHARE" depending upon weather or not that task is going to apply updates to TABLE1 which creates database locks. Then UC4 will automatically avoid the collisions for you.
Here is my MODEL.SYNC that I clone;
here is an example of one of our SYNC connections on a job;
Retrieving data ...