MAXREP64 parameter: Difference between revisions
m (1 revision) |
m (1 revision) |
||
| Line 21: | Line 21: | ||
Setting MAXREP64 to a non-zero value will cause report writers to try to use | 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. | 64-bit storage which could relieve pressure on 31-bit storage. | ||
This will only work on | 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 | ||
Revision as of 01:02, 30 October 2012
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: