SIGINT in Director
Moderators: chulett, rschirm, roy
SIGINT in Director
Hi folks, starting today, if I try to run jobs from Director, I get a job abortion with SIGINT. Jobs run fine when started in DS Designer. Ideas?
Thanks,
Doug
Thanks,
Doug
Is this a Job Sequence or just a parallel job? Are you getting any warnings before you get the SIGINT error. Can you post any warnings from director log? Couple of reasons why SIGINT error occurs is when someone tries to stop the job or if the number of warnings exceed the limit mentioned in the Job Run options.
Kris
Where's the "Any" key?-Homer Simpson
Where's the "Any" key?-Homer Simpson
kris007 wrote:Is this a Job Sequence or just a parallel job? Are you getting any warnings before you get the SIGINT error. Can you post any warnings from director log? Couple of reasons why SIGINT error occurs is when someone tries to stop the job or if the number of warnings exceed the limit mentioned in the Job Run options.
Great thanks. This is just a parallel job. There are a bunch of "standard" warnings that I get running it either way. There is a pair of warnings on each input column:
Code: Select all
The modify operator has a binding for the non-existent output field
Code: Select all
The modify operator keeps field
Thanks,
Doug
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Disable RCP to see whether that resolves the issue. If it does, try to discover why the additional, unspecified columns might have raised an interrupt signal.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Hi,ray.wurlod wrote:Disable RCP to see whether that resolves the issue. If it does, try to discover why the additional, unspecified columns might have raised an interrupt signal.
RCP is not enabled. I'm not sure that these warnings have anything to do with it. Again, the jobs run just fine when launched from Designer, warnings and all.
Thanks,
Doug
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Again, unless you override the values, the default warning limit in the Director is 50 while from the Designer it is zero - unlimited. Which could explain part of your issue with the Director but still shouldn't result in a SIGINT as far as I know.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Re: SIGINT in Director
What's changed since the day beore today?dougcl wrote:... starting today ...
"Nothing" is clearly not the correct answer.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
ray.wurlod wrote:Is JobMonApp running or disabled? Are you collecting performance statistics when running from Director?
Not sure about the former. I'm not sure how to check this. For the latter, I do not have the jobs set to record performance data on the job properties execution tab.
Regarding the problem starting yesterday, it is more accurate to say that I haven't tried to run from director in a week or so. Last time I tried it, it was fine, but many things were added to the jobs since then.
It seems really odd to me that something runs perfectly well in designer, but fails in director. I would think this can only happen in very specific ways. It's unfortunate as well that whatever it is, it's unhandled.
Thanks,
Doug
There lies your answer. You will have to figure out what component that was added might have caused this issue. I asked earlier but I'll ask again. Are there any warnings in your director log that is causing the job to fail? Usually the default value in director is 50 warnings. Do you see 50 warnings in your director log when you run the job both from the Director and Designer?dougcl wrote: Last time I tried it, it was fine, but many things were added to the jobs since then. Doug
Kris
Where's the "Any" key?-Homer Simpson
Where's the "Any" key?-Homer Simpson