If you let the signature generate, you need the previous binder blocks. The
signature changes based on the number of exported procedure. So if you add a
new procedure signature will change (if it is automatically generated).
With the previous export blocks, the current and the previous signatures are
then included in the service program.
Based on the signatures the service program is locate before activating it.
In this case there is no need to rebind the service programs if new
procedures get added.
At activation time (service-)programs where an older signature was bound
(for calling procedures) can be found, since the current service program
also includes the previous signatures.
If you work with a single fixed signature, there is no need to keep the
previous export blocks. Since always the same signature is bound to the
(caller) (Service-)programs.
You can keep the previous export blocks just information for example for
keeping track which procedures where added.
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
Modernization ? Education ? Consulting on IBM i
Database and Software Architect
IBM Champion since 2020
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
"Train people well enough so they can leave, treat them well enough so they
don't want to. " (Richard Branson)
"Learning is experience ? everything else is only information!" (Albert
Einstein)
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of James
H. H. Lampert via MIDRANGE-L
Sent: Wednesday, 10 July 2024 20:25
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: James H. H. Lampert <jamesl@xxxxxxxxxxxxxxxxx>
Subject: Binder Language
I've managed to find my altered binder source for our custom version of
HTTPAPI, and it was indeed done to create an HTTPS-enabled version that
would be drop-in compatible with a non-HTTPS version 1.21 (at the expense of
it being drop-in compatible with any other HTTPS-enabled version).
And it looks like it would be easier than I thought to update this to a more
recent HTTPAPI.
I'm currently reading up on service program creation and binder language.
And I'm not sure I understand how multiple STRPGMEXP blocks work, or how the
PGMLVL parameter works with regard to them. Can somebody point me to
something that will explain it in terms even my aging "little grey cells"
can process?
--
JHHL
--
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
questions.
midrange.com
