Large volume of SMF 255 Subtype 2 (PLOTLOG) records written by Sysview

Products

• SYSVIEW Performance Management
• NXBRIDGE - SYSVIEW/ENDEVOR

Issue/Introduction

Large volume of SMF type 255 records was being written by Sysview.

We then took dump of Sysview and restart it, but the issue continued.

We then suspected a CICS region that kept writing CICSLOGR was in a loop state, and the issue stopped after we cancelled the CICS region.

We would like to know if there is any command in Sysview that we can use to identify who is writing large volume of SMF 255 Subtype 2 records when the problem occur. 

Environment

Release : 16.0

Component : SYSVIEW

Resolution

The SMF 255 subtype 2 records are PLOTLOG records.

https://techdocs.broadcom.com/us/en/ca-mainframe-software/performance-and-storage/ca-sysview-performance-management/16-0/administrating/usage-of-smf-records/view-product-created-smf-records.html

If you do not want to collect PLOTLOG records the SYSVIEW Parmlib members SYSDATA and LGLOOKUP control the definition for the PLOTLOG.

Please review the doc for the SYSDATA member here:

https://techdocs.broadcom.com/us/en/ca-mainframe-software/performance-and-storage/ca-sysview-performance-management/16-0/administrating/library-members/cnm4bprm-parmlib-members/general-members/sysdata.html

Once you have changed the definitions it will require you to restart the SYSVIEW product.