I am running a job that calls a procedure that updates, deletes, and inserts info into 45 tables. Each time the procedure executes it writes informational messages about the sql statement it performs.
This is great when you are debugging the job, but in production this job will execute about 100,000 calls and the log locks up the machine.
Question:
is there any way to turn the log off and not report each call?
Thanks in advance!
Steve
log files
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You can define a token and, based on whether that token is defined or not, conditionally compile the PRINT statement. In this way you can turn it on again when you need to test the next version.
Code: Select all
* Toggle between $DEFINE and $UNDEFINE to enable/disable test statements
$UNDEFINE TESTING
$IFDEF TESTING
Call DSLogInfo('Value of X is ' : X, "Routine Test")
$ENDIF
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.