Analyzing system logger data (SMF Type 88 records)

When you review the output from the system logger reports produced by IXGRPT1, IXGRPT1J, and IXGRPT1L, look at the following key fields for CICS® system logs.

Check the following key fields:
  • The number of bytes deleted from primary storage is close to the number of bytes written
  • The number of bytes deleted from the system log after writing to offload data sets is usually very low:
    • If this number is high, resources are being used to move data to the offload data set only to be later deleted.
    • This number is a key indicator that log-tail deletion is not working effectively.
    • Check the MVS™ system log for any DFHRM0205 and DFHLG0743 messages from the affected CICS region.
    • Look for long-running tasks (using CICS monitoring data or a system monitoring package), or check if AKPFREQ is too high.
  • In general offloads are acceptable, but offloads triggered by NTRY FULL indicators are not a good sign:
    • NTRY FULL indicates that the entry-to-element ratio is too high.
    • Such offloads are probably the result of unlike logstreams defined in the same structure.
    • The offloads are being triggered by all the entries being used rather than triggered by the HIGHOFFLOAD value.
  • TYPE3 I/O counts must not appear in the statistics for coupling facility log streams, because they indicate that I/O is being initiated when over 90% of the elements for the log stream are in use.
  • Average buffer size is important for these reasons:
    • If over 4 KB, the writes are asynchronous, rather than synchronous.
    • Buffer size is used to determine the entry to element ratio.
    • If MAXBUFSIZE specified on the log stream definition is lower than 65 532-bytes, the element size is 256-bytes.
    • If MAXBUFSIZE is 65 532-bytes, the element size is 512-bytes.
    • The entry-to-element ratio is calculated as (average-buffer-size plus 4 divided by 4).


dfha1d6.html | Timestamp icon Last updated: Sunday, 4 June 2017