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






For a permanent library on the TOSRCFILE parm of CRTSQLRPGI, it should
probably be *CURLIB.  Otherwise, as you said it would be replaced by other
programmer compiles.  I'm still unclear on how you tell CODE to use QTEMP
from another job, even if it has ended.  I have no trouble using the
intermediate source member in QTEMP as long as it was an interactive
compile.  I just click on a field in error and the source member opens up.
The problem is when this was a batch compile and the member goes away out
of the batch job's QTEMP since the job has now ended.  The member that CODE
would find after the batch compile would either be nothing or that last
member stuffed in QTEMP from the last interactive compile.  If we always
did interactive compiles then we would always be able to get to the current
job's QTEMP for that intermediate member.

Thanks,
Craig Strong

** Vern wrote:
Craig, we do a CRTSQLxxxI OPTION(*NOGEN) TOSRCFILE(QSQL) to put the source
into QTEMP in a file we know about. Then we have a CRTxxx (module, in this
case) that uses the generated source member. These are encapsulated in a
single program. That way, you don't lose the link to a job's QTEMP.

As you suggest, you could have the generated source go to a regular library
of your choice, then have your compile use that. But then that intermediate
source has to be leaned up - of course, it'd be replaced all the time,
maybe.

With the first approach, so long as you leave the spooled output where it
is, the STRCODE job or whatever can probably find it. Just a guess on my
part, however, haven't tried it. We do all our SQL stuff in builds and with
little programs on the system, not through CODE.


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.