Problem with JOBNAME Logical Group and Threshold Triggering
search cancel

Problem with JOBNAME Logical Group and Threshold Triggering

book

Article ID: 46510

calendar_today

Updated On:

Products

SYSVIEW Performance Management NXBRIDGE - SYSVIEW/ENDEVOR

Issue/Introduction

I am trying to use logical groups in CICS threshold definitions, but having trouble using type JOBNAME. I have the following definitions in the GROUPS parmlib member: 

DEFINE CICSM 
TYPE JOBNAME 
DESC 'TEST lpar CICS Regions ' 
MEMBER CICSM1 
MEMBER CICSM2 
DEFINE MARCUS TYPE CICSTRAN DESC 'Test out GROUP function ' 
INSTANCE = 
MEMBER SSCC 
MEMBER SSCD 

The following threshold definition coded in the CTHRESH member does not trigger: 

DEFINE LIFETIME JOBNAME >CICSM TRAN >MARCUS RSCE = LIMIT 30.000 ....

 I also have this rule defined that is triggered:

 DEFINE LIFETIME JOBNAME CICSM* TRAN = RSCE = LIMIT 600.000 ...

Why the rule defined for the Group CICSM (LIFETIME JOBNAME >CICSM TRAN >MARCUS RSCE = LIMIT 30.000 ...) still does not trigger?

Environment

Release: FAQSO.00200-14.1-SYSVIEW-Performance Management
Component:

Resolution

First of all, Type CICSPLEX, not JOBNAME,  need to be used creating a logical group for " lpar CICS Regions"  (in this case Group CICSM).

So the definition within  the  GROUPS parmlib member needs to be changed to: 

DEFINE CICSM 
TYPE CICSPLEX
DESC 'TEST lpar CICS Regions ' 
MEMBER CICSM1 
MEMBER CICSM2 

Then, viewing the definitions online,we can better understand how the Threshold process searches threshold definitions and finds the best match on a rule. All threshold definitions for the specific metric or variable name will be processed. The last match in the list "wins". The generic threshold ( DEFINE LIFETIME JOBNAME CICSM* TRAN = RSCE = ) wins over the process to find the best match for a transaction defined in group MARCUS running in any of the CICS regions included in the CICSM group.

Additional Information

See Topics : Exception definition best match rules
See HELP panel for CTHRESH command