RE: service program signatures

That's why there's binder language. Check it out - specifying a binder
language source member is the default for the EXPORT parameter on the
CRTSRVPGM command. The other value is *ALL, which means export all
symbols. If you export all symbols, and the symbols change (by adding a
new export), then the signature changes.

Of course, this only refers to exports (procedure names and data items
names), not to changes within the procedure code itself. 

> -------- Original Message --------
> Subject: service program signatures
> From: brian <bsl04@xxxxxxxx>
> Date: Wed, July 13, 2005 3:21 pm
> To: midrange-l@xxxxxxxxxxxx
> 
> I'm confused about service program signatures. It seems as though IBM is
> telling me that if I add an export to my service program, the signature
> of the service program will change, and I'll have to recompile all the
> programs that use the service program, which seems pretty unreasonable.
> 
> I'd rather have things so that it isn't necessary to recompile a program
> that uses the service program unless there is an API change, not just
> because I add a new export or something.
> 
> Thanks for advice.
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.