In addition to what David has stated, there are differences in the way 
the query optimizer works, depending on whether the job is interactive 
or batch, so it could develop a completely different access plan in one 
as opposed to the other. Interactive queries are theoretically optimized 
to return a screen full of information as quickly as possible, while 
batch queries are supposed to run to completion as quickly as possible. 
It doesn't always work quite that way though. The query optimizer 
program (qqqoptim) is a piece of code, I think they sentence death-row 
inmates to work on in lieu of doing the dead-man walk. It's one complex 
Q#!#:!. There will be the occasional problem. If your debug session 
doesn't turn anything up, it might be worth a call to level 1. You could 
be the problem of the week. You get a plaque for that. I have several.
Pete Hall
http://www.pbhall.us/
fkany@xxxxxxxxxxxxxxxxxx wrote:
When I submit an SBMJOB an SQL RPG program, it takes almost an hour to
process.  When I manually run the SQL statements using STRSQL, the
processing takes about 10 minutes.
Anyone know why?
Thanks,
Frank
 
As an Amazon Associate we earn from qualifying purchases.
	
 
This mailing list archive is Copyright 1997-2025 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.