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>