Release Notes
Abstract
WebSphere® Transformation Extender V8.2.0.6 includes fixes for the Authorized Program Analysis Reports (APARs) that have been reported. The following is a complete listing of fixes for V8.2.0.6 with the most recent fix at the top.
Content
NOTE: Some APAR URLs may not work due to the APAR not having reached the publish phase.
APAR | Description |
PM49980 | A MAP FAILS TO VALIDATE INPUT DATA WHEN A DATA ITEM APPROACHES THE MAPS PAGE SIZE. |
PM54284 | NEGATIVE ONE BYTE SIGNED BINARY INTEGER IS MAPPED INCORRECTLY TO AN UNSIGNED CHARACTER INTEGER ON UNIX OR ZLINUX PLATFORM |
PM55701 | WTX DESIGN STUDIO CRASHED WHEN CLICK "SHOW RULE PROPERTIES" OF A RULE ON OUTPUT CARD ON NON-ENGLISH LOCALE. |
PM55761 | WTX RUNNING WITH DATAPOWER OUTPUTS INCORRECT XML OUTPUT |
PM54893 | EXPORT OF A TYPETREE WILL FAIL IF ONE OF THE OBJECTS INCLUDED INTHE EXPORT HAS SPECIFIC PROPERTIES SET FOR THE RELEASE CHARACTER |
PM52167 | UNABLE TO RETRIEVE UTF-8 CHARACTERS FROM LDAP SERVER VIA THE JNDI ADAPTER. |
PM55761 | WTX RUNNING WITH DATAPOWER OUTPUTS INCORRECT XML OUTPUT |
PM54616 | EXPERIENCING POOR PERFORMANCE OF RMI SERVER. |
PM54904 | XMLLIB->XPATH FUNCTION FAILS ON UNIX PLATFORMS |
PM54993 | GENERATING TREE FROM ANY QUERY HANGS DATABASE INTERFACE DESIGNERWIN WINDOWS 2008 USING NATIVE SQL DRIVER. |
PM54720 | A TYPE TREE CREATED USING XML CLASSIC IMPORTER FAILS VALIDATION. |
PM54949 | XMLLIB->XPATH() FUNCTION RETURNING INCORRECT RESULTS FROM AN ANYELEM FIELD IN AN XML FRAGMENT WHEN DATA IS UTF-8 |
PM43538 | INPUT VALIDATION ERRORS ON BIG ENDIAN DATA FOR BINARY INTEGERS FAILING WITH MINIMUM SIZE REQUIREMENTS |
PM54874 | DESIGN STUDIO CRASH ON WINDOWS 7 WHEN ACCESSING CUSTOM DATE. |
PM54359 | THE WTX 8.4 LAUNCHER AGENT IS NOT ACCEPTING CONNECTIONS |
PM53802 | DESIGN STUDIO CRASHES WHEN LAUNCHING FUNCTIONAL MAP WIZARD |
PM50139 | XML CLASSIC VALIDATION FAIL DUE TO CHOICE GROUP BEING INCORETLY SET TO BE REQUIRED GROUP AFTER UPGRADE FROM 8.1 TO 8.3 |
PM51855 | MAP DESIGNER CRASHES USING 8.3.0.4 WHEN XML INPUT IS INVALID DUETO THE XSD SCHEMA |
PM51461 | NATIVE SCHEMA TYPE TREE USING UTF-8 AS NATIONAL LANGUAGE INSTEADOF LATIN2 (ISO-8859-2) ON ZOS. |
PM52337 | VALID XML IS PARSED BY WTX AS INVALID WHEN READ USING A TYPETREECREATED BY THE CLASSIC IMPORTER |
PM53154 | MEMORY NOT RELEASED OR REUSED BY CALLING PROCESS WHEN A MAP FAILS WITH ERROR CODE 2 - 'NOT ENOUGH MEMORY TO EXECUTE MAP' |
PM48583 | LEADING SPACE IS TRUNCATED WHEN DOCUMENTVERIFICATION IS SET TO WELLFORMED(XERCES ONLY). |
PM52566 | XML PARSER VALIDATION ISSUE ELEMENT 'XXXXXXXX' IS NOT VALID FOR CONTENT MODEL ERROR MESSAGE |
PM52324 | TYPE TREE WORKED IN 8.0 BUT FAILED IN 8.3 |
PM52011 | LAUNCHER STOPS WITH RETURN CODE 139 AFTER MAP FAILS WITH DATA VALIDATION ISSUE. |
PM49993 | MAP CARD BACKUP DOES NOT WORK WITH APPEND OPTION |
PM51997 | LAUNCHER IGNORES THE OVERRIDE SETTING FOR METADATA(XML) PROPERTYFOR MAPS IN THE SYSTEM, USING INSTEAD THE COMPILED SETTING |
PM50979 | "INVALID USER/PASSWORD" ERROR CODE 1017 WHEN ACCESSING ORACLE AQ |
PM50358 | METADATA(XML) SCHEMA LOCATION IS NOT SAVED IN THE SYSTEM WHEN USING UNIX ABSOLUTE PATH |
PM50908 | MAP THAT DOES NOT CREATED OUTPUT DUE TO LARGE MEMORY REQUIREMENTS DOES NOT REPORT ERROR IN EXECUTION RETURN CODE. |
PM50996 | MESSAGE ROLLED BACK TO QUEUE EVEN THOUGH MAP COMPLETES. |
PM04221 | WMB 7.0 TOOLKIT CRASHES WHEN YOU CLICK ON MAP SETTINGS AFTER CLICKING ON EXTERNAL MAP AND BROWSING FOR A LOCAL COMPILED MAP |
PM49902 | LAUNCHER CRASH ON HPI WHEN USING BACKUP IN HIGH WORK LOAD |
PM48795 | MATHMATICAL CALCULATIONS USING BINARY NUMBER FIELDS AS A SOURCE MAY PROVIDE INCORRECT VALUES ON THE LINUX PLATFORM |
PM49547 | ERROR ENCOUNTERED WHEN BUILDING CUSTOM FUNCTION LIBRARY ON AIX |
PM37701 | INTERMITTENT CORE DUMP OCCURS WHEN DISCONNECTING WTX DB2 DATABASE ADAPTER CONNECTION RUNNING UNDER MESSAGE BROKER |
PM39540 | WHEN USING THE WTX 8.3.0.2 VERSION EMAIL ADAPTER, THE TIMESTAMP IS OFFSET BY 1 HOUR WHEN USING A DAYLIGHT SAVING TIME |
PM42589 | UNABLE TO SUCCESSFULLY CALL THE JAVA CLASS ADAPTER ON THE Z/OS PLATFORM |
PM47663 | ZERO RETURN CODE IS RECEIVED FROM THE USS COMMAND SERVER WHEN THE COMMAND LINE IS INVALID |
PM49344 | TYPE TREE ANALYZER DOES NOT DETECT INVALID CHARACTER SETS |
PM49331 | INPUT INVALID IF PRIMARY DTD FILES REFERENCES AN EXTERNAL DTD USING A RELATIVE PATH |
PM49166 | XML ERROR INVALIDDATATYPEVALUEEXCEPTION EXCEEDS MAX LENGTH FACET |
PM48312 | THE INSERT KEY TOGGLES OVERWRITE MODE. |
PM49391 | INVALID XML STRUCTURES ARE CREATED FOR EMPTY OPTIONAL FIELDS WHEN USING THE CLASSIC XML IMPORTED TYPE TREE |
PM47369 | QUOTEDTEXT FUNCTION DON'T RETURN ANY RESULT |
PM48189 | REFORMAT FUNCTION CREATING AN INCORRECT OUTPUT FOR ZONED DECIMALNUMBERS |
PM48632 | ENCOUNTERING "PAGE USAGE COUNT ERROR' |
PM47223 | A MAP WITH INVALID INPUT DOES NOT END WITH A FAIL OR WARNING CODE UNLESS ANY INPUT OBJECT IS REFERRED TO, IN THE OUTPUT. |
PM48102 | DATA TRUNCATION OF LAST CHARACTER OF DATA FROM THE OUTPUT ON UNIX PLATFORMS |
PM47906 | NUMERICAL DATA MISSING FROM WTX NODE OUTPUT WHEN XMLNSC BASED MESSAGESET IS USED IN THE PRECEDING NODE |
PM47517 | ERROR MESSAGE "INVALID EXECUTABLE MAP: VSORTEC!S! " WHEN CHANGING MAP SOURCE FOR VSORTEC MAP IN IFD. |
PM48103 | UNABLE TO RENAME FUNCTIONAL MAP IF MAP NAME HAS THE MAXIMUM NUMBER OF CHARACTERS (32) ALLOWED. |
PM48008 | XML OUTPUT DIFFERENT WHEN USING WTX 8.1 AND WTX 8.2. |
PM49666 | LAUNCHER AGENT COREDUMPS |
PM45859 | INCORRECT RANGE SET ON GROUP OBJECT IN A TYPE TREE IMPORTED FROMAN XML SCHEMA USING THE 'CLASSIC' OPTION |
PM47715 | RUNNING THE SDEPLOY COMMAND GENERATES .SUN FILES WHEN DEPLOYMENTPLATFORM IS DEFINED TO BE AIX |
PM48006 | EXTERNAL PARSER ERROR WHEN RUNNING MAP USING XML DATA. |
PM47576 | RESOURCE REGISTRY IS RESET WHEN USING WTX MAP NODE AND WTX JAVA API WITHIN THE SAME MESSAGE BROKER EXECUTION GROUP |
PM46869 | XML OUTPUT FILE MISSING DATA AFTER APPLYING PATCH FOR PM42946 |
PM43778 | UPDATE KEYS ARE BEING RE-USED ON MULTIPLE OUTPUT CARDS, DESPITE EACH USING A SEPARATE .MDQ FILE (AND UPDATE KEYS) BUT SHARED CON |
PM44404 | VALID FTP TRANSFERS USING THE WTX FTP ADAPTER ON LINUX 64 BIT PLATFORMS MAY TIMEOUT AFTER THE -TIMEOUT PERIOD |
PM49710 | MEMORY LEAK WHEN USING JALE ADAPTER AND SAP CLIENT IS DOWN |
PM45236 | THE ORACLE AQ LISTENER FAILS TO TRIGGER AFTER THE ORACLE CONNECTION HAS BEEN DROPPED |
PM45638 | EDITING LARGE MAP RULES WITH THE WTX 8.3 DESIGN STUDIO IS VERY SLOW |
PM45282 | MAP OUTPUT FROM XML CHOICE GROUP NOT BEING CREATED FOR ALL INSTANCES |
PM46043 | ERROR " HTTP/1.1 500 INTERNAL SERVER ERROR" RECEIVED WHEN CALLING SOAP ADAPTER. |
PM46197 | JAVA EXCEPTION WHEN IMPORTING A WSDL FILE |
PM46395 | WTX MAP NODE FAILS WITH ERROR "BAILING DUE TO XDS AMBIGUITY" WHEN USING WMB MESSAGE SET WITH AN ELEMENT NAMED "VERSION" |
PM46096 | HIPAA 5010X217 278 (REQUEST) HL NUMBERING IS NOT BEING CHECKED |
PM38928 | ENCOUNTERING TYPE TREE ANALYSIS ERROR WHEN USING "IN COMPONENT' IN A COMPONENT RULE |
PM45221 | WHEN EXPORTING A MAP THE 'CREATE DIRECTORY STRUCTURE FOR FILES' DOES NOT WORK AS EXPECTED |
PM44555 | CLASSIC XML TYPE TREE DOES NOT DETECT EMPTY REQUIRED FIELD THAT HAS A RESTRICTION LIST |
PM45046 | JMS ADAPTER SOURCE EVENT TRIGGERING AGAINST APACHE ACTIVEMQ RESULTS IN 'SOURCE NOT AVAILABLE' ERRORS |
PM43102 | MAP INPUT VALIDATION FAILURE OCCURS WHEN USING TYPE TREE IMPORTED USING THE XML SCHEMA IMPORTER CLASSIC METHOD |
PM42946 | INVALID XML OUTPUT WHEN USING UNORDERED XS:ALL ELEMENTS |
PM44472 | AN EMPTY FILE IS CREATED WHEN USING THE FORMAT RECFM = U ON ZOS. |
PM43718 | RUNTIME CORE DUMP / CRASH OCCURS DUE TO A MAP COMPILER ISSUE |
PM44226 | FILE OVERWRITTEN WHEN EXPORTING MAP IF 'OVERWRITE EXISTING FILESWITHOUT WARNING' IS SELECTED OR NOT SELECTED. |
PM44224 | MAP DESIGNER CRASH OCCURS WHEN USING THE CHOOSE() FUNCTION AND THE GETANDSET() FUNCTION |
PM43589 | "EXIT CALL FAILED" ERROR GENERATED WHEN USING GET DB WITH MDQ ONZ/OS. |
PM39115 | POTENTIAL FOR DATA TO BE MISSED WHEN USING THE UNIQUE() FUNCTIONON UNICODE DATA. |
PM39633 | INPUT VALIDATION LOOPS WHEN USING DEFAULT WORKSPACE VALUES FOR PAGESIZE OF 64K AND PAGECOUNT OF 8 |
PM40960 | WTX V8.3.0.4 MAP OUTPUT MAY BE TRUNCATED INCORRECTLY WHEN MODAL CHARACTER SET DATA CONTAINS "WIDE SPACE" CHARACTERS |
PM41678 | MAP OUTPUT CREATED USING A WSDL IMPORTED TYPE TREE FAILS INPUT VALIDATION WHEN USING THE SAME TYPE TREE |
PM41793 | THE ... SYMBOL FEATURE IS NOT WORKING PROPERLY ON BIG-ENDIAN PLATFORMS |
PM42652 | MAP COMPLETES SUCCESSFULLY EVEN THOUGH AN ERROR IS ENCOUNTERED |
PM42326 | CRASH MAY OCCUR WHEN USING THE ECHO ADAPTER IN RUN() FUNCTION WITH ECHOIN() FUNCTION OR -IE / -OE OVERRIDE PARAMETER |
PM42273 | XML DTD IMPORTER CREATES A XERCES TYPE TREE WHEN THE CLASSIC TYPE TREE OPTION IS SELECTED |
PM42079 | INCOMPLETE OUTPUT DATA MAY OCCUR WHEN PROCESSING REQUIRED CHOICEGROUPS |
PM41925 | DESIGN STUDIO CRASHES ON WINDOWS 7 WHEN RUNNING A MAP USING A NATIVE SCHEMA THAT FAILS VALIDATION |
PM41473 | REFORMAT FUNCTION PRODUCES INVALID OUTPUT WHEN AN EMPTY ATTRIBUTE IS USED |
PM41481 | INCREASING MEMORY USAGE OF LAUNCHER CAUSES CRASH WHEN USING THE OPGP ADAPTER |
PM45603 | WMB EXECUTION GROUP CRASH OCCURS WHEN WTX THE MAP NODE FAILS WHILE ATTEMPTING TO USE XDS PARSER AND THEN RESTARTS |
PM41867 | MAP UNABLE TO USE XDS PARSER DUE TO XML ELEMENTS NOT FOLLOWING THE XML STANDARD WHICH CAUSES AN ABEND IN WMB |
PM41132 | ERROR (-9), "XMLPARSER: COULD NOT FIND TYPE TO ASSIGN XML DATA.THROWN INTERMITTENTLY WHEN MULTITHREADING MAPS |
PM39359 | XML SCHEMA LOCATION CONTAINS EBCDIC DATA WHEN RUN ON ZOS. |
PM40865 | XML INPUT DATA LEADING SPACES ARE TRUNCATED IF THE SPACES ARE FOLLOWED BY AN '&' ESCAPE CHARACTER SEQUENCE |
PM38953 | WEB SERVICE DATA GENERATED FROM WSDL IMPORTED TYPE TREE FAILS VALIDATION WHEN USING THE SAME WSDL IMPORTED TYPE TREE |
PM40488 | WTX CRASH OR OUT OF MEMORY ERROR OCCURS DURING XML XERCES VALIDATION OF INVALID DATA WHEN USING COMPONENT RULES |
PM40633 | MAP USING IN THE TERMINATOR FAILS WITH A DISK READ ERROR WHEN PROCESSING DATA USING WTX 8.2.0.4 IF3 |
PM39218 | MAP NOT OUTPUTTING < AND > CORRECTLY |
PM40573 | DTXDEBG ENTRIES FOR MAPS GETTING RETURN CODE 4 WITH RESTART MESSAGE |
PM40221 | XML SCHEMAS THAT DEFINE TYPES THAT HAVE MULTIPLE DERIVATION LEVELS OF ABSTRACT TYPES PRODUCE INCORRECT MAP OUTPUT |
PM39668 | IF A SCHEMA DEFINES A COMPLEX ELEMENT THAT USES "ALL" GROUP AND USER TYPE, SOME ITEMS ARE MISSING FROM MAP OUTPUT |
PM39655 | OUTPUT DATA OBJECTS COULD BE TRUNCATED WHEN EXECUTING MAPS COMPILED WITH AN EARLIER VERSION OF DESIGN STUDIO |
PM39701 | INPUT DATA FAILS VALIDATION WHEN ITEM PROPERTIES ARE DEFINED WITH MAXIMUM SIZE IN BYTES AND PAD TO SIZE IN CHARACTERS |
PM39100 | WSDL IMPORTER FAILURE WHEN WSDL USES EXTERNAL XML SCHEMAS WHICH REFERENCE NAMESPACES THAT ARE DEFINED IN THE WSDL DOCUMENT |
PM40567 | MQ ADAPTER LISTENER USING -REFRESH PARAMETER EXPERIENCES SLOW TRIGGERING OF MESSAGES THAT CONTAIN NON-UNIQUE MESSAGE IDS |
PM39220 | THE :BIND([T], VARIABLE) IS BOUND AS SQL_NUMERIC INSTEAD OF TEXTIN THE SQLBINDPARAMETER CAUSING CLI0112E ERROR MESSAGE |
PM38194 | DTXVER UTILITY MAY NOT RESPOND WITH ANY OUTPUT AT ALL FOR ANY GIVEN LIBRARY |
PM38315 | CURRENTDATETIME AND IF FUNCTION NOT WORKING AS EXPECTED AFTER APPLYING APAR PM28710 |
PM38621 | RESTRICTION CHARACTER NOT WORKING AS EXPECTED AFTER APPLYING PATCH FOR APAR PM37228 |
PM35896 | DATA READ FROM FILES USING GET() FUNCTION IS NOT COPIED CORRECTLY WHEN TYPE TREES USE DEPRECATED CHARACTER SETS |
PM37318 | DESIGN STUDIO CRASHES WHEN COMPILING THE MAP WITH A LARGE RULE THAT RETURNS A COMPILATION ERROR |
PM37233 | TYPE TREE PROPERTY DEFINED AS DECIMAL WITH MAXIMUM DECIMAL PLACESIZE SET TO 2 FAILS INPUT TYPE SIZE VALIDATION |
PM36552 | MAP EXECUTION CAN END IF THE INPUT FILE IS LARGER THAN 2 GB. |
PM37743 | MISSING XML DATA BETWEEN TAGS ON OUTPUT, ALTHOUGH THE DATA IS CORRECTLY READ ON INPUT (VERIFIED BY DATA AUDIT LOGGING) |
PM35852 | WTX 8.3.0.3 XML SCHEMA CLASSIC IMPORTED TYPE TREE FAILS VALIDATION FOR NILLABLE=TRUE ELEMENT |
PM37228 | TOO FEW DECIMAL PRECISION DIGITS OUTPUT BY THE CORE ENGINE. |
PM36384 | XML PARSER TRUNCATES OUTPUT WHEN USING PACKAGE FUNCTION |
PM36423 | MIME ADAPTER ERROR -2012 WHEN READING MESSAGE PART DATA. |
PM36552 | MAP EXECUTION CAN END IF THE INPUT FILE IS LARGER THAN 2 GB. |
PM36590 | AN OUTPUT FIELD IS BUILT GREATER THAN THE DEFINED MAX SIZE WHEN CONVERTING UTF-8 DATA TO SJIS DATA |
PM36157 | LAUNCHER CRASH DURING SHUTDOWN IN MPISEMDESTROY () AT MPI_SEM.CPP:87 |
PM36163 | LAUNCHER CRASH IN DEFLATEEND () FUNCTION WHEN USING GZIP ADAPTER |
PM36051 | THE MIMPORT UTILITY IS UNABLE TO IMPORT AN EXPORTED MAP XML FILEWITH EMPTY REMARK TAG |
PM36183 | VALIDATING AN EXPORTED MAP WITH THE MAPIMPORTEXPORT.MTT TREE RESULTS IN A "ONE OR MORE INPUTS WAS INVALID" ERROR. |
PM35664 | DESIGN STUDIO CRASHES WHEN RUNNING MAP THAT CONTAINS GETANDSET()FUNCTION. |
PM36047 | THE MIMPORT UTILITY HANGS WHEN IMPORTING AN EXPORTED MAP XML FILE WITH EMPTY AUDITLOCATION.MEMORY TAG |
PM36010 | XML SCHEMA IMPORTER FAILS WITH ERROR: COMPONENT [TYPE] REFERENCED BY [ELEMENT] COULD NOT BE RESOLVED |
PM35583 | MATHLIB->RAND() FUNCTION DUPLICATES NUMBERS WHEN RUN IN A MULTI-THREADED SYSTEM. |
PM35605 | PACKAGE() PRODUCES INCORRECT XML OUTPUT WHEN USING A NATIVE XML SCHEMA WITH 8.2.0.4 INTERIM FIX 3 |
PM35282 | WTX WSDL IMPORTER FAILS WHEN WSDL FILE USES IMPORT STATEMENTS DEFINED WITH RELATIVE FILE PATHS |
PM35147 | ERRORS ENCOUNTERED WHEN IMPORTING DTD HAVING THE EMPTY PARAMETER WITH NO ATTRIBUTES |
PM35310 | WHEN MAPPING A MANDATORY EMPTY ELEMENT USING THE REFORMAT() FUNCTION, THE EMPTY ELEMENT IS NOT CREATED IN THE OUTPUT |
PM35397 | INVALID AUDIT M125 MAP BUILD ERROR OCCURS FOR DATA AUDIT SETTINGS DEFINED IN THE MAP DESIGNER |
PM35391 | BACKUP FILE ERROR FOR DATABASE ADAPTER CARD IS NOT REPORTED IN THE LAUNCHER DEBUG LOG FILE |
PM35225 | XML SCHEMA IMPORTER USING XSD HINTS = ALL OPTION, CREATES TYPE TREE WITH SEQUENCE GROUPS INSTEAD OF CHOICE GROUPS |
PM34862 | DESIGN STUDIO SHOWS DUPLICATE TYPES FOR A NATIVE SCHEMA WHEN COMPLEX TYPE WITH SIMPLECONTENT IS INHERITED |
PM34990 | SAP R/3 BAPI IMPORTER CREATES TYPE TREE FIELDS SIZED IN BYTES INSTEAD OF CHARACTERS WHEN IMPORTING AS UNICODE |
PM34299 | MAP DOES NOT FAIL WHEN DIRECTORY FOR BACKUP FILE DOES NOT EXIST AND THE ERROR IS NOT REPORTED IN THE LAUNCHER DEBUG LOG FILE |
PM34783 | MINIMUM SIZE VALIDATION FAILURE AFTER APPLYING PATCH FOR APAR PM34264 |
PM34872 | ECHOIN() FUNCTION PRODUCES DIFFERENT RESULTS USING WTX 8.2.0.4 AND WTX 8.2.0.5 |
PM29456 | MAP FAILS INPUT VALIDATION WHEN USING AN XML SCHEMA IMPORTED TYPE TREE GENERATED WITH CLASSIC OPTION |
PM29462 | THE UNIQUE() FUNCTION DOES NOT RETURNING ALL THE UNIQUE INSTANCES WHEN MORE THAN TWO UNIQUE INSTANCES EXIST |
PM30984 | MAP DOES NOT CORRECTLY PARSE DATA WITH SIZED FIELD CAUSING INPUTTO FAIL VALIDATION |
IC74446 | NULL CHARACTERS MAY OCCUR IN DATAPOWER WTX OUTPUT ALTHOUGH THEY DO NOT OCCUR IN WTX STUDIO |
PM32860 | DATE SUPPORT OF JAPANESE EMPEROR YEARS IS INCORRECT FOR MEIJI AND HEISEI ERAS |
PM34264 | BOTH REQUIRED ELEMENTS OF A CHOICE GROUP ARE CREATED WHEN USING XSD:CHOICE |
PM33276 | A MAP HANG OR CRASH OCCURS WHEN EXECUTING THE SUBSTITUTE() FUNCTION ON INVALID UTF-8 DATA |
PM32755 | XML SPECIAL OR ESCAPE CHARACTERS ARE NOT CREATED CORRECTLY IN XML ATTRIBUTE OUTPUT DATA |
PM33478 | WSDL IMPORT FAILS WITH "ERROR FINDING WSDL OPERATIONS" WHEN USING THE IBM WEBSPHERE MQ TRANSPORT |
PM33726 | LONGER EXECUTION TIME WHEN PROCESSING LARGE HIPAA FILE THROUGH V4.3.1.1 IFIX 1 COMPLIANCE CHECK MAP ON Z/OS COMPARED TO V3.0.2 |
PM34116 | MAP DOES NOT START AFTER WTX MAP NODE IS INVOKED BY A WMB MESSAGE FLOW ON ZLINUX WHEN USING MAPSERVERLOCATION VARIABLE |
PM33779 | INITIATORS AND TERMINATORS ARE NOT BUILT FOR AN ITEM OF A FIXED GROUP DEFINED WITH THE 'TRACK PLACES' PROPERTY |
PM33970 | WHEN USING SQL SERVER ODBC DRIVER, THE ODBC ADAPTER DOES NOT PROPERLY PROCESS UNICODE DATA AND THE DATA APPEARS TRUNCATED |
PM34175 | CORRUPTED FORM OF MILLISECONDS APPEARING IN THE TIMEZONE INFORMATION WHEN THE INPUT TIMEZONE USES Z (ZULU TIME) |
PM34134 | "A JAVA EXCEPTION HAS BEEN ENCOUNTERED DURING THE DOCUMENT PARSING" ERROR PRODUCED WITH CLASSIC IMPORT OF XML SCHEMA |
PM34076 | ESCAPING OF THE "&" CHARACTER IS OCCURING TWICE WHEN USING WESB AND WTX |
PM30688 | EXTRACT() FUNCTION FAILS TO DETECT DIFFERENCES WHEN COMPARING DATETIME WITH SPECIAL VALUE FOR NONE IS DEFINED AS NULL BYTE |
PM33088 | COMMAND SERVER HANG USING THE IBM WEBSPHERE TX SOCKET ADAPTER ONHP ITANIUM |
PM32965 | NATIVE SCHEMA WITH ATTRIBUTE USE=PROHIBITED NOT HANDLED CORRECTLY. |
PM33113 | DESIGN STUDIO CRASH OCCURS WHEN IMPORTING A TYPE TREE .MTS FILE |
PM32953 | MAP VALIDATION ERROR FOR FIELD SIZED IN CHARACTERS WITH 'FAILS MINIMUM SIZE REQUIREMENTS' WHEN USING PATCH FOR APAR PM31912 |
PM33188 | INITIATOR AND TERMINATOR ARE CREATED IN MAP OUTPUT FOR OPTIONAL EMPTY COMPONENTS OF A GROUP DEFINED WITH TRACK PLACES |
PM32783 | MAP USING BURST MODE FAILS INPUT VALIDATION WHEN THE INPUT TYPE TREE USES THE BINDABS() FUNCTION IN A COMPONENT RULE |
PM32623 | MEMORY LEAK USING THE IBM WEBSPHERE TX API TO CALL MULTIPLE MAPS LEADING TO AN ABEND |
PM30699 | XML TAG CREATED WITH INCORRECT GREATER THAN ">" CHARACTER BEFOREAN ATTRIBUTE THAT CONTAINS AN EMPTY VALUE |
PM32236 | WTX FOR INTEGRATION SERVERS INSTALLATION ERROR "STRING VARIABLE IS NOT LARGE ENOUGH FOR STRING" WITH INSTALLATION MANAGER 1.4 |
PM32225 | WTX MAP NODE FAILURE TO LOAD A MISSING MAP DOES NOT REPORT EXCEPTION TO MESSAGE BROKER WHEN CACHE MAP IS ENABLED |
PM30505 | MAPS MIGRATED FROM WTX 1.4.2 TO WTX 8.3 SHOW AN ADDITIONAL OVERHEAD FOR LARGER FILES OF BETWEEN 50% AND 100% |
PM31912 | MAP FAILS WITH 'ONE OR MORE INPUTS WAS INVALID' ERROR WHEN AN XML ESCAPE SEQUENCE IS PRESENT IN THE INPUT DATA |
PM31834 | IN DOUBLE BYTE LANGUAGES, TYPE DESIGNER ADDS NEW TYPE WITH A DEFAULT TYPE NAME THAT INCLUDES A NON-ALLOWED SPACE CHARACTER |
PM31886 | XMLLIB->XPATHEX() FUNCTION ONLY RETURNS THE FIRST MATCHING ITEM AND DOES NOT RETURN THE ENTIRE MATCHING SET |
PM31187 | DESIGN STUDIO SEARCH RETURNS NO RESULTS WHEN SEARCHING MAP RULESFOR AN EXPRESSION THAT INCLUDES A "(" CHARACTER |
PM31066 | MAP FAILS ON DATAPOWER DUE TO INVALID OUTPUT WHEN USING CHOOSE() FUNCTION TO REFERENCE XML SUBSTITUTION CHARACTER |
PM31451 | MESSAGE NOT AVAILABLE (RC=2033, EVENT=0) ERRORS IN MQ ADAPTER TRACE WHEN ATTEMPTING TO RETRIEVE MQ MESSAGES BY CID |
PM31037 | MAP FAILS TO LOAD FROM CORRECT LOCATION AFTER BAILING DUE TO XDS AMBIGUITY CONDITION IS ENCOUNTERED |
PM31094 | XML VALIDATION ISSUE USING TYPE TREE CREATED BY THE XML SCHEMA IMPORTER WITH CLASSIC OPTION |
PM30719 | CORRUPTED TYPE TREE PROPERTY 'SPECIAL VALUE FOR NONE' CONTAINING NULLS MAY CAUSE DESIGN STUDIO CRASH |
PM30896 | COMPLIANCE CHECK MAP FAILS TO GENERATE 999 AND TA1 OUTPUT WHEN USING CORE ENGINE PATCH FOR APAR PM26947 |
PM30792 | RUNNING A MAP WITH THE WTX DEBUGGER CAUSES A MAP TO HANG WHEN USING THE STEP IN FEATURE. |
PM30972 | XML SCHEMA IMPORTER FAILS WHEN IMPORTING SCHEMA WITH REFERENCES TO SAME SCHEMA FILENAME LOCATED IN DIFFERENT DIRECTORIES |
PM31019 | WTX MAP HANGS IN AN INFINITE LOOP WHILE VALIDATING INPUT DATA USING TYPE TREE GROUP WITH BLOB TYPE WITH NO SYNTAX DEFINED |
PM29146 | TYPE TREE ANALYSER ERROR WHEN NEW CATEOGRY ADDED. |
PM30820 | HIPAA COMPONENT RULE ADDS ALL SVD AMOUNTS AND CAS AMOUNTS FOR EACH SV1 WITHOUT CONSIDERING THAT THERE MAY BE MULTIPLE PAYERS |
PM29968 | TEMPORARY FILES CREATED AS A RESULT OF USING THE -FILE COMMAND WITH EITHER DBQUERY() OR DBLOOKUP() MAY NOT GET DELETED |
PM29706 | DATA FAILS VALIDATION WITH XML PARSER ON AIX WITH WTX 8.2.0.4 IF3 USING A JAVA COMPUTE NODE CALLING THE WTX JAVA API. |
PM30182 | NULL CHARACTERS APPEARING IN THE OUTPUT WHEN A RULE EVALUATES TO NONE |
PM30525 | A MAP USING A COBOL COPYBOOK IMPORTED TYPE TREE CRASHES DURING MAP EXECUTION |
PM29962 | WHEN CALLING A WTX RUN MAP, A LAUNCHER CRASH OCCURS IN THE PARSEARGS() FUNCTION |
PM29978 | DESIGN STUDIO DOES NOT RECOGNIZE TYPE NAMES AS DIFFERENT WHEN USING THE SAME NAME BUT WITH DIFFERENT CASE CHARACTER |
PM30270 | REFORMAT() FUNCTION MAY ADD ADDITIONAL CHARACTERS TO OUTPUT DATAWHEN OUTPUT TYPE TREE INCLUDES INITIATORS AND TERMINATORS |
PM26157 | REFORMAT() FUNCTION GIVING INCORRECT RESULTS WHEN USED IN CARDS THAT USE A NATIVE XSD INSTEAD OF A TYPE TREE |
PM25765 | OUTPUT FIELD VALUE IS NOT CREATED WHEN THE VALUE IS MAPPED FROM A PREVIOUS FIELD ON THE SAME OUTPUT CARD |
PM29510 | MAP DESIGNER CRASH OCCURS WHEN A NON DATABASE TYPE TREE IS USED IN THE INPUT DATABASE CARD |
PM29550 | RUN MAP CALL THAT USES A HANDLEIN(PACKAGE()) FUNCTION CALL TO PASS DATA TO A RUN MAP CAUSES LARGE MEMORY USAGE |
PM28150 | VALID INPUT DATA CONTAINING JAPANESE CHARACTERS FAILS MAP VALIDATION WITH "INPUT TYPE CONTAINS ERRORS" (RETURN CODE 28) |
PM29301 | CHOICE GROUP MISSING FROM TYPE TREE AFTER APPLYING XML SCHEMA IMPORTER PATCH FOR APAR PM26174 |
PM28710 | IN A WTX MAP, THE TIME ZONE VALUE DOES NOT APPEAR TO BE USED WHEN COMPARING DATETIME VALUES WHICH INCLUDE THE TIME ZONE |
PM29209 | COMPONENT RULES CHECKING INPUT CONTENT WITH SECTIONS MAY FAIL VALIDATION EVEN IF CORRECT |
PM28889 | INVOKING A WTX MAP WITH INVALID DATA FROM A MESSAGE BROKER FLOW RESULTS IN A HANG. |
PM29197 | EXECUTION GROUP HANGS ON STARTUP WHEN MISSING RESOURCE NAME FILE(MRN) REFERENCED BY RESOURCE CONFIGURATION FILE (MRC) |
PM28827 | DATA CORRUPTION MAY OCCUR IN A MULTI-THREADED XML PARSING SCENARIO ON UNIX PLATFORMS |
PM28432 | MAP EXECUTION FAILS WITH A SEGMENTATION FAULT IN CHOP_ICUXCHARS FUNCTION ON UNIX PLATFORMS |
PM24856 | INCORRECT OUTPUT CREATED WHEN MAP RULE USES COUNT OF EXTRACT FORXSD INPUT PLUS CONCATENATED LITERALS AND COUNT RESULT IS 0 |
PM27709 | LAUNCHER CRASH OCCURS IN CORE ENGINE WITH TIMING_FINDDSIZE() FUNCTION ON WTX 8.2.0.4 |
PM28341 | XML SCHEMA IMPORTER INCORRECTLY CREATES GROUP AS A SEQUENCE WHENTHE ALL-ELEMENTS OPTION IS CHOSEN |
PM28421 | LAUNCHER CRASH OCCURS IN CORE ENGINE WITH GETDATAPTR() FUNCTION WHEN RUNNING A SPECIFIC MAP ON WTX 8.2.0.4 |
PM28520 | WHEN BOTH A MAP AND ASSOCIATED TYPE TREE ARE OPEN IN THE DESIGN STUDIO, A MAP COMPILE OR BUILD CAN CAUSE A CRASH |
PM30736 | JAVA.LANG.ILLEGALSTATEEXCEPTION: ILLEGAL ATTEMPT TO START A LOCAL TRANSACTION WITHIN A GLOBAL TRANSACTION USING WTX FROM WAS |
PM28555 | CORE ENGINE CRASH WHEN USING A WORD() FUNCTION WHICH USES THE CORRUPT OUTPUT OF A MID() FUNCTION |
PM28121 | LAUNCHER HANG WITH NOT ENOUGH MEMORY ERRORS MAY OCCUR DUE TO A MEMORY LEAK WHEN MQ ADAPTER GET RETURNS NO MESSAGE FOUND ERROR |
PM27936 | IMPORTING AN XML SCHEMA USING THE CLASSIC OPTION THAT CONTAINS COMPLEX TYPES WOULD PRODUCE GROUPS CONTAINING 'NULL' COMPONENTS |
PM27858 | MAP ABEND OCCURS WHEN USING NATIVE XML SCHEMA INPUT CARD AND INPUT DATA XML ENCODING IS DIFFERENT THAN XML SCHEMA ENCODING |
PM27277 | MAP CREATES A VALID FIRST MQ MESSAGE AND A SECOND EMPTY MQ MESSAGE ON UNIX WHEN THERE IS ONLY ONE BURST OF DATA |
PM27390 | ERROR ENCOUNTERED WHEN RUNNING CLUSTER REGISTER SCRIPT ON SOLARIS |
PM23678 | MAP HANGS DURING RUNTIME IN MAP DESIGNER, COMMAND SERVER, AND MB TOOLKIT 7.0 PLUS FP1 |
PM22497 | SUBSTITUTE() FUNCTION DOES NOT WORK CORRECTLY WHEN CONVERTING FROM DBCS EBCDIC (IBM-1390) CHARACTER SET TO UTF8 CHARACTER SET |
PM22623 | TRIMRIGHT AND TRIMLEFT FUNCTIONS DO NOT WORK CORRECTLY WITH IBM-1390 DATA |
PM21690 | DESIGN STUDIO OR COMMAND SERVER CRASH OCCURS WHEN RUNNING A MAP WITH A FUNCTIONAL MAP USING AN INDEX() OF A LOOKUP() FUNCTION |
PM22682 | DESIGN STUDIO CRASHES DURING THE COMPILATION OF MAPS. |
PM23674 | DIFFERENT OUTPUT FROM 8.0.1 AND 8.3.0.2 MAP |
PM24863 | MATHLIB->RAND() FUNCTION USED IN A CONDITIONAL STATEMENT RESULTSIN INCORRECT OUTPUT |
PM26616 | VALIDATION OF THE RESULTS IN INVALID DATA |
PM26943 | VALID XML BEING MARKED AS INVALID |
PM26885 | A LAUNCHER CRASH OCCURS DUE TO MEMORY CORRUPTION DURING LAUNCHERSHUTDOWN |
PM26392 | INPUT AND OUTPUT MQ CONNECTIONS ARE SHARED WHEN THE TRANSACTION SETTINGS ARE DIFFERENT LEAADING TO INCORRECT MESSAGE COMMIT |
PM26622 | MESSAGE BROKER DATAFLOWENGINE ABEND OCCURS WHEN USING THE WTX MAP NODE AND THE MESSAGE FLOW ENCOUNTERS AN EXCEPTION |
PM25658 | XML DTD OPTIONAL FIELDS ARE CREATED AS MANDATORY WHEN THE DTD ISIMPORTED AS TYPE TREE USING THE WTX 8.1 DTD IMPORTER |
PM25388 | FIND() FUNCTION DOES NOT RETURN THE CORRECT VALUE WHEN USING UTF-8 ICU CODE PAGE |
PM26174 | USING THE CLASSIC OPTION OF THE XML SCHEMA IMPORTER CAN LEAD TO SOME OPTIONAL GROUPS BEING CREATED AS MANDATORY. |
PM27655 | WTX MAP CRASH OCCURS WHEN RUNNING ON A DATAPOWER 3.8.0.8 SYSTEM |
PM25850 | LAST PART OF OUTPUT MAPPING TRUNCATED WHEN TRADITIONAL CHINESE CHARACTERS ARE IN THE INPUT. |
PM25747 | MAP CRASHES IN SETUPRULEPARMS() FUNCTION WHEN STRING LITERALS ARE PASSED AS THE ARGUMENT OF A FUNCTIONAL MAP |
PM25642 | XML SCHEMA ELEMENTS WITH SIZE RESTRICTION IN THE EXTENSION BASE ARE IMPORTED AS TYPE TREE ELEMENTS WITHOUT MIN AND MAX SIZE |
PM25682 | POSSIBLE VALIDATION FAILURE FOR TEXT OBJECTS WHICH HAVE A MIN SIZE SPECIFIED (IN CHARACTERS) BUT NO MAX SIZE. |
PM25109 | LAUNCHER CRASH ON LINUX WHEN RUNNING MULTI-THREADED MAPS |
PM25208 | ATTACHMENTS ADDED TO AN OUTGOING EMAIL USING THE EMAIL ADAPTER (WITH THE LOTUS NOTES OPTION) GET EMBEDDED AS EMAIL BODY CONTENT |
PM25160 | ENCOUNTERING SYSTEM ERROR CODE 3 WHEN DEPLOYING FROM IFD AFTER COPYING A NEW SYSTEM TO THE MSD FILE. |
PM25166 | TYPE TREE ANALYSIS RESULTS CONTAINING AN L216 ERROR IN SUMMARY, INCORRECTLY DISPLAYS THE ERROR UNDER WARNING DETAILS |
PM23146 | NO OUTPUT FROM A TONUMBER() FUNCTION, WORKING DIRECTLY ON THE RESULTS OF A WORD() THAT REFERENCES AN OBJECT DEFINED AS UTF-8 |
PM24899 | DELIMITERS FOR EMPTY ELEMENTS ARE NOT BEING PROPERLY IDENTIFIED DURING UTF-8 VALIDATION |
PM24813 | DATABASE TRACE FILE FROM DB2 NATIVE Z/OS ADAPTER INCLUDES EXTRANEOUS MESSAGES NOT PREVIOUSLY SEEN IN LOG. |
PM24988 | SPACES ADDED TO OR MISSING FROM FIELD CONTAINING TAIWANESE CHARACTERS WHEN PATCH FOR APAR PM25850 IS APPLIED |
PM26169 | ERROR IMPORTING PL/I INCLUDE FILE - IBM1618I S SYNTAX OF THE %INCLUDE STATEMENT IS INCORRECT |
PM24628 | USING THE HANDLEIN() FUNCTION IN COMBINATION WITH THE WORD() FUNCTION MAY PRODUCE INCORRECT RESULTS |
PM24716 | WTX 64BIT LAUNCHER CRASHES OCCUR IN MPIPROPERTYGETTEXT() FUNCTION DURING GET/PUT DB ERROR HANDLING WHEN RUNNING A MAP |
PM22161 | WHEN WTX XERCES PARSES A STRING THAT IS DEFINED AS "COLLAPSED" AND STARTS WITH " &", THE PARSER STOPS AND ERRORS |
PM24479 | WTX MAP USING MID() FUNCTION RETURNING A NONE MAY CAUSE MEMORY CURRUPTION WHICH COULD RESULT IN AN ABEND OR CRASH |
PM24515 | MULTI-LINE RESPONSE FROM AN FTP SERVER STARTING WITH A SPACE WILL BREAK THE COMMUNICATION CHAIN AND POTENTIALLY FAIL THE MAP |
PM24546 | INTEGRATION FLOW DESIGNER ALLOWS MAP / COMPONENT NAMES GREATER THAN THE 32 BYTE LIMIT RESULTING IN LAUNCHER START FAILURE |
PM24065 | MANDATORY XML SEQUENCES MISSING FROM OUTPUT EVEN IF GROUP IS IMPORTED WITH A RANGE OF 1:1 |
PM24317 | FAIL() FUNCTION DOES NOT DETECT PUT() FUNCTION FILE ADAPTER FAILURE DUE TO INSUFFICIENT SPACE ALLOCATED ON Z/OS |
PM23566 | MAPPING LITTLE ENDIAN 4 BIT BINARY NUMBERS TO INTEGERS RESULTS IN INCORRECT OUTPUT |
PM23520 | SEARCHUP() MAY BE UNABLE TO FIND A PATTERN MATCH AGAINST A LITERAL IN WTX 8.1 AND ABOVE |
PM23451 | MANDATORY CHOICE ELEMENT IMPORTS AS OPTIONAL WHEN USING THE WTX XML SCHEMA IMPORTER WITH THE CLASSIC OPTION. |
PM23055 | UNABLE TO IMPORT WSDL WITH A RESTRICTION LIST THAT CONTAINS XML SUBSTITUTE STRINGS. |
PM23560 | SYNTAX ITEMS LARGER THAN 1000 BYTES MAPPED TO AN XML FIELD MAY CAUSE A CRASH. |
PM23464 | CORE TRANSFORMATION ENGINE CRASH WHEN MAP IS EXECUTED THAT WAS COMPILED WITH A PAD CHARACTER OF |
PM22689 | VALID XML FAILS TO PARSE THROUGH WTX MAP. ERROR IS "CANNOT BE USED IN A DERIVATION BY RESTRICTION FOR A COMPLEXTYPE" |
PM23348 | AFTER RIGHT CLICKING IN RULE WINDOWS IN DESIGN STUDIO 8.2 AND SELECTING HELP OPTION, NOTHING OCCURS (NO HELP PROVIDED). |
PM22989 | TYPE TREE PROPERTIES NOT BEING PROPERLY RETAINED FOR TYPE SYNTAX--> TERMINATOR --> ITEM |
PM22740 | DESIGN STUDIO AND COMMAND SERVER HANG WHEN DBCS TEXT IS ENTERED IN THE DESCRIPTION FIELD OF A TYPE TREE |
PK72045 | XML DATA CREATED AS EBCDIC BUT XML TAGS CREATED AS UTF-8 WHEN TYPE TREE LANGUAGE AND XML ENCODING SET TO EBCDIC |
PM22888 | COMPLIANCE CHECK MAP CREATES ACCEPTED 999 FOR INVALID 5010 837I DATA |
PM22776 | SYSTEM NAMES DEPLOYED TO THE LAUNCHER NEED TO BE CONSTRAINED TO A MAXIMUM OF 32 CHARACTERS |
PM22861 | INCOMPLETE POP UP MESSAGE IS DISPLAYED IN DESIGN STUDIO WHEN RUNNING A MAP ON A DATAPOWER APPLIANCE |
PM18465 | DESIGN STUDIO JAVA EXCEPTION WHEN USING SPECIFIC NATIVE XML SCHEMA AS INPUT CARD OR FAILURE "ONE OR MORE INPUTS WAS INVALID" |
PM22428 | LAUNCHER CRASH USING THE TIBCO RV ADAPTER AS A TRIGGER |
PM22306 | MAP DESIGNER CRASH WHEN RUNNING MAP THAT USES A FROMDATETIME() FUNCTION WITH FORMAT STRING THAT INCLUDES HH (NOT HH12 OR HH24) |
PM22581 | DEFAULT XML PARSER TRACE FILE CREATED WHEN RUNNING MAP USING WTXAPI WITH THE MAP TRACE TURNED OFF |
PM21172 | TRACK SET TO PLACES NOT WORKING AS EXPECTED. |
PM20369 | DESIGN STUDIO "SHOW SCHEMAS AS NATIVE ICONS" SETTING CAUSES MAP CARDS OF NATIVE SCHEMA MAP TO NOT DISPLAY PROPERLY |
PM22092 | INCORRECT USER NAME DISPLAY WHEN USING LAUNCHER.BAT / .SH COMMAND AND USER DOES NOT HAVE THE CORRECT ACCESS RIGHTS |
PM21575 | DESIGN STUDIO CRASHES WHEN SELECTING "RUN LOCALLY" ON A MAP THATCOMPILED SUCCESSFULLY FOR DATAPOWER |
PM21786 | COBOL COPYBOOK FIELDS OF -9999 CREATE GROUP OBJECT INSTEAD OF ITEM OBJECTS |
PM22441 | MEMORY LEAK RELATED TO THE XML4C_5_6::ICULCPTRANSCODER::TRANSCODE FUNCTION |
PM21888 | MESSAGE CONTAINS GARBAGE CHARACTERS AFTER ANALYZING TYPE TREE IN JAPANESE LOCALE. |
PM22012 | 930 CODEPAGE DATA NOT TRUNCATED TO 50 BYTES AFTER ADDING HEX 0F SHIFT-IN CHARACTER AND TYPE DEFINED IN BYTES. |
PM19286 | DB2 DATABASE ADAPTER TRACE CONTAINS REDUNDANT INFORMATION WHEN USING WTX 8.3 DB2 DATABASE ADAPTER |
PM21572 | DATA LANGUAGE IS CHANGED AFTER IMPORTING A WTX VERSION 8.2.0.4 EXPORTED PROJECT INTERCHANGE INTO WTX VERSION 8.3.0.2 |
PM19401 | A CRASH OCCURS WHEN RUNNING A MAP THAT USES A SPECIFIC XML TYPE TREE CREATED FROM AN XML SCHEMA |
PM21435 | 1390 CODEPAGE DATA MISSING HEX 0F SHIFT-IN CHARACTER WHEN TRUNCATED AND SIZED AS DEFINED IN BYTES |
PM21072 | CERTAIN INVALID XML ELEMENTS PARSED THROUGH A WTX MAP CAN CAUSE THE MAP DESIGNER TO CRASH |
PM21304 | GARBAGE CHARACTERS SEEN IN "DATAPOWER SOA APPLIANCE" POPUP WINDOW WHEN RUNNING A MAP |
PM21434 | DESIGN STUDIO MAP SOURCE SEARCH USING "SEARCH IN" OPTION "TYPE TREE FILES" CAUSES TYPE TREE FILE TIMESTAMP TO BE UPDATED |
PM20732 | MAP FAILS WITH INPUT XML VALIDATION ' IS NOT VALID QNAME' ERROR AS SEEN IN THE XML PARSER TRACE |
PM20166 | MAPS USING THE XMLLIB->XSLT FUNCTION EXPERIENCING SEVERE PERFORMANCE DELAYS WITH LARGE DATA |
PM20265 | THE RIGHT() FUNCTION DOES NOT RETURN THE EXPECTED TWO BYTE JAPANESE CHARACTERS |
PM20833 | DESIGN STUDIO HANG OCCURS WHEN ATTEMPTING TO BUILD A SPECIFIC MAP |
PM19761 | COMMAND SERVER OR LAUNCHER CRASH / CORE DUMP OCCURS WHEN A MAP IS VALIDATING INPUT USING WTX 64BIT |
PM20167 | LAST INSTANCE OF A REPEATING GROUP NOT SEEN AS BINARY BASE64 BY WEBSPHERE MESSAGE BROKER |
[{"Product":{"code":"SSVSD8-1","label":"WebSphere 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":"PF025","label":"Platform Independent"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"8.2.0.6","Edition":"International","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Product Synonym
Ascential DataStage TX
Was this topic helpful?
Document Information
Modified date:
06 October 2022
UID
swg27023924