RE: Processes after CRTSRVPGM

["M. Lazarus" <mlazarus@xxxxxxxx>]

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)?