|
|
Typically I run the application 5 or 6 times.
What happens is that I roll thru a 100,000 record file using
an SQL Fetch (in order to process and determine if I want the record on the
subfile.) Each fetch is accompanied by a nice little message that says the
fetch completed normally. If I can eliminate this message, everything will
be fine.
When the job dies, it generates a log file over 4000 pages,
with 99% of the log being the aforementioned completion message.
Any ideas?
William Washington III
Njia Systems Incorporated w.washington3@njiasystems.com 312-719-0519 >Date: Thu, 26 Apr 2001 19:46:26 -0700 >From: Ken.Slaugh@cm-inc.com >Subject: Re: SQL Fetch causes jjob message queue overflow > >You do have the option of changing the job message system value to wrap the >messages as there are system values to handle this problem. Although >creating a new job once in a while is not a bad idea either. > >How long does your job run before this problem occurs? > >Ken Slaugh (707) 795-1512 x118 >Chouinard & Myhre, Inc. >AS/400 Professional Administrator/MSE >Client Access Specialist >http://www.cm-inc.com/ > >>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 ....=20 >> >>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 >> |
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.
midrange.com
