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

There IS NO "parameter list map" -- the service program level checking is strictly based on the names of the exported procedures or functions, and the order they are exported.   That's it!   It does nothing for you to detect if you pass an incorrect number of parameters.

On Friday, September 30, 2022 at 01:18:01 PM EDT, x y <xy6581@xxxxxxxxx> wrote:

Yes, by signature would have been better, but then every call to a given
member (i.e., subprocedure) in a service program would have to test the
signature before calling it; that action, even if it's efficient, will
eventually generate a lot of overhead simply based on the number of called
to service programs system-wide.  The system likely builds a table in
memory with member parameter addresses when a service program is
instantiated and this will shorten the code path for each call.

Adding a new member to the end of the binder language preserves the
original parameter list map.  Activated service programs won't be affected.

Wouldn't the *IMMED/*DEFER logic get busted too?

Yes, by position is a bit quirky but that's the way the database works and
we've managed that.

On Fri, Sep 30, 2022 at 10:02 AM Tom Daly via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

It's always seemed to me that binder is stub of an idea that was never
completed. Unlike level checks with files, for a srvpgm a third object is
introduced for "level checking". I've always thought this was odd since it
didn't add much. Binder would be more useful if it referred to the
signature rather than the ordinal position and if the signature was
generated and tied to the parameters.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.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-2023 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.