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


  • Subject: Re: V5 - RPG announcements?
  • From: bmorris@xxxxxxxxxx
  • Date: Wed, 25 Apr 2001 17:35:22 -0400
  • Importance: Normal


>Date: Wed, 25 Apr 2001 15:05:47 -0500
>From: rob@dekko.com
>
>So if I use a /COPY in an /INCLUDE, or a /INCLUDE within a /INCLUDE will
>that now work?

Rob, the RPG compiler treats /COPY and /INCLUDE exactly the same way, so
you can mix and match however you like, as long as SQL isn't involved.
If SQL is involved, /INCLUDE is usually best.

- if you're using SQL and the file has things that SQL needs to see,
  like host variable definitions or embedded SQL, use /COPY
- if you're using SQL and the file has /copy (or /include) or other things
  that SQL doesn't like, use /INCLUDE
- if the file is a copy file already, and you're doing a nested copy,
  use /include within the copy file, just in case you might need it for
  SQL sometime
- otherwise, use whichever you like

By the way, /INCLUDE is available with PTFs for V4R2 and V4R4.  Check the
archives for the PTF numbers.

Barbara Morris


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-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 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.