Hi,
Is it possible to call a control job from a scheduled Report Caster control job?
Thanks
Sophie

I assume that "control job" you means is nothing but one fex procedure. And you can invoke any procedure from a scheduled report caster job just by calling that procedure under "Post-processing Procedures".

Also check out DSTRUN.

Hi,

Yes, it's a fex procedure scheduled on Report Caster which call other jobs within it.

Normally, it run successfully when calling a 'normal' job. However, when calling another control job (which has its own 'child jobs' within it), the 'sub' control job failed to run but all other 'normal' jobs run successfully within the first control job.

Hope I make myself clear here
Thanks

This is what I understand from your comments. So let’s say you have Job1 which is scheduled in Report Caster. Job1 in turn calls say: Job2, Job3 and Job4.Lets say Job2 and Job3 are normal jobs (Meaning, these jobs do not further INCLUDE or EXecute any other fex procedures) and lets say Job4 is a control job (Meaning, it in turn calls Job5 either by INCLUDE or EX command).

Now, the problem you are facing could be that when Job1 is executed by Report Caster, the Jobs: Job2 and Job3 are completing successfully and where as the Job5 (called with in Job4) is failing. Correct?

If the above scenario is what you are facing then answer the below questions:
1) What is the error message you are getting?
2) If you are running Job4 stand-alone from DevStudio, is the Job5 completing successfully?
3) Did you tried to run just the Job4 from Report Caster and is that completing successfully?

If the scenario that I have mentioned above is not correct then please try to provide such scenario.

Hi, thanks for the respond.

Yes, the scenario is similar to what was described.

There is no error message. The primary Control Job log showed that it run sucessfully with no error. However, the 'child' jobs within the sub control job didnot run.

We resubmitted the sub Control Job (stand-alone), and it run sucessfully.

Thanks

Sohpie,

Run the main job from RC manually but choose to have traces turned on. The traces can be located (default) in [install drive:\dir]\ibi\reportcaster76\trc. choose tyo trace both schedule and fex.

These may or may not tell you what is being run but the fex that is run by RC will be shown within the trace folder and you might be able to see if there are any anomolies etc.

If you still can't fathom it out then why not set (using harsha's scenario abpve) Job4 to kick off a scheduled job (set as "run once") by setting the next runtime to a time a fex minutes in the future (see Jodye Yates' excellent article).

Good luck

T

For everyone, don't forget that there are many tips and techniques available from the Developer Centre )see link top left), that may be able to spawn ideas on how to overcome your individual problem. Just keep an open mind on the way forward.