RE: Starting out with sub-procedures

jt, you miss the point of my question. 
 
The whole discussion to this point has been with using QCMDEXC, so we do
know that it would be my intention that the main program would want WRKSPLF
run by QCMDEXC. What I want to do is to learn the easiest, cleanest, and
best way to create a sub-procedure (if that is the right term) and have it
accessible to anyone's main program.
 
The question remains: do I need more than a /COPY statement and the callp
line in the main program(s)? 
 
My primary interest is in avoiding knowing any more about a procedure than
the function and the parm(s). I have a strong desire to NOT know who is
maintaining the code, etc. I don't really even want to look inside the code.
It is none of my business. None whatsoever.
 
---------------------------------------------------------
Booth Martin http://www.MartinVT.com
Booth@xxxxxxxxxxxx
---------------------------------------------------------
 
-------Original Message-------
 
From: RPG programming on the AS400 / iSeries
Date: Sunday, October 26, 2003 4:37:27 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Starting out with sub-procedures
 
... The answer is no, in the case below. Because it's unknown what is inside
the /copy, it's purpose, how that's used, who's maintaining the code, etc...
 
 
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Booth Martin
Sent: Sunday, October 26, 2003 12:08 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Starting out with sub-procedures
 
Please excuse my stepping so slowly. I want to be sure I don't make invalid
assumptions since this is not clear to me yet. May we stay in the fixed
format for this as FREE is just one more possible point of failure for me?
 
Can my main program be correct and complete as far as a sub procedure is
concerned if it has only these two lines?:
 
D/copy protosrc,pDoCmd
....
C callp (e) docmd('WRKSPLF')