|
SQL normally do not send messages in a job log. If you see messages, it means that SQL is running in debug mode. Debug mode is turned on by one of two ways: - obvious - STRDBG - less obvious - by a setting in QAQQINI file I bet somebody set debug mode in QAQQINI file (probably in QUSRSYS) and now everybody's SQL runs in debug mode. Alexei Pytel "William Washington III" To: <MIDRANGE-L@midrange.com> <w.washington3@star cc: band.net> Subject: SQL Fetch causes jjob message queue Sent by: overflow owner-midrange-l@mi drange.com 04/26/2001 07:14 PM Please respond to MIDRANGE-L Hi All, I have an interactive program that uses SQL FETCH statement to read records. Even though the SQLCOD is zero (i.e., ends normally,) it puts a message on the job message queue. The message is SQL7963 - Fetch 1 record .... How do I prevent the informational/completion message from generating in my job message queue (and job log)? It kills my session once a certain number of messages has been sent. Thanks in advance... William =============================== William Washington III Njia Systems Incorporated w.washington3@njiasystems.com 312-719-0519 =============================== +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.