FILE reports

The FILE reports contain monitored data on access to a file.

Report output

The REPORT FILE statement is used to request the output of the FILE reports.

The FILE report consists of the following sections:

• USER FILE report for the FILE user-specific monitoring program

• PRIVILEGED FILE report for the FILE monitoring program (for privileged users only)

The USER FILE report can only be output if the SM2 administrator has

• permitted the FILE user-specific monitoring program using the statement MODIFY-USER-ADMISSION FILE=*ALLOW and

• included files in the monitoring process using the FILE statement

The PRIVILEGED FILE report can only be output if the SM2 administrator has

• defined files using the ADD-FILE statement

• started file monitoring using the statement START-MEASUREMENT-PROGRAM TYPE=*FILE

Outputting monitored data in the FILE reports

In the USER FILE report, the nonprivileged user receives the values for the files of the FILE user-specific monitoring program he or she has included.

In the PRIVILIGED FILE report, the privileged user is shown the values for all the files included in the monitoring process by an SM2 administrator for the monitoring program. These values are also written to the SM2 output file.

Overflow screens may be requested for this report.

The layout of the FILE reports for nonprivileged and privileged users is identical, except for the headers (the former are entitled SM2 USER FILE REPORT, the latter are entitled SM2 PRIVILEGED FILE REPORT).

 HOST0001 SM2 PRIVILEGED FILE     CYCLE:   60 S                   <date>  <time>

 -----+-----+-----+-----+-----+-------------------------------------------------
 WAIT |CHECK|READ |WRITE|TIME |    FILENAME
 -----+-----+-----+-----+-----+-------------------------------------------------
   1.5|  0.0|  0.0|  1.5|2.23 |:2OSH:$TSOS.TSOSCAT
   0.0|  0.0|  0.0|  0.0|    *|:2SO6:$TSOS.TSOSCAT
   0.0|  0.0|  0.0|  0.0|    *|:2OS7:$TSOS.TSOSCAT
 -----+-----+-----+-----+-----+-------------------------------------------------

Monitoring information

WAIT	The number of WAIT operations per second is incremented if: reading from the file to main memory was initiated and the task is waiting for the end of the read operation, or writing from main memory to the file was initiated and the task is waiting for the end of the write operation. WAIT operations not combined with read or write operations are ignored.
CHECK	The number of CHECK operations per second is incremented whenever a check is made to see whether the preceding write operation was performed properly (read-after-write check). Only those read-after-write checks are counted which were initiated together with a write operation.
READ	Number of read operations per second
WRITE	Number of write operations per second
TIME	Average duration of an input/output operation in milliseconds; * means that no input/output operation has taken place.
	The value shown here represents the logical duration of the input/output operation from initiation to completion of the job from the point of view of the software. In the case of asynchronous input/output operations, this may be considerably greater than the hardware time. The < sign indicates that the value cannot be fully accommodated in the field.
FILENAME	Name of the monitored file

In the case of composite PAM operations such as Read and Wait for Termination, both values are incremented (READ and WAIT).