Wait For File Activity generating incorrect code?
Posted: Mon Sep 26, 2011 8:21 pm
I've been having problems with a Wait For File activity going to the exception handler rather than the links indicated by triggers.
After playing around with different options and examining the generated code, it is my belief that a Wait For File Activity generates incorrect job control code if
* you have "Automatically handle activities that fail" enabled AND
* you do not have an "Otherwise" expression on one of the links.
The effect of the incorrect code is that it checks for a failure (any response <> 0) and branches to the error handler BEFORE it checks the trigger conditions.
Maybe I misunderstand how I am supposed to use this, but this seems wrong to me.
I was hoping to have one link check for DSJE.NOERROR, a second link check for DSJE.TIMEOUT and any other failures handled by the error handler.
Is anyone able to shed any light on this behaviour, or at least provide tips the conditions they usually use with a wait for file activity?
After playing around with different options and examining the generated code, it is my belief that a Wait For File Activity generates incorrect job control code if
* you have "Automatically handle activities that fail" enabled AND
* you do not have an "Otherwise" expression on one of the links.
The effect of the incorrect code is that it checks for a failure (any response <> 0) and branches to the error handler BEFORE it checks the trigger conditions.
Maybe I misunderstand how I am supposed to use this, but this seems wrong to me.
I was hoping to have one link check for DSJE.NOERROR, a second link check for DSJE.TIMEOUT and any other failures handled by the error handler.
Is anyone able to shed any light on this behaviour, or at least provide tips the conditions they usually use with a wait for file activity?