Release Notes for WebSphere Transformation Extender V8.1.0.3

Content

IBM WebSphere® Transformation Extender, Version 8.1, Fix Pack 3
release notes (rev. 5)

© Copyright IBM Corporation 2006, 2007. 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. Command Server Notes
   For the following products:
• IBM WebSphere Transformation Extender with Command Server
• IBM WebSphere Transformation Extender with Launcher
• IBM WebSphere Transformation Extender Design Studio
6. Software Development Kit Notes
   For the following products:
• IBM WebSphere Transformation Extender
• IBM WebSphere Transformation Extender SDK
7. Launcher Studio Notes
   For the following product:
• IBM WebSphere Transformation Extender Launcher Studio
8. Resolved Authorized Program Analysis Reports (APARs)
9. Contacting customer support
10. Notices and trademarks

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

This release, while considered the third service pack for release 8.1, is a full version of the product. If you have release 8.1, 8.1 SP1 (8.1.0.1), or 8.1 SP2 (8.1.0.2) installed, you must completely uninstall it before installing 8.1.0.3. Release 8.1.0.3 can coexist on the same computer as prior point releases. For example 7.5, 8.0, and 8.1 can coexist on the same computer.

For additional information such as answers to frequently asked questions, and solutions to or workarounds for problems that have been documented for this release, view the Technotes that are on the IBM Support Web site.

The new features in this release are listed in the documentation under "What's New".

This file contains cumulative information from all service packs released for 8.1.

The sections in this file provide release notes for the IBM WebSphere Transformation Extender products listed below. There are also sections for notes that apply to specific products.

- IBM WebSphere Transformation Extender with Command Server
- IBM WebSphere Transformation Extender with Launcher
- IBM WebSphere Transformation Extender with Launcher Studio
- IBM WebSphere Transformation Extender Design Studio
- IBM WebSphere Transformation Extender
- IBM WebSphere Transformation Extender SDK


Java™ Runtime Environment (JRE)
WebSphere Transformation Extender 8.1.x is installed with and supports the IBM version of Java™ 2 Runtime Environment, Standard Edition, Version 1.4.2.

We recommend that you use the included JRE. If you configure your WebSphere Transformation Extender product installation to a different JRE, it must be the same level as the included version.


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


Default installation location
[PK55720] The default location in which the WebSphere Transformation Extender products are installed is:
c:\IBM\WebSphere Transformation Extender 8.1

If you already have references to the default installation location from previous release installations, which was c:\Program Files\IBM\WebSphere Transformation Extender 8.1, during the product installations for this release, change the target installation location to match the path you are already referencing.


Installing on your Windows Vista operating system
If you are installing the WebSphere Transformation Extender products on your Windows Vista operating system, do not specify c:\Program Files in your target installation location because of compatibility issues.

See the WebSphere Transformation Extender V8.1 Compatibility Upgrade for Windows Vista technote on the WebSphere Transformation Extender Support Web page, which has a statement about installing WebSphere Transformation Extender outside the Program Files directory.


Installation error: uncompress not found
The WebSphere Transformation Extender installation programs for UNIX operating systems rely on the UNIX "uncompress" program. In some Linux installations, the "uncompress" program might not be available. If you encounter an installation error that reports "uncompress: not found", the workaround is to either install the appropriate package or create an "uncompress" symbolic link that links to gzip.


Path location for the response files
When you are using the Installer user interface (UI) to do a silent installation of the products on UNIX environments and you have selected Generate Response files, at the Response file directory prompt, you must enter the same directory path location for the preconfigured response files as you previously entered for the directory path location that appears on the second screen of the UI. If you do not enter the same path, the "Installation failed" error message will appear although the products have successfully been installed.


InstallShield language selection dialog
When you use the Installer graphical user interface (GUI) to install the IBM WebSphere Transformation Extender products on Windows environments, do not cancel the InstallShield dialog that prompts you to select the language in which you want the installation dialogs to be presented. If you do click Cancel before
you select the language, the Installer GUI will stop responding or "hang." After you select a language, you can then click Cancel during the InstallShield installation at any point, which will end the installation process and return you to the Installer GUI properly.

If you canceled the dialog before you made your language selection and the Installer GUI has stopped responding, exit the Installer GUI and then restart it.


Product requirement for exporting type trees as schema
The Export as Schema utility that you can use to export a type tree either through the Design Studio by selecting Tree > Export as Schema, or the texport utility command in the command line outside the Design Studio GUI, requires Microsoft .NET framework version 1.0, or 1.1.


Configuring UNIX environment variables
The environment variables required to execute an WebSphereTransformation Extender map or system must be set prior to execution.

You can set the environment variables (PATH, DTX_TMP_DIR, DTX_HOME_DIR, and the appropriate library path variable for your platform) by running the setup program.

After you log on to your computer, execute the setup program in the WebSphere Transformation Extender installation directory before executing a map or system file (using the Launcher). This sets the required environment variables for this session only. Modify the .profile script to set the environment variables for all sessions.

Note: The following command procedure assumes that your UNIX command line environment is the Korn (ksh) shell.

Execute the command as follows:

. /install_dir/setup

where install_dir represents the directory in which you have installed your WebSphere Transformation Extender products.

Note: There must be a space between the initial period (.) and the command path.


Soft DATA Segment or Heap Size on UNIX systems
Using the default setting for the Soft DATA segment or heap size parameter can cause problems on UNIX platforms. This Soft DATA Segment value should be reset to a value larger than the default by the root user.

Note: On AIX platforms, use IBM's Smit (System Management Interface Tool) utility to reset the Soft DATA Segment value.

Set this value one time for each user (not for each session).
Choosing the correct value depends on the following factors:
- amount of memory available on the machine
- size of data being processed
- type of processing occurring on the respective data
- other major applications that may be running on the machine

If memory permits, start with the default value and increase it as needed. Use the following command to set the value within your own environment temporarily for testing the value setting:

ulimit -d <value>

Note: When setting the Soft DATA Segment value, the change takes effect only for the current session.


Required IBM XL C/C++ Run-Time Package Maintenance Level
If you are currently using either the 7.0.0.1 or 7.0.0.2 maintenance levels of the IBM XL C/C++ run-time environment component for AIX 5 (xlC.aix50.rte run-time package), you must install maintenance level 7.0.0.3 or higher to use the WebSphere Transformation Extender software on AIX platforms. To download the latest maintanance level of xlC.aix50.rte run-time package, contact IBM AIX support.


Running the maxdata script on AIX platforms
The maxdata script is provided to increase the maximum values for memory availability on your AIX system. Run the maxdata script prior to executing any WebSphere Transformation Extender maps. The script requires a 777 permission level. Run the script only once for each respective executable and run it on the respective executable(s) whenever the executable gets updated or replaced during the installation of a patch or update.


HP-UX product requirements
The following are the recommended settings for max_thread_proc and maxdsiz when running the Launcher on HP-UX platforms:

Kernel Parameters Default Recommended
max_thread_proc 64 512
maxdsiz 64 MBytes <user dependent>

The max_thread_proc default of 64 processes is typically not enough and should be increased to 512. For maxdsiz, the value is dependent upon the amount of available memory and the size of the data used in the maps being run. The default of 64 MBytes is typically not enough. With large data sizes and if memory permits, 512 MBytes is recommended for maxdsiz.


Recommended patches

To use any of the following Java-based adapters, install the patches recommended for your HP-UX version and Quality Pack:

CORBA Adapter
Java Class Adapter
Java Message Service (JMS) Adapter
JNDI Adapter

The URL for these patches on the Hewlett-Packard Web site is:

http://www.hp.com/products1/unix/java/java2/sdkrte14/downloads/index_pa-risc.html

If you are using HP-UX version 11.11, the following patch is required to run any of the above-mentioned, Java-based adapters:

PHSS_28871


Configuring Java-based adapters
The instructions below require you to modify the CLASSPATH environment variable. This can be done directly, or by adding the JAR files to the dtx.ini file. To do so, add entries to the [External Jar Files] section.

For example:

[External Jar Files]
jarN=c:\mypath\myjar.jar

Note: N represents the next available number if multiple jar entries exist.

For example:

[External Jar Files]
jar1=c:\J2EE\lib\j2ee.jar
jar2=c:\mypath\myjar.jar

Note: Environment variables can not be used in these entries.

1. (This step is not necessary for AIX and HP-UX platforms.)
   Install Java™ 2 SDK, Enterprise Edition (J2EE™) v1.4.2 and set environmental variable J2EE_HOME to point to the installed directory. Update the CLASSPATH environment variable as described below.
   
   For Windows: %J2EE_HOME%\lib\j2ee.jar
   
   For Sun Solaris: $J2EE_HOME/lib/j2ee.jar
   
2. The IBM version of Java™ 2 Runtime Environment, Standard Edition v1.4.2 is provided with this release. Make sure the environment variable JAVAHOME points to the installed location of this version of the JRE, and that the CLASSPATH environment variable includes:
   
   %JAVAHOME%\lib
   
3. For Windows platforms only: Set the PATH environment variable to include the following:
   
   install_dir\java\bin
   
   where install_dir represents the directory in which you have installed your WebSphere Transformation Extender products.
   
4. For UNIX systems only: Ensure that the client-side LIBPATH environment variable contains a reference to the directory in which Java 2 JRE is installed. Specifically, this is the directory in which the libjvm.s* and libjava.* files are located.
   
   For example:
   
   $(JAVAHOME)/jre/bin/classic:$(JAVAHOME)/bin
   
   Library path environment variables:
   
   HP-UX: SHLIB_PATH (SHLIB_PATH should point to the hotspot subdirectory instead of classic.)
   
   Sun Solaris: LD_LIBRARY_PATH
   
   AIX: LIBPATH
   
   Follow any provider-specific installation and setup instructions.

CICS Adapter
The CICS adapter requires the cicssrvr.loadlib file that is shipped with WebSphere Transformation Extender and is located in the installation directory. The cicssrvr.loadlib file includes server-side components required to use the CICS adapter to connect to CICS.

To install it, follow these instructions:

1. Transfer the cicssrvr.loadlib file in binary mode from the installation directory on your computer to a z/OS data set with 80 byte fixed-length records (RECFM=FB, LRECL=80, system-determined blksize).
   
   This means no ASCII-to-EBCDIC translation and no elimination of carriage-return or line-feed characters.
   
2. After you have installed the file on z/OS, issue the TSO RECEIVE command to create a load library from it. At the "READY" prompt, type the following:
   
   receive inda(‘my.upload’)
   
   The following messages are displayed:
   
   INMR901I Dataset MY.UPLOAD from USER on NODENAME
   INMR906A Enter restore parameters or 'DELETE' or 'END' +
   
3. Type the name of the load library to be created as follows:
   
   da('my.loadlib')
   
   Messages are displayed, indicating that the load library is being created.
   
4. Define the programs to the CICS region that will be running the CICS Adapter server-side components.
   
   The programs can be defined to CICS by adding the following statements to the CICS CSD definitions. To update the CSD, use either the DFHCSDUP CICS batch utility program or use the CEDA transaction and use the following statements as an example:
   
   DEFINE PROGRAM(DTXC3270)
   GROUP(DTXCICS)
   DESCRIPTION(3270 BRIDGE EXIT)
   LANGUAGE(LE)
   DATA(ANY)
   
   DEFINE PROGRAM(DTXCDRIV)
   GROUP(DTXCICS)
   DESCRIPTION(ADAPTER DRIVER)
   LANGUAGE(LE)
   DATA(ANY)
   
5. Add the cicssrvr load library to the DFHRPL concatenation for the CICS region that will be running the CICS adapter server-side components.

DB2 Adapter (UNIX)
If you are using the AIX DB2 Adapter, you must have the DB2 client version 8.1 fix pack 3 or later installed on the client computer.


Java Class Adapter
To run the Java Class Adapter example when you are using a JRE other than the one supplied with the product, xerces.jar must be in the class path. You can obtain xerces.jar from the Apache Web site.


JCA Gateway Adapter
This version of the J2EE Connector Architecture (JCA) Gateway adapter consists of two installation components: client-side and server-side. The client-side is the machine upon which the WebSphere Transformation Extender product is installed and running. The server-side is the application server.

CLIENT-SIDE
WebSphere Transformation Extender must be installed before installing the JCA Gateway adapter on the client-side machine.

SERVER-SIDE
A J2EE-compliant application server that supports the EJB 2.0 and JCA 1.0 specifications is required.


JNDI Adapter
The following indicates the supported JNDI drivers for use with the JNDI Adapter:

- COS Naming service provider, 1.2.1 release
- DNS Service Provider, 1.2 release
- File system service provider, 1.2 beta 3 release
- LDAP service provider, 1.2.4 release
- RMI registry service provider, 1.2.1 release


MIME Adapter
[PK67753]The MIME adapter requires the j2ee.jar and mail.jar files, or equivalent jar files that contain the J2EE and "javax.mail" classes. These modules are not shipped with WebSphere Transformation Extender, but are still required by the MIME adapter to properly process MIME data. After the jar files are installed from an appropriate j2ee installation, modify the CLASSPATH to include those modules.


Oracle and Oracle AQ Adapters
Only Oracle database and Oracle AQ versions 9i and 10g are supported in this release. Oracle database and Oracle AQ adapter library files for version 9i are installed by default and are referred to as the "base" product. However, both 9i and 10g libraries are provided in the product installation directory.

To use 10g, rename the 10g library file (for example, m4ora10g.dll) to the "base" library file name (for example, m4ora.dll).

Oracle database adapter "base" library files:
- m4ora.dll (Windows)
- libm4ora.so(.sl) (UNIX)

Oracle AQ adapter "base" library files:
- m4aq.dll (Windows)
- libm4aq.so(.sl) (UNIX)

After the installation process completes, use the following platform-specific instructions to rename a versioned library file (10g in this case) to the base library file.

UNIX

1. Change the directory to install_dir/libs.
2. Copy the applicable Oracle library file for "backup" purposes:
• For the Oracle database adapter, make a copy of libm4ora.so(.sl).
• For the Oracle AQ adapter, make a copy of libm4aq.so(.sl).
3. In the installation directory, locate the 10g library file and rename it to be the base library file:
• For the Oracle database adapter, rename libm4ora10g.so(.sl) to libm4ora.so(.sl).
• For the Oracle AQ adapter, rename libm4aq10g.so(.sl) to libm4aq.so(.sl).
4. Move the renamed library file to libs directory.
   
   Note: To revert back to 9i, you can repeat the same process using the additional 9i libraries that were installed with the product. For example, rename libm4aq9i.so(.sl) to libm4aq.so(.sl).

Windows

1. Go to the product installation directory.
2. Copy the applicable Oracle library file for "backup" purposes:
• For the Oracle database adapter, make a copy of m4ora.dll.
• For the Oracle AQ adapter, make a copy of m4aq.dll.
3. In the installation directory, locate the 10g library file and rename it to be the base library file:
• For the Oracle database Adapter, rename m4ora10g.dll to m4ora.dll.
• For the Oracle AQ adapter, rename m4aq10g.dll to m4aq.dll.

To revert back to 9i, you can repeat the same process using the additional 9i libraries that were installed with the product. For example, rename m4ora9i.dll to m4ora.dll.

When you use Oracle database and AQ adapters together in the same system, their Oracle client versions (9i or 10g) must match and also be for the same version of Oracle that is installed on the server.

For example, if Oracle 10g is installed on your server, and you want to use both the Oracle database adapter and the Oracle AQ Adapter in the maps in your system, you must use the 10g version for both adapters. You cannot use a 9i Oracle database adapter with a 10g Oracle AQ adapter in this case. They must both be the 10g version.


VAN Adapter
Scripts for the VAN adapter are located in:

install_dir\examples\adapters\van\scripts

The VAN adapter installation requires that a current version of Cleo A+ must already be installed. The adapter has been successfully tested with Cleo A+ Version v2.36.03 on the Windows platform and v3.17.20 on the UNIX platform.

Customers installing the VAN Adapter for the first time should contact CLEO Communications and order Cleo A+ for Windows.

CLEO Communications
Sales Department
4203 Galleria Drive
Loves Park, IL 61111
Phone: 800.233.2536, x 2693
Fax: 815.654.8294
Email: SalesIL@cleo.com
Web Site: http://www.cleo.com/

Customers upgrading from an earlier version of the VAN adapter should also contact CLEO directly, according to the contact information above, to order an upgrade from the earlier version of Cleo A+ provided with the VAN adapter. When ordering your upgrade, you must provide the serial number from your original Cleo A+ software.


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

• Maps, type trees, and systems from versions 5.0 and later can be used with 8.1.0.3. You must regenerate systems, and although it is not always required for running maps from an earlier version, you should reanalyze and save the type trees, and save and recompile the maps; otherwise, the processes must convert the files each time they load the files.

• If you are migrating from 8.0 to 8.1, you must run your database triggering scripts in order to successfully run source-triggered database systems. After version 8.1 is installed on the supported Oracle or SQL Server databases, no earlier release of WebSphere Transformation Extender can use triggering on that database because the client and source would reference different names and result in failure.

• To use the new code page functionality, you must make new selections for the Data Language and National Language type properties in your type trees.

• If you previously used a non-international version of WebSphere Transformation Extender (formerly DataStage TX or Mercator), Native has been redefined to be Latin1 instead of ASCII.

• During installation, if you are prompted to register this version as the default program for opening WebSphere Transformation Extender file types and you choose "Yes", all WebSphere Transformation Extender files, such as *.mtt or *.mms, will open with this version (8.1).

• [PK55722] When you use the dsmapconv command (Map Migration utility) to convert a map from WebSphere Transformation Extender version 6.7.1 to WebSphere Transformation Extender version 8.1.x, after the type tree has converted successfully, some of the input map rules might not be able to be converted, and will cause the dsmapconv map conversion process to fail. You can view the results in the dsmapconv log file.

If the dsmapconv map conversion process fails because some map rules were unable to be converted, do the following procedures in Map Designer to complete the conversion process:

1. Open the map.
2. Delete the unresolved rules.
3. Compile and rerun the map.

String Literals
All string literals held in rules are now encoded in UTF-16 (Unicode) rather than the Native formats used previously. The strings will be converted to the target code page before being used in the rule. However, when a map writes a string literal to a binary character field, the data will be written as UTF-16 because binary objects have no code page encoding assigned to them.


Opening Files from an earlier version
When a source file from an earlier version of a WebSphere Transformation Extender product component is saved in the current version, the content and structure of that file is automatically converted to the format for the current version.

After conversion to the current version formats, do not open these files in earlier versions of a WebSphere Transformation Extender product component because the format of the map source has changed and there are additional added features that are not supported in the earlier versions.

A behavior change should be noted regarding how files are converted prior to the v6.7 release. Previous versions would convert *.mtt files on disk; v6.7 and this version allow *.mtt files to be converted in memory when the file is opened. The backup *.omt file is not created until the file is saved.

For other files:
- *.mms files do not need to be converted for the current version.
- A map created in an earlier version opens in the current version.
- *.msl files do not need to be re-generated. They are converted on-the-fly.
- *.mmc files do not need to be recompiled.
- *.msd files still work the same way, creating an *.osd when the file is opened.
- *.mdq files should still open in the current version.


Recommendations for preparing maps to run in this version

• Analyze each type tree file for logic and structure and then save it in the current version of the Type Designer.
  
• Regenerate type trees for queries, tables, and stored procedures.
  
• For maps that will be executed using a current version of the Command Server or Launcher, build all maps using the equivalent (current) version of the Map Designer.
  
• Build and generate the Launcher system (.msl) file or the command file for all systems defined in the current version of the Integration Flow Designer.
  
• If you are upgrading from an earlier version of the UNIX Launcher (formerly known as the Event Server) in which you used a script file containing the unsupported "lci -start" and "lci -stop" features to start and stop your UNIX Launchers, note that these commands have been replaced by a fully supported and documented feature of the Management Console. You must change your existing scripts using lci as follows:
  
  To start the Launcher:
  FROM: TO:
  lci -start launcher.sh -start
  
  To stop the Launcher:
  FROM: TO:
  lci -stop launcher.sh -stop <listen_port>
  
  where:
  <listen_port> is the number of the first designated listening port in the range specified in the LauncherAdmin.bin file. The default value is "5015" and it is not required for the -start option. However, if it is provided, it should match the first listening port specified in the LauncherAdmin.bin file.
  
• If you have designed maps that could produce 0 bytes of data to an adapter (this is especially critical for R/3 adapters), you must change the OnSuccess setting to CreateOnContent or use the -XO adapter option.
  
• When opening a map in this version that was created in an earlier version that still references a custom adapter or an adapter that is no longer supported, the Source or Target in the Edit Card dialog will be blank. The map will still build successfully, but will result in a "Source not available" or "Target not available" message when executed. The solution is to select an adapter from the list in the Edit Card dialog.

Converting type trees generated in earlier versions
You can use the XML Type Tree Compatibility utility wizard (invoked from the Type Designer) and the dsxmlconv utility command (invoked from the command line) to convert type trees that were generated in
WebSphere Transformation Extender versions 6.7, SP1, SP2, and 7.0.


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


Number elements with length
There is a known issue with number elements that can occur after importing an XML Schema that contains a nillable element. When using the generated XML type tree, the validation map might run successfully, however, the generated XML output is invalid for the Schema.

To work around this issue, modify the generated XML type tree by changing the element type (Item Subclass property) from Number to Text for the elements that contain a nillable element.


BEA Tuxedo Adapter temporarily unavailable
Due to BEA licensing issues, the BEA Tuxedo Adapter is not available in this release of WebSphere Transformation Extender.


Map Designer

• The use of IN on a single object in the DataAudit settings causes the Map Designer to stop responding.

• Due to a problem with 3rd party software, the "Other" selection button for creating custom breakpoint colors for the Map Debugger is not keyboard accessible.

Resource Registry
When using the resource registry for database aliases defined in the database/query file (.mdq) or command line, you should define the alias in the Global section of the resource registry for both Command Server and Launcher.


SNMP Collection temporarily unavailable
Due to licensing issues, the SNMP Collection is not available in this release of WebSphere Transformation Extender.


PACKAGE function change
There has been a change to the PACKAGE function, where it will now return a valid code page for data contained within group objects, which previously had an unknown code page.

This primarily affects the following three map rule functions on all platforms:

- GET
- PUT
- RUN

For example, if you are running a map on the UNIX System Services (USS) execution environment, that is set up to use the Java adapter, and has a rule that uses the PACKAGE function, change the rule to use, instead, the CPACKAGE function. Also, specify the character set as NATIVE for the second argument on the rule. Because of a change to the PACKAGE function, if you use it in this specific case, the map will convert the data to the NATIVE code page, which might be invalid for the Java adapter, and cause a Java exception error.

If you are running maps on the USS execution environment, the character set for NATIVE is EBCDIC, which is invalid for the JAVA adapter.

Change the rule from:

GET("JAVA","-T",PACKAGE(GROUP:RECORD))

to:

GET("JAVA","-T",CPACKAGE(GROUP:RECORD,"NATIVE"))

In this example, when you specify NATIVE in the second argument of the CPACKAGE function, the function treats the data as if it already is in the appropriate code page and therefore, does not attempt to convert it to NATIVE.


Building maps for z/OS
When a map is built for the z/OS platform, type and map names are converted to EBCDIC. When a type or map name has characters that cannot be converted to EBCDIC, a series of question marks (??) will be substituted. This scenario might occur as a result of importing an XML Schema that contained non-EBCDIC encoding.


Known issue with Oracle when DB2 and Oracle Client libraries loaded
There is a known issue with the Oracle 9i Client and Oracle 10g Client libraries that occurs when both an Oracle Client Library and a DB2 Client library are present.

Because of the Oracle Client library issue, the following problems could occur with your WebSphere Transformation Extender maps:

• When both the DB2 Adapter and Oracle Adapter are used in a map, the map fails (crashes).
• When both the DB2 Client and Oracle Client libraries are loaded, a failure (crash) occurs when the map attempts to connect to the Oracle database.

To work around this issue, you can regenerate the Oracle Client library using the -Bsymbolic link option or contact Oracle for fix information.


=====================================================================
5. COMMAND SERVER NOTES
=====================================================================

These notes are for the Command Server component of the following products:
- IBM WebSphere Transformation Extender with Command Server
- IBM WebSphere Transformation Extender with Launcher
- IBM WebSphere Transformation Extender Design Studio

This section contains the following topics:
- Installation Information
- Additional UNIX Run-Time Information
- Set Location for Temporary Files (DTX_TMP_DIR)


Installation Information
Because procedures for Command Servers for Windows, HP-UX, RS/6000 AIX, and Solaris platforms might differ slightly, specific instructions are provided during the installation program to guide you.

The Command Servers for Microsoft Windows are components of the Client install and are installed with the IBM WebSphere Transformation Extender with Command Server and IBM WebSphere Transformation Extender with Launcher. These Command Servers are also available as components of the Command Server install for Windows-based platforms to be installed on your server for run-time purposes.

The ability to run maps at design time is provided with the IBM WebSphere Transformation Extender Design Studio install, but only from inside the Map Designer.

The HP-UX, RS/6000 AIX, and Solaris Command Servers are available as components of each platform-specific Command Server install to be installed on your server for run-time purposes.

The additional Command Servers for z/OS (Batch and CICS) that are not installed as components of the installation program for the products discussed in this file are available on platform-specific media. For information about the system requirements and procedures for installing these Command Servers, see the platform-specific readme, release notes, and the Program Directory.

Additional UNIX Run-Time Information
You must also manually set the shared library path according to your platform. If you are going to configure the environment variables manually, do not execute the setup program; refer to the following section, Set Location for Temporary Files (DTX_TMP_DIR), for instructions.

Set Location for Temporary Files (DTX_TMP_DIR)
During map execution, the Command Server creates temporary files for resource handling purposes and for retaining debug information. The default directory for these temporary files is /tmp. However, you can specify the directory where you want these files to be kept by setting the DTX_TMP_DIR environment variable.

For example:

DTX_TMP_DIR=install_dir/tmp
export DTX_TMP_DIR

Note: If you choose to allow multiple groups to access the Command Server engine, the directory specified for DTX_TMP_DIR requires permission 777 to provide permission to the user, the group, and all others.

To accomplish this, run the chmod command:

chmod 777 $DTX_TMP_DIR

In addition, for multiple users or groups, define a DTX_TMP_DIR instead of letting it default to /tmp. This
DTX_TMP_DIR variable must be defined and exported prior to running the chmod command. The DTX_TMP_DIR variable is defined and exported by the user or with the setup script.

Environmental Debug Information (DTX_DEBUG)
If a problem is encountered during map execution and the DTX_DEBUG environment variable had been defined, the Command Server can produce environmental debug information that can be helpful when determining the cause of the problem.

When you define the DTX_DEBUG environment variable, environmental debug information is recorded in a file named dtxinfo.log located in the directory defined by the DTX_TMP_DIR environment variable (which is the /tmp directory if DTX_TMP_DIR is not defined).

By default, the DTX_DEBUG environment variable is not defined and environmental debug information is not recorded.

Enabling Environmental Debug
To enable the environmental debug facility, set the DTX_DEBUG environment variable to TRUE. For example:

DTX_DEBUG=TRUE
export DTX_DEBUG

The information recorded in the dtxinfo.log file provides information that can be useful when troubleshooting a specific map. The following is a sample of the information contained in the environmental debug file:

PROCESS_ID: 2309, API_REF: 1
Date/Time: Fri Jul 25 14:30:09.279783 2003
FILE: mercmain.c, line: 714
info: [IBM WebSphere Transformation Extender Product
Version: 0.0]

PROCESS_ID: 2309, API_REF: 1
Date/Time: Fri Jul 25 14:30:09.280252 2003
FILE: mercmain.c, line: 744
info: [IBM WebSphere Transformation Extender RUNNING:
Fri Jul 25 14:30:09 2003]

PROCESS_ID: 2309, API_REF: 1
Date/Time: Fri Jul 25 14:30:09.470357 2003
FILE: mercrun.c, line: 1951
New Map File - Fri Jul 25 14:30:09 2003
[/install_dir/examples/general/map/sinkmap/sinkmap.mmc]

Disabling Environmental Debug
To disable the environmental debug facility, set the DTX_DEBUG environment variable to FALSE.

For example, you might type:

DTX_DEBUG=FALSE
export DTX_DEBUG

File Locking (DTX_FILE_LOCKING)
The file locking facilities allow two or more mapping processes or threads to write to the same output file or
files in a controlled manner. These files include not only output files, but also work files, audit log files, and trace files.

File locking is disabled by default.

The Command Server for UNIX uses file locking, so you must set the DTX_FILE_LOCKING environment variable to TRUE.

Enabling File Locking
File locking is disabled by default; that is, DTX_FILE_LOCKING environment variable is set to FALSE or
is not defined. To enable file locking, set the DTX_FILE_LOCKING environment variable to TRUE.

For example:

DTX_FILE_LOCKING=TRUE
export DTX_FILE_LOCKING

Note: To use file locking, the DTX_TMP_DIR environment variable must be set to a common directory for all instances where maps are using common output files.

Disabling File Locking
To disable the file locking facility, the DTX_FILE_LOCKING environment variable must be set to FALSE, which is the default value.

For example:

DTX_FILE_LOCKING=FALSE
export DTX_FILE_LOCKING

Note: If you do not want to use file locking, and the DTX_FILE_LOCKING environment variable is not defined, you must set DTX_TMP_DIR to unique directory paths for each mapping process.

Configuring the Map Execution Environment
Because file locking applies to all files to which were written during map execution, configure your map
settings or use the appropriate execution commands to support it.

Examples include:

• A map's output files can be managed using the Retry setting or execution command (the Rc: i option within the -Ofx command).
  
• The work files, audit log, and trace files can be managed through the MapAudit, MapTrace and WorkSpace settings or using the execution command (-Yc: i).
  
• Another option for work files and audit log files is to specify the use of unique file names. Set the MapAudit and WorkSpace > FilePrefix settings to Unique or specify this option using the corresponding execution command ( WU and -AU).
  
  Note: Because trace files do not have an option for using unique file names, they can be managed only through the use of the map retry for non-data files execution command (-Y).

For information about specifying these settings and execution commands, see the Map Designer and the Execution Commands documentation.

Setting Shared Libraries Environment Variables
After you have installed mapping components on UNIX platforms, set the appropriate shared object path
environment variable to access the shared libraries. This procedure varies slightly depending on the platform being used.

For example, to set this variable for an IBM RS/6000 AIX platform, enter the following:

LIBPATH=$LIBPATH: install_dir/libs
export LIBPATH

Note: The RS/6000 AIX platform caches shared libraries. This means if you update a shared library on the disk, you will not be able to see the update. Use the slibclean command at user root to remove the old shared library from system memory.

To set this variable for an HP-UX platform, enter the following:

SHLIB_PATH=$SHLIBPATH: install_dir/libs
export SHLIB_PATH

To set this variable for Solaris platform, enter the following:

LD_LIBRARY_PATH=$LD_LIBRARY_PATH: install_dir/libs
export LD_LIBRARY_PATH

Note: These examples show install_dir/libs as the directory where the shared libraries are located.


=====================================================================
6. SOFTWARE DEVELOPMENT KIT NOTES
=====================================================================

These notes are for the Software Development Kit component of the following products:
- IBM WebSphere Transformation Extender
- IBM WebSphere Transformation Extender SDK

This section contains the following topics:
- Installation Prerequisites
- Online Library Installation
- Environment Variable
- IBM WebSphere Transformation Extender Integration For Java
Product Requirements
- IBM WebSphere Transformation Extender Integration for Java
Servlet Integrator
- EJB API based on Platform API
- EJB API based on IBM WebSphere Transformation Extender
Programming Interface
- IBM WebSphere Transformation Extender Programming Interface
Product Requirements
- C API
- COM API
- CORBA API
- Running Multiple Versions On The Same Computer


Installation Prerequisites

Online Library Installation
Software Development Kit documentation links to the Online Library and the Resource Adapters Library are dependent on the installation of the Online Library.

Environment Variable

• If you are installing the IBM WebSphere Transformation Extender or IBM WebSphere Transformation Extender Software Development Kit (SDK) with the intention of running the EJB API based on Platform API on your application server, the DTX_DO_NOT_CHDIR environment variable must be set to TRUE. When this variable is set to TRUE, the Platform API will not change to the directory where the compiled map is located. Anomalies in performance might be experienced.

The minimum system requirements, operating system requirements, exception, and installation details for the Windows-based and UNIX-based Software Development Kit are detailed in the following topics.


IBM WebSphere Transformation Extender
Integration For Java Product Requirements
To create map and type tree components for the IBM WebSphere Transformation Extender Integration for Java 8.1.x product, IBM WebSphere Transformation Extender Design Studio 8.1.x is also required.


IBM WebSphere Transformation Extender
Integration for Java Servlet Integrator

The following components must be installed to successfully run the Servlet Integrator:

• Web server and Servlet engine or an application server that has a Servlet engine available must be installed on the same machine as the Servlet Integrator.
  
• The servlet.jar file for Java SDK 2.1 must be installed. This file may be downloaded from the following Web site:
  
  http://java.sun.com/products/
  
• For the UNIX version of the Servlet Integrator, ensure that the following variables in the install_dir/WI/webmapwizard.sh file are set correctly:
  
  JAVA: Java 2 SDK installation directory
  JAVAHOME: JVM installation directory
  WIHOME: IBM WebSphere Transformation Extender installation directory

Note: Servlet Integrator users must download the J2EE 1.4.2 compliant API packages and place the j2ee.jar file in the environment variable CLASSPATH before running the Web Integrator Servlet wizard.


EJB API based on Platform API

The following components must be installed to successfully run the EJB API:

• EJB 1.0, EJB 1.1, or J2EE compliant application server must be installed on the same machine as the EJB API.

EJB API based on
IBM WebSphere Transformation Extender Programming Interface

The following components must be installed to successfully run the
EJB API:

• EJB 1.0, EJB 1.1 or 2.0, or J2EE compliant application server must be installed on the same machine as dtxpi.jar.

IBM WebSphere Transformation Extender
Programming Interface Product Requirements

The IBM WebSphere Transformation Extender Programming Interface consists of:
- C, C#, COM, CORBA, Java, and RMI APIs.
- EJB examples

The required header files, library files, and IDLs for these APIs are located in the following directories:

- Windows
Headers - install_dir
Library - install_dir
IDLs - install_dir\idl

- UNIX
Headers - $install_dir/src
Library - $install_dir/libs
IDLs - $install_dir/idl


C API

The following compilers are supported for use with the C API:

Windows 2000/XP
Microsoft Visual Studio .NET

Sun Solaris 9/10
Workshop 6.0

AIX 5.2/5.3
IBM C/C++ 3.6.6.7

HP-UX 11/11.1
HP ANSI C++ A.03.30

IBM z/OS USS
z/OS v1.2 C/C++ Compiler


COM API

The following compilers are supported for use with the COM API:

Windows 2000/XP
Microsoft Visual Studio .NET


CORBA API
The following compilers are supported for use with the CORBA API:

Windows 2000/XP/2003
Java - JDK 1.4.2_03
C++ - Microsoft Visual Studio 6
Microsoft Visual Studio .NET

Borland Enterprise Server (Visibroker Edition) 5.2 was tested with the CORBA API for release 8.1.x.


=====================================================================
7. LAUNCHER STUDIO NOTES
=====================================================================

These notes are for the Launcher Administration, Management Console, and Resource Registry components of the IBM WebSphere Transformation Extender Launcher Studio product.


Non-Windows environments

This section contains the following topics:
- Configuration requirements
- Display Errors

Configuration requirements
For non-Windows environments, to use these products, the X Windows server, whose IP address or domain name that is specified in the export DISPLAY setting, needs to be running on the local host machine or system. You need to communicate to the remote system (X Windows client) where (display_name) on the local host to display the X Windows WTX GUI client application before you run the WTX GUI client application.

You will need to set the DISPLAY environment variable and export it to communicate to the X Windows WTX GUI client which X Windows server will do the displaying for it using the following syntax:

The syntax might vary depending on the shell version that you are using.

Syntax:

export DISPLAY=<display_name>:<server_display[.screen_number]>

Values:

• The DISPLAY environment variable name must be in uppercase letters.
  
• The display_name is the IP address or domain name of the local host machine that will be displaying the X Windows WTX GUI client application.
  
• The server_display refers to the number assigned to the X server that will do the displaying on the host machine.
  
  Most of the time, you will specify the server_display as :0, and not specify the screen_number because most local host machines have a maximum of one display monitor, keyboard, and mouse.
  
  If your system has more than one monitor (display screen), each of which is identified by a unique screen number, as in multi-headed systems, you will specify the screen_number by appending it to the end of the X server_display specification, for example, :0.1. This communicates to the remote server which screen the WTX application should access. The default screen_number is 0, which refers to the primary screen, and when it is 0, you do not need to specify it; for example, you can specify only the server_display simply as :0.

Example 1:

export DISPLAY=mycomputer.ibm.com:0

Values:

• mycomputer.ibm.com is the domain name of the local host that will be displaying the X Windows WTX GUI client application.
  
• 0 is the value for the server_display that is assigned to the DISPLAY environment variable.

Result:

• The host system exports the value to the X Windows client so that it will display the X Windows WTX GUI client application on the primary screen of the computer with the mycomputer.ibm.com domain name through the X server assigned as 0.

Example 2:

export DISPLAY=192.168.1.110:0

Values:

• 192.168.1.110 is the IP address of the local host that will be displaying the X Windows WTX GUI client application.
  
• 0 is the value for the server_display that is assigned to the DISPLAY environment variable.

Result:

• The host system exports the value to the X Windows client so that it will display the X Windows WTX GUI client application on the primary screen of the computer with the 192.168.1.110 IP address through the X server assigned as 0.

Display Errors
To avoid seeing display errors related to font.properties when starting the Launcher Administration, Management Console, or Resource Registry, ensure that the display X server has access to all fonts used in the font.properties of the Java installation.

On Solaris JVMs, the font.properties consistently refer to fonts not included with Exceed. This can sometimes cause havoc when displaying GUIs (for example, distortions and so on). To resolve this, a customized font.properties can be placed in your $HOME/lib directory. This will remove references to the offending fonts.


=====================================================================
8. Resolved Authorized Program Analysis Reports (APARs)
=====================================================================

The resolved APARs are described in the following sections:

- Map Designer
- Type Designer
- Core Engine
- Launcher
- Integration Flow Designer
- Database Interface Designer
- Adapters
- Command Server
- Utilities
- Installation
- Importers
- XML Parsers
- Miscellaneous



Map Designer


[PK54258] Memory corruption occurs during functional map creation using the Functional map wizard in the Map Designer. Memory initialization of one of the variables in the internal memory structures did not complete successfully, causing the Map Designer to crash. The memory was properly initialized to avoid memory corruption.


[PK54281] The Map Designer crashes when building maps. All references to IsLeadByte were removed in the parser and code was added to the Platform and SJIS converters to remove Ideographic Spaces.


[PK54283] Parts of the data audit fields are not in Japanese characters. When a map is opened with the Map Designer for version 8.1, the data audit settings appear to have English characters rather than Japanese as seen in version 6.7. Adjusting the Audit for the "new" type name caused it to be found again
for an old type name with the same value. The original Audits are now copied and when asked to adjust them we make sure that they existed as original Audits and only move them if they were original. This avoids moving an Audit several times.


[PK54286] Bad Japanese characters appear in the .mdq query name and cause the map build to fail. Removed the fix level work for the Database Info since it is always presumed to be Platform but was being converted to/from UTF8. Extra calls into the udbutil code were added to return the BuildQuery/Table as Platform and not UTF8. The UTF8 assigns were removed in the adapternodes.cpp for DB Information and replaced with Platform assigns (WINDOWS)


[PK54324] Printing card details from the Map Designer results in garbage characters where arrows expand the type tree subtypes. Printing bitmaps in the Map Designer and Type Designer produces black square boxes beside the types on the hard copy. Drawn bitmaps that represent Identifier, Sized, Restart Attributes in the Group and Category displays as black boxes in the Type Designer. Printing bitmaps for expansion and contraction arrows for items that have children results in black boxes both in Type Designer and Map Designer. Printing a bitmap for 'Value NOT In Range' results in a black box in the Type Designer. (WINDOWS)


[PK54309] Exported map file fails validaton against mapimportexport.mtt. Invalid adapter types will be defaulted to 'File' during convert or copy card operations in the Map Designer. The invalid adapter types on the input side are: SINK, JAVA CLASS and CORBA. Similarly, the invalid adapter on the target side is: ECHO (or BUFFER). During conversion or copy card operations the adapter type will now be checked and set to 'File' if the Map Designer finds any of these adapter types. Modifications have been made in the MapsDB component such that the given map file is automatically transformed into the invalid adapter types stored in the file. There are several functional maps within this map source file where they have the Source adapter as SINK, which is invalid, and when validated with mapimportexport.mtt using the exported map file, validation fails. Map Designer and MapsDB will now take care of this issue with older maps and user actions in the designer. The changes cover the following scenarios:

- Convert an input card to Output.
- Convert an output card to Input.
- Copy an input card as Output.
- Copy an output card as Input.
- Copy an input card as Input.
- Copy an output card as Output.
- Fix level, 15, has been modified for older maps.

Now, if the user exports the given map source file and validates against the X12_Name map, the map should complete successfully.


[PK54328] Typetree file cannot be opened if it includes the DBCS directory name. The DBCS characters in the type tree file path were not converted properly when opening the 6.7 map source file in the 8.1 version. Conversion logic has not been used in this case which resulted in a truncated type tree file path and subsequently failed to open and load the type tree file specified in the card setting. Now that the conversion of the characters from Platform to UTF8 is invoked, the DBCS characters are retained as they were defined in the card settings of the map. The type tree file is retained properly and the type tree opens and loads without problem in the Map Designer.


[PK54330] Japanese characters in an MDQ file name don't allow the MDQ DB to be recognized which results in not being able to save the card. As noted, the filename sent across to the DBUTIL (backend component) for the MDQ file read/save and other operations done on the MDQ file should be Platform-specific. The UTF-8 equivalent of the MDQ filename/file path was sent instead of a Platform equivalent to the DBUTIL. The result is that the DBUTIL is unable to open the MDQ files having Japanese characters. Subsequently, the Map Designer was unable to display the list of Databases and Queries in the MDQ file. Now, in those places where we interact with DBUTIL, the Map Designer sends the file name in the Platform equivalent of the Unicode MDQ file name instead of UTF-8 equivalent and displays the Databases and Queries in the MDQ file. (WINDOWS XP)


[PK54334] Corrected corrupted messages appearing in Debugger dialogs. (WINDOWS XP) -internal


[PK54335] Map Designer's Organizer does not display Japanese characters in the Audit Log and Trace tabs. The Engine generates the Audit and trace files in Platform format. The GUI assumes that the content is UTF8. With English characters, it does not matter and does not make any difference with respect to Platform and UTF8. It does make a difference with DBCS characters with respect to Platform and UTF8 since both Platform formats (SJIS in this case) may not have the same code point as in UTF8. Both character sets differ and represent the underlying bytes as junk. Treating the content as Platform shows the log and trace file properly. (WINDOWS XP)


[PK54338] Map Designer fails to import an exported Map Source file - error is "Failed to import the XML file". As noted, the Map Designer and MIMPORT command line utility were using the CP_UTF8 codepage instead of CP_ACP for the WideCharToMultiByte function which results in converting the directory/file path or filename to UTF8 instead of platform specific. When the Import component looks for the file in UTF8, it fails to locate it and does not import the map source from the exported file. The directory should be created after setting the Regional options and Advanced options to Japanese. (WINDOWS XP)


[PK54340] Corrupted Type Tree export while running map. Merging types to a newer type tree results in corruption leading to corrupted exported type tree files. Subsequently, the fmap cannot be read due to corrupted type trees attached in the request message. (WINDOWS XP)


[PK54342] Build error message appears corrupted in the Map Designer. The content of the Build Errors view will be shown in UTF8 format as it used to be. Map Audit and Trace views will show the content in Platform format. The Map Designer's Organizer will now show the content depending upon the format of the content stored in the corresponding files being viewed/shown. (WINDOWS XP)


[PK54343] The Map Designer cannot extract DB name or Query name from an MDQ file if the names contain Japanese characters. Now, Database Names and Query Names having Japanese characters will be displayed properly instead of junk to the user in the Map Designer when the referenced MDQ file contains such names. (WINDOWS XP)


[PK50868] Change of input card name impacts a string of the same name in the map rule. Renaming cards would not affect string literals the same way as that of card names being renamed. Only card names that are not part of string literals should be replaced with the new card name. The renaming of card names in the Edit Card settings dialog does not affect string literals.(WINDOWS XP)


[PK54344] When a v6.7 map source file is opened, Japanese path names for audit and trace files appear corrupted and files are created in the wrong location. Map Audit, Trace, and Work File Directory paths will be migrated properly from older International .mms files in the newer 8.1 version. These paths should not be converted to UTF8 and expected to be in Platform in the GUI and other parts of the product. Paths were created as expected during runtime. (WINDOWS XP)


[PK54345] Rule fails in 8.1.0.2 when it contains double byte "=" or X "81 81" value. The parser now transliterates all characters and accepts any ideographiccharacters, not just alpha, numeric, space and punctation marks.


[PK51701] The Command Server dialog on Japanese Windows 2000 does not display Japanese characters properly when running a map. This behavior was caused by using an improper font in the dialog. All other back-end dialogs display the same problem. TTMaker, OTTMaker, Build Map dialog, Launcher Monitor's Snapshot Settings dialog and the Watch Settings dialog also have been rectified. (WINDOWS 2000)


[PK54347] "One or more inputs invalid" error in WPS 6.1 but not in WTX 8.1.0.3. This was fixed by disabling the validation for the xml tree (using document verification).


[PK54348] Mistranslation of Japanese resource files for the Design Studio applications occurring. All of the components in the core product suite have been covered for revision. This includes all the Design Tools, Backend for Design Tools, Utilities, Management Tools, SNMP Agent, Adapters, Launcher, Command Server, Importers and Installs. Enterprise PACKS importers/adapters (SAP R/3 Importers - BDC, IDOC and PeopleSoft Importers - PeopleSoft, PS8CI and SIEBEL Importer) are not covered as part of this effort. And, Trading Manager and FS Manager are also not covered. (WINDOWS XP)


[PK54349] Map Designer will crash during build if there are no permissions to the .MDG file. Added code to disable debug mode if the mdg file is unable to be created.


[PK54353] Bad Japanese characters in .mdq query name cause map build to fail. Removed the fix level work for the Database Info, since it is always presumed to be Platform but was being converted to/from UTF8.


[PK53020] "Error M1021 - Disk full" error returned when compiling a map for Sun Solaris. The Map Compiler also fails to build maps for Unix and MVS platforms. The maps compile fine but when saving the compiled maps for Unix and MVS platforms, file write errors occur and subsequently abend with an M1021 error.



Type Designer


[PK54351] The 'More Find Replace' dialog does not clear the buffer for replacing restrictions.


[PK54355] Component rules are missing data when upgrading to 8.1 using the Japanese character set. This was caused by a null-led UTF-16 character (0x00 0x30 - Ideographic Space). The entire UTF-16 character is now checked and the rule is created as expected.


[PK54356] The Type Designer abends after changing and saving the component rule. The code in AddComponentEx was changed so that when a map rule fails to validate, the rule being copied is the correct size, and adjusts for the conversion to/from UTF-16.


[PK54357] Corrupt Logic Error message returned by the Type Designer after applying a patch. This was caused by the misconversion of UTF8 typenames to UTF-16.


[PK54358] The customer upgrades a type tree from Mercator v6.5.2 to WTX v8.1. He sets DBCS characters as delimiter, initiator, and terminator in group and item attributes. When the type tree is opened in WTX v8.1, these values are not inherited from v6.5.2. The check for upgrading Delimiters was modified to check if they are DT Strings (and therefore should not be converted) by calling the DTStringToExt and then ExtToDTString functions.


[PK54359] "Export failed" error message returned when exporting a type tree. Type tree export internally uses the FromScript.mmc. The Type Designer's backend component, typesdb, exports the type tree in an internal mts script (mts~ file) which then is passed to the FromScript.mmc to generate the .mts file (external XML format). The command file generated to execute the map with Input and Output files with Japanese characters is incorrect. Japanese characters in the type tree file path are converted to UTF8 instead of Platform and placed in the command file. The Runtime expects a Platform string. Encountering a UTF8 string for the path makes the runtime unable to find the path for the internal script and subsequently fails the export. Platform conversions have been used instead of UTF8 for the export to work correctly if the path contains Japanese characters. (WINDOWS)


[PK54360] Exception in Type Designer after propagating Syntax item data language. (WINDOWS XP)


[PK54364] TT Maker cannot import type trees in either 6.7 or 8.1 format. The Type Tree Maker code was modified to use UTF8 conversion instead of Platform when working with component rules. Component rules are in UTF8 format and when converting to Unicode, dstxICU_convertUtf8 has to be used instead of dstxICU_convertPlatformToUnicode. This is modified for Sequence, Choice and Unordered Groups. (WINDOWS XP)


[PK54365] Type Designer includes a debug library. When migrating older type trees to a newer version, negative values were sent to the C Runtime function, isalnum, and this resulted in an unexpected crash during open time. Checking the validity of the character being passed to the function resolves the issue. This occurs only in the Japanese environment. (WINDOWS XP)


[PK54366] Japanese import/export of type tree gives invalid output. The Type Tree Import fails when Japanese characters are present in the Component Rules. Parsing Component Rules during the import process fails due to using the improper conversion function. (WINDOWS XP)


[PK54368] Adjusted the length of the output rule in SetTypePtrs to allow for rules that are bigger in UTF8 than they were in UTF16.


[PK54369] Selecting 'Print Preview' for a type tree is causing the Type Designer to GPF. (WINDOWS)


[PK51989] Type Designer's Date Time type: if creating a custom format with brackets, when reverting to default HH24MMSS the brackets remain. Reverting to the Default Time format from the Custom Time format resets the Optional flags that were set for Time elements (Hours, Minutes, Seconds, Fractional Seconds, Meridian and Zone) with Custom Time format. (WINDOWS)


[PK54371] When the type tree is opened by the 8.1.0.3 Type Designer, initiator and terminator are missing in <root><item1>. When the type trees are open in WTX 8.1, the DBCS values are not inherited from v6.5.2 if the followings are set(group1, item2):

National language - Japanese
Data language - SJIS(not recommended)

If DBCS characters are set with the below values, they are inherited.
(group2, item2)

National language - Western
Data language - Native

The delimiter for group1 seems to be missing when opened in 8.1.0.1 and 8.1.0.3 latest build. Initiators and terminators appear as expected in the type tree for all the types in the given tree. Caused by a mis-determination of DTStrings. Added code to make the determination more exact. The delimiter being removed was due to the code determining that the literal was in fact a DateTime string, which does not get converted. Code was added to make the search for DTStrings more exact. Now, all the types in the Type DB are searched for DateTimes and to ensure the "converting" delimiter is not an allocated DTString. (WINDOWS XP)


[PK54372] Upgrading type tree from 6.7 to 8.1.0.1 adds char to Pad char length.


[PK54373] The Type designer crashes when adding multiple types to a type tree in a Japanese setting. The Type Designer creates multiple Date Time types with custom time format due to memory corruption while adding types to the type tree.


[PK54374] Error when importing a WSDL file through the Type Designer.


[PK54235] Type Designer: errors importing WSDL file. (WINDOWS XP)




Core Engine


[PK54543] After removing error in data audit settings (see WTX00000568), type reference for input card is lost due to name change. This was fixed by the correction to the Audit.


[PK54378] The map returns the message "Not enough Memory to execute map" and there are Launcher issues when executing a map on Windows and Sun Solaris. Offsets are now used to copy the original data back to the results buffer, avoiding having to resize the buffer and also avoiding a heap corruption.


[PK54380] Use of the JALE adapter causes the Launcher to fail when running a map that is using classic XML validation. The fix is to set wAdjust to 0–v_tests.c (WIN2003.)


[PK54382] Example JCL is incorrect on zOS and causes the example to fail. REGION=4M was added to the EXEC statement. (OS390, z/OS 1.4)


[PK54384] CEE dump when executing XML to EDI map. The "UTF-8" to XMLRecognizer::UTF_8 was changed. (OS390, z/OS 1.4)


[PK50986] High EXCP counts against the STEPLIB occur when using certain date/time mapping functions. (OS390)


[PK54555] On DBLOOKUP statement, if Japanese characters are used in the query, the client receives the ORA-00936 error message indicating missing expression. Added code to the tree save such that we check the code page of the O/S and if it is 932 then we save it as an International map and therefore the Native code page is SJIS (and this corrects the issue).

After applying, the customer will need to do the following:

1. Reanalyze and save their type trees.
   This will cause the type tree to have an international character set, versus a Latin-1 native character set.
2. Re-build the map.
   This will then convert the DBLookup contents into the appropriate SJIS data sequence.

[PK53845] Mid function not working correctly. The ICU Chopper function was modified for UTF-8 to leave the offset at 0 and move the pointer. (SOLARIS 2.8)


[PK53847] ToNumber function is not returning the correct output. ToNumber now converts to UNICODE and indicates to the ValidateNumber it is UNICODE. (SOLARIS 2.8)


[PK50920] External function calls do not work on WTX on z/OS. (OS390, z/OS 1.4)


[PK54388] Map Designer: Japanese text string causes map abend when using WORD with negative third argument to enable right to left separator search. The WORD function now works fine with Japanese characters using the SJIS (Deprecated) character set. It does not crash or hang when a negative argument is passed for the third parameter of the function during runtime. (WINXP)


[PK51987] NPUT data is defined as ZONED data and is producing erroneous characters on output. Modified code to tighten the checked-for Zoned digits in MakeNumberMP. (AIX)


[PK54389] Map succeeds under WTX 6.7 but fails using WTX 8.1.0.1(178). Differences exist in processing an input file under TX 6.7 and WTX 8.1.0.1. Numeric Literal Series are now parsed correctly in buildmap. (WINDOWS)


[PK54390] Audit log Work area not reflecting all the map cards. A problem with the Map Audit Log was fixed to allow the WorkArea to generate information for Output cards properly when the map is run. Now the map audit log contains all the output cards' workarea information. (WINDOWS)


[PK54391] Map not validating DateTime Zone in input. Changed ICUGetTimeZone1 to obtain the correct time zone value. (SOLARIS 2.8)


[PK54392] Map not validating DateTime Zone in input. Fixed ICUGetTimeZone1 to validate DateTimes properly and changed makeitem.c to produce the correct output for this type of timezone. (WINXP)


[PK50055] File adapter does not retry when file is in read only mode then switched to Write mode during execution. The output file retry option was modified. If the retry is set and the output file is not available immediately (as an example, file mode is read only) and the file becomes available while retry is active, map should not fail to write that file. (WINDOWS XP)


[PK52514] Audit log "contentreturn" value in ExecutionLog section is different between V6.7 and V8.1.x where V8.1.x does not display the correctreturn value on error. Now, if there are more than one input cards that are failing validation, audit.log will report only the error from the first card in the contentreturn value of the execution log. Audit log file now reports card errors for all input cards. (WINDOWS, WIN2K)


[PK53048] Map abends when Zenkaku characters are used in the SUBSTITUTE rule. ICUConvertCharSetLD now returns NULL ptr if any conversions fail.



Launcher


[PK54422] After the client has used Virtual IP Addressing (VIPA) for the Event Server on USS, the base task does not communicate with the spawned Unix process (MERAAS1) and they are not able to terminate the Launcher using a stop command. A new keyword, VIPA_HOSTNAME, has been added to the ENVAR file. The VIPA_HOSTNAME value is used instead of the value returned by gethostname().


[PK54425] Change HPUX makefiles to build both shared (standard) and exec magic launcher and command server binaries. Change hpux11.mak to build launcher_EM as an exec magic version. The launcher is available for L3, it is in BUILD_DIR/launcher/launcher_EM and can be shipped if needed.(HPUX 11.X)


[PK54429] Socket errors in the compoundsystem log file. Fixed a problem where the WTX launcher log file will be overloaded with the socket related error message when there is a problem on the communication layer between monitoring tools (e.g. Management Console or Launcher Monitor) and the launcher process on the server machine. (AIX)


[PK54431] 0C4 abends with Event Server 8.0.1 on z/OS. Changes were made to dboracle.c (in dbora8)


[PK51227] Changes to a time trigger in the IFD Launcher Settings are not being displayed in the Compound System txt file. The Launcher compound .txt log file was not reporting all omitted hours for the time trigger. If multiple hours are omitted, only the last omitted hour is reported. The problem does not affect execution and time event is not affected. (WINDOWS)


[PK54434] Launcher system with two triggers for one map will trigger immediately even though time trigger is set for Begin After 2 minutes. There is problem during startup if ALLORNONE AND ONLY_ONCE is set for a time trigger that does not use interval. (WINXP)


[PK54435] Time Trigger map does not trigger at the specific time. There is a problem with the time events only when the Launcher starts. If the hour is omitted, we would set the next run time to the whole hour instead of to the beginning of next hour.
(WINXP)


[PK54442] System that has two triggers (time and source event) for one map is leaking memory. Added code to check for an already triggered file and ignore it if it's still in a pending state. (WINNT)



Integration Flow Designer


[PK54444] The Integration Flow Designer will not build maps. Changes were made to the IFD to support relative paths for .MMS and .MMC files in the System. When .MMS file paths are specified in terms of relative paths, the IFD does not build maps, open the Map Designer, update the system diagram in the system view, input and output cards are not displayed in the Navigator, and deploy fails during the deployment to the directory specified in the server location. All these issues have been addressed and the IFD works normally. Changes were made to support relative paths and full paths simultaneously. The IFD determines the full path of the relative path based on the .MSD file path.


[PK54443] Japanese characters in card name are corrupt. CardNames with Japanese characters now appear correctly in the system view in the IFD. Card names are generally stored in Platform format (SJIS in this case) as are filenames and backup filenames in the card structure of a compiled map. These fields in the card structure should be translated to UTF-8 which are then converted to UTF-16 for GUI purposes. This conversion shows the fields in correct format in the system view in the IFD, the tool tips shown in the System view for the input or output cards, and the audit log file paths in the system view.


[PK54447] "ASCII" is not deployed correctly in the IFD. An issue with the SDEPLOY command line utility has been resolved. The IFD GUI works fine with respect to transferring additional files to the server in the specified transfer mode. SDEPLOY command line utility was not using the transfer mode specified by the user in the deploy script for the system's additional files to be transferred along with maps/system file. This issue has been resolved by checking the Mode of transfer in the deploy script before transferring the additional files. Additional files will be transferred based on the mode specified instead of defaulting to Binary mode always. The ASCII mode of transfer is supported since the 7.5 release. This issue is resolved and SDEPLOY command line utility now transfers based on the mode and not defaulting to Binary always. (WINXP)


[PK54448] Additional file transfer mode:"ASCII" msdexport (GUI or CMD) does not reflect the settings. Now, IFD export and import works fine with respect to Mode of transfer for additional files specified in the Deploy Script for the system. Mode of transfer has not been considered during export and import process. This has resulted in a difference between the original system and the imported system from exported xml file with respect to mode of transfer. Additional changes included to export and import the mode of transfer as expected. Existing function prototypes were modified to include the mode of transfer during export and import process. Now, both export and import works fine. The user should see Mode="ASCII" when ASCII is specified. By default, Mode is Binary and won't occur in the xml file. Binary mode is the default mode. As mentioned in the notes, ASCII is shown as Ascii. It has to be represented as ASCII (all capital letters). All of the resource files have been modified. The ASCII mode of transfer is supported since the 7.5 release. msdexport and msdimport command line utilities also work fine with these changes in place. (WINXP, WINXP 5.1)


[PK54449] Import fails after applying patch (PK54447, PK54448). The password encode/decode logic in general fails with the password given in this case during import as encode logic generates invalid XML characters in the exported system definition file. A new password logic (DBUTIL's way of encoding and decoding passwords for MDQ file) is being utilised now in the IFD's export and import process. The new encode and decode logic works fine with the given password. The new logic is used for files exported and imported from now onwards. For those exported files, the old logic is used to be compatible with older exported files. The customer has entered the password and then export and import with this fix in place. Export and import should then work fine without a problem. The version is set to 2 in the exported file which used to be 1. New files have been created and added to the SE project. Changes were made to Import/Export logic in the IFD to use this logic for newer exports and imports. Use older decode logic for those exported prior to this change. (WINDOWS|XP)


[PK54450] IFD is not displaying the correct Japanese characters. The MapServerLocation in the IFD displays incorrect characters. Now, the IFD displays the MapServerLocation properly as set by the user even if it contains Japanese characters. IFD was using Unicode to UTF-8 conversion at some places and vice versa. And at some other places, uses Unicode to Platform conversion and vice versa. This inconsistency in the conversions used within the IFD resulted in invalid characters shown to the user. Now, all the places in the IFD use UTF-8 instead. The GUI works fine now with respect to storing and retrieving the MapServerLocation field content. (WINDOWS)


[PK54452] Launcher settings in Japanese characters is corrupted. Path information in the settings (Map, Card, Launcher) will now store and treat/read as Platform specific infomation instead of UTF8 information. This will be consistent with backend modules where all path information is stored in Platform equivalents. Map Designer GUI component treats the Platform strings as UTF8 strings and messes up the paths. Similarly, IFD has the Platform information but Launcher Settings component assumes it as UTF8 information and messes up the paths. Incompatibilities at several places result in invalid path strings being stored and read and shown to user when the actual byte content is in platform equivalent. To resolve the paths issue universally across components, major changes have been done and all UTF8 handling was replaced with Platform handling of path strings to be consistent and work appropriately at various scenarios. The following scenarios in Map Designer and Integration Flow Designer are covered:

- AuditLog view in Organizer with resource alias defined Audit log path.
- Trace view in Organizer with resource alias defined for Trace file path.
- Invoking Database Interface Designer from Map Designer.
- Map Execution options for Workfile paths.
- Map Execution options for Tracefile paths.
- Map Execution options for Audit file paths.
- Map Tree Control that uses Resource Configuration file.
- Map Settings Tree for Launcher Card Information.
- Map Settings Dialog for Compiled map settings card information.
- Resolve resource aliases for Run Results.
- Resolve resource aliases for Reference files.
- Launcher Settings Tree for card information file paths.
- Launcher nodes in the settings tree for Map Server Location and
Launcher file path.
- Launcher card information for launcher settings.
- Backup file path nodes for compiled maps.
- Generate Card Info from Compiled files.
- Generate DB info from the MDQ files.
- Map Server location paths.
- Audit log, Trace file, work file paths in the launcher settings.
- Many changes to card information in the card information conversion logic.
- Card Information for the system.
- Unresolved settings information.
- Event Trigger information.
- SubSystem Information.
(WINDOWS)


[PK54453] Integration Flow Designer Launcher definition file path and filename for backup file will be garbage if it contains DBCS. The path information in the settings (Map, Card, Launcher) will now store and treat/read as Platform specific infomation instead of UTF8 information. This will be in consistent with backend modules where all path information is stored in Platform equivalents. The Map Designer GUI component treats the Platform strings as UTF8 strings and messes up with the paths. Similarly, IFD has the Platform information but the Launcher Settings component assumes it as UTF8 information and messes up the paths. Incompatibilities at several places result in invalid path strings being stored and read and shown to user when the actual byte content is in platform equivalent. To resolve the paths issue universally across components, major changes have been done and all UTF8 handling to Platform handling of path strings has been replaced to be consistent and work appropriately at various scenarios. The following scenarios in Map Designer and Integration Flow Designer are covered:

- AuditLog view in Organizer with resource alias defined Audit log path.
- Trace view in Organizer with resource alias defined for Trace file path.
- Invoking Database Interface Designer from Map Designer.
- Map Execution options for Workfile paths.
- Map Execution options for Tracefile paths.
- Map Execution options for Audit file paths.
- Map Tree Control that uses Resource Configuration file.
- Map Settings Tree for Launcher Card Information.
- Map Settings Dialog for Compiled map settings card information.
- Resolve resource aliases for Run Results.
- Resolve resource aliases for Reference files.
- Launcher Settings Tree for card information file paths.
- Launcher nodes in the settings tree for Map Server Location and
Launcher file path.
- Launcher card information for launcher settings.
- Backup file path nodes for compiled maps.
- Generate Card Info from Compiled files.
- Generate DB info from the MDQ files.
- Map Server location paths.
- Audit log, Trace file, work file paths in the launcher settings.
- Many changes to card information in the card information conversion logic.
- Card Information for the system.
- Unresolved settings information.
- Event Trigger information.
- SubSystem Information.


[PK54454] Japanese characters are displayed as UTF-8 rather than SJIS in audit, trace and file names. Execution of map results in "audit open error". Path information in the settings (Map, Card, Launcher) will now store and treat/read as Platform specific information instead of UTF8 information. This will be in consistent with backend modules where all path information is stored in Platform equivalents. The Map Designer GUI component treats the Platform strings as UTF8 strings and messes up with the paths. Similarly, IFD has the Platform information but Launcher Settings component assumes it as UTF8 information and messes up the paths. Incompatibilities at several places result in invalid path strings being stored and read and shown to user when the actual byte content is in platform equivalent. To resolve the paths issue universally across components, major changes have been done and replaced all UTF8 handling to Platform handling of path strings to be consistent and work appropriately at various scenarios. The following scenarios in Map Designer and Integration Flow Designer are covered:

- AuditLog view in Organizer with resource alias defined Audit log path.
- Trace view in Organizer with resource alias defined for Trace file path.
- Invoking Database Interface Designer from Map Designer.
- Map Execution options for Workfile paths.
- Map Execution options for Tracefile paths.
- Map Execution options for Audit file paths.
- Map Tree Control that uses Resource Configuration file.
- Map Settings Tree for Launcher Card Information.
- Map Settings Dialog for Compiled map settings card information.
- Resolve resource aliases for Run Results.
- Resolve resource aliases for Reference files.
- Launcher Settings Tree for card information file paths.
- Launcher nodes in the settings tree for Map Server Location and Launcher file path.
- Launcher card information for launcher settings.
- Backup file path nodes for compiled maps.
- Generate Card Info from Compiled files.
- Generate DB info from the MDQ files.
- Map Server location paths.
- Audit log, Trace file, work file paths in the launcher settings.
- Many changes to card information in the card information
conversion logic.
- Card Information for the system.
- Unresolved settings information.
- Event Trigger information.
- SubSystem Information.


[PK54455] Trying to change Workspace > Directory > Custom to Workspace > Directory > Map causes the IFD to GPF. Fixed the problem in the mapsettings, meexecoptions. When the workspace directory is changed back to the map we are not converting the strings in the set function properly. Fixed the problem by adding code to properly convert strings. (WINXP)


[PK54456] IFD GPFs when exporting an .msd file. (WINXP)



Database Interface Designer


[PK54457] Cannot open an .mdq with Japanese characters in the name. The udbutil was changed to convert to/from Platform for all conversions and the dstxICU Platform calls were changed to detect the locale.


[PK54527] Database Interface Designer error "Cannot save file" when trying to save *.mdq files with Adapter Type of Oracle and Platform of HP-Itanium. Support for HP-ITANIUM has been added to Database Interface Designer and DBUTIL components. Now, DID can save and open MDQ files with HP-ITANIUM platform for Oracle database adapter. MDQ files will now have HPITANIUM as platform tag's value when the platform HP-ITANIUM is selected for the Oracle Adapter. Oracle Adapter is supported on HP-ITANIUM. For Oracle versions supported on HP-ITANIUM during run-time, see WTX1055 for additional details. (WINXP)


[PK54458] In the Database Interface Designer, if a password begins with lower case "f", an error is returned by OCISessionBegin, errcode=1017 ORA-01017: invalid username/password; logon denied. Lowercase 'f' in the Password field causes connection failure on Japanese OS. The password encode and decode logic translates lower case 'f' to 0x7F (127), which is DEL control character. EncodePassword logic substitutes x7F with &#x7F; when writing it to the MDQ file in order to make it a safe character, as 0x7F is invalid to write as-is. On Japanese OS, XML4C (Xerces code) does not return the &#x7F; as-is and returns the rest of the encoded password which changes the password after save and read operation. This results in connection failure. The rest of the characters won't have this problem. As 0x7F is invalid character, we are storing it
as character reference instead. On English OS, it returns as-is which is then decoded to 0x7F in the DecodePassword logic. Everything works fine on English OS but is problematic with Japanese OS not returning &#x7F; as-is. XML4C/Xerces-C escapes the XML special characters automatically for the user. Password is not escaped again once it is escaped in the EncodePassword logic until now in the DBUTIL code during write/save operation. To work around this problem and make it backward compatible and work on both Japanese and English OS consistently, Password is escaped twice to retain the encoded password while reading the same. Password is escaped by EncodePassword logic and again by XML4C/Xerces. During read operation, XML4C/Xerces escapes once and again in DecodePassword. This ensures that the Password is decoded properly. For example: if the password given is just lowercase 'f' then the password written is as follows:

#I&amp;#x7F;IJ

In the previous versions before this change, it would be as follows:

#I&#x7F;IJ

During save operation, it escaped twice, 0x7F is substituted as &#x7F; which is then escaped again by XM4C/Xerces as &amp;#x7F; as & is XML special character and substituted as &amp;. When reading the
above encoded password, first the XML4C/Xerces escapes &amp; with & and returns &#x7F: which then is given to DecodePassword. Since DecodePassword does the substitution, it would change the &#x7F; to
0x7F when processing and translated subsequently to lowercase 'f'. It is fully backward compatible and all passwords generated before work the same as we haven't changed the way it decodes.


[PK54460] Query names in Japanese can be entered in DB IF Designer, but when the .MDQ file is saved, the file contained gibberish characters where Japenese names are expected. (WINDOWS|XP)


[PK54465] Getting Failure to start Database Interface Designer message when trying to start it through the Integration Flow Designer by right clicking on the card icon. If the query or table name or database name contains Japanese characters, although it launches DID, it fails to locate the same within the MDQ file. These issues are a result of improper command line translation to UTF8 instead of platform specific when launching the DID from IFD. This has been changed to use CreateProcess function instead of using UTF8
translation which automatically takes care of handling Unicode command lines instead of the WinExec function. Using CreateProcess instead of WinExec resolves this issue.


[PK54558] Database Interface Designer GPFs when it reads 6.7 MDQ file. Module corrected. (WIN, WINDOWSXP)


[PK54466] The Designer fails to display ODBC data source name if the name contains Japanese characters. (WIN, WINDOWSXP)



Adapters


[PK54467] ADAPTER JMS Issue while using IX 5.3 WTX 8.1.0.1 with system trigger to read from JMS queue defined in Weblogic 9.2 server. A JMS NULL pointer exception no longer occurs during a session connect. This NULL pointer exception was getting handled by the adapter. However, a fix has been coded so that the exception is no longer generated. (AIX 5.3)


[PK54468] ADAPTER ORACLE 9I problem selecting CLOB from Oracle 9i table. Whenever selecting CLOB data, a large enough buffer is allocated to receive the data. Before this fix, the character length of the CLOB field was used for allocating the byte count. This caused problems for multi-byte characters, since 4 bytes may be needed to handle 1 character. (WINDOWS XP)


[PK49808] Unix ODBC Adapter fails to insert into table using DataDirect ODBC SQL Server Driver; "Incorrect syntax near 'OUTPUT'" error. Any card-based DB operations that execute SQL queries, inserts, and updates now bind input data items with a parameter type of INPUT (versus INPUT_OUTPUT). Otherwise, DataDirect driver on AIX for SQL Server driver will fail with 'OUTPUT' errors, since the SQLBindParamter call would default SQL data bindings to INPUT/OUTPUT mode. (AIX 5.3)



Command Server


[PK54471] -CMD dtxcmdsv -? does not display help from the command line. Code was added to parsearg.c to launch the TX eclipse help system. (WINDOWS)


[PK54472] The sample JCL for the Burst Map example DTX.SDTXSAMP(DTXBMJCL) does not have the steplib DD statement for the XML toolkit. A reference to the XML Toolkit was added to each of dstxpage, dstxprof, and reverseb jcl examples. (OS390 BATCH)


[PK54473] The sample JCL for the DB2 Map example DTX.SDTXSAMP(DTXDMJCL) is missing the DB2 steplib. The dept.jcl, mtsmaker.jcl, and tdfmaker.jcl were changed. (OS390)


[PK54474] Client is receiving a transiderr when running the DEPT map in the IVP program for the CICS Command Server. The transaction name was changed to be linked in dtxctxt.cc2 in /os390/cics/source.


[PK54475] When the directory name for audit or trace file contains Japanese characters, Command Server creates files in the wrong place. Now, Map Audit and Trace files are generated as expected. This issue is related to migration issue WTX1521. Map Audit, trace, work file paths have to be in Platform format instead of UTF8 format. All the components in the product expect the paths to be Platform format. Made changes to MapsDB and Map Compiler to work correctly with Japanese paths in Map Audit, Trace and Work File settings. (WIN, WINDOWS XP)


[PK54478] Most map settings in Japanese appear as gibberish in the Command Server. The Command Server Map Settings Dialog now works fine with Japanese characters in Map Name, MMC File Path, Input card names, Output card names, Map Audit, Trace, Work File Paths and Soure & Target File Paths. Japanese characters are shown properly now. (WIN, WINDOWS XP)


[PK54480] 'D810CICS is not available' error when trying to use Command server in CICS by invoking transaction D810. The RDO definitions example was corrected. (OS390)



Utilities


[PK54481] Request for a sample JCL for DTXPROF WTX 8.1 on z/OS. New examples were added to the V2007 tree under os390\install\examples\ (OS390)


[PK54483] Adding additional validation to typetree causes odd behavior. (WINDOWS XP)


[PK54484] Error while exporting a type tree or importing a schema. (WINDOWS)



Installation


[PK54485] Cannot install any WTX products on Redhat5(RHEL564). Redhat5 does not come with an uncompress utility. This version of Linux only comes with gunzip. WTX install script for RedHat makes a
call to the uncompress command when it attempts to decompress a file, but the command is not included in the core RHEL AS 4.0 package and the call fails and the install script aborts. Manually replacing the "umcompress" in the script file with "gunzip" fixes this issue. The gunzip is available in all RedHat platforms.


[PK54486] Install splash screens display 8.0.2(122). Installation panels now either provide v.r.m.f(b) specification or do not provide version information at all. (WINXP)



Importers


[PK54487] Restriction list values are not being converted properly after import. Modified COBOL Copybook Importer to strip off double quotes from level 88's when they occur both at the beginning and end of the string value. (WINXP)


[PK54490] Text File Importer cannot parse Japanese text. Amended the Text Importer to read file as bytes and read the SJIS properly. (WIN, WINDOWS XP)


[PK54491] Upgrading an *.mdq file causes maps to GPF when they are built. Upgrading the 6.7 version to 8.1 version would not crash the Map Designer or MCOMPILE command line utility when compiling the maps using the MDQ file. Corrupted value in the older MDQ files caused newer version designers to crash while reading the data from the MDQ file. (WINDOWS)


[PK54493] XML REG WTX748 Numeric element sets wrong Data language value. (WINDOWS)


[PK54494] Fix for WTX183 not working in 8.1.0.3 for type tree import. Add the apos and ' restrictions lists where it seemed appropriate.



XML Parsers


[PK54497] XML PARSER - Issue with Field after xml schame import - it is text and not number as expected in WTX 8.1.0.2.


[PK54498] Parser exception when validating data using type tree created using the XML Schema importer on WTX 8.1.


[PK54500] WTX launcher crashing when executing XML -> CSV performance test case. (WIN, WINDOWSXP)


[PK54501] Corrupted XML output when using PACKAGE with unspecified namespace-prefix on the target card WTX 8.0.1.1.


[PK51043] "External Parser returned Error" using type tree systemimportexport.mtt to validate map system Export XML file generated by the Integration Flow Designer. (WINDOWS XP)


[PK54503] XML REG spaces are truncated in the output files (WINDOWS)


[PK54504] xmlrunlog.xsd is incorrect according to xmlspy WTX 8.0.1.1. Fixed xmlrunlog.xsd validation errors. One of the schema elements is not defined properly.



Miscellaneous


[PK54551] MAP DESIGNER- map crashes on TX 8.1 after upgrading from 6.5 when we matched the string we were looking for, we incremented our input pointer by the size of the string we were looking for, and the output pointer by the size of the string we substituted for it, but we didn't change our character length array index. So when we went to look at the next character position to see if the data there matched the string we were looking for, and it didn't match, we incremented our pointers by the size of an earlier character, not the size of the current character. Added code to update the character length array index.


[PK48813] RESOURCE MANAGER - RC 1002 - no data found error on second map burst. Fixed a problem when the top level map is bursting and calling data base adapter in the last burst with the zero sized data. The ‘no data’ condition is causing a map error. The map should finish sucsesfully because ‘no data’ is not an error condition. (SOLARIS 10A)


[PK54506] Resource Registry cannot read MRC/MRN files created by Mercator 6.7. SJIS encoding is not supported by IBM XML parser. (WIN, WINDOWS XP)


[PK50366] Garbage characters exist in last message box when running Map Debugger in Japanese. Debug Run Status Window now receives Platform encoded strings and converts them to UTF-16 for
display. (WINDOWS XP)


[PK54507] MQS adapter file libm4mqs.so missing from WTX 8.1 for Message Broker 6.0 (C12BPML.tar) for Linux install. Corrected component list file for Linux TX for Message Broker install generation.


[PK51236] The connect result in the SelectLauncherserver through Launcher Monitor (Japanese environment) is showing garbage characters in the System Name column. Japanese characters in System Names and System File Names are displayed in UTF8 format instead of Platform (SJIS) format gives an appearance of garbage to the user. Now, Launcher Monitor's Select System Dialog shows Japanese characters properly.


[PK54508] Command line argument for launcher.sh displays systemname as being optional when running launcher.sh on HPUX11ia. Removed optional for system name. (HPUX 11i)


[PK54509] Garbage System name appearing in Launcher Monitor. Now, Japanese characters in watch/map titles will be shown properly in the Snapshot settings dialog of Launcher Monitor. All the Japanese characters are shown correctly. (WIN, WINDOWS XP)


[PK53031] COMMON TX PROGRAMMING INTERFACE FUNCTIONS - Custom function with '4' parameter does not work. External Functions in a component rule are not properly analyzed. This has been fixed in the parser. (WINDOWS XP)


[PK54510] SUN cluster support is missing from Solaris installations. Issue invoking RunCluster.sun build script. Corrected hard coded platform name and corrected script interface to use proper build area and summary log file. Also corrected build component copy to remove cluster source files prior to install staging.



=====================================================================
9. CONTACTING CUSTOMER SUPPORT
=====================================================================

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



=====================================================================
10. 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
The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States or other countries, or both:

i5/OS
IBM
the IBM logo
AIX
AIX 5L
CICS
DB2
DB2 Universal Database
Domino
HelpNow
IMS
Informix
iSeries
Lotus
Lotus Notes
MQIntegrator
MQSeries
MVS
Notes
OS/400
Passport Advantage
pSeries
Redbooks
SupportPac
WebSphere
z/OS

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. 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.

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.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Other company, product, or service names may be trademarks or service marks of others.


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

WebSphere Transformation Extender, Version 8.1.0.3