• Subject: Re: CRTPGM Creation Options *DUPVAR *DUPPROC
  • From: "Joep Beckeringh" <joepb@xxxxxx>
  • Date: Thu, 22 Jul 1999 23:40:14 +0200

We use option *DUPPROC because it enables us to override procedures, just
like we use the library list for dynamic calls.  We build standard
applications.  When we customize programs for clients, they are put in a
client library, that is placed in the library list before the standard
libraries during runtime.  Using *DUPPROC we can do the same with procedures
at build time.

Joep Beckeringh

----- Oorspronkelijk bericht -----
Van: <Jon.Paris@halinfo.it>
Aan: <RPG400-L@midrange.com>
Verzonden: donderdag 22 juli 1999 21:41
Onderwerp: Re: CRTPGM Creation Options *DUPVAR *DUPPROC


>
>
> It is not a good idea to use these options since it makes it impossible to
> defend against problems caused by someone creating a completely different
> procedure with the same name as another.  I would suggest that you
establish a
> "common" binding directory and whenever a routine is needed in more than
one
> binding directory, it should be placed in the common one instead which all
> compiles would then reference.


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
* be directed to the list owner / operator: david@midrange.com          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].