×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Only the names of exported procedures matter on signatures. Do a RTVBNDSRC on your service program and you will see that it is just a list of procedure names. As long as they don't change, neither will the signature. Parameters have nothing to do with it.
Brian May
IBM i Modernization Specialist
Profound Logic Software, Inc.
http://www.profoundlogic.com
937-439-7925 Phone
877-224-7768 Toll Free
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James Lampert
Sent: Thursday, April 19, 2012 11:43 AM
To: Midrange Systems Technical Discussion
Subject: Stupdid NOOB Question about service program signatures
Just out of morbid curiosity:
On service programs created with EXPORT(*ALL),
I know that adding or removing an exposed function/procedure call changes the signature.
And I just added optional parameters to one exposed call, and found (to my surprise) that the signature didn't change.
Does anybody know what, other than adding or removing an exposed call, can change the signature? And what is guaranteed NOT to do so?
--
JHHL
--
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.
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.1913 / Virus Database: 2411/4946 - Release Date: 04/19/12
midrange.com
