Service Task Details situation
The single predefined situation in this category monitors that OMEGAMON® is correctly configured to provide the required monitoring functions.
- CICSplex_WLM_Blocks_Usage_High
- WLM blocks usage is approaching the maximum configured level.
Use the OMEGAMON WLM Blocks Usage view on the Service Task Details workspace or the F agentname,OC STATUS,WLMBLOCKS diagnostic command to determine the peak usage that the system has experienced for either transaction or the accumulation records. Use the
KC5_WLM_BLOCKS
parameter in PARMGEN Configuration Tool to adjust the WLM Blocks parameter so the peak value of no more that 80% is ever experienced.Accumulation records are used to hold summaries for service classes. There is an accumulation record for each combination of service class, CICS region, CICSplex, and transaction ID received, as well as one extra record for each CICS region. The volume depends upon the number of service classes defined, transactions that are categorized in those service classes, and CICS regions. When this situation fires, the number of accumulations being collected is more than the defined space allows, probably because the number of regions and the number of different types of transactions being collected have been increased.
There is a direct relationship between the WLM Blocks parameter and the maximum number of accumulation records. For example, if 500 blocks results in a consistent usage of 80%, changing the value to 1000 blocks results in a usage of 40%.
Formula:
If the value of the attribute WLM_Accumulation_Data_Current_percent is greater than 70 or the value of the attribute WLM_Accumulation_Data_Peak_percent is greater than 80 then situation CICSplex_WLM_Blocks_Usage_High is true
User response: Increase the CICS OMEGAMON agent’s WLM BLOCKS parameter. WLM blocks can be increased dynamically (and thereby avoid recycling the OMEGAMON for CICS agent) by using OMEGAMON CICS WLM Modify commands to stop the WLM subtask and then restart it with new parameter values:/F jobname,OC STOP ID=WLM /F jobname,OC START ID=WLM,BLOCKS=2560
Note: If you specify only the BLOCKS parameter, WLM will be restarted using defaults for RESP and GOAL. If your CICS agent is running in its own address space, look at the KC5AGST member in the RKANCMDU library to determine what your WLM startup options are:
If you are using something other than the default startup options for RESP and GOAL, you will also need to include those on the START ID=WLM Modify command.OC START ID=WLM,BLOCKS=2560,RESP=2.00,GOAL=A
See also the CICSplex Service Task Details attribute group.