Binding Directory Signatures

I've been researching implementing ILE RPG in our office versus OPM style coding. I've read through the ILE RPG Reference as well as the Concepts and Programmer's Guides. I now have *SRVPGMs moderately well figured out and I've defined Binding Directories for compiling my *SRVPGMS. I discovered the hard way that inserting a new procedure into a *SRVPGM and not recompiling all of the *PGMS that reference the *SRVPGM can lead to disasterous results due to the fact that the Binding Directory signatures don't match between the *SRVPGM and *PGM. I did further research and now have a vague understanding of using signatures on the Binding Directory when adding new procedures. It looks like I can add procedures to the *SRVPGM and then update the Binding Directory with the new procedure AND A NEW SIGNATURE and then recompile the *SRVPGM. That way, I won't have to recompile all of the *PGMS that call the *SRVPGM. That being said, I'm looking for some suggestions for good methodoloy for standardizing my nomeclature for the signatures. Does anyone have some sample Binding Directories they could share that shows multiple signatures that were defined as they added procedures to *SRVPGMs? Thanks, in advance.

Answer Wiki

Thanks. We'll let you know when a new response is added.

Here’s a good article on service programs and binding directories, Article ID: 20172.
You may have to be a member to access it. But I think they have a limited subscription for free.


Keep it simple. Use the name of the service program and a two, three or four digit sequence number. Don’t try embedding too much information in the signature; just increment the number. The service program name is a simple identifier and a sequence number makes things easier to find. If you expect to have more than a thousand versions, then go with a four digit number. Or if you want something version/release, you can still go with four digits — two by two.

What more can you possibly need?

Note that nothing actually stops you from stepping outside of a simple standard if truly unusual needs dictate a more explicit signature. Just don’t try to do it as a normal act.


Discuss This Question: 1  Reply

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Aglauser
    One suggestion I've come across is to use a signature containing a version number and the date, for example 'V1.00_20050808'. If you are interested in a really good course on effectively using subprocedures and service programs, check out: I'm not associated with Lab/400 in any way, I just found the information very useful and accessable. Hope this helps, Adam
    0 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: