Re: Processes after CRTSRVPGM

IBM's service programs seem to have binder-source-generated signatures - no auto-generated ones. I'm all for this - especially as a vendor with customers that need to use the blame things - and do NOT want to keep recompiling. Now a middle ground might be to make additional sections in binder source for new functionality and versions.

Vern
-------------- Original message --------------
From: Buck <kc2hiz@xxxxxxxxx>

Adam Glauser wrote:

M. Lazarus wrote:

Lim,

[Specifying SIGNATURE on STRPGMEXP] tells the system that you are
managing the signatures.
This is almost the equivalent of setting LVLCHK(*NO) on your files.
It gets rid of the error message, but also disables the error checking!

That's a bit of a stretch in my opinion. It's true that specifying a
signature can cause problems. However, I think it's quite a bit simpler
to recreate or update a service program safely while overriding the
safety measures than it is to add a field to a file with LVLCHK(*NO)
without causing problems.

I agree with Adam. I think the difference is that with files, there is
no *PRV support, whereas with binder language, we can successfully use a
newly compiled service program with an old calling program.

I have a strong tendency to make my signatures look like strpgmexp
pgmlvl(*current) signature('01.02 20071019'). When I do a DSPPGM I can
immediately see what version of a service program it's bound to.

The caveat, of course, is that one must add new exports AFTER existing
exports or the calling program will call the wrong procedure without a
signature violation.
--buck
--
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.