|
On Fri, 2006-02-17 at 20:04 +0000, Martin Rowe wrote: > 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. > That's the sort of workaround I was hoping someone might suggest. I haven't done any CHOICEPGM's. I guess I'll do some googling... Thanks.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.