Re: Processes after CRTSRVPGM

Right on David - Steve is like the guy who wanted to put a basement on his fish house. (It's cold here in Minnesota!) Either that, or he's happy to rebind everything that uses that service program.

There's a difference between in-house development and vendor development - vendors who distribute service programs to be used by customers need to avoid causing pain - like rebinding the world.

I go again to the source (sic) - IBM - check out the signatures on their service programs - lots of them are not generated - they are some variant of the service program name with maybe SRVPGM at the end. Maybe they make a policy of using generated for internal use items only - have no idea. But we went with using the same signature for most situations.

Later
Vern

At 02:48 PM 2/14/2008, you wrote:

Steve Richter wrote:
> There are two reasons I dont like adding new procedures to the end
> of the binding source. The first is cosmetic. I use the binding
> source as a document for finding the procedure I am looking for. For
> that purpose, I want the names listed alphabetically.

Um, seems to me that you're using binding source for entirely the wrong
reason. It's specific purpose is to allow you to specify the order that
procedures should be placed in the service program. Not documentation.


> Most as400 programmers dont understand ILE and service programs. In a
> shop where more than a single person adds procedures to a srvpgm,
> there is no protection that someone with a little knowledge will
> place the new export in its logical, alphabetical location in the
> binding source and CRTSRVPGM.

We put a standard header in our binding source with instructions where
to place new procedure and when the signature should be updated ...
we've *NEVER* had a problem.

david

--
IBM System i - For when you can't afford to be out of business

--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.