Re: Processes after CRTSRVPGM

On 14/02/2008, at 5:48 AM, Grizzly Malchow wrote:

I am using binder language with *PRV and *CURRENT levels and creating a
new signature every time. It's not ideal but it works.

That is the correct process. If you do this properly you DO NOT need to rebind the consumers. You only need to bind programs/service programs that use whatever it was you changed that caused you to issue a CRTSRVPGM again.

I'll look into using UPDSRVPGM, when it's applicable, instead of CRTSRVPGM every time.
Thanks

Makes no material difference to the signature validation process. Slightly easier in terms of change because you don't need to know all the modules in the service program but that is usually handled by a decent change management system.

Even when using UPDSRVPGM the signature should be changed if you add a completely new module or new exported procedure to an existing module. The only time the signature should not change is if you are in the camp that specifies a fixed signature (e.g., IBM using the *SRVPGM name as the signature). I think the signature should change whenever the public interface changes. That is:
1) New exports added
i) New module
ii) New exported procedures
iii) New exported data
2) Changes to interface of existing procedures
i) New parameters added (*NOPASS)

If this is done properly even though the signature changes you will not have to rebind consumers. See the archives for more detail. This topic has been done to death by me and sundry others.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------