Sequence check condition stage help

sigma · Post by **sigma** » Mon Oct 06, 2008 5:06 pm

Hi

The output of my log for the execute command stage is

Seq_Madison_Customer_Master..JobControl (@Command_To_Chk_Rejects): Executed: wc -l /cdwdata/reject/pharma/madison/*Rejects.txt | grep total | awk '{print $1}'
Reply=0
Output from command ====>
0

Then I do a custom expression in the next check condition stage as in

Command_To_Chk_Rejects.$CommandOutput > 0

The problem is I still get a email as it seems to not pass this above condition

I think I am missing something basic woudl greatly appreciate any help

sigma

sigma · Post by **sigma** » Mon Oct 06, 2008 5:08 pm

The point is that it goes through to execute the notification stage when my output is 0 and I am telling it to send email only if the value is greater than 0

Sigma

chulett · Post by **chulett** » Mon Oct 06, 2008 10:03 pm

Output from the Execute Command stage is returned in a dynamic array, which means there's more to that zero than meets the eye. It's actually a zero followed by a Field Mark, which is why your test fails.

Couple of solutions. Either check just the first element of the array or remove the field mark. Trigger examples for both:

Code: Select all

Command_To_Chk_Rejects.$CommandOutput<1> > 0

Code: Select all

Convert(@FM,"",Command_To_Chk_Rejects.$CommandOutput) > 0

sigma · Post by **sigma** » Tue Oct 07, 2008 7:37 am

Thanks a lot for the reply

Convert(@FM,"",Command_To_Chk_Rejects.$CommandOutput) > 0 solution works

I will try and understand what it does but it seems to work

The other solution

Command_To_Chk_Rejects.$CommandOutput[1] > 0 does not seem to work

Thanks a lot again and I will consider this post closed

Regards
Sigma

chulett · Post by **chulett** » Tue Oct 07, 2008 7:53 am

Check the one that "doesn't work" - you changed what I posted. Angle brackets, not square brackets.

sigma · Post by **sigma** » Wed Oct 08, 2008 7:03 am

I did change it as the angle brackets would not compile

I will try it again and post here shortly

It would become red as an expression indicating something not syntactically right but maybe I missed something let

I will post backhere shortly

ray.wurlod · Post by **ray.wurlod** » Wed Oct 08, 2008 2:58 pm

What error did you get from the compiler when "it wouldn't compile"?

Instead of the angle bracket notation you can use a Field() function which is equivalent (that is, the delimiter is @FM).

Code: Select all

Field(Command_To_Chk_Rejects.$CommandOutput,@FM,1,1) > 0