How to implement a rule on CMRTTHR view to kill transactions for one target group?

From the main view EZCFSSI, set the context for the PAS ssid:



Access the view CMRTTHR:



Issue EDIT on the command line to enter on edit mode:



Issue ADD to add a new Target Group definition:



Set the Target Group Definition Name and the Target(s). Leave all the thresholds blank. This ensures that no transactions running in the targets defined will be killed until we specify more details.



Press PF3 to save the new rule definition for the Target Group

The screen below shows the base defaults for the Target Group. This rule affects all the transactions for the TARGET01 target.



Now we are going to add a Child Target Transaction Group so we can specify which thresholds we wish to have. Issue ADC in the CMD column next to the new Target Group named TEST01



The Add Child command (ADC) will open the Task Kill Table Transaction Group Add/Change panel. The first part of this panel shows the base Target Group thresholds (currently blank so that any transactions on the target that we do not explicitly define will not get killed). The bottom section of the panel shows the thresholds for the Child Transaction Group. Press PF1 on the fields to show the help panels. In this example we will set the CPU Time to 500:



Press PF3 to save the child. Select the Target Group name TEST01 to confirm the threshold is defined:





We now need to add transactions to the Child Transaction Group so the system knows which transactions we want to have killed if they exceed 500 CPU.

To add transactions to the child, issue ADC in the CMD column next to Record No 1 to access the Task Kill Table Transaction Add panel:



On this example, transactions ABC1, ABC2 and ABC3 will have the threshold of 500, any other transaction will not get killed.



Issue SAVE on the command line to save all the changes.



----------------------------------------------------------------------------------------------

If you want the base rules for any and all transactions on the target(s) to be killed then you do not need to add a Child Transaction group. Simply define the threshold in the Target Group.

For example, if you want any and all transaction on target TARGET01 to be killed when they reach 200 CPU, then define the TARGET GROUP like this:

Note: By doing this we will affect ALL transactions for the target including any new transactions later defined.

-----------------------------------------------------------------------------------------------

Use the VERify command to validate the changes. More information about on:

https://docs.bmc.com/docs/bmcics73/verifying-default-and-inherited-values-for-a-target-group-and-transaction-with-cmrtthr-1097523529.html?src=search