Re: binder language, binding directories, bind by copy/reference

["Joep Beckeringh" <joep.beckeringh@xxxxxxxxxx>]

Hey Joe,

When I almost have to sneeze, I look outside. When I see the light, the
sneeze will follow :-)

But seriously, you are a knowledgeable guy; you know Java and understand
MOVE, but binder language is too much? What exactly don't you understand?

Every service program has a signature. In the binder language you can just
use a string for signature (like SIGNATURE('SRVPGMNAM') or SIGNATURE('JOE'))
or you can use the default SIGNATURE(*GEN). In this case the name of the
exports are hashed into a string.

When a program is bound (or linked, as it was called before IBM invented
ILE), the binder looks up the name of the procedure to be called, but only
records the number of the entry point. Your source says 'call procedure
dosomething', but the program object only knows 'jump to entry point #3'. So
when you move procedure dosomething to another position, you are in trouble.
Hence the signatures, which are meant to give you a level check when you
change the service program.

Joep Beckeringh
Haaaachooo!!!

----- Original Message -----
From: "Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
To: "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
Sent: Friday, June 20, 2003 12:40 AM
Subject: RE: binder language, binding directories, bind by copy/reference


> > From: Joep Beckeringh
> >
> > This is actually the way we do it, we hardcode package name and
> > release # in the signatures of all our service programs.
>
> AGGHHHHHHHHHHH!
>
> This is all sooooo cool and I don't quite get it.  Whenever you folks talk
> about this stuff, I ALMOST understand it.  It's like when you ALMOST have
to
> sneeze... incredibly frustrating!
>
> Does anyone have a SIMPLE, real example that I can compile on my machine
to
> exemplify the pros and cons of this?  Or if something from one of the
> manuals is best, just point me at it.  I have to be able to touch
something
> (and break it <grin>) in order to understand it.  (Hence the piles of
> lawnmower parts in my backyard when I was growing up.)
>
> Joe