Re: CALLPRC

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 11/27/2018 12:01:01
PM:

On Tue, 27 Nov 2018 at 16:46, <dlclark@xxxxxxxxxxxxxxxx> wrote:

I do this, too, and it works for me. What you have to do in

CL/LE

is to build in the 2-byte binary length of the varying length string

you

are passing to RPG/LE. For example:

DCL VAR(&VARSTR) TYPE(*CHAR) LEN(82)
DCL VAR(&VARLEN) TYPE(*UINT) LEN(2) STG(*DEFINED) DEFVAR(&VARSTR 1)
DCL VAR(&VARDATA) TYPE(*CHAR) LEN(80) STG(*DEFINED) DEFVAR(&VARSTR

3)

Good to know.
I considered that but wasn't really sure if I thought it was a good idea

to

suggest.
.
Do you just set your varlen to the maximum or do you use something like
%Scan to try to determine what the blank trimmed length is?

I created a command called UTRTVSTRLN to retrieve the string
length of any variable content. It turns out that the CMD language makes
this easy -- no separate scan or trim operations required. The CMD
language accepts the parameter content as a string expression. It then
creates a variable-length string (prefix and all) to pass to the CPP. All
the CPP has to do is extract the length from the prefix and return that in
the second parameter. You would call it like this:

/* get the string data length */
UTRTVSTRLN STREXP(&VARDATA) STRLEN(&STRLEN)
CHGVAR VAR(&VARLEN) VALUE(&STRLEN)


CMD PROMPT('Retrieve CL String Length') +
ALLOW(*BPGM *IPGM *BREXX *IREXX *BMOD *IMOD) +
HLPID(*CMD) HLPPNLGRP(UTRTVSTRLN)
PARM KWD(STREXP) TYPE(*CHAR) LEN(4998) MIN(1) +
EXPR(*YES) VARY(*YES *INT2) CHOICE('string +
expression') PROMPT('Expression to evaluate')
PARM KWD(STRLEN) TYPE(*DEC) LEN(4) RTNVAL(*YES) MIN(1) +
PROMPT('Return variable (4,0)')


Sincerely,

Dave Clark