Fixes are available
APAR status
Closed as new function.
Error description
Allow situations with Take Actions or with Display Item to be duperized.
Local fix
Problem summary
Allow situations with Take Actions defined or Display Item set to be duperized. Allow situations with Take Actions defined or Display Item set to qualify for the duper process. See the APAR Conclusion for more details about this new support.
Problem conclusion
With this enhancement, duper is automatically applied to situations with reflex actions and display item. No additional configuration is required. General Duper Note: ------------------- Situations are considered for the duper process only during the management server startup. Therefore, situations need to be defined with the "Run at startup" option selected to be considered for duper the next time the management server is started. Duper Situation with Take Action Note: -------------------------------------- Any situation with take action is distributed to the agent via two requests, one for situation sampling and one for the take action. The same applies for situations with take actions that are duper situations. This is an example of a message for sampling part of duper situation: KRAIRA000, Starting Enterprise situation _Z_QMQUEUES0 <200 279635,114296567> for KMQ.QMQUEUES., Producer(IRA Constructor) This is an example of the take action parts when the situation is defined to Execute the Action at the Managed System (Agent). In this scenario, the takes actions are sent as separate reqeusts: KRAIRA000, Starting Enterprise situation MQ_SIT_A_101 <200 279698,112199411> for KMQ.QMQUEUES., Producer(IRA Constructor) KRAIRA000, Starting Enterprise situation MQ_SIT_A_100 <200 279709,114296560> for KMQ.QMQUEUES., Producer(IRA Constructor) So it is correct when a situation that contains a take action is duperized to see a separate message for each take action, when the evaluation is to be done at the agent. New environment variable KMS_EVAL_REFLEX_AT_TEMS: ------------------------------------------------- If you have a large number of situations with reflex actions set in the Tivoli Enterprise Portal to Execute the Action at the Managed System (Agent), then you can set the monitoring server environment variable KMS_EVAL_REFLEX_AT_TEMS=Y in the KBBENV file to increase your level of duper optimization. Set the KMS_EVAL_REFLEX_AT_TEMS environment variable at each monitoring server in your environment to cause the evaluations of the actions to be handled by duper on the monitoring server, while the actions are still directed to the managed systems. If you want to implement this variable, your managed systems must be connected to a monitoring server in order for the actions to execute. Attention: Use the KMS_EVAL_REFLEX_AT_TEMS environment variable with caution since the agent must be connected to the management server for the action to be executed. Note: The KMS_EVAL_REFLEX_AT_TEMS variable has no affect on your situation if you have set Execute the Action at the Managing System (TEMS). The fix for this APAR is contained in the following maintenance packages: | fix pack | 6.2.3-TIV-ITM-FP0002
Temporary fix
Comments
APAR Information
APAR number
IV27435
Reported component name
TEMS
Reported component ID
5724C04MS
Reported release
623
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-09-04
Closed date
2012-09-11
Last modified date
2012-10-08
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
TEMS
Fixed component ID
5724C04MS
Applicable component levels
R623 PSY
UP
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCTLMP","label":"ITM Tivoli Enterprise Mgmt Server V6"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"623","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
08 October 2012