RE: Re-creating Service Programs and Binding Directories

I get the same results with a command line CRTSRVPGM. 

Duane Christen

> -----Original Message-----
> From: Lim Hock-Chai [mailto:Lim.Hock-Chai@xxxxxxxx]
> Sent: Monday, September 13, 2004 9:30 AM
> To: RPG programming on the AS400 / iSeries
> Subject: RE: Re-creating Service Programs and Binding Directories
> 
> 
> I think it might have something to do with the change 
> management package.  Sometime change management package  
> compile/create object in its own library first before moving 
> it to production.  This step is causing the dup proc to happen.
> 
>  
> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Christen, Duane J.
> Sent: Monday, September 13, 2004 9:13 AM
> To: 'RPG programming on the AS400 / iSeries'
> Subject: Re-creating Service Programs and Binding Directories
> 
> 
> I have searched the archive and infocenter and have not come 
> up with a good
> answer.
> 
> Our set-up of Turnover does not allow the use of UPDSRVPGM.
> 
> I am re-creating a service program (CRTSRVPGM), which alredy 
> exists in the
> binding directory. The binder is finding the exports for the existing
> functions in both the modules listed on the CRTSRVPGM command 
> and in the
> existing service program (found in the binding directory), 
> which results in
> "multiple strong definitions". I know I can get around this 
> by using DUPPROC
> and/or DUPVAR (which I have done previously), but this does not seem
> "correct" to me. Why would the binder examine the service 
> program that is
> going to be replaced for exports which will not exist?
> 
> My hope is that we are missing a PTF, my fear is that this is 
> the nature of
> the beast.
> 
> Duane Christen
> 
> 
> 
> --
> This is the RPG programming on the AS400 / iSeries (RPG400-L) 
> mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
> 



NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named.  Any use, copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via e-mail.