SYSVIEW GSVX554E (SMFDATA) and GSVX554E (CICSLOGR) messages in Sysview started task

Products

• SYSVIEW Performance Management

Issue/Introduction

Sysiew 16 and 17 on z/OS 2.4 operating systems. In the Sysview started task - 

GSV2808I (SMFDATA) Specified log stream name not defined in the LOGR policy.
GSVX554E (SMFDATA) IXGCONN CONNECT failed, log stream name not defined      

and 

GSV2808I (CICSLOGR) Specified log stream name not defined in the LOGR policy.
GSVX554E (CICSLOGR) IXGCONN CONNECT failed, log stream name not defined      

I am in the process of upgrading from 16 to 17. These messages are also in all of my 16 Sysviews. I just want to clean up these messages if I can. The first thing I found in the knowledge was to change the logstream defintions in CICSLOGR to None, but it was already set to none. Also tried setting DynamicSMFLogstreamDefinitions to COLD but that didn't work either, so I backed that out. 

Can you assist with cleaning these up?

Environment

Release : 17.0 and 16.0 

Cause

Parmlib Settings require update

Resolution

Start with reviewing the SMFDATA and CICSLOGR members in your CNM4BPRM library.   

(A note on libraries:   We encourage all sites to create a **.SITE.CNM4BPRM, where any site changes should be made.   The **.SYSTEM.CNM4BPRM should remain a Broadcom distributed copy, as fixes could cause updates to these members).   

In addition to reviewing the CICSLOGR and SMFDATA member, which specifies the logstream files, the parmlib member LGLOOKUP needs to be reviewed as it also references the various LOGSTREAM datasets. 

So in the event the SYSVIEW output shows the OPTION CICS, the LGLOOKUP checks to see if it is available and then assigns the CICS logstreams.  The CICS data collection section can instead be commented out by placing an asterisk (*) in front of the these lines, and then the messages should no longer appear in the task.