|
SQL and CODE/RSE do not play together well. For that matter RPG has issues with SQL too. :>) In addition to Vern's suggestions, you might want to check the midrange archives under SQL or RPG as well as CODE. there have been some lengthy discussions about embedded SQL in the last several months. Dave Boettcher -----Original Message----- From: craigs@xxxxxxxxx [mailto:craigs@xxxxxxxxx] Sent: Friday, August 29, 2003 12:04 PM To: code400-l@xxxxxxxxxxxx Subject: Re: Why does my RPG program compile twice? I am having this SQL RPGLE problem too, I was just never bothered by it enough to mention it until now. I cannot link to fields from the compile listing for the SQL RPGLE. I tried CRTSQLRPGI with DBGVIEW(*SOURCE) and OPTION(*EVENTF) and then with DBGVIEW(*NONE) and OPTION(*EVENTF). I think that answers one of the previous questions. The last discussion on this topic on this thread ended with PTF SI06000 and SI06922 already installed on our system. These were supposed to do with debug/eventf. These are still installed on our system and we are still having the problem. We are still running V5R2 and WDSC 5.0.1. When I execute the CRTSQLRPGI with OPTION(*EVENTF) and there is an error in the source, in all cases, the following happens after the compile listing shows up and I click the field in error: 1. A box pops up that says, "Object not found QSQLTEMP1". EVF2062 RC=291 on top. I click OK. Then 2. "Unexpected error opening file '<OS400>QTEMP/QSQLTEMP1(<mbr>)'" appears at the bottom of the compile listing. The field appears under '<OS400>QTEMP/QSQLTEMP1(<mbr>)' even though that member exists in a different library and source file. My guess is that CODE/400 is reading a different QTEMP than used to create the object in batch. Why should it be using QTEMP in the first place? I then developed a theory that if I compiled interactively I would be able to get to the member in QTEMP. Sure enough, I compiled interactively and when I clicked on the field in error on the compile listing, the QTEMP member opened in CODE and I was taken to the error. I think doing this interactively is as worthless as batch anyway. Why would you want to edit a member in QTEMP? At least you can see the error. I think the problem is the fact that the member is copied to QTEMP behing the scenes and compiled from there. Why does it do that and can we get around this problem? I am getting into writing more and more SQL RPGLE programs but not being able to get to errors quickly is a big hinderance to using CODE with SQL. Especially when it is one of my top reasons for using CODE. Also, especially when IBM is pushing SQL. Does SQL RPG have the same problems? I usually don't write in RPG III but I will probably run into quite a bit of legacy SQL RPG code soon. Thanks, Craig Strong ** Rob wrote: Violaine, I am running V5R2 and still have this issue. ServicePackLevel = 3 VERSION = 4.0.0 Cume = TL03021 WRKPTFGRP PTF Group Level Status SF99519 40 Installed SF99502 6 Installed SF99271 7 Installed SF99190 10 Installed SF99169 8 Installed SF99149 3 Installed SF99148 3 Installed SF99098 7 Installed SF99085 2 Installed SF99039 2 Installed Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Violaine Batthish" <batthish@xxxxxxxxxx> Sent by: code400-l-bounces@xxxxxxxxxxxx 03/28/2003 09:04 AM Please respond to CODE/400 Discussion & Support To: CODE/400 Discussion & Support <code400-l@xxxxxxxxxxxx> cc: Fax to: Subject: Re: Why does my RPG program compile twice? Hi Ben, There was a bug with the SQL compilers such that if you specify DBGVIEW (*SOURCE) , the OPTION(*EVENTF) is ignored. This would have the result of the user not being able to see any errors found in the error list. This problem was fixed by the compilers in V5R2M0. To circumvent the problem, CODE compiles twice: once with OPTION(*EVENTF) and DBGVIEW(*NONE) and then again with OPTION(*NOEVENTF) and DBGVIEW(*SOURCE) This ensures that you see any errors in the error list, and that you have your *PGM or *MODULE object generated with the appropriate debug level. In WDSc 4.0, CODE is smart enough to detect whether the host is V5R2M0 and only compile once for that release, and twice for earlier releases. Hope this helps! Violaine Batthish CODE Project Lead batthish@xxxxxxxxxx IBMCA(BATTHISH) WDT/400 page: http://www.ibm.com/software/ad/wdt400 WDT/400 Support : http://www.ibm.com/software/ad/wdt400/support Ben_Pforsich@xxxxxx ns.com To: CODE/400 Discussion & Support <code400-l@xxxxxxxxxxxx> Sent by: cc: code400-l-bounces@x Subject: Why does my RPG program compile twice? idrange.com 03/27/2003 03:47 PM Please respond to CODE/400 Discussion & Support Just wondering why every time I initiate a compile from CODE Editor (usually an SQLRPGLE source type), two jobs (running that EVFCFDBK pgm) are submitted on the 400 and I get two messages back on my 400 session saying that the job either ended normally or abnormally, instead of just one? Looking into the job logs, I see that they appear to be identical. Both are executing the command: CALL PGM(QDEVTOOLS/EVFCFDBK) PARM('37' 'Y' 'AS400' 'CRTSQLRPGI OBJ(J20##X2DEV/JKG100) SRCFILE(JBACUST/QRPGSRC) SRCMBR(JKG100) OPTION(*NOEVENTF) DBGVIEW(*SOURCE)') I'm running WDT/400 v5.1 SP5 on Win 2K with SP3. In Program Generator, my default settings are: Batch, Notify on Complete, Job Description: *USRPRF, Job Queue: QPGMR, Default ILE Command: CRTBNDxxx Just a nuisance. Is there something I have configured incorrectly? Ben Pforsich Bob Evans Farms, Inc. Food Products Division I/S Department Columbus, Ohio Ben_Pforsich@xxxxxxxxxxxx _______________________________________________ This is the CODE/400 Discussion & Support (CODE400-L) mailing list To post a message email: CODE400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/code400-l or email: CODE400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/code400-l. NOTE: WDSc for iSeries disucssion has it's own mailing list. Information can be found at http://lists.midrange.com/cgi-bin/listinfo/wdsc-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.