|
You can have some control over the position of PARMS with the second
element on the PROMPT key word.
But as those are missing, I wonder how this could compile. Having
required PARMS (max(1)) after optional ones always throws compile errors
at me.
Op 30-7-2021 om 21:52 schreef Charles Wilt:
You can't have optional parms appear before required ones...Y or
Change MIN(0) to MIN(1) for these
PARM KWD(DATE) TYPE(*CHAR) LEN(8) MIN(0) +
DFT(*CURRENT) PROMPT('Date to process +
(YYYYMMDD)')
PARM KWD(ITEM) TYPE(*DEC) LEN(6 0) MIN(0) +
DFT(0) PROMPT('Item to process')
PARM KWD(STORE) TYPE(*DEC) LEN(3 0) MIN(0) +
DFT(0) PROMPT('Store to process')
PARM KWD(VENDOR) TYPE(*DEC) LEN(5 0) MIN(0) +
DFT(0) PROMPT('Vendor to process')
HTH,
Charles
On Fri, Jul 30, 2021 at 12:41 PM Robert Rogerson <rogersonra@xxxxxxxxx>
wrote:
Hi all, this has me stumped. I have this source for a command
CMD PROMPT('SBT BIMBO Refresh ')
PARM KWD(DATE) TYPE(*CHAR) LEN(8) MIN(0) +
DFT(*CURRENT) PROMPT('Date to process +
(YYYYMMDD)')
PARM KWD(ITEM) TYPE(*DEC) LEN(6 0) MIN(0) +
DFT(0) PROMPT('Item to process')
PARM KWD(STORE) TYPE(*DEC) LEN(3 0) MIN(0) +
DFT(0) PROMPT('Store to process')
PARM KWD(VENDOR) TYPE(*DEC) LEN(5 0) MIN(0) +
DFT(0) PROMPT('Vendor to process')
PARM KWD(MODE) TYPE(*CHAR) LEN(1) MIN(1) +
VALUES('Y' 'N') RSTD(*YES) +
PROMPT('Update Production (Y/N)')
PARM KWD(SENDEDI) TYPE(*CHAR) LEN(1) MIN(1) +
VALUES(Y N) RSTD(*YES) +
PROMPT('Send EDI Sales (Y/N)')
PARM KWD(CLSBSLP) TYPE(*CHAR) LEN(1) MIN(1) +
VALUES(Y N) RSTD(*YES) +
PROMPT('Clear SBTSALESP')
If I call the command from the command line
SB0125CMD DATE(20210708) ITEM(883082)
the cpp is called.
I thought the only valid values for the last three parameters would be
listN and since MIN(1) is specified it could only be Y or N.
But the CPP is being called and the last three parameters are blank.
How do I restrict the last three parms to only Y or N and not blank?
Thanks,
Rob
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
relatedTo post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
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.