RE: Command Parameter Question

Well I wouldn't like to presume how IBM do it, but I don't know any way of
doing this on the command itself. Being a product manager for a product
which front ends every function with a command (over 1000 of them and
rising!)  I have done most things that are possible on commands, but have
never seen that. It would be possible to translate a parameter prior to the
CPP, if you did the processing in a prompt override program, or in a
validity checker, though with the latter, IBM do state that it is not
guaranteed that any values changed in a CVC will be passed to the CPP
correctly. I guess we can also add to the list the new command exit
programs available. I would say though that doing it in the CPP would be
the most straightforward way.

If you do find a means of doing this some other way, I would be very
interested in the solution!

Mike



                      "Smith, Nelson"
                      <NSmith@lincare.co        To:       
"'midrange-l@midrange.com'" <midrange-l@midrange.com>
                      m>                        cc:
                      Sent by:                  Subject:  RE: Command Parameter 
Question
                      midrange-l-admin@m
                      idrange.com


                      01/07/2002 14:15
                      Please respond to
                      midrange-l






Thanks, Mike, but I guess I asked the question wrong.  I really meant in
the
Command source itself, rather than the CPP.  I'm writting the command, and
I
was trying to get one parm to default to the value of another.  It looked
like, in the CPYF example, IBM was doing what I wanted and I wondered how
they did it.  Are you saying they do it in the Command Processing Program
rather than  in the Command source itself?  I was trying to get the default
value into the parm before it ever got to the CPP.  I'm not sure if that is
possible or not.

> -----Original Message-----
> From:            Mike.Collins@syan.co.uk [SMTP:Mike.Collins@syan.co.uk]
> Sent:            Monday, July 01, 2002 8:45 AM
> To:        midrange-l@midrange.com
> Subject:         Re: Command Parameter Question
>
>
> How we do it is simplicity itself:
>
> IF (&TOMBR = '*FROMMBR') THEN(CHGVAR &TOMBR &FROMMBR)
>
>
>
>
>                       "Smith, Nelson"
>                       <NSmith@lincare.co        To:
> "'midrange-l@midrange.com'" <midrange-l@midrange.com>
>                       m>                        cc:
>                       Sent by:                  Subject:  Command
> Parameter Question
>                       midrange-l-admin@m
>                       idrange.com
>
>
>                       01/07/2002 13:20
>                       Please respond to
>                       midrange-l
>
>
>
>
>
>
> On a CPP, is there a way to get one parameter to default to the value of
> an
> earlier parameter?
>  Seems like I have seen this on some IBM commands, but I can't seem to
> find
> anything on how to do it.  The closest example I could find was the
> *FROMMBR
> option on the TOMBR parameter of the CPYF command.  How is that
> implemented?
> In other words, in the CPP, how is *FROMMBR linked to the value of the
> FROMMBR parameter?
>
>
> Nelson Smith
> nsmith@lincare.com
> ncsmith@tampabay.rr.com
>
>
>
>
**************************************************************************
>
**************************************************************************
> ********************************************************
>
> This message originates from Lincare Holdings Inc. It contains
information
> which maybe confidential or privileged and is intended only for the
> individual or entity named above.
> It is prohibited for anyone else to disclose, copy, distribute or use the
> contents of this message.
> All personal messages express views solely of the sender, which are not
to
> be attributed to Lincare Holdings Inc., and may not be copied or
> distributed without this disclaimer.
> If you received this message in error, please notify us immediately at
> MailAdmin@lincare.com or (800) 284-2006.
>
**************************************************************************
>
**************************************************************************
> ********************************************************
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
>
>
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.