× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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 thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.