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