+OVERRIDEOUTPUT
Value | Description |
---|---|
NO | (default) BMC AMI Utilities Automation routines cannot override OUTPUT command values. If you specify NO, BMC AMI Utilities do not call the BMC AMI Utilities data set allocation automation routines. |
YES | BMC AMI Utilities Automation routines can override OUTPUT command values. If you specify YES, BMC AMI Utilities call the BMC AMI Utilities data set allocation automation routines, which can change allocation values. |
XDSN | BMC AMI Utilities Automation routines can override OUTPUT command values, except for the data set name. If you specify XDSN, the BMC AMI Utilities call the BMC AMI Utilities data set allocation automation routines, which can change any allocation values except for the data set name. |
Validating OUTPUT data set names
When BMC AMI Utilities run, they resolve symbolic variables in OUTPUT command data set names. If you specify +OVERRIDEOUTPUT(NO) or (XDSN), BMC AMI Utilities validate resolved data set name masks on the OUTPUT command. A resolved data set name is invalid if it:
- Is more than 44 characters long
- Has a node more than eight characters long
When the validation is done, BMC AMI Utilities substitute values that fill the maximum node length to verify if the data set exceeds the maximum allowable length. As an example, a data set name may be created:
BMCRYM.DBNAME01.TSNAME01.P6534.F19025.T105542
This does not correspond to any actual data set name that is used by BMC AMI Utilities. The actual data set names are generated during utility processing.
If BMC AMI Utilities detect an invalid data set name early in the run, it issues an early warning message. You can then stop the process at the beginning of the process by using automation control points to capture the message and trigger an error condition to terminate the job.
If BMC AMI Utilities resolve a data set name resulting in an invalid value during utility processing, the utility:
- Terminates with a return code of 8
- Issues an error message to the SYSERROR file