"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 04/11/2018
03:14:01 PM:
'T is been awhile.
But you cannot have 2 prompt controls on a PARM, IIRC. Can you show the
PARM on which those PMTCTL should work? Or have you forgiiten to fill
that key word?
So, if the compile works, then the second one will be ignored.
Compiles with warnings, only (creates the object). But not even a
warning about the second PMTCTL referencing the same parameter name. Is
such a restriction documented somewhere?
Keep in mind, though... It does work as long as there is a value
in the referenced parameter (the first one). It does alternately remove
the second parameter or remove the third parameter like I would expect
when I change the value of the first parameter. The only thing I didn't
expect is that it would show both the second and third parameters when the
first parameter is empty.
Now, there are actually more parameters than this in my command.
But, I have stripped it down to just the three parms I am talking about.
PARM KWD(MSGID) TYPE(*NAME) LEN(7) MIN(1) +
SPCVAL((*LAST)) PROMPT('Message identifier')
NOBODY: PMTCTL CTL(MSGID) COND((*NE '*LAST') (*EQ ' ')) +
NBRTRUE(*GT 0) LGLREL(*OR)
PARM KWD(BODY) TYPE(*CHAR) LEN(10) RSTD(*YES) +
DFT(*HLPTEXT) SPCVAL((*FULLMSG) (*MSGTEXT) +
(*HLPTEXT)) PMTCTL(NOBODY) +
PROMPT('Email body')
LASTHDR: PMTCTL CTL(MSGID) COND((*EQ '*LAST')) NBRTRUE(*EQ 1)
PARM KWD(HDRMSGID) TYPE(*NAME) LEN(7) DFT(*DFT) +
SPCVAL((*DFT ' ')) MIN(0) PMTCTL(LASTHDR) +
PROMPT('Header message identifier')
Sincerely,
Dave Clark
midrange.com
