Readme: IBM Tivoli Composite Application Manager Agent for SAP Applications Version 7.1.1 Fix Pack 9

1.0 General description

2.0 Problems fixed  

3.0 Architecture and Prerequisites  

4.0 Download Instructions  

5.0 Installation instructions  

6.0 Additional installation information  

7.0 Known problems and workarounds  

8.0 Additional product information  

9.0 Copyright and trademark information  

10.0 Notices

1.0 General description

=======================

This fix pack resolves the APARs and defects listed in the 'Problems fixed' section. This fix pack also includes the superseded fixes listed in Section 2.4.

2.0 Problems fixed

=======================

The following problems are addressed by this fix pack.

2.1 APARs

---------------------

No APARs

2.2 Defects

---------------------

No Defects

2.3 Enhancements

---------------------

Abstract: ITCAM Agent for SAP Applications with SNC - Multiple SAP NetWeaver RFC SDK libraries versions.

https://automation-management.ideas.ibm.com/ideas/ITMAPM-I-90

Additional Information

SAP agent version 7.1.1 Fix Pack 9 supports SAP NetWeaver RFC SDK libraries 7.50 PL14 and above.

2.4 Superseded fixes

----------------------------------

7.1.1-TIV-ITM_SAP-FP0008

7.1.1-TIV-ITM_SAP-FP0007

7.1.1.6-TIV-ITM_SAP-IF0004

7.1.1.6-TIV-ITM_SAP-IF0003

7.1.1.6-TIV-ITM_SAP-IF0002

7.1.1.6-TIV-ITM_SAP-IF0001

7.1.1-TIV-ITM_SAP-FP0006

7.1.1.5-TIV-ITM_SAP-IF0001

7.1.1-TIV-ITM_SAP-FP0005

7.1.1-TIV-ITM_SAP-FP0004

7.1.1.3-TIV-ITM_SAP-IF0001

7.1.1-TIV-ITM_SAP-FP0003

7.1.1-TIV-ITM_SAP-FP0002

7.1.1.1-TIV-ITM_SAP-IF0002

7.1.1.1-TIV-ITM_SAP-IF0001

7.1.1-TIV-ITM_SAP-FP0001

7.1.1-TIV-ITM_SAP-IF0001

------------------------------------------

7.1.1-TIV-ITM_SAP-FP0008 

------------------------------------------

​APARs

APAR: IJ45253

Abstract: The Attribute Group KSAORASUM (Database Summary) and the Attribute Group KSAORADTL (Database Details) are showing the data referring to Transaction Code DB02OLD  instead of Transaction Code DB02 on TEPS.

Additional Information: The SAP Standard Function Module is deprecated which is exclusively used for Transaction code DB02OLD. The new Standard Function Module has been implemented to fetch the data from the Transaction Code DB02 and the same will be displayed for Attribute Group KSAORASUM (Database Summary) and the attribute group KSAORADTL (Database Details) on TEPS.
Note:  The size-related Attribute Group KSAORASUM (Database Summary), KSAORADTL (Database Details), and KSAORAPERF (Oracle Database Performance Overview) will be shown in MB only. The data for the attributes CPUUSAGE and CPUTIME for the Attribute Group KSAORAPERF (Oracle Database Performance Overview) are displayed as blank as these attributes are not supported by the newly implemented Data Collector. 

APAR: IJ46117

Abstract: Wrong origin for object ZITM_AUTH in ABAP package /IBMMON/ITM.

Additional Information: The SAP "Software Update Manager" (SUM) tool, which is used to perform the release changes and updates, finds the Object ZITM_AUTH from ABAP package /IBMMON/ITM and tries to delete it as it is marked with the origin "SAP", which is incorrect.

Defects

-----------

No Defects

Enhancements

-------------------

No Enhancements

------------------------------------------

 7.1.1-TIV-ITM_SAP-FP0007

------------------------------------------

Enhancement:

Abstract: S/4 HANA 2021 support is available.

Additional Information: Support for monitoring of S/4 HANA 2021 (SAP Basis version 756) is provided.

------------------------------------------

​7.1.1.6-TIV-ITM_SAP-IF0004

------------------------------------------

---------------------

Enhancement

Abstract: S/4 HANA 1709 support is available.

Additional Information: Support for monitoring of S/4 HANA 1709 (SAP Basis version 752) is provided.

Enhancement: RFE 130567

Abstract: S/4 HANA 1809 support is available.

Additional Information: Support for monitoring of S/4 HANA 1809 (SAP Basis version 753) is provided.

Enhancement: RFE 140873

Abstract: S/4 HANA 1909 support is available.

Additional Information: Support for monitoring of S/4 HANA 1909 (SAP Basis version 754) is provided.

Enhancement

Abstract: S/4 HANA 2020 support is available.

Additional Information: Support for monitoring of S/4 HANA 2020 (SAP Basis version 755) is provided. As a prerequisite, SAP Note 2767860 "Generation of RFC destinations with invalid name" should be implemented on the SAP system.

------------------------------------------

 7.1.1.6-TIV-ITM_SAP-IF0003

------------------------------------------

Defects

Enhancements

APARs

Defects

No Defects

Enhancements

1.  "Hardcoded Domain":      
   For improved security, the user can configure the password of the default username.  
2. "Generic Table operations":      
   An Authorization Object 'S_DEVELOP' is added to the profile /IBMMON/AUTH and assigned to user IBMMON_AGENT. The user with Authorization Object 'S_DEVELOP' has the authority to perform Generic table operations such as: "Generic Read Report" "Generic Delete Report" "Generic Table Query(Read Access)" "Forceful querying(Read/Write Access)" 
3. "Missing authority check in Report":      
   A new Authorization Object ZITM_AUTH is created in the profile /IBMMON/AUTH and assigned to user IBMMON_AGENT. The user with the Authorization Object ZITM_AUTH has the authority to execute the Reports.    
4. "Missing Authority check before Call Transaction":     
   An Authorization Object 'S_DEVELOP' is added to the profile /IBMMON/AUTH and assigned to user IBMMON_AGENT. The user with the Authorization Object 'S_TCODE' has the authority to call any transactions.
5. "Direct database modification":   
   For improved security, an additional internal security layer is implemented for database access.
6. "Usage of db tables without authorization groups"      
   Added an authorization group "ZITM" and all database tables are assigned to the ZITM authorization group. This authorization group is assigned to the authorization object "S_TABU_DIS". This authorization group is added to the profile /IBMMON/AUTH and assigned to user IBMMON_AGENT.      The user with the Authorization Object 'S_TABU_DIS' with authorization group ZITM has the authority to access database tables.

1. A new Authorization Object ZITM_AUTH is created in the profile /IBMMON/AUTH and assigned to user IBMMON_AGENT. The user with Authorization Object ZITM_AUTH will only have authority to access the attributes tagged under "SYS","SLM","LDS","SOL,"PI" node. For other users, "RFC Error Check Agent Log" message will be displayed on TEP.
2. The default password for IBMMON_AGENT is replaced with a random generation of password. User can modify the password of their choice according to their password policy.
3. Direct read and write access of directories is replaced with logical file paths.
   Note: If the SAP system is installed on Unix/Linux or WINDOWS NT operating system, the ConfigBackup.csv file gets created either on the application server inside the work directory at /usr/sap///work/ or inside the global directory at /usr/sap///global/. According to the SAP environment, filename might truncate.

7.1.1.5-TIV-ITM_SAP-IF0001

1. Create an entry in the table - /IBMMON/ITM_CNFG with PARM_NAME = "BATCH_JOBS_PERF" and VALUE_CHAR = "YES" to maintain a configuration parameter. The total number of entries fetched will be equivalent to a critical constant value which includes jobs with Active and Cancelled status within the default sample period interval.
2. Create an entry in table - /IBMMON/ITM_CNFG with PARM_NAME = "BATCH_JOBS_PERF" and VALUE_CHAR = "YES_LONG_RUN" to maintain a configuration parameter. This will fetch all Cancelled jobs for the request within the default sample period interval and all Active jobs in the system without any sample period constraints up to the critical constant value.
3. Create an entry in table - /IBMMON/ITM_CNFG with PARM_NAME = "BATCH_JOBS_PERF" and VALUE_CHAR = "YES_ALL" to maintain a configuration parameter. This will fetch jobs with all statuses for the request within the default sample period interval and all Active jobs in the system without any sample period constraints up to the critical constant value.
4. If there is no configuration parameter added, it will fetch all jobs with all statuses for the request within the default sample period interval.

• MAX_CCMS_ALERT_THRESHOLD=3500
• CMS_ALERT_SHORT_INTERVAL=0
• CMS_ALERT_LONG_INTERVAL=0
• DELETE_IDX_AT_AGENT_RESTART=N
• DELETE_IDX_AT_SAP_SYSTEM_RESTART=N

• CMS_ALERT_SHORT_INTERVAL_OVERLAP=Y
• SAVE_OPEN_AND_CLOSED_CACHE=N 
  Where,
• AX_CCMS_ALERT_THRESHOLD - This parameter indicates that agent will cache 3500 alerts. If this value is not set by the user then by default value 3500 is set.
• CCMS_ALERT_SHORT_INTERVAL - This parameter indicates the short interval duration in minutes.  If the configuration parameter is not set, by default 0 value is set and no short calls will be triggered by the SAP Agent. Only the integer value between 15 to 60 minutes is acceptable for this configuration parameter.
• CCMS_ALERT_LONG_INTERVAL - This parameter indicates the long interval duration in hours. It is recommended to set the parameter value to 0. Only the integer value between 0 to 24 hours is acceptable for this configuration parameter.
• DELETE_IDX_AT_AGENT_RESTART - This parameter enables the feature of IDX file deletion when SAP Agent is restarted. IDX file stores the timestamp. It is recommended to set the parameter value to ‘N’. When set to 'N', it will collect all alerts from the timestamp stored in idx file. If required, then you  can set the value to ‘Y’ if you want to collect all  alerts after the SAP agent restart. 
• DELETE_IDX_AT_SAP_SYSTEM_RESTART - This parameter enables the feature of IDX file deletion when SAP System is restarted. It is recommended to set the parameter value to ‘N’. When set to 'N', it will collect all alerts from the timestamp stored in idx file. If required, then you can set the value to ‘Y’  if you want to collect all alerts after the SAP system restart. 
• CMS_ALERT_SHORT_INTERVAL_OVERLAP - This parameter indicates that SAP agent will overlap the Short interval calls with the respect to time interval. This parameter will be used only if CCMS_ALERT_SHORT_INTERVAL is set with some value between 15 to 60 minutes.
• SAVE_OPEN_AND_CLOSED_CACHE - This parameter indicates whether user wants to preserve CCMS Alerts Cache after the Agent is stopped and reload CCMS Alerts after agent is started. This works only when the value for DELETE_IDX_AT_AGENT_RESTART parameter is set to ‘N’.
  Note - After the agent instance is reconfigured, please verify if the above entered parameters are present in sa_.config file on Linux/AIX platform or KSAENV_ file on Windows platform. If they are not present, please add them and restart the agent to activate this feature.

7.1.1-TIV-ITM_SAP-FP0005

3.0 Architecture and Prerequisites

==========================================

This Fix Pack is supported on all operating systems listed in the IBM Tivoli Composite Application Manager Agent for SAP Applications. Installation, Configuration, Reference, and Troubleshooting guides, Version 7.1.1 Fix Pack 9: Link: SAP Applications Agent

3.1 Prerequisites for this fix

--------------------------------

• For SAP agent version 7.1.1 Fix Pack 9, SAP NetWeaver RFC SDK libraries 7.50 PL14 are prerequisites. Download the required RFC libraries from the SAP support portal. No backward compatibility support has been provided with this fix for SAP NetWeaver RFC SDK libraries of any previous versions of 7.20 and 7.50.
• As this fix is cumulative, it can be installed on any fix level for this version, release, and modification level above the prerequisite. 

4.0 Download Instructions

============================
The installation package "ITCAM_SAP_APP7.1.1.9_MLMP.tar.gz" can be downloaded from Passport Advantage using Part Number M0N7VML.

5.0 Installation instructions

=============================
When you download this fix pack image from the IBM Software Support website, the following rules are applicable:

1. You can locally install the fix pack only on a system that already hosts a licensed copy of IBM Tivoli Monitoring for SAP Applications. Similar to other upgrade software, the fix pack image can also be locally installed on a computer where the product software is not already installed.
2. You can populate agents to the depot. ​
3. You can remotely deploy agents to the existing or new installations.

When you download this fix pack image from Passport Advantage, the following rules are applicable:  

1. ​You can locally install the fix pack on a system that already hosts a licensed copy of IBM Tivoli Monitoring for SAP Applications.  
2. You can locally install the fix pack on a system that does not already host a licensed copy of IBM Tivoli Monitoring for SAP Applications.  
3. You can populate agents to the depot.  
4. You can remotely deploy agents to the existing or new installations.  

5.1 Before installing the fix

•  The prerequisites listed under section 3.1 entitled, 'Prerequisites for this fix' must be installed for upgrade.  
• In this README, the <CANDLEHOME> symbol indicates the location of 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 pack on UNIX systems, set the CANDLEHOME environment variable to the IBM Tivoli Monitoring installation directory.    
  For example
  > CANDLEHOME=/opt/IBM/ITM     > export CANDLEHOME  
• As there is no uninstall utility for this fix pack, be sure to back up your environment before installing the fix pack.

5.2 Local agent update

----------------------  

1. Transfer the appropriate archive file to a temporary directory on the system that contains the agent to be updated. For 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. This step creates a directory structure that contains fixes for all the supported operating systems.  
3. Use the procedures in the 'IBM Tivoli Composite Application Manager Agent for SAP Applications Version 7.1.1 Fix Pack 7 Installation and Configuration Guide' to install the agent.

5.3 Remote agent update

-----------------------  

1. Transfer the appropriate archive file to a temporary directory on the IBM Tivoli Enterprise Monitoring Server system. In 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 extract utility on Windows systems. This step creates a directory structure that contains fixes for all of the supported operating systems.  
3. To add the agent fix pack 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 Appendix A. Commands reference of the 'IBM Tivoli Monitoring Command Reference'.      
   On UNIX systems, if the fix was expanded to /:  
    

   \> $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/<PARTNUMBER>/unix -t sa  

   On Windows systems, if the fix was expanded to \:      
    

   > %CANDLE_HOME%\bin\tacmd addBundles -i \\WINDOWS\Deploy -t sa        

   Where:        
   -i is the directory that contains the deployment bundles to be added to the depot.         
   -t is the product code of the product to add, in this case, "sa" represents the Monitoring Agent for SAP.  
4. To log in to the Tivoli Enterprise Monitoring server, and deploy the fix to the appropriate nodes where the agent is running, use the following 'tacmd' commands.   For more information on the 'tacmd login' and 'tacmd updateAgent' commands, see the IBM Tivoli Monitoring Command Reference.
   Note: Before Upgrade, remove the existing SAP NetWeaver RFC SDK libraries 7.50 PL12 from agent candlehome copy SAP NetWeaver RFC SDK libraries 7.50 PL14, and then upgrade the SAP agent.  
   On UNIX systems,   
     

   > $CANDLEHOME/bin/tacmd login -s
                                 -u
                                 -p      
   > $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                                          
                                       -v 07110900      

   On Windows systems,
   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   
                                         -v 07110900    

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

5.4 Agent support update

------------------------  
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 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 extract utility on Windows systems. This step creates a directory structure that contains fixes for all of the supported platforms.  
3. Use the procedures in the 'IBM Tivoli Composite Application Manager Agent for SAP Applications Version 7.1.1 Fix Pack 7 Installation and Configuration Guide' to install the support.  
4. If the Tivoli Enterprise Monitoring Server being updated is remote (not a Hub Tivoli Enterprise Monitoring Server) then restart the Tivoli Enterprise Monitoring Server.  
5. If the Tivoli Enterprise Portal Desktop or Tivoli Enterprise Portal Browser was running when the update was installed, then it must be restarted.

5.5 Installing SAP agent transport:

----------------------------------  
Note: From this fix onwards, a single ITM file is provided for importing SAP transport on all the supported SAP versions having BADI or non-BADI implementation. This procedure installs the SAP transport into the SAP 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 SAP environment as follows:        
   1. The following sets of transport files are in the ABAP directory of the SAP agent fix archive:          
      1) K711_00153U.ITM and R711_00153U.ITM in /ABAP directory.              
      These files are for Unicode versions of the transport.          
      2) K711_00153_DELETE.ITM and R711_00153_DELETE.ITM              
      These transport files remove the ABAP code. Do not import the DELETE transport unless you stop using the product entirely and want to remove the transports from your SAP systems.        
   2. Copy your transport files to the SAP Transport System data directory as follows:          
      1) Copy the K711_00153U.ITM file to the cofiles directory.          
      2) Copy the R711_00153U.ITM file to the data directory.    
   3. Run the following command where:          
      SID Target SAP: system ID          
      PROFILE_NAME: Name of the tp profile file          
      nnn: Number for the target client where the agent is to run            
      tp addtobuffer ITMK711_00153U SID              
      pf=\usr\sap\trans\bin\PROFILE_NAME            
      tp import ITMK711_00153U SID client=nnn U16              
      pf=\usr\sap\trans\bin\PROFILE_NAME    
      Alternatively, you can use the SAP 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.    
   4. The default password for IBMMON_AGENT is replaced with a random generation of password. User can modify the password of their choice according to their password policy.        Use the following procedure to change your password:        
      1. Go to SU01 transaction.        
      2. In the user field, enter username and click the change icon.        
      3. Open the Logon Data tab.        
      4. In New Password and Repeat Password fields, enter the password of your choice.        
      5. Click save.        
      Important: You must confirm that /IBMMON/AUTH authorization profile is present in the Profile tab.        
      Use the following procedure to create the IBMMON/AUTH authorization profile:          
      a) Press F4 and Search /IBMMON/AUTH.          
      b) Select /IBMMON/AUTH from the search result and click Save.

6.0 Additional installation information

=======================================  

6.1 Verifying the update

1. To verify that the agent is updated correctly, use the tacmd command to view the current version of the agent after the agent is restarted. You must 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                                                                                                   -u    
                                   -p      
   > %CANDLE_HOME%\bin\tacmd listSystems -t sa      

   Note:      
   - The component (-t) for the tacmd list Systems command is specified as two characters (sa), not three characters (ksa).  When the agent update is successful, the agent version must be displayed as 07.11.09.00. After the agent is restarted, you can also use the GUI to verify that the agent was successfully updated.  
   - The date of the build displayed might not be accurate. This is a known problem.      
2. To verify that the agent support files were updated correctly, use the kincinfo command on Windows systems or the cinfo command on Linux(R) 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.    
   On Unix systems,
   ----------------------     
   To validate that all components are installed, run the following command:     
   For example:       
   > %CANDLE_HOME%/bin/cinfo -i     
   Note: cinfo output might differ depending on the ITM version.    
    

   ​*********** Mon Apr  3 12:12:13 IST 2023 ******************     
   User: root Groups: root     
   Host name : control-plane        Installer Lvl:06.30.07.19     
   CandleHome: /opt/IBM/SAP     
   ***********************************************************     
   ...Product inventory       
   ax   IBM Tivoli Monitoring Shared Libraries          
   lx8266  Version: 06.30.07.21     
   gs   IBM GSKit Security Interface          
   lx8266  Version: 08.00.55.17       
   jr   Tivoli Enterprise-supplied JRE          
   lx8266  Version: 08.07.10.00       
   sa   IBM Tivoli Composite Application Manager Agent for SAP Applications          
   lx8266  Version: 07.11.09.00

8.0 Additional product information

==================================    

8.1 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. Note: The mySAP agent does not run correctly if not installed with a compatible level of transport.

Fix Level          Delivered Transport      Minimum Transport Level

----------       ----------------------   --------------------------

FP0009               ITMK711_00153             ITMK711_00153

8.2 Additional Information

---------------------------    

1. TEMA version is upgraded to ITM 630 FP7 SP13 from 630 FP7 SP12 for 7.1.1-TIV-ITM_SAP-FP0008 SAP Agent.  
2. Changed the unit from “kb to MB” under the attribute caption for the below attributes of Database Details (KSAORADTL) and Database Summary (KSAORASUM).     
   1. For KSAORADTL Attribute Group following attributes caption has been changed from "kb to MB" -      Size, Size\Change\Per Day, Size\Used, Size\Free, Minimum\Free, Maximum\Free, \Next\Extent,      Size_64, Size\Change\Per Day_64, Size\Used_64, Size\Free_64, Minimum\Free_64, Maximum\Free_64,  \Next\Extent_64    
   2. For KSAORASUM Attribute Group following attributes caption has been changed from "kb to MB" -    Total\Size, Total\Used, Total\Free, Minimum\Free, Total\Size\MB, Total\Used\MB, Total\Free\MB, Minimum\Free\MB, Total\Size_64, Total\Used_64, Total\Free_64, Minimum\Free_64, Total\Size\MB_64, Total\Used\MB-64, Total\Free\MB_64, Minimum\Free\MB_64  
3. There will be no data for Analysis time (of Database Details and Database summary) and CPU Time(sec) and CPU Usage(%) attributes (of Oracle database performance) workspaces. These attribute data will be blank as no data is coming for it from SAP system.
4. 711FP8 is not backward compatible. Hence, you must install 711FP8 agent and 711FP8 supports.  
5. 711FP9 supports two different tokens towards SNC(Secured Network Communication) Configuration i.e. X509, Kerberos.   

9.0 Copyright and trademark information

10.0 Notices

============
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION 'AS IS' WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Microsoft, Windows, and Windows Server are trademarks of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others.
Third-Party License Terms and Conditions, Notices and Information
-----------------------------------------------------------------
The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided or referenced below. Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version. Not withstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities(collectively 'IBM'), the third party software code identified below are 'Excluded Components' and are subject to the following terms and conditions: - the Excluded Components are provided on an 'AS IS' basis - IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE - IBM will not be liable to you or indemnify you for any claims related to the Excluded Components. - IBM will not be liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages with respect to the Excluded Components.