RE: Best way of using Service programs.

I have had to do stuff like this for when one prototype needed to reference
a data structure from another copy book for one of its parms.  Working good
so far :-)

Aaron Bartell 

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Lapeyre, Francis
Sent: Friday, February 17, 2006 11:38 AM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: Best way of using Service programs.

How about doing this in your prototypes:

      **+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+       
      *===  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


This way, you can group the prototypes into different members if you want.
If all your prototypes are defined this way, you can't have any duplicates.

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



-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Fisher, Don
Sent: Friday, February 17, 2006 10:52 AM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: Best way of using Service programs.

Name clashes are more difficult to manage when your prototypes are scattered
among many different source members.  That's why we have all our prototypes
in one source member.

As for initial design and development definition, well, those steps here
tend to be one person shows.  When we were a big shop, we have a quality
assurance team to handle stuff like that.  We figure our small team size (6)
and the senior level experience (noone with less than ten years on
iSeries/AS400) negates the need.  That's all the more reason to make
resolving issues like procedure name clashes as simple as possible. 

Donald R. Fisher, III
Project Manager
Roomstore Furniture Company
(804) 784-7600 extension 2124
DFisher@xxxxxxxxxxxxx

<clip>
The problem will only be highlighted during first-phase development and not
during subsequent development Such things as

name clashes should be considered during the design phase, and new procedure

names should be included as part of the development definition.
<clip>
--
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.
--
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.