Release Notes
Abstract
This document provides a complete list of fixes for Transformation Extender, V9.0.0.2. The most recent fix is at the top of the table.
Content
Note: An APAR link does not work if the APAR has not reached the publish phase yet.
Entitled customers can download Transformation Extender, V9.0.0.2 from Fix Central.
| APAR | Description |
| PI80965 | LAUNCHER SEGMENTATION FAULT AFTER APPLYING PATCH FOR APAR PI79981 |
| PI80476 | LAUNCHER CRASHES WHEN PROCESSING DATA USING XSLT FUNCTION IN MAP RULES |
| PI80250 | ITX CICS COMMAND SERVER "FATAL ERROR - OPTION ARRAY LOOKUP FAILED(2)" WHEN RUNNING A MAP CALLED BY AN API PASSING BUFFERS |
| PI80150 | OPTIONS NOT FOUND FOR 0012334C59E8 |
| PI79981 | RESULT OF PARSE() FUNCTION TRUNCATED IN OUTPUT |
| PI79007 | NATIVE XSD OUTPUT IGNORES RESTRICTION PATTERN |
| PI78826 | CORRUPTION IN DATA WHEN USING THE PARSE() FUNCTION |
| PI78604 | ABEND USING ITX 9.0.0.1 ON Z/OS BATCH WHERE TO TOP LEVEL MAP CALLS A SUB MAP WITH A RUN() FUNCTION AND SUB MAP USING SINK |
| PI78461 | CORRUPTION OF DATA USING PARSE FUNCTION WITH CERTAIN PAGE SIZE SETTINGS |
| PI78117 | CRASH/HANG OF THE CORE ENGINE WHEN USING A MAP BASED ON JSON TYPETREES |
| PI78073 | 'IMPLIED DEFAULT VALUE' NOT SET BY THE IBM TX V9 COBOL COPYBOOK IMPORTER |
| PI78035 | COBOL COPYBOOK IMPORTER NOT IMPORTING FIELDS IN THE CORRECT FORMAT WITH PIC-99.99999 |
| PI77857 | 'MAP COULD NOT COMPLETE (38)' ERROR MESSAGE EXECUTING MAP ON SOLARIS |
| PI77828 | INTERMITTENT LAUNCHER CRASHES ON WINDOWS 64 BITS WHEN RUNNING LARGE DATA VOLUMES THROUGH TRADING MANAGER |
| PI77768 | UNABLE TO PROCESS LARGE DATA OF 2 GB AND MORE FROM A TX MAP WHEN CALLED FROM B2BI BP |
| PI77581 | CORRUPTED OUTPUT (ONLY WITH CERTAIN PAGE SIZE SETTINGS) USING PARSE() FUNCTION IN ITX 9.0.0.1 |
| PI77515 | LAUNCHER ADMINISTRATION COMMAND LINE UTILITY EXPORTS 'AUTOMATIC STARTUP' OPTION FOR SYSTEM FILES INCORRECTLY |
| PI77396 | JAVA.LANG.NOCLASSDEFFOUNDERROR USING ITX4IS 9.0.0.0 WITH IBM BUSINESS PROCESS MANAGER ADVANCED 8.5.7 |
| PI77331 | DURING NATIVE WSDL IMPORT XML SCHEMA IS CREATED INCORRECTLY. IT IS MISSING CONTENT |
| PI77320 | ONE BYTE LOST WHEN CONVERTING BETWEEN UTF-8 AND IBM-1390 |
| PI77182 | UPDATE SYSTEMS PROPERTIES USING -EDDIR NOT WORKING AS EXPECTED |
| PI77019 | ABEND S0C4 EXECUTING A TX Z/OS BATCH JOB |
| PI76674 | COBOL COPYBOOK IMPORTER IS CREATING A TYPETREE WITH INCOMPLETE DESCRIPTION FIELD |
| PI76571 | AUTOMATIC STARTUP IS NULL AFTER USING -ADDIR/-EDDIR WITH THE LAUNCHER ADMINISTRATION UTILITY |
| PI76183 | DATA MISSING FROM OUTPUT WHEN USING ISERROR FUNCTION, DEPENDING ON ITS POSITION IN THE INPUT |
| PI75969 | DATA MISSING FROM OUTPUT WHEN USING RESTART/REJECT FUNCTIONALITY IN THE MAP IN CERTAIN SITUATIONS |
| PI75839 | WHEN IMPORTING WSDL WITH CLASSIC IMPORT OPTION IT GENERATES THE TREE WITH ALL OPERATIONS EVEN THOUGH WE ONLY SELECT ONE |
| PI75291 | DESIGN STUDIO UNABLE TO ABLE CONNECT TO STERLING B2B INTEGRATOR WHEN SI MAP TEST HTTP SERVER ADAPTER IS CONFIGURED TO USE SSL |
| PI75030 | MAP CRASHING DUE TO BAD COMPILED MAP BEING RUN |
| PI74500 | CONNECTIVITY ISSUES USING THE SOCKET ADAPTER WITH ITX LAUNCHER 9.0.0.1 ON THE LINUX PLATFORM |
| PI74183 | DTXWMQI*.SH SCRIPT COPIED TO $MQSI_WORKPATH/COMMON/PROFILES DIRECTORY WITH THE ROOT USER ACCOUNT AS THE OWNER |
| PI73921 | X12 DATA CORRUPTION USING WTX 8414(7) ON Z/OS |
| PI73584 | DESCRIPTION FIELD NOT AS COMPLETE USING NEW COBOL COPYBOOK IMPORTER (EVEN AFTER APPLYING APAR PI72484) COMPARED TO OLD |
| PI73438 | MAP GET CRASH WHILE USING JAPANESE/ASCII(DEPRECATED) |
| PI73125 | BIDIRECTIONAL PROPERTIES OF A NUMBER ITEM FROM A WTX / ITX TYPE TREE ARE NOT EXPORTED CORRECTLY |
| PI72677 | 'COULD NOT FIND TYPE TO ASSIGN XML DATA' ERROR WHEN USING WTX ON THE Z/OS PLATFORM |
| PI72484 | NEW COBOL COPYBOOK IMPORTER TYPE TREE FIELD COMMENTS DOES NOT MATCH DEPRECIATED COBOL COPYBOOK IMPORTER |
| PI72197 | TX LAUNCHER CRASH WHEN USING THE SAP R/3 ADAPTER AND THE SAP SYSTEM IS DOWN OR THE CONNECTION INFORMATION IS INCORRECT |
| PI72176 | DESCRIPTION FIELD MISSING VITAL DETAILS USING THE NEW COBOL COPYBOOK IMPORTER |
| PI72175 | WHEN IMPORTED WITH THE NEW COBOL COPY BOOK IMPORTER THE RANGE MIN VALUE SHOWS AS 1 |
| PI72142 | THE DEFAULT SYSTEMS DIRECTORY IS CONTAINED IN THE LAUNCHERLOG EVEN THOUGH IT IS NOT A DEFINED DEPLOYMENT DIRECTORY |
| PI71370 | NON-DEPRECATED COBOL COPYBOOK IMPORTER DOES NOT RUN CORRECTLY IN THE COMMAND LINE OF 'TIMPORT' COMMAND LINE UTILITY |
| PI71361 | FILE FAILS IF THE FIELD USED AS SIZE IS A LEFT ALIGNED NUMBER OR RIGHT JUSTIFIED PADDED WITH SPACES |
| PI71120 | THE SYSTEMS ASSOCIATED WITH A DEPLOYMENT DIRECTORY ARE NOT VISIBLE USING LAUNCHER ADMINISTRATOR |
| PI70962 | THE LINUX INSTALLER CREATES DIRECTORIES WITH DIFFERENT INCONSISTENT PREMISSIONS |
| PI70660 | ALTERNATING REPEATING GROUPS SHOW MISSING DATA WHEN XML IS MAPPED TO OUTPUT |
| PI70558 | A NULL OBJECT IS NOT PARSED AS EXPECTED |
| PI70097 | CORE DUMP WHEN FTP ADAPTER FAILS TO CONNECT ON SOLARIS |
| PI69829 | ASRA ABEND IN CICS COMMAND SERVER WITH XML TRACE ENABLED |
| PI69714 | ITX 9.0.0.1 ADDS TO THE 'DEPLOYMENTDIRECTORIES' IN THE LAUNCHERADMIN.BIN |
| PI69706 | DTXWMQI.LIL CALLS _SETUPJNI WHICH CALLS MB CLASS LOADER THAT SCANS DEPLOYED OBJECTS BEFORE THEY HAVE BEEN INITIALIZED |
| PI69688 | ORACLE TRIGGERING ISSUE ('ONE OR MORE INPUTS WAS INVALID') WHEN THE LAUNCHER IS UNDER HEAVY LOAD (MULTITHREADED) |
| PI69181 | DESIGN STUDIO ALWAYS MARKS TREES AS MODIFIED, PROMPTING TO SAVE |
| PI69176 | LAUNCHER CRASH WHEN CREATING A BACKUP FILE FOR AN OUTPUT CARD IF THE MAP ENDS WITH WARNING CODE 21 |
| PI68774 | ORA-01756: WHEN USING SPACE IN ARGUMENT WITH -VAR OPTION |
| PI68549 | COMPLIANCE CHECK CRASHING WHEN AUDIT_COMMAND IS ENABLED IN THE PARAMETER.DAT FILE |
| PI68548 | RETURN CODE 16 DISK WRITE ERROR IN X12INITIALCONTROLSUMMARY.MMC WHEN STREAMMAXMEMLIMIT IS SET TO A LOW VALUE |
| PI68229 | NUMBER ITEM FROM INPUT XML CORRUPTED WITH CONTENT FROM OTHER LOCATIONS |
| PI68148 | INPUT DATA MISSING FROM TYPE TREE STRUCTURE IN WTX 8.4.0.X AND ABOVE |
| PI68013 | PATTERN MINIMUM DECIMAL DIGITS BEING IGNORED WHEN WTX CREATES A DECIMAL OUTPUT IN XML DATA USING THE XSD NATIVELY IN THE CARD |
| PI67670 | MAP COMPILE ERROR USING ITX 9.0 FOR MAP THAT COMPILES OK USING WTX 8.4 |
| PI67667 | XML DATA CORRUPTED USING THE PARSE() FUNCTION |
[{"Product":{"code":"SSVSD8","label":"IBM Transformation Extender"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"9.0.0.2","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Was this topic helpful?
Document Information
Modified date:
06 October 2022
UID
swg27049027