ibm-information-center/dist/eclipse/plugins/i5OS.ic.dm_5.4.0.1/rbal3call.htm

118 lines
9.2 KiB
HTML
Raw Permalink Normal View History

2024-04-02 14:02:31 +00:00
<?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" />
<meta name="abstract" content="In the Integrated Language Environment, overrides can be scoped to the call level, the activation-group level (the default), and the job level." />
<meta name="description" content="In the Integrated Language Environment, overrides can be scoped to the call level, the activation-group level (the default), and the job level." />
<meta name="DC.subject" content="scope, overriding, override command, job, definition, interactive, interactive job, OVRSCOPE (override scope) parameter, *JOB value, override, parameter, OVRSCOPE, OVRSCOPE (override scope) parameter, activation group, user default, named, user default activation group, named activation group, group, activation, call level, in ILE, in user default activation group, job level, override command, scoping override, *CALLLVL value, job level, description, overriding file, call level, relationship with call stack, call stack of active job, CALL command, RETURN command, program stack, in named activation group" />
<meta name="keywords" content="scope, overriding, override command, job, definition, interactive, interactive job, OVRSCOPE (override scope) parameter, *JOB value, override, parameter, OVRSCOPE, OVRSCOPE (override scope) parameter, activation group, user default, named, user default activation group, named activation group, group, activation, call level, in ILE, in user default activation group, job level, override command, scoping override, *CALLLVL value, job level, description, overriding file, call level, relationship with call stack, call stack of active job, CALL command, RETURN command, program stack, in named activation group" />
<meta name="DC.Relation" scheme="URI" content="rbal3applyovr.htm" />
<meta name="DC.Relation" scheme="URI" content="rbal3prior.htm" />
<meta name="DC.Relation" scheme="URI" content="rbal3ile.htm" />
<meta name="DC.Relation" scheme="URI" content="rbal3ovrgp.htm" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rbal3call" />
<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</title>
</head>
<body id="rbal3call"><a name="rbal3call"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">How the server processes overrides</h1>
<div><p>In the Integrated Language Environment<sup>®</sup>,
overrides can be scoped to the call level, the activation-group level (the
default), and the job level.</p>
<p><a href="#rbal3call__ile1">Figure 1</a> shows a representation
of a job running in the Integrated Language Environment.</p>
<div class="fignone" id="rbal3call__ile1"><a name="rbal3call__ile1"><!-- --></a><span class="figcap">Figure 1. A job in the Integrated Language
Environment<sup>®</sup></span><br /><img src="rv3h012.gif" alt="A job in the Integrated Language&#xA;Environment" /><br /></div>
<p>In the description that follows, the reference keys refer
to the corresponding reference keys in the <a href="#rbal3call__ile1">Figure 1</a>.</p>
<div class="p">A <dfn class="term">job</dfn> is a piece of work that the server performs.
An <dfn class="term">interactive job</dfn> begins when a user signs on and ends when
a user signs off. Overrides (<dfn class="term">A</dfn>) that are scoped to the job level
affect all programs that are running in any activation group within the job.
There can be only one active override for a file at the job level. If you
specify more than one, the most recent one takes effect. An override that
is scoped to the job level remains in effect until one of the following events
occurs: <ul><li>The job ends</li>
<li>The server explicitly deletes the override</li>
<li>Another job level override for the same file replaces the override</li>
</ul>
This is true regardless of the call level in which the overrides were
specified. For example, an override that is issued in call level 3 that is
scoped to the job level remains in effect when call level 3 is deleted. Overrides
can be scoped to the job level by specifying OVRSCOPE(*JOB) on the override
command.</div>
<p>Overrides (<span class="uicontrol">B</span>) that are specified in the user default
activation group can be scoped to the call level or to the job level. They
cannot be scoped to the user default activation group level. However, overrides
(<span class="uicontrol">C</span> and <span class="uicontrol">D</span>) that are specified
in a named activation group can be scoped to the call level, activation group
level, or the job level. Overrides (<span class="uicontrol">C</span>) scoped to a
named activation group level remain in effect until the server replaces or
deletes the override, or until the server deletes the named activation group.</p>
<p>Overrides (<span class="uicontrol">D</span>) that are scoped to the call level
within a named activation group remain in effect until they are replaced,
deleted, or until the program in which they were issued ends. Overrides can
be scoped to the call level by specifying OVRSCOPE(*CALLLVL) on the override
command.</p>
<p>Overrides that are scoped to a named activation group level apply only
to programs that run in the named activation group. They have no effect on
programs that run in other named activation groups or in the user default
activation group.</p>
<p><span class="uicontrol">Call levels</span> identify the subordinate relationships
between related programs when one program calls another program within a job.
Overrides that are scoped to the call level remain in effect from the time
they are specified until they are replaced, or deleted, or until the program
in which they are specified ends. This is true whether you issue the override
in the user default activation group or in a named activation group.</p>
<p>For example:</p>
<div class="fignone" id="rbal3call__job"><a name="rbal3call__job"><!-- --></a><span class="figcap">Figure 2. Call levels within a job</span><br /><img src="rv3h011.gif" alt="Call levels within a job" /><br /></div>
<p>Several commands, such as <a href="../cl/wrkjob.htm">Work
with Job (WRKJOB)</a>, <a href="../cl/wrkactjob.htm">Work
with Active Jobs (WRKACTJOB)</a>, or <a href="../cl/dspjob.htm">Display Job (DSPJOB)</a>, have options that allow you to
display the call stack of an active job. There is a one-to-one relationship
between a program that is displayed in the call stack and the call level.
The first program name displayed (at the top of the list) on the call stack
is the program at call level 1 for that job. Call level 1 is the lowest call
level for a job. The second program name displayed is the program at call
level 2 for that job. The last program name displayed is the program at the
highest call level for that job.</p>
<p>In the example in <a href="#rbal3call__job">Figure 2</a>, the <a href="../cl/tfrctl.htm">Transfer Control (TFRCTL)</a> command
to PGMC causes PGMC to replace PGMB from the call stack. A CALL command places
another program in the call stack. A RETURN command removes a program from
the stack.</p>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="rbal3prior.htm">Process priority of overrides</a></strong><br />
Some overrides have higher priorities than others.</li>
<li class="ulchildlink"><strong><a href="rbal3ile.htm">How the server processes overrides: scenario</a></strong><br />
<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></li>
<li class="ulchildlink"><strong><a href="rbal3ovrgp.htm">Process overrides: General principles</a></strong><br />
The server processes overrides according to some general principles.</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal3applyovr.htm" title="You can perform two general types of overrides, which are file overrides and overrides for program device entries.">Apply overrides</a></div>
</div>
</div>
</body>
</html>