RE: Service Programs

["Bartell, Aaron L. (TC)" <ALBartell@xxxxxxxxxxxxxx>]

I am pretty sure that the signature is not based on the name of the field,
but rather the number of parms, their order, their data type, and how they
are passed (*nopass, value, *omit, etc).

Correct me if I am wrong.

Aaron Bartell


-----Original Message-----
From: Barbara Morris [mailto:bmorris@ca.ibm.com]
Sent: Friday, April 19, 2002 11:49 AM
To: rpg400-l@midrange.com
Subject: Re: Service Programs


dmosley@dancik.com wrote:
>
> I found this defintion on the web.
> "When creating a service program, the system calculates a 'signature' for
> your service program. This works in a similar manner to the way 'record
> format level checks' work on a database file -- if something in the
service
> program changes, they prevent you from possibly accessing it incorrectly."
>
> To be more specific, if something changes in any of the procedures
> parameters, this would cause a Signature Violation.
>

David, it would be nice if changing the parameters caused a signature
violation, but in fact the signature isn't affected by the parameters.
I don't know exactly what the signature encodes, but I think it's just
the number and maybe the names of the exports.


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