JAL: link repair

2016-02-29T16:57:28Z

link repair

← Older revision		Revision as of 16:57, 29 February 2016
Line 27:		Line 27:
	<li>Set the <var class="product">Model 204</var> parameter <var>[[MINBUF parameter\|MINBUF]]</var> to at least 10000.</li>		<li>Set the <var class="product">Model 204</var> parameter <var>[[MINBUF parameter\|MINBUF]]</var> to at least 10000.</li>

	<li>Set the <var>[[~~LDBKMWND~~ parameter\|~~LDBKMWND~~]]</var> parameter to at least 30.</li>		<li>Set the <var>[[LDKBMWND parameter\|LDKBMWND]]</var> parameter to at least 30.</li>
	</ul>		</ul>

Admin: 1 revision: from Stage

2016-02-19T01:41:12Z

1 revision: from Stage

← Older revision	Revision as of 01:41, 19 February 2016
(No difference)

JAL: add category

2016-02-19T01:26:26Z

add category

New page

The <var>[[Fast/Unload Extraction Language (FUEL)#UNLOAD ALL INFORMATION or UAI|UAI]]</var> and <var>[[Fast/Reload statements#laistmt|LAI]]</var> statements support the
reorganization of procedures and procedure aliases.
Procedures and aliases present in the TAPEI input data set for a <var class="product">Fast/Reload</var> run
are loaded as is by <var>LAI</var> by default.
The <var>UAI</var> unload and <var>LAI</var> reload preserve their associations.

If procedure or alias names clash with names in the target file, the reload stops.
If you want the unloaded procedures and aliases not to be reloaded, you
specify the <var>NOPROCS</var> option of the <var>LAI</var> statement.

The procedure reloading feature likely entails some environmental adjustments
(especially more storage buffers), and it offers an automatic tuning of
the target file's procedure dictionary settings.

==Preparing the environment==
When you are <var>LAI</var>-reloading a file that has procedures, take into consideration the
following recommendations:
<ul>
<li>More CSECTs are required than in the typical BATCH204 module.
<li>Instead of maintaining separate BATCH204 and ONLINE modules,
combine their CSECTs into a single ONLINE module, and use that for <var class="product">Fast/Reload</var>.
<li>Ensure sufficient disk buffers to minimize the elapsed time for the reload:

If your storage capacity is plentiful, 10,000 to 15,000 buffers
should ensure maximum throughput.
<ul>
<li>Set the <var class="product">Model 204</var> parameter <var>[[MINBUF parameter|MINBUF]]</var> to at least 10000.</li>

<li>Set the <var>[[LDBKMWND parameter|LDBKMWND]]</var> parameter to at least 30.</li>
</ul>

Otherwise, if storage capacity is a concern, set the <var>[[MAXBUF parameter|MAXBUF]]</var> parameter
to the number of pages in the unloaded procedure dictionary, plus some overhead:
MAXBUF = PDpgs + LDKBMWND + 50 + min(10, nprocs) * avgProcpgs


Where:
<ul>
<li><code>PDpgs</code> (total number of pages in the unloaded procedure
dictionary), <code>nprocs</code> (number of unloaded procedures),
and <code>avgProcpgs</code> (average procedure length in pages)
are available from the <var>[[Fast/Unload program parameters#fstp|FSTATS]]</var> statistics in the <var>UAI</var> report data set.</li>

<li>The <var>LDKBMWND</var> parameter is set to at least 30.</li>
</ul></li>
</ul>

==Setting PDSIZE==
Procedure loading includes an automatic <var>[[PDSIZE parameter|PDSIZE]]</var>-setting feature.
This auto-sizing is weighted toward creating a new procedure dictionary
whose total size is nearly the same as the old, but which typically is a
product of a larger <var>PDSIZE</var> and fewer procedure dictionary chunks
(blocks of contiguous pages) than the old.

The sizing feature is invoked only when you are loading into a file that has no
procedures, the file's <var>PDSIZE</var> value is the default size (3),
and the number of pages of <var>UAI</var> unloaded procedures and aliases
is greater than the default <var>PDSIZE</var>.

When the preceding conditions exist, the <var>PDSIZE</var> of the reload target file is set
to one of the following:
<ul>
<li>The number of pages in the unloaded file's procedure dictionary,
if that number of pages is less than or equal to 255.</li>

<li>The smallest number less than 255 that will yield the smallest number of
page chunks, if the number of pages in the unloaded procedure dictionary exceeds 255.

To arrive at these smallest numbers, (the rounded-up, integral
result of) the number of pages in the unloaded procedure dictionary is
divided by the initial number of chunks in the new dictionary.
This chunks value is the quotient of the old page count and 255,
rounded up to the next integral value.</li>
</ul>

For example, for an unloaded dictionary that has 800 pages, the new chunk
count would be 4 (<code>800/255</code>, then rounded up), and the new <var>PDSIZE</var> would be
200 (<code>800/4</code>).
For an unloaded dictionary that has 1332 pages, the new chunk
count would be 6, and the new <var>PDSIZE</var> would be 222.

The target file's existing value for <var>PDSIZE</var> is used in any of the following cases:
<ul>
<li>A procedure dictionary already exists.</li>

<li><var>PDSIZE</var> is already set to a value other than 3.</li>

<li>The unloaded procedures and aliases used no more than 3 pages.</li>
</ul>

Note: The <var>PDSIZE</var> optimization feature is only activated if the <var class="product">Fast/Unload</var>
user has the <var>[[Fast/Unload program parameters#fstp|FSTATS]]</var> feature enabled.
If <var>FSTATS</var> is not enabled, necessary optimization information is not written to the unloaded data set.


==See also==
{{Template:Fast/Reload topic list}}

[[Category:Fast/Reload]]

Fast/Reload procedure handling - Revision history

JAL: link repair

Admin: 1 revision: from Stage

JAL: add category