|
Ron, In that case, I would centralize all SQL access into a single module. You could use dynamically prepared statements and an SQLDA or the call level interface. You can download an example of the former from the December 1999 issue of Midrange Computing at their web site. David Morris >>> ron.klein@brctsg.com 02/14/00 12:04PM >>> David, We are on V4R2. Only because we are a software house. So of course we also have to stay behind the current versions of OS for our customer's sake. Ron > -----Original Message----- > From: David Morris [SMTP:dmorris@plumcreek.com] > Sent: Monday, February 14, 2000 12:48 PM > To: MIDRANGE-L@midrange.com > Subject: Re: %editc > > Ron, > > What release are you referring to? I know that %EDITC works > for V4R3 and V4R4 SQLRPGLE modules. The pre-compiler is way > behind, but at least for these releases, this isn't one of > the areas that it lags in. I would recommend moving all SQL > related processing to its own module(s) so that you can insulate > your other modules from SQL's shortcomings. > > David Morris > > >Hi All, > > >I was just going through some of the BOFs and thought that the %EDITC > would > >be a great tool for some of the field manipulations we do here. I put it > in > >an RPGILE program and it runs great. I moved the identical statement to > a > >SQLRPGLE program and no compile. It says %EDITC is an invalid token. > >What's the deal, is IBM using two different compilers dependent on the > >program type? > > >Any thoughts. > > >TIA > >Ron +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.