Tips about displaying overrides

 

Here are some tips you might use when you display overrides.

Note that when specifying a call level, as in the first two examples in this section, the call level on which you first entered override commands might not be level 1. Depending on the contents of the first program and first menu specified in your user profile, and any other programs or menus you might have come through, you might have entered your first override commands at level 3 or 4. You can enter WRKJOB and select option 11 (call stack) to see what programs are running at lower call levels. Unless you know exactly what you want to see, it is typically best to request the override display with no parameters, because options on the basic override display allow you to select a detailed display of any override you are interested in. The specific options available are:

• From the merged display of all overrides, you can request the display that is not merged, as in Example: Displaying overrides with WRKJOB.

• From the unmerged display of all overrides, you can request the merged display.

• From the merged display of all overrides, you can request a merged detail display of any override, equivalent to the command in Example: Displaying merged file overrides for one file.

• From the merged display of all overrides, you can request a display of all the individual overrides that contributed to the merged display, showing the level (call level or job level) for which each was requested.

• From either the display of contributing overrides or the display (not merged) of all overrides, you can request a detail display of the override for a particular file at a single call level.

 

Parent topic:

Display of overrides