Is there a parameter or setting that you can put into the 7.5.2 environment to keep it from logging 'warnings' when a job runs?
There are some developers that run this huge job and it logs about 400MB of warnings during the run.
Matt
Reducing Log file entries
Moderators: chulett, rschirm, roy
-
- Charter Member
- Posts: 560
- Joined: Wed Jul 13, 2005 5:36 am
- Location: Ohio
Sorry, but answers 2 and 3 don't apply to Server jobs.
Your best answer is to fix the job so that it doesn't generate any warnings. There's no reason on the planet why a Server job should generate anything but loverly little green Info messages.
Your best answer is to fix the job so that it doesn't generate any warnings. There's no reason on the planet why a Server job should generate anything but loverly little green Info messages.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Yup. Only two ways to keep those warnings in check - either don't create them or abort the job after X warnings to keep them from overflowing your logs.
If neither one of those work, perhaps try setting this parameter:
APT_BAT_UPSIDE_HEAD=True
Oh, wait... Server job. Never mind.
If neither one of those work, perhaps try setting this parameter:
APT_BAT_UPSIDE_HEAD=True
Oh, wait... Server job. Never mind.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Well designed jobs do not generate warnings unless something goes wrong (as opposed to is wrong). Tell your developers to fix the job so that it detects problems rather than generating warnings.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.