This topic contains a list of commands that ignore and restrict overrides.
The following commonly used commands ignore overrides entirely:
The system does not apply overrides to any system files that you open as part of an end-of-routing step or end-of-job processing. For example, you cannot specify overrides for the job log file. In some cases, when you need to override something in a system file, you might be able to change it through a command other than an override command. For example, to change the output queue for a job log, the output queue can be changed before sign-off using the OUTQ parameter on the Change Job (CHGJOB) command to specify the name of the output queue for the job. If the printer file for the job log contains the value *JOB for the output queue, the output queue is the one specified for the job. The save and restore commands open the tape file with SECURE(*YES) so that the tape file overrides will be ignored.
The following commands allow overrides for the SRCFILE and SRCMBR parameters only:
(All create program commands. These commands also use overrides to determine which file will be opened by a compiled program. See the File Management topic for more information about applying overrides when compiling a program.)
The following commands allow overrides, but do not allow changing the MBR to *ALL:
The following commands do not allow overrides to be applied to the display files they use. Overrides to the printer files they use should not change the file type or the file name. Various restrictions are placed on changes that might be made to printer files used by these commands, but the system cannot guarantee that all combinations of possible specifications will produce an acceptable report.