Originally posted by: cjordan

Folks, I have a problem at a customer site whereby some of there batch scripts are now not working due to an upgrade of there scheduling tool (Tivoli workload Scheduler).
After doing all sorts of debug It looks like the environment vairables are all good etc etc
so the nect thing I did was add the following
truss command to the script to see what was happening.
Once I added the truss - the script all works well

Without the truss command it gives a SIGKILL -
Any ideas what "extra" the truss is doing to get the thing to work??

if $# -gt 0 ; then
truss -a __AB_INVOKE_PROJECT "${_AB_SAVED_PROJECT_DIR}"/.project.ksh "${_AB_SAVED_PROJECT_DIR}" execute start "$@"
else
truss -a __AB_INVOKE_PROJECT "${_AB_SAVED_PROJECT_DIR}"/.project.ksh "${_AB_SAVED_PROJECT_DIR}" execute start
fi

Originally posted by: MarkTaylor

SIGKILL is a kill -9 or -KILL .. TWS does not send SIGKILL

Ref: http://www-01.ibm.com/support/docview.wss?uid=swg21206347

So, I would look for a script or prog on the customers system that issues a kill -9 .. it could be that another batch script or prog is
picking up your TWS jobs from the ps listing and killing them .. speak to your customer.

The truss is in kernel space doing i/o, so cannot be killed BTW, thats why your scripts are running whilst forked off from truss.

HTH
Mark Taylor