News about Beta during TWS webcast on 01/31/2013
Tivoli Workload Automation - Development Collaboration Community
From archive: January 2013 X
FlorianaFerrara 270000UB00 718 Views
We have implemented a very nice and good add-on to TWS that can be used to create a kind of "audit trail" log for TWS, using information from the TWS event records and plan audit records.
With this add on we can see, how many times a job in TWS did end with RC=2, how many time the job was cancelled or rerunned by a given user etc.
The problem is that time stamp in events seems to be "rounded" to nearest whole minute, while time stamp in the plan audit records are in hh.mm.ss format.
Is it possible to get seconds information from the event records?
Finn Bastrup 0600005EVQ Tags:  tws kill code return command agent dynamic job 1 Comment 2,869 Views
When doing TWS kill on a running dynamic agent jobs, the job (PID) is stopped on the server and the job status is
Error (Internal status Abend) but Return code is 0:
In the job log we see the following message:
= Status Message: AWSITA116I The job was stopped by the user
= Exit Status : 0
= Elapsed Time (Minutes) : 37
= Tue Jan 8 13:59:51 CET 2013
Is it possible to configure the TWS dynamic agent to end killed jobs with Exit status (return code) different from zero?
Or is it hard-coded in the dynamic agent code?
Using audit tools or automation to work with the return code, it could be nice to have a return code for killed jobs
(the same way as it happens on a FTA).