Re: Starting out with sub-procedures

[Scott Mildenberger <scottmildenberger@xxxxxxxxx>]

Making the procedure only have one parm and doing the dirty work
inside the procedure is exactly the way to do it.  Whenever
possible hide the dirty stuff inside procedures so the only one
who has to know about it is the person who wrote the procedure. 
My procedure to execute commands (I use the C function system
but could have used QCMDEXC just as easily) even has optional
parameters that work a little like MONMSG in CL - allowing the
call to indicate it worked successfully even if a certain
message id is received.

Scott Mildenberger
--- Booth Martin <Booth@xxxxxxxxxxxx> wrote:
> 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?



__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com