A fix is available
APAR status
Closed as program error.
Error description
Severity: 3 Approver:BEH Compid: 5724C04MS Tivoli Enterprise Management Server Abstract: RTEMS slow shutdown due to Sits w/ pending state updates Environment: ITM 6.30 FP1 on Windows Problem Description: When a RTEMS is shutdown, for all pending Situation 'status' changes that reside in StatusQueueManager, a Situation status update is being sent to HUB TEMS for each one. These 'Y' to 'N' or 'N' to 'Y' status updates being sent to HUB TEMS are unnecessary as the associated Situations will be stopped as a by product of RTEMS shutdown, per RTEMS sending Situation 'Stop'statuses to the HUB TEMS. If there is a slow network link between RTEMS and HUB TEMS the processing time for these unnecessary Situation status updates is prolonging the overall time required to complete shutdown of the RTEMS. The larger the number of pending Situation 'status'updates the more noticeable the processing overhead incurred by RTEMS shutdown.
Local fix
Problem summary
Remote monitoring server may be very slow to complete shutdown processing. When a remote monitoring server is shutdown, for each Situation running at remote monitoring server there may be pending 'state' events waiting to be sent to HUB monitoring server. These 'state' events would be "Y' or 'N' events. This is unnecessary data transfer overhead since every Situation running at remote monitoring server will be stopped because the remote monitoring server is shutting down, thus making the 'Y' or 'N' events obsolete. If there is a slow network link between remote monitoring server and HUB monitoring server the aggregate of data transfer time over the network plus processing time for the collection of individual events is exacerbated and in turn increases the time needed for remote monitoring server to complete shutdown.
Problem conclusion
A solution was implemented that when remote monitoring server receives a shutdown request it no longer sends 'Y' events for Sample type situations and no longer sends any 'N' events for any situations. The remote monitoring server will continue to send 'Y' events for Pure type situations. Eliminating the sending of obsolete 'state' events will provide some reduction in remote monitoring server shutdown time. Note, APAR IV67984 will provide the significant reduction in remote monitoring shutdown time. The fix for this APAR is contained in the following maintenance packages: | fix pack | 6.3.0-TIV-ITM-FP0006
Temporary fix
Comments
APAR Information
APAR number
IV67982
Reported component name
TEMS
Reported component ID
5724C04MS
Reported release
630
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-12-17
Closed date
2015-10-02
Last modified date
2015-12-10
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
R630 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":"630","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
10 December 2015