IV29705: TACMD CREATESIT -B DOES NOT MAINTAIN EIF SLOT INFORMATION
Fixes are available
Closed as program error.
Approver:LG Environment: zLinux system at ITM 622 FP3. Replicated on zLinux at ITM 622 FP7. Not specific to latest maintenance level. Problem Description: Abstract is sufficient in this case. Detailed Recreation Procedure: 1) created a simple Linux situation with this formula ( Process System CPU (Percent) >= 10.00) I also added a mapping of one field into the msg slot 2) I did the following commands ./tacmd login.. ./tacmd viewsit -s IBM_test_map_101 -e IBM_test_map_101.xml ./tacmd createsit -s IBM_test_map_101_new -b IBM_test_map_101 ./tacmd viewsit -s IBM_test_map_101_new -e IBM_test_map_101_new.xml A check of the original xml file shows nmp180:/opt/IBM/ITM/bin # grep MAP IBM_test_map_101.xml <MAP><![CDATA[<situation name="IBM_test_map_101" ><class name="KLZ_Base" /><slot slotName="msg" ><mappedAttributeValue name="KLZ_Process.Timestamp" /></slot></situation>]]></MAP> but a check of the cloned situation shows: nmp180:/opt/IBM/ITM/bin # grep MAP IBM_test_map_101_new.xml nmp180:/opt/IBM/ITM/bin # Related Files and Output: Some ECUREP logs. but replication is simple as above.
Use Situation Editor Create Another... to create a cloned situation under a different name. Or, create the cloned situation and add the mapping manually.
'tacmd createsit -b' does not maintain EIF slot information of the situation to be cloned.
New code added to read the EIF slot information from the base situation and replicate them for the new situation to be created. The fix for this APAR is contained in the following maintenance packages: | fix pack | 6.2.3-TIV-ITM-FP0003
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