RE: command definition

["Elvis Budimlic" <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Thanks all (Charles, Eric, Jon, Don ...), PMTCTL looks like the ticket.  
F9 does still show all parms, but I think that's OK in this case.

Elvis

-----Original Message-----
Subject: RE: command definition

No prompt control doesn't prevent all parameters from being shown when
F9/F10 is hit.

If the original poster really wants that, then he'll probably need to do
this with a HHL program display file.

Charles Wilt


> -----Original Message-----
> Subject: RE: command definition
> 
> 
> Sure you can. I do it all the time. It is accomplished by the PMTCTL
> keyword, although, I don't remember if it prevents showing 
> possible entries
> when the F9 is hit. It may take a while to cut one of my 
> commands up to use
> as an example, but I'll post it tomorrow, if someone else doesn't post
> first.
> 
> John Brandt 
> 
> -----Original Message-----
> Subject: RE: command definition
> 
> 
> I doubt one can accomplish what you want in a command.  
> Perhaps a command
> processing program will help?  I would do this using an HLL 
> and a display
> file just to make it simpler, not to mention far more 
> flexible.  After all,
> can you guarantee the number of categories will always be 
> five or less? ;)
> 
> Good luck. 
> 
> Donald R. Fisher, III
> 
> <clip>
> I'd like to create a command that requires user to enter one 
> of 5 special
> values (categories), i.e.:
> <clip>
> Based on the category selected, additional required 
> parameters would be
> displayed underneath the first parameter, i.e.:
> <clip>
> Ideally, I would not like other parameters to show even if F9 was hit.
> 
> Is it possible to do this in a single command source?  How 
> would you go
> about it?
> <clip>