The Herb Garden

Thresholds can be displayed via the “Problems” screen from the “CICS Region Menu” or the CREGPRB view display.
Each threshold represents the upper limit of a range of measurable values.
The colour of a message indicates whether an informational, a warning, or a severe threshold has been exceeded.
This document explains how to set problem thresholds with the CMRPRBT macro. This macro generates a problem message threshold table.
Each table entry consists of a message number followed by the thresholds that trigger the display of informational, warning, and severe messages.

Modifying the CMRPRBT Macro

The messages
All MAINVIEW for CICS problem messages are located in the ISV.BMC.MAINVIEW.BBMLIB data set with a separate member for each message. The members are named with an ‘@’ before the message number. For example @FT043 contains information for message FT043. Only the messages listed in CMRPRBT can have their thresholds modified.
MAINVIEW for CICS issues a number of problem messages that do not require thresholds (for example, FT056 CURRENTLY AT ACTIVE MAXIMUM TASK CONDITION). These messages are not listed in CMRPRBT. The CMRPRBT default thresholds are specified in BBSAMP member CMRUPRBT.

To modify CMRPRBT, perform the following steps:

Edit sample member CMRUPRBT
in ISV.BMC.MAINVIEW.BBSAMP(CMRUPRBT) to set message thresholds.

Edit the TARGET parameter to include the CICS regions whose messages you want to set thresholds for:
TARGET=(name1,name2,...,namen, | *)
Thresholds apply to the messages generated by the CICS regions specified with the TARGET parameter. An asterisk (*) indicates that message thresholds apply to all unspecified CICS regions.
If a TARGET=* parameter is not included in CMRPRBT, the first TARGET parameter is used to set thresholds for any unspecified regions. For example, if TARGET statements are in the following order, the thresholds for CICS1 and CICS2 apply to CICS3 because it is an unspecified region:
CMRPRBT TARGET=(CICS1,CICS2),
FT033=(200,300,400),
FT034=(10,40,60),
.....
CMRPRBT TARGET=(CICSTST,CICSPROD),
FT033=(100,200,300),
FT034=(80,100,200),

Edit the FTnnn message statements to change the default message thresholds.
The format of the FTnnn statement is as follows:
FTnnn=(aaaaaa,bbbbbb,cccccc)
The variable, FTnnn, represents the message number. The values within parentheses, aaaaaa, bbbbbb, and cccccc, represent thresholds as follows:
_ aaaaaa represents a informational message threshold.
_ bbbbbb represents a warning message threshold.
_ cccccc represents a severe message threshold.
Threshold values for count messages are specified as integers.
The following example demonstrates how message thresholds are specified for counts:
FT041=(32,100,200)
_ An informational message is issued when the task uses more than 32 K of DSA.
_ A warning message is issued when the task uses more than 100 K of DSA.
_ A severe message is issued when the task uses more than 200 K of DSA.
Percent and time thresholds are expressed as integers without a decimal point. A
zero is added as the low-order number. The following example demonstrates how
message thresholds are specified for percent thresholds:
FT046=(500,750,900)
_ An informational message is issued when CICS uses more than 50.0% of CPU resources.
_ A warning message is issued when CICS uses more than 75.0% of the CPU.
_ A severe message is issued when CICS uses more than 90.0% of the CPU.

Decrease the CPU utilization of the CREGION View (optional) and the interval recorder by limiting the scope of region problem count collection.
To stop CREGION and interval recorder collection of problem counts for storage violations (FT066 and FT088), add an 'N' as the fourth parameter to their Problem Threshold Table entries for the FT066 message. An example of the MACRO parameter is as follows:
FT066=(0,10,20,N), STORAGE VIOLATIONS X
Similarly, to stop collection of problem counts for program loads (FT099), add an 'N' as the fourth parameter to the entries for the FT099 message. An example of the MACRO parameter is as follows:
FT099=(25,50,100,N), TIMES PROGRAM FETCHED X

Change the default colour (optional) for a type of message by placing the name of a colour after the equal sign in the following statements:
.
SEVERE=RED,
WARN=BLUE,
INFO=GREEN,
.
MAINVIEW for CICS supports the following colors:
_ red
_ white
_ blue
_ green

Exclude messages (optional) from being displayed with the PROBLEM service if you think they represent insignificant events:
Locate the following statements:
XTRAN=(' ',' ',' ',' ',' ',' ',' ',' ',' ',' '),
XFILE=(' ',' ',' ',' ',' ',' ',' ',' ',' ',' '),
The XTRAN and XFILE statements specify which transactions or CICS files should be excluded from appearing with the PROBLEM service, even if their thresholds are exceeded.
Enter the names of up to 10 transactions or files within the parentheses of the appropriate XTRAN or XFILE statement, and include single quotation marks around each transaction or file name and separate them with a comma. Both statements support the “+” and “*” wildcards (for example, ‘file_name1’,’file_name*’).

Assemble and link the CMRUPRBT source module. JCL from BBSAMP member CMRASM has been copied into the source module so simply submit the member.
_ CMRPRBT must be assembled and linked into BBLINK or an authorized load library that is concatenated in front of BBLINK.
_ CMRPRBT must be linked reentrant.
_ You must include the BBSAMP data set in the assembler SYSLIB concatenation.
Check the job output to make sure all steps are completed with a return code of 0

Resetting the CMRPRBT Macro
To reset the CMRPRBT table dynamically, issue the following command:
.RESET PARM CMRPRBT
You need to go to the LOG screen to issue this command.

• CICS