Re: Command Parameter Question.

On 21-Feb-2018 09:46 -0700, Kevin wrote:

If I have a command parameter type of *X - how should I define that in
the cl processing program.

At the moment it is *CHAR 100 - but I'm getting pointer errors when I
try and access that parameter in the cl program.

Any thoughts...

This is not my software - I do have all the source however.

Here is the code in question..

PARM KWD(MSGRPY) TYPE(*X) RTNVAL(*YES) VARY(*YES) +
PASSATR(*YES) CHOICE('Variable name') PROMPT('CL +
var for message reply' 7)

What is the failing invocation? A pointer error [i.e. a msg MCH3601] generally would indicate that the command invocation had not specified a "Variable name" on the [presumed-to-be-optional] MSGRPY Parameter (PARM) that was coded in the Command Source [as shown in the example snippet of CMD source above].

For example, if the command name were RTVMSGRPY, and another [likely-to-be-required] parameter named MSGX() specified whence the "message reply" would be retrieved, then the first invocation shown below would fail with a "pointer not set" error whereas the second invocation shown below would be able to address the storage:

RTVMSGRPY MSGX(MYMSG)

RTVMSGRPY MSGX(MYMSG) MSGRPY(&RETURNSTG)