File Management - IBM

activation group level. The system does not process this override until it has
processed all overrides with call levels greater than or equal to the call level of
the oldest procedure in activation group 8. In this example, the call level of
the oldest procedure in activation group 8 is 3. Therefore, the system will
process all call level overrides that are issued at call levels greater than or
equal to 3 before processing the activation group override that is issued at call
level 8.
4. The system searches call level 7 for applicable overrides that were scoped to
the call level. Because the override issued at call level 7 is scoped to the call
level, it is processed. The LPI(9) attribute is assigned to file ZZZ.
5. The system searches call level 6 for applicable overrides that were scoped to
the call level. Notice that call level 6 is in activation group 21. There is an
override for file ZZZ; however, it is scoped to the activation group level of
activation group 21. The system ignores this override altogether because it is
scoped to an activation group other than activation group 8.
6. The system searches call level 5 for applicable overrides that were scoped to
the call level. There are no such overrides. (The override issued in call level 5
is for file YYY and does not apply.)
7. The system searches call level 4 for applicable overrides that were scoped to
the call level. Because the override issued at call level 4 is scoped to the call
level, it is processed. The CPI(12) attribute is assigned to file ZZZ.
8. The system searches call level 3 for applicable overrides that were scoped to
the call level. Because the override issued at call level 3 is scoped to the call
level, it is processed. Notice that the file being opened has been changed to
YYY from ZZZ. The DEV(P1) attribute is assigned to file YYY. The LPI(9)
attribute is changed to LPI(6) and is assigned to file YYY.
Call level 3 is the call level of the oldest procedure in activation group 8.
Therefore, any overrides (for file YYY) that were scoped to the activation
group level of activation group 8 are processed. The override issued at call
level 9 is processed. This changes the LPI(6) attribute to LPI(5).
9. The system searches call level 2 for applicable overrides that were scoped to
the call level. The override issued in call level 2 is processed. This assigns the
FOLD(*YES) attribute to file YYY.
10. The system searches call level 1 for applicable overrides that were scoped to
the call level. There are no such overrides.
11. The system searches the job level for applicable overrides that were scoped to
the job level. Because, the override issued in call level 5 was scoped to the job
level and it is for file YYY, it is processed. This changes the DEV(P1) attribute
to DEV(P2).
How the system processes overrides-scenario 2
When several overrides that override the file type to be used by a program are
applied, only the attributes specified on the overrides of the same type as the final
file are applied. In the following example, assume that program MAKEMASTER
attempts to open the diskette file DKA:
Chapter 3. Using overrides 45