ELowell: /* Example */

2014-11-11T20:16:12Z

Example

← Older revision		Revision as of 20:16, 11 November 2014
Line 73:		Line 73:
	<p>		<p>
	For example, if you execute a program that includes either of the following SOUL statements, all values of the Ordered Index for the field referenced are checked. Processing the statement holds some critical file resources for the file for a long time; update users are delayed until the search completes.</p>		For example, if you execute a program that includes either of the following SOUL statements, all values of the Ordered Index for the field referenced are checked. Processing the statement holds some critical file resources for the file for a long time; update users are delayed until the search completes.</p>
	<p class="code">FD <i>ordered-numeric-field-1</i> IS GT ''		<p class="code">FD <i>ordered-numeric-field-1</i> IS GT ''
	</p>		</p>
	<p>or</p>		<p>or</p>

JAL: minor cleanup

2014-11-11T20:15:07Z

minor cleanup

Show changes

Alex: Automatically generated page update

2013-02-28T01:05:10Z

Automatically generated page update

New page

==Summary==
<dl>
<dt>Privileges
<dd>System administrator
<dt>Function
<dd>To display each user that currently holds and enqueue on a critical file resource.
</dl>
==Syntax==
MONITOR CFR

The MONITOR command supports the CFR option, so you can display the following information regarding critical resource enqueues. The display consists of: 
<ul>
<li>
User number
</li>

<li>
File
</li>

<li>
Time of acquisition
</li>

<li>
Lock type-share or exclusive.
</li>
</ul>
MONITOR CFR output displays the following columns: 
<table>

<tr> <th>
Column heading in display
</th> <th>
Critical file resource held
</th> </tr>

<tr> <th><var>
USER
</var></th> <td>
User number of USERID holding the resource
</td> </tr>

<tr> <th><var>
USERID
</var></th> <td>
Identifies the specific user
</td> </tr>

<tr> <th><var>
FILE
</var></th> <td>
Name of file being locked or shared
</td> </tr>

<tr> <th><var>
RECENQ 
</var></th> <td>
Record enqueuing table
</td> </tr>

<tr> <th><var>
ALLOCD
</var></th> <td>
Resource to allocate pages from Table D
</td> </tr>

<tr> <th><var>
EXIST 
</var></th> <td>
Existence bitmap
</td> </tr>

<tr> <th><var>
INDEX 
</var></th> <td>
Ordered index
</td> </tr>

<tr> <th><var>
DIRECT 
</var></th> <td>
Table B
</td> </tr>

<tr> <th><var>
ALLOCE
</var></th> <td>
Resource to allocate pages from Table E
</td> </tr>

</table>
==Usage==
You can use the MONITOR CFR command to detect critical file resource conflicts in long-running, complex searches against large Ordered Indexes. You can issue a BUMP userid command or STOPU or correct the inefficient program. 
==Example==
The following is typical MONITOR CFR output:
USER USERID FILE RECENQ ALLOCD EXIST INDEX DIRECT ALLOCE
64 DOGS CCATEMP 190305 190305 190305 190305 190305 190305
38 NO USERID ACCT7 S>190305 S>190305
61 NO USERID ACCT0 S>190305
71 NO USERID CCATEMP S>190305 S>190305
76 NO USERID CCATEMP S>190305 S>190305

For example, if a user executes a program that includes either of the following User Language statements, all values of the Ordered Index for the field referenced are checked. Processing the statement holds some critical file resources for the file for a long time; update users are delayed until the search completes.
FD ordered-numeric-field-1 IS GT ''

or
FD ordered-character-field-1 IS LIKE *ABC

If at the same time, another user uses a program that includes the following User Language syntax, this user is delayed until the previous search completes.
CHANGE ordered-character-field-2 TO 'ABC'

Note: The S> characters before the timestamps indicate a shared lock type.
[[Category: System administrator commands]]
[[Category:Commands]]

MONITOR CFR command - Revision history

ELowell: /* Example */

JAL: minor cleanup

Alex: Automatically generated page update