Multiple Job Steps SQL 2000

Hi,
I have 3 DTS packages I want to run after each other, in no particular
order.
I have x3 jobs, each running one of the DTS using CmdExec.
I don't want to run these jobs on individual schedules. I also don't want a
single DTS package with x3 steps to achieve the same thing.
I want visibility of Status etc available in the SQL EM Job view for each of
the jobs.
I created a single multi-step job, with each step invoking a DTS package
using CmdExec. This works but then the individual jobs are redundant and the
level of job status visibility is lost.
I created a single multi-step job, with each step using T-SQL and
sp_start_job. Now this ran the jobs and gave visibility of their individual
status but the jobs did not run synchronously. They all started together.
How can I write a single 'wrapper' job to start one job and wait for it to
complete before starting the next job? This allows me to maintain a single
schedule and yet see x3 status indicators?
ThanksCreate an another package , with three Execute Sql Task, and use work flow to
execute each task only after success so that it wont run synchronously.
Thanks,
Sree
"Gramps" wrote:
> Hi,
> I have 3 DTS packages I want to run after each other, in no particular
> order.
> I have x3 jobs, each running one of the DTS using CmdExec.
> I don't want to run these jobs on individual schedules. I also don't want a
> single DTS package with x3 steps to achieve the same thing.
> I want visibility of Status etc available in the SQL EM Job view for each of
> the jobs.
>
> I created a single multi-step job, with each step invoking a DTS package
> using CmdExec. This works but then the individual jobs are redundant and the
> level of job status visibility is lost.
> I created a single multi-step job, with each step using T-SQL and
> sp_start_job. Now this ran the jobs and gave visibility of their individual
> status but the jobs did not run synchronously. They all started together.
>
> How can I write a single 'wrapper' job to start one job and wait for it to
> complete before starting the next job? This allows me to maintain a single
> schedule and yet see x3 status indicators?
> Thanks
>
>