Page 1 of 1

Unhandled failure (255) encountered

Posted: Mon Oct 22, 2012 3:49 am
by SPuneet
i have a similiar requirement... and i am also getting the error. the command i am using is:

/opt/app/ibm/InformationServer/V87/Server/DSEngine/bin/dsjob -run -mode NORMAL -wait spuneet_dev1 /opt/app/spuneet/projects/MainSeq

here spuneet_dev1 is name of my project
MainSeq is the main sequence that has all my jobs
(I have given the complete path of sequence)

the error that i encounter is as follows:

commandlinejob..JobControl (@Execute_Command_0): Controller problem: Unhandled failure (255) encountered executing command /opt/app/ibm/InformationServer/V87/Server/DSEngine/bin/dsjob -run -mode NORMAL -wait spuneet_dev1 /opt/app/spuneet/projects/MainSeq



also i see this in logs:

commandlinejob..JobControl (@Execute_Command_0): Command /opt/app/ibm/InformationServer/V87/Server/DSEngine/bin/dsjob -run -mode NORMAL -wait spuneet_dev1 /opt/app/spuneet/projects/MainSeq did not finish OK, reply = '255'


please help..how should i rectify this

Posted: Mon Oct 22, 2012 6:07 am
by SPuneet
IBM Documentation says dsjob has a dependancy on libvmdsapi.so.
Could this be the cause of my error.

can somebody tell me the location of this libvmdsapi.so so that i can verify on teh unix box if this is present or not

Re: Unhandled failure (255) encountered

Posted: Mon Oct 22, 2012 6:12 am
by chulett
SPuneet wrote:please help..how should i rectify this
Begin by starting your own post. Your issue isn't "similar" to the post you jumped on the end of, so I split you out so we could keep the two unrelated conversations... unconnected.

Posted: Mon Oct 22, 2012 6:16 am
by chulett
You don't have a library error. All the "unhandled failure" means is your command did not return a zero and you have the "Automatically handle activities that fail" option enabled in the Sequence. You didn't specify what to do on failure so it handled it.

You'll need to dig into the logs of the sequence and jobs you ran to see what failed. Out of curiosity, why are you running this from the Execute Command stage rather than the Job Activity stage? :?