***
*** (C) Copyright International Business Machines Corp. 2002,2010.
*** All Rights Reserved
*** Licensed Materials - Property Of IBM
***
*** Welcome to WebSphere Data Interchange Version 3.3.0 ***
*** Readme.txt for Server Fix Pack (SFP) 5 - November 2010 ***
**************************************************************
*** General SFP Installation Information
**************************************************************
SFPs are cumulative. Previous modules/functions are not deleted
as part of the build process.
This way you can install the latest SFPs without having to
install each SFP to get to the latest SFP. For example, you can
install SFP5 without having to install SFP1, SFP2, to SFP5. But
once you install SFP5, you cannot install a previous SFP. Also,
you cannot install the same SFP twice.
For uninstall, once you uninstall, you will need to reinstall
the base, then the latest SPF. Install will check for the base
install before installing any SFPs.
How can you tell which SFP you have installed?
For Windows :
Look at the registry,
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\WebSphere Data Interchange Server,
look for key 3.3.0, then property "Service Level". The value is the
latest SFP number installed.
For AIX:
Issue this command,
lslpp -L IBMWDI33SERVER
You should see output with this info:
FileSet Level State Type Description (Uninstaller)
-------------------------------------------------------------------
IBMWDIServer33 3.3.6.5 C P ISMP installed entry
where 6 is the SFP number
**************************************************************
*** WDI Client requirements:
**************************************************************
To take full advantage of the enhancements and fixes we
recommend that you also have the latest Client Fixpack installed.
This SFP will also work with earlier versions of the WDI 3.3.0
Client, but at a reduced level of function.
APAR PM18749 fixed in this WDI 3.3 Server Fix Pack is dependent upon
Client Fix Pack 11. That is, when applying Server Fix Pack 5,
multiple DB2 views will be changed, for which Client Fix Pack 11 is
required for proper functionality. If the DB2 views are changed accordingly,
and CFP11 is not yet deployed on user's WDI Client, the following error
will result when entering a partial Transaction Handle value on
the Selection Criteria window for the "Transactions" or
"Enveloped Transactions" tab:
11041: A database error ocurred while attemption to open table
"EDIENU33.EDIVTSTH". ODBC return code is -1. Description: SQL0181N
The string representation of datetime value is out of range. SQLSTATE=22007.
On the other hand, Client Fix Pack 11 may be installed without first
applying Server Fix Pack 5, however, the user will not gain improved
performance without the new DB2 view therein.
See the following link for apar PM18749 details:
http://www-01.ibm.com/support/docview.wss?uid=swg1PM18749
General note to all users --
Be sure your WebSphere Data Interchange configuration is set to generate
appropriate century values for 2011 dates and beyond. Century date may
be unexpectedly output as 19 when translating or transforming data,
i.e. the century and year may be output as 1911, instead of 2011.
Check your configuration now using this link:
http://www-01.ibm.com/support/docview.wss?uid=swg21418940
**************************************************************
*** Summary of enhancements to date:
**************************************************************
- Support for all AIX 5.x Platforms (CSD3)
P8011574 - PK43285 - Add SMF 89 registration and deregistration support
to allow subcapacity pricing in batch Z/OS and CICS.
The registration and deregistration is automatic and
will occur whether SMF89 is implemented or not.
P8011867 - PK57839 - Add date and time for each event to the XML print file.
****************************************************************
*** Special instructions for installing SFPs
****************************************************************
Some SFPs have introduced database changes. These instructions
tell you how to update your database to work with this SFP.
If this is a new install (fresh database load) the following
installation process can be used:
(a) Install the WDI Base Code
(b) Install the latest Server Fix Pack
(c) Perform the Installation Configuration steps as indicated
for the Base Code install (DB2 configuration steps).
This is described in the section "Install instructions for
WebSphere Data Interchange V3.3" in the readme for the base install.
Complete server installation and setup instructions can also be found in
the WebSphere Data Interchange Administration and Security Guide.
If you are applying this SFP to an existing installation, you
need to do the following steps after you install this SFP:
1) Apply database updates, if necessary.
1a) Perform the following steps as a user with DB2 administrator authority.
1b) If you are installing on Windows, using your DB2 administrator user ID,
select Start -> Programs -> IBM DB2 -> Command Window to open the DB2
Command window. If you are installing on AIX, log in as a user with
administrator authority.
Note: You should use the same userid that was initially used to create the
EDIEC33E database.
1c) Using the command window or login session,
apply the database updates from any previosy SFPs that have not already been installed
Note: SFP4 is the first v3.3 SFP with a database change
1d) If you have already applied the updates for some of the previous
SFPs, but not all of them, you can skip the steps for the SFPs you have already
installed on your system. If you have already applied ALL previous CSDs, you can
skip directly to (1f) and apply the updates for this SFP.
Although the CSD files are cumulative, the database updates are not. If there
are special database updates that needed to be done as part of previous SFPs, you
need to apply those changes.
If there are steps that you do not want to do in any of the scripts, you can
comment out the line by placing a "--" at the beginning of the line. Comments
within the scripts describe what each of the steps will do.
1e) SFP4: Run the script to update the database tables
1e1) Change to the ddl directory under the installation directory.
1e2) Issue the following command:
db2 -tf sfp4.ddl -l sfp4.log
This creates 2 DB2 Table Indexes in the database.
1f) SFP5: Run the script to update the database tables
1f1) Change to the ddl directory under the installation directory.
1f2) If sfp5.ddl is not already available in this directory, then download
from SFP5 download page and store in the ddl directory.
1f3) Issue the following command:
db2 -tf sfp5.ddl -l sfp5.log
This changes 4 DB2 Views and 1 Synonym in the database.
Note: If running sfp5.ddl for the first time, you will encounter warning:
SQL0204N "EDIENU33.DSEXTR" is an undefined name.
1f4) Issue the following command:
db2 -tf grntec33.ddl -l grntec33_sfp5.log
This will restore the GRANT authority dropped when the VIEWs were dropped.
2) Load the updated default data
2a) Change to the ddl directory under the installation directory.
2b) Issue the following command:
loadmsgs.bat
This process will load the updated messages into the DB2 table
3) Bind the new WDI executables to the database
3a) Change to the bind directory under the installation directory.
3b) Issue the following command:
db2 -tf bindgrnt.fil
****************************************************************
******** End of special instructions ***************************
****************************************************************
****************************************************************
*** START OF WebSphere Data Interchange V3.3 SFP5 README.TXT ***
****************************************************************
November 2010 - SPF5
The following problems have been resolved with this SFP:
P8012077 - PM13739 - HOST - CICS ASRA DURING PERFORM IMPORT
P8012098 - IC67182 - RECEIVE FILE OVERWRITTEN WHEN USED FROM DATA REFERENCE
P8012101 - PM10440 - TR0832 SEVERITY 12 MESSAGE RECEIVED WHEN PERFORM TRANSLATE
P8012104 - IC67604 - SOME SAC08 VALUES HAVE LEADING ZEROS
P8012108 - PM12684 - SERVER - EXPORT EI0048 STANDARD X
P8012110 - PM12670 - SERVER - ABEND U4083 DURING ENVELOPE DATA EXTRACT
P8012112 - PM12146 - CSV002I - REQUEST FOR MODULE FXXZCBLH EXCEEDS MAXIMUM USE COUNT
P8012113 - IC67862 - REPETITION SEPARATOR PARAMETER DOES NOT WORK PROPERLY
P8012114 - PM12384 - UCS ENVELOPE OUTPUT IS INCORRECT - GS07 POPULATED W/LOW-VALUES
AND GS08 CONTAINS COMBINED VALUE FROM GS07/GS08 U ENV PROFILE.
P8012115 - PM15239 - SQLERR -811 DURING RGT ON EDITSGP TABLE
P8012116 - PM13715 - CICS - MEMORY LEAKS DURING PERFORM TRANSFORM
P8012118 - IC68153 - TRAILING DECIMAL POINT ADDED TO SOME ACCUMULATED SAC05 VALUES
P8012122 - IC68443 - EDISERVR STDERR SHOWS: WDI SERVICE DIRECTOR EXCEPTION, HOWEVER,
IDOC SEND MAP APPEARS TO COMPLETE SUCCESSFULLY AS PER STDOUT
P8012123 - IC68484 - DT(ADF-EDI) PERFORMANCE ISSUE WHEN TRANSACTION STORE IS ENABLED
FOR AN ADF INPUT MESSAGE FILE WITH MANY TRANSACTIONS
P8012124 - IC68843 - WDI 3.3 DT MAP (ADF-EDI) TRUNCATES TRAILING MINUS SIGNS '-'
P8012125 - PM15349 - RECEIVE MAP GENERATES 997 AK304 WITH LEADING SPACES BEFORE VALUE
P8012126 - PM16514 - IEW2648E LINK-EDIT ERRORS OCCUR WHEN RUNNING SAMPLE JCL EDIJRSML
OR FXXJRSML.
P8012127 - PM16706 - AFTER DOING INBOUND PROCESSING TRANSACTIONS DO NOT SHOW UP UNDER
ENVELOPED TRANSACTIONS IN DOCUMENT STORE
P8012128 - PM16863 - ADDITIONAL TRANSACTION TYPES INCLUDED IN OUTBOUND ENVELOPES WHEN
"CONTROL NUMBERS BY TRANSACTION ID" IS DEFINED IN USAGE.
P8012145 - PM18617 - SERVER - UNABLE TO READ THE CICS EVENT LOG HOLDFILE
P8012148 - PM18749 - WDICLIENT SLOW PERFORMANCE WHEN OPENING A TRANSACTION FROM THE
LIST ON DOCUMENT STORE TRANSACTIONS TAB
P8012149 - IC70093 - WDISERVER ADV ADAPTER FAILS WITH MQ ERROR REASON 2110 WHEN THE
MQMD.FORMAT NAME IN MESSAGE IS MQFMT_NONE AND CP SET IS TO 1208.
P8012150 - IC70171 - NULL POINTER EXCEPTION IN SAMPLE JAVA EVENT HANDLER FOR E-MAIL
WHEN TWO OR MORE EVENT MESSAGES ARE AVAILABLE.
P8012154 - PM21619 - ASRA ABEND OCCURS WHEN USING HOTDI ON THIRD TRANSACTION
P8012156 - IC71734 - GLOBAL VARIABLE ON A RECEIVE MAP IS BEING RESET BETWEEN 1ST AND
2ND TRANSACTION WHEN USING ADVANCED WMQ ADAPTER.
P8012157 - PM23221 - EDIJMLOD PERFORMANCE ISSUE WITH LARGE NUMBER OF TS RECS
P8012158 - IC71338 - WDI ADVANCED ADAPTER ABENDS WITH SIGNAL 11 WHEN MULTIPLE
MESSAGES ARE PLACED ON INPUT QUEUE FOR A DT TRANSFORMATION.
P8012160 - PM23488 - TS0300 SEVERITY 12 ERROR DURING TRANSFORMATION OF ZERO LENGTH
EDI TRANSACTION AND DOCUMENT STORE IS ON.
P8012161 - IC71573 - WDI ADVANCED ADAPTER HANG WHEN TRANSLATOR RECEIVES A SIGNAL 11'S
AND DOES NOT RECOVER GRACEFULLY.
P8012162 - PM23732 - CSV TO EDI DATA TRANSFORMATION IS NOT HONORING THE BEGINNING
RECORD AS THE START OF A NEW TRANSACTION.
P8012163 - PM24630 - UP0026 TRANSFORMATION WARNING WHEN MAPPING GETPROPERTY ("ISA16")
DUE TO WDI 3.3 INCORRECTLY RETURNING 4 BYTE HEX REPRESENTATION.
---- Special Considerations --------------------
P8012148 / APAR PM18749, fixed by WDI 3.3 PTF Server Fix Pack 5 or WDI z/OS PTF UK60104,
is dependent upon Client Fix Pack 11. That is, when applying Server Fix Pack 5,
or PTF UK60104, multiple DB2 views will be changed, for which Client Fix Pack 11
is required for proper functionality. If the DB2 views are changed accordingly,
and CFP11 is not yet deployed on user's WDI Client, the following error will result
when entering a partial Transaction Handle value on the Selection Criteria window for
the "Transactions" or "Enveloped Transactions" tab:
11041: A database error ocurred while attemption to open table
"EDIENU33.EDIVTSTH". ODBC return code is -1. Description: SQL0181N
The string representation of datetime value is out of range. SQLSTATE=22007.
On the other hand, Client Fix Pack may be installed without first
applying Server Fix Pack 5 or without z/OS PTF UK60104, however, the
user will not gain improved performance without the new DB2 view therein.
See the following link for apar PM18749 details:
http://www-01.ibm.com/support/docview.wss?uid=swg1PM18749
P8012125, APAR number PM15349, changes the definition for X12 Functional Acknowledgment
maps distributed with the WDI 3.3 base product. Only clients migrating to WDI v3.3 from
versions prior to SFP5 need take any special action. These corrections are included
with SFP5, but they are not automatically installed into the database.
Clients who experience issues with the AK3 segment as described in this APAR should follow
the following process to update their definitions.
1) A modified Data Format is being distributed in the file named "eidatamp.eif" provided in the
../eif folder located in the WDI install directory path, e.g. Program Files/IBM/WDIServer/V3.3.
This file contains many installation default objects. DO NOT apply all objects in this file.
Doing so may overlay installation modified parameters.
The modified Data format definition is named FUNCACKX12APP. This is the only object that
is affected by P8012125.
2) Use the WDI Client to import the modified Data Format in the import file named "eidatamp.eif".
FUNCACKX12APP is the only object to be imported.
3) Again using WDI Client, compile the Control Strings for the following FAMaps located in the
SEND Maps folder of WDI Client:
$FUNACK997
$FUNACK997G
$FUNACK997V35
$FUNACK997V35G
$FUNACK997V37
$FUNACK997V37G.
Without these new definitions, clients will see alignment problems with the AK304 element
as described in the APAR.
**************************************************************
*** END OF WebSphere Data Interchange V3.3 SFP5 README.TXT ***
**************************************************************
****************************************************************
*** START OF WebSphere Data Interchange V3.3 SFP4 README.TXT ***
****************************************************************
April 2010 - SPF4
The following problems have been resolved with this SFP:
P8010661 - PK74102 - HOST - ABEND - TRANSACTION STORE AFTER NETWORK STSATUS UPDATE
P8012054 - PM00818 - WDI 3.3 "PERFORM TRADING PARTNER CAPABILITY DATA EXTRACT" COMMAND
P8012060 - PM10787 - UNIQUE SQL SELECT USAGES STATEMENT FINDS MULTIPLE ROWS (-811)
P8012064 - IC65086 - ADVANCED ADAPTER ABENDS WHEN WMQ QUEUE LENGTH EXCEEDS 39 CHARS
P8012065 - PM03354 - DATE AND ICN NOT OUTPUTTED IN PERFORM PRINT
P8012067 - PM05403 - CICS - DT UTILITY CONTROL BLOCK FABUILT
P8012068 - PM05397 - CICS - DT INTERCHANGES MISSING FROM QDATA
P8012069 - IC65355 - TRANSFORMATION OF ADF TO EDI NOT HANDLING
P8012070 - IC65436 - WHEN DOING A ADF TO EDI TRANSLATION USING REGULAR ADAPTER
WDI ISSUES A SQL1024 DATABASE CONNECTION DOES NOT EXIST
P8012071 - PM05185 - ASRA ABEND IN EDIDTUTL DURING XML TO ADF
P8012072 - IC65790 - VN1007 ERROR WHEN ATTEMPTING TO WRITE ADF OUTPUT TO WMQ QUE
P8012073 - IC65840 - WDI ADVANCED ADAPTER ATTEMPTS TO PROCESS
P8012075 - IC65969 - MAP RULE UNABLE TO RESOLVE SENDER ID TO TRADING PARTNER NICKNM
P8012078 - PM06549 - SQLCODE991 WHEN USING PGM IKJEFTXX AND EDITSIN ALSO ALLOCATED
P8012079 - IC66038 - UT0002 SEVERITY: 04 - CODEPAGE CONVERTER FAILED TO INITIALIZE
P8012081 - PM07292 - RGT SERVER FAILURE RE:8011948 PARSING MULTIPLE UNTDI - LOOP
P8012082 - IC66106 - SAP STATUS UPDATE FAILS WITH ERROR FF0566 EDISST DBERROR -1421
P8012083 - PM06927 - DELETE EDI STANDARD PERFORMANCE IS SLOW AND CAN BE IMPROVED
P8012084 - IC66761 - SUPPORT ZONED-DECIMAL WITH SEND / RECEIVE TRANSLATION
P8012085 - PM07503 - SCH SEGMENT BEING ADDED TO BEGINNING OF TRADACOM ERRONEOUSLY
P8012086 - IC66458 - ADVANCED ADAPTER DOES NOT PROPAGATE CORREL ID IN PRTFILE OR EVENT QUEUE
P8012087 - IC66480 - SETPROPERTY ON MQMD PROPERTIES CAUSES ABEND IN EDISERVR WITH PAGE(Y)
P8012089 - PM08403 - WDI CICS RECEIVE TRANSLATION PERFORMANCE DEGRADED FOR XML
P8012095 - PM10327 - NO TEXT FOUND FOR MESSAGE EI0034 IN MESSAGE TABLE
P8012097 - IC67181 - EVENT DESTINATIONS IN WMQ QUEUE DOES NOT CONTAIN RFH2 HDR
P8012100 - PM10090 - ABENDS0C1 OCCURS WHEN CALLING FXXZCBL FROM COBOL TRANSLATION
---- Special Considerations --------------------
With the correction required to resolve P8012069, WDI now requires that Application Data match the
appropriate Data Format Record definition, especially when 'no delimiters' is specified on the Data Format
General Tab. The UP0021 message will identify data that is not the proper length and will issue a
return code of 8.
With the correction implemented with P8012084, Zoned-decimal format should be fully functional. In
addition, the packed-decimal format will now support a paradigm which expects data in ASCII format
and will produce PD output in ASCII format. With the support of Zoned-decimal fields and packed-decimal fields
in the conversion routines for open systems, it was necessary to convert input data from ASCII to EBCDIC and
output data from EBCDIC to ASCII. There are certain assumptions which are taken and specific requirements that
must be met for the conversions to be correct.
1) it is assumed that when PD data is desired on an open system that it will be transfered to a z/OS platform
for consumption, thus the contents of the PD output field will be converted to ASCII for the expected FTP
to a z/OS Host.
2) there are a number of techniques for performing the FTP
a) the IBM Personal Communications, PCOMM, software product,
b) Windows FTP Server, or,
c) 3rd party FTP software.
These SW packages use translation tables for conversion. They must match the tables used by the conversion
routines. The conversion routines used by Send and Receive translation differ from those used in Data
Transform mapping, but the values in ASCII / EBCDIC conversions are the same as the IBM Default Translation
Tables used by IBM Personal Communications emulator (PCOMM). FTP from and to a z/OS host was tested with that
Software. If other products are usedm they must use a custom table with the same values in the PCOMM IBM
Default Translation tables for upload (ASCII to EBCDIC) and download (EBCDIC to ASCII), else PD conversions
may not work correctly.
3) WDI uses "text" opens for files except when ONEMSG(Y) is specified. In this case the a "binary" open is
performed. It is thought that packed-decimal fields may cause unexpected results if not opened in binary,
because some bytes in a PD field may represent a control character, such as NL or EOD, or CR.
4) The local code page of the machines will have an effect on the FTP and the conversions. We have tested going
from code page 1047 (host standard) to 1252 (Windows standard) using a local code page of 819 - Latin-1.
**************************************************************
*** END OF WebSphere Data Interchange V3.3 SFP4 README.TXT ***
**************************************************************
****************************************************************
*** START OF WebSphere Data Interchange V3.3 SFP3 README.TXT ***
****************************************************************
December 2009 - SPF3
The following problems have been resolved on this SFP:
P8010319 - PK89526 - FF0111 issued with RC 8,400 to WDIOUT NETPROF
P8011894 - PK93078 - Transform ISA control numbers mismatch in PRTFILE
P8012016 - PK85776 - Forward translation table data missing from build control file
P8012018 - PK87079 - Incorrect segment count (SE01)
P8012019 - PK87213 - Signal 11 and FF0205 with stacked DT Perform Statements
P8012029 - PK88600 - UK25207 in error - missing JCLIN entry for FXXTSRSS
P8012033 - PK92009 - unable to read WMQ RFH2 <USR>
P8012035 - PK92279 - DF To EDI DT processing not writing input to EXCEPTION file
P8012036 - PK99695 - SETPROPERTY May cause MB0001 and MB0002 Processing Large EDI Input
P8012039 - PK94031 - Not generating MQMD V1headers when using EDIMQSR
P8012041 - PK94219 - Unable to Reconstruct Transaction
P8012042 - PK94651 - SEGMENTED(Y) keyword not working on Perform Print Transaction
P8012043 - PK96002 - PTF in error - Send Mapping fails under CICS
P8011946 - PK97866 - Unable to read MQ Profile
P8012048 - PK97809 - Abend during DF to DF translation with comma delimited input file
P8012049 - PM01005 - CICS DT Not Handling NL Characters Correctly
P8012052 - IC64243 - DT not reporting errors when an DF input processed under SYNTAX(E)
P8012053 - PM00219 - DT to Comma separated data format writes extra decimal point
P8012055 - PM01016 - CICS - Erroneous UT0028 Messages with XML DT Input
P8012057 - PM01107 - Sample EDISDB2 missing documentation
**************************************************************
*** END OF WebSphere Data Interchange V3.3 SFP3 README.TXT ***
**************************************************************
****************************************************************
*** START OF WebSphere Data Interchange V3.3 SFP2 README.TXT ***
****************************************************************
April 2008 - SPF2
The following problems have been resolved on this SPF:
P8011887 - PK65876 - TR0204 Message text change
P8011892 - PK63956 - Batch import of usages fails
P8011893 - PK64347 - Reconstruct returns all transactions instead of selected ones
P8011895 - PK64573 - Abend - Batch import of standard data
P8011896 - PK64581 - Signal 11 on Data Format to XML Data Transformation
P8011897 - PK68684 - Erroneous EL0015 message when Perform Remove Log Entries
P8011898 - PK64710 - Failure in Batch export - no error message received
P8011899 - PK65089 - EDIFFUT not processing data in CICS
P8011902 - IC56434 - IC55289 not fixed in SPF1
P8011912 - PK66174 - Signal 11 - FF0205 on EDI to DF after TR0051
P8011923 - PK71486 - Export of specific DF results in huge Print and EIFILE
P8011928 - PK67158 - PTF UK24652 in error - RU0001 - No Active Rule Found
P8011932 - IC56986 - WDI not populating RFH2 properly in output
P8011933 - PK67944 - SQL Code 991 when using EDIFFUT
P8011935 - PK68322 - Duplicate Interchange Control Numbers
P8011946 - PK70069 - ABEND when variable length exceeds 64 bytes
P8011947 - PK70735 - HOT-DI Data Transformation holding exculsive lock on EDIPROF
P8011951 - IC57743 - FF0608 issued when using &SET
P8011955 - PK71888 - UNB Date sporatically populated
P8011957 - PK72126 - Incorrect Last Update date after batch import
P8011962 - PK72826 - Abend in EDIIOS when SEDILMD1 is in link-list
P8011966 - PK73861 - SETPROPERTY not overriding MHD0201 element value
P8011969 - PK74633 - PS0301 errors in Event Log
P8011970 - PK74716 - Incorrect Close Cursor in RATR routine
P8011971 - PK74714 - Transaction Store not updated in CICS
P8011977 - IC58864 - FTX0401 Value not output
P8011987 - PK75938 - EI0012 Database error during export of map usages
P8011988 - PK76672 - ABEND - Data Transformation parser using sender/receiver id
P8011989 - PK76368 - SQLCODE 100 during job EDIJMLOD
P8011991 - IC59394 - Memory leak in advanced adapter
P8011992 - PK79950 - ABEND in EDIEAS during insert of Event Log entries
P8011994 - PK79756 - Function values incorrect in command export errors
P8011995 - PK79950 - ABEND - UK43320 in Error - EDIIOS
P8011998 - PK83461 - ABEND - in program EDIEDADF
P8012000 - PK82435 - FF0205 Error performing DF TO EDI Translation
P8012004 - PK83789 - SQL0530N error importing map file
P8012008 - PK84103 - Program corruption with Functional Acknowledgements on Windows
P8012009 - PK84146 - Getting EL0015 Erroneously
P8012011 - PK85251 - Server import loses outbound validation
P8012012 - PK85246 - Batch import sets incorrect import date
P8012013 - PK85796 - Perform Reconstruct gives warning
P8012015 - PK85516 - Control Numbers are set differently
**************************************************************
*** END OF WebSphere Data Interchange V3.3 SFP2 README.TXT ***
**************************************************************
****************************************************************
*** START OF WebSphere Data Interchange V3.3 SFP1 README.TXT ***
****************************************************************
April 2008 - SPF1
The following problems have been resolved on this SPF:
P8009366 - PK44344 - input file does not exist incorrectly reported
P8009530 - PK49084 - FIXEDFILEID keyword not working with delayed enveloping
P8009644 - PK50214 - Add TOTAL COUNT to PRINTFILE for REMOVE TRANSACTIONS
P8009651 - PK52054 - PRINT EVENT LOG - Gets error
P8010247 - PK45508 - Abend with UCS input and TA1 acknowledgment using default FA enveloping
P8010567 - PK44419 - Invalid EncodeTarget keyword causes abend for data format output
P8010695 - PK47880 - FF0515 Msg for failed import, but no other error messages
P8010697 - PK43307 - Message EI0048 incorrectly shows Data Format category when exporting a non-existent
standard
P8010759 - PK50211 - EPURDATE with no To keyword doesn't find Purge date
P8010773 - PK42001 - ABEND TP Profile Data Extract INTID
P8010823 - IC50173 - WDI does not allow transaction to be enveloped when orphan transaction exists in table
EDITSAU with same Batch ID number
P8011252 - PK52089 - Fixed format import/export record mismatch between client and host
P8011399 - PK44368 - CICS Receive and Process does not work from Continuous Receive profile
P8011564 - IC51150 - Getting EV0019 -'NO TRADING PARTNER FOUND' using Business ID's
P8011574 - PK43285 - Add SMF 89 registration and deregistration support to allow subcapacity pricing in
batch Z/OS and CICS
P8011599 - PK40482 - UNT Control number is different than UNH with multiple messages in an interchange using
Version 4
P8011629 - PK45170 - Allow the config database of WDI Client to be defined in a z/OS database
P8011634 - PK41988 - The new envelope profile fields (ST03, new UNB/UNG/UNH fields) are not included on
import/export
P8011664 - PK42595 - ABEND Mixing DT and SEND/RECEIVE Performs in same job step
P8011682 - PK40484 - CICS SOURCEENCODE keyword does not work for XML input
P8011715 - PK40464 - SIGNAL 11 when TRADACOM EDI TO ADF
P8011758 - PK44005 - unexpected errors during Perform Transform
P8011760 - IC51706 - Message format not correct in output when using SETPROPERTY ROOT.MQMD.FORMAT
P8011775 - PK40483 - ABEND in SAP STATUS EXTRACT
P8011779 - PK40281 - WDI does not generate the RSGRSG message for UNTDI envelopes
P8011782 - PK40488 - extra UT0033 message logged
P8011785 - PK40498 - unexpected memory growth
P8011786 - PK40493 - Using the mapping command for ErrorContext without a previous FAError command in a
validation map may cause abends
P8011789 - PK41541 - UP0025 with data format output and record name length 30
P8011792 - IC52032 - SETPROPERTY and E_PROFILE will not override values in UNH
P8011793 - PK43225 - FF0205 and ABEND in EDIM
P8011794 - PK42939 - WDI unable to parse EDI msgs when single ISA with multiple GS's that contain 997'S
P8011795 - PK44004 - FF0209 error message when processing EDI TO ADF and ADF TO EDI jobs concurrently
P8011796 - PK44006 - ADF TO EDI DT processing drops last segment terminator when wrapping to next record
P8011798 - IC52163 - NULL Pointer exception using GETINSERTDATA method
P8011799 - IC52165 - Added getDirection() and setDirection() methods for the XMLHandler class
P8011808 - IC52346 - XML-EDI Translation ABEND in EDIUPXML when XMLSPLIT(Y) KEYWORD used in large XML
input file
P8011812 - PK43235 - Bind error with DB2 V8 in new function mode
P8011821 - IC52473 - When transforming XML to EDI and doing XML split, white spaces are being
removed from the data
P8011822 - PK47162 - ONEMSG(Y) not supported on TRANSLATE TO APPLICATION type commands
P8011826 - PK44438 - STEP004 of EDIJEXPD jobfails with EI0025 when importing X12 standards from SEDISTD1
P8011827 - PK44180 - EV0017 error occurs if envelope type is blank on Rule or says use default
P8011828 - PK44363 - TR0840 error pointing to U envelope profile when send map uses UN/TDI and default envelope
P8011829 - PK50191 - memory leak in DT processing
P8011831 - PK44429 - JCL samples need SDSNEXIT for DB2 V8
P8011833 - Pk45168 - EDIDSATTR entries not deleted by Remove
P8011835 - PK45045 - ERRORCONTEXT without FAERROR may cause ABEND
P8011836 - PK45047 - UNTDI inbound data containing asteriskis incorrectly processed
P8011838 - PK45048 - propogate MQ headers to multi output
P8011839 - PK51936 - Infinite loop using MQSERIES with RECVFILE
P8011841 - PK50194 - batch export of map fails to include comments
P8011842 - PK50198 - CICS ABEND when SENDERID is spaces in ISA06 and ISA05 is ZZ
P8011843 - PK49425 - CICS - ASRA ABEND during FA processing
P8011844 - PK48535 - EDIHLI ABEND doing Transaction Store processing
P8011845 - PK53403 - TR0001 not issued whn mandatory element is missing in output
P8011849 - IC53415 - Validation node reports incorrect TR0051 errors
P8011852 - PK51967 - EDI TO ADF DT map unable to write trailer records when using
IF (STRCOMP (LAST_MESSAGE, 'Y')=0)
P8011853 - IC53520 - Transaction control number lock can become deadlocked when multiple translators
are in use
P8011855 - PK51642 - problems with Send translation that does not specify the envelope type on the send usage
P8011858 - PK54162 - EDI-ADF DT map gives incorrect TR0002 and TR0050 Validation errors
P8011859 - IC53871 - SIGNAL 11 performing EDI TO XML Ttransaction
P8011866 - PK56195 - Running migration job EDIJEXPD encounters an infinite loop when exporting data format
P8011867 - PK57839 - Add date and time to the XML print file and destinations
P8011869 - IC54450 - Signal 11 when enveloping a message from the transaction store
P8011870 - PK57705 - STEP006 of EDIJEXPD job nags when migrating from 3.1 to 3.3
P8011871 - IC55267 - CREATEDB.DDL results in SQL5153N warning
P8011872 - PK59488 - extraneous colons in XML output of transform
P8011875 - IC55285 - error loading the "edimqs" shared object module
P8011876 - IC55270 - UP0021 error occurs during translation
p8011877 - PK64018 - for XML to X12, the DocInfo for the input XML document does not
contain values for: Sndid, Sndqual, Rcvid and Rcvqual
P8011878 - PK61640 - abend that is related to improper memory access
p8011883 - PK61820 - errors TR0841 and TR0830 occur translating ADF to EDI after
applying PTF UK19151
P8011884 - PK62388 - output missing for X12 mandatory B2A segment
p8011889 - PK64516 - an import of Client generated EIFILE containing XML DTDs gets error, FM0100
p8011890 - PK64695 - SAP Acknowledgment Status gets corrupted during update
**************************************************************
*** END OF WebSphere Data Interchange V3.3 SFP1 README.TXT ***
**************************************************************
*** Uninstall instructions for WebSphere Data Interchange V3.3
To uninstall on AIX:
1) Change directory to the _uninst directory
2) Issue the command:
uninstall.bin
To uninstall on Windows:
1) Use the Windows "Add/Remove Programs" dialog on the control panel
to uninstall the program.
*** Acknowledgements ***
This product includes software developed by the
Apache Software Foundation (http://www.apache.org/).
Copyright (c) 1999-2000 The Apache Software Foundation. All rights reserved.
This software is distributed under Apache Software License, Version 1.1.
A copy of this license (LICENSE.TXT) is included in the same directory as
this file.
This product also includes International Components for Unicode.
Copyright (c) 1995-2001 International Business Machines Corporation and others
All rights reserved. This is distributed under the X License (XLicense.html),
which is included in the same directory as this file.
*********************************************************
*** END OF WebSphere Data Interchange V3.3 README.TXT ***
*********************************************************