Page 1 of 1

Problem while running job through shell script

Posted: Mon Apr 24, 2006 6:52 am
by amit_haldar
Hi,

I am using Datastage 7.5.1.A edition. I am facing one problem. I am trying to run a job through shell script using the following comand in the DSHOME directory:

dsjob -run FINLANDPRJ test_contact_load

where FINLANDPRJ is the project name
and test_contact_load is the job name.

It's showing job aborted after 50 errors. But while running the same job manually through the client it's running perfectly ok without any error.

I have drilled down the matter and found out that the command is working fine if we are populating upto 60 columns. The moment I add 61st column it's showing error using the above command, but even after adding the 61st column it works perfectly ok while running it through client.

In another job although the number of columns is less than 60 but it was showing the same problem. It was due to the date field and after modification of the code it worked perfectly fine.

Please help me in solving this problem.

Thanks and Regards

Amit

Posted: Mon Apr 24, 2006 6:56 am
by ArndW
What is the warning you are getting?

Re: Problem while running job through shell script

Posted: Mon Apr 24, 2006 6:57 am
by chulett
amit_haldar wrote:It's showing job aborted after 50 errors. But while running the same job manually through the client it's running perfectly ok without any error.
If the 'client' is the Designer, then I would bet it is not running 'perfectly ok' - but rather you have the warnings set to unlimited. It will look all green and good from the Designer, but the Director will show Finished (see log) and it will have more than 50 warnings in it.

Posted: Mon Apr 24, 2006 7:19 am
by amit_haldar
ArndW wrote:What is the warning you are getting? ...

It's showing job aborted after 50 errors

Posted: Mon Apr 24, 2006 7:23 am
by sb_akarmarkar
Hi,

Have you check the log from datastage director after runing from shell.
what is the log it is showing ?
Go through the log...

Thanks,
Anupam

Posted: Mon Apr 24, 2006 7:47 am
by amit_haldar
Hi,

I got the message "job aborted after 50 errors" from the director.

Posted: Mon Apr 24, 2006 9:19 am
by ArndW
The job won't abort until it hits 50 warnings by default, it always aborts on the first error. As stated earlier, the different behaviour is caused by differing number of allowed warnings. Get rid of your warnings and the behaviour will be the same.

Posted: Tue Apr 25, 2006 4:19 am
by sb_akarmarkar
amit_haldar wrote:Hi,

I got the message "job aborted after 50 errors" from the director.

I need warings which will be in yellow colors icons in Director...

Thanks,
Anupam