Re: create command - make required

The MIN(1) requires you to enter a value. You could also include a default value in the command, which, I'm assuming, would not require you to manually enter a value.

You can also create a parameter that does not show up when you prompt the command, but is 'hard-wired' to include a fixed value:
PARM KWD(SECRET) TYPE("*CHAR) LEN(10) CONSTANT('anyvalue ')

The Command Processing Program can use the SECRET parameter to do different things. We've customized some commands by location so that the proper location code is passed when the command is used.

--Paul E Musselman

.



At 2:56 PM -0500 11/23/20, Jay Vaughn wrote:

if I create a command with only this in it...

PARM KWD(TEST) TYPE(*PNAME) LEN(10) EXPR(*YES)
MIN(1) PROMPT('TEST')

It forces me to enter a value when I run the command...

However if I put that into another command with other parms in it, it is
not forcing the required input.

What am I missing?
Can other parms actually cause other parms to not allow an input to be
required?

tia

Jay
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com