RE: problems with program binding

["Jonathan Mason" <jonathan.mason@xxxxxxxxxxxxxxxx>]

Hi Mihael

Using binder language isn't much of a development overhead - I find it takes
me around 30 seconds to open the source member and add a new sub-procedure
to the list of exports before I compile, and that's only if I've added a new
sub-procedure to the service program.

If you specify your own signature in the binder source it removes a lot of
the overhead of having to copy export blocks to maintain multiple
signatures.  I use the following for all my service programs:

        STRPGMEXP PGMVAL(*CURRENT) SIGNATURE('Astradyne UK Ltd')
          EXPORT SYMBOL("procedure_1")
          EXPORT SYMBOL("procedure_2")
            ..
            ..
        ENDPGMEXP

Just remember to add your new procedures to the end of the list and you're
done.

All the best

Jonathan

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Knezevic, Mihael
Sent: 08 December 2006 10:16
To: Midrange Systems Technical Discussion
Subject: problems with program binding

hi,

i got a little problem with the binding of programs. but first some
background. we have a test and production environment on one machine.
each has its own lib (we call it test and prod here for the discussion).
both libs are in the libl in the order: first test then prod (the
machine is a devel machine). we are using a global binding directory for
binding.

the case:

i'm working on a serviceprogram. the serviceprogram exists in it's old
form in the prod lib and in it's new form in the test lib. another
developer is working on a program which uses some procedures from my
serviceprogram. during the development phase everything is working fine.
now he promotes the program to the prod lib and the program gets the
signature of the serviceprogram in the prod lib. seems ok so far.

but now he calls the program (which is in prod) and it brings an error
(MCH4431). translation: Invalid programsignature. 

it seems that the program tries to call the procedures from the
serviceprogram in test (which is in libl before prod).

how can this dilemma be solved? is the only way out the use of the
binder language? that seems a lot more development overhead than having
a binding directory.

thanx in advance

mihael knezevic