|
Darren ... Having spent most of the day yesterday trying to debug an embedded SQL statement, your comment about what would cause the error "query options file couldn't be retrieved" caught my eye. I had the same problem yesterday. What I noticed was that when I was running debug, I always saw that message when I looked at the job log. When I ran the program without debug (even though my same SQL error was still there!), I didn't see the message in the job log. I don't think I ever really "fixed" the problem, but it seemed to be related to debug, and I don't think it was hurting anything. Curious if someone else knows what this message really means ... maybe I have another problem I don't know about! darren@dekko.com Sent by: To: rpg400-l@midrange.com rpg400-l-admin@mi cc: drange.com Subject: RE: SQL query optimization 02/12/2002 08:30 AM Please respond to rpg400-l >'SELECT QCCAT, QCCACT FROM QACAT00 ORDER BY QCCAT ' >The keyfield in the file is 'QCCAT' >Why is it not using the access path of my logical? (Mike) Mike, This is a fairly simple statement. I'm sorry I can't offer a concrete solution yet. One thing I do to troubleshoot SQL is the STRSQL. You can STRDBG and then play with different interactive SQL statements to try and deduce what is going on. I'm a little concerned that it said your query options file couldn't be retrieved, I wonder what would cause this... _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l or email: RPG400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
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.