MAXREP64 parameter: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
mNo edit summary
 
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Template:MAXREP64 parameter subtitle}}
==Summary==
==Summary==
<dl>
<dl>
Line 12: Line 14:
<dd><var class="product">[[Sirius Mods]]</var> 7.2
<dd><var class="product">[[Sirius Mods]]</var> 7.2
</dl>
</dl>
==Description==
==Description==
This parameter indicates the maximum amount of 64-bit virtual storage to be used
This parameter indicates the maximum amount of 64-bit virtual storage to be used
by report writers (currently, only the Dataset class SirtuneReport method).
by report writers (currently, only the <var>Dataset</var> class <var>[[SirtuneReport (Dataset function)|SirtuneReport]]</var> method).
Report writers can use a lot of virtual storage which can adversely effect other
Report writers can use a lot of virtual storage which can adversely effect other
users in an Online.
users in an Online.
This is why the default is 0 for any multi-user run.
This is why the default is 0 for any multi-user run.


Setting MAXREP64 to a non-zero value will cause report writers to try to use
Setting <var>MAXREP64</var> to a non-zero value will cause report writers to try to use
64-bit storage which could relieve pressure on 31-bit storage.
64-bit storage which could relieve pressure on 31-bit storage.
This will only work on <var class="product">Model 204</var> V6R3 and later, because earlier releases of <var class="product">Model 204</var>
This will only work on <var class="product">Model 204</var> V6R3 and later, because earlier releases of <var class="product">Model 204</var> do not support 64-bit addressing.
do not support 64-bit addressing.
For more information on utilizing 64-bit storage, see the documentation for the
For more information on utilizing 64-bit storage, see the documentation for the
specific report writer (for example the [[SirTune Reference Manual]]).
specific report writer (for example the <var class="book">[http://www.sirius-software.com/maint/download/tunr.pdf SirTune Reference Manual]</var>).


For single-user runs, it probably makes sense to make MAXREP64 very large
For single-user runs, it probably makes sense to make <var>MAXREP64</var> very large
(like 100000), as no report writer is likely to use that much, anyway, and
(like 100000), as no report writer is likely to use that much, anyway, and
the system-wide MEMLIMIT controls should prevent a job from using more virtual
the system-wide MEMLIMIT controls should prevent a job from using more virtual
Line 33: Line 35:
See also:
See also:
<ul>
<ul>
<li>[[CURREP31 parameter|CURREP31]]
<li><var>[[CURREP31 parameter|CURREP31]]</var>
<li>[[CURREP64 parameter|CURREP64]]
<li><var>[[CURREP64 parameter|CURREP64]]</var>
<li>[[HGHREP31 parameter|HGHREP31]]
<li><var>[[HGHREP31 parameter|HGHREP31]]</var>
<li>[[HGHREP64 parameter|HGHREP64]]
<li><var>[[HGHREP64 parameter|HGHREP64]]</var>
<li>[[MAXREP31 parameter|MAXREP31]]
<li><var>[[MAXREP31 parameter|MAXREP31]]</var>
</ul>
</ul>
[[Category:System parameters]]
[[Category:System parameters]]
[[Category:Parameters]]
[[Category:Parameters]]

Latest revision as of 20:03, 14 August 2014

Maximum 64-bit storage for report writers (megabytes)

Summary

Default value
0
Parameter type
System
Where set
System manager resettable
Related products
SirTune
Introduced
Sirius Mods 7.2

Description

This parameter indicates the maximum amount of 64-bit virtual storage to be used by report writers (currently, only the Dataset class SirtuneReport method). Report writers can use a lot of virtual storage which can adversely effect other users in an Online. This is why the default is 0 for any multi-user run.

Setting MAXREP64 to a non-zero value will cause report writers to try to use 64-bit storage which could relieve pressure on 31-bit storage. This will only work on Model 204 V6R3 and later, because earlier releases of Model 204 do not support 64-bit addressing. For more information on utilizing 64-bit storage, see the documentation for the specific report writer (for example the SirTune Reference Manual).

For single-user runs, it probably makes sense to make MAXREP64 very large (like 100000), as no report writer is likely to use that much, anyway, and the system-wide MEMLIMIT controls should prevent a job from using more virtual storage than it should.

See also: