× 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: Quick ILE question about service programs
  • From: "Slava Zharichenko" <Slava.Zharichenko@xxxxxxxx>
  • Date: Fri, 27 Apr 2001 21:32:12 -0400


Thanks.
I think it is much clear now that the only way to bind by /copy is to bind
actual modules, once modules are assembled into service program only bind
by reference is possible . It is actually make sense now that service
program can be used by other programs and have to be independent.

Thanks everybody









Jon.Paris@hal.it@midrange.com on 04/27/2001 06:08:44 PM

Please respond to RPG400-L@midrange.com

Sent by:  owner-rpg400-l@midrange.com


To:   RPG400-L@midrange.com
cc:

Subject:  Re: Quick ILE question about service programs




Definitive answer (It should be anyway since I've been teaching this stuff
since before it was released!! <g>)

A CALL (or CALLP where the prototype says EXTPGM) will _always_ be a
dynamic call.  Fully resolved at run-time.  No static binding of any kind -
no module copying - just the same old call we had back on S/38 and AS/400
before ILE.

An Eval or CALLB  (or CALLP when EXTPROC is specified) will either bind by
reference (to a Service Program) or bind by copy (to a procedure in a
separate Module object) - all this provided the call is not to a subproc in
the same module in which case the question is irrelevant.

Which of the two methods (copy or reference) is up to the programmer.

Copy will be used if the module containing the procedure is specified to
the CRTxxxMOD, CRTPGM or CRTSRVPGM command.  It will also be used if the
procedure is located by virtue of the module being listed in a binding
directory.  When copy is used a "copy" of the _module_ is included in the
*PGM object.  No run-time resolution is required.

Reference will be used if the service program containing the procedure was
listed to the CRTxxxMOD, CRTPGM, or CRTSRVPGM. As for bind by copy, it will
also be used if the service program is located by virtue of being listed in
a binding directory.  When reference is used no copy is made - rather a
"memo" is made that a specific service program and specific entry point
within that service program will be used.  Final linkage is made at
run-time.

Since all IBM routines (to the best of my knowledge) are always supplied in
service programs they will always be bound by reference which means that
they are not copied anywhere but linked at run-time.

Hope this helps.



+---
| 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
+---



______________________________________________________________________
Important Email Information



The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this email
by anyone else is unauthorized. If you are not the intended recipient, any
disclosure, copying, distribution or any action taken or omitted to be
taken in reliance on it, is prohibited and may be unlawful. If you are not
the intended addressee please contact the sender and dispose of this
e-mail.


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