Hi, I would suggest that you create your own commands with only the parmeters that you need. For example you create a command called USRPRF with only a few parameters - this command uses CL program USRPRF which does a WRKUSRPRF or CHGUSRPRF based on the parameters that your user has entered. Regards, Martin Gilbert. The operating system allows selective prompting on command parameters so you can limit the amount of parameters you want a user to see. Cheeck the following link to this topic. http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/rbam6/secpr.htm Hope this helps. WaltZ400 ======================================================== One simple method can be used when the full command string will be 32 characters or less. Here's an example *CMD definition that replaces one form of the RUNQRY command with QRY:<pre> QRY: CMD PROMPT('RUNQRY QCMDEXC') PARM KWD(CMDSTR) TYPE(*CHAR) LEN(32) + CONSTANT('runqry ??qryfile() ??outtype()') PARM KWD(CMDLEN) TYPE(*DEC) LEN(15 5) CONSTANT(30)</pre> The QRY command would be compiled with QSYS/QCMDEXC as the command-processing program (the CPP). The new command provides definitions for the two parameters needed by QCMDEXC -- the command string and the length of the command string. It's simple because it uses the CONSTANT() attribute of the first parm. It's limited because CONSTANT() values must be 32 characters or less. However, you can make as many of these as you need for different "short-cuts". You can shorten command strings in many cases by leaving keywords off. You can use selective prompting for variable elements as I did for RUNQRY. Quick and easy. But limited. Tom

Hi, I would suggest that you create your own commands with only the parmeters that you need. For example you create a command called USRPRF with only a few parameters - this command uses CL program USRPRF which does a WRKUSRPRF or CHGUSRPRF based on the parameters that your user has entered. Regards, Martin Gilbert. The operating system allows selective prompting on command parameters so you can limit the amount of parameters you want a user to see. Cheeck the following link to this topic. http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/rbam6/secpr.htm Hope this helps. WaltZ400 ======================================================== One simple method can be used when the full command string will be 32 characters or less. Here's an example *CMD definition that replaces one form of the RUNQRY command with QRY:<pre> QRY: CMD PROMPT('RUNQRY QCMDEXC') PARM KWD(CMDSTR) TYPE(*CHAR) LEN(32) + CONSTANT('runqry ??qryfile() ??outtype()') PARM KWD(CMDLEN) TYPE(*DEC) LEN(15 5) CONSTANT(30)</pre> The QRY command would be compiled with QSYS/QCMDEXC as the command-processing program (the CPP). The new command provides definitions for the two parameters needed by QCMDEXC -- the command string and the length of the command string. It's simple because it uses the CONSTANT() attribute of the first parm. It's limited because CONSTANT() values must be 32 characters or less. However, you can make as many of these as you need for different "short-cuts". You can shorten command strings in many cases by leaving keywords off. You can use selective prompting for variable elements as I did for RUNQRY. Quick and easy. But limited. Tom