If you are unable to create a new account, please email support@bspsoftware.com

 

Condition Node and Stopping the Job Stream on a failure result

Started by cognosjon, 15 Jan 2010 07:24:10 AM

Previous topic - Next topic

cognosjon

Any help appreciated on this one,

I've a conditional node that works fine, in that if the result is a fail it writes a message to a log file and if the result is true it continues on it's merry way. My question is how do I get the job stream to stop if the condition node goes down the false route?


MFGF

Hi,

Are the nodes in the jobstream linked in series or do you have parallel processing legs?

If it's the former, simply link the False leg of the condition node to a procedure node that sends a message to the log file, and have no further links on from this procedure node.

If it's the latter, you need to define a procedure node with 'Abort' set as the Action on failure, and have the expression do something which will fail  (eg run a System function which tries to delete a non-existent file).

MF.
Meep!

cognosjon

Thanks for the reply,

it's actually the former. I have set the node so that on fail it sends a log message and ends there, however when I run the job it writes the log message and then reports the condition node as being successful and kicks on to the next jobstream node. No idea why?????? It's driving me mad.......
I may try your suggestion of pushing the failure node down the route of running some code that won't succeed after it's finished the logfile update.

Cheers

cognosjon

Even more confused now, shut down Data Manager, reopened re-run the job and it now functions as expected..... arrrrgggghhhhhh!!!!!!!!

Thanks again for the reply though much appreciated

LEO

In the procedure node which is linked to the FALSE leg, use the msglog() to write to the log file and then write EXIT(1).

EXIT(1) would cause ur job stream to fail with FALSE status and hence nothing further would proceed.