IBM Tivoli Monitoring for Applications: mySAP Agent, 6.2.0-TIV-ITM_SAP-IF0016

Downloadable files


Abstract

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.4

Download Description

Copyright International Business Machines Corporation 2013.

All rights reserved.

1.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.


Component: IBM(R) Tivoli(R) Monitoring for Applications: mySAP Agent,
Version 6.2.0

Component ID: 5724B97SO

Interim Fix: 0016, 6.2.0-TIV-ITM_SAP-IF0016

Date: August 30, 2013

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. This fix also includes the superseded fixes listed in
section 2.4.

This fix does not contain the installation image for Linux 64-bit
platforms, but it provides a maintenance package for Linux 64-bit
support. To install the mySAP agent on Linux 64-bit operating
systems, download and install LA0009 before applying this fix.

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

2.1 APARs
----------
APAR: IV46184
Abstract: CCMS ALERTS OLDER THAN 3 MINUTES ARE NOT SET TO DONE WHEN THE
ALERT CONDITION IS CLOSED.
Additional Information:As the NEW CCMS Design is only collecting the
alerts for specified start and end time, we changed the logic
of comparision of previous and new collection of alert. Wth the
new ccms alert data collection, using DONE status to perform
auto-closure of the events, a problem occurs if the alerts are
older than 3 minutes. If you open an event, and wait longer than
3 minutes to close the event, the event does not get closed.


APAR: IV41680
Abstract: CCMS ALERTS STATUS SET TO DONE IN THE NEXT DATA COLLECTION
USING THE NEW CCMS ALERT DATA COLLECTION METHOD INCORRECTLY
Additional Information:As the NEW CCMS Design is only collecting the
alerts for specified start and end time, we changed the
logic of comparision of previous and new collection of alert.
SAP AGENT is sending open and closed alerts for a given time
frame (Start and End time).
Open alerts are collected from SAP Standard function module and
closed/completed alerts are collected from SAP standard table
ALALERTDB. Currently no SAP API is available to collect closed
alerts in specified alert change time, so we are collecting the
completed alerts from ALALERTDB table according to the changed
time.

Limitations:
If SAP System is CEN(Centralized Monitoring) System SAP agent
will fetch closed alerts from remote system from table
ALALERTDB. However while collecting these old alerts SAP agent
will also take care of performance issue or delay caused during
data collection.
To avoid any further delay in closed alerts data collection SAP
agent will collect below fields from remote systems.
Customer should include only following attributes in closed
situation's formula
'ALSYSID' SAP System Name
'ALUNIQNUM' Alert Unique Identifier
'ALERTDATE' Alert Date
'ALERTTIME' Alert Time
'MTSYSID' Name of the SAP System
'MTUID' Monitoring Types ID
'MTMCNAME' Alert: Name of Monitoring Context
'MSEGNAME' Alert: Name of Monitoring Segment
'MTCLASS' MTE Class
'VALUE' Alert Value
'SEVERITY' Severity
'STATUS' Alert Status
'OBJECTNAME' Alert Object Name
'FIELDNAME' Alert Field Name

Pre-Requisite:
1. To collect the rfc destinations of remote systems
Pre-Requisite is that while configuring CEN the below RFC
Destinations should be present according to the recommended
naming convention and these should be active in RZ21. These
steps are mentioned by SAP while configuring CEN system to
monitor multiple systems, please check the link below.

https://help.sap.com/saphelp_nw70/helpdata/en/84/d2b33a687d747ee10000000a114084/content.htm


RFC Destination: Enter the name for the RFC connection; we
recommend <SID>_RZ20_COLLECTfor the RFC destination for data
collection, <SID>_RZ20_ANALYZE for the RFC destination to
execute the analysis method.
Connection Type: Enter 3 (for ABAP system).

2. Authorization might be required to read the table ALALERTDB
from Remote systems however we have added an authorization:
S_TABU_DIS to IBMMON_AGENT User which will be used to collect
data from remote systems. Please refer to
ITCAM_SAP_Agent_HowTos.pdf for steps for adding authorizations.

Note: If any error happens while reading the remote system agent
will write a syslog entry like below example
'Error reading ALALERTDB table from remote system'.
You can check this entry from SM21 transaction code.

APAR: IV38554
Abstract: /IBMMON/ITM_IDOCS SYSTEM_FAILURE NO MORE STORAGE SPACE
AVAILABLE FOR EXTENSDING AN INTERNAL TABLE
Additional Information: mySAP agent code improved to handle ABAP dump
occurs for IDOC function module.

APAR: IV33539
Abstract: MULTIBYTES CHARS WAS CUT OFF INCORRECTLY IN MESSAGE TEXT
ATTRIB
Additional Information: When a multiple bytes character like Japanese
character is overlaid before and behind 78th bytes in Message
Text attribute of System Log attribute group, the character is
cut off at the middle of the character incorrectly. Then, the
character is garbled. As a result, the event isn't formed
correctly in Netcool EIF probe and it cannot handle the event.

APAR: IV33183
Abstract: SAP AGENT SOMETIMES FAILED TO COLLECT SYSTEM LOG DATA
Additional Information: With 620 IF0015 mySAP agent sometimes failed
to collect System Log Information. As a result all of situation
of SAP syslog monitor delays around 15 minutes. Issue is fixed
in this build and change is done to modify the default value of
SYSLOG_FREQUENCY. Default value is 600 seconds.
How To change SYSLOG_FREQUENCY.
1. For Windows: Set SYSLOG_FREQUENCY=180 in a agent specific
configuration file
Example: <candle home>\tmaitm6\ksaenv_<sid>
2. For Non-Windows: Set SYSLOG_FREQUENCY=180 in a agent
specific configuration file
Example :<candle home>/config/sa_<sid>.config

Recommended values are between 5 to 10 minutes.

APAR: IV32752
Abstract: MYSAP AGENT FILE SYSTEMS WORKSPACE NOT DISPLAYING
FILESYSTEM NAMES FOR NON-UNICODE SAP SYSTEMS
Additional Information: After applying 6.2.0-TIV-ITM_SAP-IF0014 mySAP
agent Systems Workspace not displaying Filesystem names for
non-Unicode sap Systems. This is expected behavior and agent
running on non-Unicode sap system does not show any value.
There is no applicable data for such fields.

2.2 Defects
----------------
Defect: 184476
Abstract: CT: ABAP mismatch though correct level transports on sol11
x86_64
Additional Information:On Solaris 11 x86_64 platform, after applying
IF15 patch on sap 620 GA, the agent version is updated. But on
portal the ABAP mismatch error is thrown.

Defect: 184473
Abstract: CT: Take action not working for Non windows platforms
Additional Information: After applying 6.2.0-TIV-ITM_SAP-IF0014 mySAP
agent on non-windows platform, agent's take action are not
working and gives return code as 4.

Defect: 207614
Abstract: Situation and HDC is not working for CCMS alerts in first
call
Additional Information: The situation is not firing and HDR files are
not getting created or updated for alerts which are collected
in first mySAP agent call, this issue is fixed under this
defect

2.3 Enhancements
----------------
Enhancements: 29809/205493
Abstract: No Duplicate alerts in 620 IF0016
Additional Information: As per old CCMS design SAP agent collect all
all open alerts which also includes duplicate in each cycle.
Issue fixed in old CCMS design to avoid duplicate alerts.

Limitations:
1. If switching between Old CCMS design and New CCMS design
does not happen then this approach guaran-tees 'no duplicate
EventArrived() calls for the same alert, across agent
sessions'.
2. When user switches agent from Old CCMS design to New CCMS
design, due to unavailability of the <SID>_alerts.idx file
or due to timestamp is not updated in the file, agent will
collect all the alerts which were sent by it when Old CCMS
design was on.
3. when user switches agent from New CCMS design to Old CCMS
design, user has to restart the agent. And after restart,
due to unavailability of the <SID>_alerts_old_design.idx or
due to Alert Unique Identifier is not updated in the file,
agent will call EventArrived() on all the alerts which were
sent by it when New CCMS design was on.
3. This feature is limited to “Add new open alert”. For
"Close alert” and “Update alert” this is not applicable as
these can come out-of-sequence.


Enhancement: 27843
Abstract: CCMS current state monitoring filter
Additional Information: Currently /IBMMON/ITM_CCMS_MTE_STATE function
module retrieves all records with states green,red,yellow etc.
Situations which are associated with this attribute use only red
and yellow states. A new configurable “Green_Alerts check box”
option at ABAP side is added under transaction
/n/ibmmon/itm_ccmsmon. If this check box is checked then
Function module will retrieve all MTE states and if its
unchecked then only red and yellow state will be retrieved.
Note: By default its unchecked.
Steps To Enable Green alerts state -
1) Logon to SAP GUI.
2) Execute “/n/IBMMON/ITM_CONFIG” transaction code
3) click /IBMMON/ITM_CCMSMON
4) Check “Green Alerts” checkbox
5) Save changes.


Enhancement: 187311
Abstract: New CCMS Enhancement To Improve Performance
Additional Information: At the SAP system, all the CCMS records are
pushed to SAP agent in each sampling cycle. It is observed in
few PMRs that if CCMS record count becomes huge then returning
all records to SAP agent has negative performance (old CCMS
design), both on network and agent process. In new Design to
reduce the CCMS record count agent will collect all new alerts
in samples. Default Sample period is 3 minutes. In new design
mySAP agent handle the failure occurs during any sample cycle.
In case of any failure mySAP agent would start collecting alerts
from previous sample cycle(i.e. after last successful cycle)

Steps To Enable new CCMS Design-
1) Logon to SAP GUI.
2) Go to transaction code SE16 and give table name
"/IBMMON/ITM_CNFG".
3) To create entry, press F5.
4) Provide PARM NAME as ISNEWCCMSDESIGN.
5) VALUE CHAR as YES.
6) Save changes.

The agent is enhanced to adjust the CCMS alerts displayed on TEP
using one new configuration parameter MAX_CCMS_ALERT_THRESHOLD.
By default value is 1000, so user will see 1000 alerts on the
TEP, older alerts will be removed from the agent cache.
User can modify the max CCMS alert threshold value as below.
If Value less than 100 is set then agent will take 100.

On windows
. Edit “<candle_home>\tmaitm6\KSAENV” file.
. On Non-Windows
. Edit “<candle_home>/config/sa.ini” file.
. Add variable MAX_CCMS_ALERT_THRESHOLD=< Value>
. Save changes.
. It will reflect automatically if new CCMS design is enabled
on SAP side.

NOTE: Collection of CCMS alerts does not depends on the size of
agent cache.

Steps To Disable new CCMS Design
1) Logon to SAP GUI
2) Go to the transaction code SE16 and give table name
“/IBMMON/ITM_CNFG”
3) Press F7 and then press F8
4) Select ISNEWCCMSDESIGN parameter
and in table entry select delete all option.
(delete all deleted the selected entry only)
5) Select yes in the confirmation pop up box.

After disabling the new CCMS design on the SAP side,
restart the mySAP agent to return to the old design.

Steps to verify if New CCMS Design is enabled
(A)SAP Side Steps:
1) Logon to SAP GUI.
2) Go to the transaction code SE16 and give table name
“/IBMMON/ITM_CNFG”.
3) Press “Enter” and then press F8.
4) Check whether “ISNEWCCMSDESIGN=YES” entry is present or
not. If Yes then new design is enabled.
5) Save changes.

(B)Agent Side Steps:
1) Open agent log files
On windows:
. <candle_home>\tmaitm6\logs\<Agent Host>_sa_<SID>_ksaagent
_<8 digit num>-01.log
On non-windows:
. <candle_home>/logs/<Agent Host>_sa_<SID>_ksaagent_
<8 digit num>-01.log
2) Search following messages in agent log,
a. “New CCMS design is enabled on ABAP side”
This means new CCMS design is enabled.
b. CCMS alerts cache capacity MAX_CCMS_ALERT_THRESHOLD is
set to <1000>
This means max alert threshold is set to shown value.
c. New CCMS Design calling function module:
</IBMMON/ITM_ALERTS>
Agent is logging this message before requesting CCMS
alerts data from SAP

Troubleshooting
In mySAP agent new ABAP function module (/IBMMON/ITM_CNFG) is
used to check whether New CCMS design is enabled or not on SAP
side. If this new ABAP function module is not available in
transport which is configured/imported on SAP side then
following error will come.

Error:
(51259A4D.0000-25E4:ksalogmsg.cpp,173,"logmsg") KSA0911
errmsg: -911 ***
Failure on call to Fatal RFC error - program ending
(51259A4D.0001-25E4:ksalogmsg.cpp,173,"logmsg") KSA0911
errmsg: RFC
ERROR SNAPSHOT at 11:53:50 on 02/21/2013
(51259A4D.0002-25E4:ksalogmsg.cpp,173,"logmsg") KSA0911
errmsg:
Parameter 1 : RFCTYPE_UNKNOWN_HANDLE
(51259A4D.0003-25E4:ksalogmsg.cpp,173,"logmsg") KSA0911
errmsg: Error exception:
(51259A4D.0004-25E4:ksalogmsg.cpp,173,"logmsg") KSA0911
errmsg: Error key : RFC_ERROR_SYSTEM_FAILURE
(51259A4D.0005-25E4:ksalogmsg.cpp,173,"logmsg") KSA0911
errmsg: Error status :
(51259A4D.0006-25E4:ksalogmsg.cpp,173,"logmsg") KSA0911
errmsg:
Error message : Function module "/IBMMON/ITM_CNFG" not found.
(51259A4D.0007-25E4:ksalogmsg.cpp,173,"logmsg") KSA0911
errmsg: Error instat :
(51259A4D.0008-25E4:ksaerrmsg.cpp,58,"rfc_error") Fatal RFC
error – Process terminating with exit code -911

Solution: Ensure to import same level of transport first on SAP
side then update agent.
Or alteast make sure to import ABAP transport on SAP system
prior to agent installation to avoid this error.
Agent will not work if ABAP transport less than IF0016.

Enhancement: 207615
Abstract: Multiple client support for IDOCs
Additional Information: The mySAP agent will collect IDOCs for all
SAP clients configured on SAP server.

Enhancement: 207618
Abstract: IDOCs status is collected as per particular start and end
time
Additional Information: IDOCS status are stored in the table EDIDS
and SAP agent will now collect the IDOC Status records which
are changed in that particular time only to reduce the huge
number of entries. This is done to improve the IDOC data
collection.

2.4 Superseded fixes
---------------------
6.2.0-TIV-ITM_SAP-IF0015
6.2.0-TIV-ITM_SAP-IF0014
6.2.0-TIV-ITM_SAP-IF0013
6.2.0-TIV-ITM_SAP-IF0012
6.2.0-TIV-ITM_SAP-LA0011
6.2.0-TIV-ITM_SAP-LA0010
6.2.0-TIV-ITM_SAP-IF0008
6.2.0-TIV-ITM_SAP-IF0007
6.2.0-TIV-ITM_SAP-IF0006
6.2.0-TIV-ITM_SAP-LA0005
6.2.0-TIV-ITM_SAP-LA0004
6.2.0-TIV-ITM_SAP-LA0003
6.2.0-TIV-ITM_SAP-LA0002
6.2.0-TIV-ITM_SAP-LA0001

2.5 APARS and defects included from superseded fixes
---------------------------------------------------------------
6.2.0-TIV-ITM_SAP-IF0015
--------------------------
APAR: IV10144
Abstract: SAP AGENT CONSUMING HIGH CPU
Additional Information: The agent consumes high memory on the SAP
system because of a heavy workload that causes ABAP memory
dumps such as "TSV_TNEW_PAGE_ALLOC_FAILED". The agent was
enhanced to adjust the duration of data collection by using two
new configuration parameters for STATISTICS COLLECTION and one
new parameter for IDOCS COLLECTION.

How to modify the values of these two new parameters.
Please follow below these steps:

(1)'STAT_READ_MAX_HISTORY'
The max history will be in hours. This variable is used
to collect statistical data from the SAP system. If not
specified, by default SAP API used by the agent collects
data for the last 6 hours.

Example: For 2 HOURS
PARAM NAME = STAT_READ_MAX_HISTORY
VALUE CHAR = <leave blank>
VALUE INT = 2

Example: For 5 HOURS
PARAM NAME = STAT_READ_MAX_HISTORY
VALUE CHAR = <leave blank>
VALUE INT = 5

(2)'STAT_READ_API_INTERVAL'
The value of this parameter is seconds. To collect statistical
data for STAT_READ_MAX_HISTORY duration, the agent will call SAP
API will use STAT_READ_API_INTERVAL to collect complete data in
samples. This will avoid low memory issue during data collection
by calling SAP API in short interval as specified in
STAT_READ_API_INTERVAL. If not specified, the default
is five minutes.

Example: For 60 SECONDS or 1 min
PARAM NAME = STAT_READ_API_INTERVAL
VALUE CHAR = <leave blank>
VALUE INT = 60

Example: For 180 SECONDS or 3 mins
PARAM NAME = STAT_READ_API_INTERVAL
VALUE CHAR = <leave blank>
VALUE INT = 180

Use these steps to modify the “/ibmmon/itm_cnfg” table:
1: Log on to the SAP system through the SAP GUI.
    2: Run the ‘SE16’ transaction code.
        3: Enter ‘/IBMMON/ITM_CNFG’ as the table name.
        4: Press F5 to create a new entry.
       5.a. In the PARM NAME field, enter 'STAT_READ_MAX_HISTORY' and
in VALUE INT field, enter the number (Default is 6).
OR
5.b. In the PARAM NAME field, enter 'STAT_READ_API_INTERVAL'
and in the VALUE INT field, enter the number
(Default is 300)
6. Press Save or CNTRL+S.
7. Press F3 to go to back one screen.

How to modify the values of the IDOCS Configurable parameter.
Please follow below steps:

(1)'IDOCS_READ_INTERVAL'
The value of the API Interval is in seconds. To collect IDOCS
data for a Sample duration, the SAP API is called
'IDOCS_READ_INTERVAL' to collect complete data. This will avoid
low memory issue during data collection by calling SAP API in
short interval as specified in IDOCS_READ_INTERVAL.
If not specified, the default is five minutes

Example: For 60 SECONDS or 1 min
PARAM NAME = IDOCS_READ_INTERVAL
VALUE CHAR = <leave blank>
VALUE INT = 60

Example: For 180 SECONDS or 3 mins
PARAM NAME = IDOCS_READ_INTERVAL
VALUE CHAR = <leave blank>
VALUE INT = 180

Use these steps to modify the “/ibmmon/itm_cnfg” table:
1: Log on to the SAP system through the SAP GUI.
2: Run the ‘SE16’ transaction code.
3: Enter ‘/IBMMON/ITM_CNFG’ as the table name.
4: Press F5 to create a new entry.
5. In the PARM NAME field, enter 'IDOCS_READ_INTERVAL' and in
the VALUE INT filed, enter the number(Default is 6)
6. Press Save or CNTRL+S.
7. Press F3 to go to back one screen


APAR: IV14414
Abstract: VALUES OF SYSTEM_DESCRIPTION ATTRIBUTE ON NON-UNICODE SAP
SYSTEMS IS NOT CORRECT
Additional Information: The agent does not display the value of
System_Description correctly when it runs on Russian(RU)
systems.

APAR: IV18311
Abstract: SAP ON AIX HAS A DIFFERENT STYLE DATE FORMAT
Additional Information: SAP Gateway Connections Request Time displays
an incorrect value in the Tivoli Enterprise Portal when the SAP
system is on an AIX platform.

APAR: IV15697
Abstract: ZERO VALUES IN SAP WORKSPACE FOR FRONT END NETWORK TIMES &
GUI TIMES
Additional Information: After applying 6.2.0-TIV-ITM_SAP-IF007/IF0014,
the values of two attributes, Front-End Network Time and
GUI-Time, are always zero in the Transaction Performance
workspace. This issue occurs because the agent is using an
older version of the SAP API.

APAR: IV25676
Abstract: ITM FOR SAP 6.2.0 HOW MONITOR SAP CENTRAL INST OUTAGE
Additional Information: After applying 6.2.0-TIV-ITM_SAP-IF0014 in
multiple SAP instances setup if both SAP Instances, including
the Central Instance is down then System_Down situation only
fires once , indicating that Application Instance is down. So
the issue is that up to now we never have seen any System_Down
Alert indicating that the Central Instance is down.

2.2 Defects
------------
Defect: 166690
Abstract: SAP Agent SYS Log not working on SAP system 702
Additional Information: This problem is specific to SAP V7.0.2
The agent does not return system log information from SAP V7.0.2
server due to SAP API change.

Defect: 174080
Abstract: Sap agent reconfigure deletes saplogon groups registry
entries
Additional Information: The SAP agent reconfiguration deletes saplogon
groups registry entries when using the SAPLOGON option.

Defect: 175567
Abstract: Unwanted log statements in mySAP agent log files
Additional Information: After applying 6.2.0-TIV-ITM_SAP-IF0014 agent
log files are filled up with unwanted debug statements.


Defect: 177456
Abstract: To add the missed definition for few attributes with
affinity
Additional Information: During the last few releases, new attributes
were added, but affinity was not set correctly.

Defect: 182474
Abstract: ksa agent hang issue/ unable to start or stop sometime
Additional Information: Sometimes the V6.2.0 agent stops after
starting agent and no data is displayed in the workspace.
This issue rarely occurs on all OS platforms.

--------------------------
6.2.0-TIV-ITM_SAP-IF0014
--------------------------
APAR: IV01667
Abstract: TACMD ADDSYSTEM FOR ITM SAP AGENT REMOVES REGISTRY
CT_CMSLIST.
Additional Information: On Windows systems, after applying
6.2.0-TIV-ITM_SAP-IF0012/IF0013, "tacmd addsystem" for the mySAP
agent removes the CT_CMSLIST registry setting. The fix for this
APAR resolves the issue of creating a new mySAP agent instance
remotely when the SAP agent 6.2.0-TIV-ITM_SAP-IF0014 patch level
is applied.
NOTE: Update the mySAP agent to the 6.2.0-TIV-ITM_SAP-IF0014
patch level before creating an instance. A remote instance
created for the mySAP Agent with a lower version
(for example, 6.2.0-TIV-ITM_SAP-IF0012) will have the issue of
the CT_CMSLIST registry setting. To correct the configuration of
the instance created with the lower patch level, use the
following steps on a mySAP agent computer:
a.
- Go to the %CANDLE_HOME%\TMAITM6 folder.
- Open the ksacma_<Instance_Name>.ini file of the mySAP agent
instance that is having this issue. Example: ksacma_ECC.ini.
- Manually edit the ksacma_<Instance_Name>.ini file to
replace "PreProcess=InitExit" with the correct value:
"PostProcess=InitExit".
- Save the ksacma_<Instance_Name>.ini file.
b. Manually reconfigure the SAP instance and provide
the value of “Hostname or IP Address”.
c. Restart the SAP agent instance.

APAR: IV01415
Abstract: SITUATION EVENT FOR "R3_ALERT_SYSTEM_UP" RAISED ON
UNEXPECTED SUBNODE,CAUSING THE DOWN EVENT NOT TO BE CLEARED.
Additional Information: When the "Lost connection to mySAP system"
alert appears in the CCMS alerts, the agent fires the
"R3_Alert_System_Down_LI" situation. Later, when the system is
online, the "Reconnect to mySAP system" alert is generated on
another instance or subnode and as a result the event for
"R3_Alert_System_Down_LI" cannot close automatically.
To close a situation when a situation that is up is triggered,
the display item must not have a "message" value.

APAR: IV01690
Abstract: SITUATION R3_BATCH_TOO_LONG WRONGLY DEFINED :
IT CONTAINS A DISPLAY ITEM.
Additional Information: When clicking on the Display Item for the
predefined mySAP agent "R3_Batch_Too_Long" situation,
the following error message is displayed: "KFWITM053E The
Display Item Feature cannot be used with this Situation because
its definition contains an embedded situation.".

APAR: IV03066
Abstract: CX_SY_CONVERSION_OVERFLOW IN FUNCTION MODULE
/IBMMON/ITM_WORK_PROCESSES
Additional Information: 'CX_SY_CONVERSION_OVERFLOW' ABAP dump was
generated in the /IBMMON/ITM_WORK_PROCESSES function module,
because of an overflow when converting from "6.64614e+35" with
Runtime Errors CONVT_OVERFLOW.

APAR: IV06898
Abstract: SAP AGENT CRASHED WHEN MONITORED SAP INSTANCE WAS STOPPED
Additional Information: The mySAP agent stopped when the monitored
SAP instance was stopped. This issue occurs rarely.

--------------------------
6.2.0-TIV-ITM_SAP-IF0013
--------------------------
APAR: IZ98715
Abstract: ITM WAREHOUSE DATA NOT CORRECT.
Additional Information: IF0012 ABAP transport failed to import into
4.6C/D SAP system due to syntax error ABAP dump.

APAR: IZ95402
Abstract: LITM6U37 ABAP WHOLE NUMBER OVERFLOW ON ADDITION.
Additional Information: After applying 6.2.0-TIV-ITM_SAP-IF0013,
the /IBMMON/ITM_WORK_PROCESS ABAP function sometimes
generates CX_SY_ARITHMETIC_OVERFLOW ABAP dumps.

APAR: IV01672
Abstract: SITUATION OF SYSTEM LOG ATTRIBUTE DIDN'T FIRE AT ALL.
Additional Information: After applying 6.2.0-TIV-ITM_SAP-IF0013,
a situation using the System Log attributes group did not fire.

APAR: IZ96886
Abstract: 'CX_SY_CONVERSION_OVERFLOW' ABAP DUMP GENERATED IN
/IBMMON/ITM_BUFFER_PERF FUNCTION MODULE
Additional Information: 'CX_SY_CONVERSION_OVERFLOW' ABAP dump was
generated in the /IBMMON/ITM_BUFFER_PERF function module,
because of incorrect integer data handling. The data exceeded
the maximum integer value and generated the ABAP dump.

APAR: IZ98165
Abstract: MISSING ENTRIES IN WAREHOUSE FOR SEVICE_RESPONSE_TIME
ATTRIBUTE GROUP
Additional Information: The mySAP agent does not collect historical
data sometimes when an interval has expired; therefore, entries
are missing in data warehouse.

APAR: IZ95698
Abstract: FROM TIME TO TIME,SAP AGENT DOES NOT DETECT SAP SYSLOG
EVENTS
Additional Information: Sometimes, the SAP agent does not fire
situations defined in the System Log attribute group.

APAR: IZ95885
Abstract: INCORRECT VALUE OF ERRORS ATTRIBUTE IN WORK PROCESS
ATTRIBUTES.
Additional Information: At Process Overview in the SAP GUI, when you
select a work process and then select "Process" ->
"Cancel without core" in the menu bar, the 'Errors' column for
the work process changes to '1'. However, the 'Errors'
attribute for the work process is still 0 in the Tivoli
Enterprise Portal workspace.

APAR IZ99290
Abstract: NO USEFUL DISPLAY_ITEMS FOR KSAMTSTATE ATTRIBUTE GROUP.
Additional Information: The Current State Information attributes group
has only one attribute that can be selected as Display_Item in
the Situation Editor: "Number" attribute. But typically, this
attribute is not helpful. Other attributes must be included in
the Display_Item list, for example, TID_Internal_Handle and
Monitor Object Name.

Defect: 150074
Abstract: Change system log attributes group from sample event type
to pure event type.
Additional Information: Currently, the System Log attribute group
is a sample event and you must change it to a pure event.

Defect: 154525
Abstract: Fix CX_SY_CONVERSION_OVERFLOW error in
TM_WORK_PROCESS ABAP function module
Additional Information: The /IBMMON/ITM_WORK_PROCESS ABAP function
sometimes generates CX_SY_CONVERSION_OVERFLOW ABAP dumps.

Defect: 157216
Abstract: 6.2.0-TIV-ITM_SAP-IF0013 ABAP transports failed to import
into 4.6C SAP systems.
Additional Information: 6.2.0-TIV-ITM_SAP-IF0013 failed to import
into 4.6C SAP system and generated SYNTAX_ERROR ABAP dumps.

Enhancement: 151151
Abstract: Add total active user number into Instance Configuration
attribute groups.
Additional Information: Add total active user number, RFC user number,
interactive user number, and registered user number to the
Instance Configuration attribute group.

Enhancement: 150849
Abstract: Add GUI type into the Status Reason attribute in Work
Process attribute groups.
Additional Information: Currently, the GUI type is missing from the
Status Reason attribute, so you must add this type.


--------------------------
6.2.0-TIV-ITM_SAP-IF0012
--------------------------
APAR: IZ89230
Abstract: AVG_RESP_TIME is not calculated using weighted time for the
SAP attribute group GROUP R3_SERVICE_RESPONSE_TIME.
Additional Information: In the R3_Service_Response_Time_H/_D/etc
table, Avg Resp Time is calculated from the
R3_Service_Response_Time table into the
R3_Service_Response_Time_H table. But, the average AVG_Resp_Time
is not calculated using the Weighted Mean
(IBM Tivoli Monitoring uses average without weight).
This calculation causes the KPI in the _H table to be
meaningless. The same problem applies to the other summary
table.

Enhancement: 143865
Abstract: Add an attribute about the alert actual severity into
KSAALERTS ODI table.
Additional Information: Currently, the alert severity
attribute is in the KSAALERTS attributes group, but it is not
the severity displayed in the SAP system; therefore, you
must add a new attribute to show the severity of CCMS
alerts in the Tivoli Enterprise Portal workspace.

------------------------
6.2.0-TIV-ITM_SAP-LA0011
------------------------

APAR: IZ70825
Abstract: Incorrect system down situation fired.
Additional Information: When the SAP system gives the wrong message
when connecting to the RFC, the mySAP agent treats this
situation as SAP System Down, and fires the System Down
situations, even though the SAP system is running.

APAR: IZ68793
Abstract: BCD_FIELD_OVERFLOW caused by V2_STAT_NORM_QUEUETI field
too small.
Additional Information: A BCD_FIELD_OVERFLOW ABAP dump caused by
V2_STAT_NORM_QUEUETI being too small. The root cause of the
problem is that the new SAP structure used in version 7.0 is
larger than the older structure.

APAR: IZ72895
Abstract: Operating system performance historical collection did
not update.
Additional Information: The historical data collected for the
Operating System Performance workspace looks wrong. The
attributes are never refreshed and are the same for the entire
collection interval, unless you manually or automatically
refresh the related Tivoli Enterprise Portal workspace.

APAR: IZ66593
Abstract: User for mySAP agent is created as communication user not
as system user.
Additional Information: Options are available so you can
configure the agent user ID and password in a property file.

APAR: IZ80917
Abstract: CX_SY_ARITHMETIC_OVERFLOW dump in /IBMMON/ITM_WORK_PROCESS
function module.
Additional Information: A CX_SY_ARITHMETIC_OVERFLOW ABAP dump was
caused by the /IBMMON/ITM_WORK_PROCESS function module.

Defect: 129450
Abstract: Enable offline node for inactive SAP instances.
Additional Information: An option is available so you can select
one of the two modes: offline for inactive instances and
online for inactive instances. If you want to choose the
'offline for inactive instances' mode, you must insert an
"OfflineForInactiveServer=YES' record into the
/IBMMON/ITM_CONFIG table; then the mySAP agent de-registers
the subnode for all inactive instances to make them display
as inactive in the Tivoli Enterprise Portal. By default,
this record is not in the table, and the mySAP agent keeps
online subnodes for inactive SAP instances. Because this is
the current behavior for the mySAP agent, this change does
not affect most of the users.

Defect: 134711
Abstract: In 4.6C/4.6D environment, it generates
ITM-FAILED_STAT_FILE_READ ABAP dump
Additional Information: An option is available to disable this ABAP
dump like in the 640 and 700 versions.

Defect: 131911
Abstract: CCMS alerts cause performance issues
Additional Information: The /IBMMON/ITM_CCMS_ALERTS function module
takes a long time to retrieve data from the SAP system, and
sometimes this action causes a performance issue. Performance
tuning has enhanced the codes of the /IBMMON/ITM_CCMS_ALERTS
function module to avoid the performance issue.

Defect: 130005
Abstract: ksar3 tools used to close CCMS alerts action
has performance issue.
Additional Information: In the current design, each time an alert is
closed, the ksar3 retrieves all alerts from the SAP system and
then finds the information for the alert to be closed.
Retrieving all alerts from the SAP system causes a big
performance issue. In the new design, the required information
to close an alert is collected when updating the alerts cache.
When closing an alert, the new ksar3 tool does not need to
retrieve all alerts from the SAP system, but closes the alert
directly.

Defect: 135881
Abstract: On Windows System, mySAP Agent process crashes randomly.
Additional Information: On Windows(R) systems, if there are multiple
instances of the mySAP agent monitoring different SAP Systems,
when the file size of dev_rfc.trc under %system_root%/system32
in general exceeds 8m, one of the mySAP agent processes stops
randomly. The ksaagent_<SID>.ras file is under
%system_root%/system32, and some STACK_OVERFLOW exceptions
are in this file.

Defect: 137011
Abstract: Fire events for closed CCMS alerts.
Additional Information: Currently the mySAP agent does not have the
capability of firing an event when a CCMS alert is closed in
SAP. This defect provides this function. You can define a new
situation with the condition 'Alert Status' equal to 'DONE' so
that an alert that is closed in CCMS can fire a event.

Enhancement: 127432
Abstract: Provides options to disable function modules during
importing the ABAP transport.
Additional Information: In the current version, the mySAP agent has
the capability of disabling function modules after importing
the ABAP transport, but cannot disable them when importing
the ABAP transport. Follow the instructions to disable the
function modules.

How to disable a function module when importing a transport:

1. Create a file named transport.prop under SAP work dir.
By default, the work directory must be /usr/sap/<SYSID>/
DVEBMGS<SYSNR>/work (for example, /usr/sap/U06/DVEBMGS10/work).
The value of the work directory can also be retrieved by the
'rdisp/workdir' parameter in the 'RZ11' transaction code.
2. Append a line such as <function_module>=NO to disable
<function module> (for example, /IBMMON/ITM_ALERTS=NO is to
disable /IBMMON/ITM_ALERTS function module).
3. Save all changes and grant read and write authority to the
corresponding sap admin user.
4. Import the ABAP transport packaged in this LA fix.
The function module is now disabled when importing the ABAP
transport and no extra actions are required after importing.

6.2.0-TIV-ITM_SAP-LA0010
------------------------
APAR: IZ75515
Abstract: Something is wrong with sorting by 'Average Response Time'
in Transaction Performance workspace
Additional Information: When an attribute in the ODI table is defined
as follows and without *OPTION: SORTBYINTERNAL in the
definition, a problem exists with this attribute in the Tivoli
Enterprise Portal when using it to sort the table view:
*TYPE I£¬4
*ENUM: Value_Exceeds_Minimum=-2147483648
*ENUM: Value_Exceeds_Maximum=2147483647


APAR: IZ73261
Abstract: The task type for each transaction code will be always
with same value
Additional Information: After opening the workspace with Query
Transaction Performance (620), the task type for each
transaction code always has the same value. This value
is incorrect because transaction workload statistical data
sometimes includes more than one task type.
This problem is introduced by IF0007.

The fix for this APAR, includes the following features
and fixes:

1. A new R/3_Trans_Perf_Task_Type attribute group
was added for recording the transaction workload
statistical data with task types (RFC, Dialog, Background,
HTTP, and so on) for each aggregation type as SAP ST03N.
The following aggregation value list for
R/3_Trans_Perf_Task_Type is valid:

TCODET: statistical data aggregated by Transaction Code
USERT: statistical data aggregated by User Id
TCUSET: statistical data aggregated by Transaction Code
and User Id
APPLT: statistical data aggregated by Application
SUBT: statistical data aggregated by Sub Application
DYNPRT: statistical data aggregated by DYNPRO
EXECIT: statistical data aggregated by EXECIN
PEXEIT: statistical data aggregated by Transaction Code
and EXECIN
UEXEIT: statistical data aggregated by User id and EXECIN


2. The original R/3_Transaction_Performance attribute group
records the statistical data ('All' as task type) in ST03N
for each aggregation type. The following aggregation value
list for R/3_Transaction_Performance is valid:

TCODE: statistical data aggregated by Transaction Code
USERID: statistical data aggregated by User Id
TCUSER: statistical data aggregated by Transaction Code
and User Id
APPL: statistical data aggregated by Application
SUB: statistical data aggregated by Sub Application
DYNPRO: statistical data aggregated by DYNPRO
EXECIN: statistical data aggregated by EXECIN
PEXEIN: statistical data aggregated by Transaction Code
and EXECIN
UEXEIN: statistical data aggregated by User id and EXECIN


3. Transaction Performance (620) is revised and defined under
the R/3_Trans_Perf_Task_Type attribute group. This attribute
retrieves transaction performance statistical data aggregated
by Transaction Code (aggregation type is 'TCODET') with
task type except 'All'.

If you want to look through transaction performance
statistical data aggregated by another aggregation type,
copy Transaction Performance (620) and define another
new query with your preferred aggregation type listed in the
above section 1.

For example: To look through the statistical
data with task types aggregated by user ID, follow these steps:

1) Open the Query Editor.
2) Select Transaction Performance (620) under the
R/3_Trans_Perf_Task_Type tree.
3) Click Create another query and define the name and
description of the new query.
4) Modify the aggregation value from 'TCODET' to 'USERT'.
5) Assign this query to your workspace to look through the
statistical data.

4. Because all values of column enservtype of R/3 Transaction
Performance are '0', the task type is 'All'. So if you want to
analyze the transaction performance statistical data stored in
the IBM Tivoli Monitoring Data Warehouse table to generate
reports about the transaction performance statistical data with
'Dialog' or another task type except the 'All' task type, use
R/3_Trans_Perf_Task_Type instead of R/3_Transaction_Performance.

If you want to analyze the transaction performance statistical
data stored in the IBM Tivoli Monitoring Data Warehouse table
to generate reports about the transaction performance
statistical data with the 'All' task type, use the
R/3_Transaction_Performance database table.

Example: To compare the sum of Dialog Steps for each Service
Type and aggregation type from the IBM Tivoli Monitoring
Data Warehouse, use the following SQL:

select SUM("Dialog_Steps"), "Service_Type", "Row_Aggregation"
from "R/3_Trans_Perf_Task_Type"
where "System_Name" = 'P73'
and "Service_Type_Encoded" = 'D'
and trunc(to_date(substr("Sample_Interval_End", 2, 12),
'YYMMDDHH24MISS'),'DD') < trunc(sysdate, 'DD')
and to_date(substr(("Sample_Interval_End"), 2, 12),
'YYMMDDHH24MISS') > to_date(sysdate - 1,
'DD.MM.YY HH24MI')
GROUP BY "Row_Aggregation", "Service_Type"

Enhancement: 127432
Abstract: Provide option to disable function modules during
importing the ABAP transport.
Additional Information: In the current version, the mySAP agent has
the capability of disabling function modules after importing
the ABAP transport, but cannot disable function modules while
importing the ABAP transport. An option is available to disable
the function modules when importing a transport. Follow the
instructions to disable the function modules.

How to disable function modules while importing a transport

1. Create a file named transport.prop under the SAP work
directory. By default, the work directory must be /usr/sap/
<SYSID>/DVEBMGS<SYSNR>/work (for example, /usr/sap/U06/
DVEBMGS10/work). The value of the work directory can also be
retrieved by the 'rdisp/workdir' parameter in the 'RZ11'
transaction code.
2. Append a line such as <function_module>=NO to disable
<function module> (for example, /IBMMON/ITM_ALERTS=NO is to
disable /IBMMON/ITM_ALERTS function module).
3. Save all changes and grant read and write authority to the
corresponding sap admin user.
4. Import the ABAP transport packaged in this LA fix.
The function modules are disabled when importing the ABAP
transport and no extra action is required after importing.

6.2.0-TIV-ITM_SAP-IF0008
------------------------
APAR: IZ61460
Abstract: ksar3 tool takes about 15 seconds or more time to close
an alerts under some SAP environments
Additional Information: When using the ksar3 tools to close an
alert, if the alert is still open, it takes about 15
seconds to close it; if the alert has been closed in the
Central CCMS of the SAP System, it takes more time
to close it.

APAR: IZ58705
Abstract: Sometimes the mySAP agent dumps the "(R70) No Data Found"
messages into the system log of SAP system.
Additional Information: When viewing the data of the
"Workload performance" workspace and some other workspaces,
the ABAP code of the mySAP agent calls
"SWNC_GET_STATRECS_FRAME", which is the standard function
module of the SAP system that gets the workload statistical
data. In some scenarios, the "SWNC_GET_STATRECS_FRAME"
function module returns the "(R70) No Data Found" error
message and the mySAP agent dumps it into the system log
of the SAP system. It is also requested by MR080409265.

Enhancement: 113937
Abstract: SYSLOG_HEARTBEAT_MESSAGE by default is not dumped into
system log of SAP System.
Additional Information: This enhancement is addressed by
MR0904095941, which requires the mySAP agent not to dump the
heartbeat mesage into the system log of the SAP system
SYSLOG_HEARTBEAT_MESSAGE to collect CCMS by default.

Enhancement: 115726
Abstract: "gethostbyname" error messages are dumped into system
log of SAP System.
Additional Information: This enhancement is addressed by
MR071309407. The mySAP agent calls the SAP kernel call,
'RFCControl', to retrieve the IP address using the host name
of the user's terminal. The "gethostbyname" error messages
are dumped into the system log of the SAP System by the
kernel call.

6.2.0-TIV-ITM_SAP-IF0007
------------------------
APAR: IZ52957
Abstract: IBM Tivoli Monitoring mySAP agent causes a high workload
on the TSTCT table of SAP system.
Additional Information: When there are many active users on an SAP
system, if the situations associated with the R/3_Active_Users
attribute group are started, the SAP
agent queries the TSTCT table and causes a high workload on
the TSTCT table, which is a system table of the SAP system.

APAR: IZ52571
Abstract: Cyrillic characters are incorrectly displayed when the
mySAP agent is monitoring the non-unicode SAP system.
Additional Information: The agent does not translate the Russian
characters when it runs on Russian (RU) systems. As a result,
the Russian characters are not displayed correctly in the
relevant Tivoli Enterprise Portal workspaces.

Defect: 101350
Abstract: After restarting the monitored SAP system, the agent
fails to get a valid RFC handle.
Additional Information: The agent C/C++ code cannot get a valid
RFC handle after the monitored SAP system is restarted.
As a result, many error messages about RFC connection
failures are included in the agent logs.

Enhancement: 100201
Abstract: CCMS current state support added to the 620 release.
Additional Information: This enhancement is addressed by
MR0312086126, which requires the mySAP agent to collect CCMS
alerts and report the "Current State" of the centralized CCMS
environment. Without this enhancement, the CCMS alerts are
retrieved from the "Open alerts" view, which is a type of
historical data. But the customer expects to see the real-time
status of the CCMS MTE, which must be retrieved from the
"Current State" view.

Enhancement: 100132
Abstract: Add the R/3_Alert_System_Up situation.
Additional Information: This enhancement is addressed by
MR0311096430,which requires the agent to provide the
R/3_Alert_System_Up predefined situation to notify the
SAP System restart event. When the agent is running and the
SAP system is restarted, the R/3_Alert_System_Down and
R/3_Alert_System_Up situations are subsequently triggered.

Enhancement: 101467
Abstract: Add the new Dialog Steps column in the KSAPERF odi
table for the R/3_Service_Response_Time attribute group.
Additional Information: This enhancement is addressed by
MR0625083051. By appending the new Dialog Steps column in the
KSAPERF ODI table for the R/3_Service_Response_Time attribute
group, you can assign the new "Service Response (620)" query
to a new workspace or an existing workspace to show
the number of dialog steps for each service type that has been
executed per day on the Tivoli Enterprise Portal.

Enhancement: 101744
Abstract: Add the Service Type attribute to the KSATRANST odi
table for the R/3_Trans_Perf_Task_Type attribute group.
Additional Information: This enhancement is addressed by
MR0625083051. By appending the new "Service Type" and "Encode
Service Type" attributes in the KSATRANS ODI table for the
R/3_Trans_Perf_Task_Type attribute group, you can assign the
new "Transaction Performance (620)" query to a new workspace or
an existing workspace to display the service type information
for the transaction performance data on the Tivoli Enterprise
Portal.

6.2.0-TIV-ITM_SAP-IF0006
------------------------
APAR: IZ42127
Abstract: ABAP dump is caused by the DBREALTIME field overflow
in the /IBMMON/ITM_WORK_PROCESSES function module.
Additional Information:
ABAP dump "BCD_OVERFLOW" occurs when data collection is
requested for the R/3_Work_Process attribute group and
the value of the Database_Reads_Time attribute exceeds
the maximum value of an integer.

Defect: 92089
Abstract: ABAP dump occurs while calling the /IBMMON/ITM_HOSTS
function module.
Additional Information: ABAP SYSTEM_FAILURE and
COMMUNICATION_FAILURE exceptions occur in the
/IBMMON/ITM_GET_FILE_NAMES_ALL function module if some
instances are unavailable.

6.2.0-TIV-ITM_SAP-LA0005
------------------------
APAR: IZ37608
Abstract: ERROR in /IBMMON/ITM_HOSTS to check system type for the
mySAP agent.
Additional Information: The system type check for the
unicode_system variable returns an error on the little-endian
SAP system when the agent ABAP code is running with
Simplified Chinese (ZH), Traditional Chinese (ZF), Korean( KO),
Japanese (JP), or Thai (TH) languages. As a result, the node is
not registered and the node is not displayed on the Tivoli
Enterprise Portal for the mySAP agent.

Defect: 88246, 88357, 88359
Abstract: Add 32-bit overflow check on the following odi tables:
KSAOFFICE, KSATRANRFC, KSADUMPS, KSAEDIFILE and KSAGWYSTAT.
Additional Information: When the values of some attributes in
these ODI tables exceed the maximum value of an integer,
an ABAP dump is generated.

6.2.0-TIV-ITM_SAP-LA0004
------------------------

APAR: IZ33843
Abstract: ABAP dumps related to statistics data collection.
Additional Information:
ABAP dump "ITM-ITM-ILED_STAT_FILE_READ_REMOTE"
occurs when the data collection is requested for
R/3_Transaction_Performance and R/3_Service_Response_Time and
these statistical data collection function modules cannot
collect the data from the SAP systems. This problem was
introduced in the 6.2.0-TIV-ITM_SAP-LA0002 release.

Defect: 82823
Abstract: mySAP agent predefined take action commands such as
Close Alerts fail with exit code 4.
Additional Information:
mySAP agents running on Windows systems require an additional
step to fully resolve this problem. See the "Known Problems
and Workarounds" section for additional information.
For mySAP agents running on UNIX(R) or Linux systems, no
additional steps are necessary.

6.2.0-TIV-ITM_SAP-LA0003
-------------------------

APAR: IZ28117
Abstract: mySAP agent returns incorrect data for Transaction
Performance.
Additional Information:
When summarizing Transaction Performance, summarization columns
such as MIN_, MAX_, SUM_, and AVG_ are not being reported for
the Dialog_Step attribute.

APAR: IZ27587
Abstract: AE IZ20878 fix completion. LA02 does not report Transaction
Performance attribute fields.
Additional Information:
This problem was introduced in 6.2.0-TIV-ITM_SAP-LA0002.
This problem results in incorrect warehouse data for the
Transaction Performance attributes.

APAR: IZ25758
Abstract: The 'SYSCP-DYNCP-AGTCP' message is displayed multiple times
in SYSLOG.

APAR: IZ29271
Abstract: mySAP agent shut down automatically.
Additional Information:
An operating System SIGHUP signal received by the mySAP agent
causes it to shut down automatically.


Enhancements:
-------------
This fix provides the following additional
capabilities and functions:

FITS (fully integrated tool set) requirements addressed:
MR083007185 - Add ability to configure the agent to connect to an
SAP system through a logon group.

This capability is provided through the specification of four new
environment variables and the requirement to configure the
agent with the real SAP system identifier (SID) instead of a
3-character identifier.

1. New environment variables:
SAPLOGONGROUP - Name of the SAP logon group.

SAPMSGSERVER - Host name of the SAP message server. An IP
address is also acceptable.

SAPMSGSERVICE - Message service name (example, sapmsTV1) or
full Message service port number (example, 3601)

Note: Service names, if used, must be included in the
operating system services files:
- UNIX systems: /etc/services
- Windows systems: \windows\system32\drivers\etc\services

SAPROUTESTRING - Route string to the SAP system.

2. Existing environment variables:
SAPSYSTEMNAME - 3-character SAP system identifier (SID). Any
3-character identifier can be used with the mySAP agent,
but for logon group support, this value must
be the exact SID value of the SAP system.

3. Configuring the agent to connect using a logon group:
A) Ensure that the value entered for the System Identifier
when the agent is originally configured is the real SID
of the SAP system. If this value is different, configure a
new instance of the agent using the real SID.

B) Set the new environment variables described above. The new
environment variables must be set manually in the agent
configuration file. Perform the manual updates on the
computer where the mySAP agent is installed.

UNIX systems:
1. Go to the CANDLEHOME/config directory.
2. Edit the sa_<SID>.config file.

Windows systems:
1. Go to the CANDLEHOME/tmaitm6 directory.
2. Edit the KSAENV_<SID> file.

UNIX and Windows systems:
3. Add the following required environment variables:
SAPLOGONGROUP
SAPMSGSERVER
SAPMSGSERVICE
4. Add the following optional environment variables,
if needed:
SAPROUTESTRING
5. Restart the mySAP agent.

Example:
Edit the sa_GS3.config file (on UNIX systems) or the
KSAENV_GS3 file (on Windows systems) to add the
following values:
SAPLOGONGROUP='GS3_LOGON_GRP'
SAPMSGSERVER='gs3host'
SAPMSGSERVICE='sapmsGS3'

C) Limitations and considerations
1. Support is not provided for a logon group name with
leading or trailing blanks. Logon group names with
embedded blanks are supported.
2. Support is not provided for logon group names with
double-byte characters.
3. Support is explicitly provided for logon group names
consisting of the following single-byte characters:
- A-Z
- a-z
- 0-9
- underscore (_)
- hyphen (-)
- periond (.)
- colon (:)
- plus (+)
- at (@)
- embedded blanks
4. Logon group processing is enabled by the presence of the
SAPLOGONGROUP environment variable.
- If this variable is present, then logon group
processing is in effect and the SAPMSGSERVER and
SAPMSGSERVICE variables must be set.
- If this variable is not present, then the existing
method of SAP system logon using application server
information is in effect.
5. Logon group support can be used with the mySAP agent
ksar3exe and ksar3nfy utilities. This support is
activated for the utilities by updating their wrapper
scripts with the new environment variables.

4. Use of logon groups with remote deployment:
A) Logon group specifications can be used with mySAP agent
remote deployment. The new remote deployment parameters are as
follows:

SAPSETTINGS.sap_logongroup
SAPSETTINGS.sap_msgserver
SAPSETTINGS.sap_msgservice
SAPSETTINGS.sap_routestring

Example:
tacmd addSystem -t SA -n tiv35:KUX -p INSTANCE=GS3
SAPSETTINGS.sap_systemno=00
SAPSETTINGS.sap_clientno=000
SAPSETTINGS.sap_logongroup="GS3_LOGON_GRP "
SAPSETTINGS.sap_msgserver=gs3host.ibm.com
SAPSETTINGS.sap_msgservice=sapmsGS3
SAPSETTINGS.sap_routestring=/H/9.181.27.61/H/
SAPSETTINGS.sap_userid=IBMMON_AGENT
SAPSETTINGS.sap_password=pwagent
SAPSETTINGS.sap_language=EN

B) Enabling remote deploy
For remote deployment to function correctly with the
new parameters, some mySAP configuration files must be
updated, as follows:

UNIX systems:
1. Edit the CANDLEHOME/config/sa.ini file.
2. Add the following lines:
SAPLOGONGROUP=$SAPLOGONGROUP$
SAPMSGSERVER=$SAPMSGSERVER$
SAPMSGSERVICE=$SAPMSGSERVICE$
SAPROUTESTRING=$SAPROUTESTRING$
3. Edit the CANDLEHOME/config/.ConfigData/ksaenv file.
4. Add the following lines:
default|SAPLOGONGROUP|
default|SAPMSGSERVER|
default|SAPMSGSERVICE|
default|SAPROUTESTRING|

Note: For Windows systems, all updates to the mySAP
configuration files are performed by the patch installation.

C) Limitations
1. When remote deployment is used on a Windows system, the
new logon group parameters are stored in the Windows
Registry. Values set in the Windows Registry override
any values set in the KSAENV_<SID> file. When you use
remote deployment on Windows systems, you must continue
to use remote deployment to set the agent parameters
because manual updates to the KSAENV_<SID> file are no
longer processed.

6.2.0-TIV-ITM_SAP-LA0002
-------------------------

APAR: IZ20878
Abstract: The mySAP agent stops reporting data to the Tivoli
Enterprise Portal Server (portal server) for extended periods
of time.
Additional Information:
The mySAP agent performance is degraded when the
agent is monitoring SAP distributed statistics records (that use
R/3_Service_Response_Time or R/3_Transaction_Performance
situations) on an SAP system that has a high volume of
statistical records. This performance degradation affects the
response time for all mySAP situations running at the same time.
The agent has been modified to optimize SAP statistics data
collection and improve agent performance.

APAR: IZ17077
Abstract: The "DISPLAY ITEM" FOR "R/3_ALERT_SYSTEM_DOWN" situation
does is not displayed correctly on the Tivoli Enterprise Portal
(portal).
Additional Information:
Japanese characters are missing from the R3_Alerts_System_Down
message. The problem occurs only on non-Unicode double-byte
language mySAP systems when the logon language is a double-byte
language.

APAR: IZ06262
Abstract: SCALE/PREC is not applied to long-term history query
attributes
Additional Information:
Agent queries such as "Buffer Performance (610)" that filter on
an integer attribute return no long-term data from the
warehouse. An error message similar to the following error
message is displayed in the Tivoli Enterprise Portal Server
log: SQL0401N. The data types of the operands for the operation
">=" are not compatible.

Defect: 65616
Abstract: Situations do not fire for Managed Group Subnodes.

Defect: 73167
Abstract: Bogus value for R/3_Operating_System_Performance from the
/IBMMON/ITM_OS_PERF function module.
Additional Information:
This problem was introduced in 6.2.0-TIV-ITM_SAP-LA0001.


6.2.0-TIV-ITM_SAP-LA0001
-------------------------

APAR: IZ05536
Abstract: The ITM6 mySAP Agent Memory workspace fails to return
metrics in a non-English SAP environment.
Additional Information: In a non-English SAP environment,
the R/3_Buffer_Performance.Name attribute gets the values from
the SAP system in non-English. The Tivoli Enterprise Portal
Server workspace filter values are in English (Extended Memory,
Heap Memory, Page Area, and Roll Area). Therefore, the portal
server filter values do not match the values returned and no
data is displayed in the workspace views. Tivoli Enterprise
Portal Server workspace queries were modified to use the
R/3_Buffer_Performance.Encoded_Name attribute.

APAR: IZ13182
Abstract: BCD-OVERFLOW with exception CX_SY_CONVERSION_OVERFLOW
occurs in /IBMMON/ITM_TRAN_PERF
Additional Information:
The problem results in an ABAP dump in the agent-provided
ITM_TRAN_PERF function module.

APAR: IZ14058
Abstract: Modify ITM 6.2 ABAP transports compatible for repackaging.
Additional Information:
Agent-supplied transports have been modified so you can
repackage these transports on your SAP systems.

APAR: IZ15745
Abstract: BCD_ZERODIVIDE with exception CX_SY_ZERODIVIDE
Additional Information:
SAP system user IDs that include spaces cause a zero divide
exception in the agent-provided ITM_TRAN_PERF function module.

APAR: IZ16617
Abstract: mySAP agent function ITM_GWY_CONNECTIONS raises the
"GWY_MONITOR_DISABLED"exception condition.
Additional Information:
This problem occurs even when gateway monitoring is correctly
enabled on the SAP instance being monitored and results in an
ABAP dump in the ITM_GWY_CONNECTIONS mySAP agent function.
The problem is specific to SAP systems with multiple application
server instances.

APAR: IZ16866
Abstract: ABAP Dump BCD-OVERFLOW with exception
CX_SY_CONVERSION_OVERFLOW occurs in /IBMMON/ITM_ORA_DETAIL.
Additional Information:
The problem results in an ABAP dump in the agent-provided
/IBMMON/ITM_ORA_DETAIL function module.

APAR: IZ18167
Abstract: ABAP Dump CONVT_NO_NUMBER with exception
CX_SY_CONVERSION_NO_NUMBER
Additional Information:
The problem results in an ABAP dump in the agent-provided
/IBMMON/ITM_WORK_PROCESSES function module and an
additional "Unable to interpret "**" as a number" error message.
This problem is specific to SAP application servers running more
than 99 work processes.

APAR: IZ19279
Abstract: Managed groups are not defined for new central CCMS
systems.
Additional Information:
New managed groups are not automatically defined when alerts
from new SAP systems are passed from the monitored SAP Central
CCMS system to the mySAP agent code.

APAR: IZ18815
Abstract: ABAP Dump BCD-OVERFLOW occurs in /IBMMON/ITM_IDOCS
Additional Information:
The problem results in an ABAP dump in the agent-provided
/IBMMON/ITM_IDOCS function module.

APAR: IZ19337
Abstract: ABAP Dump COMPUTE_INT_PLUS_OVERFLOW occurs in
the agent-provided /IBMMON/ITM_OS_PERF function module.
Additional Information:
The problem results in an ABAP dump in the agent-provided
/IBMMON/ITM_OS_PERF function module.

APAR: IZ10788
Abstract: Existing historical collection does not start on a newly
created SAP agent instance.

APAR: IZ11119
Abstract: The user ID that calls the CCMS MONITOR needs additional
SAP authority to be able to receive this central CCMS data.
Additional Information:
The agent-provided ZITM_620AUTH role and profile does not have
the authorities required to obtain alerts from a Centralized
CCMS system. This problem resulted in missing alerts in the
Alerts workspace. The required authorities are added to
the ZITM_620AUTH role, the ZITM_620AUTH profile, and the
IBMMON_AGENT user ID.

3.0 Architecture and prerequisites
===================================
This fix is supported on the following operating systems:

Windows:
Windows 2000 Server (32-bit)
Windows 2000 Advanced Server (32-bit)
Windows Server 2003 Data Center Edition (32-bit)
Windows Server 2003 Enterprise Edition (32-bit)
Windows Server 2003 Standard Edition (32-bit)

UNIX and Linux:
AIX 5.2, 5.3 (32-bit and 64-bit)
HP-UX 11i V1, V2, V3 for PA-RISC (32-bit and 64-bit)
HP-UX 11i V2, V3 for Integrity (64-bit)
Red Hat Enterprise Linux 2.1, 3.0, 4.0, 5.0 for x86-32 (32-bit)
Solaris 8, 9, 10 for SPARC (32-bit and 64-bit)
Solaris 10 for x86-64 (64-bit)
SUSE Linux Enterprise Server 8, 9, 10 for x86-32 (32-bit)
SUSE Linux Enterprise Server 8, 9, 10 for System z (64-bit)
SUSE Linux Enterprise Server 10 (x86-64)
SUSE Linux Enterprise Server 9 (x86-64)
Redhat Linux Enterprise Server 5 (x86-64)
Redhat Linux Enterprise Server 4 (x86-64)

Newly supported operating systems for SAP Agent 6.2 IF16:

  • AIX 7.1 (64-bit)
  • RHEL 6 32bit
  • RHEL 6 64 bit
  • Windows 2008 R2 EE 64bit
  • Solaris 11 x86_64 64bit
  • Solaris 11 SPRC 64bit
Newly supported ITM for SAP Agent 6.2 IF16:
  • ITM623FP3

The following link is for the Tivoli operating system and application
support matrix. See this matrix for the latest certification
information.

http://www.ibm.com/software/sysmgmt/products/support/Tivoli_Supported_Platforms.html

The following website contains the latest certification information:
Software Product Compatibility Reports (SPCR)
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 for Applications: mySAP agent, Version 6.2.0

- IBM Tivoli Monitoring, Version 6.2.0

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

4.0 Image directory contents
=============================
This fix image contains the following files:
- 6.2.0-TIV-ITM_SAP-IF0016.README - This README file
- 6.2.0-TIV-ITM_SAP-IF0016.tar - Fix archive .tar format
- 6.2.0-TIV-ITM_SAP-IF0016.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 environment; use the .zip file if
you are working in a Windows environment.

The fix archive file contains the following files:
6.2.0-TIV-ITM_SAP-IF0016/ksa_winnt_tema_IF0016.cab - Binaries for Windows
6.2.0-TIV-ITM_SAP-IF0016/KSAWINNT.dsc - Descriptor file for Windows
6.2.0-TIV-ITM_SAP-IF0016/ksaaix523.dsc - Descriptor file for AIX 32-bit
6.2.0-TIV-ITM_SAP-IF0016/ksaaix526.dsc - Descriptor file for AIX 64-bit
6.2.0-TIV-ITM_SAP-IF0016/ksahp11.dsc - Descriptor file for HP-UX 32-bit
6.2.0-TIV-ITM_SAP-IF0016/ksahp116.dsc - Descriptor file for HP-UX 64-bit
6.2.0-TIV-ITM_SAP-IF0016/ksahpi116.dsc - Descriptor file for HP-UX Itanium
6.2.0-TIV-ITM_SAP-IF0016/ksali6242.dsc - Descriptor file for Linux on Intel
6.2.0-TIV-ITM_SAP-IF0016/ksali6243.dsc - Descriptor file for Linux on Intel
6.2.0-TIV-ITM_SAP-IF0016/ksali6263.dsc - Descriptor file for Linux on Intel
6.2.0-TIV-ITM_SAP-IF0016/ksals3246.dsc - Descriptor file for Linux 64-bit
6.2.0-TIV-ITM_SAP-IF0016/ksals3266.dsc - Descriptor file for Linux 64-bit
6.2.0-TIV-ITM_SAP-IF0016/ksasol283.dsc - Descriptor file for Solaris 8 32-bit
6.2.0-TIV-ITM_SAP-IF0016/ksasol286.dsc - Descriptor file for Solaris 8 64-bit
6.2.0-TIV-ITM_SAP-IF0016/ksasol606.dsc - Descriptor file for Solaris 10 Opteron 64-bit
6.2.0-TIV-ITM_SAP-IF0016/sa_dd_06200016.xml - xml file
6.2.0-TIV-ITM_SAP-IF0016/sa_dd.properties - File for product properties
6.2.0-TIV-ITM_SAP-IF0016/ABAP/K620_00055.ITM - Control file for non-Unicode version of Transport
6.2.0-TIV-ITM_SAP-IF0016/ABAP/R620_00055.ITM - Data file for non-Unicode version of Transport
6.2.0-TIV-ITM_SAP-IF0016/ABAP/K620_00055U.ITM - Control file for Unicode version of Transport
6.2.0-TIV-ITM_SAP-IF0016/ABAP/R620_00055U.ITM - Date file for Unicode version of Transport
6.2.0-TIV-ITM_SAP-IF0016/ABAP/K620_00055_DELETE.ITM - Delete Transport
6.2.0-TIV-ITM_SAP-IF0016/ABAP/R620_00055_DELETE.ITM - Delete Transport
6.2.0-TIV-ITM_SAP-IF0016/ksa_tems_teps_tepd_IF0016.tar - Support files for UNIX IBM Tivoli Enterprise Monitoring Server/Tivoli Enterprise Portal Servers
6.2.0-TIV-ITM_SAP-IF0016/ksa_tems_teps_tepd_IF0016.zip - Support files for Windows IBM Tivoli Enterprise Monitoring Server/Tivoli Enterprise Portal Servers
6.2.0-TIV-ITM_SAP-IF0016/ksa_aix523_tema_IF0016.tar - Binaries for AIX 32-bit
6.2.0-TIV-ITM_SAP-IF0016/ksa_aix526_tema_IF0016.tar - Binaries for AIX 64-bit
6.2.0-TIV-ITM_SAP-IF0016/ksa_hp11_tema_IF0016.tar - Binaries for HP-UX 32-bit
6.2.0-TIV-ITM_SAP-IF0016/ksa_hp116_tema_IF0016.tar - Binaries for HP-UX 64-bit
6.2.0-TIV-ITM_SAP-IF0016/ksa_hpi116_tema_IF0016.tar - Binaries for HP-UX Itanium
6.2.0-TIV-ITM_SAP-IF0016/ksa_li6242_tema_IF0016.tar - Binaries for Linux on Intel
6.2.0-TIV-ITM_SAP-IF0016/ksa_li6243_tema_IF0016.tar - Binaries for Linux on Intel
6.2.0-TIV-ITM_SAP-IF0016/ksa_li6263_tema_IF0016.tar - Binaries for Linux on Intel
6.2.0-TIV-ITM_SAP-IF0016/ksa_lx8263_tema_IF0016.tar - Binaries for Linux 64-bit on Intel
6.2.0-TIV-ITM_SAP-IF0016/ksa_ls3246_tema_IF0016.tar - Binaries for Linux 64-bit
6.2.0-TIV-ITM_SAP-IF0016/ksa_ls3266_tema_IF0016.tar - Binaries for Linux 64-bit
6.2.0-TIV-ITM_SAP-IF0016/ksa_sol283_tema_IF0016.tar - Binaries for Solaris 8 32-bit
6.2.0-TIV-ITM_SAP-IF0016/ksa_sol286_tema_IF0016.tar - Binaries for Solaris 8 64-bit
6.2.0-TIV-ITM_SAP-IF0016/ksa_sol606_tema_IF0016.tar - Binaries for Solaris 10 Opteron 64-bit

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 <CANDLEHOME> symbol 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 CANDLEHOME
environment variable to the IBM Tivoli Monitoring installation
directory.

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

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

5.2 Local agent update
--------------------------
1. Transfer the appropriate archive file
(6.2.0-TIV-ITM_SAP-IF0016.tar or .zip) to a temporary
directory on the system that contains the agent code
to be updated. For the purpose of this README, the <TEMP> symbol
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
unzip utility on Windows systems. Expanding the file 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 about the itmpatch
command, see section 6.2.

On UNIX systems, if the fix was expanded to
<TEMP>/6.2.0-TIV-ITM_SAP-IF0016, the install command is:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.0-TIV-ITM_SAP-IF0016/ksa_xxxxxx_tema_IF0016.tar

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

In the following example, the file is ksa_li6243_tema_IF0016.tar.
> ./cinfo -i
Monitoring Agent for mySAP agent
li6243 Version: 06.20.00.16 Build: <build date>
<run the command on your system and find the real build date>

On a Windows system, if the fix was expanded to
<TEMP>/6.2.0-TIV-ITM_SAP-IF0016, the install command is:

> itmpatch -h <CANDLEHOME>
-i <TEMP>\6.2.0-TIV-ITM_SAP-IF0016\ksa_winnt_tema_IF0016.cab


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

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

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 about the tacmd addBundles command, see the IBM Tivoli
Monitoring Command Reference.

On UNIX systems,
if the fix was expanded to <TEMP>/6.2.0-TIV-ITM_SAP-IF0016
>$CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.2.0-TIV-ITM_SAP-IF0016

On Windows systems,
if the fix was expanded to <TEMP>\6.2.0-TIV-ITM_SAP-IF0016
>%CANDLE_HOME%\bin\tacmd addBundles -n -i <TEMP>\6.2.0-TIV-ITM_SAP-IF0016

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. 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.

On Windows systems,
if the fix was expanded to <TEMP>\6.2.0-TIV-ITM_SAP-IF0016
>%CANDLE_HOME%\bin\tacmd addBundles -n -i <TEMP>\6.2.0-TIV-ITM_SAP-IF0016

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. 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. After "tacmd addBundles.." from step 3 above, control files
on the Tivoli Enterprise Monitoring Server and the
Tivoli Enterprise Portal Server must be updated.
These updates must be done manually.

a. Tivoli Enterprise Monitoring Server update
The sa_dd_06200016.xml and sa_dd.properties files must be
copied from the <TEMP>/6.2.0-TIV-ITM_SAP-IF0016 directory to
the 062000000 version of the Tivoli Enterprise Monitoring
Services depot.

Two scripts are provided to make these copies and are located
in the fix <TEMP>/6.2.0-TIV-ITM_SAP-IF0016 directory after
the expansion of the tar or zip file:

ksa_patchdepot.bat - Windows
ksa_patchdepot.sh - UNIX

From the <TEMP>/6.2.0-TIV-ITM_SAP-IF0016 directory, run the
appropriate script based on the operating system. The script
output details the copies being made.

b. Tivoli Enterprise Portal Server update
Resource files must be copied from the
<TEMP>/6.2.0-TIV-ITM_SAP-IF0016 directory to the Tivoli
Enterprise Monitoring Portal directory.

Two scripts are provided to make these copies. The scripts are
located in the fix <TEMP>/6.2.0-TIV-ITM_SAP-IF0016 directory
after the expansion of the tar or zip file:

ksa_patch_resource_teps.bat - Windows
ksa_patch_resource_teps.sh - UNIX

From the <TEMP>/6.2.0-TIV-ITM_SAP-IF0016 directory, run the
appropriate script based on the operating system. The script
output contains details about the copies being made.

5. If you are using remote deployment to deploy the mySAP agent to
UNIX systems and you are using the new logon group functionality,
then you must update the agent control files on the UNIX system
as described in section "2.3 Enhancements." If you do not update
these files in advance, you must manually edit the
sa_<SID>.config file to add the logon group parameters.

6. 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 about the
tacmd login and updateAgent commands, see the "IBM Tivoli
Monitoring Command Reference."

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 sa
-n <Managed system name>
-v 06200016

On a Windows system:
> %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 sa
-n <Managed system name>
-v 06200016

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

5.4 Agent support update
------------------------
This fix (6.2.0-TIV-ITM_SAP-IF0016) includes changes to the agent
support files that must be installed. If you have already
installed these updates, there are no additional installation
steps. Otherwise, use the following steps to update the Tivoli
Enterprise Monitoring Server, Tivoli Enterprise Portal Server, or
Tivoli Enterprise Portal Desktop.

1. Transfer the appropriate archive file (6.2.0-TIV-ITM_SAP-IF0016.tar
or .zip) to the Tivoli Enterprise Monitoring Servers, Tivoli
Enterprise Portal Servers, or Tivoli Enterprise Portal Desktops.

2. Expand the archive file using the tar command on UNIX systems or
an unzip utility on Windows systems. Expanding the file creates a
directory structure that contains fixes for all supported
platforms.

3. Expand the archive file (ksa_tems_teps_tepd_IF0016.tar or .zip)
that contains the updates for the Tivoli Enterprise Monitoring
Server, Tivoli Enterprise Portal Server, and Tivoli Enterprise
Portal Desktop using the tar command on UNIX systems or an unzip
utility on Windows systems. Expanding the file creates a directory
structure that includes a subdirectory called CD-ROM, with the
necessary updates.

4. Start the Application Support Installer GUI to install
the fix. The GUI install can be started by using one of the
following commands from within the CD-ROM directory where
setup.jar is located:

On UNIX systems, GUI install:
> ./itmasi.sh

On Windows systems, GUI install:
> < itmasi

For a GUI install, when prompted by the Application Support
Installer for the installable media directory, select the CD-ROM
directory, not the component directory. The installer can install
updates for multiple components at the same time.

5. For a GUI install, the next panel presented by the Application
Support Installer asks for the selection of the Tivoli Monitoring
components to which you want to add application support.
For this fix, the check boxes must be as follows:

checked - Tivoli Enterprise Monitoring Server (TEMS)
checked - Tivoli Enterprise Portal Server (TEPS)
checked - Tivoli Enterprise Desktop Client (TEPD)

Continue through the remaining GUI panels by selecting the mySAP
Agent - 06.20.00.16 support to complete the installation.

6. If the Tivoli Enterprise Portal Desktop or Tivoli Enterprise
Portal Browser was running when the update was installed, it must
be restarted.


5.5 Installing mySAP agent transport
------------------------------------
This procedure installs the SAP transport into the mySAP system. You
are not required to uninstall the previous transport before installing
this transport.

1. Go to the ABAP directory in the location where you expanded the
fix archive file.

2. Copy the transport files into the mySAP environment as follows:
a. The transport files are located in the ABAP directory of the
mySAP agent fix archive. The following three sets
of transport files are in the directory:

1) K620_00055.ITM and R620_00055.ITM
These files are non-Unicode versions of the transport.

2) K620_00055U.ITM and R620_00055U.ITM
These files are Unicode versions of the transport.

3) K620_00055_DELETE.ITM and R620_00055_DELETE.ITM
These transport files remove the ABAP code. The DELETE
transport does not need to be imported, unless you stop
using the product entirely and want to remove the
transports from your mySAP systems.

b. Determine which transport is required for your mySAP system:
Unicode or non-Unicode.

c. Copy your transport files to the mySAP Transport System data
directory as follows:
non-Unicode transport
1) Copy the K620_00055.ITM file to the cofiles directory.
2) Copy the R620_00055.ITM file to the data directory.
or
Unicode transport
1) Copy the K620_00055U.ITM file to the cofiles directory.
2) Copy the R620_00055U.ITM file to the data directory.

3. Run the following non-Unicode and Unicode commands where:
SID Target mySAP : system ID
PROFILE_NAME : Name of the tp profile file
nnn : Number for the target client where the agent is to run
non-Unicode
tp addtobuffer ITMK620_00055 SID
pf=\usr\sap\trans\bin\PROFILE_NAME
tp import ITMK620_00055 SID client=nnn U16
pf=\usr\sap\trans\bin\PROFILE_NAME
Unicode
tp addtobuffer ITMK620_00055U SID
pf=\usr\sap\trans\bin\PROFILE_NAME
tp import ITMK620_00055U SID client=nnn U16
pf=\usr\sap\trans\bin\PROFILE_NAME

Alternately, you can use the mySAP STMS transaction to import the
transport requests. Ensure that the Import Transport Request Again
and the Overwrite Objects in Unconfirmed Repairs options are checked
on the Import Options tab of the Import Transport Request window.

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

6.1 Installation instructions for agent baroc file
------------------------------------------------------

This fix (6.2.0-TIV-ITM_SAP-IF0016) includes changes to the agent
baroc files that must be reinstalled. If you have already
installed these baroc files, there are no additional installation
steps. If you have not installed the files, refer to the "IBM Tivoli
Monitoring, Version 6.2.0, Installation and Setup Guide" under
"Installing monitoring agent baroc files on the event server" in the
"Installing the IBM Tivoli Enterprise Console Event Synchronization"
section for more information.

6.2 Additional information on using the 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 path must include the
drive letter.

6.3 Verifying the update
------------------------
1. To verify that the agent was updated correctly, use the tacmd
command to view the current version of the agent after the agent
is restarted. You are required to log in to a Tivoli Enterprise
Monitoring Server before 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 sa

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 sa

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

When the agent update is successful, the agent version is
06.20.00.16.

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

When the agent update is successful, the agent version is:
06.20.00.16

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

For the agent on Windows systems, the version number is
06.20.00.16.
For the agent on UNIX systems, the version number is
06.20.00.16.

2. To verify that the agent support files were updated correctly,
use the kincinfo command on Windows systems or the cinfo command
on Linux or UNIX systems. The sample output below shows the versions
of the Tivoli Enterprise Portal Server, Tivoli Enterprise Monitoring
Server, or Tivoli Enterprise Portal Desktop systems after this
fix has been successfully applied.

Note:
- The date of the build displayed might not be accurate. This is
a known problem.

On Windows systems:
--------------------
To validate that all components have been installed, run the
following command:

For example:
> %CANDLE_HOME%\InstallITM\kincinfo -i

>kincinfo -i
************ Monday, Aug 20, 2013 11:07:08 PM ************
User : Administrator Group : NA
Host Name : TIVE38 Installer : Ver: 062202000
CandleHome : E:\IBM\ITM
Installitm : E:\IBM\ITM\InstallITM
****************************************************************
...Product Inventory

Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal
Server, and Tivoli Enterprise Portal Desktop update:

SA mySAP Support
WINNT Version: 06.20.00.16 Build: 201308190814

SA mySAP Support
WINNT Version: 06.20.00.16 Build: 201308190814

SA mySAP Support
WINNT Version: 06.20.00.16 Build: 201308190814

6.4 Upgrade the SAP agent from version 6.2 to 7.1
--------------------------------------------------
On the UNIX platform, if the host name is greater than 8 digits you
cannot upgrade the SAP agent from version 6.2 to 7.1. Also, you cannot
start and stop the agent.
To solve this problem, complete the following steps:
1. For the UNIX platform, add or edit the CTIRA_SYSTEM_NAME variable
in the sa.ini file to your host name.
For example, CTIRA_SYSTEM_NAME=$RUNNINGHOSTNAME$
2. Complete the steps to upgrade and start and stop the agent again.

On the Solaris 9 32-bit SPARC platform, you cannot upgrade the SAP
agent from version 6.2 to 7.1.
To solve this problem, complete the following steps:
1. For the Solaris 9 32-bit SPARC platform, add or edit the
CTIRA_SYSTEM_NAME variable in the sa.ini file to your host name.
For example, CTIRA_SYSTEM_NAME=$RUNNINGHOSTNAME$
2. Complete the steps to upgrade and start and stop the agent again.

7.0 Known problems and workarounds
===================================
Problem:
'Close more severe alerts than current state' not working.

Workaround:
After enabling 'Close more severe alerts than current state'
please enable 'Green Alerts' option also.

Problem:
On Windows operating systems, Take Action commands that invoke ksar3
report exit code 4, even when the action is completed successfully.

Workaround:
On Windows operating systems, create a back up copy of
<ITM_HOME>\TMAITM6\ksar3.bat. Then, open the
<ITM_HOME>\TMAITM6\ksar3.bat file and change the last two lines as
indicated below. The value on the left is the original code.
The value on the right is the new code.

start /min ksar3exe.exe %1 == change to ====> call ksar3exe.exe %1
exit == change to ====> exit %ERRORLEVEL%

Problem:
Importing the ABAP transport fails with ABAP dumps in 'ST22'
transaction code such as 'CONNE_IMPORT_WRONG_COMP_LENG' or
'CX_SY_IMPORT_MISMATCH_ERROR'.

Workaround:
Stop the mySAP agent and then re-import the transport, and restart
the mySAP agent.


8.0 Additional product information
===================================

ABAP Transport Compatibility:
------------------------------
Each fix includes an updated agent executable
program (ksaagent or ksaagent.exe) and an updated ABAP transport.
Install both programs to obtain the highest level of support.

Recognizing that there are situations in which you cannot install
a new transport immediately because of change control processes on the
mySAP systems, it is sometimes possible to run a new agent executable
with a prior version of the ABAP transport. This section explains when
it is possible to run a newer agent executable program with an older
version of an ABAP transport.

Note: The mySAP agent does not run correctly if not installed with
a compatible level of the transport.

Fix Level Delivered Transport Minimum Transport Level
----------- ------------------- -----------------------
IF0016 ITMK620_00055 ITMK620_00055
IF0015 ITMK620_00054 ITMK620_00052
IF0014 ITMK620_00053 ITMK620_00052
IF0013 ITMK620_00052 ITMK620_00052
IF0012 ITMK620_00051 ITMK620_00051
LA0011 ITMK620_00050 ITMK620_00050
LA0010 ITMK620_07378 ITMK620_07378
LA0009 ITMK620_00049 ITMK620_00048
IF0008 ITMK620_00049 ITMK620_00048
IF0007 ITMK620_00048 ITMK620_00048
IF0006 ITMK620_00047 ITMK620_00035
LA0005 ITMK620_00046 ITMK620_00035
LA0004 ITMK620_00045 ITMK620_00035
LA0003 ITMK620_00044 ITMK620_00035
LA0002 ITMK620_00043 ITMK620_00035
LA0001 ITMK620_00038 ITMK620_00035


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(R) 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(R) 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 are trademarks of Sun Microsystems,
Inc. in the United States, other countries, or both.

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.

Prerequisites

IBM Tivoli Monitoring for Applications: mySAP agent, Version 6.2.0 or any previous IFix version.

Installation Instructions

Please refer to the 6.2.0-TIV-ITM_SAP-IF0015.README contained in the description section above for general installation instructions

Download package

Problems solved

IV46184, IV41680, IV38554, IV33539, IV33183, IV32752

Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is Fix Central (FC)?
6.2.0-TIV-ITM_SAP-IF0016.README 30 Aug 2013 English 103032 FC FTP
6.2.0-TIV-ITM_SAP-IF0016.tar 30 Aug 2013 English 69386240 FC FTP
6.2.0-TIV-ITM_SAP-IF0016.zip 30 Aug 2013 English 30124708 FC FTP
6.2.0-TIV-ITM_SAP-IF0016.README.CHS 30 Aug 2013 Simplified Chinese 93413 FC FTP
6.2.0-TIV-ITM_SAP-IF0016.README.CHT 30 Aug 2013 Traditional Chinese 95769 FC FTP
6.2.0-TIV-ITM_SAP-IF0016.README.DEU 30 Aug 2013 German 119631 FC FTP
6.2.0-TIV-ITM_SAP-IF0016.README.ES 30 Aug 2013 Spanish 118173 FC FTP
6.2.0-TIV-ITM_SAP-IF0016.README.FR 30 Aug 2013 French 118173 FC FTP
6.2.0-TIV-ITM_SAP-IF0016.README.JPN 30 Aug 2013 Japanese 116050 FC FTP
6.2.0-TIV-ITM_SAP-IF0016.README.PTB 30 Aug 2013 Brazilian Portuguese 111700 FC FTP

Product Alias/Synonym

IBM(R) Tivoli(R) Monitoring for Applications: mySAP Agent Version 6.2.0
Component ID: 5724B97SO

Problems (APARS) fixed
IV46184, IV41680, IV38554, IV33539, IV33183, IV32752

Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Monitoring for Applications
IBM Tivoli Monitoring for Applications mySAP.com

Software version:

6.2

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows, Windows 2003 server

Software edition:

All Editions

Reference #:

4035660

Modified date:

2014-06-30

Translate my page

Machine Translation

Content navigation