RE: Creating Commands

Hi Shannon,

You're on the right track.  Instead of *PMTRQS as the value for the PMTCTL
parm, make up a name.  Use that name as the label for a PMTCTL line or
lines, which contain the conditions under which you want the parm to be
displayed.  Here's an excerpt:

              PARM       KWD(ONERROR) TYPE(*CHAR) LEN(10) RSTD(*YES) +
                           DFT(*SNDMSG) VALUES(*SNDMSG *RETRY +
                           *RUNPGM) PROMPT('On error action')
              PARM       KWD(MSGTYPE) TYPE(*CHAR) LEN(10) RSTD(*YES) +
                           DFT(*DIAG) VALUES(*DIAG *ESCAPE) +
                           PMTCTL(SNDMSG) PROMPT('Message type to +
                           send if error')
              PARM       KWD(PGM) TYPE(Q2) PMTCTL(RUNPGM) +
                           PROMPT('Program to run if error')
              PARM       KWD(NBRRETRIES) TYPE(*DEC) LEN(5 0) DFT(3) +
                           SPCVAL((*NOMAX 99999)) PMTCTL(RETRY) +
                           PROMPT('Number of times to retry')

  RETRY:      PMTCTL     CTL(ONERROR) COND((*EQ '*RETRY'))
  RUNPGM:     PMTCTL     CTL(ONERROR) COND((*EQ '*RUNPGM'))
  SNDMSG:     PMTCTL     CTL(ONERROR) COND((*EQ '*SNDMSG'))

Depending upon what the user enters for  the ONERROR parm, one of the 3
following parms will be displayed.

hth,
Peter Dow
Dow Software Services, Inc.
www.dowsoftware.com
909 793-9050 voice
909 793-4480 fax




> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Shannon ODonnell
> Sent: Saturday, December 17, 2005 11:33 AM
> To: 'Midrange Systems Technical Discussion'
> Subject: RE: Creating Commands
>
>
> Ah... amazing how once you ask someone a question the answer pops out at
> you.
>
> I just discovered the PMTCTL(*PMTRQS) parameter.  Which hides the extra
> parms until the users presses the F10 function key. Woo-hoo!
>
> I'm still trying to figure out how to trigger a set of parms showing up
> based on a certain value entered in another parm.  If anyone has
> an idea on
> that one, I'd appreciate suggestions.
>
> Or, I guess if you wait long enough to answer, I'll probably figure it out
> myself in the meantime. :-)
>

--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.1/206 - Release Date: 12/16/2005