Using the Automation Measurement Environment › Generate the OSFEVENT Segment

Generate the OSFEVENT Segment

The statistics reported in the OSFEVENT Segment of the Automation Statistics Report describe a particular OSF server transaction. When the OSF server transaction finishes and the OSFTRANSSMFREC parameter is set to YES, CA OPS/MVS generates an SMF record that describes the transaction. The OSFEVENT Segment reports the data in this SMF record.

To generate the OSFEVENT Segment, specify SEGMENTS=(OSFEVENT) and RECTYPE=(EVENT).

Example: OSFEVENT Segment

Here is an example of the OSFEVENT Segment:

               Automation Measurement Environment
  Statistics For SMFID S034    First Record Start: 2005/11/11 07:45:19
  SSNM OPSS                       Last Record End:            14:28:17
                       OSFEVENT: OSF Transaction Statistics
                            OSF Transaction Statistics
1>     Server job name . . . . . . . . . . . . . . . . . . . OPSOSF
       Server step name. . . . . . . . . . . . . . . . . . OPSS010E
       Server procstep name. . . . . . . . . . . . . . . . . . OPSS
       Server ASID . . . . . . . . . . . . . . . . . . . . . . 010E
2>     Command text  . . . . . . . SUBMIT 'OPS.O.CCLXCNTL(ARCHJOB)'
       Command length. . . . . . . . . . . . . . . . . . . . . . 28
       Command count . . . . . . . . . . . . . . . . . . . . . .  6
       Average command output lines. . . . . . . . . . . . . . .  3
       Average command I/O count . . . . . . . . . . . . . . . . 22
3>     Average command elapsed time. . . . . . . . . . . . . 2 secs
4>     Average command CPU (TCB + SRB) time. . . . . . . . . 193 ms
5>     Average time spent on server queue. . . . . . . . . .   2 ms

The following list describes the important items in the above report:

1

The job name of the OSF server that processed the transaction.

2

The text of the command that was sent to the OSF server that initiated the processing of the transaction.

3

The average elapsed time that the OSF server took to process the transaction.

4

The average CPU time that the OSF server took to process the transaction.

5

The average amount of time this transaction waited on the internal OSF Execute Queue until a server became available to process the transaction.