RE: service program question

["Njål Fisketjøn" <n.f@xxxxxxx>]

Smith, Mike wrote:

> 
> What is the process for removing a procedure from a service program and
> making it into its own service program.  
> 
> i want to be careful because this is in production and i don't 
> want to cause
> any problems.  
> 
> i have a procedure within my service program that has global variables.
> iwant to remove this into its own service program.  i just think that as i
> add more procedures to this service program, the global variables will
> clutter it up.  
> 
> So i've decided that if my procedure needs globals, then it will 
> be its own
> srv pgm.  

Wouldn't it be sufficient to place the procedure in it's own module?
Unless you're exporting data (variables) I cannot see any benefit of placing
the procedure in it's own service program.

If you want to move to to a different service program, you will have to use
the "version stamping" feature of the binder source to rename the "old
procedure" to something like oldxxxx or whatever so that it doesn't collide
with the "new procedure" when both service programs are used in the same 
program.

example:
STRPGMEXP  PGMLVL(*CURRENT) SIGNATURE('FLI V2')
EXPORT     SYMBOL(OLDGetWayP)
EXPORT     SYMBOL(OLDGetLegs)
...

STRPGMEXP  PGMLVL(*PRV) SIGNATURE('FLI V1')
EXPORT     SYMBOL(FliGetWayP)
EXPORT     SYMBOL(FliGetLegs)
...


+---
| 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
+---