Re: That Darn Text Issue Pops Up Again...

Mike wrote:

7. Re: That Darn Text Issue Pops Up Again... (Mike)

They do:

CMD PROMPT(CMD)

PARM KWD(FROM) TYPE(*CHAR) LEN(100) MIN(1) PROMPT('From
Address: ')
PARM KWD(TO) TYPE(*CHAR) LEN(32767) MIN(1) PROMPT('To
Address:')

Mike:

For *CHAR 100, I wouldn't usually think twice. But for *CHAR 32767...??

I'm pretty sure I wouldn't have have considered sending that in as a fixed-length parameter.

For this and subsequent parms, I probably would have added the VARY(*YES *INT2) attribute and accepted varying length parameters into the RPG program. Because *CMDs are _usually_ used in CL programs and on command lines, and historical limits have often come into play (in the past), I probably wouldn't start by thinking of creating a 32K parameter much less a series of them.

For much of my work (in the past), I've had to be mindful of limits on command-string lengths. Where 6k was one limit for an entire command-string for example, I had little use for single parameters of 32K. (But that's beside the point. CL has been growing up. It's time for me to search out all current limits on command-string lengths.)

Anyway, consider VARY(*YES *INT2) on your command definition and perhaps [32767A VARYING] fields in your program. I don't think I've done this with a *ENTRY PLIST, but I'd expect it to work with little effort.

Beyond all that, please provide a description of _how_ the command is being executed. Is it constructed as a string and passed to QCMDEXC (or other API)? Sent to a batch *jobq? Compiled into a CL program? ILE or OPM? Typed on a command line?

Tom Liotta

PARM KWD(CC) TYPE(*CHAR) LEN(32767) PROMPT('CC Address:')
PARM KWD(BCC) TYPE(*CHAR) LEN(32767) PROMPT('BCC
Address:')
PARM KWD(SUBJECT) TYPE(*CHAR) LEN(32767) MIN(1)
PROMPT('Subject:')
PARM KWD(MESSAGE) TYPE(*CHAR) LEN(32767) MIN(1)
PROMPT('Message:')

On 6/19/07, Scott Klement wrote:

Do the data types and lengths in the *CMD source match the types and
lengths of the variables in your *ENTRY PLIST? You didn't post the
code for cmd definition or for the variables defined in your *ENTRY
PLIST... But, they do have to match.

Mike wrote:
> I didn't put that code out here, but mentioned it. I have a command
> already on the RPG.
>
> I have a command call an RPG program wrapper for a subprocedure.