Release notes for IBM Transformation Extender Trading Manager 8.2.1.14

(c) Copyright IBM Corporation 2005, 2016. All Rights Reserved.
(c) Copyright HCL Technologies Ltd. 2017, 2021. All Rights Reserved.

CONTENTS

About this release
Installation and Configuration
Upgrade and Migration Information
Known Limitations, Problems, and Workarounds
New and Changed Behavior
Resolved Authorized Program Analysis Reports (APARs)
Contacting Customer Support
Notices and Trademarks

ABOUT THIS RELEASE

Trading Manager version 8.2.1.14 is a full version of the product.

Where to find the software to download

Download the software for this release of Trading Manager from Fix Central.

What's new in this release

This version of Trading Manager will not support any new standard included with Supply Chain V10.1.0 and will support up to the same standards as Trading Manager 8.2.1.13, namely X12 version 7050 and Edifact versions 17B, 18A and 18B

This version of Trading Manager supports:

• Transformation Extender Pack Healthcare V10.1.0
• Transformation Extender Pack for Supply Chain EDI V10.1.0 (excluding new standards higher than X12 7050 and EDIFACT 18B)
  Consequently, customers currently using trading manager 8.2.1.13 on ITX V 9.x will not gain any benefit by installing Trading Manager 8.2.1.14 for 9.x. They should consider upgrading to this version of Trading Manager when upgrading to ITX 10.x.
• IBM Transformation Extender V9.0.0.4
• IBM Transformation Extender V10.0.0
• IBM Transformation Extender V10.0.3
• IBM Transformation Extender V10.1.0

Documentation notes

For the Trading Manager 8.2.1 documentation, see the Transformation Extender knowledge center . No documentation is installed with the product.

Translated documentation

In this release of the product, documentation is provided in English (United States) only.

INSTALLATION AND CONFIGURATION

Installation prerequisites for Trading Manager

Before you install this version of Trading Manager, make certain that Transformation Extender Design Studio and Transformation Extender with Launcher are installed.
To install Trading Manager from the ESD site, install the pack using the appropriate executable (*.exe) file for your Transformation Extender base product version:

Install the desired pack:

• IBM Transformation Extender Pack for Healthcare V10.1.0.0
• IBM Transformation Extender Pack for Supply Chain EDI 10.1.0.0 (X12)

For prerequisites of the Transformation Extender base product, refer to the Transformation Extender release notes and the system requirements.

Other Mandatory Pre-requisites

For executing Trading Manager on Transformation Extender 10.1.0, please obtain from support a patch for Core related to Jira ITXP-8906, APAR: PH35944. This patch solves an issue with launcher not resolving resource registry settings, causing Target or sources not found when running Trading Manager.

ODBC Requirements for installing Partner Manager on Microsoft Windows

To install and execute the Partner Manager the following ODBC settings are required:

• Run the 32-bit ODBC Administrator using C:\Windows\SysWOW64\odbcad32.exe
• Run the 64-bit ODBC Administrator using C:\system32\odbcad32.exe.

Installing Partner Manager on Microsoft Windows 7 and Windows 2012 using Oracle 11gR2

Set the PATH system variable ( Advanced > Environment variables) to either the IBM Transformation Extender root installation path or to the literal ./;

Installing Trading Manager for the first time

The Microsoft Access database that is installed with Trading Manager is already configured for the current version of Trading Manager. No additional steps are required.

To install a new database other than Microsoft Access, run the following scripts in the order listed. Do not run these scripts to convert an existing database. To upgrade an existing version of Trading Manager, follow the instructions in the Upgrade and migration section.

DB2 users: Trading Manager requires a DB2 tablespace page size of 32K. Ask your database administrator (DBA) to create such a tablespace. Before you run the *inst78.sql script, replace USERSPACE1 in the *inst78.sql script with the name of this tablespace.

Run the following scripts, located in the sql/Migration directory:

*inst78.sql

*load78.sql

*update78to82.sql

*update82to821.sql

*update821to8211.sql

*update8211to8213.sql

*update8212or8213to8214.sql

*update8214to8215.sq

*update8215to8216.sql

*update8216to8217.sql

*update8217to8218.sql

*update8218to8219.sql

*update8219to82110.sql

*update8210to82111.sql

*update8211to82112.sql

*update8212to82113.sql

Run the following script, located in the pmgr/sql directory:

*update8213to82114.sql   (Note, this script just updates the database version, it does not add any additional structures to the tables)

UPGRADE AND MIGRATION INFORMATION

All upgrade instructions depend on the value of the "TM database version." To determine this version, issue the following SQL statement:

SELECT CurrentBEVersion FROM BackEndVersion

Locate the version returned by the script in the links below to find the set of scripts to run for your release. Run each script individually in the order presented and examine the result for errors. If no errors occurred, commit the script if "autocommit" is not enabled. Do not proceed with the next script if an error is returned. Contact technical support or your DBA for assistance.

1. Run the *inst78.sql and *load78.sql scripts to create a new 7.8 database in a new instance.
2. Convert your existing database by running the appropriate "PMUpdate" program located in the pmgr directory. Set the "source" database to your current version, and the "destination" database to the 7.8 database that you created in step 1. The program prevents you from running an incorrect version of PMUpdate:

PMUpdate61to78.exe

PMUpdate70to78.exe

PMUpdate75to78.exe

PMUpdate76to78.exe

PMUpdate77to78.exe

3. Run the scripts in Converting from 7.8 to upgrade to the latest release.

Warning: The migration from Trading Manager 8.2.1.8 to a later version includes scripts to remove HIPAA 4010 addenda versions (4010X nnnAx) from trade links that specify HIPAA validation and convert the trade links to type 1 validation.

HIPAA 4010 non-addenda queries

HIPAA 4010 non-addenda trade links are not supported. Existing HIPAA 4010 non-addenda trade links that have a validation level of Type 2 or greater are automatically set to "Type 1 only" when you upgrade from a version prior to V8.2.

To see which trade links are affected by this change, run the following queries on the Trading Manager 7.8 database, which is the source database for the update SQL scripts. Note that if you have any HIPAA 4010 non-addenda trade links, these queries will return zero rows.

Because converting to Trading Manager 8.2 requires the source database to be at the 7.8 release, convert your database to 7.8 before you issue the queries. Note that the queries vary by database vendor; choose the correct query for your database.

Note for Microsoft Access only: Running these queries on an Access database requires the Microsoft Office Access application. Create a new query using the SQL syntax below. If you do not have the Microsoft Office Access application, you may send your Access database (.mdb) to support for analysis.

These queries can take some time to process if you have many trade links in your database.

Access, SQL Server, Sybase

SELECT DISTINCT X12InboundGroups.GS_VersionRelease,
X12IBTrans.TransactionID,
X12InboundGroups.GS_FunctionalID, X12TP_0.PartnerName,
X12AppPartners_0.ApplicationName, X12TP_1.PartnerName,
X12AppPartners_1.ApplicationName
FROM X12IBTrans,X12InboundGroups,
X12AppPartners X12AppPartners_0,
X12TradingPartners X12TP_0, X12IBTradeLink,
X12AppPartners X12AppPartners_1,
X12TradingPartners X12TP_1, X12Version
WHERE X12InboundGroups.X12IBTradeLinkNo =
X12IBTradeLink.X12IBTradeLinkNo AND
X12AppPartners_0.PartnerNo = X12TP_0.PartnerNo AND
X12IBTradeLink.FromExtAPNo =
X12AppPartners_0.ApplicationNo AND
X12IBTradeLink.ToIntAPNo =
X12AppPartners_1.ApplicationNo AND
X12AppPartners_1.PartnerNo = X12TP_1.PartnerNo AND
X12IBTrans.X12InboundGroupNo =
X12InboundGroups.X12InboundGroupNo AND
X12InboundGroups.TradeUnknownInd = 'T' AND
X12Version.VersionSubSet = 'H'
AND X12Version.GS_VersionRelease =
X12InboundGroups.GS_VersionRelease AND
RIGHT(X12InboundGroups.GS_VersionRelease,2) <> 'A1' AND
LEFT(X12InboundGroups.GS_VersionRelease,4) = '4010' AND
RIGHT(X12InboundGroups.ValType,6) <> '000000'
UNION SELECT DISTINCT X12InboundGroups.GS_VersionRelease,
X12IBTrans.TransactionID, X12InboundGroups.GS_FunctionalID,
' UNKNOWN', 'UNKNOWN', X12TradingPartners.PartnerName,
X12AppPartners.ApplicationName
FROM X12InboundGroups, X12Unknown_Link, X12IBTrans,
X12TradingPartners, X12Version,
X12AppPartners WHERE X12InboundGroups.X12Unknown_LinkNo =
X12Unknown_Link.X12Unknown_LinkNo
AND X12Unknown_Link.ToIntAPNo = X12AppPartners.ApplicationNo
AND X12AppPartners.PartnerNo = X12TradingPartners.PartnerNo
AND X12IBTrans.X12InboundGroupNo =
X12InboundGroups.X12InboundGroupNo AND
X12InboundGroups.TradeUnknownInd = 'U' AND
X12Version.VersionSubSet = 'H'
AND X12Version.GS_VersionRelease =
X12InboundGroups.GS_VersionRelease AND
RIGHT(X12InboundGroups.GS_VersionRelease,2) <> 'A1' AND
LEFT(X12InboundGroups.GS_VersionRelease,4) = '4010' AND
RIGHT(X12InboundGroups.ValType,6) <> '000000'

Oracle and DB2

SELECT DISTINCT X12InboundGroups.GS_VersionRelease,
X12IBTrans.TransactionID,
X12InboundGroups.GS_FunctionalID, X12TP_0.PartnerName,
X12AppPartners_0.ApplicationName, X12TP_1.PartnerName,
X12AppPartners_1.ApplicationName
FROM X12IBTrans,X12InboundGroups, X12AppPartners
X12AppPartners_0,
X12TradingPartners X12TP_0, X12IBTradeLink,
X12AppPartners X12AppPartners_1,
X12TradingPartners X12TP_1, X12Version
WHERE X12InboundGroups.X12IBTradeLinkNo =
X12IBTradeLink.X12IBTradeLinkNo AND
X12AppPartners_0.PartnerNo = X12TP_0.PartnerNo AND
X12IBTradeLink.FromExtAPNo =
X12AppPartners_0.ApplicationNo AND
X12IBTradeLink.ToIntAPNo = X12AppPartners_1.ApplicationNo AND
X12AppPartners_1.PartnerNo = X12TP_1.PartnerNo AND
X12IBTrans.X12InboundGroupNo =
X12InboundGroups.X12InboundGroupNo AND
X12InboundGroups.TradeUnknownInd = 'T' AND
X12Version.VersionSubSet = 'H'
AND X12Version.GS_VersionRelease =
X12InboundGroups.GS_VersionRelease
AND
SUBSTR(X12InboundGroups.GS_VersionRelease,
LENGTH(X12InboundGroups.GS_VersionRelease) - 1) <> 'A1' AND
SUBSTR(X12InboundGroups.GS_VersionRelease, 1, 4) = '4010' AND
SUBSTR(X12InboundGroups.ValType,2,6) <> '000000'
UNION SELECT DISTINCT X12InboundGroups.GS_VersionRelease,
X12IBTrans.TransactionID, X12InboundGroups.GS_FunctionalID,
' UNKNOWN', 'UNKNOWN', X12TradingPartners.PartnerName,
X12AppPartners.ApplicationName
FROM X12InboundGroups, X12Unknown_Link, X12IBTrans,
X12TradingPartners, X12Version,
X12AppPartners WHERE X12InboundGroups.X12Unknown_LinkNo =
X12Unknown_Link.X12Unknown_LinkNo
AND X12Unknown_Link.ToIntAPNo =
X12AppPartners.ApplicationNo AND
X12AppPartners.PartnerNo =
X12TradingPartners.PartnerNo AND
X12IBTrans.X12InboundGroupNo =
X12InboundGroups.X12InboundGroupNo AND
X12InboundGroups.TradeUnknownInd = 'U' AND
X12Version.VersionSubSet = 'H'
AND X12Version.GS_VersionRelease =
X12InboundGroups.GS_VersionRelease AND
SUBSTR(X12InboundGroups.GS_VersionRelease,
LENGTH(X12InboundGroups.GS_VersionRelease) - 1) <> 'A1' AND
SUBSTR(X12InboundGroups.GS_VersionRelease, 1, 4) = '4010' AND
SUBSTR(X12InboundGroups.ValType,2,6) <> '000000'

KNOWN LIMITATIONS, PROBLEMS, AND WORKAROUNDS

Using IFD to build, generate and deploy map to Unix platforms may not work.

Maps built using the IFD during the deployment process are not appropriately being built for the platform specified in the server of the system/subsystems and the msl may also not generate appropriately. This is due to the server information not being propagated to the maps level. There is already a reported defect for this but not solved yet.  Below are a couple of workarounds to be able to deploy the maps and systems to the Unix platforms:

Workaround 1:

Use the sdeploy command option (either in command line or in a script) to perform these actions. Information and syntax of the sdeploy can be found in the documentation under :

https://www.ibm.com/support/knowledgecenter/SSVSD8_10.0.0/com.ibm.websphere.dtx.utilcmd.doc/references/r_utility_commands_Using_sdeploy_to_Build_Maps_from_the_Command_a.htm.

The recommended command lines are:

For building maps:

ITX install_dir> sdeploy <tmgr_install_dir/mmgr/Msg_Mgr.msd -BUILDMAPS -A -P <platform>

Or

tmgr_install_dir/mmgr> ITX install_dir sdeploy Msg_Mgr.msd -BUILDMAPS -A -P <platform>

For generating the msl:

ITX install_dir> sdeploy <tmgr_install_dir/mmgr/Msg_Mgr.msd -GENERATE MessageManager -EMODE ES -P <platform> -O <desired path>/Msg_mgr.msl

Or

tmgr_install_dir/mmgr> ITX install_dir sdeploy Msg_Mgr.msd -GENERATE MessageManager -EMODE ES -P <platform> -O <desired path>/Msg_mgr.msl

Also, the sdeploy or ssfptdeploy commands could be used to deploy the maps and system to the Unix platform provided connection can be resolved from the Windows system. Otherwise, all can be ported manually (or with a script) to the Unix platform. Remember also to transfer the additional files defined in the Msd deploy definitions.

Workaround 2:

Although less recommended and with more work, an alternative would be to expand each subsystem in the IFD, navigate to the window that contains the maps and change the server information from None to the same server that was defined at the system level. This must be done for all the subsystems containing maps. Consequently, new “executable” systems will show in IFD navigator, which can be confusing. After doing this, the options to build all maps and generate the msl file from the MessageManager deploy settings can be used.  Note that this will generate map extension that are platform specific and may need to be renamed to .mmc prior to porting.

aX12 5010 997 or 999 acknowledgement (outbound tradelink) will fail validation for X12 version 7050.

Prior to generating the X12mail.mtt using the EDIWIZARD from partner Manager:

• Open the ansi5010.mtt from the Supply Chain pack V10.1.0
• Add version 007050 to the restriction list of element VersionReleaseIndustryIDCd under the V5010 Element group.

Versions not supported

The following versions are not supported in HIPAA and do not allow any acknowledgment above type 1 (for which only the EDI ANSI 4010 or 5010 type tree should be used, as opposed to the hipaa_x12_type_1.mtt tree).

All existing trade links with the following versions are converted to allow type 1 validation only.

4010X nnn
4010X nnnA n
5010X220
5010X221
5010X222
5010X223A1
5010X224A1
5010X279

5010X216 (transaction 278N) is provided only as an example in the HIPAA 4.4.1.7 pack; it is not supported in Trading Manager. To include support for this as a type 1 validation only see the instructions in the documentation to create a custom version.

It is important to note that the pack for Healthcare Payer 9.0.2 includes a deprecated folder that contains a type 1 tree for 4010 Addenda versions. Although not allowed to validate and report errors higher than a type 1 level, users can select to use the type 1 tree from this deprecated HIPAA directory, as opposed to the EDI ansi5010 type tree, when generating the tree from the EDI Wizard.

Creation of claim acknowledgement not supported

Trading Manager does not support the creation of claim acknowledgment 5010X214 277CA. Use the Pack for HIPAA to obtain those.

HIPAA code list validation not supported

Trading Manager does not support HIPAA Type 5 or Type 7 validation.

X12mail.mtt might fail to analyze without errors.

When mixing tradelinks for HIPAA versions and X12 versions (including the acknowledgement version 5010X230 and 5010X231A1) the resulting tree generated from the EDI Wizard in Partner Manager might fail to analyze with errors, which will be apparent when deploying the system, as a screen will pop up indicating the tree has not analyzed clean.

The reason for this is that there is a dependency on which portions of the tree are created first, based on the order of tradelinks included, and because there is a difference between the main Functional Group structure from non X12 vs. HIPAA versions.

It is likely that the problem will be an error indicating the following:

“L00 – Component neither inherited not local: ‘All Parameter Control’ of Type: #xxx Fnnnn Outbound Partner Funct’lGroup ANSI EDI’(error)”

Where xxx is the HIPAA transaction (example 278) and nnnn if the Version (example, 5010).

In order for Trading Manager to continue the deployment and validation process, this error in the tree needs to be manually corrected.

For this, open the X12mail type tree and expand the following path: EDI/ANSI/Funct’lGroup/Partner/Outbound

Once in the location, open the components of the Fnnnn partitioned object (might need to do more than one), and include as a first optional component, the object located under:

EDI/ANSI/Control/Parameter/All

Once this element is included in the Funct’lGroup(s) save and reanalyze the tree, which then should analyze clean.

NEW AND CHANGED BEHAVIOR

Enhanced X12 and EDIFACT support

This version of Trading Manager supports the Supply Chain EDI pack V10.1.0.0 in order to support X12 7050 and EDIFACT 17B, 18A and 18B versions.

HIPAA support

This version of Trading Manager supports only the Pack for Healthcare 10.1.0.0. If you still require full support for addenda 4010 HIPAA versions, you must continue using a previous version of Trading Manager: Trading Manager V8.2.17 with HIPAA 4.4.1.1.

Discontinued support

Trading Manager, V8.2.1.14 does not support IBM Transformation Extender version 8.3, 8.4, or 8.4.1.

RESOLVED AUTHORIZED PROGRAM ANALYSIS REPORTS (APARs)

For a list of the APARs that are fixed in this version of the product, see the Fix List.

CONTACTING CUSTOMER SUPPORT

Contact Customer Support at 1-800-IBM-SERV, or go to the support portal.

NOTICES AND TRADEMARKS

This information was developed for products and services offered in the US. This material might be available from IBM in other languages. However, you may be required to own a copy of the product or product version in that language in order to access it.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBMrepresentative 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, MD-NC119
Armonk, NY 10504-1785
US

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan

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.

Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk.

IBM may use or distribute any of the information you provide in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Director of Licensing
IBM Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
US

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to actual people or business enterprises is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.


Trademarks

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

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

Terms and conditions for product documentation

Permissions for the use of these publications are granted subject to the following terms and conditions.

Applicability
These terms and conditions are in addition to any terms of use for the IBM website.

Personal use
You may reproduce these publications for your personal, noncommercial use provided that all proprietary notices are preserved. You may not distribute, display or make derivative work of these publications, or any portion thereof, without the express consent of IBM.

Commercial use
You may reproduce, distribute and display these publications solely within your enterprise provided that all proprietary notices are preserved. You may not make derivative works of these publications, or reproduce, distribute or display these publications or any portion thereof outside your enterprise, without the express consent of IBM.

Rights
Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either express or implied, to the publications or any information, data, software or other intellectual property contained therein.

IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of the publications is detrimental to its interest or, as determined by IBM, the above instructions are not being properly followed.

You may not download, export or re-export this information except in full compliance with all applicable laws and regulations, including all United States export laws and regulations.

IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.

IBM Online Privacy Statement

IBM Software products, including software as a service solutions, (“Software Offerings”) may use cookies or other technologies to collect product usage information, to help improve the end user experience, to tailor interactions with the end user, or for other purposes. In many cases no personally identifiable information is collected by the Software Offerings. Some of our Software Offerings can help enable you to collect personally identifiable information. If this Software Offering uses cookies to collect personally identifiable information, specific information about this offering’s use of cookies is set forth below.

This Software Offering does not use cookies or other technologies to collect personally identifiable information.

If the configurations deployed for this Software Offering provide you as customer the ability to collect personally identifiable information from end users via cookies and other technologies, you should seek your own legal advice about any laws applicable to such data collection, including any requirements for notice and consent.
For more information about the use of various technologies, including cookies, for these purposes, see IBM’s Privacy Policy at http://www.ibm.com/privacy and IBM’s Online Privacy Statement at http://www.ibm.com/privacy/details in the section entitled “Cookies, Web Beacons and Other Technologies,” and the “IBM Software Products and Software-as-a-Service Privacy Statement” at http://www.ibm.com/software/info/product-privacy.