RE: Question about command parameters (PARM statement)

I think you are looking for the DEP statement.

Create a message id that contains the error text, then trigger the error text using DEP.

I imagine something like this could work:

DEP CTL(&USER *NE *CURRENT) +
PARM((&USER *EQ 'USER1') +
(&USER *EQ 'USER2') +
(&USER *EQ 'USER3')+
) NBRTRUE(*EQ 1) MSGID(XXX1235)

WHERE you create message id XXX1235 to contain your message like 'User id is not allowed'



Like this example from CPYTOSTMF:

DEP CTL(&CVTDTA *EQ 2) PARM((TBL *N *N)) +
NBRTRUE(*EQ 1) MSGID(CPDA086)
DEP CTL(TBL) PARM((&CVTDTA *EQ 2)) NBRTRUE(*EQ +
1) MSGID(CPDA098)



Message ID . . . . . . . . . : CPDA086
Message file . . . . . . . . : QCPFMSG
Library . . . . . . . . . : QSYS

Message . . . . : TBL parameter required with CVTDTA(*TBL).
Cause . . . . . : You specified the CVTDTA(*TBL) parameter without
specifying the TBL parameter.
Recovery . . . : Either change the value on the CVTDTA parameter or specify
the TBL parameter. Then, try the command again.



Message ID . . . . . . . . . : CPDA098
Message file . . . . . . . . : QCPFMSG
Library . . . . . . . . . : QSYS

Message . . . . : TBL parameter can only be specified with CVTDTA(*TBL).
Cause . . . . . : A table name was specified (TBL parameter) and a value of
*TBL was not specified for the CVTDTA parameter.
Recovery . . . : Remove the TBL parameter or change the CVTDTA parameter to
CVTDTA(*TBL). Then try the request again.


https://www.ibm.com/docs/en/i/7.4?topic=ssw_ibm_i_74/cl/dep.htm



Chris Hiebert
Senior Programmer/Analyst
Disclaimer: Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of James H. H. Lampert
Subject: Question about command parameters (PARM statement)

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