Re: Question about command parameters (PARM statement)

[PaulMmn <PaulMmn@xxxxxxxxxxxxx>]

If you can't restrict parms in the Command, there's always the 
Validity Checking Program, which lets you examine the values of the 
parms, adjust them as needed, then let the command procede.

There's a message to reply with to reject the command entirely.

The Validity Checking Program isn't difficult-- you write a program 
that has the same parm list as the CPP, then poke at the parms as 
needed.

--Paul E Musselman

.



At 5:32 PM -0700 4/27/21, James H. H. Lampert wrote:
> In defining a command's parameters, I see a number of ways to define 
> what values are specifically *allowed* for a parameter.
>
> Is there a way to define several (in this case, ten) distinct values 
> *prohibited* for a parameter?
>
> In this case, the parameter is a value to be passed to a SBMJOB's 
> "USER" parameter, and so it should accept either a valid SNAME or 
> "*CURRENT," but reject the user profiles that are prohibited for 
> that parameter of SBMJOB.
>
> And if I can reject it at the command level, rather than the CPP 
> level, then a wrong value will of course keep it from compiling in a 
> CL program, and make it fail a syntax check in SEU.
>
> --
> JHHL