I have a control job containing approximately 12 jobs or so. In one of these jobs only, I need to assign the preference of aborting after 1 warning. The reason is that:
1. I am loading a large target table with several rows.
2. Instead of reading from this large table in the next job based on the same criteria for the inserts, I simply create a flat file output that gets loaded
with the same rows that the table does.
3. I use the flat file output as input to my next process.
You can now see why I would need to fail this after 1 warning only. If for any reason the insert to the table fails, then there will be discrepancies between the flat file and the table. Logically, I have eliminated all reasons why this would be the case. You never know when a database issue may creep up however.
My question is: How do I set the preferences for this job alone, and leave the remaining jobs to abort after 50 warnings (the default)? If I were running this job as a standalone, then its easy to set this preference at run time, but I must run this with a set.
Thanks,
Nowell Henry
Corporate Data Warehouse Team
New York Life
Abort after 1 warning only
Hi Henry,
have you tried to use DSSetJobLimit???
I think this can help you.
Regards,
Riccardo
----- Original Message -----
From: "Nowell Henry"
To:
Sent: Wednesday, October 17, 2001 5:56 PM
Subject: Abort after 1 warning only
> I have a control job containing approximately 12 jobs or so. In one
> of these jobs only, I need to assign the preference of aborting after
> 1 warning. The reason is that:
>
> 1. I am loading a large target table with several rows.
> 2. Instead of reading from this large table in the next job based on
> the same criteria for the inserts, I simply create a flat file output
> that
gets
> loaded
> with the same rows that the table does.
> 3. I use the flat file output as input to my next process.
>
> You can now see why I would need to fail this after 1 warning only.
> If
for
> any reason the insert to the table fails, then there will be
> discrepancies between the flat file and the table. Logically, I have
> eliminated all reasons why this would be the case. You never know
> when a database issue may creep up however.
>
> My question is: How do I set the preferences for this job alone, and
leave
> the remaining jobs to abort after 50 warnings (the default)? If I
> were running this job as a standalone, then its easy to set this
> preference at run time, but I must run this with a set.
>
> Thanks,
>
> Nowell Henry
> Corporate Data Warehouse Team
> New York Life
>
>
>
have you tried to use DSSetJobLimit???
I think this can help you.
Regards,
Riccardo
----- Original Message -----
From: "Nowell Henry"
To:
Sent: Wednesday, October 17, 2001 5:56 PM
Subject: Abort after 1 warning only
> I have a control job containing approximately 12 jobs or so. In one
> of these jobs only, I need to assign the preference of aborting after
> 1 warning. The reason is that:
>
> 1. I am loading a large target table with several rows.
> 2. Instead of reading from this large table in the next job based on
> the same criteria for the inserts, I simply create a flat file output
> that
gets
> loaded
> with the same rows that the table does.
> 3. I use the flat file output as input to my next process.
>
> You can now see why I would need to fail this after 1 warning only.
> If
for
> any reason the insert to the table fails, then there will be
> discrepancies between the flat file and the table. Logically, I have
> eliminated all reasons why this would be the case. You never know
> when a database issue may creep up however.
>
> My question is: How do I set the preferences for this job alone, and
leave
> the remaining jobs to abort after 50 warnings (the default)? If I
> were running this job as a standalone, then its easy to set this
> preference at run time, but I must run this with a set.
>
> Thanks,
>
> Nowell Henry
> Corporate Data Warehouse Team
> New York Life
>
>
>