From MPEX help the CMDPARM command will show you the value of the parm: CMDPARM (S) [STR] Returns the value of the parameter indicated by S of the currently-executing command file or UDC. Why use CMDPARM("XYZ") and not "!XYZ"? Because CMDPARM works even when the parameter XYZ contains embedded quotes -- the "!XYZ" syntax would cause a syntax error in this case. Scott Lindholm Sr. Systems Administrator 1 Environmental Way Broomfield, Colorado 80021-3416 (303) 664-3264 [log in to unmask] > -----Original Message----- > From: Simonsen, Larry [SMTP:[log in to unmask]] > Sent: Tuesday, August 01, 2000 2:42 PM > To: [log in to unmask] > Subject: Re: [HP3000-L] Command file wonders > > The problem stems from the fact that x is both a parm and a variable. I > believe the parm overrides the system variable. > > ------------------------------------------------- > Larry Simonsen Phone: 801-489-2450 > Flowserve Corporation Fax: 801-491-1750 > PO Box 2200 http://www.Flowserve.com > Springville, UT 84663 e-mail: [log in to unmask] > ------------------------------------------------- > All opinions expressed herein are my own and reflect, in no way, those of > my > employer. > > -----Original Message----- > From: Dave Knispel [mailto:[log in to unmask]] > Sent: Tuesday, August 01, 2000 2:35 PM > To: [log in to unmask] > Subject: Command file wonders > > To the list, > > Why does this happen? Why doesn't the variable x increment to 4? > > MPEiX:PRINT TEST > parm x > setvar x !x + 1 > echo !x > setvar x !x + 1 > echo !x > > MPEiX:test 2 > 2 > 2 > > MPEiX:showvar x > X = 3 > > > David Knispel > [log in to unmask] > Phone: 513-248-5029 > Fax: 513-248-2672