|
Scott,
On top of my head: should the SPCVAL keyword not be on the PARM code?
Regards,
Carel Teijgeler.
*********** REPLY SEPARATOR ***********
On 9-5-03 at 10:58 Scott Klement wrote:
>I'm trying to write a command that has a qualified job as one of it's
>parameters. My code looks like this:
>
> PARM KWD(JOB) TYPE(JOB1) PROMPT('Job Name')
>
> JOB1: QUAL TYPE(*NAME) SPCVAL((*))
> QUAL TYPE(*NAME) PROMPT('User')
> QUAL TYPE(*CHAR) LEN(6) RANGE(000000 999999) +
> PROMPT('Number')
>
>However, this won't compile. I get this message:
>
>* CPD0244 30 '* ' for SNGVAL or SPCVAL parameter not valid for first
>QUAL statement in group.
>
>If I change SPCVAL((*)) to SPCVAL((*CURRENT)) it works, but that's not what I
>want :( I want this to work just like the IBM >commands, for the sake of
>consistency.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.