Re: CMD difficulty - V5R2

[Martin Rowe <dbg400.net@xxxxxxxxx>]

On 17/02/06, Rich Duzenbury <rduz-midrange@xxxxxxxxxxxxxxxxxxx> wrote:
> Hi all,
>
> I need to write a command that can prompt for one or more command
> strings, which I thought would be easily possible.
>
> I first tried
>
> parm kwd(commands) type(*cmd) max(10)
> Error CPD6229, if type *CMD specified, MAX(1) required.
>
> Ummm, ok.
>
> How about elem?
>
> ELEM type(*cmd)
> Error CPD0133, *CMD not allowed for type.
>
> This seems like an odd restriction.  Surely there is some way to allow
> the user to prompt for a list of commands.  Could someone enlighten me,
> please?

Hi Rich

>From my recollection, not only can you only have a single *CMD field,
rather than a list, but you can only have one *CMD type parm in a
command definition. At least that appears to be the case at V5R2.
Possibly you could do something with a long *CHAR field with an
associated CHOICEPGM parm, to get your string prompted via QCMDCHK or
QCAPCMD.

A useful tool to see how commands are contructed is Dave McKenzie's
RTVCMDSRC. It's freeware/public domain and available from
http://www.iseriesnetwork.com/code/sharewarefiles/rtvcmd.zip

Regards, Martin
--
martin@xxxxxxxxxx  AIM/Gaim: DBG400dotNet  http://www.dbg400.net   /"\
DBG/400 - AS/400 & iSeries Open Source/Free Software utilities     \ /
Debian GNU/Linux | ASCII Ribbon Campaign against HTML mail & news   X
TWiki - an Enterprise Collaboration Platform - http://twiki.org/   / \