Release Notes
Abstract
These release notes contain information on the location from where you can download the software, instructions on installation, and the known problems and workarounds among other information, for the IBM Transformation Extender, Pack for Supply Chain EDI, version 10.2.2.0.
Content
IBM Sterling Transformation Extender Pack for Supply Chain EDI, V10.2.2.0 release notes.
© Copyright IBM Corporation 1998, 2016. All rights reserved.
© Copyright HCL Technologies Ltd, 2017, 2023. All Rights Reserved.
=====================================================================
CONTENTS
=====================================================================
About this release
Installation
Using the pack with the Design Server
Exit libraries EDIFACT, IATA, X12, and RAIL Compliance
Known limitations, problems, and workarounds
Resolved Authorized Program Analysis Reports (APARs)
Contacting customer support
Notices and trademarks
Note: IBM Transformation Extender was formerly called WebSphere Transformation Extender. Documentation, few interfaces, and few websites still refer to it as WebSphere Transformation Extender.
INSTALLATION
====================================================================
EDIFACT - Compliance Check – edifactCompliance .zip
Contains maps, schemas and sample data for the EDIFACT Compliance Checker. The maps are deployed and executed using one of ITX API’s or with the command server to validate your data against the supported EDIFACT Standards. Supported standards range from version 90_1 to D22A and D22B.
EDIFACT - Examples – edifactExamples .zip
Contains example maps, schemas, and sample data to support integration and transformation requirements. The examples use several EDIFACT D17A messages.
EDIFACT – Standards – edifdxxx_standard .zip
Where xxx is the EDIFACT version, contains the supported EDIFACT Standards to be used with integration and transformation requirements. For example, edifd20a_standard.zip contains the standard for EDIFACT version D 20a. Supported standards range from version 90_1 to D22A and D22B.
TRADACOMS – Standards – tradacomsStandardSchemas .zip
Contains the last published TRADACOMS Standard to be used with integration and transformation requirements. Version 96 is the last publication of the TRADACOMS Standard.
X12 - Compliance Check – x12Compliance .zip
Contains maps, schemas and sample data for the X12 Compliance Checker. The maps are deployed and executed using one of ITX API’s or with the command server to validate your data against the supported X12 Standards. Supported standards range from version 2003 to 8040.
X12 - Examples – x12Examples .zip
Contains example maps, schemas and sample data to support integration and transformation requirements. The examples use several X12 7040 messages.
X12 – Standards – ansixxxx_standard .zip
Where xxxx is the X12 version containing the supported X12 Standards to be used with integration and transformation requirements. For example, ansi8020_standard.zip contains the standard for x12 version 8020. Supported standards range from version 2003 to 8040.
=====================================================================
ABOUT THIS RELEASE
=====================================================================
Where to find the software to download
To download the software for this version of the IBM Sterling Transformation Extender Pack for Supply Chain EDI, go to Passport Advantage. This location will direct you to the Passport Advantage (PA) and Passport Advantage Express (PAE) overview page. The Passport Advantage (PA) and Passport Advantage Express (PAE) are comprehensive IBM programs by which clients may order eligible products. The customers can search PA and PAE for the following part numbers to download the files for Windows install and Red Hat OpenShift which include the project files used with the Design Server and certified containers.
ABOUT THIS RELEASE
=====================================================================
Where to find the software to download
To download the software for this version of the IBM Sterling Transformation Extender Pack for Supply Chain EDI, go to Passport Advantage. This location will direct you to the Passport Advantage (PA) and Passport Advantage Express (PAE) overview page. The Passport Advantage (PA) and Passport Advantage Express (PAE) are comprehensive IBM programs by which clients may order eligible products. The customers can search PA and PAE for the following part numbers to download the files for Windows install and Red Hat OpenShift which include the project files used with the Design Server and certified containers.
Part numbers for Supply Chain EDI V10.2.2.0, search:
- Windows install - G08WGML
- Red Hat OpenShift - G08WJEN
Note: IBM Transformation Extender was formerly called WebSphere Transformation Extender. Documentation, few interfaces, and few websites still refer to it as WebSphere Transformation Extender.
What's new in this release
New Configuration setting:
The workspace identification is configurable and that controls how work files are used for run map calls during compliance check execution. You can optimize the speed of map processing using the workspace configuration setting.
When processing a large amount of input data in a map, use the file-based workspace with default paging. For example -WU. When small amounts of data are processed, smaller page sizes and memory-based workspaces are recommended. For example -WM. The default setting is memory-based workspaces.
Pack Install Location:
With the recent addition of installation options to IBM Sterling Transformation Extender Design Studio version 11.0.0, there may be a need to adjust the location where packs are installed. These installation options offer the ability to choose a target Windows folder, typically within <program files>, as a security measure to prevent unauthorized modifications.
To ensure flexibility and accommodate modifications to pack artifacts, it is advisable to consider a different folder location, such as <program data>, for pack installation. This allows for greater flexibility in managing the pack's components.
The supply chain pack includes batch script files used for compiling all maps during compliance checking. It is important to note that if the default pack installation location (<TX install folder>\packs\supplychain_edi_vn.n.n.n) is not used, you will need to update the batch script files to match the new location of the TX Core component installation. This is important to ensure that the maps can be compiled correctly.
X12 component:
Contains the X12 Standard currency updates with version 8040.
X12U component:
The new component contains extended processing for the ISX segment. Full implementation of the ISX segment can be used with X12 standard versions 4010 to most current, when the ISA version is 00801 to most current. Contains the X12Standard currency updates with version 8040 and character encoding support for new ISX02 values 17-37.
Note: Using the ISX segment requires Trading Partner agreements. The configuration settings to ignore the ISX segment must be applied in the event an unexpected ISX segment is received.
EDIFACT component:
Contains the EDIFACT Standard currency updates with D22A and D22B versions.
TT-X12 component:
A new component that contains maps, schemas, and sample data for the travel and transportation X12 Compliance Checker. The standards contain a sub-set of messages related to the travel and transportation industry based on the full X12 standards. The maps are deployed and executed using one of the ITX API's or with the command server to validate your data against the supported X12 Standards. The supported standards are version 8010. The configuration and execution are similar to the X12 component.
x12isxTransform Example: Design Server Only:
A new component that contains maps, schemas and sample data to illustrate document flows with EDI X12 ISX encoding. There are 2 flows defined. The x12ToJsonFlow will use an X12 EDI document encoded as UTF-16LE and transform it to XML. A flow variable is defined with the decision to use the flow designer Format Converter node to create JSON output. The xmlToX12Flow will use XML input, transform to an X12 EDI document, and encode the document as UTF-16LE.
Documentation notes
View the latest product documentation
See the online documentation for the latest documentation for this product.
Supply Chain latest 10.2.2 documentation is available in the V11 online documentation, see What's new in Packs V10.2.2 for more details.
Translated documentation
The online documentation is provided in these languages:
- English (United States)
- French
For the latest product information, see the English version in the online documentation.
Viewing translated documentation
To display translated content in the online documentation:
- Open the online documentation. A typical URL to the documentation is shown below:
https://www.ibm.com/support/knowledgecenter/SSVSD8_n.n.n/com.ibm.websphere.dtx.welcome.doc/kc_welcome_nnn.html - Edit the URL to include the desired language code immediately after "/knowledgecenter":
https://www.ibm.com/support/knowledgecenter/<language code>/SSVSD8_n.n.n/com.ibm.websphere.dtx.welcome.doc/kc_welcome_nnn.html
As an example, enter the language code "/fr" to display French content. - Remove the "/<language code>" to return to the English display.
INSTALLATION
====================================================================
Exit libraries
The Windows Design Studio installation for the Pack for Supply Chain EDI, V10.2.2.0 contains a platform_support folder. The platform_support folder contains exit libraries, which are used during system runtime executions for compliance checking.
The Design Server installation for the Pack for Supply Chain EDI, V10.2.2 provides the exit libraries for all supported operating systems in the platform support directory and the ediPlatformSupport* project zip files. The exit library must be installed with the Windows Design Server. Install scripts are provided to help with installation for the exit library.
The compliance check exit library for z/OS is shipped in the XMIT file format.
After installing the Supply Chain EDI Component on a Windows workstation, perform the following steps for each z/OS execution platform prior to porting and executing the Supply Chain Compliance Check application on that platform.
Transfer the load library module file:
<install_dir>/packs/supplychain_edi_vn.n.n/platform_support/zos/31/edisvu.loadlib
or
<install_dir>/packs/supplychain_edi_vn.n.n/platform_support/zos/64/edisvu.loadlib
as binary to a z/OS dataset allocated as 80-byte fixed length records named my.exit.upload. There should be no ASCII to EBCDIC translation and no elimination of carriage return or line feed characters.
After the file is uploaded to z/OS, issue the TSO Receive command to create a load library.
At the prompt, enter the following: ready
Enter the following: receive inda ('my.exit.upload')
receive inda ('userid.edisvu.upload')
The following messages are displayed:
INMR901I Dataset EDISVU, UPLOAD from USER on NODENAME
INMR906A Enter restore parameters or 'DELETE' or 'END' +
Enter the name of the load library to be created as follows
da ('my.exit.upload')
da ('userid.edisvu.vxxx.loadlib')
Messages indicating that the load library is being created are displayed.
In the JCL responsible for executing the Supply Chain Compliance Check application, include a STEPLIB for the created load library that appears before the Transformation Extender Core Install loadlib. For example:
//STEPLIB DD DSN=MY.exit.LOADLIB,DISP=SHR
// DD DSN=MY.WTX.INSTALL.LOADLIB,DISP=SHR
Installation prerequisites
Before you install this version of the pack, you must install one of the following versions of IBM Transformation Extender:
- 11.0.0.0
- 10.1.2.0
- 10.1.1.0
- 10.1.0.0
Deployment to other operating systems
See the individual component documentation for information on deploying to other operating systems.
Installation directories
The pack components are installed in the following directory:
install_dir\packs\supplychain_edi_v10.2.2.0
Where <install_dir> indicates the installation location of the IBM Transformation Extender base product.
Installing the pack on Windows systems
To install the Pack for Supply Chain EDI on Windows systems, perform the following procedures:
- Obtain the image from Passport Advantage.
- IBM Transformation Extender 10.1.0: SCE_1022_v1010.zip
- IBM Transformation Extender 10.1.1: SCE_1022_v1011.zip
- IBM Transformation Extender 10.1.2: SCE_1022_v1012.zip
- IBM Transformation Extender 11.0.0: SCE_1022_v1100.zip
- Extract all the files containing the zip file to the TX install folder and packs location.
For example:
D:\IBM\TransformationExtender_11.0.0\packs
The pack components will be installed under the folder supplychain_edi_v10.2.2.0
Uninstalling the pack on Windows systems
To uninstall the pack from the Design Studio, delete the pack install.
Installing the pack for Design Server
For all other non-windows platforms, the exit libraries can be found in the IBM Transformation Extender 10.x.x runtime install\libs folder.
The exit and libraries for both Linux Windows Design Server may also be found in the image zip files. The zip files beginning ediPlatformSupport* contain the exit library used during system runtime executions for compliance checking, a script file to remove the exit from the default location, and a script file to copy the exit to the default location. The windows script files must be updated to the ITX core install location for example C:\IBM\TransformationExtender_11.0.0.
To install the Pack for Supply Chain EDI for the Design Server, perform the following procedures:
- Obtain the image zip file from Passport Advantage. The Industry Pack zip file may be found in the same location as the Design Server.
- IBM Transformation Extender Linux or Windows Design Server 10.1.0:
IBM_supplychain10.2.2.0_10.1.0.0.zip - IBM Transformation Extender Linux or Windows Design Server 10.1.1:
IBM_supplychain10.2.2.0_10.1.1.0.zip - IBM Transformation Extender Linux or Windows Design Server 10.1.2:
IBM_supplychain10.2.2.0_10.1.2.0.zip
The IBM_supplychain10.2.2.0_10.1.x.x zip and 11.0.x.x files contain two zip files, a set of projects to be used with Linux Design Server and a set of projects to be used with Windows Design Server. For example, to use the Supply Chain EDI version 10.2.2.0 with Design Server 10.1.1.0 perform the following steps:
- Unzip the IBM_supplychain10.2.2.0_10.1.1.0.zip.
- Unzip the IBM_linux_supplychain10.2.2.0_10.1.1.0.zip or
IBM_win_supplychain10.2.2.0_10.1.1.0.
The Design Server provides features for project zip file selection from a Windows system. - Using the Linux or Windows Design Server Web based user interface, select the project zip file you want to import and import the project zip file. The ITX Command Server might be used for the import if the project zip files are located on the same server as the target database.
Uninstalling the pack from Design Server
To uninstall the pack from the Design Server, delete the project.
=====================================================================
USING THE PACK WITH THE DESIGN SERVER
=====================================================================
The ITX Industry packs are provided in a single zip file, containing multiple project zip files. Each zip file is a Design Server project that can be imported into the server database. The project files contain maps, schemas and data files used for various industry standards compliance validation as well as examples and schemas to accelerate implementation for your business processes.
Project summaries
The following projects are contained in the Pack for Supply Chain EDI zip.
EDIFACT - Compliance Check – edifactCompliance .zip
Contains maps, schemas and sample data for the EDIFACT Compliance Checker. The maps are deployed and executed using one of ITX API’s or with the command server to validate your data against the supported EDIFACT Standards. Supported standards range from version 90_1 to D22A and D22B.
EDIFACT - Examples – edifactExamples .zip
Contains example maps, schemas, and sample data to support integration and transformation requirements. The examples use several EDIFACT D17A messages.
EDIFACT – ediblockchain – edifactExampleBlockChain .zip
Contains example maps, schemas, and sample data to illustrate using traditional EDI with blockchain. The example is using EDIFACT EDI documents, but the blockchain concept is not limited to EDIFACT or EDI documents.
Contains example maps, schemas, and sample data to illustrate using traditional EDI with blockchain. The example is using EDIFACT EDI documents, but the blockchain concept is not limited to EDIFACT or EDI documents.
EDIFACT – Standards – edifdxxx_standard .zip
Where xxx is the EDIFACT version, contains the supported EDIFACT Standards to be used with integration and transformation requirements. For example, edifd20a_standard.zip contains the standard for EDIFACT version D 20a. Supported standards range from version 90_1 to D22A and D22B.
ediPlatformSupport - validation exit libraries ediPlatformSupport*.zip
Contains the platform specific exit libraries and scripts to remove and copy the exit module. The exit library must be installed with the Windows Design Server. This file should not be used as a project import. See the EDIFACT, X12, AND RAIL COMPLIANCE section in this document.
ISO8583 – example - ISO8583Example.zip
Contains examples that demonstrate transformation using the ISO8583 standard.
IATA-API - Compliance Check – iata-apiCompliance .zip
Contains maps, schemas and sample data for the IATA-API EDIFACT Compliance Checker. The maps are deployed and executed using one of ITX API's or with the command server to validate your data against the supported standards. Supported standards are versions D14B and D15B. The standards contain messages IATA-API based on EDIFACT standards and IATA implementation guides.
IATA-API - Standards – iata-apiStandards .zip
Contains the supported IATA-API EDIFACT Standards to be used with integration and transformation requirements. Supported standards are versions D14B and D15B. The standards contain messages IATA-API based on EDIFACT standards and IATA implementation guides.
IATA-PNR - Compliance Check – iata-pnrCompliance .zip
Contains maps, schemas and sample data for the IATA-PNR EDIFACT Compliance Checker. The maps are deployed and executed using one of ITX API's or with the command server to validate your data against the supported standards. The standards contain messages IATA-PNR based on EDIFACT standards and IATA-PNR implementation guides V16.1 and V17.1.
IATA-PNR - Standards – iata-pnrStandards .zip
Contains the supported IATA-PNR EDIFACT Standards to be used with integration and transformation requirements. The standards contain messages IATA-PNR based on EDIFACT standards and IATA-PNR implementation guides V16.1 and V17.1.
Rail - Compliance Check – railCompliance .zip
Contains maps, schemas and sample data for the Rail X12 Compliance Checker. The maps are deployed and executed using one of ITX API's or with the command server to validate your data against the supported Rail Standards. Supported standards range from version 7030 to 7060.
Rail – Standards – railxxxx_standard .zip
Where xxxx is the Rail version containing the supported Rail Standards to be used with integration and transformation requirements. For example, rail7060_standard.zip contains the standard for Rail version 7060. Supported standards range from version 7030 to 7060.
TRADACOMS – Standards – tradacomsStandardSchemas .zip
Contains the last published TRADACOMS Standard to be used with integration and transformation requirements. Version 96 is the last publication of the TRADACOMS Standard.
TT-EDIFACT - Compliance Check – tt-edifactCompliance .zip
Contains maps, schemas and sample data for the EDIFACT Compliance Checker. The maps are deployed and executed using one of ITX API's or with the command server to validate your data against the supported standards. Supported standards are versions D19A and D15B. The standards contain messages related to the travel and transportation industry based on the full EDIFACT standards.
Contains maps, schemas and sample data for the EDIFACT Compliance Checker. The maps are deployed and executed using one of ITX API's or with the command server to validate your data against the supported standards. Supported standards are versions D19A and D15B. The standards contain messages related to the travel and transportation industry based on the full EDIFACT standards.
TT-EDIFACT - Standards – tt-edifactStandardSchemes .zip
Contains the supported EDIFACT Standards to be used with integration and transformation requirements. Supported standards are versions D14A and D19B. The standards contain messages related to the travel and transportation industry based on the full EDIFACT standards.
Contains the supported EDIFACT Standards to be used with integration and transformation requirements. Supported standards are versions D14A and D19B. The standards contain messages related to the travel and transportation industry based on the full EDIFACT standards.
X12 - Compliance Check – x12Compliance .zip
Contains maps, schemas and sample data for the X12 Compliance Checker. The maps are deployed and executed using one of ITX API’s or with the command server to validate your data against the supported X12 Standards. Supported standards range from version 2003 to 8040.
X12 - Examples – x12Examples .zip
Contains example maps, schemas and sample data to support integration and transformation requirements. The examples use several X12 7040 messages.
X12 – Standards – ansixxxx_standard .zip
Where xxxx is the X12 version containing the supported X12 Standards to be used with integration and transformation requirements. For example, ansi8020_standard.zip contains the standard for x12 version 8020. Supported standards range from version 2003 to 8040.
X12U - Compliance Check – x12uCompliance .zip
Contains maps, schemas and sample data for the X12U Compliance Checker. The version of X12 compliance enables the ISX character encoding processing. The Standard schemes are defined with UTF-8. A set of maps is included to perform the character decoding and encoding as defined in the ISX and compliance check configuration using the X12U Standard schemas as the target or source for processing. The maps are deployed and executed using the ITX API's or with the command server to validate your data against the supported X12 Standards. Supported standards range from version 4010 to 8040.
Contains maps, schemas and sample data for the X12U Compliance Checker. The version of X12 compliance enables the ISX character encoding processing. The Standard schemes are defined with UTF-8. A set of maps is included to perform the character decoding and encoding as defined in the ISX and compliance check configuration using the X12U Standard schemas as the target or source for processing. The maps are deployed and executed using the ITX API's or with the command server to validate your data against the supported X12 Standards. Supported standards range from version 4010 to 8040.
TT-X12 - Compliance Check – tt-x12Compliance .zip
Contains maps, schemas and sample data for the X12 Compliance Checker. The maps are deployed and executed using one of ITX API's or with the command server to validate your data against the supported standards. Supported standards are version 8010. The standards contain messages related to the travel and transportation industry based on the full X12 standards.
Contains maps, schemas and sample data for the X12 Compliance Checker. The maps are deployed and executed using one of ITX API's or with the command server to validate your data against the supported standards. Supported standards are version 8010. The standards contain messages related to the travel and transportation industry based on the full X12 standards.
TT-X12 - Standards – tt-x12StandardSchemes .zip
Contains the supported X12 Standards to be used with integration and transformation requirements. Supported standards are version 8010. The standards contain messages related to the travel and transportation industry based on the full X12 standards.
Contains the supported X12 Standards to be used with integration and transformation requirements. Supported standards are version 8010. The standards contain messages related to the travel and transportation industry based on the full X12 standards.
X12 - x12isxTransform – x12isxTransform.zip
Contains example maps, schemas and sample data to illustrate document flows with EDI X12 ISX encoding. There are 2 flows defined. The x12ToJsonFlow will use an X12 EDI document encoded as UTF-16LE and transform it to XML. A flow variable is defined with the decision to use the flow designer Format Converter node to create JSON output. The xmlToX12Flow will use XML input, transform to an X12 EDI document, and encode the document as UTF-16LE.
Contains example maps, schemas and sample data to illustrate document flows with EDI X12 ISX encoding. There are 2 flows defined. The x12ToJsonFlow will use an X12 EDI document encoded as UTF-16LE and transform it to XML. A flow variable is defined with the decision to use the flow designer Format Converter node to create JSON output. The xmlToX12Flow will use XML input, transform to an X12 EDI document, and encode the document as UTF-16LE.
=====================================================================
EXIT LIBRARIES EDIFACT, IATA, X12, AND RAIL COMPLIANCE
=====================================================================
In the same location as the project compressed files, there is also an ediPlatformSupport_IBM.tar.gz file for Linux Design Server and ediPlatformSupport.zip for Windows Design Server.
To use these files with the Linux Design Server, follow these steps.
- Make sure that the Design Server is installed and started.
- Create a temp directory called packs.
For example: /home/user/packs - FTP (in binary mode) the ediPlatformSupport_IBM.tar.gz to the pack’s directory defined in the previous step.
Perform the following steps in the temp directory:
- Extract the ediPlatformSupport_IBM.tar.gz file.
For example: $ tar -zxf ediPlatformSupport_IBM.tar.gz - Run the edisvusetup.sh script.
For example: $ ./edisvusetup.sh
This script copies the edisvu.so file to the ITX server. - Restart the Design Server: docker restart tx-server.
OPTIONAL:
- Run the cleanedisvu.sh script.
For example: $ ./cleanedisvu.sh
This script moves the edisvu.so file from the ITX server. - Restart Design Server: docker restart tx-server.
To use these files with Windows Design Server, follow these steps.
- Make sure that the Design Server is installed and started.
- Create a temp directory called packs.
For example: /home/user/packs
Perform the following steps in the temp directory:
- Extract the ediPlatformSupport.zip file.
- Update the edisvusetup.bat to use the ITX server install folder.
For example:
Replace <windows design server install> with C:\IBM\TransformationExtender_10.1.1 - Run the edisvusetup.bat script.
This script copies the edisvu.dll file to the ITX server. - If needed, stop/start the Design Server.
OPTIONAL:
- Update and run the cleanedisvu.bat script.
This script moves the edisvu.dll file from the ITX server. - Restart Design Server: docker restart tx-server.
=====================================================================
KNOWN LIMITATIONS, PROBLEMS, AND WORKAROUNDS
=====================================================================
Issues with the X12 7060 table data
- RFI 2377 - The 7060 version contains a new transaction 897, which has functional group id - SC. The code-list for GS01 element 479 does not list the 897 transaction to share the SC functional group id with the 832 transaction.
- MANUAL CHANGE: Move both messages out of the functional group and into the special groups with parent SC because parsing will find the 832 and not process the 897 under the functional group.
- RFI 2379 - X12 7060 for transaction 897 is not defined in the code list for ST01 element 143.
- MANUAL CHANGE: add 897 to ST01 code list.
- RFI 2380 - The 7060 version of the 832 adds the YNQ segment at position 1684 in loop 2000. The YNQ segment is also defined previously in loop 2000 at position 0450. We are unsure whether the duplicate definition meets the criteria documented in Section 2.2.10 under Design Rules?
- MANUAL CHANGE: Add a copy of YNQ segment as YNQ2 and manually add missing segments and loops to the inbound and outbound transactions. ** CAUTION ** Our manual changes to the 832 transactions were made as a temporary fix to enable the message to be included in the 7060 version. Using this transaction will cause unpredictable results and we advise using a known valid version of the 832 transaction ***
X12.org RESPONSE:
RFIs 2377 and 2379 are errata and will be fixed at version 008010. RFI 2380 is also errata and has been already repaired in 007061.
Possible M202 warning when building source maps
Building some of the source maps might trigger M202 warnings similar to the following:
M202 WARNING:
Map: FormatContrl Output: TestIndicator Element Good UNB Envelope
Control EnvelopedContrl
Parm 2 of EITHER doesn't match the required type.
These warnings can be ignored.
EDIFACT version 1 - 3 using syntax level B delimiters
EDIFACT versions prior to version 4 used different non-printable default delimiters for syntax level B (Syntax Id = UNOB), or higher. The EDIFACT type trees do not support these alternate delimiters. If you need to process data that uses these, create modified versions of the EDIFACT type trees that use these alternate delimiters, instead of the default delimiters used by version 4 and by syntax level A in the older standards.
To create modified type trees, follow these instructions:
- Copy the type tree from the pack to create a separate tree to be used for syntax UNOB interchanges. For example, copy edifd08b.mtt to edifd08b-unob.mtt.
- Edit the new type tree, to update the following categories. For each change, propagate the change to the item's subtree:
Composite Control EDIFACT EDI
- Change: Group Subclass ->Format->Component Syntax->Delimiter->Default to <US>
Envelope Control EDIFACT EDI
- Change: Group Subclass->Format->Component Syntax->Delimiter->Default to <GS>
- Change: Type Syntax ->Terminator->Default to <FS>
Composite Vxxxx EDIFACT EDI (NOTE: this category must be updated to be Format Explicit, to match its subtypes.)
- Change: Group Subclass->Format->Component Syntax->Delimiter->Default to <US>
Segment Vxxxx EDIFACT EDI
- Change: Group Subclass->Format->Component Syntax->Delimiter->Default to <GS>
- Change: Type Syntax->Terminator->Default to <FS> - Analyze and save the new type tree, and use the updated tree in your map, or maps.
Type trees warnings
The following type trees have warnings when analyzed:
- ccx12.mtt (Pack for X12)
- ccedf.mtt (Pack for EDIFACT)
Pack for EDIFACT support for batch messages
The Pack for EDIFACT supports batch messages, but it does not support interactive messages.
====================================================================
RESOLVED AUTHORIZED PROGRAM ANALYSIS REPORTS (APARs)
====================================================================
For a list of 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.
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, and 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 the 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 the 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 obtains 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.
Privacy Policy Considerations
IBM Software products, including software as a service solution, ("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 a customer the ability to collect personally identifiable information from end users via cookies and other technologies, you should seek your 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 the IBM Privacy Policy, the IBM Online Privacy Statement section entitled "Cookies, Web Beacons and Other Technologies," and the IBM Software Products and Software-as-a-Service Privacy Statement.
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
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 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 the 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.
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 the 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.
HCL
2600 Great America Way,
Suite 401, Santa Clara CA 95054
USA
Attention: Office of the General Counsel
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
2600 Great America Way,
Suite 401, Santa Clara CA 95054
USA
Attention: Office of the General Counsel
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
HCL
2600 Great America Way,
Suite 401, Santa Clara CA 95054
USA
Attention: Office of the General Counsel
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 disclaimers 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 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 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.
2600 Great America Way,
Suite 401, Santa Clara CA 95054
USA
Attention: Office of the General Counsel
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 disclaimers 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 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 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.
HCL
2600 Great America Way,
Suite 401, Santa Clara CA 95054
USA
Attention: Office of the General Counsel
2600 Great America Way,
Suite 401, Santa Clara CA 95054
USA
Attention: Office of the General Counsel
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, and 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 the 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 the 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 obtains 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.
Privacy Policy Considerations
IBM Software products, including software as a service solution, ("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 a customer the ability to collect personally identifiable information from end users via cookies and other technologies, you should seek your 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 the IBM Privacy Policy, the IBM Online Privacy Statement section entitled "Cookies, Web Beacons and Other Technologies," and the IBM Software Products and Software-as-a-Service Privacy Statement.
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
- Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
- Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
- Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.
- UNIX is a registered trademark of The Open Group in the United States and other countries.
This product includes software developed by the Eclipse Project (http://www.eclipse.org/).
[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSP4Z2","label":"IBM Sterling Transformation Extender Pack for Supply Chain EDI"},"ARM Category":[{"code":"a8m0z000000bmMTAAY","label":"Pack for Supply Chain EDI"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"10.2.2"}]
Was this topic helpful?
Document Information
Modified date:
19 April 2024
UID
ibm17055913