What contributes to the CPU utilization in CA-GSS by the CA SYSVIEW System Condition Monitor (SCM)?

Document ID : KB000009432
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

This is a basic summary of how CA GSS processes SYSVIEW commands to gather information for the SYSVIEW System Condition Monitor (SCM) display.

Environment:
z/OS
Instructions:

This is a basic summary of how CA GSS processes SYSVIEW commands to gather information for the SYSVIEW System Condition Monitor (SCM) display.

Solution:

The SYSVIEW Parmlib member SCM controls which IMODS get run by CA GSS.

The Control Section Interval )INTERVAL determines how often GSS is to 'wake up' and run
through the list of IMODS.

Next are the Section Definition Default values.
These are the default values which will be used in the event that the Definition Sections are missing one or more of the parameters.

The Definitions Section determines what is displayed on the SCM display.

For example, the following definition:
DEFINE * MVS OPERATOR
INTERVAL 120
IMOD *
PARMS
DETAILIMOD SCM_WTOR SUMMARYALL
DETAILIMOD SCM_TAPE SUMMARYALL
DETAILIMOD SCM_MIATAPES SUMMARYALL
DETAILIMOD SCM_PRINTERS SUMMARYALL
DETAILIMOD SCM_LISTCONS SUMMARYALL
DETAILIMOD SCM_SPOOLS
DETAILIMOD SCM_SMF
DETAILIMOD SCM_LISTINP SUMMARYALL
DETAILIMOD SCM_CONFLICTS SUMMARYALL

Places the following entry on to the SCM display:

Under SCM primary command you will see the following entries:
Description
<Define in parmlib - SYSNAMES>
MVS
JOBS
USS
JES2
CICSPLEX

When you select the entry for MVS you will see the following entry;

Name Description
OPERATOR Operations overview

Hence the DEFINE entry MVS OPERATOR.

The OPERATOR entry contains subentries similar to the following:

Description
Mount pending on 1 TAPE device.
WTOs requiring replies is 37
The JES2 input queue has 25 jobs held due to duplicate jobnames.
The JES2 input queue has 89 jobs held due to TYPRUN=HOLD.
There are 10 jobs waiting for classes A,B,H.
WTO buffers are queued on 4 CONSOLES.
No jobs are waiting due to enqueue conflicts.
No PRINT devices require attention.
Spool volume SPLXDA extension 9 is 19.8% full.
Spool volume SPLXD1 extension 7 is 12.1% full.
Spool volume SPLXD2 extension 6 is 11.9% full.
Spool volume SPLXD3 extension 3 is 12.1% full.
Spool volume SPLXD4 extension 8 is 13.7% full.
Spool volume SPLXD6 extension 1 is 15.0% full.
Spool volume SPLXD8 extension 0 is 34.4% full.
Spool volume SPLXD9 extension 2 is 15.4% full.
SMF is recording to DATASET
SMF recording 18% used. Dsn=SYS1.MAN5

These are the results of running the following IMODS:
SCM_WTOR
SCM_TAPE
SCM_MIATAPES
SCM_PRINTERS
SCM_LISTCONS
SCM_SPOOLS
SCM_SMF
SCM_LISTINP
SCM_CONFLICTS

So, if you were to comment out the line SCM_CONFLICTS the CONFLICTS entry would be missing from the MVS OPERATOR SCM display.

If you want to almost half your CPU utilization you could just double the value of the INTERVAL parameter on each DEFINE statement.
You should evaluate what entries you want to have displayed on the SCM. Do you need or want all of the SCM entries that are activated out of the box?
They are:

WLM
TAPE
OPERATOR
XSYSTEM
PAGING
STORAGE
ALERTS
ENQUEUES
PRINTERS
SMS
CHANNELS
DEVICES
DASD
HEALTH
LXATABLE
PARTINFO
VTAM

This information gives you some guidance in how to set up the SCM for CA SYSVIEW.