Copyright International Business Machines Corporation 2009. 
All rights reserved.


Component: IBM Tivoli Monitoring for Applications: mySAP Agent, 
           Version 6.1.0

Component ID: 5724B97SO

Interim Fix: 0015, 6.1.0-TIV-ITM_SAP-IF0015
Date: August 15, 2009

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.

It does not include fixes for the add-on language support features.
The language support features for this fix are addressed in language
pack 6.1.0-TIV-ITM_SAP-LA0010.

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

  2.1 APARS:
  ----------
  APAR: IZ55846
  Abstract: mySAP agent does not support to decrypt the AES256 password
  encrypted by IBM Tivoli Monitoring framework

  Additional Information:
        mySAP agent 6.1 is configured to monitor SAP systems under an
        IBM Tivoli Monitoring 6.1 framework. After upgrading the OS 
        agent to 6.2, 6.2.1, or a later version, the IBM Tivoli 
        Monitoring framework is upgraded to the corresponding version.
        When restarting the mySAP agent 6.1, the mySAP agent can not 
        connect to an SAP system because it can not decrypt 
        the password: sappassword.

  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 neither registered nor displayed
        on the Tivoli Enterprise Portal for the Monitoring
        Agent for mySAP.
  
  2.2 Defects
  ------------
  Defect: 110972
  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.
       
  Defect: 110965
  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 generated in the agent logs.
  
  2.3 Enhancements
  -----------------
  None.

  2.4 Superseded fixes
  ---------------------
  6.1.0-TIV-ITM_SAP-LA0014
  6.1.0-TIV-ITM_SAP-LA0013
  6.1.0-TIV-ITM_SAP-LA0012
  6.1.0-TIV-ITM_SAP-LA0011
  6.1.0-TIV-ITM_SAP-LA0009
  6.1.0-TIV-ITM_SAP-LA0008
  6.1.0-TIV-ITM_SAP-LA0007
  6.1.0-TIV-ITM_SAP-LA0006
  6.1.0-TIV-ITM_SAP-LA0005
  6.1.0-TIV-ITM_SAP-LA0003
  6.1.0-TIV-ITM_SAP-LA0002
  6.1.0-TIV-ITM_SAP-LA0001

  2.5  APARS and changes included from superseded fixes
  -----------------------------------------------------

  6.1.0-TIV-ITM_SAP-LA0014
  ------------------------

  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 reported for
        Dialog_Step attribute.

  APAR: IZ25758
  Abstract: The message 'SYSCP-DYNCP-AGTCP' appears multiple times in
  syslog.

  APAR: IZ29271
  Abstract: mySAP agent shutdown automatically.

  Additional Information:
        Operating System SIGHUP signal makes mySAP agent shut down
        automatically.

  6.1.0-TIV-ITM_SAP-LA0013
  ------------------------

  APAR: IZ06262
  Abstract: SCALE/PREC not applied to long term history query 
  attributes

  Addtional Information:
        Agent queries such as "Buffer Performance (610)"  that filter
        on an integer attribute return no long term data from the 
        Warehouse. An error similar to the following appears in the
        Tivoli Enterprise Portal Server log:
        SQL0401N  The data types of the operands for the operation ">="
        are not compatible.

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


  6.1.0-TIV-ITM_SAP-LA0012
  ------------------------

  APAR: IZ16866
  Abstract: ABAP dump BCD-OVERFLOW with exception 
  CX_SY_CONVERSION_OVERFLOW occurs in /IBMMON/ITM_ORA_DETAIL

  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 
        function module /IBMMON/ITM_WORK_PROCESSES and an additional  
        error message, "Unable to interpret "**" as a number." 
        This problem is specific to SAP application servers running
        more than 99 work processes.

  APAR: IZ19279
  Abstract: Managed groups 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 Monitoring Agent for mySAP code.

  APAR: IZ18815
  Abstract: ABAP dump BCD-OVERFLOW occurs in /IBMMON/ITM_IDOCS

  APAR: IZ19337
  Abstract: ABAP dump COMPUTE_INT_PLUS_OVERFLOW occurs in 
  /IBMMON/ITM_OS_PERF

  APAR: IZ17077
  Abstract: "DISPLAY ITEM" FOR "R/3_ALERT_SYSTEM_DOWN" situation does
  not display correctly on Tivoli Enterprise Portal Server

  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: IZ20878
  Abstract: mySAP agent does not report data to the Tivoli Enterprise
  Portal Server for extended periods of time.

  Additional Information:
        The Monitoring Agent for mySAP performance is degraded when the
        agent is monitoring SAP distributed statistics records (through
        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.

  Defect: 65616
  Abstract: Situations do not fire for managed group subnodes.

  Defect: 69509
  Abstract: No historical data for mySAP agent in Warehouse database.
  On a Windows system, the Monitoring Agent for mySAP short-term 
  history files on the Tivoli Enterprise Monitoring Agent do not 
  upload to the Warehouse database.

  Defect: 71472
  Abstract: No data is returned for R/3_Spool_Requests attribute
  group.

  Additional Information:
        This problem exists in 6.1.0-TIV-ITM_SAP-LA0009 and
        6.1.0-TIV-ITM_SAP-LA0011.


  6.1.0-TIV-ITM_SAP-LA0011
  ------------------------

  APAR: IZ05536
  Abstract: mySAP agent memory workspace fails to return metrics
  in non-English environment.

  Additional Information/Symptom:
        In a non-English SAP environment, the 
        R/3_Buffer_Performance.Name attribute gets the values from the
        SAP system in non-English and the filter values 
        (Extended Memory, Heap Memory, Page Area, and Roll Area) are in
        English and do not match. Blank tables/charts are displayed.

  APAR: IZ13182
  Abstract: BCD-OVERFLOW with exception CX_SY_CONVERSION_OVERFLOW
  occurs in /IBMMON/ITM_TRAN_PERF

  APAR: IZ14058
  Abstract: Modify IBM Tivoli Monitoring 6.1 ABAP transports compatible
  for repackaging.

  Additional Information/Symptom:
        Existing IBM Tivoli Monitoring 6.1 transports protect the ABAP
        code that does not allow repackaging. These transports are now 
        modified to allow you to repackage these transports in their 
        SAP systems.

  APAR: IZ15745
  Abstract: BCD_ZERODIVIDE with exception CX_SY_ZERODIVIDE occurs 
  in /IBMMON/ITM_TRAN_PERF

  APAR: IZ16619
  Abstract: mySAP agent incorrectly determines central instance
  after exception.

  Additional Information/Symptom:
        When any exception occurs in the mySAP agent, the RFC         
        connection is closed and re-opened, and all saved
        variables are lost and must be re-established. The
        central_instance variable is now determined to be the instance
        that contains the enqueue process, and it is not able to find
        the central instance. The central_instance variable   
        remains unset and blank. Now, the code is modified to 
        use the logon instance name for the agent instead of the 
        central instance name.

  APAR: IZ16617
  Abstract: GWY_MONITOR_DISABLED exception

  Additional Information/Symptom:
        On an SAP system where multiple instances run, gateway function
        modules are called from the logon instance. One such funtion 
        module, GWY_DUMP_INFO, is being called without specifying the  
        destination and causes the GWY_MONITOR_DISABLED exception.

  Defect: 66506
  Abstract: Handle GWY_MONITOR_DISABLED exception same as in
  IBM Tivoli Monitoring 6.2.


  6.1.0-TIV-ITM_SAP-LA0009
  ------------------------
  
  APAR: IZ10788
  Abstract: Existing historical collection does not start on newly
  created mySAP agent instance.

  APAR: IZ08143
  Abstract: mySAP agent user is locked after reconfiguration.

  Additional Information:
        After the mySAP agent is reconfigured, the agent can no longer 
        connect to the mySAP system due to a corrupt password.  
        This problem occurs only on mySAP agents running on Windows
        systems in a multi-byte language environment such as Japenese.

  APAR: IZ04398
  Abstract: mySAP agent: Possible COMPUTE_INT_PLUS_OVERFLOW 
  or COMPUTE_INT_MINUS_OVERFLOW in BUFFERS/MEMORY.

  Additional Information/Symptom:
        This arithmetic overflow occurs when collecting Buffer and 
        Memory performance statistics on SAP systems with very high 
        activity that have been running for a long time, or on SAP  
        systems with very large memory allocation on 64-bit operating
        systems. The problem results in an ABAP dump in the agent-
        provided function module /IBMMON/ITM_BUFFER_PERF.

  APAR: IZ11119
  Abstract: The USERID calling the CCMS monitor needs additional 
  SAP authority to be able to receive this central CCMS data.
  
  Additional Information/Symptoms:
        The agent-provided role and profile, ZITM_610AUTH, did not
        have the authorities required to obtain alerts from a 
        centralized CCMS system. This resulted in missing alerts
        in the Alerts workspace. The required authorities have 
        been added to both the ZITM_610AUTH role and 
        ZITM_610AUTH profile; and thus; the IBMMON_AGENT userid.

  Defect: 58082
  Abstract: ABAP ITM_NUMBER incorrectly typed as TBTCO-JOBCOUNT.

  Additional Information: The above error prevents the Tivoli 
        Enterprise Portal Server link from Batch Jobs table view to the
        Batch Job log workspace from working by causing a 
        'CONVERT_NO_NUMBER' ABAP dump in function module 
        /IBMMON/ITM_JOB_LOG.
  
  6.1.0-TIV-ITM_SAP-LA0008
  ------------------------

  Defect: 39387
  Abstract: Transport fails to import on 4.6C R/3

  Defect: 44444
  Abstract: N/A is shown in Userid field in User Performance
  workspace

  Defect: 51726
  Abstract: Divide by zero in transaction /IBMMON/ITM_TRAN_PERF.


  New mySAP transport files.
    You must use the LA0008 version of the transport, ITMK610_00116,
    with the LA0008 version of the mySAP agent. The LA0008 agent WILL
    NOT work with earlier versions of the mySAP transport.

  FITS requirements addressed:
    MR0614074849 -  Update R/3_Transaction_Performance attribute 
    group to report the number of dialog steps per transaction type
    that exceed a specified threshold. The following three new 
    attributes were added to R/3_Transaction_Performance. 

    Dialog Steps Above Threshold - Number of dialog steps with a 
    response time exceeding the Dialog Step Response Threshold.

    Dialog Steps Above Threshold (%) - Percentage of dialog steps
    with a response time exceeding the Dialog Step Response Threshold.
    Calculated as Dialog Steps Above Threshold / Dialog Steps.

    Dialog Step Response Threshold (ms) - The response time 
    threshold, in milliseconds, for dialog steps.  A dialog step
    with a response time exceeding this threshold is counted by 
    configuring the mySAP agent ABAP code.

  Configuring Dialog Step Response Threshold in mySAP system.
      
    You can configure a Dialog Step Response Threshold for any 
    transaction by executing transaction SE16. In the "Table Name"
    field, enter "/IBMMON/ITM_TRSH" and then, select "Table 
    Contents (F7)" to access the table. 
      
    To view the current threshold settings, select "Execute (F8)".
    The transaction names are shown under column "WORKLOAD"; the
    threshold values are shown under column "THRESHOLD".
      
    To add a new threshold setting, select "Create (F5)". Enter
    the transaction name in the "WORKLOAD" field. The following
    wild cards are accepted for the WORKLOAD value:

       *  matches multiple characters
       +  matches any single character 
      
    Enter the threshold value, in milliseconds, in the "THRESHOLD"
    field. Select "Save" to save this setting.
      
    New and changed threshold values do not take effect immediately,
    but take effect under either of the following conditions:

       - The agent has been restarted.
       - The agent reopens its RFC connection to the mySAP system.
       This occurs every 12 heartbeats, which is about
       every 2 hours and 10 minutes by default .
           
    The value entered for the Threshold column is returned in
    the Dialog Step Response Threshold attribute of the 
    R/3_Transacation_Performance attribute group.

  6.1.0-TIV-ITM_SAP-LA0007
  ------------------------
  APAR: IY96036
  Abstract: Alphanumeric characters in JOBCOUNT field causing 
  ABAP dump

  APAR: IY98599
  Abstract: Spool service metrics in tep show incorrect value
                                                         
  APAR: IY99370
  Abstract: mySAP agent produce entry every 10 mins in syslog 
  MSG:"YIT TM-ITM FOR MYSAP STILL CONNECTED TO RWP WITH 
  NORMAL HEARTBEAT"

  APAR: IY99380
  Abstract: mySAP agent receives error message KSA0301 
  failure on call to /IBMMON/ITM_TRAN_PERF function module

  Defect: 46786
  Abstract: Obsolete SAP program RSPO0043 still being called.

  Defect: 49808
  Abstract: ITM_RSPO1043 batch job never runs, remains 'Scheduled'.

  6.1.0-TIV-ITM_SAP-LA0006
  ------------------------
  APAR: IY95435 
  Abstract: Arguments messages are lost in TEP 

  6.1.0-TIV-ITM_SAP-LA0005
  ------------------------
  APAR: IY94348 
  Abstract: Problem with historical data for 
  "USER TRANSACTION PERFOMANCE"

  Defect: 41044
  Abstract:
  IBM Tivoli Monitoring normal syslog messages sometimes are displayed
  as red, yellow, or green messages. These syslog messages are now 
  categorized so they show up in the syslog with a color 
  of white.

  Defect: 41125
  Abstract:
  Managed Groups are ignored on Unicode mySAP systems. They do not
  show up in the Tivoli Enterprise Portal.

  Defect: 41320
  Abstract:
  The import of the agent transport fails on some 
  mySAP systems with return code = 12.  The error occurs in the XPRA
  (Method Execution) step and is reported as follows:
  CALL_FUNCTION_PARM_UNKNOWN...Function parameter "CALLER_CODEPAGE"
  is unknown

  This same error can also occur at run time when the ABAP code is 
  called for data collection.

  Defect: 41185
  Abstract:
  R/3_Transaction_Performance aggregation attribute is not available
  for use in situations.


  6.1.0-TIV-ITM_SAP-LA0003
  ------------------------
  APAR: IY93163
  Abstract: Transport import problem

  APAR: IY93473
  Abstract: Problem with SYSLOG output in Tivoli Enterprise Portal 
  Server

  Defect 39951
  Abstract:
  ksar3 (or ksar3exe) fails when called to run an ABAP program 
  when a named variant is also specified. The mySAP system
  issues an error stating that the specified variant does not exist.

  Defect 40736
  Abstract:
  The agent provided function module /IBMMON/ITM_ITM_ALERTS and 
  program /IBMMON/ITM_RUN_REPORT use an obsolete SAP program, 
  RSPO0043, to do a spool consistency check.

  Defect 40798
  Abstract:
  The agent provided function module /IBMMON/ITM_ORA_SUMMARY and
  /IBMMON/ITM_ORA_DETAIL generate an ABAP dump reporting a
  CALL_FUNCTION_CONFLICT_LENG error when run on some mySAP systems.

  New mySAP transport files.
    You must use the LA0003 version of the transport, ITMK610_00107,
    with the LA0003 version of the mySAP agent. The LA0003 agent does
    not work with earlier versions of the mySAP transport.

  FITS requirements addressed:
     MR1107062734 -  Update R/3_Transaction_Performance attribute 
     group to include an attribute that reports the transaction 
     (such as SE38) that invoked the program or the job that ran
     the program.

     MR1107065832 - Update R/3_Logon_Information attribute group to
     report additional information about when a specific user ID is
     unlocked.

  6.1.0-TIV-ITM_SAP-LA0002
  ------------------------
  APAR: IY89748
  Abstract: when starting monitoring, BCD_OVERFLOW error occurs

  APAR: IY92450
  Abstract: Japanese text from a non-unicode double byte language 
  mySAP system does not display correctly                          

  APAR: IY92452
  Abstract: Installation of non-unicode double byte language support
  into a non-unicode mySAP system fails with an SAP shortdump.    

  6.1.0-TIV-ITM_SAP-LA0001
  -------------------------
  SAP Basis 7.0 support - mySAP transport ITMK610_00094 or higher
  provides support for monitoring SAP Basis 7.0 systems. 

  These transports do not support the new mySAP 7.0 password 
  features. Passwords specified during mySAP agent configuration must
  conform to pre-7.0 SAP release password rules. You must 
  configure the agent with an upper case password of 12 characters or
  fewer.

  If you require support for mySAP 7.0 password features, upgrade
  to IBM Tivoli Monitoring for Applications: mySAP Agent, version 6.2.0, 
  which provides support for SAP 7.0, including longer case-sensitive
  passwords.

  The mySAP agent depends on SAP statistics collection working
  correctly on the mySAP systems it monitors. On SAP 7.0 systems, you
  must set the mySAP system time zone to match the operating system
  time zone in order for SAP statistics to be collected with the
  correct time stamps. You must make this change in order for the
  mySAP agent to successfully collect data. See SAP note 
  926290 located in the SAP Support Portal for more information on
  this problem.

    
3.0 Architecture and prerequisites
======================
This fix is supported on all operating systems listed in the IBM
Tivoli Monitoring for Applications: mySAP Agent User's Guide, 
version 6.1.0.

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

  3.1 Prerequisites for this fix
  --------------------------------
  The prerequisite level for this fix is as follows:
  - IBM Tivoli Monitoring for Applications: mySAP Agent, version 6.1.0.  
  - IBM Tivoli Monitoring, Version 6.1.0: Fix Pack 0002 (6.1.0-TIV-ITM-FP0002).   
     
  Because this fix is cumulative, it can be installed on any fix level for
  this version, release, and modification level later than the prerequisite. 

4.0 Image directory contents
=============================
This fix image contains the following files:
- 6.1.0-TIV-ITM_SAP-IF0015.README - This README file
- 6.1.0-TIV-ITM_SAP-IF0015.tar - Fix archive .tar format
- 6.1.0-TIV-ITM_SAP-IF0015.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 :
   6.1.0-TIV-ITM_SAP-IF0015/ksa_winnt_tema_if0015.cab       - Binaries for Windows
   6.1.0-TIV-ITM_SAP-IF0015/KSAWINNT.dsc		    - Descriptor file for Windows
   6.1.0-TIV-ITM_SAP-IF0015/ksaaix513.dsc		    - Descriptor file for AIX 32-bit
   6.1.0-TIV-ITM_SAP-IF0015/ksaaix516.dsc       - Descriptor file for AIX 64-bit
   6.1.0-TIV-ITM_SAP-IF0015/ksahp11.dsc			    - Descriptor file for HP-UX 32-bit
   6.1.0-TIV-ITM_SAP-IF0015/ksahp116.dsc		    - Descriptor file for HP-UX 64-bit
   6.1.0-TIV-ITM_SAP-IF0015/ksahpi116.dsc		    - Descriptor file for HP-UX Itanium
   6.1.0-TIV-ITM_SAP-IF0015/ksali6242.dsc		    - Descriptor file for Linux on Intel
   6.1.0-TIV-ITM_SAP-IF0015/ksali6243.dsc		    - Descriptor file for Linux on Intel
   6.1.0-TIV-ITM_SAP-IF0015/ksals3246.dsc		    - Descriptor file for Linux 64-bit
   6.1.0-TIV-ITM_SAP-IF0015/ksasol283.dsc		    - Descriptor file for Solaris 8 32-bit
   6.1.0-TIV-ITM_SAP-IF0015/ksasol286.dsc		    - Descriptor file for Solaris 8 64-bit
   6.1.0-TIV-ITM_SAP-IF0015/ksasol606.dsc		    - Descriptor file for Solaris 10 Opteron 64-bit
   6.1.0-TIV-ITM_SAP-IF0015/sa_dd_061000015.xml		  				- xml file
   6.1.0-TIV-ITM_SAP-IF0015/sa_dd.properties		    				- File for product properties
   6.1.0-TIV-ITM_SAP-IF0015/ABAP/K610_00135.ITM             - Control file for non-unicode version of Transport
   6.1.0-TIV-ITM_SAP-IF0015/ABAP/R610_00135.ITM             - Data file for non-unicode version of Transport
   6.1.0-TIV-ITM_SAP-IF0015/ABAP/K610_00135U.ITM            - Control file for Unicode version of Transport
   6.1.0-TIV-ITM_SAP-IF0015/ABAP/R610_00135U.ITM            - Date file for Unicode version of Transport
   6.1.0-TIV-ITM_SAP-IF0015/ksa_tems_teps_tepd_if0015.tar   - Support files for UNIX IBM Tivoli Enterprise Monitoring Server/Tivoli Enterprise Portal Servers 
   6.1.0-TIV-ITM_SAP-IF0015/ksa_tems_teps_tepd_if0015.zip   - Support files for Windows IBM Tivoli Enterprise Monitoring Server/Tivoli Enterprise Portal Servers 
   6.1.0-TIV-ITM_SAP-IF0015/ksa_aix513_tema_if0015.tar      - Binaries for AIX 32-bit
   6.1.0-TIV-ITM_SAP-IF0015/ksa_aix516_tema_if0015.tar      - Binaries for AIX 64-bit
   6.1.0-TIV-ITM_SAP-IF0015/ksa_hp11_tema_if0015.tar        - Binaries for HP-UX 32-bit
   6.1.0-TIV-ITM_SAP-IF0015/ksa_hp116_tema_if0015.tar       - Binaries for HP-UX 64-bit
   6.1.0-TIV-ITM_SAP-IF0015/ksa_hpi116_tema_if0015.tar      - Binaries for HP-UX Itanium     
   6.1.0-TIV-ITM_SAP-IF0015/ksa_li6242_tema_if0015.tar      - Binaries for Linux on Intel
   6.1.0-TIV-ITM_SAP-IF0015/ksa_li6243_tema_if0015.tar      - Binaries for Linux on Intel
   6.1.0-TIV-ITM_SAP-IF0015/ksa_ls3246_tema_if0015.tar	    - Binaries for Linux 64-bit
   6.1.0-TIV-ITM_SAP-IF0015/ksa_sol283_tema_if0015.tar	    - Binaries for Solaris 8 32-bit
   6.1.0-TIV-ITM_SAP-IF0015/ksa_sol286_tema_if0015.tar	    - Binaries for Solaris 8 64-bit
   6.1.0-TIV-ITM_SAP-IF0015/ksa_sol606_tema_if0015.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 symbol <CANDLEHOME> is the 
    IBM Tivoli Monitoring installation directory. The default value
    for CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\IBM\ITM'
    on Windows systems.

    Before installing this fix on UNIX systems, set the environment 
    variable, CANDLEHOME, to the IBM Tivoli Monitoring installation 
    directory.
        
    For example: 
    > CANDLEHOME=/opt/IBM/ITM 
    > export CANDLEHOME
    
  - <OPTIONAL: Refer to section 7.0 entitled "Known problems and workarounds" before
    installation.>
    
  - 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.1.0-TIV-ITM_SAP-IF0015.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 
     symbol, <TEMP>, represents the fully qualified path to this 
     directory. Note: On Windows, 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. This creates a directory 
     structure that contains fixes for all of the supported operating systems.

  3. Use the itmpatch command to install the fix for the operating 
     system for that agent. For more information on the itmpatch command,
     see section 6.2.      
     
     On UNIX systems, if the fix was expanded to <TEMP>/6.1.0-TIV-ITM_SAP-IF0015,
     the install command would be:
     
     > itmpatch -h <CANDLEHOME> 
                -i <TEMP>/6.1.0-TIV-ITM_SAP-IF0015/ksa_xxxxxx_tema_if0015.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_if0015.tar.  
         > ./cinfo -i
           Monitoring Agent for mySAP agent
           li6243  Version: 06.10.00.00               

     On Windows systems, if the fix was expanded to 
     <TEMP>\6.1.0-TIV-ITM_SAP-IF0015, the install command is:

     > itmpatch -h <CANDLEHOME> 
                -i <TEMP>\6.1.0-TIV-ITM_SAP-IF0015\ksa_winnt_tema_if0015.cab


  5.3 Remote agent update
  ----------------------------
  1. Transfer the appropriate archive file (6.1.0-TIV-ITM_SAP-IF0015.tar
     or .zip) to a temporary directory on the Tivoli Enterprise 
     Monitoring Server system.  For the purpose of this README, the 
     symbol, <TEMP>, represents the fully qualified path to this
     directory. Note: On Windows, 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. This 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 on the tacmd addBundles command, see the IBM Tivoli
     Monitoring Administrator's Guide.

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

     On Windows systems, 
     if the fix was expanded to <TEMP>\6.1.0-TIV-ITM_SAP-IF0015:
     > %CANDLE_HOME%\bin\tacmd addBundles -n -i <TEMP>\6.1.0-TIV-ITM_SAP-IF0015
     
     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. To log in to the Tivoli Enterprise Monitoring Server, and deploy
     the fix to the appropriate nodes where the agent is running, use
     the following tacmd commands.  For more information on the tacmd
     login and updateAgent commands, see the IBM Tivoli Monitoring 
     Administrator's Guide.

     On UNIX systems: 
     > $CANDLEHOME/bin/tacmd login -s <server>
                                   -u <itmuser> 
                                   -p <password>
                                   
     > $CANDLEHOME/bin/tacmd listSystems
          
     The output shows the Managed System Name for the OS agent on the
     remote system to be updated. Use this value as the target of the
     tacmd updateAgent command.
     
     > $CANDLEHOME/bin/tacmd updateAgent -t sa  
                                         -n <Managed system name>
                                         -v 061000015

     On Windows systems:
     > %CANDLE_HOME%\bin\tacmd login -s <server>
                                     -u <itmuser> 
                                     -p <password>
                                    
     > %CANDLE_HOME%\bin\tacmd listSystems
          
     The output shows the Managed System Name for the OS agent on the
     remote system to be updated. Use this value as the target of the
     tacmd updateAgent command.
     
     > %CANDLE_HOME%\bin\tacmd updateAgent -t sa 
                                           -n <Managed system name>    
                                           -v 061000015
                              
     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.1.0-TIV-ITM_SAP-IF0015) includes changes to the agent
  support files that need to 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.1.0-TIV-ITM_SAP-IF0015.tar
     or .zip) to the IBM Tivoli Enterprise Monitoring Servers, IBM 
     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. This creates a directory 
     structure that contains fixes for all of the supported platforms.

  3. Expand the archive file (ksa_tems_teps_tepd_if0015.tar or .zip)
     that contains the updates for 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. This 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 can be started by using one of the following commands
     from within the CD-ROM directory where setup.jar is located:
       
     On UNIX systems:
     > $CANDLEHOME/JRE/<platform>/bin/java -jar setup.jar   
                
     On Windows systems:
     > <"C:\Program Files\IBM\Java15">\jre\bin\java -jar setup.jar 
             
       where <"C:\Program Files\IBM\Java15"> is the default drive
       and location of IBM Java 1.5. The location of IBM Java 1.5
       on your system might vary.          
                          
     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. The next panel presented by the Application Support Installer asks
     for the selection of which Tivoli Monitoring components to which
     you want to add application support.  For this fix, the check 
     boxes should 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 selecting the mySAP
     06.10.00.15 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 do not need 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 Monitoring Agent for mySAP fix archive. There are three
           sets of transport files:

          1) K610_00135.ITM and R610_00135.ITM
             These files are non-Unicode versions of the transport.

          2) K610_00135U.ITM and R610_00135U.ITM
             These files are Unicode versions of the transport.

          3) K610_00135_DELETE.ITM and R610_00135_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 K610_00135.ITM file to the cofiles 
              directory.
              2) Copy the R610_00135.ITM file to the data directory.
          or
            Unicode transport
              1) Copy the K610_00135U.ITM file to the cofiles 
              directory.
              2) Copy the R610_00135U.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 ITMK610_00135 SID
            pf=\usr\sap\trans\bin\PROFILE_NAME
            tp import ITMK610_00135 SID client=nnn U16
            pf=\usr\sap\trans\bin\PROFILE_NAME
        unicode
            tp addtobuffer ITMK610_00135U SID
            pf=\usr\sap\trans\bin\PROFILE_NAME
            tp import ITMK610_00135U 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
  ------------------------------------------------------
  There are no updates to the baroc files included in this fix or
  any of the superceded fixes.  No additional installation steps are
  required.
  
  6.2 Additional information on using itmpatch command
  ------------------------------------------------------
   The itmpatch command has the following syntax.

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

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

   where:

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

   For example, on UNIX systems:
   - To preview the fix installation, use the "-t" option:
     > <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -t <TEMP>
    
   - To install the fix, use the "-i" option:
     > <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -i <TEMP>
    
   where:   
   <CANDLEHOME> is the fully qualified IBM Tivoli Monitoring 
   installation directory. On Windows, this must include the drive 
   letter.
   <TEMP> represents the fully qualified directory specification, where
   the fix is located. On Windows, this 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 was restarted. You are required to log in to a Tivoli
     Enterprise Monitoring Server prior to viewing the agent version.  

     For example:
     On UNIX systems, where $CANDLEHOME is the IBM Tivoli Monitoring
     installation directory. The default location is '/opt/IBM/ITM'.   
    
     > $CANDLEHOME/bin/tacmd login -s <server>
                                   -u <itmuser> 
                                   -p <password>
     > $CANDLEHOME/bin/tacmd listSystems -t sa

     On a Windows system, 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 should 
     now be:
     06.10.00.15

     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.10.00.15.
    
     After the agent is restarted, you can also use the GUI to verify
     the agent was successfully updated.

     For the agent on Windows systems, the version number is 
     06.10.00.15.
     For the agent on UNIX system, the version number is
     06.10.00.15.
    
  2. To verify 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 a Windows system:
     ---------------------
     To validate that all components have been installed, run the
     following command:
    
     For example:
     > %CANDLE_HOME%\InstallITM\kincinfo -i       
   
     >kincinfo -i
     *********** Mon Aug 10 16:43:14 China Standard Time 2009 *****************
     User      : Administrator Group    : NA
     Host Name : TIVU28       Installer: Ver: 0NOVALUE00000
     CandleHome: C:\IBM\ITM
     *********************************************************************
     ...Product Inventory
   
     Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal 
     Server, and Tivoli Enterprise Portal Desktop update:
   
     SA       mySAP Support
              WINNT Version: 06.10.00.15 Build: 200908030715

     SA       mySAP Support
              WINNT Version: 06.10.00.15 Build: 200908030715

     SA       mySAP Support
              WINNT Version: 06.10.00.15 Build: 200908030715
   

7.0 Known problems and workarounds
  ===================================
Defect  :  36560
Abstract:     File Not Found errors during UNIX Take Actions
Symptoms:
  Take Action commands that call the utility commands such as 
  ksar3 that are provided by the Monitoring Agent for mySAP do 
  not run. The stderr output reports errors such as 
  "ksar3 not found." This error affects all predefined Take Action 
  commands such as "R/3 Batch Jobs~Start Job" and user-
  defined Take Action commands. This problem occurs only for a 
  Monitoring Agent for mySAP running on a UNIX computer. 

Workaround:
  Modify the PATH variable used by the monitoring agent so the
  utility commands are found. On the computer running the Monitoring
  Agent for UNIX OS do the following:

    - cd <CANDLE_HOME>/config
    - Edit the sa_<SID>.config file
    - Append the following directory to the PATH variable setting:
        <CANDLE_HOME>/<ARCH>/bin
      For example, /opt/IBM/ITM/aix516/bin


Defect  :  36560
Symptoms:
  The utility commands such as ksar3 provided by the Monitoring Agent
  for mySAP fail to run. The stderr output reports a 
  "library librfccm not found" error, a "Missing Language Record" 
  error, or both of these errors. This problem occurs only for mySAP
  utility commands run on a UNIX computer.

Workaround:
  Modify the LIBPATH variable used by the utility commands so the RFC
  library is found. On the computer running the Monitoring Agent for
  mySAP do the following:

    - cd <CANDLE_HOME>/<ARCH>/bin
    - Edit the utility command file (ksar3, ksanfy or ksapwd)
    - Append the following directory to the LIBPATH, LD_LIBRARY_PATH 
    	or SHLIB_PATH variable:
        <CANDLEHOME>/<ARCH>/sa/lib
      For example, /opt/IBM/ITM/aix516/sa/lib/

  Modify the KSA_MSGBASE environment variable so it correctly finds
  the MSG file.

    - cd <CANDLE_HOME>/<ARCH>/bin
    - Edit the utility command file (ksar3, ksanfy or ksapwd)
    - Append "ksamsgf.msg" the to KSA_MSGBASE variable.
      For example,
        export KSA_MSGBASE=/opt/IBM/ITM/aix516/bin/ksamsgf.msg

Defect: None
Abstract:
  mySAP agent stops communicating with mySAP system after 
  approximately 24 hours. Even though the agent continues to run, 
  data is no longer reported to Tivoli Enterprise Monitoring Server/
  Tivoli Enterprise Portal. RAS1 logs show the agent reconnects 
  successfully to mySAP server several times in the first 24 hours, 
  then it receives an RFC error on the next reconnection attempt. 
  All subsequent attempts to connect to the mySAP server fail. 
  This problem is seen most often with mySAP agents running on AIX 
  systems but can occur on any operating system that has both IPV4
  and IPV6 interfaces enabled.

Workarounds:
  There are two different workarounds for this problem. Choose one:

  1) Add the following line to the
     $INSTALL_DIR/config/sa_<3-character-ID>.config file where
     $INSTALL_DIR is the directory where you installed the
      agent code:

         KDEB_INTERFACELIST_IPV6='-'

OR

  2) During mySAP agent configuration, specify IP addresses instead of 
  	 hostnames for the following configuration prompts:  
  	 Primary Host name, Primary Gateway name. Also, specify an 
  	 IP address for Alternate 1 and Alternate 2 if you use those 
  	 optional settings.

8.0 Additional product information
===================================
ABAP Transport Compatibility:
---------------------------------
Each limited availability fix includes an updated agent executable
program (ksaagent or ksaagent.exe) and an updated ABAP transport. 
It is highly recommended that both programs be installed 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
-----------     -------------------     -----------------------
IF0015	        ITMK610_00135           ITMK610_00116
LA0014	        ITMK610_00133           ITMK610_00116
LA0013	        ITMK610_00130           ITMK610_00116
LA0012	        ITMK610_00127           ITMK610_00116
LA0011	        ITMK610_00122           ITMK610_00116
LA0009	        ITMK610_00118           ITMK610_00116
LA0008	        ITMK610_00116           ITMK610_00116
LA0007	        ITMK610_00112           ITMK610_00107
LA0006          ITMK610_00110           ITMK610_00107
LA0005          ITMK610_00109           ITMK610_00107
LA0004          Not applicable          Not applicable
LA0003          ITMK610_00107           ITMK610_00107
LA0002          ITMK610_00104           ITMK610_00094
LA0001          ITMK610_00094           ITMK610_00094


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.