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



1. Someone had indicated on a earlier post that they could not get the
SQL errors on a SQL compile because they went to QTEMP. Using my compile
tool, you can solve this problem.

      *_> CNLLSTSPLF SRCFILE(@2/@1) SRCMBR(@3)                      
      *_> DLTMOD MODULE(@5/@4)                                      
      *_> CRTSQLRPGI OBJ(@5/@4) +                                   
      *_>   SRCFILE(@2/@1) SRCMBR(@3) +                             
      *_>   OBJTYPE(*MODULE) COMMIT(*NONE) OPTION(*EVENTF) +        
      *_>   DBGVIEW(*SOURCE) CLOSQLCSR(*ENDMOD) +                   
      *_>   TOSRCFILE(@2/QSQLTEMP1)                                 

Note the TOSRCFILE. Instead of compiling to QTEMP, I send it to a
permanent library. Then when you click on the line, it has the compile
to bring up.

2. But the real question is why does compile in Green Screen of an SQL
program operate differently than in WDSC. 

If I compile a program in PDM and then do a F15, type 2 and then search
for *err, I find the errors. Now the important thing here that when the
compile runs, it is submited to batch. It is still being compiled to
QTEMP but it finds the error without any problems.

Now if I compile the program in WDSC, it either does not find the file
(I didn't use the trick above) or it goes to another screen to display
the error, not the screen with the code on it. 

I don't know if this is clear or not.

If WDSC has the compiled code, why doesn't it just go to the error in
the source?


 



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.