For me is not necessary to build a program and use do-shout.
Design a flow to do this logical:
a) if a cm for db terminate well --> jobA end ok
b) move a file ---> second jobB
Using controlM only if the jobA terminates well the jobsB starts: is sufficient to link JOBA-TO-JobB (native functionality).
Is the condition: added is the jobA end well.
Is not necessary to build something, only link the two jobs.
Shout to Program
Having one job that do a shout to another program in postprocessing, and so have a separate control of the result. Its not logical specially if you have control-M...
And also in the controlM use you have contruct something, a shout and a script rather than using the controlM without programming. You dont understand, but having two jobs in controlM is more flexible, powerfull, simple and robust.
And try to consider the logical flow: is true in controlM interface you have only one job; but the real flow is two programs that run one after the correct ending of the first. Are two executions, two programs, why dont integrate them in one flow? You may have only advantages is you use controlM for the two (or more) jobs.
Forgive my point of view, but use the shout capabilities when you have complicated problems and dont complicate what is simple...
Regards
And also in the controlM use you have contruct something, a shout and a script rather than using the controlM without programming. You dont understand, but having two jobs in controlM is more flexible, powerfull, simple and robust.
And try to consider the logical flow: is true in controlM interface you have only one job; but the real flow is two programs that run one after the correct ending of the first. Are two executions, two programs, why dont integrate them in one flow? You may have only advantages is you use controlM for the two (or more) jobs.
Forgive my point of view, but use the shout capabilities when you have complicated problems and dont complicate what is simple...
Regards