RE: Processes after CRTSRVPGM

Yes. Sort of. However, if you exam it a bit more, it really makes no
different between the static signature method and the *prv/*current
signature method. Both methods require you to export new procedure to
the end of the service program. Otherwise, unpredictable result will
occur.

So, if you do below, existing program (Compiled before the *current was
added) will not get signature violation but it will still execute the
wrong procedure. ==> *prv/*current method does not really buy you
anything (Actually it is more trouble than it worth).

STRPGMEXP PGMLVL(*CURRENT)
EXPORT SYMBOL(IFS_LinkExist)
EXPORT SYMBOL(IFS_FileSize)
ENDPGMEXP

STRPGMEXP PGMLVL(*PRV)
EXPORT SYMBOL(IFS_FileSize)
ENDPGMEXP


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of M. Lazarus
Sent: Wednesday, February 13, 2008 1:58 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Processes after CRTSRVPGM

Lim,

That method 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!

-mark


At 2/13/08 02:14 PM, you wrote:

I personally like the idea of using named signature.

STRPGMEXP PGMLVL(*CURRENT) SIGNATURE('SomeSignatureName')

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Grizzly Malchow
Sent: Wednesday, February 13, 2008 12:49 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Processes after CRTSRVPGM

I am using binder language with *PRV and *CURRENT levels and creating a

new signature every time. It's not ideal but it works. I'll look into
using UPDSRVPGM, when it's applicable, instead of CRTSRVPGM every time.
Thanks

Are you using binder language? Are you creating a new signature
every

time you add a procedure to a service program? What about when you
change a procedure's logic (without changing the parameter list)?

--
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.