Fixes are available
APAR status
Closed as program error.
Error description
'tacmd bulkimportsit' does not prevent a situation with an invalid 'TDST' value, from being inserted. 'tacmd createsit -i' alerts the user that the Event Destination ID is invalid - 'tacmd bulkimportsit' should do the same. Reproduction [1] ITM 6.21 IF2 on SLES (TEMS & TEPS) [2] Enable Event Forwarding for TEMS [3] Create a new Event Destination, using 'tacmd createeventdest', eg 'tacmd createeventdest -i 2 host1=falsetecserver:4567 name=test' [4] In TEPS, create a new situation. [5] On EIF tab, set Event Fowarding to the Server specified in step [4] OK to save the situation [6] Export the situation via CLI, with 'tacmd bulkexportsit' [7] Verify 'TDST' value is set in the .xml file created through 'bulkexportsit' [8] Delete event destination using cli, eg 'tacmd deleteeventdest -i 2' [9] Delete situation created in step 4 [10] Import situation using 'bulkimportsit' with -n switch, eg 'tacmd bulkimportsit -n situation.xml' [11] Verify that import worked without error to StdOut [12] Open newly imported situation in TEP Situation Editor [13] Goto EIF tab [14] Notice that 'Assigned' list is empty [15] Notice that 'Available' list contains default only [16] Click on 'Default' reciever to move to Assigned [17] Click Apply [18] Open a different situation via list on left hand side [19] Re-open test sit [20] Notice that Assigned list is empty Repeat step 9 & 10, but with 'tacmd createsit -i' instead of 'tacmd bulkimportsit' and you get a KUICCS007E message (which is good, and what should happen). bulkimportsit should report a KUICCS007E message just like createsit does.
Local fix
Problem summary
'tacmd bulkimportsit' does not prevent a situation with an invalid 'TDST' value, from being inserted. 'tacmd createsit -i' alerts the user that the Event Destination ID is invalid - 'tacmd bulkimportsit' should do the same.
Problem conclusion
Added the code to correctly manage the check of the real event servers as in tacmd createsit command The fix for this APAR is contained in the following maintenance packages: | fix pack | 6.2.1-TIV-ITM-FP0001
Temporary fix
Comments
APAR Information
APAR number
IZ54598
Reported component name
TEMS
Reported component ID
5724C04MS
Reported release
621
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-07-06
Closed date
2009-10-15
Last modified date
2009-12-11
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
R621 PSY
UP
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTFXA","label":"Tivoli Monitoring"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"621"}]
Document Information
Modified date:
04 October 2021