RE: Creating a service program

["Stone, Brad V (TC)" <bvstone@xxxxxxxxxxxxxx>]

I know you can find this out with DSPPGM, and there's probably an API to
retrieve it if you wanted to make a command.  Not sure which one.. :)

> -----Original Message-----
> From: Chris Bipes [mailto:chris.bipes@cross-check.com]
> Sent: Wednesday, August 23, 2000 3:32 PM
> To: 'RPG400-L@midrange.com'
> Subject: RE: Creating a service program
> 
> 
> Now that's great example and explanation.  I wish IBM made it 
> that clear.
> Now how would one find out what program is using what 
> signature so you can
> clean up old *PRV signatures when they are no longer in use.  
> Also how does
> this work when you update an existing module with out 
> changing the parms?
> 
> 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: Stone, Brad V (TC) [mailto:bvstone@taylorcorp.com]
> Sent: Wednesday, August 23, 2000 10:26 AM
> To: 'RPG400-L@midrange.com'
> Subject: RE: Creating a service program
> 
> 
> You can specify more than one signature.  So, when you add 
> the 4th in your
> example, you make a copy of the first export, change it to *PRV for
> signature, and add the 4th to the top list.. like this..
> 
> STRPGMEXP                        
> EXPORT     SYMBOL(Proc1)    
> EXPORT     SYMBOL(Proc2)    
> EXPORT     SYMBOL(Proc3)    
> EXPORT     SYMBOL(Proc4)    
> ENDPGMEXP                        
> STRPGMEXP  PGMLVL(*PRV)          
> EXPORT     SYMBOL(Proc1)    
> EXPORT     SYMBOL(Proc2)    
> EXPORT     SYMBOL(Proc3)   
> ENDPGMEXP         
> 
> You will now have to sigs for the service program.  The old 
> programs that
> don't need Proc4 don't need to be recompiled because they'll 
> still function
> fine with the old sig. 
> 
> One thing you do have to watch out for is this.
> 
> SRVPGM1 is created and in production.  It's updated, now has 
> 2 sigs, but the
> SRVPGM is only in test environment.  Now, a new program is 
> created that uses
> SRVPGM1 and is compiled, so it will grab the current sig from SRVPGM1.
> 
> If you move NEWPGM into production before the new copy of 
> SRVPGM1, you will
> get a signature error.  Just a slight gotcha... :)  When programs are
> compiled using a service program, they always grab the 
> *CURRENT signature.
> 
> Rare case, but something to be weary of.
> 
> Brad               
> +---
> | 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
+---