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



Just a stab in the dark, but is she by any chance specifying the original 
source file in the TOSRCFILE parameter?  TOSRCFILE specifies where to put 
the 'temporary' source generated by the SQL precompiler.  I've never tried 
it to know if would even allow that, but I suppose if you put the original 
source file name in TOSRCFILE it would overwrite the SQLRPGLE source with 
the precompiler-generated source--that's what you would be asking it to 
do.  WDSc might be picking up the generated RPGLE member and not seeing 
that the SQLRPGLE member has been overwritten.

If this is what's happening, either leave TOSRCFILE(QTEMP/QSQLTEMP1)---the 
default---or specify a  location other than the original source.

wdsci-l-bounces@xxxxxxxxxxxx wrote on 01/31/2007 01:00:05 PM:

date: Wed, 31 Jan 2007 12:16:53 -0500
from: DHoffma@xxxxxxxxxxxxxxxxxxxxx
subject: Re: [WDSCI-L] Issue with SQLRPGLE source member

I have a question about an issue that just occured to one of our 
consultants.   She had created an SQLRPGLE source member.   Once she 
compiled the source thru WDSc, she noticed that an RPGLE member for the 
same program now appeared.

She deleted the RPGLE source member, and without any warning, the 
SQLRPGLE 
member was also deleted!

Can someone explain why this happens?

Thanks,
David Hoffman
Programmer Analyst
Commerce Insurance



As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.