Command parameters should be ‘orthogonal’—each parameter should represent the values of only one variable. For example, rather than have four values for a parameter OUTPUT (values: *PRT, *DSP *PRTDTL, DSPDTL), you should have two separate parameters, OUTPUT (values: *, *LIST) and DETAIL (values: *PRT, *DSP). This allows future values to be added.
Keep the number of parameters to a minimum.
Do not place parameters specifying work management attributes (for instance job priority, switch settings, output queue) on commands, unless the command is specifically concerned with the initialization of a job or jobs; for example, a special version of the SBMJOB command. This is because it is generally preferable to control work management values through the job. Where it is useful to have an override on a particular command, you should make the default value to be that of the job (*JOB).
|
Copyright © 2014 CA.
All rights reserved.
|
|