Re: Starting out with sub-procedures

["Booth Martin" <Booth@xxxxxxxxxxxx>]

ok, I am learning.  slowly of course, but at least it is sinking in instead
of bouncing off. 

Here is the next question:

Why does my new procedure that will run QCMDEXC need two parms in?  Why can
t I just send the command and let the new procedure determine the command's
length?
 
  
---------------------------------------------------------
Booth Martin   http://www.MartinVT.com
Booth@xxxxxxxxxxxx
---------------------------------------------------------
 
-------Original Message-------
 
From: RPG programming on the AS400 / iSeries
Date: Thursday, October 23, 2003 4:41:37 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Starting out with sub-procedures
 
-------Original Message-------
 
From: Midrange Systems Technical Discussion
Date: Thursday, October 23, 2003 1:33:48 PM
To: Midrange Systems Technical Discussion
Subject: Re: starting out with sub-procedures
 
A first step maybe...this copy
   *
   * Set up Prototype for QCMDEXC
D Qcmdexc pr Extpgm('QCMDEXC')
D Cmd Like(Qcmd) Options(*Varsize) Const
D Len 15p 5 Const
D Opt 3 Options(*NoPass) Const
   *
D Qcmd s 1024
 
 
In code
 
D/COPY QCPYLESRC,QCMDEXC
 
 
   *
   * CLRPFM SomeFile
C Eval Qcmd = 'CLRPFM FILE('SomeFile')
   *
C CallP(E) Qcmdexc(Qcmd:%Len(%Trim(Qcmd)))
   *
C If %Error
C Endif
 
Hey now that I think about it how does it simpler, clearer, more efficient,
and all of the other good stuff people
talk about.
 
Bill Hopkins