Re: Error while calling QCMDEXC API

[Vernon Hamberg <vhamberg@xxxxxxxxxxx>]

Hi Scott

Blame it on an intense day of whirling through too many odd problems. 
You're right, what I meant to say is that it might be preferable to 
send the length without trailing blanks - it's my preference although 
not absolutely necessary.

Nice catch on the trimr - thanks

See you in Nashville
Vern

At 04:21 PM 3/4/2008, you wrote:

> Hi Vern,
>
> > Srinivas - the length parameter has to be the exact length of the
> > command - you are better off using something like %len(%trim(cmd)) in
> > a prototyped call of QCMDEXC - I think someone gave you what the
> > prototype and the call look like.
>
> Huh?  QCMDEXC doesn't require the length to be the exact length of the
> command... QCMDEXC will happily ignore trailing spaces.  Unless this is
> some new V6R1 thing?!
>
> Also, %len(%trim(cmd)) is wrong.   It should be %len(%trimr(cmd)).  You
> don't want to trim LEADING blanks when calculating the length --
> consider the following example:
>
> command='bbbbWRKSPLF'   (where b=blank)
>
> If you do a %len(%trim(command)) it'll come up with 7, since it'll trim
> the 4 leading blanks.   When you pass this command to QCMDEXC, the API
> will only look at the first 7 characters 'bbbbWRK', and therefore give
> an error on a perfectly valid command.
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.