Keep job from running if it fails to compile?
Posted: Tue Aug 24, 2004 11:18 am
I am noticing some interesting behavior as part of our Version Control usage. On promotion, we set the flags to compile objects and mark them read-only. If a dependent object is missing, it would seem that the job would not be able to compile and we would see that in the compilation report. Instead, however, it appears that the job is not compiled at all, and the compiled version from source project is promoted into the target project. Nice, but it causes confusion since we have something missing from the target and no notification of the fact without looking at the jobs manually. It is also confusing because I would not be comfortable assuming that the code that is running is the new code and not code associated with a previous version. I thought that maybe compiling the jobs would help identify this situation when it occurs, but we cannot recompile in DataStage (read-only), and CompileAll gives the same behavior - it compiles without argument even though the dependent object is missing.
Does anyone understand how this works? Is there a way to identify when items are promoted to a target project but are not in a usable state? Should I just relax and trust that the job that is running is the one I wanted to run, even though it has red in the derivation column when I inspect the job?
Thanks,
Stan
Does anyone understand how this works? Is there a way to identify when items are promoted to a target project but are not in a usable state? Should I just relax and trust that the job that is running is the one I wanted to run, even though it has red in the derivation column when I inspect the job?
Thanks,
Stan