Abort after 999.999 warning

eoyylo · Post by **eoyylo** » Mon May 30, 2005 8:50 am

Hi,
I must run a job with dsrun command in a unix shell.
To run the job I use the next command:

bin/dsjob -run -warn 999999 <project> <job>

and it aborts after 999.999 warning messages.

Is it possible to set the warning limit to "UNLIMITED"?
Which is the unix command to do this?

Thanks in advance

Regards

chulett · Post by **chulett** » Mon May 30, 2005 8:54 am

Set the limit to zero for unlimited.

ArndW · Post by **ArndW** » Mon May 30, 2005 8:58 am

eoyylo,

You could set the warnings to 0

but....

For each warning an entry is written to the log file. For that large a number of warnings you are going to get a job performance that is probably about as fast typing the data into the database by hand (well, maybe not quite that bad, but close enough).

So the better answer to your question is that you absolutely need to get rid of your warnings. Have you approached the issue from tahat angle yet?

chulett · Post by **chulett** » Mon May 30, 2005 9:07 am

Wasn't gonna open that can of worms, Arnd.

More than a million warnings? And that's ok?

Yikes.

ArndW · Post by **ArndW** » Mon May 30, 2005 9:15 am

Craig - I had to say that about the warnings (if I hadn't I'm sure Ray would have put it in somewhat stronger words when he logs in later). The overhead to write the warnings in that job is going to be far higher than that of the job itself. I've had warning that I was sure I couldn't get rid of - until I was forced to do so, then a solution was found.

roy · Post by **roy** » Mon May 30, 2005 9:19 am

Kinda makes you think ...
Are you after Rays position as top poster by far ???

gotta give him some scraps for more posts LMAO

Just Kidding

Guessing a month tops till you pass my posts Arnd WTG (Way To Go !!!)

ArndW · Post by **ArndW** » Mon May 30, 2005 9:32 am

Roy - I'm going for the fast-food high volume posting approach; I'll leave the real quality to Roy's and Ray's (play on words to one of my favorite international food chains, and my favorite bartender [but another Ray]

).

ray.wurlod · Post by **ray.wurlod** » Mon May 30, 2005 4:01 pm

In a production environment, one warning is too many imho.
One should always seek to design server jobs so that they do not generate any warnings. Then, if one ever does occur, it means that something truly unusual has occurred.

In parallel jobs it's more difficult to eliminate certain specific warnings, but it remains an admirable goal to seek to achieve this result.

DSXchange

Abort after 999.999 warning

Abort after 999.999 warning

Warning!! Warning!!