RE: CrtBndRpg vs. CrtPgm

Sounds like there's a module remaining from a previous CRTRPGMOD in a "real"
library that's causing the confusion.  The one in QTEMP comes from CRTBNDRPG
and is probably the one you really want to bind.  

> -----Original Message-----
> From: Smith, Nelson [mailto:NSmith@xxxxxxxxxxx]
> Sent: Friday, May 09, 2003 2:01 PM
> To: midrange-l@xxxxxxxxxxxx
> Subject: CrtBndRpg vs. CrtPgm
> 
> 
> When compiling an RPGLE program using CrtBndRPG, and the 
> program already
> exists somewhere else in the library list, I get the following error:
> 
> Message . . . . :   Definition supplied multiple times for symbol
> 
>   'STS_PHYS_D'.
> 
> Cause . . . . . :   Definition STS_PHYS_D was found to be 
> exported from both
> 
>   *MODULE object STS_PHYS_D in library QTEMP and *MODULE 
> object STS_PHYS_D
> in      
>   library *LIBL. Recovery  . . . :   Try the Create Program 
> (CRTPGM) or
> Create     
>   Service Program (CRTSRVPGM) command again, supplying only 
> one of these
> 
>   objects, or try the CRTPGM or CRTSRVPGM command again, 
> specifying one or
> 
>   both of OPTION(*DUPVAR) and OPTION(*DUPPROC).
> 
> 
>  'STS_PHYS_D' is the name of the module.  The same module 
> compiles just fine
> with CrtPgm, using the Option keywords mentioned in the error 
> message.  I'm
> on V4R5.
>                                                                     
> The CrtBndRpg command does not seem to accept Option( 
> *DUPPROC *DUPVAR )
> like CrtPgm does.  Yet, it does allow procedures from service 
> programs and
> other modules to be used through the BndDir parameter.  What 
> can be done
> about duplicate names if you can't use these options?   Is 
> this a situation
> where we would be forced to use CrtPgm instead, or is there some other
> workaround?  
> 
> Nelson Smith
> nsmith@xxxxxxxxxxx
> ncsmith@xxxxxxxxxxxxxxx
> 
> 
> 
> **************************************************************
> **************************************************************
> **************************************************************
> ******************
> This message originates from Lincare Holdings Inc. It 
> contains information which may be confidential or privileged 
> and is intended only for the individual or entity named above.
> It is prohibited for anyone else to disclose, copy, 
> distribute or use the contents of this message. 
> All personal messages express views solely of the sender, 
> which are not to be attributed to Lincare Holdings Inc., and 
> may not be copied or distributed without this disclaimer. 
> If you received this message in error, please notify us 
> immediately at MailAdmin@xxxxxxxxxxx or (800) 284-2006.
> **************************************************************
> **************************************************************
> **************************************************************
> ******************
> 
> _______________________________________________
> This is the Midrange Systems Technical Discussion 
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>