Customizing thresholds
You can customize threshold criteria by user, by site, or by product.
Before you begin
Workspaces reflect the status of data on the basis of threshold criteria. Each product that supports the enhanced 3270 user interface provides predefined thresholds. You can customize these thresholds to more accurately reflect your site and user criteria.
About this task
This task describes how to create and refresh customized threshold definitions using the enhanced 3270 user interface.
- User-specific
-
User-specific thresholds affect only a single user. The customized user-specific thresholds are defined in a member named user_id, which is the TSO or SAF user ID of the user.
To customize user-specific thresholds, you must create the user_id member and include only the changes that you want to make. Ideally, member user_id contains only the threshold overrides that are specific to the user and is not intended to include all threshold definitions.
If you use member user_id for custom thresholds, you must have a user profile for the same ID in the UKOBDATF data set.
- Site-wide
-
Site-wide thresholds affect all users and all products in the environment. The customized site-wide thresholds are defined in a member named CUASITE.
To customize site-wide thresholds, you must create the CUASITE member and include only the changes that you want to make. Ideally, member CUASITE contains only the site-wide threshold overrides and is not intended to include all threshold definitions.
Note: Member IBMSITE contains site-wide, product-provided threshold definitions. Member IBMSITE is used only if member CUASITE is not found. - Product-specific
-
Product-specific thresholds affect all users of a specific product. Each product provides predefined threshold definitions in member KppTHRSH of data set TKANPAR, where pp is the product code. For example, OMEGAMON for CICS has member KCPTHRSH, and OMEGAMON for z/OS has member KM5THRSH.
To customize product-specific thresholds, you must create a copy of member KppTHRSH that is a complete copy of the original predefined threshold member. You then update this copy with your changes, and it is used in place of the original predefined threshold member.
Thresholds are applied in the following order: user_id, CUASITE (or IBMSITE), KppTHRSH.
<hilev>.<rtename>.RKANPARU
. The enhanced 3270 user interface user profiles and site-customized profiles also use
members named user_id and CUASITE,
respectively; the profile members exist in the default user-profile data set
<hilev>.<rtename>.UKOBDATF.000009 ************************************************************************ 000010 * TABLE : KCPPLX * 000011 * * 000012 * PANEL ID: KCPPLXS - ENTERPRISE CICSPLEX SUMMARY * 000013 * SUBPANEL: 1 - ALL ACTIVE CICSPLEXES * 000014 ************************************************************************ 000015 IF ( OMCICS.KCPPLX.TRANRATE GT 1000/MIN OR 000016 OMCICS.KCPPLX.TRANRATE LT 100/MIN 000017 ) 000018 THEN DO 000019 STATUS ( CRITICAL 9 ) 000020 ENDDO 000021 IF ( OMCICS.KCPPLX.TRANRATE EQ 900/MIN<>1000/MIN OR 000022 OMCICS.KCPPLX.TRANRATE EQ 100/MIN<>300/MIN
After you have completed your customizations, you must refresh the threshold definitions in your environment. An administrator can dynamically refresh the site-wide and product-specific thresholds for all users using the MVS MODIFY command THRESHREFRESH; for any users that are logged on to the enhanced 3270 user interface, these changes take effect immediately and automatically. If you make any user-specific threshold customizations and are logged on to the enhanced 3270 user interface, you must use the Threshold Refresh option in the interface for the changes to take effect; this option also refreshes the site-wide and product-specific thresholds.
Complete the steps in the following procedure to customize and refresh your threshold definitions.