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

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:')
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 <rpg400-l@xxxxxxxxxxxxxxxx> 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.
>
>
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.