RE: /copy prototype

["Lapeyre, Francis" <FLAPEYRE@xxxxxxxx>]

What we do is put in conditional defines:

      **+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+       
      *===  Procedure:   TimeStamp                                          
      *===  Description: Returns a the current time stamp with microseconds 
      *===             : yyyy-Mm-dd-hh.MM.ss.mmmmmm                         
      *===           ex: 2004-06-24-07.40.29.948000                         
      **+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+       
      /IF NOT DEFINED (Arvtime_Timestamp_DONT_COPY)                         
      /DEFINE Arvtime_Timestamp_DONT_COPY                                   
     DArvtime_...                                                           
     D Timestamp       PR              Z                                    
      /ENDIF                                                                

You can see that the conditional define is always called
{procedure_name}_DONT_COPY. In our case, Arvtime is also the name of the
copy member for a service program (Arvtime), and Arvtime_Timestamp is the
function within the service program Arvtime. If that standard is adhered to,
you'll never have duplicates. This allows us to use any function in any
program or service program and not worry about duplicates.

Add those conditional defines to every prototype in every copy member. 

It's a bad idea to clone copy members - somebody could change one, but
forget about the other one.


Francis Lapeyre
IS Dept. Programmer/Analyst
Stewart Enterprises, Inc.
E-mail: flapeyre@xxxxxxxx 




-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jen Raihala
Sent: Thursday, April 6, 2006 7: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.