RE: service program question

["Smith, Mike" <Mike_Smith@xxxxxxxxxxxxxxxx>]

thanks for the reply
I thought there would be backward compatibility problems, but wasn't
positive.  

i think i will take njals approach. 
The only reason i was doing it was that it just seemed to get cluttered up
with the globals variables in there.  

so much to learn

mike

-----Original Message-----
From: Scott Klement [mailto:klemscot@klements.com]
Sent: Thursday, July 19, 2001 5:14 PM
To: RPG400-L@midrange.com
Subject: Re: service program question



The problem with splitting one service program into two service programs
is backward compatibility.   When you compiled the *PGM's that call
routines from your *SRVPGM, they located the service program and decided
which procedures to call.

If you make a totally diffeent service program, they will no longer see
those procedures, and won't work -- unless, of course, you re-bind them.

So, I see two solutions:

1) Follow Njal's excellent suggestion, and split your service program
    up into different modules.  This way, it remains only one serivce
    program, but your global variables can be scoped differently.

2) If for some reason you NEED it to be two separate *SRVPGM objects,
   change the existing procedures so that they call the procedures in
   the NEW *SRVPGM.  This allows the existing *PGM's the ability to
   still call your original *SRVPGM, and allows you to have the 
   same procedures with the same signatures.

Or... at least, that's what pops into my head :)



On Thu, 19 Jul 2001, 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.  
> 
> 
> Mike
> 
> +---
> | 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
> +---
> 

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