× 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: Binder Language problems
  • From: "David Morris" <dmorris@xxxxxxxxxxxxx>
  • Date: Thu, 30 Jul 1998 15:41:51 -0600

Nelson,

Sounds like you are adding exports correctly.  The current export area cannot 
change order.  It seems as if the person who created binding source support 
thought it would be really useful to be able to change the name of an exported 
procedure or value.  Instead of allowing the name to be overridden with another 
command, they decided to use the ordinal value for exports in the *CURRENT 
section to determine what procedure gets executed in the *PRV section(s).  We 
have not found it useful to change the name of an export.  We have accidentally 
changed the order of *CURRENT exports.  When the order changes you find 
programs calling the wrong procedure or using the wrong value.  All of this is 
documented in the ILE concepts manual.

We ended up writing a command to add service exports.  It automates the process 
that you describe below.  We also created a remove obsolete signitures command. 
 To do this you need to have a cross reference of modules to service programs 
and programs/service programs to service programs.

David Morris

>>> Nelson Smith <ncsmith@gate.net> 07/24 8:04 PM >>>
When I execute the RTVBNDSRC command on an ILE module to add new exports
to previously existing binder source, the command always puts the new
source at the end of the source member and it alphabetizes the exports.

I cannot get my service programs to compile properly unless the new
source is at the beginning of the binder source member and if I leave
the exports alphabetized, previously compiled calling programs will get
signature errors.  To get clean compiles, I have to manually move the
new source to the top of the source member and rearrange all the exports
to look like the previous version plus the new ones at the end.  

Am I doing something wrong in the way I call RTVBNDSRC or is it just a
poorly written command?  For the life of me, I cannot figure out why IBM
would create a command that generates source code that is incompatible
with the way it's own compiler works.
-- 
Nelson Smith
"Standards are Wonderful....cause there's so many to choose from!"
ncsmith@gate.net 


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