Re: Command Help

Our MAILTOOL command does this.. when they choose to send email using
*MAILTOOL instead of *IBMSMTP... here's a small snippet:

...

PARM KWD(SENDWITH) TYPE(*CHAR) LEN(10) RSTD(*YES) +
DFT(*IBMSMTP) VALUES(*MAILTOOL *IBMSMTP) +
PROMPT('Send With Server Type')
PARM KWD(MAILRTR) TYPE(*CHAR) LEN(64) DFT(*NONE) +
PMTCTL(USEMLT) PROMPT('Mail Router')
PARM KWD(USERTR) TYPE(*CHAR) LEN(5) RSTD(*YES) +
DFT(*NO) VALUES(*NO *YES *ONLY) +
PMTCTL(USEMLT) PROMPT('Use Mail Router')
....

USEMLT: PMTCTL CTL(SENDWITH) COND((*EQ '*MAILTOOL'))

So, what happens is, when SENDWITH is equal to *MAILTOOL any command
parameter with the PMTCTL of USEMLT is shown.

F9 will also show ALL parameters, conditioned or not.


On Wed, Apr 22, 2015 at 10:19 AM, CRPence <crpbottle@xxxxxxxxx> wrote:

On 21-Apr-2015 17:03 -0500, Jon Paris wrote:

<<SNIP>> Here’s what I want.

Outfile required . . . . . . *YES *YES, *NO
Output file . . . . . . . . *GEN______ Name, *GEN
Library . . . . . . . . . __________ Name
Member . . . . . . . . . . __________ Name, *FILE, *DATE
Replace physical file . . *NO_ *YES, *NO

Only if *YES is specified to the first parm do I want the others to
appear.

The RUNQRY command has something near identical [with the file specified
as a qualified name rather than the Library as another element] with the
Report Output Type (OUTPUT) parameter in combination with an Output File
(OUTFILE) parameter serving as the conditioning on the special-value
*OUTFILE being coded:

In *CLKWD presentation view [just the conditioned and control]:

Report output type . . . . . . . OUTTYPE > *OUTFILE
Output file: OUTFILE
File . . . . . . . . . . . . . *RUNOPT___
Library . . . . . . . . . . *RUNOPT___
Member . . . . . . . . . . . . *FIRST____
Option . . . . . . . . . . . . *RUNOPT_

In /Choices/ presentation view [just the conditioned and control]:

Report output type . . > *OUTFILE *RUNOPT, *DISPLAY...
Output file:
File . . . . . . . . *RUNOPT___ Name, *RUNOPT
Library . . . . . *RUNOPT___ Name, *RUNOPT, *CURLIB
Member . . . . . . . *FIRST____ Name, *RUNOPT, *FIRST...
Option . . . . . . . *RUNOPT_ *RUNOPT, *NEWFILE...


Buck included the output from a RtvCmd or RtvCmdSrc here:
<http://archive.midrange.com/midrange-l/200201/msg00057.html>

I can condition them via a defined Type but then it does not
appear to allow me to specify default values for the individual
components such as Member and Replace.

Not sure what is being implied there. But if the issue is using
representative types, for example an integer one vs integer zero to define
*NO and *YES, then the aforementioned RUNQRY example does that and assigns
defaults to the elements.

Only if I specify them as individual parms can I get the defaults
accepted.

The Default Value (DFT) is specified in the ELEM and QUAL specifications
that are provided as the individual components of the complex TYPE [i.e.
TYPE(name_vs_SpcVal)] that was specified for the PARM.

Is what I want possible? Seems like it should be.

In a related question - how do I control which parms appear in the
initial prompted screen. It seems that the minute I have a parm
related to a PMTCTL it does not appear unless I press F9 and then I
get everything.

The effect of F9=All Parameters, by descriptive text alone, is
suggestive of that effect :-) Use the F10=Additional Parameters instead,
to ask to have presented additionally, just those parms that were not yet
presented due to a Prompt Control specification of *PMTRQS.

The Prompt Control (PMTCTL) specification on a PARM, by naming a label
rather than the special-value *PMTRQS redirects the decision about whether
the parameter is displayed according to the logic in the Prompt Control
Definition (PMTCTL) defined at that label. That logic specifies another
parameter keyword [Controlling Keyword (CTL)] from which the data is found
to predicate the presentation [Controlling Conditions (COND)]; i.e. defines
what must be specified before the controlled parameter will be presented,
which in the given example, apparently the test would be if what represents
the value *YES was specified on the OUTFILRQD [the Outfile Required]
parameter

Can anyone provide a little WD40 to loosen up my aged brain?

Perhaps something of the above helps [now, or someone in the future
referencing the archives].

--
Regards, Chuck

--
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.