Re: Command programming

Dan

Yes, the CL will see a 4-byte binary - for a 3-digit number you could use an *INT2 - it also does not need to be unsigned. At V5R4 you can use the *INT data type, I think, in CL.

Of course, even though the decimal point can be entered into a *DEC, it is not passed to the program.

MIN(1) - they all have to be located together - is there more than 1, and is there an parameter in between that does not have min(1)? If you want them in a different order, use an ordinal on the PROMPT parameter of the PARM command.

HTH
Vern

-------------- Original message --------------
From: Dan <dan27649@xxxxxxxxx>

On Tue, Jun 3, 2008 at 12:18 PM, Wilt, Charles wrote:

I've never had an issue using *DEC, as when you specify the length you can
specify the # of decimal
positions but 0 is assumed.

Yeah, I saw that, but it still allows entry of a non-integer. Weird.

Otherwise, use *UNIT4 and specify RANGE(1 999).


Yeah, that's what I've been looking at using. Is the CL CPP going to see a
4-byte binary value when it processes this parameter?

BTW, here's what I'm trying:
PARM KWD(SAVESET#) TYPE(*DEC) LEN(3 0) RANGE(001 999) +
MIN(1) CHOICE('001-999') PROMPT('SaveSet Number')

And a new wrinkle: Even though I've specified MIN(1), I can prompt / run
the command without entering a value for the parameter. I thought MIN(1)
forced a value. Is there another command definition keyword I'm missing?

Thanks again,
Dan
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.