ULTRACEP parameter: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
 
(2 intermediate revisions by one other user not shown)
Line 15: Line 15:


==Description==
==Description==
This numeric parameter indicates the maximum number of CCATEMP pages that
This numeric parameter indicates the maximum number of [[Using_the_system_scratch_file_(CCATEMP)|CCATEMP]] pages that
will be allocated for a user for holding trace data.
will be allocated for a user for holding trace data.
The CCATEMP wrap-around trace table is a user-specific trace table that
The CCATEMP wrap-around trace table is a user-specific trace table that
Line 21: Line 21:
<var>ULTRACEP</var> user parameter.
<var>ULTRACEP</var> user parameter.


If <var>ULTRACEP</var> pages are already in use when a <var>Trace</var> statement is issued,
If <var>ULTRACEP</var> pages are already in use when a <var>[[Trace statement|Trace]]</var> statement is issued,
and output is being routed to the trace table (<code>ULTRACE X'04'</code> set &mdash;
and output is being routed to the trace table (<code>ULTRACE X'04'</code> set &mdash;
see <var>[[ULTRACE parameter|ULTRACE]]</var>), the trace data on the oldest page is discarded,
see <var>[[ULTRACE parameter|ULTRACE]]</var>), the trace data on the oldest page is discarded, and the oldest page is reused for the new trace data.
and the oldest page is reused for the new trace data.
For more information on the <var>Trace</var> statement, see the <i>[http://sirius-software.com/maint/download/factr.pdf SirFact_Reference_Manual]</i>.


The wrap-around trace table is dumped in <var class="product">SirFact</var> dumps, and it can be viewed
The wrap-around trace table is dumped in <var class="product">[[SirFact]]</var> dumps, and it can be viewed with the following command when using the [[SirFact FACT subsystem|FACT]] subsystem to examine a dump:
with the following command when using the <var>FACT</var> subsystem to examine a dump:
<p class="code">D[ISPLAY] T[RACE][.{* | N}]
<p class="code">D[ISPLAY] T[RACE][.{* | N}]
</p>
</p>
Line 36: Line 33:


The current contents of the wrap-around trace table can also be examined
The current contents of the wrap-around trace table can also be examined
with the <var>$Trace2List</var> function or the <var>Stringlist</var> class <var>[[AppendTrace (Stringlist function)|AppendTrace]]</var> method.
with the <var>[[SirFact $functions#tr2list|$Trace2List]]</var> function or the <var>Stringlist</var> class <var>[[AppendTrace (Stringlist function)|AppendTrace]]</var> method.
For more information about <var class="product">SirFact</var> dumps, the <var>$Trace2List</var> function, and
 
the <var>AppendTrace</var> method, see the <var class="product">SirFact</var> manual.
<!-- VTPRNAME - BELONGS TO CCA -->
<!-- VTPRNAME - BELONGS TO CCA -->


[[Category:User parameters]]
[[Category:User parameters]]
[[Category:Parameters]]
[[Category:Parameters]]

Latest revision as of 14:22, 17 October 2017

Max UL Trace statement pages

Summary

Default value
2
Parameter type
User
Where set
User and $Resetn resettable
Related products
SirFact
Introduced
Before Sirius Mods 6.7

Description

This numeric parameter indicates the maximum number of CCATEMP pages that will be allocated for a user for holding trace data. The CCATEMP wrap-around trace table is a user-specific trace table that consists of a set of CCATEMP pages whose maximum size is specified by the ULTRACEP user parameter.

If ULTRACEP pages are already in use when a Trace statement is issued, and output is being routed to the trace table (ULTRACE X'04' set — see ULTRACE), the trace data on the oldest page is discarded, and the oldest page is reused for the new trace data.

The wrap-around trace table is dumped in SirFact dumps, and it can be viewed with the following command when using the FACT subsystem to examine a dump:

D[ISPLAY] T[RACE][.{* | N}]

where N specifies that the last n entries are to be displayed. Specifying D T will display all trace entries, and specifying D T.20 will display the last 20.

The current contents of the wrap-around trace table can also be examined with the $Trace2List function or the Stringlist class AppendTrace method.