Closed as program error.
Customer updated as below : We had an auto trouble ticketing mechanism for every TBSM alarm that is inserted at Aggregation ObjectServer pair. And for every TBSM alarm,the enrichment to be performed using Impact with Network Inventory. It was noticed that some alarms though they meet the auto trouble ticket criteria, trouble tickets are not raised because of delay in response we received. The work flow of a TBSM Alarm - initially when TBSM alarm is inserted with ImpactStatus_private value to 99. Then policy 1 acts on this alarm and updates the Summary of TBSM alarm and set the value of ImpactStatus_private to 8. Later another policy acts on this alarm and enriches fields like Locatiion, LocationCity_private etc..and finally sets the value of ImpactStatus_private to 9. But it was noticed that for alarms that missed the auto trouble ticket criteria, the ImpactStatus_private value was 8 and in the mean time a Clear alarm is generated for the alarm and later ImpactStatus_private was updated to 9 after the response is received. Note: Trouble ticket can't be raised on a Clear alarm
L3 provided a local fix to the customer which customer updated as working
When using the deviant fields property, the fields specified in the list are the ones that are ignored not the ones to compare.
A property was added to make it so that the user can set the deviant fields to the one to compare instead of the ones to ignore. The fix for this APAR is contained in the following maintenance packages: |Fix Pack | 6.1.0-TIV-NCI-FP0002
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels