Re: OVRMSGF and QCMDEXC procedure

["Peter Dow (ML)" <maillist@xxxxxxxxxxxxxxx>]

Because QCMDEXC does not expect a varying length field as a parameter -- 
how do you tell it to skip the length in the 1st two bytes?

Not that it's a whole lot different:

QCMDEXC(CmdStr:%Len(%trim(CmdStr)));


Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx wrote:
> why calculate???  i use varying length fields for creating the command 
> string then on the call i just use:
>
> QCMDEXC(CmdStr:%Len(CmdStr));
>
> Thanks,
> Tommy Holden
>
>
>
> "Peter Dow (ML)" <maillist@xxxxxxxxxxxxxxx> 
> Sent by: rpg400-l-bounces@xxxxxxxxxxxx
> 08/24/2007 01:32 PM
> Please respond to
> RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
>
>
> To
> RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
> cc
>
> Subject
> Re: OVRMSGF and QCMDEXC procedure
>
>
>
>
>
>
> You're way ahead of me then (as usual :-)  ).  For most things the 
> QCMDEXC procedure works just fine and it seemed cleaner to let the 
> procedure calculate the command length, but you're right -- it's not 
> much and it avoids the occasional scoping problems.
>
> Scott Klement wrote:
>   
> > I learned this years ago -- and it's why I never wrap QCMDEXC into a 
> > subprocedure.  Granted, it adds one more line of code to my program, but 
> >     
>
>   
> > one line won't kill me.
> >
> > Peter Dow (ML) wrote:
> >
> >     
> > > In this situation, the override is only in effect while control is in 
> > > the QCMDEXC procedure.  When control returned to the TESTADDR 
> > >       
> procedure, 
>   
> > > the override was gone.  I guess I should of realized this since a 
> > > procedure is another entry on the call stack.
> > >
> > >