Exactly what changes signature on a Service Program??

[BEllis@xxxxxxxxxxxx]

I wanted to be sure I understand this completely.  Please correct any
assumptions made here.

My assumption is, whether or not Binder Language is used (i.e. Export
(*SRCFILE) -vs- Export(*ALL) ). If I don't change the number of or names of
procedures or the parameters of the procedures, the export signature will
not change.  I should be able to change the logic within any of the
procedures without having to worry about a signature violation.
I understand the concept of *CURRENT and *PRV exports using binder language
to control this.
I'm searching for a concise list of actions that will cause an export
signature for a service program to change.  I can't seem to find this in
any one place.  Any suggestions on where I can find this.  I've searched
the online books @ IBM and went through the list archives.
TIA,
Brian Ellis.

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---