One of the sequencer( underneath 5jobs) got triggered for every 5 mintues. Genreally it takes max of 1-2 min for completion of execution. But sometime any one of the job got hung and it runs continuously.
If i clear the resources from director, job get aborted and again in the next of couple of runs it gets hung.
After abortion of job the processes unix as below.
Can anyone suggest to get rid of this? I can see phantom processes and also .fifo file which might have corrupted. What can be done to resolute this?[/code]
What you really need to do is to address the reasons why the underlying jobs exhibit this intermittent behaviour.
A job sequence can not complete until all of the activities in it have completed (or a Terminator activity is executed), therefore if the underlying activity is hanging, or simply taking a long time to execute, then the job sequence itself will patiently await its completion.
Killing underlying processes is fraught with a number of dangers, primarily that you do not identify all the processes associated with the job - for example external commands (whether from the job sequence or from stages such as External Filter) do not execute osh and therefore are not picked up by the Cleanup Resources tool (which was - and really still is - intended primarily for server jobs).
If you are unable or unwilling to determine and prevent the problems in the underlying activities, then I would suggest that you create custom job control code that establishes a time within which the activity must complete and issues a stop request if this timeout occurs. You can use the generated job control routine from the job sequence as a template and paste it into the Job Control tab of a new server job as a prototype that you can edit.
Last edited by ray.wurlod on Mon Jul 14, 2008 5:23 pm, edited 1 time in total.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Once we set these 2 paramters in user defined section of Administrator, the issue is resolved.
APT_DONT_OPTIMIZE_MODIFY=1
APT_MSG_LINE=1
Not sure actual reason. If anyone have any clue on this...please share with me.
But it is always suggestable to clear the &PH& directory periodically for a project to get rid of the issue.
Please explain what these environment variables do, and how you came to decide on these specific settings for them, so that we all might understand your resolution and why it may have worked.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Very. Purging or pruning them is fine, however, as long as the job they are associated with has completed running. Typically, people script something to run every day and remove any items X days old where X is on the order of 3 to 7, I would guess.
-craig
"You can never have too many knives" -- Logan Nine Fingers
Can you send me any document or anything if you have, to know what &PH& is all about, bcos yesterday it had taken 2GB of data.
So being little proactive here. Thanks
