File Management - IBM

When control is transferred to another program (TFRCTL command), the overrides
in the call level of the transferring program are not deleted.
You can also explicitly delete overrides on your system by using the Delete
Override (DLTOVR) command. The DLTOVR command can delete overrides that
are scoped to the call level, activation group level, or the job level. To delete
overrides that are scoped to the activation group level, you do not need to specify
a value for the OVRSCOPE parameter because OVRSCOPE(*ACTGRPDFN) is the
default. To delete overrides that are scoped to the job level, you must specify
OVRSCOPE(*JOB) on the DLTOVR command.
To identify an override, use the file name that is specified on the FILE parameter
of the override command. You can delete all overrides at the current level (call
level, activation group level, or job level) by specifying value *ALL for the FILE
parameter.
See the following topics for additional information on deleting overrides:
v “Deleting overrides: scenario 1”
v “Deleting overrides: scenario 2”
Deleting overrides: scenario 1
In the following example, assume that all the commands are entered at the same
call level:
Override 1 OVRDBF FILE(DBA) +
TOFILE(DBB)
Override 2 OVRPRTF FILE(PRTC) +
COPIES(2)
Override 3 OVRDKTF FILE(DKT) +
EXCHTYPE(*BASIC)
Delete Override 1 DLTOVR FILE(DBA)
Delete Override 2 DLTOVR FILE(*ALL)
Delete override 1 causes override 1 to be deleted. Delete override 2 causes the
remaining overrides (overrides 2 and 3) to be deleted.
Deleting overrides: scenario 2
In the following example, assume that commands 1, 2, and 14 are entered
interactively, at call level 1:
Chapter 3. Using overrides 55