Excluding CICS transactions from CPUTIME thresholding, but not DSA% Usage.

book

Article ID: 4494

calendar_today

Updated On:

Products

CA SYSVIEW Performance Management NXBRIDGE - SYSYVIEW/ENDEVOR

Issue/Introduction

Issue:    

Using the CTRANOPT function of CA SYSVIEW, customer would like the ability to exclude certain transactions from CPUTIME threshold checking, but not from DSA% usage. Long running transactions will legitimately use more CPU which is to be expected. However, the customer wants to make sure that the same transaction(s), do not use too much DSA storage.  

 

Environment

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

Resolution

Resolution:

This can not be accomplished using the CTRANOPT function, as CTRANOPT generically filters transactions by TRANID, regardless of threshold rules. 

However, this can still be accomplished using CA SYSVIEW.  A generic rule can be defined for CPUTIME, then define exclusion rules for CPU time for certain TRANIDs. An exclusion rule can be defined by setting the TRIVLVL to NONE for those transactions you wish to exclude from CPU monitoring.