DSXchange

Posted: **Mon May 19, 2008 11:05 pm**

Designer (I believe) ignores anything you give in Job Run Options and uses the defaults (set using Tools menu in Director).

There does not appear to be any mechanism in Director for recovering the run and warning limits with which a job was run, even when non-default values are given.

If you really want to hack the only place I've found the information is in the RT_STATUS record for the job (this gets marginally more complex if the job is multi-instance).

Code: Select all

SELECT @ID FMT '40L', EVAL "@RECORD<18>" WARNLIMIT FROM RT_STATUSnnn WHERE EVAL "@RECORD<1>" = 'JOB';

where nnn is the job number from DS_JOBS.

Posted: **Mon May 19, 2008 11:27 pm**

Actually, the Designer ignores any default run time limit you may have established in the Director and always seems to default to 'unlimited'. The Director is the only thing that pays attention to that setting there.

I for one have never seen it 'abort after 50' when you haven't set it to 50... unless perhaps you have a Reject row with an 'Abort After' value?

Posted: **Mon May 19, 2008 11:53 pm**

Thanks Ray and chulett,

I didn't give any limits during run time for both warning and row tabs, also no values like abort after this much rows has been processed in job level.

Thanks, Ragu

Posted: **Mon May 19, 2008 11:55 pm**

Thanks Ray and chulett,

I didn't give any limits during run time for both warning and row tabs, also no values like abort after this much rows has been processed in job level.

Thanks, Ragu

Posted: **Tue May 20, 2008 12:09 am**

Then look in Director, under the Tools menu (Options) to learn that the default warning limit is 50.

DSXchange

How to find the job warning limits in director log