× 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: ILE Binding Confusion
  • From: Scott Mildenberger <Smildenber@xxxxxxxxxxxx>
  • Date: Thu, 9 Mar 2000 10:33:13 -0700

Jeff,

If you had used this procedure previous to doing the update service program
then the old version would still be active in the activation group.  You
could force the new version by doing RCLACTGRP on the activation group that
was active.  If it was the default activation group then you would have to
signoff and then back on.  This can cause much confusion when testing and
you forget to reclaim the activation group in between changes.  I believe
the service program reference is resolved when it is first accessed, if the
activation group remains active then the reference is never re-resolved.
Being aware of this is can be very important in determining when to update a
service program.  If every job needs to see the changes at the same time
then no one can be active when updating, if the change can be 'phased' in
then you can update the service program and eventually every job will see
the changes.  


Scott Mildenberger


> -----Original Message-----
> From: Jeff Crosby [SMTP:jlcrosby@fwi.com]
> Sent: Thursday, March 09, 2000 8:57 AM
> To:   RPG400-L@midrange.com
> Subject:      ILE Binding Confusion
> 
> I have a service program compiled in RPG/ILE.  There is only a single
> *MOD object in the service program.  I made a slight change to one of
> the procedures in this service program (I added one item to a
> compile-time array).  I then recreated the *MOD object and did an
> UPDSRVPGM.  Note that I did not add or remove any procedures, so the
> service program's signature did not change.  The UPDSRVPGM command was
> as follows:
> 
> UPDSRVPGM SRVPGM(DILGARD/SUBRAUT) MODULE(DILGARD/SUBRAUT) +
>           EXPORT(*SRCFILE) BNDDIR(DILGARD)
> 
> The binder language source was:
> 
>  StrPgmExp PgmLvl(*CURRENT)  
>    Export Symbol(AutDesc)    
>    Export Symbol(Authorized) 
>    Export Symbol(AutSelect)  
>    Export Symbol(IsRchStrDt) 
>    Export Symbol(IsRchStrD8) 
>    Export Symbol(ListAutCod) 
>    Export Symbol(RtvOrGdShw) 
>  EndPgmExp                   
> 
> I then ran a CLLE program that did a CALLPRC to one of the procedures
> (LstAutCod) in this service program.  The compile-time array change was
> _not_ reflected.  After recreating the CLLE *MOD and *PGM objects, then
> the change was reflected.
> 
> I thought that service programs were bound by reference such that when I
> change a service program, that change is immediately reflected to any
> calling program.  What am I missing?
> 
> -- 
> -Jeff
> +---
> | 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
> +---
+---
| 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-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.