Warning : Unable to find SoftwareResourceLocator start point
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
Warning : Unable to find SoftwareResourceLocator start point
Hi all,
I am getting a warning message while running the sequences.
the warning text is "Unable to find SoftwareResourceLocator start point"
and this warning comes continuously unless I cleanup the resources
i am unable to stop the sequence too. it doesn't aborts/stops through the abort button. for that i have to logout the processes through cleanup resources option.
can anyone tell me how to resolve this?
Regards,
I am getting a warning message while running the sequences.
the warning text is "Unable to find SoftwareResourceLocator start point"
and this warning comes continuously unless I cleanup the resources
i am unable to stop the sequence too. it doesn't aborts/stops through the abort button. for that i have to logout the processes through cleanup resources option.
can anyone tell me how to resolve this?
Regards,
Priyadarshi Kunal
Genius may have its limitations, but stupidity is not thus handicapped.![Wink :wink:](./images/smilies/icon_wink.gif)
Genius may have its limitations, but stupidity is not thus handicapped.
![Wink :wink:](./images/smilies/icon_wink.gif)
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You may need to recompile the job sequence.
You may further need to check that the logic of the job sequence is intact, for example that every path through the job sequence can enter an activity and leave that activity.
You may further need to check that the logic of the job sequence is intact, for example that every path through the job sequence can enter an activity and leave that activity.
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.
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
Hi Ray,ray.wurlod wrote:You may need to recompile the job sequence.
You may further need to check that the logic of the job sequence is intact, for example that every path through the job sequence can enter an activity and leave that activity.
This job was running fine previously but now i am getting this problem.
The sequence runs fine when all the jobs finishes successfully.
but when any of them fails we are getting this warning.
Regards,
Priyadarshi Kunal
Genius may have its limitations, but stupidity is not thus handicapped.![Wink :wink:](./images/smilies/icon_wink.gif)
Genius may have its limitations, but stupidity is not thus handicapped.
![Wink :wink:](./images/smilies/icon_wink.gif)
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
Hi Ray,ray.wurlod wrote:It's the restart logic code. That's why I suggested recompiling.
I recompiled that sequence and ran again it worked fine.
but I am getting this warning in 90% of the time when any job aborts.
Is there any work around that can restrict these warning and abort the job normally.
Regards,
Priyadarshi Kunal
Genius may have its limitations, but stupidity is not thus handicapped.![Wink :wink:](./images/smilies/icon_wink.gif)
Genius may have its limitations, but stupidity is not thus handicapped.
![Wink :wink:](./images/smilies/icon_wink.gif)
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Preventing the jobs from aborting would be favourite.
What compilation options have you set in your job sequence? Are you using explicit Failure triggers on the Job activities? Is there an Exception Handler in your job sequence?
What compilation options have you set in your job sequence? Are you using explicit Failure triggers on the Job activities? Is there an Exception Handler in your job sequence?
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.
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
Yes, thats what i prefer too.ray.wurlod wrote:Preventing the jobs from aborting would be favourite.
What compilation options have you set in your job sequence? Are you using explicit Failure triggers on the Job activities? Is there an Exception Handler in your job sequence?
yes we have exception handler in the sequence to abort the sequence (using terminator)after mailing activity.
There are few conditional triggers to to abort the sequence in case of warnings.
and i use the simplest compile option that is on the tool bar of datastage designer (i think i am mis-interpreting this one, correct me if it is so)
Regards,
Priyadarshi Kunal
Genius may have its limitations, but stupidity is not thus handicapped.![Wink :wink:](./images/smilies/icon_wink.gif)
Genius may have its limitations, but stupidity is not thus handicapped.
![Wink :wink:](./images/smilies/icon_wink.gif)