One possibility is that your system is overloaded and the last one takes so long to initiate thatis causes a timeout. If you monitor your system load using your favorite monitoring tool (such as vmstat) while this sequence runs does the system begin to page or swap and what is the CPU load?
No, you can also get this if one of the databases to which you're connected is in a "not ready" state, or takes too long to execute your "query from hell".
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Thank you very much for responsing immediately, Actually there was around 30 jobs were lock, due to that I was getting sequence aborted, I unlock all the jobs then I re-run the sequence then I runs perfectly.