CTHRESH Setup to prevent cancel of a task

book

Article ID: 192790

calendar_today

Updated On:

Products

CA SYSVIEW Performance Management NXBRIDGE - SYSYVIEW/ENDEVOR

Issue/Introduction

I have Intertest for CICS installed. 

The menu transaction (ITST) appears to time out and the transaction is cancelled by SYSVIEW. 

Here's what I see in the CICS log:

GSVC157I (SDCS) Tran ITST Task  67 to be cancelled by  831                     

         threshold.|Jobname = Metric LIFETIME Rsce1 ITST Rsce2 =                

         |CanLimit 12.00000 Policy=00122690                                    

GSVC101I (SDCS) GSVCSDCS has issued a CANCEL for the transaction ITST  67 CICSSV

GSVC102I (SDCS) CANCEL Tran ITST Task  67 WaitType ZCIOWAIT WaitName DFHZARQ1 Jo

 

Checked with Intertest Support and they said they've seen this with other CICS monitors such as Omegamon and TMON. 

The suggestion is to bypass monitoring of this transaction.   

I tried to set up a rule using CTHRESH but it's not working. 

Can you look at it and tell me what values I should be putting in these fields or if there's a way to bypass monitoring the ITST transaction?  !

Environment

Release : 16.0

Component : SYSVIEW

Resolution

If you really don't want ITST tran to participate in the threshold processing then I would suggest using the CTRANOPT display and add an entry for ITST.
 
Overtype the >add with the transaction name ITST and the Jobname with the CICS region name CICSSVWA.
Help for the other fields is available by hitting PF1 while your cursor is in the field name.
 
Field names are
Collect,
Thresh (set to NOTHRESH) , CanEligible (which you would want to insure is set to NOCANCEL). 
The remainder are miscellaneous data collection options...
 
The one caveat to adding dynamic definitions is that they are available only for the life of SYSVIEW inside of CICS unless you are doing WARM starts of the product and you do a SAVE once you have the definition set up.