Tivoli Log File Agent, Version 6.3.0 Interim Fix 04 6.3.0-TIV-ITM_LFA-IF0004

Download Description

(C) Copyright International Business Machines Corporation 2015.
All rights reserved.

Component: Tivoli® Log File Agent,
Version 6.3.0

Component ID: 5724C04LF

Interim Fix: 0004, (6.3.0-TIV-ITM_LFA-IF0004)

Date: February 20, 2015

Contents:

1.0 General description
2.0 Problems fixed
3.0 Architecture and prerequisites
4.0 Image directory contents
5.0 Installation instructions
6.0 Additional installation information
7.0 Known problems and workarounds
8.0 Additional product information
9.0 Copyright and trademark information
10.0 Notices


1.0 General description
===============
This fix resolves the APARs and defects listed in the "Problems Fixed"
section below. This fix also includes the superseded fixes listed in
section 2.3.


2.0 Problems fixed
============
The following problems are addressed by this fix.

2.1 APARs
-------------

APAR: IV68698
Abstract: WITH JAPANESE LOCALE, BACKSLASH CHARACTER IS WRONGLY
TRANSLATED WHEN INCLUDED IN TAKE ACTION COMMAND STRING
Additional information: When an event which is detected by the agent
is output from a situation using a Take Action command, by a
redirection, etc.; a single-byte backslash character ("\") is
displayed as a double-byte "middle point" character.

The character is correctly displayed in the portal indicating
that it is correctly read and translated by the agent when
read from the monitored log file.

The problem only occurs when the attribute containing
backslash is used in a Take Action command. When the
character is read from the monitored file, it is converted
from ibm-943_P15A-2003 to UTF-8 0xC2A5 - the UTF8
representation of backslash\yen). When the take action is
performed either at the agent or the monitoring server, the
agent translates the 0xC2A5 from UTF-8 to the native CP932
which results in the 0xFCFC character code.

The problem exists on the Log File Agent version 6.3.0
Interim Fix 0003 (6.3.0-TIV-ITM_LFA-IF0003) and earlier, with
Japanese locale. It can occur on Windows and UNIX platforms.

Problem Determination: With the following trace enabled for
the LO agent:
KBB_RAS1= ERROR (UNIT:logmonitor all)(UNIT:kum0nget all)
(UNIT:kumprmfr ALL) (UNIT:task ALL)
the agent log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
contains trace entries similar to the following:
- - -
...
(54B982FE.000A-B30:kum0nget.c,411,"TranslateStringToUTF8") Entry
(54B982FE.000B-B30:kum0nget.c,419,"TranslateStringToUTF8")
Converting string buffer from ibm-943_P15A-2003 to UTF-8
...
(54B982FE.000F-B30:kumprmfr.c,449,"KUMP_ReadMonitorFileUnicodeRe
cord") <0x5FD6678,0x19>
+54B982FE.000F 00000000 2045206C 696E6461 C2A56C6D
6E6F61C2 .E.lmnoa..lmnoa. !!!!
+54B982FE.000F 00000010 A56C6D6E 6F61200D 0A
...
...
(54B982FE.00BE-F20:tasklibrary.cpp,1531,"ConvertCommandToLocal")
Converting UTF-8 command to codepage 932
...
(54B982FE.00DC-F20:tasklibrary.cpp,864,"executeTaskRequest")
Executing task cmd /c "echo lindaüülindaüülinda
>>c:\output.sit"


APAR: IV68574
Abstract: IN TAKEACTION, COMMAND OF MULTI-BYTE CHARACTERS WHICH HAVE 0XBA
OR 0XBB IS TRANSLATED TO LOCAL CODE PAGE INCORRECTLY.
Additional information: In takeAction processing, multi-byte
characters 0x82BA or 0x82BB in a command are translated to
local code page incorrectly. They are incorrectly replaced
with "[" and "]", respectively.

The problem exists on Log File Agent v6.3.0 Interim Fix 0003
(6.3.0-TIV-ITM_LFA-IF0003) and earlier releases and is
platform independent.

Problem Determination: With the following trace enabled for
the LO agent:
KBB_RAS1= ERROR (UNIT:Logmonitor ALL) (UNIT:Kumprmfr ALL)
(UNIT:kum0nget ALL) (UNIT:Task ALL)
the agent log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
contains trace entries similar to the following:
- - -
...
...:kum0nget.c,419,"TranslateStringToUTF8") Converting string
buffer from ibm-943_P15A-2003 to UTF-8
...:kum0nget.c,482,"TranslateStringToUTF8") Buffersize 31158
bytes; Translated size 4 ; Copied 31158 characters readBuffer
1113EE3B0
...:kum0nget.c,498,"TranslateStringToUTF8") Exit: 0x113EE3B0
...:kum0nget.c,397,"KUM0_Fgets") Exit: 0x113EE3B0
...:kumprmfr.c,449,"KUMP_ReadMonitorFileUnicodeRecord")
<0x1113EE3B0,0x4> ?
+5492C8B8.000A 00000000 E3819D0A
... !!!!!!
...
<< The event is submitted to EIF - it still looks correct >>
(5492C8B8.005F-1B:logmonitorqueryclass.cpp,2433,"LogMonitorQuery
Class::setInstanceData") Submitting EIF event:
+5492C8B8.005F SOTEST_Event;C1='ã ';
E89 << hex character values>>
31D

...
...
...:tasklibrary.cpp,1225,"actionCallback") Received Take
action. Cmd=<print -r ' ã '>>/LFA/49806/sotestout.txt >,
User=<sysadmin>
...
...
...:tasklibrary.cpp,1531,"ConvertCommandToLocal") Converting
UTF-8 command to codepage 932
...:tasklibrary.cpp,1554,"ConvertCommandToLocal") Exit: 0x10F4BBF0
...
...
<< However when it is translated back from UTF-8 to codepage 943
it becomes incorrect:>>
...:tasklibrary.cpp,749,"executeTaskRequest") Entry
...:tasklibrary.cpp,791,"executeTaskRequest")
taskInfo.name = print
...:tasklibrary.cpp,841,"executeTaskRequest") Did
not find Task name 'print'. Going to run 'system' on the
request print -r ' ?]
'>>/LFA/49806/sotestout.txt .
...
- - -

APAR: IV68490
Abstract: ALL EVENTS ARE NOT DETECTED AND SENT AS EXPECTED WHEN
TRANSLATING FROM A MULTI-BYTE CODE PAGE
Additional information: All events are not matched and sent to the
event receiver. The events that are received might contain
garbled characters. Close examination of the agent log with
tracing enabled, shows that parts of the events or lines are
overwritten.

This only occurs when translating the data from a multi-byte
code page to UTF-8 and the conversion fails. The conversion
fails because the agent was unable to read all the bytes
required for a complete character into its buffer. This might
occur if a group of messages are sent or when a message
exceeds the maximum event size (EventMaxSize). Increasing the
EventMaxSize might produce different results.

The problem exists on the following Log File Agent versions:
- 6.3.0 interim fix 0003 and earlier
- 6.2.3.2 and later
- 6.2.2.4 Interim Fix 07 and later.
It is platform independent.

Problem Determination: With the following trace enabled for
the LO agent:
KBB_RAS1= ERROR (UNIT:logmonitor all)(UNIT:kum0nget all)
(UNIT:kumprmfr all)
the agent log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log might
contain these error indicators:
"partial data", "RESIDUAL" , or "*****Error: u_strFromUTF8
failed for string".

Trace entries are similar to the following where the
translation buffer ends 0x1A and contains partial data.
- - -
...
...:kum0nget.c,411,"TranslateStringToUTF8") Entry
...:kum0nget.c,417,"TranslateStringToUTF8") translateBuffer
allocated 865 bytes at 43075E0
...:kum0nget.c,419,"TranslateStringToUTF8") Converting string
buffer from ibm-943_P15A-2003 to UTF-8
...:kum0nget.c,467,"TranslateStringToUTF8") Input buffer
43E31C3 of length 288 when translated into 43075E0 of
length 293 has partial data
...:kum0nget.c,469,"TranslateStringToUTF8") <0x43E31C3,0x120>
+... 00000000 23232323 3C323031 342F3132 2F303120
. . .
. . .
+... 00000100 3C313431 37343039 35343939 36383E20
<1417409549968>.
+... 00000110 3C424541 2D303030 3030303E 203CE383
<BEA-000000>.<..
+... 00000120 A1E38388 1A <---
..... !!

<< Note: When the failure occurs, the last three bytes of the
translated data are 0xEF 0xBF0 0xBD or the last byte is a 0x1A.>>

...:kum0nget.c,479,"TranslateStringToUTF8") Buffersize
865 bytes; Translated size 292; Copied 865 characters to
readBuffer 43E31C3 RESIDUAL 1 <----
!!!!!!!!!!
...
(...:kum0regx.c,286,"KUM0_IsRegExPatternMatch")
*****Error:u_strFromUTF8 failed for string
...
- - -

APAR: IV67737
Abstract: DUPLICATE EVENTS SENT BECAUSE LOG DETECTED AS SWITCHED OR
RE-CREATED
Additional information: After applying Log File Agent v6.3 IF0003
(6.3.0-TIV-ITM_LFA-IF0003) on AIX and Linux, with
NumEventsToCatchUp=-1 set in the conf file, the monitored log
is incorrectly detected as re-created or switched. The
monitored log is re-read from the beginning, resulting in
duplicate events.

This issue occurs on AIX, Linux. It does not exist on Windows
operating systems.

Problem Determination: With a mininum of the following trace
enabled for the LO agent:
KBB_RAS1= ERROR (UNIT:kumpfdp2 ALL) , the agent RAS1 log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log shows
trace points similar to the following:
- - -
...
...:kumpfdp2.c,778,"DoFileTailRestart") Retrieved old monitor
filename </tmp/test_lfa.txt> creation time <1411741772> last
modification time <1411741772> size <699>
...
...:kumpfdp2.c,792,"DoFileTailRestart") Comparing creation
time <1411743260> last modification time <1411743260> size <758>
...:kumpfdp2.c,816,"DoFileTailRestart") Note: Monitorfile
/tmp/test_lfa.txt has been switched or re-created, updating
restart file
</opt/IBM/ITM/logs/LO_LFA01_LogfileEvents_LogfileEvents_tivoli85
.rst>
...:kumpfdp2.c,834,"DoFileTailRestart") Per TailRestartFromTop
parameter, restarting file monitoring from beginning of file
</tmp/test_lfa.txt>
...
- - -

The file, listed above, is detected as re-recreated based on the
file information returned by the operating system:
creation time modification time size
last <1411741772> <1411741772> <699>
current <1411743260> <1411743260 > <758>

APAR: IV67708
Abstract: WINDOWS EVENT LOG EVENTS WITH %N RESULTS IN A MESSAGE OF
"NONE"
Additional information: The event msg field or slot might contain
a value of "None", when a Windows event log message contains
a %n where n is a number in the event description field.
If the %n is not substituted, the Microsoft EvtFormatMessage
API returns ERROR_EVT_UNRESOLVED_VALUE_INSERT (15029) which
the agent treats as an error. As a result of the error, the
agent discards the event description and substitutes "None".

Problem Determination: With a mininum of the following trace
enabled for the LO agent:
KBB_RAS1= ERROR (UNIT:WinLogQuery ALL), the agent log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log shows
the "15029" error:
- - -
...
...:winlogqueryclass.cpp,932,"renderEvent") Rendering
message for event
...:winlogqueryclass.cpp,594,"renderEventString") Entry
...:winlogqueryclass.cpp,629,"renderEventString")
Retrieved metadata for provider MYEVENTSOURCE from hashmap
...:winlogqueryclass.cpp,676,"renderEventString")
EvtFormatMessage failed, error = 15029, evt handle = 0x00000002
...:winlogqueryclass.cpp,705,"renderEventString") Exit: 0x0
...
- - -

APAR: IV65900
Abstract: LOG FILE AGENT WINDOWS EVENT LOG EVENT ID NOT DETECTED
PROPERLY
Additional information: When the Windows Event log event ID is zero,
Log File Agent shows a random event ID.

Problem Determination: With a mininum of the following trace
enabled for the LO agent:
KBB_RAS1=ERROR (UNIT:WinLogQuery ALL)
the agent log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
contains the following trace point that shows an error
ocurred:
...:winlogqueryclass.cpp,799,"renderEvent") Error retrieving EventId

APAR: IV65500
Abstract: PROCESS PRIORITY NOT WORKING WITH SUBNODES
Additional information: The agent Process Priority Class setting
does not work with subnodes when it is enabled through the
autodiscovery option.

During the agent configuration, when the conf file and format
file are not specified and only the autodiscovery directory
and Process Priority Class are set, the Process Priority is not
set properly for the agent. It takes the default value.

APAR: IV64093
Abstract: EXCEPTION ACCESS VIOLATION WHEN EVENT EXCEEDS MAXIMUM
EVENT SIZE
Additional information: The kloagent process may terminate with an
Exception 0xC0000005 (ACCESS_VIOLATION), when the size of an
event exceeds the maximum event size (EventMaxSize) and is
truncated. The LO agent instance unexpectedly stops and goes
offline.

The crash occurs when the truncation occurs on a boundary
condition, and the event is truncated at a single quote and
has no ending semi-colon. It only occurs in the mapping of
the attribute slots to CustomSlots when sending events to IBM
Tivoli Monitoring from either a Windows event log or a file.

Problem Determination: With a mininum of the following trace
enabled for the LO agent:
KBB_RAS1= ERROR (UNIT:LogMonitorQuery ALL) (UNIT:WinLogQuery
ALL) (UNIT:kum0regx ALL)
the agent log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
contains the following trace points that show the size and
data of the incoming event:
...
...::winlogquerylist.cpp,1134,"writeEventDataToPipe")
Writing event of length ###### to pipe:
<contents of the log entry / event>
...:winlogquerylist.cpp,1145,"writeEventDataToPipe")
Node <.fmt stanza> wrote event to pipe for event log <logname>,
event size = XXXXX , bytes written = YYYYY

The following trace shows that the overall event exceeds
EventMaxSize and will be truncated. The '16384 bytes' is the
ventMaxSize the agent is using.
...
...:kum0regx.c,1152,"KUM0_PerformStringReplace")
Warning: Replacement string size ZZZZZ for attribute EIFEvent
larger than available buffer, only copied 16384 bytes to ....

The following trace points show the access violation:
...:logmonitorqueryclass.cpp,1812,"LogMonitorQueryClass:
:getSlotAttrAndValue") Entry
...:logmonitorqueryclass.cpp,1823,"LogMonitorQueryClass:
:getSlotAttrAndValue") No ; at end, <slotname>=' must be last
slot
...
...:kumpxtrt.c,51,"KUMP_PerformDataCallback")
***************************************************************
...:kumpxtrt.c,52,"KUMP_PerformDataCallback")
***** Data Callback Execution Exception Handler *****
...:kumpxtrt.c,56,"KUMP_PerformDataCallback")
***** Data Callback Function - EXCEPTION_ACCESS_VIOLATION *****
...:kumpxtrt.c,62,"KUMP_PerformDataCallback")
***************************************************************
...:kumpxtrt.c,65,"KUMP_PerformDataCallback") Exit: 0x0

Note: These entries might not be at the end of the log.
There will not be the corresponding exit trace point:
"LogMonitorQueryClass::getSlotAttrAndValue") Exit

See the APAR text for the .RAS file call stack information.

APAR: IV63704
Abstract: HEAVY WINDOWS EVENT LOG LOAD CAUSES DELAYS AND THE
APPEARANCE OF HANGS
Additional information: A heavy Windows event log throughput causes
delays in the events being displayed on the portal.
For example: when sending 1000 events per second per thread,
on 4 threads, the delay in seeing the events on the portal
might be as much as 30 minutes. The delay increases as the
PollInterval increases.

The agent might also appear to hang if too many duplicate
Windows Event log messages are received.

Problem Determination: With a mininum of the following trace
enabled for the LO agent:
KBB_RAS1: ERROR (UNIT: WinLogQueryList ALL) (UNIT:kum0nget ALL)
(UNIT:kumpfdp6 FLOW DETAIL)
the agent log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
shows that the agent is continuing to monitor for incoming
events but no new events are received.
- - -
...
...:winlogquerylist.cpp,1143,"writeEventDataToPipe") Records
written to pipe n writeResult=1
< where n is the number of events written to pipe >
...
...
< And the following sequence repeatedly even though new events are
being sent. >
...:kumpfdp6.c,162,"WaitUntilNextSampleTime") >>>>>
WaitForSingleObject returned 258 for WaitFileHandle @78
...:kumpfdp6.c,233,"WaitUntilNextSampleTime") Exit: 0x1
...:kum0nget.c,122,"KUM0_Fgets") Entry
...:kum0nget.c,136,"KUM0_Fgets") read / actual BufferSize =
64146 / 192438, encoding = ibm-5348_P100-1997, convertToUTF8 = 1
...:kum0nget.c,308,"KUM0_Fgets") Using fgets() to get string
from file
...:kum0nget.c,355,"KUM0_Fgets") Pipe read returned no data
setting EOF
...:kum0nget.c,399,"KUM0_Fgets") Exit: 0x0
...
- - -

APAR: IV21752
Abstract: EIF: ERROR CODE 67 IS NOT HANDLED WHILE SENDING EVENTS
Additional information: If Error code 67 (Connection is broken) is
seen while sending events to the Event Integration Facility
(EIF) receiver, then the EIF sender ignores it and keeps
sending events forward, even though the events are not being
received by the EIF receiver.

This APAR is included in this fix for the Log File Agent on
Windows systems only. For UNIX/Linux systems, the fix is
included in IBM Tivoli Monitoring Shared Libraries (TEMA)
component of IBM Tivoli Monitoring version 6.2.3 Fix Pack 02
or later. You must install the Shared Libraries (ax) component
separately from the agent.

2.2 Defects
--------------
None.

2.3 Enhancements
------------------
Enhancement: 212595
Abstract: Implement AESnnn-CTR ciphers for remote logs

2.3 Superseded fixes
-------------------------
6.3.0-TIV-ITM_LFA-IF0003
6.3.0-TIV-ITM_LFA-IF0002
6.3.0-TIV-ITM_LFA-IF0001

2.4 APARs and defects included from superseded fixes
---------------------------------------------------------------

6.3.0-TIV-ITM_LFA-IF0003
------------------------

APAR: IV60491
Abstract: SELINUX AUDIT LOG MESSAGES GENERATED WHEN USING IPV6 WITH
LOG AGENT
Additional information: On Log File Agent v6.3 and prior releases,
running the agent on a Security-Enhanced Linux (SELinux)
system using IPv6 with the SELinux security policy set to
"enforcing" generates audit messages. The messages in the
SELinux audit log /var/log/audit/audit.log are similar
to the following where <hostname> is the system the agent is
running on:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
type=AVC msg=audit(1389964628.602:213): avc: denied { write }
for pid=8121 comm="ifconfig" path="/opt/IBM/ITM/auditlogs/itm.
<hostname>_lz_audit.log" dev=dm-5 ino=4660
scontext=system_u:system_r: ifconfig_t:s0
tcontext=system_u:object_r:usr_t:s0 tclass=file
type=AVC msg=audit(1389964628.613:214): avc: denied { write }
for pid=8126 comm="ifconfig"
path="/opt/IBM/ITM/logs/<hostname>_lz_klzagent_52d92647-01.log"
dev=dm-5 ino=5066 scontext=system_u:system_r:ifconfig_t:s0
tcontext=system_u: object_r:usr_t:s0 tclass=file
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

APAR: IV60333
Abstract: EVENTS FROM WINDOWS EVENT LOG ARE INTERMITTENTLY NOT
DETECTED.
Additional information: Windows Event Log events are
intermittently not detected and sent. With the UnmatchLog
parameter specified, the event is also not saved in the
UnmatchLog file. In previous occurrences, the missing event
matches one of the format expressions and is sent. With
tracing set as described below, after the initial rendering
of the Windows Event Log event is seen in the agent log,
there are no occurrences of the event in the log.

This is more likely to occur when monitoring more than one
Windows Event Log (for example: Application, Security,
System, etc).

This problem occurs on Windows systems with Log File Agent
version 6.2.3.2 and 6.3.

APAR: IV59814
Abstract:BLANK ARCFOUR ALGORITHM CAUSES JAVA CORE WITH REMOTE LOG
FILE MONITORING
Additional information: The Log File Agent v6.3.0 might create Java®
cores when attempting to use the Remote Log File monitoring
feature which relies on SSH. The Java core is the result of a
blank("") arcfour algorithm name for the cipher.
The problem was initially seen on Linux, but is platform
independent.

With a minimum of KBB_RAS1: ERROR (UNIT:kex ALL), the agent
log <hostname>_lo_<instance>_kloagent_<timestamp>.log
ends with trace entries similar to the following:
- - -
...
(53444D90.04B8-40:kex.c,1880,"libssh2_kex_exchange") Entry
(53444D90.04B9-40:kex.c,1030,"kexinit") Entry
- - -

APAR: IV42315
Abstract: NUMEVENTSTOCATCHUP=-1 DOES NOT DETECT WHEN THE FILE HAS
BEEN REPLACED
Additional information: On restart of the Log FiLe agent, when the
configuration option NumEventsToCatchup is set to "-1", the
agent does not detect that a monitored file has been replaced
with a smaller file. The monitored file is not processed until
the file reaches the size maintained in the restart file. It
should result in the file being read from the beginning.

6.3.0-TIV-ITM_LFA-IF0002
------------------------

APAR: IV57736
Abstract: LOG FILE AGENT MAY CORE, CRASH ON HP-UX WHEN
NUMEVENTSTOCATCHUP IS USED.
Additional information: On HP-UX, when the configuration option
NumEventsToCatchUp is set to a value other than zero, the
agent might core. The problem occurs on Log File Agent v6.3.

The core might show the following:
Core was generated by ´kloagent'.
Program terminated with signal 11, Segmentation fault.
SEGV_MAPERR - Address not mapped to object
........
(gdb) where
#0 0xc000000010a30320:0 in UpdateRestartFileBaseFunction () at
kumpfdp2.c:427
#1 0xc000000010a32760:0 in UpdateRestartFileWithStats () at
kumpfdp2.c:553
#2 0xc000000010a3d970:0 in DoFileTailRestart () at
kumpfdp2.c:893
#3 0xc000000010a90af0:0 in KUMP_FileServer () at kumpfile.c:23
#4 0xc000000010b8eee0:0 in Task () at kumptask.c:35
#5 0xc0000000000fb140:0 in __pthread_bound_body+0x190 ()
from /usr/lib/hpux64/libpthread.so.1
........

With a minimum of "KBB_RAS1: ERROR (UNIT: kumpfdp2 ALL)
tracing, the agent log
<hostname>_lo_<instance>_kloagent_<timestamp>.log ends with
trace entries similar to the following:
- - -
...
...:kumpfdp2.c,173,"KUMP_ParseSingleRestartLine") Parsing
RecPtr 6000000000736F4F <735>
...:kumpfdp2.c,1250,"KUMP_ParseNumericString") Unsuccessfully
parsed <NULL> to value 735
...:kumpfdp2.c,200,"KUMP_ParseSingleRestartLine") Error: parsed
location <NULL> file <735> creation <NULL> modification <NULL>
size <NULL> with RecPtr 6000000000736F53
...:kumpfdp2.c,427,"UpdateRestartFileBaseFunction") Note:
Required fields missing from restart file </opt/IBM/ITM/logs/L
O_default_LogfileEvents_hpia5.rst>
...:kumpfdp2.c,173,"KUMP_ParseSingleRestartLine") Parsing
RecPtr 6000000000736F53 <;>
...:kumpfdp2.c,200,"KUMP_ParseSingleRestartLine") Error: parsed
location <NULL> file <NULL> creation <NULL> modification
<NULL> size <NULL> with RecPtr 5FFFFFFFA0736F52Page 34 of 35
...:kumpfdp2.c,427,"UpdateRestartFileBaseFunction") Note:
Required fields missing from restart file
</opt/IBM/ITM/logs/LO_default_LogfileEvents_hpia5.rst>
- - -

APAR: IV56299
Abstract: A PERCENT SIGN (%) LITERAL IS NOT SUPPORTED IN FORMAT
STATEMENT
Additional information: When a percent sign (%) or a percent sign
(%) followed by a literal other than the valid variables of s,
t, n, is used in a FORMAT statement, it results in an "illegal
variable" message and an incorrect regular expression. As a
result, the record does not match as expected.

For example:
FORMAT 43866_Class10
43866_10 %s % %s*
. . .

or

FORMAT 43866_30
%t %s %MIDDLEWR: %s
. . .

With KBB_RAS1: ERROR, the the agent log
<hostname>_lo_<instance>_kloagent_<timestamp>.log contains
trace entries similar to the following:
- - -
...
(5317981A.0002-12E0:lfaconfig.cpp,1042,"generateFormatFilter")
Format
for class 43866_Class10 contains illegal variable "%" in format
expression "43866_10 %s % %s*"
(5317981A.0003-12E0:lfaconfig.cpp,1045,"generateFormatFilter")
Variable
of type not recognized
...
- - -

This problem occurs on Log File Agent v6.3 and prior releases.
It is platform independent.

APAR: IV54710
Abstract: WINDOWS EVENT LOG NOT MONITORED ON SOME WINDOWS 2012
SYSTEMS AFTER INSTALLING 6.3.0-TIV-ITM_LFA-IF0001
Additional information: On some Windows® 2012 systems, after
installing Log File Agent v6.3 interim fix 0001
(6.3.0-TIV-ITM_LFA-IF001), Windows Event Log events are no
longer monitored. The Data Collection Status workspace shows
File Status: "231".

With a minimum of "KBB_RAS1: ERROR tracing, the agent log
<hostname>_lo_<instance>_kloagent_<timestamp>.log contains
trace entries similar to the following:
- - -
...
...:kum0fdp0.c,162,"KUM0_DynamicFileOpen")
fopen(\\.\pipe\KLO_gail_LogfileEvents_evl(System), rb) returned
NULL errno 231 'Unknown error'
...
- - -

APAR: IV53803
Abstract: TACMD ADDSYSTEM OF LO AGENT FAILS WITH
6.3.0-TIV-ITM_LFA-IF0001
Additional information: On Tivoli Enterprise Monitoring Server
v6.2.3 and beyond, when both the Log File Agent v6.3 (CIGM6ML)
and the interim fix (6.3.0-TIV-ITM_LFA-IF0001) are in the
depot, "tacmd AddSystem" fails because the interim fix
does not have a pre-requisite for LO version 06.30.00. The
agent is not pushed to the endpoint. This only occurs with
UNIX system targets.

APAR: IV53568
Abstract: ON WINDOWS FOR NUMEVENTSTOCATCHUP=-1 CREATES MULTIPLE
ENTRIES FOR EACH LOGS IN .RST AND MISSES EVENTS
Additional information: If NumEventsToCatchUp=-1, the restart (.rst)
file should be continuously updated. This file should contain
the name of each log being monitored along with the last
position read from the log. There should only be one line for
each monitored log file. However, instead of replacing the
line as it should, a new row is added. As a result, it is not
able to resume at the file position it was at when the agent
was stopped and events that occurred while the agent was
stopped are missed.

CPU performance issues might result from the excess processing
of the restart file.

APAR: IV52833
Abstract: SOME LOG LINES WRITTEN IN SEPARATE PIECES ARE INTERMITTENTLY
NOT SENT AS EVENTS
Additional information: On Windows® systems, some single lines
written to the monitored file in separate pieces are not sent
and do not appear in the UnmatchLog, if one was specified.
This might occur intermittently, when lines are written in
multiple parts, particularly on Windows systems.

With a minimum of KBB_RAS1: ERROR, the agent log
<hostname>_lo_<instance>_kloagent_<timestamp>.log contains a
trace entry similar to the following:
- - -
...:kum0mpbc.c,50,"KUM0_MoveStringPointerByChar")
***** Input string is NULL
- - -

APAR: IV52411
Abstract: MULTI-LINE *DISCARD* FORMAT FILTER INTERMITTENTLY ALLOWS
RECORDS TO ESCAPE FILTER AND SHOWS UP IN THE PORTAL.
Additional information: A multi-line *DISCARD* format filter
intermittently allows records to escape the filter and shows
up in the portal.

In addition, the handling of the end of the file (EOF) with
saved data from a previous read is not handled correctly.
This allows multi-line records which are split by EOF to
escape. The agent is not correctly retrying its read attempts
when it has a partial buffer and hits the EOF logic.

With a minimum of KBB_RAS1 with (UNIT:kum ALL) the agent log
<hostname>_lo_<instance>_kloagent_<timestamp>.log contains
trace entries similar to the following:
- - -
. . .
(523B46FE.06DD-12:kum0regx.c,353,"KUM0_IsRegExPatternMatch")
Exit: 0x0
(523B46FE.06DE-12:kumpcapf.c,548,"KUMP_CheckAttributesPassFilter
s") Data <Sep 19 12:48:27 gisdev scsi: [ID 107833 kern.warning]
WARNING: /scsi_vhci/ssd@g600601602d301e0002f28a3e1ff9e111
(ssd63):
+523B46FE.06DE > AttrName <EIFEvent> failed MatchRegEx filter
1: <()^(.*Error for Command.*)\r?\n(.*)\r?\n(.*)\r?\n(.*)\r?\n
(.*asymmetric.*)()>
. . .
- - -

6.3.0-TIV-ITM_LFA-IF0001
------------------------

APAR: IV48040
Abstract: LOG FILE AGENT PROCESSING WINDOWS EVENT WHICH IS GREATER
THAN 64K CAUSES THE AGENT TO LOOP AND NOT PROCESS ANY MORE
EVENTS
Additional information: There were three issues found:
1)Event buffer size was limited to 64K. The event buffer
size is increased to 128K. A WARNING message is also issued
if an event exceeds the buffer size.

2)When the record is not processed because the buffer is too
small, the current event pointer is not incremented. On the
next pass, the same too-large event is read again, which
fails again and no more events are processed.

3)When numEventsToCatchUp is set to a value larger than the
number of records in the event log, the record number to read
is calculated incorrectly.

APAR: IV45784
Abstract: FILES CREATED AFTER KLO AGENT IS STARTED ARE NOT MONITORED
Additional information: On a Windows® system, if the monitored file
does not exist when the agent is started, the file is not
monitored after it is created. There might not be an entry for
the non-existent file in the Monitored File Status in the Data
Collection Status workspace.

The agent agent must be re-started to recognize the file or
the file must exist when the agent is started.

With a minimum of KBB_RAS1: ERROR, the agent log
<hostname>_lo_<instance>_kloagent_<timestamp>.log contains
trace entries similar to the following:
- - -
...
...:kumpwfrm.c,261,"KUMP_WaitFileReadyForMonitor") ***
Unable to open file local file <filename>, Errno: 0,
ErrorText: No error, NO retry. Exiting
...:kumpfdp5.c,231,"CheckFileExistAndReady") *** File
C:/lo/43866/43866.log -- initial monitoring setup failed
<timestamp>:kumpfile.c,891,"KUMP_FileServer") >>>>> DP file
server ThreadID F04 ended for local file C:/lo/43866/43866.log
...
- - -

APAR: IV42745
Abstract: SOME LINES WRITTEN IN PIECES ARE UNMATCHED AND PARTIALLY
DISCARDED
Additional information: When a single line is written to the
monitored file in separate pieces, sometimes the line does
not match and is not sent as an event. This is because the
latter or subsequent piece of the line is written to the same
location in the internal read buffer and overwrites the
initial piece of the line. The resulting partial line does
not match the formats and is sent to the UnmatchLog, if one
was specified in the configuration file. This might occur
intermittently when lines are written in multiple parts,
particularly on Windows systems.

With a minimum of KBB_RAS1: ERROR (UNIT:kumprmfr ALL), the
agent log <hostname>_lo_<instance>_kloagent_<timestamp>.log
contains trace entries similar to the following:
- - -
...
...:kumprmfr.c,1015,"KUMP_ReadMonitorFileUnicodeRecord")
SavedRec 51A6A58 14 <job6 started: >
...
...:kumprmfr.c,412,"KUMP_ReadMonitorFileUnicodeRecord")
<0x51A6A58,0x56> 4+5187EED2.026F 00000000 362F362F
32303133 2036363A 3636200D 6/6/2013.66:66..
...
- - -
The second part of line is written to the same location in
the buffer, in the above example 0x51A6A58, overwriting the
first part of the line.

APAR: IV42699
Abstract: LAST MATCHING LINE OF LOG IS NOT IMMEDIATELY SENT AS A
MATCHING EVENT
Additional information: With record patterns that span multiple
lines (RECORDSET patterns), the last matching line of a
monitored file is not immediately sent as an event and it
does not show up in the UnmatchLog, if one was specified.
The amount of wait time till the event is actually sent is a
factor of the PollInterval.

With a minimum of KBB_RAS1: ERROR (UNIT:kumprmfr ALL)
(UNIT:kumpfdp ALL), the agent log
<hostname>_lo_<instance>_kloagent_<timestamp>.log contains
trace entries similar to the following with the default
PollInterval of 5:
- - -
...
...:kumpfdp3.c,117,"OpenFileForMonitor") Assigned
RecordSetMaxWait = 5 seconds
...
...:kumprmfr.c,1090,"KUMP_ReadMonitorFileUnicodeRecord")
Waiting for RECORDSET end delimiter, RecordSetWaitCount 1
MaxRecordSetWait limit 100
...:kumprmfr.c,1090,"KUMP_ReadMonitorFileUnicodeRecord")
Waiting for RECORDSET end delimiter, RecordSetWaitCount 2
MaxRecordSetWait limit 100
...
...:kumprmfr.c,1090,"KUMP_ReadMonitorFileUnicodeRecord")
Waiting for RECORDSET end delimiter, RecordSetWaitCount 99
MaxRecordSetWait limit 100
...
- - -

APAR: IV41215
Abstract: BRACKET { IN FORMAT RESULTS IN LOAD METAFILE EXECUTION
EXCEPTION
Additional information: When an opening { bracket is used without a
closing bracket } in a FORMAT statement of the format file,
the agent log ends with a "Load Metafile Function -
EXCEPTION_ACCESS_VIOLATION" on agent start-up.
The agent process is still running but it is waiting for
initialization to complete successfully and is not monitoring.
The Data collection status Error Code is "No ERROR" but there
is no entry in the Monitored File Status for the monitored
file. This problem is platform independent.

With a minimum of "KBB_RAS1: ERROR tracing, the agent log
<hostname>_lo_<instance>_kloagent_<timestamp>.log contains
trace entries similar to the following:
- - -
...
...:kumplmet.c,204,"KUMP_LoadMetafile")
***************************************************************
...::kumplmet.c,205,"KUMP_LoadMetafile") ***** Load Metafile
Execution Exception Handler *****
...:kumplmet.c,209,"KUMP_LoadMetafile") ***** Load Metafile
Function - EXCEPTION_ACCESS_VIOLATION *****
...:kumplmet.c,215,"KUMP_LoadMetafile")
****************************************************************
...:logmonitorqueryclass.cpp,4031,"LogMonitorQueryClass:
:completReset") Table LogfileEvents still waiting for kum to
initialize after 30 seconds
...
- - -

APAR: IV39967
Abstract: RESTORED FILE IS NOT MONITORED AFTER CONF/FMT FILES
MODIFIED
Additional information: A restored log file is no longer monitored
and no new events are processed, when the sequence of all the
following events occur:
a) update the conf or fmt file to trigger reset processing,
b) remove the file, for example via un-mount, rename, delete,
move
c) wait for the 'File does not exist' status
d) restore the file.
The Data Collection workspace continues to show a File Status
of "FILE DOES NOT EXIST".

If the reset process (step a) is not triggered and only the
file is removed, the file is re-discovered properly. If only
the reset process (step a) is triggered, it also continues to
function properly.
Note: When the file is re-discovered after it is restored, it
is read from the beginning as a new file. This is not new
behavior with this APAR.

The root cause of this problem occurs on LFA v6.3, but the log
file is monitored when the file is restored.

APAR: IV37051
Abstract: EVENTS INTERMITTENTLY NOT MATCHED WHEN LINE WRITTEN IN
PIECES
Additional information: When an application writes only part of the
line and later writes the remainder of the line, the line
intermittently matches as an event with no changes to the fmt
file. This occurs more prevalently on Windows systems because
the operating system notifies the agent when the file has
changed. When the first part of the line is written, the agent
is notified but the partial line does not match any formats.
When the second part of the line is written, the agent is
notified again but the remainder of the line does not match
any formats. The two pieces of the line are treated as two
lines, neither of which match and both pieces are written as
two lines to the UnmatchLog, if one is configured.

Defect: 207998
Abstract: Agent does not continue to retry on remote log, when
RC -3, because errno is zero.
Additional information: When monitoring remote log files where the
connection breaks; for example, the remote system shuts down
or a network outage, the agent does not continually try
to re-establish the connection. The remote file is not
monitored. The Monitored File Status might not show a row
for the file.

With a minimum of "KBB_RAS1: ERROR tracing, the agent log
<hostname>_lo_<instance>_kloagent_<timestamp>.log contains
trace entries similar to the following:
- - -
...:session.c,243,"banner_send") Unable to send the banner
...:session.c,245,"banner_send") -3 - Error sending banner
to remote host
...:session.c,691,"session_startup") -3 - Error sending banner
to remote host
...:kum0sshlib.c,1227,"ssh_session_connect") Failed to
establish an SSH connection in 0 seconds for remote
root@mypia.tivlab.austin.ibm.com:22
/opt/IBM/ITM/logs/^mypia_ux_kuxagent_.*\.log$
mypia.ibm.com:22 socket 25 rc -3 errno 17 :
LIBSSH2_ERROR_BANNER_SEND
...
- - -

Defect: 206531
Abstract: Failed to load GSKit library
Additional information: When both GSKit version 7 and 8 are
installed on the same agent machine, either because of two
IBM Tivoli Monitoring installs, or some other product that
put a GSKit into the system /usr/lib directory, the wrong
version of the library is loaded and the GSKit
initialization fails. This problem has only been seen on
Linux®.

Defect: 205184
Abstract: Improve handling of files on re-mounted file systems

Defect: 204120
Abstract: Log agent crashes on Solaris due to mis-aligned integer
Additional information: Agent crashes in KUMP_DoDPdataToDCH when it
formats data from a buffer into integers and other formats,
due to a copy of an odd-aligned integer.

Defect: 203012
Abstract: LogSources wildcards match directories remote log -31 err
Additional information: If a LogSources specifies a remote directory
and not a remote file, the Monitored File Status shows "File
Status" OK, "File Type" of "REGULAR FILE", "PIPE" or
"UNKNOWN" and "Current File Size" 4096, but no files are
monitored.

Note: After the fix, when there are no wildcards in the
directory path, it may still show Status" OK, "File Type"
of "REGULAR FILE".


3.0 Architecture and prerequisites
======================
This fix is supported on all operating systems listed in the Tivoli
Log File Agent User's Guide, version 6.3.0.

Please refer to the IBM Software Product Compatability Reports (SPCR)
for the latest operating system certification information:
http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html

3.1 Prerequisites for this fix
--------------------------------
The prerequisite level for this fix is as follows:
- IBM Tivoli Monitoring, Version 6.2.2: Fix Pack 02 or higher
(6.2.2-TIV-ITM-FP0002)
- IBM Tivoli Log File Agent V6.3, Multiplatform, Multilingual
(CIGM5ML) available from PassPort Advantage.

As this fix is cumulative, it can be installed on any fix level for
this version, release, and mod level above the prerequisite.

For details, see the Troubleshooting Wiki:
https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/Tivoli%20Monitoring/page/Log%20File%20Agent

4.0 Image directory contents
===================
This fix image contains the following files:

- 6.3.0-TIV-ITM_LFA-IF0004.README
- 6.3.0-TIV-ITM_LFA-IF0004.tar
- 6.3.0-TIV-ITM_LFA-IF0004.zip.

Note: The .tar and .zip files are identical in content. Use the .tar
file if you are working in a UNIX® environment; use the .zip file if
you are working in a Windows environment.

The following two archive files contain dsc files for remote deploy
from a Tivoli Monitoring Enterprise Server version 6.2.3 Fix Pack 02
or older:
- 6.3.0-TIV-ITM_LFA-IF0004-PRE623FP3DSC.tar
- 6.3.0-TIV-ITM_LFA-IF0004-PRE623FP3DSC.zip.
See section 5.3 "Remote agent update", step 2 for additional
instructions to work-around this problem.

The fix archive file contains the following files:
6.3.0-TIV-ITM_LFA-IF0004/itmpatch.exe
6.3.0-TIV-ITM_LFA-IF0004/kloaix523.dsc
6.3.0-TIV-ITM_LFA-IF0004/klo_aix523_tema_if0004.tar
6.3.0-TIV-ITM_LFA-IF0004/kloaix526.dsc
6.3.0-TIV-ITM_LFA-IF0004/klo_aix526_tema_if0004.tar
6.3.0-TIV-ITM_LFA-IF0004/klohp11.dsc
6.3.0-TIV-ITM_LFA-IF0004/klo_hp11_tema_if0004.tar
6.3.0-TIV-ITM_LFA-IF0004/klohp116.dsc
6.3.0-TIV-ITM_LFA-IF0004/klo_hp116_tema_if0004.tar
6.3.0-TIV-ITM_LFA-IF0004/klohpi116.dsc
6.3.0-TIV-ITM_LFA-IF0004/klo_hpi116_tema_if0004.tar
6.3.0-TIV-ITM_LFA-IF0004/kloli6263.dsc
6.3.0-TIV-ITM_LFA-IF0004/klo_li6263_tema_if0004.tar
6.3.0-TIV-ITM_LFA-IF0004/klols3263.dsc
6.3.0-TIV-ITM_LFA-IF0004/klo_ls3263_tema_if0004.tar
6.3.0-TIV-ITM_LFA-IF0004/klols3266.dsc
6.3.0-TIV-ITM_LFA-IF0004/klo_ls3266_tema_if0004.tar
6.3.0-TIV-ITM_LFA-IF0004/klolx8266.dsc
6.3.0-TIV-ITM_LFA-IF0004/klo_lx8266_tema_if0004.tar
6.3.0-TIV-ITM_LFA-IF0004/klosol283.dsc
6.3.0-TIV-ITM_LFA-IF0004/klo_sol283_tema_if0004.tar
6.3.0-TIV-ITM_LFA-IF0004/klosol286.dsc
6.3.0-TIV-ITM_LFA-IF0004/klo_sol286_tema_if0004.tar
6.3.0-TIV-ITM_LFA-IF0004/klosol606.dsc
6.3.0-TIV-ITM_LFA-IF0004/klo_sol606_tema_if0004.tar
6.3.0-TIV-ITM_LFA-IF0004/KLOWINNT.dsc
6.3.0-TIV-ITM_LFA-IF0004/klo_winnt_tema_if0004.cab
6.3.0-TIV-ITM_LFA-IF0004/KLOWIX64.dsc
6.3.0-TIV-ITM_LFA-IF0004/klo_wix64_tema_if0004.cab
6.3.0-TIV-ITM_LFA-IF0004/lo_dd_063000004.xml
6.3.0-TIV-ITM_LFA-IF0004/lo_dd.properties


5.0 Installation instructions
==================
This fix can only be installed over an existing installation. Use the
following steps to install this fix.

5.1 Before installing the fix
-------------------------------
- The prerequisites listed under section 3.1 entitled 'Prerequisites
for this fix' must be installed before this fix can be installed.

- For the purpose of this README, the symbol <CANDLEHOME> is the
IBM Tivoli Monitoring installation directory. The default value
for CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\IBM\ITM'
on Windows systems.

- Before installing this fix on UNIX systems, set the environment
variable CANDLEHOME to the IBM Tivoli Monitoring installation
directory.

For example:
> CANDLEHOME=/opt/IBM/ITM
> export CANDLEHOME

- Because there is no uninstall utility for this fix, make sure to
perform a backup of your environment before installing this fix.

5.2 Local agent update
--------------------------
1. Transfer the appropriate archive file
(6.3.0-TIV-ITM_LFA-IF0004.tar or .zip) to a temporary directory
on the system that contains the agent to be updated. For the
purpose of this README, the symbol <TEMP> represents the fully
qualified path to this directory. Note: On Windows systems, this
path includes the drive letter.

2. Expand the archive file using the "tar" command on UNIX systems
or an extract utility on Windows systems. This step creates a
directory structure that contains fixes for all of the supported
platforms.

3. Use the "itmpatch" command to install the fix for the operating
system of that agent. For more information on the "itmpatch"
command, see section 6.2.

On UNIX systems, if the fix was expanded to <TEMP>/6.3.0-TIV-ITM_LFA-IF0004,
the install command is:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.3.0-TIV-ITM_LFA-IF0004/klo_xxxxxx_tema_if0004.tar

where:
- xxxxxx corresponds to the value in the first column returned
by the ./cinfo -i command.

In the following example, the file is "klo_lx8266_tema_if0004.tar".
> ./cinfo -i
lo Tivoli Log File Agent
lx8266 Version: 06.30.00.00

On Windows systems, if the fix was expanded to
<TEMP>\6.3.0-TIV-ITM_LFA-IF0004, the install command is:

> <TEMP>\6.3.0-TIV-ITM_LFA-IF0004\itmpatch -h <CANDLEHOME>
-i <TEMP>\6.3.0-TIV-ITM_LFA-IF0004\klo_winnt_tema_if0004.cab

Note: The itmpatch.exe provided with older releases of IBM Tivoli
Monitoring did not support updating 64-bit Windows systems with
32-bit binaries. For 64-bit Windows systems, you must use the
itmpatch.exe provided with this interim fix.

5.3 Remote agent update
----------------------------
1. Transfer the appropriate archive file
(6.3.0-TIV-ITM_LFA-IF0004.tar or .zip) to a temporary directory
on the IBM Tivoli Enterprise Monitoring Server system. For the
purpose of this README, the symbol <TEMP> represents the fully
qualified path to this directory. Note: On Windows systems, this
path includes the drive letter.

2. Expand the archive file using the "tar" command on UNIX systems or
an extract utility on Windows systems. This step creates a directory
structure that contains fixes for all of the supported platforms.

Note: If your Tivoli Enterprise Monitoring Server is a release or
version prior to v6.2.3 Fix Pack 04 and you are using remote
deploy to install the fix to a UNIX system, download the archive
file 6.3.0-TIV-ITM_LFA-IF0002-PRE6233DSC.tar or .zip to <TEMP>
as described in step 1. Expand the archive file using the "tar"
command on UNIX systems or an extract utility on Windows systems.
This refreshes the .dsc files for your environment.

3. To add the agent fix bundles into the remote deploy depot, use
the "tacmd addBundles" command found in $CANDLEHOME/bin on UNIX
systems or in %CANDLE_HOME%\bin on Windows systems. For more
information on the "tacmd addBundles" command, see the IBM Tivoli
Monitoring Administrator's Guide.

Note:
1. The prerequisite Log File Agent bundles must also be in the
depot, to ensure successful completion of the remote agent update.
2. The 6.3.0-TIV-ITM_LFA-IF0001 bundles must be removed from the
depot, using the "tacmd removeBundles" command.
For example: tacmd removeBundles -t lo -v 063000001

On UNIX systems,
if the fix was expanded to <TEMP>/6.3.0-TIV-ITM_LFA-IF0004:
> $CANDLEHOME/bin/tacmd addBundles -n
-i <TEMP>/6.3.0-TIV-ITM_LFA-IF0004

On Windows systems,
if the fix was expanded to <TEMP>\6.3.0-TIV-ITM_LFA-IF0004:
> %CANDLE_HOME%\bin\tacmd addBundles -n
-i <TEMP>\6.3.0-TIV-ITM_LFA-IF0004

where:
-n indicates that prerequisite bundles are not automatically
added. The -n parameter must be used because the fix
directory does not contain any prerequisites that the fix
might require. Please see Section 3.1 for the prerequisites
for this fix.
-i is the directory that contains the deployment bundles to be
added to the depot.

4. To log in to the Tivoli Enterprise Monitoring server, and deploy
the fix to the appropriate nodes where the agent is running, use
the following "tacmd" commands. For more information on the
"tacmd login" and "tacmd updateAgent" commands, see the IBM Tivoli
Monitoring Administrator's Guide.

On UNIX systems:
> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>

> $CANDLEHOME/bin/tacmd listSystems

The output shows the Managed System Name for the OS agent on the
remote system to be updated. Use this value as the target of the
"tacmd updateAgent" command.

> $CANDLEHOME/bin/tacmd updateAgent -t lo
-n <Managed system name>
-v 063000004

On Windows systems:
> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>

> %CANDLE_HOME%\bin\tacmd listSystems

The output shows the Managed System Name for the OS agent on the
remote system to be updated. Use this value as the target of the
"tacmd updateAgent" command.

> %CANDLE_HOME%\bin\tacmd updateAgent -t LO
-n <Managed system name>
-v 063000004

Note:
- The component (-t) for the "tacmd updateAgent" command is
specified as two characters (LO), not three characters (KLO).
- The node (-n) for the "tacmd updateAgent" command is the managed
system name of the operating system (OS) agent to be updated.
The target node for the "tacmd updateAgent" command is always
an OS agent.

5.4 Agent support update
------------------------------
There are no agent support updates for the Tivoli Enterprise
Monitoring Server, Tivoli Enterprise Portal Server,or Tivoli
Enterprise Portal Desktop included in this fix or any of the
superseded fixes. No additional installation steps are required.

6.0 Additional installation information
========================
For additional troubleshooting installation information, see the
itmpatch.log in the patchlogs directory in <CANDLEHOME>.

6.1 Installation instructions for agent baroc file
-----------------------------------------------------
There are no updates to the baroc files included in this fix or
any of the superseded fixes. No additional installation steps are
required.

6.2 Additional information on using "itmpatch" command
--------------------------------------------------------------
The "itmpatch" command has the following syntax:

Usage: itmpatch -h <installation home> [OPTIONS]

itmpatch -h <installation home>
-t { <patch_file_directory> | <patch_file> }

itmpatch -h <installation home>
-i { <patch_file_directory> | <patch_file> }

where:
-h Specifies the IBM Tivoli Monitoring installation directory
-i Specifies the path to the directory or patch file to be installed
-t Generates a report of the actions to be taken by the patch


For example, on UNIX systems:
- To preview the fix installation, use the "-t" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -t <TEMP>

- To install the fix, use the "-i" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -i <TEMP>

where:
<CANDLEHOME> is the fully qualified IBM Tivoli Monitoring
installation directory. On Windows systems, this path must include
the drive letter.
<TEMP> represents the fully qualified directory specification, where
the fix is located. On Windows systems, this must include the drive
letter.

6.3 Verifying the update
----------------------------
1. To verify the agent was updated correctly, use the "tacmd" command
to view the agent's current version after the agent is restarted.
You are required to log in to a Tivoli Enterprise Monitoring
Server prior to viewing the agent version.

For example:
On UNIX systems, where $CANDLEHOME is the IBM Tivoli Monitoring
installation directory, the default location is '/opt/IBM/ITM'.

> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>
> $CANDLEHOME/bin/tacmd listSystems -t LO

On Windows systems, where %CANDLE_HOME% is the IBM Tivoli
Monitoring installation directory, the default location
is 'C:\IBM\ITM'.

> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>

> %CANDLE_HOME%\bin\tacmd listSystems -t LO

Note: The component (-t) for the "tacmd listSystems" command is
specified as two characters (LO), not three characters (KLO).

When the agent update is successful, the agent version is:
06.30.00.04.

After the agent is restarted, you can also use the GUI to verify
the agent was successfully updated.

For the agent on Windows systems, the version number is
06.30.00.04.

2. To verify the agent you are running contains the updates from the
fix, see the following lines in the agent log
<hostname>_lo_<instance>_kloagent_<timestamp>.log located in
$CANDLEHOME/logs on UNIX systems and
%CANDLE_HOME%\tmaitm6\logs on Windows systems:

<timestamp> Component: ira
<timestamp> Driver: agent_fac_63:201501261618/4507060.3
<timestamp> Timestamp: Jan 26 2015 16:43:11
...
...
<timestamp> Component: kum
<timestamp> Driver: agent_fac_63: 201501261618/4507060.3
<timestamp> Timestamp: Jan 26 2015 16:42:20


7.0 Known problems and workarounds
=========================

APAR: IV53803
ABSTRACT: TACMD ADDSYSTEM OF LO AGENT FAILS WITH 6.3.0-TIV-ITM_LFA-IF0001
Additional information: As a result of this APAR fix, on Tivoli
Enterprise Monitoring Server releases and versions prior to
6.2.3 Fix Pack 03, tacmd updateAgent of UNIX system fails with
"KDY0005E: The component LO is not installed on <machine>. The
Agent lo bundle requires that this component be present for
the installation to proceed... ". See section 5.3 "Remote
agent update", step 2 for additional instructions to work-
around this problem.


8.0 Additional product information
======================
None.


9.0 Copyright and trademark information
==================================
A current list of IBM trademarks is available on the Web at "Copyright
and trademark information" at www.ibm.com/legal/copytrade.shtml.


10.0 Notices
=======
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Some jurisdictions do not allow disclaimer of express or implied
warranties in certain transactions, therefore, this statement may not
apply to you.

This information could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM
may make improvements and/or changes in the product(s) and/or the
program(s) described in this publication at any time without notice.

Microsoft, Windows, and Windows Server are trademarks of Microsoft
Corporation in the United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or
registered trademarks of Oracle and/or its affiliates.

UNIX is a registered trademark of The Open Group in the United States
and other countries.

Linux is a registered trademark of Linus Torvalds in the United States,
other countries, or both.

Other company, product, or service names may be trademarks or service
marks of others.

Third-Party License Terms and Conditions, Notices and Information
-----------------------------------------------------------------
The license agreement for this product refers you to this file for
details concerning terms and conditions applicable to third party
software code included in this product, and for certain notices and
other information IBM must provide to you under its license to
certain software code. The relevant terms and conditions, notices and
other information are provided or referenced below. Please note that
any non-English version of the licenses below is unofficial and is
provided to you for your convenience only. The English version of the
licenses below, provided as part of the English version of this file,
is the official version.

Notwithstanding the terms and conditions of any other agreement you
may have with IBM or any of its related or affiliated entities
(collectively "IBM"), the third party software code identified below
are "Excluded Components" and are subject to the following terms and
conditions:

- the Excluded Components are provided on an "AS IS" basis
- IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND
CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT
NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE
AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE
- IBM will not be liable to you or indemnify you for any claims
related to the Excluded Components
- IBM will not be liable for any direct, indirect, incidental,
special, exemplary, punitive or consequential damages with respect
to the Excluded Components.