Hi prakash56,
you may want to write log entries with timestamps to catch the point that drags out the batch job. Another option would be to create a statement monitor, if you can't change the batch job.
Very occasionally, I have seen things like this simply going away after termination or completion of the batch job.
Finally, you may want to have AIX gather work load statistics for yourself.
Johann
Quote:
Originally posted by prakash56
V7.2 fix pak 6
Unix AIX
I have got a batch proces running for six hours, which was taking 1 hour till yesterday.
what could be reason ?.
where to start from?.
db2 diaglog entries are not showing any problem.
|