30.06.2013 Views

File Management - IBM

File Management - IBM

File Management - IBM

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

42 <strong>File</strong> <strong>Management</strong> V4R5<br />

activation group level. However, overrides (C and D) that are specified in a named<br />

activation group can be scoped to the call level, activation group level, or the job<br />

level. Overrides (C) scoped to a named activation group level remain in effect until<br />

the system replaces or deletes the override, or until the system deletes the named<br />

activation group.<br />

Overrides (D) that are scoped to the call level within a named activation group<br />

remain in effect until they are replaced, deleted, or until the program in which they<br />

were issued ends. Overrides can be scoped to the call level by specifying<br />

OVRSCOPE(*CALLLVL) on the override command.<br />

Overrides that are scoped to a named activation group level apply only to<br />

programs that run in the named activation group. They have no affect on<br />

programs that run in other named activation groups or in the user default<br />

activation group.<br />

Call levels identify the subordinate relationships between related programs when<br />

one program calls another program within a job. Overrides that are scoped to the<br />

call level remain in effect from the time they are specified until they are replaced,<br />

or deleted, or until the program in which they are specified ends. This is true<br />

whether you issue the override in the user default activation group or in a named<br />

activation group.<br />

For example:<br />

Job<br />

User Default Activation Group<br />

Call Level 1 PGM A<br />

CALL PGM B<br />

Call Level 2 PGM B<br />

TFRCTL PGM C<br />

PGM C<br />

Call Level 3 PGM D<br />

Figure 5. Call Levels within a Job<br />

CALL PGM D<br />

RETURN<br />

RV3H011-1<br />

Several commands, such as Work with Job (WRKJOB), Work with Active Jobs<br />

(WRKACTJOB), or Display Job (DSPJOB), have options that allow you to display<br />

the call stack of an active job. There is a one-to-one relationship between a<br />

program that is displayed in the call stack and the call level. The first program

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!