Command output of ExecCommand

chulett · Post by **chulett** » Sun Sep 30, 2007 2:26 pm

Good, one down. What did you find when you searched the forum for your new error message? It's been discussed quite a number of times...

"Controller problem: Unhandled failure"

ray.wurlod · Post by **ray.wurlod** » Sun Sep 30, 2007 2:36 pm

Will you STOP using the Field() function until we can sort out exactly which field you want?

Where are you calling the SDK routine UtilityWarningToLog from?

abc123 · Post by **abc123** » Sun Sep 30, 2007 7:58 pm

I am caling the UtilityMessageToLog from the RoutineActivity stage. Now, in the RoutineActivity stage, I have:

RoutineName: UtilityMessageToLog
Value Expression: ReadFile.$CommandOutput

I am still getting the same error. I'll keep doing research on this forum on this error. Please let me know if I can provide any more information.

abc123 · Post by **abc123** » Sun Sep 30, 2007 8:09 pm

Ok. I found why I was getting the error. It is due to the fact that I had "Automatically handle activities that fail" checked. I unchecked it and I don't get the error. Thanks Ray, ArndW and Craig for your help.

ray.wurlod · Post by **ray.wurlod** » Sun Sep 30, 2007 9:21 pm

You're not done yet. What is it that is causing the activity to fail? If it's the Execute Command activity, this is an exit status other than zero; you may need to make a small adjustment in your shell script (exit 0).

You still have not properly gathered the command output either - or, if you have, you have not posted that you have.

abc123 · Post by **abc123** » Mon Oct 01, 2007 9:49 am

After using absolute path, proper value is returned by the Linux script. After that, if I use Field(ExecCmd.$CommandOutput, @FM,1,1) or ExecCmd.$CommandOutput wihtout Field, it works.

The RoutineActivity call to UtilityMessageToLog returns a 1. When I check "Automatically Handle Activitties That Fail", it interpretes this as an error and the sequence aborts.

If you have an idea so that I can avoid this without unchecking this property, I would really like to hear it.

ray.wurlod · Post by **ray.wurlod** » Mon Oct 01, 2007 2:43 pm

Use a custom trigger on the Routine activity. Allow 1 as the returned value.

ray.wurlod · Post by **ray.wurlod** » Mon Oct 01, 2007 2:44 pm

Use a custom trigger on the Routine activity. Allow 1 as the returned value.

chulett · Post by **chulett** » Mon Oct 01, 2007 9:47 pm

You don't really need a custom trigger. The thing about the 'automatically handle' option is that it only kicks in it "needs to" - when you don't handle errors. The online help spells it out for you, but basically make it think you've got all the bases covered and those kind of 'failures' won't be an issue.

For example, a typical pair of triggers that shut down the 'automatic' option would be an 'Ok (Conditional)' and an 'Otherwise' link. In your case, the 'Otherwise' link is the one that is actually your expected path but both are needed - send them both to a Sequencer set to 'Any' and then from there to your next step. The 'automatically handle' option can now be turned back on and will function for all of the other activities in your Sequence.

deejje · Post by **deejje** » Wed Jun 16, 2010 4:18 am

abc123 wrote:Craig, that was the issue. The relative path. My ExecCommand produces the right values. However, the RoutineActivity still errors out. I still get the error:

Controller problem: Unhandled failure (1) encountered calling routine DSX.UTILITYMESSAGETOLOG

In the RoutineActivity stage, I am selecting Routine Name as UtilityMessageToLog and in Value Expression for Arg1, I have:

Field(ReadFile.$CommandOutput, @FM,1)

The output from the ExecCommand is sometimes appended at the end with a newline character. I ran into a similar problem and selected the leftmost byte from the command output _$CommandOutput that was numeric. I could run my job activity with that. You probably need to find out how to just select numeric characters out of the command output and you should be fine.

Thanks
- Deejje