IBM Tivoli Monitoring Agent Builder Interim Fix 01 6.2.3.1-TIV-ITM_ABLDR-IF0001

Downloadable files


Abstract

This fix resolves the APARs and defects listed in the "Problems Fixed" section below.

Download Description

Copyright International Business Machines Corporation 2012.

All rights reserved.

Component: IBM(R) Tivoli(R) Monitoring Agent Builder, Version 6.2.3.1

Component ID: 5724C04BR

Fix: 0001, 6.2.3.1-TIV-ITM_ABLDR-IF0001

Date: August 27, 2012

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 Notices


1.0 General description
===============
This fix resolves the APARs and defects listed in the "Problems Fixed"
section below.


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

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

APAR: IV25203
Abstract: FORMAT PATTERNS ,U AND ,RA AND ,RF FAIL TO MATCH DATA
Additional information: Formats whose patterns include "),U" or
"),RA" or "),RF' fail with a <U_REGEX_MISMATCHED_PAREN> and a
"*****Regular expression parsing error in pattern" error.
As a result, it may fail to match any data or more data than
expected.

For example, this pattern includes "),U" where there is a
close parenthesis followed by a comma followed by a U with no
spaces in between:
... (.*),ULD +,(.*),(.*),(.*) ...


With KBB_RAS1=ERROR level tracing, the following error is seen
in the agent log <hostname>_<pc>_<instance>_k<pc>agent_<timestamp>.log:

(<timestamp>:kum0regx.c,1189,"KUM0_OpenRegExPattern")
*****Error: uregex_open failed for pattern ...
pRegEx NULL status 66311 <U_REGEX_MISMATCHED_PAREN>

(<timestamp>:kumpiafi.c,889,"KUMP_InitializeAttrFilterInfo")
*********Regular expression parsing error in pattern ...

APAR: IV24412
Abstract: ONE OR MORE SPACES ARE REMOVED FROM LOG RECORD
Additional information: When one or more blank characters (space
character x20) are the only data read into an internal buffer,
the blanks or spaces are removed.

For example, if the record was "1 2 3 4 5 6 7" and the blank
character between "6" and "7" was read into the internal
buffer, the resulting event record might appear as
"1 2 3 4 5 67"
where the blank character is removed between the 6 and 7.

APAR: IV24080
Abstract: SAMPLE TIME FOR LOG FILE MONITORING NOT CONFIGURABLE
Additional information: A regression occurred in version 6.2.3 to
cause the sample time for the log file being monitored to be
fixed at 150 seconds. In previous releases, the default
sample time was 60 seconds and was configurable with an
environment variable. If a log file is updated every minute,
a different value should be seen when historical data is
retrieved every minute, but the same data is seen in
multiple collection intervals.

APAR: IV23901
Abstract: RATES AND DELTAS CALCULATED AGAIN ON JOINED ATTRIBUTE GROUPS
Additional information: Joining two attribute groups which contain
attributes which are rates or deltas result in incorrect values.
The value seen in the portal for the attribute in the Join
attribute group is different from the value in the base
attribute group because the rate or delta is calculated again
on the joined attribute.

This also applies to filter attribute groups and can occur on
any platform.

APAR: IV23788
Abstract: SUBNODE CONFIGURATION VARIABLE VALUE NOT SEEN AT THE
SUBNODE LEVEL
Additional information: On UNIX(R) with a script or command data
source, the value of a configuration variable defined at
both the agent and subnode level incorrectly contains the
agent level value at the subnode level. This may be seen as
a configuration variable value with a space causing the value
to be set to a partial or no value in the script or command
environment. Depending on how the variable is used, the
results are unpredictable but incorrect.

APAR: IV23313
Abstract: JDBC TESTER DOES NOT AUTOMATICALLY CREATE ATTRIBUTES
Additional information: Entering a JDBC query or stored procedure
into the JDBC statement field on the JDBC information page
does not automatically create the necessary attributes. As a
result, the test button does not return any data rows and does
not return an error. This functionality existed in Agent
Builder version 6.2.3 and prior versions.

At DEBUG_MIN trace level, the
k<pc>_JDBC_ [instanceName]_trace.log contains the following
trace statement:
- MIN - t3 - main -
RefFileParser.ConfigAttributeGroup - Number of metrics in table: 0

APAR: IV22267
Abstract: FRENCH CHARACTERS NOT CORRECTLY PARSED
Additional information: On Windows systems, an agent using a script
data provider uses the system code page to translate the
script output data to UTF-8. However, the system code page
might be different from the user code page causing the code
page specific characters to be translated incorrectly.

For example, a French e accent aigu or accent grave might
appear as a comma in the portal or in the log.
With KBB_RAS1=ERROR (UNIT:shell ALL) tracing, it might be
seen as follows:
(<timestamp>:shellqueryclass.cpp,581,"internalCollectData")
Line received: . . . Unit‚ de temp‚rature . . .

APAR: IV22265
Abstract: JDBC: DECIMAL SEPARATOR NOT HANDLED PROPERLY IN DIFFERENT
LOCALES
Additional information: JDBC drivers always use the period as the
decimal separator and ignore the locale. The Agent Builder
JDBC data provider and agent expect the decimal separator to
be locale specific, not always a period. Locales that use a
comma decimal separator get data values off by magnitudes of
10 based on the scale definition from the JDBC data provider
because the comma is viewed as a hundreds grouping or
separator and is removed.

For example, with DEBUG_MID tracing the following is seen in
the k<pc>_JDBC_[instanceName_]trace.log where <VALUE> is the
column name and the expected result is 1.62:
<timestamp> - MID - tiv-mon - KQZJobHandler0 -
JdbcDataCollector.getAttributeValue - Fetching column value for VALUE
<timestamp> - MID - tiv-mon - KQZJobHandler0 -
JdbcDataCollector.getAttributeValue - Exit, return value = Value = 1.62
. . .
<a v="162"/>

The collector returns the value of 162, instead of 1.62.
The agent then multiplies the value by 100 based on the scale
definition. So the 16200 is seen in the portal.

With KBB_RAS1=ERROR (UNIT:genericagent ALL) tracing, the
value is seen as 16200 in the agent log
<hostname>_<pc>_[ <instance> ]_k<pc>agent_<timestamp>-01.log:
(<timestamp>:genericagent.cpp,1173,"GenericAgent::AddData")
VALUE=16200

APAR: IV21773
Abstract: LOG DATA SOURCES NOT HANDLING DECIMAL SCALE ADJUSTMENT
Additional information: The "Scale Decimal adjustment" of a numeric
attribute is ignored or lost. As a result, the values are
treated as integers and all decimal values are seen as zeros.
For example: "12.45" is truncated to 12 and then displayed in the
portal as "12.00".

APAR: IV21701
Abstract: PERFORMANCE OBJECT STATUS ERROR CODE SHOWS "MISSING LIBRARY"
Additional information: The libk<pc>udp.so library fails to load
even though it exists in $CANDLEHOME/<platform>/<pc>/lib with
the correct owner and group read and execute permission that
the agent is running as, and the LD_LIBRARY_PATH and
LD_LIBRARY_PATH_64 correctly contain the path to the library.
This is a rare and random problem seen on some Solaris
operating systems when starting the agent.

With KBB_RAS1: ERROR tracing, the following error is seen in
the agent log
<hostname>_<pc>_[ <instance> ]_k<pc>agent_<timestamp>-01.log:

(<timestamp>:logmonitorqueryclass.cpp,1019,"registerCallbacks")
Failed to load shared library libk<pc>udp.so : ld.so.1: k<pc>agent:
fatal: libk<pc>udp.so: open failed: No such file or directory.

APAR: IV21698
Abstract: OCTET STRINGS THAT INCLUDE NON-DISPLAYABLE CHARACTERS
DISPLAY INCORRECTLY.
Additional information: OCTET strings that include non-displayable
characters, outside the range of 0x32 to 0x126 (and 0x10,0x13,
CRLF) are incorrectly displayed as ASCII strings, which might
result in the data looking corrupted or invalid in the portal.

For example: The OCTET_STRING 0x0A416A06 is displayed as
"Aj<invalid character> because 0x06 is a non-displayable
ASCII character.

With KBB_RAS1: ERROR (UNIT:snmp ALL) tracing, the following
trace is seen in the agent log
<hostname>_<pc>_[ <instance> ]_k<pc>agent_<timestamp>-01.log:

<timestamp> varBind oid: OBJECT_IDENTIFIER . . .
<timestamp> value: OCTET_STRING
<timestamp> Aj<invalid character>

APAR: IV20604
Abstract: MULTI-BYTE CHARACTERS IN AN EVENT MIGHT BE CORRUPTED
Additional information: With a log file in a multi-byte character
code page, a log agent might occasionally generate event
messages that contain incorrect or corrupted characters. The
problem occurs when the agent reads in an incomplete or
partial multi-byte character and attempts to translate the
data to UTF-8. The buffer contains a series of 3 invalid
characters: xEF xBF xBD or the last translated byte is x1A.

For example, with KBB_RAS1: ERROR (UNIT:kum0regx ALL) tracing,
the "EFBF BD" is seen in the agent log
<hostname>_<pc>_[ <instance> ]_k<pc>agent_<timestamp>-01.log:

(<timestamp>:kum0regx.c,308,"KUM0_IsRegExPatternMatch")
<0x1020752E0,0x30A4> 80808080
. . .
+timestamp> 00003030 92B0E5A2 832F1AE9 9CB9EFBF BD504344
...../.......PCD


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

2.3 Superseded fixes
-------------------------
None.

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


3.0 Architecture and prerequisites
======================
This fix is supported on all operating systems listed in the IBM
Tivoli Monitoring Agent Builder User's Guide, version 6.2.3.1.

3.1 Prerequisites for this fix
--------------------------------
The prerequisite level for this fix is as follows:

IBM Tivoli Monitoring V6.2.3.1 Agent builder, which is available
from PassPort Advantage under the following eAssembly:

* IBM Tivoli Monitoring V6.2.3 Fixpack 1 Agent builder, English,
Multiplatfom (CI6WIEN)
* IBM Tivoli Monitoring V6.2.3 Fixpack 1 Agent builder for Business
Partners, English, Multiplatform (CI75EEN).


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

- 6.2.3.1-TIV-ITM_ABLDR-IF0001.README - This README file
- 6.2.3.1-TIV-ITM_ABLDR-IF0001.tar - Fix archive .tar format
- 6.2.3.1-TIV-ITM_ABLDR-IF0001.zip - Fix archive .zip format.

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

The fix archive file contains the following files:
- plugins/com.ibm.tivoli.monitoring.AgentGenerator.runtime_6.2.3.v201208240847.jar
- plugins/com.ibm.tivoli.monitoring.AgentGenerator_6.2.3.v201208240847.jar
- plugins/com.ibm.tivoli.monitoring.agentkit.provider.jdbc_6.2.3.v201208240847.jar

Note: The plugins contained in this fix are not removed when the
builder is uninstalled. They must be manually removed.

5.0 Installation instructions
==================
This fix applies to an Agent Builder, version 6.2.3.1 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.

- If the Agent Builder is currently running, stop the builder.

5.2 Agent Builder update
--------------------------
1. Transfer the appropriate archive file 6.2.3.1-TIV-ITM_ABLDR-IF0001.tar
or .zip to the directory where the Agent Builder to be updated is
installed. The default installation location on Windows systems is
"C:\Program Files\IBM\ITM\AgentBuilder" and on UNIX systems, it is
"/opt/IBM/ITM/AgentBuilder".

2. Expand the archive file in to the Agent Builder installation
location using the tar command on UNIX systems or an extract
utility on Windows systems. This installs the fix in the
plugins directory.

The plugins directory now contains the new jar files listed in
section 4.0 "Image directory contents".

3. If the builder was running when the update was installed, you may
restart the builder.

4. Use the Generate Agent Wizard to regenerate your agents and then
re-install the agent.

5.3 Agent support update
------------------------------
There are no Agent Builder changes which affect agent support files
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.


6.0 Additional installation information
========================

6.1 Verifying the update
----------------------------
1. In the builder, select Help->About IBM Tivoli Monitoring Agent
Builder and select the "Installation Details" button. Select the
Plug-ins tab. Click on the Version column header to sort in
descending order. The top entries are:
1. Plug-in Name: IBM Tivoli Monitoring Agent Generator
Version: 6.2.3.v201208240847
2. Plug-in Name: IBM Tivoli Monitoring Agent Generator Runtime
Version: 6.2.3.v201208240847.jar
3. Plug-in Name: JDBC Data Provider
Version: 6.2.3.v201208240847

2. To verify the Agent Builder was updated correctly, the header of
most newly generated text based agent files contain a few similar
lines with a timestamp of "201208240847":

. . .
<!-- IBM Tivoli Monitoring Agent Generator 6.2.3.1 201208240847-->
. . .
<!-- IBM Tivoli Monitoring JDBC Data Provider 6.2.3.1 201208240847-->
. . .

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

<timestamp> Component: ira
<timestamp> Driver: 201208240847/4264477.3
<Timestamp> Timestamp: Aug 24 2012 09:36:32

7.0 Known problems and workarounds
=========================
None.


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


9.0 Notices
=======
This information was developed for products and services offered in the United
States. IBM may not offer the products, services, or features discussed in this
document in other countries. Consult your local IBM representative for information
on the products and services currently available in your area. Any reference to an
IBM product, program, or service is not intended to state or imply that only that
IBM product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify
the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

The following paragraph does not apply to the United Kingdom or any
other country where such provisions are inconsistent with local law:

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 states do not allow disclaimer of express or implied warranties in
certain transactions, therefore, this statement may not apply to you.

Trademarks and service marks
------------------------------------
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks
of International Business Machines Corp., registered in many
jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM trademarks
is available on the Web at "Copyright and trademark information" at
www.ibm.com/legal/copytrade.shtml.

Microsoft, Windows, Windows NT, and the Windows logo 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.

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

Prerequisites

The prerequisite level for this fix is as follows:

IBM Tivoli Monitoring V6.2.3.1 Agent builder, which is available
from PassPort Advantage under the following eAssembly:

* IBM Tivoli Monitoring V6.2.3 Fixpack 1 Agent builder, English,
Multiplatfom (CI6WIEN)
* IBM Tivoli Monitoring V6.2.3 Fixpack 1 Agent builder for Business
Partners, English, Multiplatform (CI75EEN).

Installation Instructions

Please refer to the full README contained in the Download Description section above for general installation instructions.

Download package


Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is Fix Central (FC)?
6.2.3.1-TIV-ITM_ABLDR-IF0001 27 Aug 2012 English 80732160 FC

Product Alias/Synonym

factory

Problems (APARS) fixed
IV25203, IV24412, IV24080, IV23901, IV23788, IV23313, IV22267, IV22265, IV21773, IV21701, IV21698, IV20604

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Monitoring Version 6
Agent Builder

Software version:

6.2.3.1

Operating system(s):

AIX, Linux, Windows

Reference #:

4033239

Modified date:

2012-08-28

Translate my page

Machine Translation

Content navigation