RE: Creating a service program

[Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>]

Awh! Don't create with the 4th proc but update the service program added the
4th proc.  Try the UPDSRVPGM command.  This does not change the signatures
for the first 3 procs.

Christopher K. Bipes    mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst  mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.        http://www.cross-check.com
6119 State Farm Drive   Phone: 707 586-0551 x 1102
Rohnert Park CA  94928  Fax: 707 586-1884

If consistency is the hobgoblin of little minds, only geniuses work here.
Karen Herbelin - Readers Digest 3/2000

-----Original Message-----
From: Gwecnal@aol.com [mailto:Gwecnal@aol.com]
Sent: Wednesday, August 23, 2000 9:56 AM
To: rpg400-l@midrange.com
Subject: Re: Creating a service program


OK - From the thread on this topic I understand that when you add procedures

to a service program and export(*all) the signature changes and calling 
programs will do the equivalent of a level check.  If you list the
procedures 
separately in a bind source and use this on the create service program, this

problem goes away. This is the part I don't understand.  Say I have a
service 
program with three procedures (Proc1, Proc2, and Proc3) and I create a 
service program (SrvProg) listing all three in my bind source.  Then I use 
this service program in 50 other programs.  Then I decide that Proc4 would
be 
useful so I add it to my service program source, add it to my bind source 
list and re-create SrvProg with the new bind source.  Doesn't SrvProg now 
have a new signature?  Won't my other 50 programs blow up?  If not, why not?

TIA, Lance
+---
| 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
+---