RE: /copy prototype

["Wilt, Charles" <CWilt@xxxxxxxxxxxx>]

Jen,

Take a look at the conditional compiler directives:
/IF DEFINED
/IF NOT DEFINED

/DEFINE

/ENDIF

The way I'd do it is surround the CalcRow prototype in both copy members
like so:

      /IF NOT DEFINED(CALCROW_INCD)
      /DEFINE CALCROW_INCD
     d CalcRow        pr


      /ENDIF

HTH,

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
  

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jen Raihala
> Sent: Thursday, April 06, 2006 8:42 AM
> To: Midrange Systems Technical Discussion
> Subject: /copy prototype
> 
> First a very brief description of the issue:
>   
>   Last year, the company decided to move to a one-size for 
> all #xx0000pr  /copy standard. For the most part, after 
> resolving the majprity of  glitches, it has worked pretty well.
>   
>   A month ago, (partly my fault because I liked the CalcRow 
> for subfile  error marking), the programmer that developed 
> it, at the request of  another programmer who read some of my 
> code and liked the CalcRow too,  moved a copy of the 
> procedure to the new general copy member (and left  it in the 
> original one since it is in use in a vast majority of their  
> programs). 
>   
>   However, my issue now is in the more generally used one, 
> there is a  calendar lookup that I need for a program, and I 
> was instructed  yesterday to use the older /copy member... 
> which now duplicates the  CalcRow when I /copy them both.
>   
>   So, is there a way to /copy just the calendar lookup 
> procedure into my program without /copy the whole protoype?
>   
>   Thank you in advance,
>   JenR
>   
>   
> -- 
> 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/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.
> 
>