MONITOR CFR command

Summary

Privileges

System administrator

Function

To display each user that currently holds and enqueue on a critical file resource.

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:

• User number
• File
• Time of acquisition
• Lock type-share or exclusive.

MONITOR CFR output displays the following columns:

Column heading in display	Critical file resource held
USER	User number of USERID holding the resource
USERID	Identifies the specific user
FILE	Name of file being locked or shared
RECENQ	Record enqueuing table
ALLOCD	Resource to allocate pages from Table D
EXIST	Existence bitmap
INDEX	Ordered index
DIRECT	Table B
ALLOCE	Resource to allocate pages from Table E

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 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.

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 SOUL 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.