144 lines
8.5 KiB
HTML
144 lines
8.5 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
<!DOCTYPE html
|
||
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
<html lang="en-us" xml:lang="en-us">
|
||
|
<head>
|
||
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2005" />
|
||
|
<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" />
|
||
|
<meta name="security" content="public" />
|
||
|
<meta name="Robots" content="index,follow" />
|
||
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
<meta name="DC.Type" content="concept" />
|
||
|
<meta name="DC.Title" content="How the server processes overrides: scenario" />
|
||
|
<meta name="abstract" content="When overrides are scoped to an activation group, the server does not process these overrides until it reaches the call level of the oldest procedure in that activation group." />
|
||
|
<meta name="description" content="When overrides are scoped to an activation group, the server does not process these overrides until it reaches the call level of the oldest procedure in that activation group." />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rbal3call.htm" />
|
||
|
<meta name="DC.Format" content="XHTML" />
|
||
|
<meta name="DC.Identifier" content="rbal3ile" />
|
||
|
<meta name="DC.Language" content="en-us" />
|
||
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
<!-- US Government Users Restricted Rights -->
|
||
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
<title>How the server processes overrides: scenario</title>
|
||
|
</head>
|
||
|
<body id="rbal3ile"><a name="rbal3ile"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">How the server processes overrides: scenario</h1>
|
||
|
<div><p><span><img src="./delta.gif" alt="Start of change" />When overrides are scoped to an activation
|
||
|
group, the server does not process these overrides until it reaches the call
|
||
|
level of the oldest procedure in that activation group.<img src="./deltaend.gif" alt="End of change" /></span></p>
|
||
|
<p>The following example shows how overrides work in multiple activation groups.</p>
|
||
|
<div class="note"><span class="notetitle">Note:</span> By using the code example, you agree to the terms of the <a href="codedisclaimer.htm">Code license and disclaimer information</a>.</div>
|
||
|
<div class="fignone"><span class="figcap">Figure 1. Example of override processing in multiple activation groups</span>. <span class="figdesc">An example of how overrides work in multiple activation groups.</span><pre> Program A (in user default activation group)
|
||
|
Call Level 2 OVRPRTF FILE(YYY) FOLD(*YES) OVRSCOPE(*CALLLVL)
|
||
|
CALL PGM B
|
||
|
|
||
|
Call Level 3 Program B (in activation group 8)
|
||
|
OVRPRTF FILE(ZZZ) TOFILE(YYY) DEV(P1) LPI(6) +
|
||
|
OVRSCOPE(*CALLLVL)
|
||
|
CALL PGM C
|
||
|
|
||
|
Call Level 4 Program C (in user default activation group)
|
||
|
OVRPRTF FILE(ZZZ) CPI(12) OVRSCOPE(*CALLLVL)
|
||
|
CALL PGM D
|
||
|
|
||
|
Call Level 5 Program D (in activation group 21)
|
||
|
OVRPRTF FILE(YYY) DEV(P2) OVRSCOPE(*JOB)
|
||
|
CALL PGM E
|
||
|
|
||
|
Call Level 6 Program E (in activation group 21)
|
||
|
OVRPRTF FILE(ZZZ) LPI(12) OVRSCOPE(*ACTGRPDFN)
|
||
|
CALL PGM F
|
||
|
|
||
|
Call Level 7 Program F (in activation group 8)
|
||
|
OVRPRTF FILE(ZZZ) LPI(9) OVRSCOPE(*CALLLVL)
|
||
|
CALL PGM G
|
||
|
|
||
|
Call Level 8 Program G (in activation group 8)
|
||
|
OVRPRTF FILE(ZZZ) DUPLEX(*NO) +
|
||
|
OVRSCOPE(*ACTGRPDFN)
|
||
|
CALL PGM H
|
||
|
|
||
|
Call Level 9 Program H (in activation group 8)
|
||
|
OVRPRTF FILE(YYY) LPI(5) OVRSCOPE(*ACTGRPDFN)
|
||
|
CALL PGM I
|
||
|
|
||
|
Call Level 10 Program I (in activation group 8)
|
||
|
OPEN FILE(ZZZ)</pre>
|
||
|
</div>
|
||
|
<p>When program I opens file ZZZ, file ZZZ has the following attributes:</p>
|
||
|
<div class="p"> <dl><dt class="dlterm">CPI(12)</dt>
|
||
|
<dd>From call level 4</dd>
|
||
|
<dt class="dlterm">FILE(YYY)</dt>
|
||
|
<dd>From call level 3</dd>
|
||
|
<dt class="dlterm">LPI(5)</dt>
|
||
|
<dd>From call level 9</dd>
|
||
|
<dt class="dlterm">FOLD(*YES)</dt>
|
||
|
<dd>From call level 2</dd>
|
||
|
<dt class="dlterm">DEV(P2)</dt>
|
||
|
<dd>From call level 5</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
<div class="p">The server processes the overrides in the following order: <ol><li>File ZZZ opens at call level 10. The server looks for any overrides issued
|
||
|
at call level 10 that were scoped to the call level. There are no such overrides.</li>
|
||
|
<li>The server searches the next previous call level (level 9) for applicable
|
||
|
overrides that were scoped to the call level. There are no such overrides.
|
||
|
(The override issued in call level 9 is for file YYY and does not apply.)</li>
|
||
|
<li>The server searches call level 8 for applicable overrides that were scoped
|
||
|
to the call level. There is an override for file ZZZ; however, it is scoped
|
||
|
to the activation group level. The server 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 server 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.</li>
|
||
|
<li>The server 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.</li>
|
||
|
<li>The server 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 server ignores this override altogether
|
||
|
because it is scoped to an activation group other than activation group 8.</li>
|
||
|
<li>The server 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.)</li>
|
||
|
<li>The server 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.</li>
|
||
|
<li>The server 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. <p>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).</p>
|
||
|
</li>
|
||
|
<li>The server 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.</li>
|
||
|
<li>The server searches call level 1 for applicable overrides that were scoped
|
||
|
to the call level. There are no such overrides.</li>
|
||
|
<li>The server 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).</li>
|
||
|
</ol>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div>
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal3call.htm" title="In the Integrated Language Environment, overrides can be scoped to the call level, the activation-group level (the default), and the job level.">How the server processes overrides</a></div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</body>
|
||
|
</html>
|