IBM Support

Release notes for IBM WebSphere Transformation Extender Trading Manager, V8.2.1.10

Release Notes


Abstract

These release notes for IBM WebSphere® Transformation Extender Trading Manager Version 8.2.1.10 describe where to obtain software and lists resolved APARs. This version of WebSphere Trading Manager is updated to work with ITX V.9.0.0.

Content

IBM WebSphere® Transformation Extender Trading Manager
Version 8.2.1.10 release notes

© Copyright IBM Corporation 2006, 2016. All Rights Reserved.


============================================================
CONTENTS
============================================================
1. About this release
2. Installation and configuration information
3. Upgrade and migration information
4. Known limitations, problems, and workarounds
5. New and changed behavior
6. Resolved Authorization Program Analysis Reports (APARS)
7. Contacting customer support
8. Notices and trademarks


============================================================
1. ABOUT THIS RELEASE
============================================================

This release is a full version of the product.

Where to find the software to download

To download the software for this release of Trading Manager, go to FixCentral.

What's new in this release

This version of Trading Manager supports:
  • WebSphere Transformation Extender Pack for HIPAA EDI, V.4.4.1.6 (with LAIF for APAR number PI63433 )
  • WebSphere Transformation Extender Pack for X12, V.2.8.1.4 (with current LAIF for APAR number PI63435 if running under WebSphere Transformation Extender 8.4, 8.4.1 or 9.0.0.)
  • WebSphere Transformation Extender Pack for EDIFACT, V.2.8.1.4
  • WebSphere Transformation Extender 8.3.0.6
  • WebSphere Transformation Extender 8.4.0.5
  • WTX 8.4.1.4 (minimum build 23 containing LAIF for APAR # PI63429, or minimum build 29 containing LAIF for APAR # PI64638 if executing under Windows 64-bit operating system)
  • ITX 9.0 (minimum build 199 containing LAIF for APAR # PI63403 and APAR # PI63429, or minimum build 204 containing LAIF for APAR # PI64638 if executing under Windows 64-bit operating system)

Documentation notes

The PDF files and the IBM Eclipse help system that install with Trading Manager are deprecated beginning with release 8.2.1.9. See the IBM Transformation Extender 9.0 online documentation for the Trading Manager 8.2.1 documentation. These release notes contain the latest information about Trading Manager 8.2.1.10.

For detailed information about WebSphere Transformation Extender product documentation, see the Documentation release notes

Translated documentation

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


============================================================
2. INSTALLATION AND CONFIGURATION INFORMATION
============================================================

Installation prerequisites for Trading Manager

Before you install this version of Trading Manager, make certain that one of the following versions of the WebSphere Transformation Extender or IBM Transformation Extender base product is installed.

If you are installing Trading Manager from the ESD site, install the pack using the executable (*.exe) file associated with your WebSphere Transformation Extender or IBM Transformation Extender base product as indicated in the following table:

WebSphere Transformation Extender or IBM Transformation Extender base product requiredExecutable file
9.0.0.0tmgr82110_900.exe
8.4.1.4tmgr82110_841.exe
8.4.0.5tmgr82110_84.exe
8.3.0.6tmgr82110_83.exe

Install the desired pack:
  • HIPAA - WebSphere Transformation Extender Pack for HIPAA EDI, V.4.4.1.6 (with LAIF for APAR PI63433)
  • X12 - WebSphere Transformation Extender Pack for X12, V.2.8.1.4 (with LAIF for APAR PI63435 if running under WebSphere Transformation Extender 8.4, 8.4.1 or 9.0.0)
  • EDIFACT - WebSphere Transformation Extender Pack for EDIFACT, V.2.8.1.4

LAIF (Limited Availability Interim Fix) for HIPAA and EDI pack products can be obtain via a request for a patch to our support department.



For additional installation prerequisites related to the IBM Transformation Extender base product, refer to the IBM Transformation Extender release notes.

Note for users of WebSphere Transformation Extender V 8.4.1.4 (build 22 or prior) and IBM Transformation Extender V.9.0.0 (build 198 or prior): To install this product with WebSphere Transformation Extender V.8.4.1.4 or ITX V.9.0.0, contact support and request a LAIF for the core product that contains a fix for APARs PI63403 (only applies to ITX 9.0.0.x) and PI63429 (minimum builds 23 for WebSphere Transformation Extender 8.4.1.4 and 199 for ITX 9.0.0). If running launcher under a 64 bit Windows environment, also ensure patch PI64638 is included (minimum build 29 for WebSphere Transformation Extender 8.4.1.4 and build 204 for ITX 9.0.0). These issues were resolved in later versions of the Transformation Extender core product to address an issue for IBM where the reject files do not contain the details of the transactions in error under a <DataLog> Section, EDI Wizard failures creating a type tree under Partner Manager and memory corruption using Launcher under 64 bit Windows.

Installing Partner Manager on Windows 7 and Windows 2008



When installing Partner Manager on 64-bit Windows 7 and Windows 2008 systems, a 32-bit version of ODBC is required.

On 64-bit Windows systems, the 32-bit ODBC Administrator is run using C:\Windows\SysWOW64\odbcad32.exe and the 64-bit ODBC Administrator is run using C:\system32\odbcad32.exe.

On 32-bit Windows systems, the 32-bit ODBC Administrator is run using C:\system32\odbcad32.exe.

Trading Manager for IBM Transformation Extender V.9.0.0 uses a 64-bit environment. This scenario requires two drivers: a 32-bit driver to connect to the Partner Manager database, and a 64-bit driver to use in the Database Editor file (update.mdq) to connect the Message Manager maps to the database.

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

Ensure that the PATH system variable in your system (Advanced > Environment variables) is modified so that either the WebSphere Transformation Extender root install path or the literal ./; is added.

Installation instructions

Follow these steps if you are installing IBM WebSphere Transformation Extender Trading Manager for the first time. If you have an existing version and you want to convert it, refer to the Upgrade instructions below. Trading Manager version 8.2.1.10 is a full installation. If you are using a database other than Microsoft Access, Trading Manager requires multiple steps to bring the database up to the current version.

To install a new database for Trading Manager V.8.2.1.10, run the following scripts in the order listed. Do not run these scripts to convert an existing database.

*inst78.sql

Note on *inst78.sql for DB2 users: Change the tablespace name (search and replace in USERSPACE1) as directed by your DBA.
Trading Manager requires a DB2 tablespace page size of 32K. Ask your DBA to create such a tablespace, and replace USERSPACE1 in the script with the name of this tablespace.

The following scripts are located in the sql/Migration directory:

*load78.sql
*update78to82.sql
*update82to821.sql
*update821to8211.sql
*update8211to8213.sql
*update8212or8213to8214.sql
*update8214to8215.sq
*update8215to8216.sql
*update8216to8217.sql

*update8217to8218.sql
*update8218to8219.sql

*update8219to82110.sql


============================================================
3. UPGRADE AND MIGRATION INFORMATION
============================================================

Upgrade instructions

All upgrade instructions depend on the value of the "TM database version." To obtain this version, issue the following SQL statement and make note of the value returned. Use that value to find the proper instruction set to follow, below.

SELECT CurrentBEVersion FROM BackEndVersion

Refer to "Trading Manager SQL Scripts," above, before proceeding.

Run each script individually, examine the results for any errors, and most importantly, commit the script if you do not have "autocommit" on. Do not proceed with the next script if an error is returned. Contact IBM support or your DBA for assistance.

Scripts must be run in the order presented.

Converting from 8.2.1.9 (CurrentBEVersion=8.2.1.9)

Run the following script:

*update8219to82110.sql

Converting from 8.2.1.8 (CurrentBEVersion=8.2.1.8)

Run the following scripts:

*update8218to8219.sql

*update8219to82110.sql

Converting from 8.2.1.7 (CurrentBEVersion=8.2.1.7)

Run the following scripts:

*update8217to8218.sql

*update8218to8219.sql

*update8219to82110.sql

Converting from 8.2.1.6 (CurrentBEVersion=8.2.1.6)

Run the following scripts:

*update8216to8217.sql

*update8217to8218.sql

*update8218to8219.sql

*update8219to82110.sql

Converting from 8.2.1.5 (CurrentBEVersion = 8.2.1.5)

Run the following scripts:

*update8215to8216.sql

*update8216to8217.sql

*update8217to8218.sql

*update8218to8219.sql

*update8219to82110.sql

Converting from 8.2.1.4 (CurrentBEVersion = 8.4.2)

Run the following scripts:

*update8214to8215.sql

*update8215to8216.sql

*update8216to8217.sql

*update8217to8218.sql

*update8218to8219.sql

*update8219to82110.sql


Converting from 8.2.1.2 or 8.2.1.3 (CurrentBEVersion = 8.3 or 8.3.1)

Run the following scripts:

*update8212or8213to8214.sql

*update8214to8215.sql

*update8215to8216.sql

*update8216to8217.sql

*update8217to8218.sql

*update8218to8219.sql

*update8219to82110.sql


Note: The database schema did not change between 8.2.1.2 and 8.2.1.3. For this reason, one script handles the 8.2.1.2 version and the 8.2.1.3 version upgrade to 8.2.1.4.


Converting from 8.2.1.1 (CurrentBEVersion = 8.2.3)

Run the following scripts:

*update8211to8213.sql

*update8212or8213to8214.sql

*update8214to8215.sql

*update8215to8216.sql

*update8216to8217.sql

*update8217to8218.sql

*update8218to8219.sql

*update8219to82110.sql


Converting from 8.2.1 (CurrentBEVersion = 8.2.1.3)

Run the following scripts:

*update821to8211.sql

*update8211to8213.sql

*update8212or8213to8214.sql

*update8214to8215.sql

*update8215to8216.sql

*update8216to8217.sql

*update8217to8218.sql

*update8218to8219.sql

*update8219to82110.sql


Converting from 8.2 (CurrentBEVersion = 8.2.4)

Run the following scripts:

*update82to821.sql

*update821to8211.sql

*update8211to8213.sql

*update8212or8213to8214.sql

*update8214to8215.sql

*update8215to8216.sql

*update8216to8217.sql

*update8217to8218.sql

*update8218to8219.sql

*update8219to82110.sql


Converting from 7.8 (CurrentBEVersion = 7.8.3)

Run the following scripts:

*update78to82.sql

*update82to821.sql

*update821to8211.sql

*update8211to8213.sql

*update8212or8213to8214.sql

*update8214to8215.sql

*update8215to8216.sql

*update8216to8217.sql

*update8217to8218.sql

*update8218to8219.sql

*update8219to82110.sql



Converting from releases prior to 7.8 (CurrentBEVersion 7.8.3)

Converting databases prior to release 7.8 requires two main steps: converting your database to 7.8, and then following the "Converting from 7.8" steps above. To convert to 7.8, use the "PMUpdate" programs in the pmgr directory. The steps are:
  1. Create a new 7.8 database. Run the *inst78.sql and *load78.sql scripts to create this database in a new instance.
  2. Convert your existing database by running the proper "PMUpdate" program found in the pmgr directory. The program will confirm that you are using the correct version, so you cannot run the wrong one.

    Pick one of the following programs, set the "source" database to your current version, and the "destination" database to the 7.8 database created in step 1.

PMUpdate61to78.exe

PMUpdate70to78.exe

PMUpdate75to78.exe

PMUpdate76to78.exe

PMUpdate77to78.exe

3. Follow the steps for "Converting from 7.8," above.


HIPAA 4010 addenda support

Warning: The migration step from tmgr 8.2.1.8 to 8.2.1.9 includes scripts to remove HIPAA 4010 addenda versions (4010XnnnAx) from those tradelinks that specify HIPAA validation and to convert them to type 1 validation if needed.


HIPAA 4010 non-addenda queries

HIPAA 4010 Non-Addenda are not supported. Because of this, any 4010 HIPAA Non-Addenda trade links that you might have with a validation level of Type 2 or greater will be automatically set to "Type 1 only" when upgrading from a version prior to 8.2.

To see which trade links are impacted 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 you cannot have any such trade links; if so, these queries will return zero rows.

As a conversion to Trading Manager 8.2 requires the source database to be at the 7.8 release, convert your database to 7.8 before issuing 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.

Note: 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'


============================================================
4. KNOWN LIMITATIONS, PROBLEMS, AND WORKAROUNDS
============================================================

Versions not supported

The following versions are not supported in HIPAA and, as such, should 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 tradelinks with the following versions are converted to allow type 1 validation only.

4010Xnnn

4010XnnnAn

5010X220

5010X221

5010X222

5010X223A1

5010X224A1

5010X279

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

It is important to note that the pack for HIPAA 4.4.1.7 contains 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.

Reject file not displaying transaction details in DataLog section for users in ITX V.9.0.0



Due to a recent defect encountered in the core engine, when a data file is rejected, the detail portion of the rejection is not displayed in the reject file. This happens when using IBM Transformation Extender V.9.0.0 build 198 or earlier. For a workaround, please request the patch for problem APAR PI63403 from support. Ensure that the patch also contains the fix for APAR PI64638, or that the build number of the core patch is is build 204 or higher..

EDI Wizard not creating a type tree for users in WebSphere Transformation Extender 8.4.1.4 and ITX 9.0.0

Due to a recent defect encountered in the core engine, when EDI Wizard is invoked via Partner Manager by users running under WebSphere Transformation Extender 8.4.1.4 (prior to build 23) or ITX 9.0.0 (prior to build 199), the EDI Wizard will generate an error and fail creating a type tree. For a workaround, please request a patch for APAR PI63429 from support for either WebSphere Transformation Extender 8.4.1.4 or ITX 9.0.0, as appropriate.

If using ITX 9.0.0, ensure that the patch also contains the fix for APAR PI63403. If running under a 64 bit Windows environment, also request patch for APAR PI64638 or ensure that the build number of the core patch is build 204 or higher for ITX 9.0.0.0, and build 29 or higher for WebSphere Transformation Extender 8.4.1.4.

Memory Corruption under WINDOWS 64-bit Launcher executing a RUN map

Due to a recent defect encountered in the core engine, when Launcher running on Windows under 64 bit executes a RUN map, the resource manager corrupts memory. For a workaround, please request from support a patch for APAR PI64638 for either WebSphere Transformation Extender 8.4.1.4 or ITX 9.0.0. Ensure that the patch also includes APARs PI64303 (not needed for WebSphere Transformation Extender 8.4.1.4) and PI63429, or that the build number of the core patch is build 204 or higher for ITX 9.0.0 and build 29 or higher for WebSphere Transformation Extender 8.4.1.4.

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

5. NEW AND CHANGED BEHAVIOR


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

Enhanced X12 and EDIFACT support

This version of Trading Manager supports the Pack for EDI V2.8.1.4 in order to support X12 7020 and EDIFACT 14a and 14b versions. However, a current patch of this pack needs to be obtained for APAR PI63435 to correctly work with TMGR 8.2.1.10 if executing Trading Manager under WebSphere Transformation Extender V.8.4, V.8.4.1, or V.9.0.0


Enhanced HIPAA support

This version of Trading Manager supports only the Pack for HIPAA EDI V4.4.1.6, thus allowing ICD 10 support. If you still require full support for addenda 4010 HIPAA versions, you must continue using a previous versions of Trading Manager: Trading Manager V.8.2.1.5 with HIPAA 4.3.2.2, or Trading Manager V.8.2.17 with HIPAA 4.4.1.1. However, in order to support version ANSI 7020, a current patch for APAR PI63433 must be obtained from support, as indicated in earlier sections of this document. This patch should also contain Patch for APAR PI63435.


============================================================
6. RESOLVED AUTHORIZED PROGRAM ANALYSIS REPORTS (APARs)
============================================================

This is a list of the APARs that are resolved in this version of the product:


APARDescription
PI43751SQL Server definition of table ArchiveInfo has incorrect column names.
PI44190AK905 shows 4 instead of 0 as both GS and GE contain same control number.
PI45641When the SV202-03 field is reduced to one character, it is rejected correctly in Compliance Check as Data Element Too Short. In Trading Manager, the same data is incorrectly rejected as Data Element Too Long.
PI60849Segment Terminator as (HEX 15 - NegativeACK) works correctly in Trading Manager V.8.2.1.1 but not with Trading Manager V.8.2.1.9.

This is a list of the APARs that need to be applied to other components used with Trading Manager:

APARDescription
PI63429Creating a type tree using the type tree wizard from Partner Manager fails due to a flag incorrectly set for the Group Exclude Character list. This is fixed in typesdb32.dll for build 23 of V.8.4.1.4 and build 199 for V.9.0.0
PI63403When running Audit log in ITX V.9.0.0, the <Datalog> portion is missing, causing the Trading Manager reject files to not contain expected information.
PI634337020 type tree needed to be added to type 1 restriction list to support Trading Manager V.8.2.1.10.
PI63435
Modification required for trees in EDI X12 2.8.1.4 pack to work with Trading Manager V.8.2.1.10 in WebSphere Transformation Extender V.8.4, V.8.4.1, and V.9.0.0.


============================================================
7. CONTACTING CUSTOMER SUPPORT
============================================================

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


============================================================
8. NOTICES AND TRADEMARKS
============================================================

This information was developed for products and services offered in the U.S.A.

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.

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

IBM World Trade Asia Corporation Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan

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.

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 Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply 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 Corporation
577 Airport Blvd., Suite 800
Burlingame, CA 94010
U.S.A.

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.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

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.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, a nd represent goals and objectives only.

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 the names and addresses used by an actual business enterprise 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.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Programming interface information
Programming interface information, if provided, is intended to help you create application software using this program.

General-use programming interfaces allow you to write application software that obtain the services of this program's tools.

However, this information may also contain diagnosis, modification, and tuning information. Diagnosis, modification and tuning information is provided to help you debug your application software.

Warning: Do not use this diagnosis, modification, and tuning information as a programming interface because it is subject to change.

Trademarks and service marks
IBM, the IBM logo and ibm.com are 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.
  • Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.
  • IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
  • Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
  • Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
  • Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
  • ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office
  • UNIX is a registered trademark of The Open Group in the United States and other countries.
  • Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom.
  • Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
  • Oracle and all Oracle-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.

Other product and service names might be trademarks of IBM or other companies.


This product includes software developed by the Eclipse Project
(http://www.eclipse.org/).

[{"Product":{"code":"SSR2U3","label":"WebSphere Transformation Extender Trading Manager"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Trading Manager","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"8.2.1.10","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
05 October 2022

UID

swg27048159