1. MIN(1) will force an error if nothing is entered
<i>2. I want to check at a *cmd level , not at the *pgm level behind the command if the entered parameter contains a string. </i>
That, unfortunately, doesn’t make a lot of sense. If the parm type is *CHAR and the parm requires MIN(1) as noted above, then it is automatically a “string” no matter what is typed as long as it isn’t left blank.
<i>(i.e. if the parameter is a mail, and it is , i want to be sure that it is like %@myworkspace.com or other )</i>
But if the request is about how to enforce some <i>arbitrary pattern</i> on the characters, then there is no way the *CMD can do that. A validity-checker program is required if you need to validate the <i>content</i> of the parm value. And that’s probably a good idea since it would make command definitions much more complex to do it in *CMD language. Why create a new *CMD language construct when it’s already possible in all of the allowed VCP languages?