WebSphere Data Interchange Client v3.2.1 README.TXT
--------------------------------------------------------------
Client Fix Pack Interdependencies with Server Maintenance:
For proper Client operation, Server database changes are required
in support of certain Client feature enhancements. As a result,
please ensure the following Server maintenance is applied before
applying this fix pack:
For distributed platform users, CSD22 should be applied.
For z/OS users, the following PTF list should be applied:
- DT TO CHARACTER TYPE ADF FIELD IN CSV FORM - FP18 + CSD22 or PK14754
- DB changes for unicode enhancements - FP17 + CSD21 or PTF UK09539
- ENHANCEMENT FOR SOURCE/TARGET CODEPAGE - FP16 + PTF UK06667
- DB changes have occured - FP15 + CSD19 or PTF UK05042
- CICS Continuous Receive for TRANSFORM - FP13 + CSD16 or PTF UQ95969
- XML Split user interface - FP11 + CSD14 or PTF UQ91317
- XML Schema Support - FP8 + CSD9 or PTF UQ83083
While not essential for proper Client operation, to take full
advantage of other feature enhancements made in Server code, you
must have the corresponding Server maintenance installed.
Note: FP represents Client Fix Pack mainteance level, CSD is for
distributed platform Server users, and PTF is for z/OS Server users.
Fix Packs are cumulative, so it is not necessary to install each
one individually to get to the latest maintenance level.
---------------------------------------------------------------
**************************************************************
*** Summary of new enhancements to date:**********************
**************************************************************
- ALLOW TEXT DELIMITER AND QUALIFIER IN ADFS - FP18 + CSD22 or PTF UK11810
- Unicode enhancements - FP17 + CSD21 or PTF UK09539
- Business IDs for DT Maps - FP17 + CSD19 or PTFs UK05042, UK06769
- Transaction Store Functional Area Renovation - FP17
- Updated the Event Log Viewer - FP17
- The Query List window has been enhanced - FP17
- Export / Import of Queries - FP17
- Additional shared configuration database support - FP17
- Additional lan based install support - FP17
- General Client usability improvements - FP16
- ALLOW ACTIVATION OF SELECTED OBJECTS - FP16
- Improve DB2 Performance - FP16 + CSD20 or PTF UK06574
- Additional Platform Support: DB2 8.2 - FP15
- ADDED RECORD NUMBER ON IMPORT MESSAGES - FP15
- MENU/TOOLBAR ARCHITECTURE ENHANCEMENT - FP15
- IMPLEMENT "YES TO ALL" IN IMPORT - FP14
- ADD AN "APPLY TO ALL" OPTION ON THE IMPORT'S USAGE OPTION
DIALOG. - FP14
- ONLY ASK FOR ASSOC OBJECTS ONCE ON EXPORT TO SYSTEM - FP14
- SUPPORT SETELEMENTATTRIBUTE COMMAND - FP14 + CSD18
- CLIENT - IMPLEMENT "VIEW" WITHIN CLIENT - FP14
- DT, Validation and FA Map reports in HTML format - FP13
- CICS Continuous Receive for TRANSFORM - FP13 + CSD16 or PTF UQ95969
- Panel update to 3.2.1 - FP12 + CSD15 or PTF UQ92717
- XML Split user interface - FP11 + CSD14 or PTF UQ91317
- Export usages as an assoc object of TP - CSD12 or PTF UQ87581
- Optional Records - CSD11 or PTF UQ85350
- Database changes made in CSD10 needed with Fix Pack 8
- XML Schema Support - FP8 + CSD9 or PTF UQ83083
- TA1 Support for DT mapping - CSD8 or PTF UQ82191
- C&D records support - FP6 + CSD7 or PTF UQ79410 & UQ80034
- RFH2 parser - CSD6 or PTF UQ78539
- SAP Status support - CSD5 or PTF UQ77622
- EDI Transaction Store Support for TRANSFORM - CSD3 or PTF UQ75669
---------------------------------------------------------------
June 2006
WebSphere Data Interchange Client v3.2.1 FIX PACK 19 README.TXT
Included in this section are:
1. List of problems fixed added in Fix Pack 19
2. Server Dependencies
---------------------------------------------------------------
1. Problems fixed in Fix Pack 19 include:
P8010710 - PK21408
Modify the Standard Transaction short report to include the
Table Number, Loop IDs, Loop Repeat, Position Numbers,
Required Designation, and Segment Max Use.
P8010753 - IC49380
CLIENT ABENDS WHEN ATTEMPTING TO OPEN A SPECIFIC DTD/SCHEMA
One of the elements in the DTD had nearly 300 child elements
P8010674 - PK19158
S/R MAPPING NOT ALLOWING DUPLICATE LEVEL, PARENT MAPPING WITH
DIFFERENT STRUCTURES
P8010749 - PK24766
ELEMENT NUMBERS MISSING UNDER COMPOSITE ELEMENTS WHEN USING
PRINT PREVIEW
P8010776 - IC49529
UNABLE TO EXPORT INTERNAL TRADING PARTNER ID DEFINED
IN XML SCHEMA
------------------------------------------------------------------------
2. Server Dependencies
There are no server dependencies with this fix pack.
*************************************************************************
*End of WebSphere Data Interchange Client v3.2.1 FIX PACK 19 README.TXT**
*************************************************************************
February 2006
WebSphere Data Interchange Client v3.2.1 FIX PACK 18 README.TXT
Included in this section are:
1. List of problems fixed added in Fix Pack 18
2. Server Dependencies
---------------------------------------------------------------
1. Problems fixed in Fix Pack 18 include:
P8010654 - see also PK14754
ALLOW TEXT DELIMITER AND QUALIFIER IN ADFS
Data Formats have been worked to support more common delimited
field record formatting. A variety of field delimiters can now
be specified. The qualifier used to enclose text is also more
flexible. Refer to the help topic for the Data Format Editor's
General tab page for additional information.
P8010651 - PK17522
13002 CRYSTAL REPORTS SQL ERROR PREVIEWING SHORT REPORT
P8010670 - PK20354
ABEND IMPORTING DTD OR SCHEMA USED IN MAP
P8010663 - PK18405
DOCUMENTATION IN HELP FOR RESOLVIMG CHARGE VALUE WITH IEBASE
------------------------------------------------------------------------
2. Server Dependencies
P8010622 - PK14754
DATA TRANSFORMATION TO CHARACTER TYPE ADF FIELD IN CSV FORMAT
DOES NOT ESCAPE QUOTATION MARKS.
You will need to apply either the PTF on your host system OR CSD 22
on your distributed system for full functionality of this fix pack.
*************************************************************************
*End of WebSphere Data Interchange Client v3.2.1 FIX PACK 18 README.TXT**
*************************************************************************
December 2005
WebSphere Data Interchange Client v3.2.1 FIX PACK 17 README.TXT
Included in this section are:
1. List of problems fixed added in Fix Pack 17
2. Enhancements
3. Server Dependencies
---------------------------------------------------------------
1. Problems fixed in Fix Pack 17 include:
P8010581
Correct issue where the Status window would not be available
when preferences indicate that messages are not to be purged
automatically.
P8010582
USE RIGHT CLICK POPUP ON OVERVIEW TO SET RAW DATA
P8010574
Corrected the issue that occurred while imporint code lists with
a transaction from the X12V3R2 standard posted on the website.
P8010475 - IC46336
WHEN PERFORMING AN QUERY, IF WRONG DATE FORMAT IS USED NO ERROR
IS REPORTED.
P8010594 - IC47548
CLIENT - TRANSACTION STORE INTERCHANGES QUERY GIVES NO RESULTS
WITH E IN FUNCTIONAL ACKNOWLEDGEMENT STATUS CODE, WHEN EXPECTED.
P8010621 - PK14741
WDICLIENT COMPILE REQUIRED REMAINS "NO" ON IMPORTED XML SCHEMA,
SHOULD BE "YES".
P8010569
STANDARD CONTROL STRING CONTAINS INCORRECT LOOP IDS
P8010644 - IC48110
CLIENT CRASHES WHEN MODIFYING CTA SEGMENT
P8010631 - PK15280
WDI 3.2.1 CLIENT CRASHES DURING EDITING AN ADF- EDIFACT
(EDI96A-INVOIC) SEND MAP
P8010525
SENDER/RECEIVER FIELDS INCORRECT IF XML NAMESPACE
------------------------------------------------------------------------
2. Ehancements
P8010586
Updated the Event Log Viewer. Fields were resized and
repositioned. A user can tab into the read only fields
on the viewer. The values in the read only fields can be
selected and copied to the clipboard.
P8010602
The Map Rules, Send Map Usages and Receive Map Usages have been
updated to eliminate 'cryptic' codes. Cryptic codes have been
replaced with descriptive values. This affects list windows, the
Query Editor dialog and the related editors. The editors have also
had some layout changes to accommodate the descriptive values.
P8010607 and P8010580
WDI Client has been updated to more easily support a LAN based
install and a shared configuration database. Please review the
technical documents available for these subjects on the website
for additional information.
P8010610
The Continuous Receive Profile Editor has been updated to replace
symbolic codes with descriptive terms, enlarge the length of some
fields, update terminology to agree with the remainder of the Client
application, and update the related help as needed.
P8010619
The Query List window has been enhanced. Additional information
and functionality is now provided by the window. Export of Queries
is now supported from the Query List window. The import process has
been updated to support import of Queries.
The Transaction Store Functional Area has undergone a major renovation.
Be aware of the following:
- "Interchanges" has been renamed to "Enveloped Transactions".
This object has always displayed transactions in the Transaction Store
that have been enveloped.
- Additional fields have been made available in the "Transactions" object.
- Additional fields have been made available in the "Enveloped
Interchanges" object.
- Additional fields have been made available in the "Groups" object.
- The viewers for "Transactions" and "Enveloped Transactions" have been
updated to display more of the information associate with a transaction
or enveloped transaction.
- The default Queries for "Transactions", "Enveloped Transactions", and
"Groups" have been updated in an attempt to make them more useful.
- A number of fields have had minor terminology changes to make them
consistent and easier to understand.
- The "Groups" object now contains a viewer and supports a report.
- A new object called "Interchanges" has been added. This object
displays only the interchanges contained in the Transaction Store.
- Symbolic codes have been replaced with descriptive terms. The
symbolic codes can still be used as selection criteria when a Query
is performed, or the descriptive term can be used as the selection
criteria instead.
- The term "Direction" has been renamed "Source or Target". Since the
introduction of Data Transformation Maps, the field has indicated
whether the document in the Transaction Store was a "source document"
input to a translation or is a "target document" created by a translation.
Translations using Send Maps place "target documents" into the
Transaction Store. Translations using "Receive Maps" place "source
documents" into the Transaction Store. Translations using Data
Transformation Maps can place "source documents", "target documents",
or both into the Transaction Store during a translation.
- The "Image" tab page contained in the "Transactions" viewer has been
updated to support the "Find" function.
- The "Image" tab page contained in the "Transactions" viewer also has
been updated to support large images and to improve performance. This
is accomplished by displaying only a portion of an image at first.
How much of the image is displayed depends on a value set by the user
on the "Image" tab page. The "Image" tab page provides buttons to page
through the portions of the image.
- The "Image" tab page now appears in the "Enveloped Transaction" viewer
in addition to the "Transactions" viewer.
- It may be desirable to "reset" each of your Transaction Store Queries
once using the list window properties dialog when they are displayed in
a transaction store.
- Transaction Store Queries you have created may have default labels used
in selection criteria that no longer are consistent with the fields they
represent. These can be corrected quickly using the Query Editor.
------------------------------------------------------------------------
3. Server Dependencies
You will need to apply either the PTF on your host system OR CSD 21
on your distributed system for full functionality of this fix pack.
*************************************************************************
*End of WebSphere Data Interchange Client v3.2.1 FIX PACK 17 README.TXT**
*************************************************************************
September 2005
WebSphere Data Interchange Client v3.2.1 FIX PACK 16 README.TXT
Included in this section are:
1. List of problems fixed added in Fix Pack 16
2. Enhancements
---------------------------------------------------------------
Problems fixed in Fix Pack 16 include:
P8010530
Updated the list window to correct intermittent repainting issues.
P8010539
SCHEMA/DTD ERRORS IF RECURSIVE ELEMENT REPEATS IN SEQUENCE
P8010537 - PK09392
CLIENT - FILTERING BY USERID NOT WORKING WHEN VIEWING EVENT LOGS
P8010540
Corrected an issue that occurred in the Mapping Command window
when a recursive element contained itself as a child. In this
situation, the child recursive element was not including itself
as one of its child element.
P8010355 - IC44595
OUTPUT FROM HL5 LOOPS INCORRECT AFTER TRANSLATION FROM ADF TO
EDI ON W2K
*** Important note ***
Send/receive maps which are run on a Windows platform should
be recompiled with the new Client Fixpack to verify that they
are compiled correctly.
P8010554
Added new Data Transformation Map properties to obtain the names
of the sending and receiving trading partner profiles. Also added
Data Transformation map properties to access the values in the
user fields of the sending and receiving trading partner profile
properties. The "EncodeTarget" property has been extended to
apply to EDI Standard documents.
P8010470 - PK06204
CLIENT RECEIVES ERROR "10538", WHEN TRYING TO CREATE CODE LIST
FROM COBOL COPYBOOK USING 88'S CHECK BOX, TO CONVERT CODE LIST
P8010473 - PK06224
CLIENT 11052 - DATABASE ERROR ADDING A ROW IN TABLE
'DI32.EDIADFRECORD'. SQL0530N
P8010454
Corrected the install issue that prevented some users from being
able to use the print preview's button to export the print report
to other formats.
P8010499
PRINT (PREVIEW) FORWARD REVERSE TRANSTABLE COMMENTS
P8010120
RULES/USAGE ICON ACTIVE ENVELOPE PROFILE EDITOR
---------------------------------------------------------------
Enhancements:
P8010545 - Customer submitted requirement (DHIN-69NMW4)
General Client usability improvements
Update the Status Window so a user can select and copy information
from the dialog. This helps the user to perform easier problem
determination by making the information more readily available and
easy to preserve. The information is also easier to pass to Customer
Support.
* Accessibility enhancements
* Allows data to be selected from the Status window and copied to
the clipboard, so it can then be copied to other applications.
* The Status window can be resized and repositioned. It will
restores its last size and positioned each time it is opened.
* Data no longer is cleared each time the Status window is opened
- it will accumulate up to a certain number of lines.
* The user can clear the Status window by using a "clear" option
in a right click popup menu.
* The user can open and hide the Status window at any time using
a menu item under the "View" menu.
* Some messages written to the Status window are reformatted to make
the Status window easier to read.
* An "Always on Top" feature has been added.
P8010561 - Customer submitted requirement (LCLK-6AXQ27)
Allow the user to indicate that all selected objects should
be activated. Allow user to indicate that all selected
objects should be deactivated.
The existing "toggle activation" function has been
enhanced so that it still does "toggle", but also can
be used to force all selected objects to be "active"
or "inactive" regardless of their current states.
The function now applies to Continuous Receive Profiles and CICS
Performance Profiles in addition to Map Rules, Send Map Usages,
and Receive Map Usages.
*************************************************************************
*End of WebSphere Data Interchange Client v3.2.1 FIX PACK 16 README.TXT**
*************************************************************************
July 2005
WebSphere Data Interchange Client v3.2.1 FIX PACK 15 README.TXT
Included in this section are:
1. List of problems fixed added in Fix Pack 15
2. Help Text Updates
3. Enhancements
4. Server Dependencies
5. Additional Platform Support
---------------------------------------------------------------
Problems fixed in Fix Pack 15 include:
P8010489 - IC46466
CLIENT FIND QUERY BY MAP TYPE RETURNS ALL MAP TYPES, AND IF ALL
COLUNMS ARE UNSELECTED THEN SELECTED, ALL COLUMNS SHOW MAP NAME
Corrected query logic so that FIND for a specific map type will
only show results for that specific map type.
P8010419 - PK03046
WDI CLIENT 3.2 FP13 DISPLAY THE INCORRECT SEGMENT NUMBER AT EDI
DIC SEGMENTS SCREEN WHEN SCROLLBAR AND 'PAGE UP/ DOWN' USED
Updated code to make use of the page up and page down keys more
predictable in list windows.
P8010478 - PK09992
Corrected the issue in the Data Element editor where the
selected code list was reset to the first item in the code list
dropdown control when the user opened the dropdown control.
P8010480 - IC46353
WDI CLIENT RETURNS ERROR WHEN NAMESPACED SCHEMA REFERS TO AN
ELEMENT IN THE NON-NAMESPACED SCHEMA
P8010493 - PK09994
FIND CORRECT STRING IN COMBOBOX/GPF/DEBUG
P8010461 - IC46100
IMPORTING SEND OR RECEIVE "RULES AND USAGES" WDI DEACTIVATES ALL
BUT LAST USAGE WHEN "FORCE ALL IMPORTED USAGES TO BE ACTIVE"
Updated the 'active usage' check for Send Map Usages.
P8010412 - IC45447
AFTER UPGRADING TO FIXPACK13, AN ODBC ERROR OCCURS WHEN
PERFORMING AN QUERY
P8010294 - IC43599
CLIENT - SQL0206N "EDIENU32.EDIVTSIS.STDTRNID ODBC ERROR WHEN
DOING A FILE OPEN REPORT LIST
P8010469 - PK06148
CLIENT - FREEZES WHEN CLICKING OK TO SAVE &ST02
ON MAPPING DATA ELEMENT EDITOR SCREEN.
P8010474 - PK06343
WDICLIENT ADF DOCUMENT DESTINATION TYPE PULL DOWN SELECTION
INCORRECTLY DEFINES CICS PROGRAM AND CICS TRANSACTION SETTINGS.
P8010524 - PK08822
CLIENT - INFORMATION DESCRIBING SETUP ICON AT BOTTOM OF SCREEN
IS SPELLED INCORRECTLY, 'FUNCTIONAL' IS MISSING THE 'L'
P8010529 - PK09998
CLIENT-MAP PROBLEMS FOR XML ELTS WITH SAME LOCAL NAME
P8010430 - PK03947
CLIENT COMPILE REQUIRED NO ON IMPORTED ADF,SHOULD BE YEs
FOR SEND / RECEIVE MAPS.
P8010486 - PK06862
EDIT TP CONTROL NUMBERS DELETES ALL ROWS WHEN ATTEMPTING TO
DELETE CERTAIN ROWS AFTER DOING A BATCH IMPORT OF TP PROFILE
------------------------------------------------------------------------
Help Text Updates
P8010098
PROBLEMS ASSOCIATED WITH MAILBOX PROFILE & HELPTEXT
1) Need to update the "title" of the helptext for the Remote
Status Program field to say "Remote Status Program field"
without the Pgm abbreviation.
2) Message User Class field helptext has a typo:
"This is because all documents received in a receive request
will be treated the similarly.".
3) The "title" of the helptext for the "Acknowledgments"
field is shown as "Acknowledgment" field.
4) The Mailbox Profile - Storage Format field has:
A L O as valid values for CICS
and
C L N as valid values for MVS
but the dropdown list shows
C L N U
A and O should be added.
------------------------------------------------------------------------
Ehancements
P8010494 - PK09995
NEED RECORD NUMBER ON IMPORT MESSAGES.
P8010479 - PK09997
MENU/TOOLBAR ARCHITECTURE ENHANCEMENT
------------------------------------------------------------------------
Server Dependencies
PTF UK05042 or MP CSD19
You will need to apply either the PTF on your host system OR the CSD
on your distributed system for full functionality of this fix pack.
------------------------------------------------------------------------
Additional Platform Support
DB2 8.2 Support
WebSphere Data Interchange 3.2 will run without problem DB2 8.2
*************************************************************************
*End of WebSphere Data Interchange Client v3.2.1 FIX PACK 15 README.TXT**
*************************************************************************
---------------------------------------------------------------
WebSphere Data Interchange Client v3.2.1 FIX PACK 14 README.TXT
Included in this section are:
1. List of problems fixed added in Fix Pack 14
2. Enhancements
3. Server Dependencies
---------------------------------------------------------------
Problems fixed in Fix Pack 14 include:
P8010377 - PK07238
IMPORT FILES WITH USAGES AS ASSOC. OBJECTS
Send usages, Receive usages, Map Rules and MCD profiles will
appear in the import window with multi-part names to help uniquely
identify each object. Previously these only appeared with a single
value for the name in the import window and thus often objects
could not be uniquely identified.
P8010369 - PK00938
WDI 3.2 10512 - CONTACT NAME FIELD IS REQUIRED WHEN CHOOSING
CONTACT FROM TRADING PARTNER WHEN CONTACT DUPLICATES ARE ALLOWED
P8010379 - PK07241
CLIENT - XML NAMESPACE - URI SHOWS MANDATORY BUT ISN'T
P8010396 - PK01905
WDI 3.2 CLIENT ERROR SQL0803N SQL -803 WHILE IMPORTING SCHEMA
P8010384 - PK07244
CLIENT - RESTRICT FUNCTION BY DATABASE TYPE
P8010399 - PK01981
CLIENT 10534 ERROR -EDIT/SAVE OF TRADING PARTNER PROFILE
FROM VALID CHARACTER "/" SLASH IN NICKNAME FIELD
P8010405 - PK07264
CLIENT - RESTRICT ATTR LISTS, SEQ NODES, CHOICE NODES
XML attribute list nodes, XML sequence nodes and XML choice nodes
can no longer be dragged in a map. In addition, compound elements
can no longer be dropped on these node types. This change was made
because these node types are not valid in mapping commands.
P8010410 - PK07265
CLIENT - CONTROL STRING COMPILE ABEND WITH "!!" IN EXPRESSION
P8010413 - PK02740
A GPF related to using the page up and page down keys under certain
circumstances in the grid controls used in the Data Format Editors
and Standards Editors has been fixed.
P8010260 - PQ95612
WHEN DOING PRINT PREVIEW OF A WDI 3.2 MAP THE APPLICATION FIELD
NAME IS SOMETIMES SHOWN AS PART OF THE WRONG RECORD NAME
P8010373 - PK00990
WDI 3.2 SEND/RECEIVE MAP REPORT FIELDS NOT BEING PRINTED
P8010439 - PK07286
CLIENT - XML SCHEMA NILLABLE ATTRIBUTE NOT SUPPORTED
The Client was updated to check if an element is nillable.
If the element is nillable, then an xsi:nil attribute is added
for the elements, in addition to any other elements that may
be declared. The user can map a value to this attribute
if they want to.
P8010458 - PK05408
WDI CLIENT INCORRECTLY OUTPUTS TRANSFORM, PROCESS, AND RCVPROC
TAGS AS "Y" EVEN THOUGH THE DATABASE CONTAINS BLANKS
------------------------------------------------------------------------
Enhancements
P8010429 - PK07267
CLIENT - IMPLEMENT "VIEW" WITHIN CLIENT
"View" works exactly like "open" except that the editors and related
dialogs are opened in 'read-only' mode. The "View" function is available
on the File Menu beneath the Open function.
The preferences dialog has been updated to allow the user to indicate
whether “Open” or “View” will be the default when the current “Open”
button is pressed on the List Window toolbar. This option will also
affect the action that occurs when the user double clicks on an object
that normally would produce an “Open” action. This preference will allow
users that only have read access to the database to work efficiently without
the added steps of going to the File menu. The tooltip that displays above
the toolbar will reflect the user’s preference.
The following additional related changes have been made:
· Any editor that contains an "Edit" button used to open a referenced
object (these are located in the data format and standards editors)
will change the label on the button to "View" when the editor is opened
as "View".
· Any editor that contains a tree or list that provides an "open" function
in a popup menu will now also provide a "View" function.
· Ctrl+V is implemented as a hotkey to invoke the "View" function.
· "View" and "Open" perform the same function for the Message Log,
Transaction Store, and Event Log. These objects have always been
“read-only”.
----------------------------------------------------------
P8010438 - PK07277
CLIENT - IMPLEMENT "YES TO ALL" IN IMPORT and ADD AN
"APPLY TO ALL" OPTION ON THE IMPORT'S USAGE OPTION DIALOG.
Changed the import replace dialog to have "yes to all"
and "no" buttons. "yes to all" will replace all existing
objects without displaying the replace dialog again. "no"
will not replace the existing object, the current import
object will be skipped, and import will continue.
Changed the import usage options dialog to contain
a "apply to all" checkbox. When selected, the specified
usage option will be applied to all imported usages and
rules without redisplaying the options dialog.
----------------------------------------------------------
P8010441 - PK07289
CLIENT - ONLY ASK FOR ASSOC OBJECTS ONCE ON EXPORT TO SYSTEM
This enhancements provide the following:
- The associated objects dialog is displayed now only once during
export to system instead of for each and every selected object.
- The object type has been added to the messages displayed during
export of an object. This provide additional information to the
user and should be helpful during problem resolution.
------------------------------------------------------------------------
Server Dependencies
P8010443 - PK07292 Client Fix Pack 14 plus PTF PK05005 or MP CSD18
CLIENT - SUPPORT SETELEMENTATTRIBUTE COMMAND
**Please see implementation guide available on the website.
*************************************************************************
*End of WebSphere Data Interchange Client v3.2.1 FIX PACK 14 README.TXT**
*************************************************************************
---------------------------------------------------------------
WebSphere Data Interchange Client v3.2.1 FIX PACK 13 README.TXT
Included in this section are:
1. List of problems fixed added in Fix Pack 13
2. Enhancements
3. Server Dependencies
4. DataBase Update Instructions
---------------------------------------------------------------
Problems fixed in Fix Pack 13 include:
P8010251 - PQ98445
ABEND COMPILING MAP
P8010254 - PQ95236
WDI 3.2 MAP IMPORT ERROR
P8010264 - PQ95806
DELETE MAPPING, CHOOSING NO, FREEZES SCREEN IN WDI 3.2 CLIENT
FIXPAK11 LEAVING A RECTANGLE ON THE SCREEN, WHEN USING MOUSE
P8010269 - PQ98446
GENERAL GRID ISSUES HAVE BEEN REPORTED
P8010147 - PQ98449
DATA ELEMENT MIN MAX LENGTH & SAVE RESULTS IN 0
P8010271 - PQ96240
THE SQL0104N ERROR OCCURS WHEN CUSTOMER ATTEMPTS TO PREVIEW ANY
MAPS SELECTED AS THE OBJECT TYPE ON THE REPORTS LISTS WINDOW
P8010300 - PQ97790
CLIENT RECEIVE USAGE COPY FUNCTION ASSIGNS INCORRECT TRANSACTION
WHEN AT FIX PACK 11. FIX PACK 10 AND BELOW IS WORKING
P8010303 - PQ97828
CONTROL NUMBERS ASSOCIATED WITH TRADING PARTNERS NOT
EXPORTED WHEN EXPORTING TRADING PARTNER PROFILE
P8010308 - PQ97954
CANNOT ENTER DASH WHEN ENTERING NEW FIELD NAME FROM
ADF RECORD EDITOR GRID
P8010311 - PQ98010
WDI CLIENT DOES NOT ALLOW FOLD CHARACTER TO BE TILDA OR CARROT
IN LANGUAGE PROFILE
P8010282 - IC43407
Errors handling schemas with mixed="true" attribute
P8010292 - IC43545
Unable to find element for schema with
elementFormDefault="unqualified" in certain cases
P8010287 - PQ97163
CONTACT INFO IN TRADING PARTNER PROFILE MEMBERS NOT MIGRATING
FROM DI 3.1 TO WDI 3.2
P8010307 - IC43777
QUERY FOR DT MAPS IN CLIENT HAS DICTIONARY NAME/TRANSACTION/
DATA FORMAT NAME FIELDS BUT THEY DON'T WORK
P8010332 - PQ98610
UPDATED CLIENT TO HANDLE UPPERCASE FILETYPES WHEN IMPORTING
DTD AND SCHEMA FILES
P8010304 - IC43739
CORRECTED ISSUE HANDLING DATES GREATER THAN JANUARY 18, 2038
IN THE TRANSACTION STORE AND EVENT LOG
P8010334 - PQ98619
WDI CLIENT COPY OF SEND USAGES "APPLY CHANGES TO ALL SELECTED
SEND MAP USAGES" IS INEFFECTIVE FOR ALL COPIED-TO USAGES.
P8010346 - PK00369
CLIENT - LANG PROFILE - NEW - NEG SIGN REQD BUT NO ERR MSG
P8010347 - PK00370
CLIENT - RENAME OF DATA FORMATS OR DATA FORMAT DICTS ABENDS
P8010359 - PK00672
COPY OF DATA FORMAT FIELD FAILS IF NAME IS > 16
------------------------------------------------------------------------
Enhancements
P8010322 - MP CSD16 or PK00372
The label on the "Open" button in the "Select Export File" dialog has
been changed to OK per outstanding user requests.
P8010323 - MP CSD16 or PK00373, Customer Conference Requirement
The Data Transformation, Validation and Functional Acknowledgment Map
reports are now available in HTML format.
P8010196 - PQ98219 or MP CSD16, Requirement RPOE-5X8QJ9
Implement CICS Continuous Receive capability for PERFORM TRANSFORM.
------------------------------------------------------------------------
Server Dependencies
8010190 - PQ91707 or MP CSD16
16122 - AN INVALID LITERAL KEYWORD WAS SPECIFIED WHEN ATTEMPTING
TO MAP &SE01 AND &SE02 IN WDI 3.2 WHEN IT WORKED FINE IN DI 3.1
*************************************************************************
*End of WebSphere Data Interchange Client v3.2.1 FIX PACK 13 README.TXT**
*************************************************************************
Additional Platform Support:
- DB2 8.1
- Windows XP
---------------------------------------------------------------
DB2 8.1 Support
WebSphere Data Interchange 3.2 will work on a DB2 7.2 or
DB2 8.1 database.
Note1:
When migrating from DB2 7.2 to DB2 8.1 databases, there appears
to be some DB2 migration restrictions associated with DB2 8.1
Clients accessing a DB2 7.x database.
Consult the following DB2 8.1 Release Notes documentation for
more information on this restriction:
ftp://ftp.software.ibm.com/ps/products/db2/fixes/english-us/
db2winIA32v8/fixpak/FP1_WR21316/Release.Notes/release.txt
If you are in a migration state, and are using WDI 3.2 Client
(with DB2 8.1 Client software) to access a WDI 3.2 MP Server
database (on a DB2 7.1 database), you may experience the
following error messages:
"11041 - A database error occurred while attempting to open
table "EDIENU32.EDIPSDI". ODBC return code is: -1.
Description: SQL0805N Package "NULLID.SYSYSH200" was not found.
SQLSTATE=51002"
After pressing Cancel button, this is followed by:
"11231 - Unable to determine the version of the database. If
the table EDIPSDI was not found, you may need to upgrade your
database to the current WebSphere Data Interchange release.".
No upgrade of WebSphere Data interchange is required.
The situation is a part of DB2 migration.
Note2:
There is no known problem with accessing DB2 8.1 databases
with a DB2 7.2 Client.
To avoid problems during this migration state:
1) It is recommended that a copy of the WDI 3.2 Client that
uses DB2 7.2 Client software exist during migration from DB2 7.2
to DB2 8.1, as this Client software will be able to access both
DB2 7.1 and DB2 8.1 (Server) databases.
2) It is further recommended to use the WDI 3.2 Client release
migration facility during the migration from the DB2 7.2 database
to the DB2 8.1 database.
If you are installing WDI 3.2 MP on DB2 8.1 without migration,
then you should not encounter the above errors."
--------------------------------------------------------------------
Windows XP Platform Support
WDI 3.2 Multi-Platform (MP) runs on the Windows XP platform
with the following notes/concerns:
1) Windows XP requires MQSeries 5.3.
WDI does not that require this, but this is required for
using MQSeries on Windows XP.
2) WDI 3.2 MP runs on Windows XP with either DB2 7.2 or DB2 8.1.
3) However, there is a known problem with running the WDI 3.2
Client with Microsoft Access (the "Development" database).
Whenever the user opens any list window, they will receive an error
(actually two error messages) and then may get the list window displayed.
For example:
Attempt to open a list window (example: SETUP, DATA FORMATS,
STANDARDS, MAPPING) and the user may get a pop-up window with
the folllowing information:
"11268 - An error occurred trying to open data source name
"WDICLient32DEV". Path to the database is
"C:\Program Files\IBM\WDI Client V3.2\wdiclient32dev.mdb".
Database extended error code is "2000". You may need to re-install
Microsoft DAO. Contact support if you need assistance."
followed by another pop-up window with the following information:
"12013 - An error occurred while updating the Transaction Store
database table definitions in the "Development" system.
Working with the Transaction Store may be problematic.
An attempt will be made to correct the problem the next time
the system is opened. " then the list window is displayed.
Therefore, it is recommended that users of WDI 3.2 Client on
Windows XP either:
A) use DB2 for their development database.
B) upgrade the original version of the wdiclient32dev.mdb file
to a newer version of Access.
1) Do a release migration to export all of your system and
configuration data.
2) Then put on a new version of the MDB's.
3) Then do a release migration to import the previously
exported data.
-----------------------------------------------------------------------
December 3, 2004
WebSphere Data Interchange Client v3.2.1 FIX PACK 12 README.TXT
With this fixpack, WebSphere Data Interchange v3.2 becomes v3.2.1.
This is in conjunction with the zOS product service rollup to v3.2.1.
There are no fixes or additional function contained in this Fix Pack.
The corresponding MP CSD is CSD15.
The client application continues to allow you to manage the servers on
the differing platforms simultaneously, using a single Client application.
Installation testing revealed that for new users who have the base code
installed and then go directly to Fix Pack 12 will encounter an initial
database error message. This is caused by a database timing issue
because of the way dbupdate is written. These types of errors will
self-correct when the Retry button is clicked. This has been logged
as a development problem and will be resolved in a future fix pack.
*************************************************************************
*End of WebSphere Data Interchange Client v3.2.1 FIX PACK 12 README.TXT**
*************************************************************************
WebSphere Data Interchange Client v3.2 FIX PACK 11 README.TXT
Included in this section are:
1. List of problems fixed added in Fix Pack 11
2. Enhancements
3. Server Dependencies
------------------------------------------------------------------------
Problems fixed in Fix Pack 11 include:
P8010148 - OA07860, OA08123
KEYWORD, &TCN PRODUCING INCORRECT RESULT
P8010155 - PQ89936
ERRONEOUS TR0052 MANDATORY SEGMENTS MISSING
P8010161 - PQ90220
TREE VIEW OF CLIENT MAP, WHEN COPYING OR DELETING IT, CAUSES
A DICLIENT.EXE APPLICATION ERROR AND TERMINATES THE CLIENT
P8010191
DB ERROR WHEN COPYING DTD OR SCHEMA
P8010124 - PQ88464
USFLAG IN EDIPSAP IS NOT UPDATED CORRECTLY WHEN A COPY IS
P8010215 - PQ92551
WDI CLIENT DOES NOT SHOW APPLICATION SENDER OR RECEIVER ID WHEN
DISPLAYING RECEIVE USAGES. FLAG COLUMN SHOWS S OR R AS EXPECTED
P8010211 - PQ92495
SQL -301 ERROR USING DATADIRECT ODBCSEQUELINK DRIVER
P8010213 - PQ92539
CLIENT - 11041 POPUP MESSAGE NUMBER OF BOUND COLUMNS EXCEEDS THE
NUMBER OF RESULT COLUMNS WHEN USING SEQUELINK ODBC DRIVERS
P8010220 - PQ92639
CLIENT UNABLE TO USE THE SPECIAL CHARACTER NOT SYMBOL WHEN
CREATING NEW TRADING PARTNER
P8010172 - IC41356
EXISTING QUERY IN WDI CLIENT, RECEIVES ODBC ERROR 11060, AFTER
INSTALLING FP9 OR FP10, WHEN QUERY HAS NULL VALUE FOR FIXEDVALUE
------------------------------------------------------------------------
Enhancements
P8010183 - Requirement LCLK-62DM68
ENHANCEMENT - ADD ACTIVATE ACTION FOR RULES/USAGES
P8010162 - Requirement DESZ-5XYM57
ENHANCEMENT TO ALLOW EXPORT OF RULES/USAGES
P8010181
ENHANCEMENT - XML SPLIT USER INTERFACE
Fix pack 11 includes a reworking of the code related to the grid
control used in the editors for data formats and standards. In
the past, there were a number of problems raised about the grid
controls. Some of the changes and problems that have been fixed
include:
* Cells now only allow you to enter valid characters into the cell.
Before you could enter anything you wanted. The cells now work like
the corresponding controls from the editors.
* You no longer must click on another cell or row to have your change
accepted by the cell.
Previously, having invalid data in a cell when save is pressed would
result in the value being replaced and the save completing successfully
without an error message or warning being issued. With fix pack 11 an
invalid value in a cell when save is pressed will result in an error
message, the invalid value will remain in the cell, and save will not
complete.
* Previously, entering characters in a dropdown list would result in a
matching value from the dropdown list prefilling the cell. Entering
additional characters in the cell resulted in the new characters being
inserted into the value that was prefilled instead of replacing the
prefilled value. This has been corrected in fix pack 11.
* The cells dealing with "unlimited use" and "maximum repeat" now work
together. Before setting the checkbox in unlimited use set a number
value in maximum repeat, such as 9999. Setting the number like 9999 in
maximum use set the checkbox in unlimited use. Changing the number in
maximum repeat could change the unlimited use checkbox. Now if the user
sets the unlimited use checkbox then the maximum use field becomes
blanked and disabled.
* The grid will now preserve column width and row heights.
* The user must now enter data into a new row that is required before they
can access the optional cells in that row.
A new row is not appended to a grid until the minimum amount of data is
entered into a previous row. This was an issue because it was entirely
possible for a user to create 10 new rows all with insufficient data in
them. This led to many different error handling issues in the client.
* Formatting of data in cells is better - some columns will be centered.
* Unselecting rows now works in list windows
* The grids are now closer to IBM "accessibility" compliant requirements.
The last item, "accessibility", seems to be causing a major issue. In the
past, it was common to use the tab key or the arrow keys to move around the
grid. However, if you could not use a mouse then you could never leave the
grid. You could not get to other controls on the tab page or move to
another tab page. Fix pack 11 corrects this issue by continuing the common
standard of using the tab key to move from one control to the next. If you
are in the grid and press the tab key, focus moves from the grid to the
next control, usually the tab itself. Pressing the tab key again moves
focus to the next control, and so on until focus returns to grid. When
focus is on a tab, the arrow keys can be used to move from one tab page to
another. While in the grid, you can still navigate the grid using the
arrow keys. This is a bit of change for those that are use to using the
tab key to navigate the grid control, but it is a change that is necessary
to conform to "accessibility" requirements.
* There have been other grid issues that have been fixed that are not as
noticeable and far more severe than the issues with fix pack 11. The
recent grid work fixed many problems and provided a number of usability
enhancements.
------------------------------------------------------------------------
Server Dependencies - CSD14
XML Split User Interface - CSD14 or PTF PQ92067
EXISTING QUERY IN WDI CLIENT, RECEIVES ODBC ERROR 11060, AFTER
INSTALLING FP9 OR FP10, WHEN QUERY HAS NULL VALUE FOR FIXEDVALUE - CSD14
*************************************************************************
***End of WebSphere Data Interchange Client v3.2 FIX PACK 11 README.TXT***
*************************************************************************
-----------------------------------------------------------------------
WebSphere Data Interchange Client v3.2 FIX PACK 10 README.TXT
Included in this section are:
1. List of problems fixed added in Fix Pack 10
2. Enhancements
3. Server Dependencies
4. Help updates
------------------------------------------------------------------------
Problems fixed in Fix Pack 10 include:
P8010127 - PQ88658
EDI2DICT TRANSLATION TABLE IS HIDDEN FROM VIEW ON WDI 3.2 Z/OS.
PROBLEM DOES NOT AFFECT MULTIPLATFORM (AIX AND W2K)
P8010130 - PQ88817
ABENDS0C4 DURING RECEIVE TRANSLATION OF PAYMUL TRANSACTION.
ABEND DOES NOT OCCUR ON DI 3.1, NOR ON 3.2 WITH 3.1 C.S.
P8010048 - IC39807
ODBC CONNECTION SQL0203N ERROR WHEN ATTEMPTING TO USE PRINT
PREVIEW IN TRANSACTION STORE
P8010153 - IC41098
CLIENT WDI SHUTS DOWN WHEN ATTEMPTING TO MODIFY AN EDI STANDARD
------------------------------------------------------------------------
Enhancements
1) Continuous Receive editor has been enhanced. It now has 4 tabs instead
of the previous 2. It also groups the controls better to assist the user
to work with the profile.
2) The term “Forward Translation” has been standardized to “Forward
Translation Table”.
3) The term “Reverse Translation” has been standardized to “Reverse
Translation Table”.
4) The Global Variables editor will now only allow you to enter valid
characters into the initial values field.
5) The local variables properties dialog will now only allow you to enter
valid characters into the initial values field.
6) Editors containing grids will now allow you to resize the width of columns
and height of rows. These values will be restored each time you open the editor.
7) Labels in grid editors are inserted dynamically now. They are no longer
hardcoded into the grid resource.
8) Default sizing of columns has been changed so it is based on the current
system font and not a hardcoded value. This will allow column widths to default
correctly regardless of the font selected by the user.
9) List windows will now restore the height of rows.
------------------------------------------------------------------------
Server Dependencies - There are none with this fix pack.
------------------------------------------------------------------------
Help Updates
1) Help has been rewritten for the Forward Translation Tables, Reverse
Translation Tables, and Code Lists.
*************************************************************************
***End of WebSphere Data Interchange Client v3.2 FIX PACK 10 README.TXT***
*************************************************************************
Included in this section are:
1. List of problems fixed and enhancements added in Fix Pack 9
2. Server dependencies
3. Enhancements
------------------------------------------------------------------------
Problems fixed in Fix Pack 9 include:
P8009852 - OA04862
CLIENT - UNABLE TO INSERT AN ELEMENT WITHIN A SEGMENT
P8009947 - IC38658
SERVICE PROFILE PRE-EXECUTION AND POST-EXECUTION COMMAND FIELDS
ARE NOT FUNCTIONING
P8009967
CLIENT - XML SCHEMA AND OTHER HELPTEXT TYPOS
P8009975
CLIENT REPORT LIST WINDOW - NO XML FUNCTIONAL AREA
P8009976
CLIENT - COPY NAMESPACE/SCHEMA OBJECT GETS WRONG HELP
P8009985
CLIENT - NO DF OR STD CONTROL STRINGS IN RELEASE MIGRATION
P8010001 - IC39270
DATA FORMAT CIRCULAR REFERENCE ERROR 16304 OCCURS WHEN SAVING
AN ADF AFTER INCREASING THE MAX USE OF A RECORD
P8010004 - IC39290
SETPROPERTY FOR ACFIELD NOT DOCUMENTED IN HELP TEXT, USER GUIDE,
OR TRANS STORE IMPLEMENTATION GUIDE
P8010024
CLIENT- NETWORK PROFILE EDITOR HELP - MESSAGE HANDLER FIELD
P8010026
CLIENT - MQSERIES HIGHLIGHTED WORD IN PRTFILE HELPTEXT
P8010039 - IC39752
DATECNV() FUNCTION HELP UPDATE
P8010058
CLIENT - SHOW DT RULES IN ENVELOPE PROFILES VIEW RULES & USA
P8010073 - IC40070
ERROR POPUP 11060 WHEN IMPORTING TO AN AIX DB2 DATABASE
P8010075 - OA07085
DICLIENT "EXPORT TO OTHER SYSTEM" FAILS FOR CONTROLS STRING
P8010077 - Requirement DESZ-5XKMJ6
CLIENT - ENHANCEMENT TO MANUALLY FA GROUPS IN TRANS STORE
P8010085 - PQ87295
WDICLIENT MAILBOX PROFILE ON WDI 3.2 DOES NOT CONTAIN ALL FIELDS
AS WERE AVAILABLE IN THE REQUESTOR PROFILE ON DI 3.1
P8010088
CLIENT - 11268 ERROR OPENING WDICLIENT32DEV. RE-INSTALL DAO
With FIXPAK9, the user may initially experience the
following error message (ONLY ONCE):
"11041 - A database error occurred while attempting to open
table "EDIDTDHDR". ODBC return code is:-1.
Description: Too few parameters. Expected 2."
possibly followed by the following:
"12018 - An error occurred while updating the EDIDTDHDR
database table deinition in the "Development" system.
Working with XML may be problematic. An attempt will be made
to correct the problem the next time the system is opened."
It appears to be a timing issue between adding the new grammar
type column and trying to initialize the value of that column
for existing rows in the database.
P8010090
CLIENT - ABEND IN MAP EDITOR AFTER FAILED COMPILE
P8010091
CLIENT - ICHGSNDRQL, ICHGRCVRQL PROPERTIES MISSING
P8010092 - IC40374
CLIENT CANNOT ADD HL LOOPS TO A DT MAP DOING EDI TO XML
P8010095
CLIENT - UNABLE TO MAP DTD/SCHEMA WITH PERIODS INCLUDED
P8009981
FATAL ERROR XML PARSER SCHEMA / DTD - SPACE COL 255
Note: You will only need to re-import the specific schemas where this
problem occurs. You do not need to re-import all of your schemas.
------------------------------------------------------------------------
Server Dependencies
- there are none for this Fix Pack.
------------------------------------------------------------------------
Enhancements
1) The database error that you may have gotten when WDI Client is started
is now fixed.
2) There is now a "Rules and Usages" functional area. There is a new
button on the navigator bar. You can create your own Queries to select
Rules and Usages. Also, windows list of Rules and Usages will now "remember"
your column settings.
3) The Query editor has been updated. This feature will improve performance
in listing objects.
4) Tree scrolling in Data Transformation Maps, Validation Maps, and Functional
Acknowledgement Maps when a branch is expanded has been implemented.
This was requested by users at the customer conference last year.
5) A System added is now immediately available to the user. Previously,
the user had to close WDI Client and then open it again before the System
would be available.
*************************************************************************
***End of WebSphere Data Interchange Client v3.2 FIX PACK 9 README.TXT***
*************************************************************************
Included in this section are:
1. List of problems fixed and enhancements added in Fix Pack 8
------------------------------------------------------------------------
IMPORTANT NOTE - Server Dependencies:
There were database changes that are included in CSD9/CSD10 which will
effect a client/server installation on the open platforms. Please
be sure that when upgrading to / installing this fix pack that you
also upgrade/install CSD9/CSD10 so that your database is updated.
------------------------------------------------------------------------
Problems fixed in Fix Pack 8 include:
P8009865
ENHANCEMENT - SHARED DATABASE COLOR
The system color will now be taken from the system
definition in the configuration database. Any preference
set by the user will override the configuration database
setting. Setting the database color from the Systems
editor will reset the preference specified color. The
System specified color always displays in the Systems
editor. The preference specified color displays in the
preferences window. If a preference specified color does
not exist, then the system specified color will be present
in the preferences window.
P8009866
ENHANCEMENT - RESIZEABLE DT MAPPING COMMAND EDITORS
The command editors, comment editors, and group
editors have been modified so they can be resized.
The editors can be made larger, but they can not be
made smaller than the default size. Size and positional
information is serialized so the editors are restored
as the user left them.
P8009882 - IC37824
ORDER OF CONSTRUCTS IN MAPPING WINDOW DON'T CHANGE AFTER
IMPORTING NEW DTD OR ADF AND NO ERRORS ARE ISSUED.
P8009901
CAN ONLY CREATE 2 FOREACH() CMDS USING DRAG
In target based maps, only two ForEach() commands
can be created by dropping on an element. Afterwards
a message is issued stating that the mapping command
window can not determine which existing ForEach()
command should be followed to insert this command.
The message should never be displayed when creating
ForEach() commands by dropping on an element. A new
ForEach() command should be created within the element
dropped on.
P8009909 - Requirement IGS
ENHANCEMENT - TA1/SERVICE SEGMENT VALIDATION
Add comments to help file for TA1 and service
segment support. Add ServSegVal property to
popup menus and to help.
**NOTE: The TA1 support is provided on the server in CSD8.
P8009930 - IC38228
PLUS SIGN (+) ON DT MAP DEFAULT QUALIFY MESSAGE SEGMENT
DISAPPEARS UPON DELETE AND RECREATE OF QUALIFY COMMAND
P8009895 - IC37967
CANNOT USE SPACES IN TRADING PARTNER'S ACCOUNT AND USER
ID NAMES
P8009898 - IC38007
CANNOT CREATE MULTIPLE RULES IN THE SAME DT MAP USING TP
ISA05/06 VALUE, WITH AN UNIQUE APPLICATION SENDER ID GS02
P8009828 - Requirement Customer Conference
ENHANCEMENT - ADD XML SCHEMA SUPPORT
**NOTE: Schema support for the server is included in CSD9.
P8009951 - IC38683
ERROR RUNNING REPORTS: ODBC ERROR: SQL0206N "EDIENU32.EDIVTSTH.
STDTRNID" IS NOT VALID IN THE CONTEXT WHERE IT IS USED
P8009896 - IC37972
ONLY 1 TRADING PARTNER RULE/USAGE CAN BE ACTIVE AT A TIME, THAT
HAS THE SAME SENDER ISA05/06 NAME AND UNIQUE APP SENDER ID GS02
P8009964
COMPILE OF DT MAPS - NO TARGET DOC - ILLEGAL INSTRUCTION
Client abends when trying to compile a DT map that has the source
document, but is missing the target document.
P8009965
TR0053 ISSUED WITH HIPAA 270/TRN SEGMENT
P8009990
When opening a map that has any command in the nodes, the commands
appear at the top of their embedding structure. If the map is then
changed and saved, the mapping commands are saved in the wrong
position.
**Note: Maps are NOT backward compatible.
For example: if you create or change a map with Fix Pack 8 then it
may or may not display at earlier Fix Pack levels.
*************************************************************************
***End of WebSphere Data Interchange Client v3.2 FIX PACK 8 README.TXT***
*************************************************************************
Included in this section are:
1. List of problems fixed in Fix Pack 7
------------------------------------------------------------------------
As part of Client Fixpack 7 and Server CSD7, the FAError mapping command
has been extended. Client Fixpack 7 should only be installed if the WDI
Server is also upgraded to CSD7. Control strings that are compiled
using Client Fixpack 7 will NOT work on a server that has not been
upgraded to CSD7 or later.
P8009787 - IC36711
HL ITERATION REFERRING TO NONEXISTENT PARENT IS NOT FLAGGED AS
AN ERROR. THIS CONDITION VIOLATES X12 SYNTAX RULES.
P8009788 - IC36714
HL ITERATION REFERRING TO INCORRECT PARENT AS PER HIPAA STANDARD
IS NOT FLAGGED AS AN ERROR. THIS VIOLATES HIPAA SYNTAX, NOT X12.
P8009511
DO NOT ALLOW GENERIC ENVELOPES IN MAP RULES
P8009799 - OA04189
WDICLIENT LOOPS/HANGS DURING COMPILE OF A MAP WHEN ADF CONTAINS
MORE THAN 999 FIELDS.
P8009792
SUPPORT C&D RECORD SUPPORT IN DATA TRANSFORMATION MAP
(this corresponds to the server enhancement provided on CSD7)
P8009833
SUPPORT EXTENDED FAERROR() COMMAND
(this corresponds to the server enhancement provided on CSD7)
P8009834
ADD HLDEFAULT COMMAND TO SOURCE BASED MAPS.
This command can be placed following HLLevel() commands.
There can only be one within the same parent at the same level.
P8009775
GET MESSAGE CONTROL STRING COMPILE SUCCESS, BUT NO CONTROL STRING
*************************************************************************
***End of WebSphere Data Interchange Client v3.2 FIX PACK 7 README.TXT***
*************************************************************************
Included in this section are:
1. List of problems fixed in Fix Pack 6
------------------------------------------------------------------------
- Unable to update the envelope type on standards
- Support MQMD and MQRFH2 properties
(this corresponds to the server enhancement provided on CSD6)
- WDIClient cannot print data formats - 13002 Crystal Reports encountered
the following difficulty: Cannot open SQL server.
Perform the following:
- Go to Settings > Control Panel > Adminstrative tools
- Open the Data Source(ODBC) panel.
- Double click "ADFTemp32 MP". This will open "ODBC Text Setup
- Click "Select Directory" button.
- Drill down to folders C:\program files\ibm\wdiclient32\crw
- Single click the file name ADFTEMP.txt and then click OK
- Restart the WDI client and try to print the data format again
- Command chaining not working on EDI to XML double translations
(this corresponds to a server change provided on CSD6 or for
zOS customers PTF UQ78935)
*************************************************************************
***End of WebSphere Data Interchange Client v3.2 FIX PACK 6 README.TXT***
*************************************************************************
Included in this section are:
1. List of problems fixed in Fix Pack 5
------------------------------------------------------------------------
- Customer unable to compile map on DI 3.2, after migrating from 3.1
using fix to fix translation.
- ADF Print encounters ODBC error when the "decimal symbol" on the users
W2K Regional Options is set to comma.
- Customer migrated from 3.1 to 3.2 and got the following error when
they made some changes and tried to save it:
16011 - The "Record ID" field is required and must be at least 1
character(s) long.
- 15313 - The "Sending Trading Partner Profile" value is not valid
TPNICKN(xxxxx) import failed.
- DBERROR - Receive usage - CLI0100E Wrong number parms.
- Receive Usage - Version, Release, Agency in APPLID.
- Receive Usage - Group level FA only value not saved.
- French customer receives error message after updating map. Found this
to be possibly caused by codepage translation, but more likely because
they are using version 5 of DB2. Fix was to add space after commas
in SQL INSERT and UPDATE commands.
- Trading Partner Profile member does not recognize apostrophe.
Code was changed to add this support.
*************************************************************************
***End of WebSphere Data Interchange Client v3.2 FIX PACK 5 README.TXT***
*************************************************************************
WebSphere Data Interchange Client v3.2 FIX PACK 4 README.TXT
Included in this section are:
1. Enhancements in FIX PACK 4
------------------------------------------------------------------------
Enhancements include:
- Paste in an edit control does not support the UNDO function
- Support right mouse button drag
* When the user drops a mapping command after dragging using the
right mouse button, a popup menu should be displayed allowing
the user to put the mapping command before, after and within the
target node (depending on what is valid for the node that was
dropped on). This will make mapping easier for users.
- Double click in mapping command editor
* Change the double click action on the mapping command editor
so it does not include the adjacent delimiters.
- Enhance the mapping command editor to make it easier for the
user to build mapping commands.
* Right click on the mapping command to display a popup menu.
The popup menu will assist the user to create the mapping command.
- UNS Segment in SUSDEC messages is being matched against 2 different
positions in validation map.
- When looking at a specific ADF, on the general tab, click on
where used, it does not show transformation maps.
- When importing Maps that have many Receive usages an error 11041
can occur when importing the Receive Usages. The error indicates
that no more table can be opened. In client/server mode, the
error points to the EDITPRT table.
- Added the THandle property to the values menu for the Getproperty
function. Help text was also updated accordingly.
*************************************************************************
*** End of WebSphere Data Interchange Client v3.2 FIX PACK 4 README.TXT****
*************************************************************************
WebSphere Data Interchange Client v3.2 FIX PACK 3 README.TXT
Included in this section are:
1. Special Instructions
2. List of problems fixed in FIXPACK 3
3. Enhancements
4. On line help updates
------------------------------------------------------------------------
Special Instructions:
When the WebSphere DataInterchange Client first accesses a local database,
it attempts to insert a column and update two views in the local database.
These changes are related to Transaction Store enhancements. We have found
on some machines that an error occurs relating to Microsoft's Data Access
Objects (DAO). If this problem occurs on your machine, you will receive a
warning message each time you open the local database. The message indicates
that the attempt to update the database relating to the Transaction Store
has failed. Despite the message, you will have no problems using the
WebSphere Data Interchange Client unless you attempt to access the
Transaction Store in the affected local database. Data is never contained
in the local database relating to the Transaction Store. Therefore, this
should not be a significant issue. This problem does not affect access of
the Transaction Store on Server databases. The local database contains a
Transaction Store for compatibility with the Sever database only.
At this time, we have not found a solution to the problem relating to
Microsoft's DAO. The message can be ignored or a work around can be
performed. To implement the work around solution, perform the following
steps:
1. Download the "WDIClient32Dev.mdb" database from the web at URL
www.ibm.com/websphere/datainterchange and click on Downloads.
2. Use WebSphere DataInterchange Client to perform a "release migration"
to export data from the local database. Refer to WebSphere Data
Interchange Client help for detail information about the "release migration" function.
3. Rename your existing local database. This is usually called "WDIClient32Dev.mdb". It is normally located in your WebSphere
Data Interchange Client install directory. Typically this is directory
" C:\Program Files\IBM\WDI Client V3.2".
4. Put the downloaded database into the directory where the local
database was located.
5. Use WebSphere Data Interchange Client to perform a "release migration"
to import the data exported in step 2.
If you have additional local databases, you may need to perform the above
steps for each of your local databases. In this case, the name of the
local database and the directory it is contained in may be different than the "typical" names.
------------------------------------------------------------------------
Problem fixes include:
- SYNC UP DELETIONS AND QUERY SELECTIONS TO PREVENT GPFs of LIST
WINDOWS
- HL QUALIFIED MAP SHOWS INCORRECT LOOPING SEGMENTS,
THEN AFTER MAP SAVE/CLOSE/OPEN ERROR ICON APPEARS BY TABLE 2
- ERROR MOVING/COPYING HL MAPPING
- CLIENT/SERVER 11041 CLI0112W CLIO112E ON ADF WHERE USED
- COMPILE ERROR ON DT XML TO EDI MAP AFTER ADDING A FOREACH ON AN
HL LOOP
- DBERROR - TRANSACTION STORE VIEW - INPUT INHIBIT
------------------------------------------------------------------------
Enhancements:
- New field added to transaction store
------------------------------------------------------------------------
Help updates:
- Dialog updated to standardize "repeat" button terminology
*************************************************************************
*** End of WebSphere Data Interchange Client v3.2 FIX PACK 3 README.TXT****
*************************************************************************
WebSphere Data Interchange Client v3.2 FIX PACK 2 README.TXT
Included in this section are:
1. List of problems fixed in FIX PACK 2
2. On line help updates
------------------------------------------------------------------------
Problem fixes include:
- REMOVE "L" FROM MAP RULE ENVELOPE TYPE FIELDS
- MAP RULE - KNOWN GOES BLANK
- DON'T ALLOW SEND OR RECEIVE TP FIELDS TO BE MODIFY
- GPF WHEN DRAGGING TO AN INVALID ELEMENT
- &TCN NOT WORKING WHEN A LITERAL IS USED TO SET IT.
- STANDARDIZE "REPEAT" BUTTON TERMINOLOGY
- CHANGE MOVE/COPY HL SO IT BRINGS COMMANDS WITH QUALIFICATION
- COPY OF SEND USAGE/GENERIC USAGE
- COPY RECEIVE USAGE - NO GENERIC
------------------------------------------------------------------------
Help Text Updates:
- Overall update on product help text
*************************************************************************
*** End of WebSphere Data Interchange Client v3.2 FIX PACK 2 README.TXT****
*************************************************************************
WebSphere Data Interchange Client v3.2 FIX PACK 1 README.TXT
Included in this section are:
1. List of problems fixed in FIX PACK 1
2. Enhancements
3. Help Text Updates
------------------------------------------------------------------------
Problem fixes include:
- MAPTO () WITH A REPEATING STRUCTURE OVERLAPS OUTPUT
- RECEIVE TRADING PARTNER PROFILE ON DT RULE NOT EXPORTED
- EXPORT TO OTHER SYSTEM - MSG 15561 MISSING MAPDESRD
- TRANSACTION STORE DISPLAY ENTRY REPORT BLANK
- MULTIPLE ACTIVE INFORMATIONAL USAGES/RULES
- WRONG AMM SEQUENCE NUMBER CAUSES VALIDATION ERRORS
- INCORRECT CONTROL STRING ON FOREACH (HL_LOOP)
- ENVELOPE PROFILES DROPDOWN IN USAGES/RULES
- MAP IMPORT REPLACES XML DICTIONARY
- SUBELEMENT SYNTAX COMPILED INCORRECTLY
-Users should recompile their maps if unexpected conditional
errors (TR0010-TR0014) are encountered for a composite element.
- GPF WHEN DRAF RESULTS IN RECURSION
- ADD EXPAND ALL / COLLAPSE ALL FUNCTION
- ADD "KNOWN" TO TP DROPDOWNS IN RULES
- DON'T ALLOW "KNOWN" TP TO BE CREATED
- RULE WITH FA MAP SPECIFIED DOESN'T EXPORT SUCCESSFULLY
------------------------------------------------------------------------
Enhancements:
- RELEASE MIGRATION ENHANCEMENTS
-BROWSE BUTTON IS AVAILABLE ON EXPORT TO ASSIST IN SELECTING
A PATH TO CONTAIN RELEASE MIGRATION DATA
-CONFIRMATION DIALOG HAS BEEN UPDATED FOR CONSISTENCY
------------------------------------------------------------------------
Help Text Updates:
- RELEASE MIGRATION ENHANCEMENTS
- DTD CONVERT UTILITY HELPTEXT INCORRECT
*************************************************************************
*** End of WebSphere Data Interchange Client v3.2 FIX PACK 1 README.TXT****
*************************************************************************
WebSphere Data Interchange Client v3.2 README.TXT
Included in this file are:
1. Installation instructions for WebSphere Data Interchange Client 3.2
2. Installing WDI Client to a Server
3. Installing and Using WDI Client from a Server
4. Creating and Using a Shared CONFIG Database
5. EDI Standards Installation
6. Known problem areas
7. Crystal Reports and printer fonts
8. ODBC considerations
9. Transaction Store considerations
10. Multi-user database considerations
11. Middleware, Upload/Download considerations
12. Creating Multiple PC database configurations
13. Fixes included in this version
-------------------------------------------------------------------
1. Installation instructions for installing WebSphere Data Interchange Client
Start the installation by placing the install CD in the CD-ROM drive.
The install should start automatically, in the event that it does not then
Use Windows Explorer to view the WDI Client directory. Execute Launch.exe
to begin the install. Follow the install wizard instructions to complete
the installation.
If you are converting from a previous version of the Client to
WebSphere Data Interchange Client 3.2, make sure you install to a different
directory. Otherwise, WDI Client 3.2 will overlay the existing WDI Client
version(s). Before installing WDI Client, perform a release migration to
extract data from local databases and/or customization time data from
Server databases. To perform a release migration, perform the following
actions:
1. In WDI Client 3.1 or DataInterchange 4.1 from the View menu on the Menu
bar, select the option “DI Client Release Migration”. This option will only
appear if all list windows are closed. When “DI Client Release Migration”
is selected, a wizard will appear which will guide you through the release
migration process. Include configuration data if you have queries, reports or
customizations that you want to retain. You may select multiple Systems
to export if desired. Do not export runtime data if the data exists on
a Server database. Runtime data on a Server database will be migrated by
DataInterchange Host 4.1 or WebSphere Data Interchange 3.1 to 3.2
migration process.
Exporting is tracked using an Execution Status Window, with messages
indicating progress being written to the Execution Status Window as
the exporting progresses.
2. Install WDI Client 3.2.
3. Open WDI Client 3.2.
4. Using WDI Client 3.2, if you exported configuration data in WDIClient 3.1
or DataInterchange 4.1, perform a release migration in WDI Client 3.2 to import
the configuration data you exported from your previous version.
5. Using WDI Client 3.2, open the Systems List window. Update any existing
Systems to utilize the correct ODBC Data Source Name (DSN). Add any new
Systems that need to be added. You may wish to set the System background
frame color at this time.
6. Using WDI Client 3.2, use release migration to import each System that
was exported from previous versions.
Migration is complete after this last step. Note that the DataInterchange
Host or WebSphere Data Interchange server migration must be performed before
everything is in place and ready to use. Also note that release migration export
from a shared database, such as a DataInterchange Host DB2 database needs to be
performed only once. The release migration import also needs to be performed
only once. Only Systems not shared with other users will need to be migrated
by individual users.
See the WebSphere Data Interchange Users Guide for complete
installation instructions.
Run the application by clicking on the WebSphere Data Interchange icon in the
WDI Client program group.
-------------------------------------------------------------------
2. Installing WDI Client to a Server:
The following assumptions are made:
1. A server based install of WDI Client will use a shared CONFIG database.
This is not a requirement, but the following install instructions assume
a shared CONFIG database is being used.
2. The LAN drive used to access WDI Client will always be accessed the same
way.
3. You have the ODBC drivers necessary to access any database used by
WDI Client.
4. You are able to install these ODBC drivers.
5. You are able to setup the ODBC Data Source Names (DSN) needed to access
any database used by WDI Client.
6. Future upgrades to the server installed WDI Client application should be
done from this same machine or a machine that is not using WDI Client as a
server based application.
To install WDI Client to a server, perform the following:
1. If needed, install the ODBC drivers needed to access the shared CONFIG
database and the any other database you intend to access.
2. Update the WDIClient32CFG ODBC entry. Delete the default WDIClient32CFG
entry and create a new one using the appropriate ODBC driver.
3. Add ODBC entries for the other databases you will be using from inside
of WDI Client.
4. Link to the server disk and install WDI Client as you normally would.
5. Start WDI Client. Edit the "Systems". Delete the default "Development"
System and define the Systems that you will be using with WDI Client.
6. Test access to each of your defined Systems.
7. Place the DICLIENTREMOTEINSTALL.EXE file, into the install directory.
This can be found at url http://www.ibm.com/websphere/datainterchange/
under Downloads - WebSphere Data Interchange V3.2
8. At this point, you may want to create client install instructions
specific to your environment. Use the section from below called
INSTALLING AND USING WDI CLIENT FROM A SERVER as a starter.
------------------------------------------------------------------------------
3. Installing and Using WDI Client from a Server
For each machine that will use WDI Client over the LAN, perform the following
steps:
1. Install WDI Client normally.
2. If needed, install the ODBC drivers needed to access the shared CONFIG
database and any other shared databases.
3. Update the WDIClient32CFG ODBC entry. Do this by deleting the default
WDIClient32CFG entry and creating a new one using the appropriate ODBC driver.
WDI Client is now installed on the LAN. This machine is now ready to use
WDI Client. Nothing further needs to be done.
If you are using DB2 as your database server, a sample DOS batch file
called CREATEDSN.BAT. This can be found at url
http://www.ibm.com/websphere/datainterchange/
under Downloads - WebSphere Data Interchange V3.2
This file can be used as a model to produce a file that can assist the
people using WDI Client to setup their ODBC for DB2 based databases.
------------------------------------------------------------------------------
4. Creating and Using a Shared CONFIG Database
WDI Client can be run with a shared CONFIG database. This allows multiple
users of WDI Client to share queries and can ease maintenance
considerations.
To setup a shared CONFIG database, perform the following steps:
1. Use WDI Client to perform a release migration of the data in the
configuration database.
2. Install the CONFIG database to a database server, such as DB2, using
the CONFIG.UDB DDL provided in the \DDL directory that was created inside
your WDI Client install directory.
3. If needed, install the ODBC drivers needed to access the shared CONFIG
database.
4. Update the WDIClient32CFG ODBC entry. Delete the default WDIClient32CFG
entry and create a new one using the appropriate ODBC driver.
5. Start WDI Client. It should start without any problems.
6. Delete the default Systems defined to WDI Client.
7. Use release migration to import the configuration data that you
previously exported.
This machine should now be ready to run WDI Client normally.
For each machine that will use WDI Client with the shared CONFIG database,
perform the following steps:
1. Install WDI Client normally.
2. If needed, install the ODBC drivers needed to access the shared CONFIG
database.
3. Update the WDIClient32CFG ODBC entry. Delete the default WDIClient32CFG
entry and create a new one using the appropriate ODBC driver.
Considerations:
1. Each user utilizing the shared CONFIG database will have the same
Systems defined in WDI Client. It is important that each database in each
System be properly defined in the user’s ODBC for each System to work
properly.
2. Each user of the shared CONFIG database will be able to update certain
items in the shared CONFIG database, such as queries and reports. Every
user will be affected by any change made by a single user.
3. Each user will have access to all messages contained in the message
log, regardless of the user that originated the message.
-----------------------------------------------------------------------------
5. EDI Standards Installation
The STDS path on the CD-ROM contains EDI standards in WebSphere Data
Interchange export/import tagged format. The files are intended to be imported
into WDI Client 3.2. See WDI Client 3.2 help text or the WebSphere Data
Interchange User's Guide, Version 3, Release 2 for instructions on importing the
EDI standards. This path has five subdirectories - X12, EDIFACT, UCS,
VICS, and RAIL. Within each subdirectory are the latest EDI standards for
each EDI Standards Agency (e.g. ANSI X12). The name of the export/import
file (.eif) is the version and release of the EDI standard. For earlier
versions of these EDI standards and also updated versions, please visit
the web site (www.ibm.com/webshere/datainterchange) for downloading.
X12 directory: X12V4R1
X12V4R2
X12V4R3
X12V4R4
X12V4R5
EDIFACT directory: EDI98A
EDI98B
EDI99A
EDI99B
EDI00A
EDI00B
EDI01A
UCS directory: UCSV4R1
UCSV4R2
UCSV4R3
RAIL directory: AARV4R1
AARV4R2
AARV4R3
AARV4R4
AARV4R5
VICS directory: VICSV4R1
VICSV4R2
VICSV4R3
The envelope standards are available for downloading from the
web site. Once the envelope standards are imported into a
WebSphere Data Interchange System, they must be compiled before
they can be used by Websphere Data Interchange Host.
Web Site address: www.ibm.com/websphere/datainterchange - Downloads
------------------------------------------------------------------
6. Known problem areas
a) Microsoft Access 97 is the PC database distributed with WDI Client.
If an installation is running in client/server mode using
DB/2 as the Host database, some functions are not supported.
While Microsoft Access 97 supports CASCADE UPDATE, DB/2 does not.
The DIClient RENAME function uses CASCADE UPDATE to rename
many objects. Therefore, the RENAME function is not supported
for most complex objects, including Trading Partners profiles,
Contact profiles, maps, data formats, and EDI standards for any
database that does not support CASCADE UPDATE, including DB2.
Some simple objects will support rename because there are no
referential integrity rules associated with them.
b) During DIClient installation, the object ODBC32.DLL is placed in the
WINDOWS\SYSTEM directory in Windows.
You may experience problems with DIClient initialization if you have
an older version of ODBC32.DLL in another subdirectory that is
accessed in your path before the SYSTEM subdirectory. If this is
the case, you should remove the older version of ODBC32.DLL.
Exercise caution when doing this, however, so you do not affect any
other applications that may also use ODBC32.DLL.
c) Collation tables in the PC Database
Some databases provide a table that dictates a collation sequence
for update and sorting purposes. These tables may not only be used
to determine the order characters will sort in, but also to determine
what character values are equal to one another. For instance, the
default collation table used by Sybase SQL Anywhere specifies that
a character hex 'D5' is equivalent to a character hex '31'. This
causes problems when both of these characters are used as a 'key'
value. A 'duplicate record' message will occur, even though there
appears to be no duplicate keys.
This problem is not likely to occur when using standard characters.
If collation becomes a problem, refer to the documentation for the
database product you are using. Either avoid using characters that
cause these problems, or try to determine how to update the collation
table used by the database product.
d) If you have DIClient 3.1 and DIClient 4.1 installed, you will not
be able to print data format reports from the DIClient 3.1 version.
-------------------------------------------------------------------
7. Crystal Reports and printer fonts
WDI Client uses the Crystal Reports product to produce reports.
The fonts used by Crystal Report Layouts provided with this release
are:
Times New Roman
Arial10
Arial12
If these fonts are not available to WDI Client when a report is printed
or previewed, the image produced may have a "garbled" appearance.
Note that after installation, the WDI CLIENT install directory will have
a CRW subdirectory. The CRW subdirectory contains Crystal
Report layouts (*.RPT files) used by WDI Client. In addition, there
are drivers installed in the operating system directories that
allow Crystal Report outputs to be directed to files, fax lines,
other PC databases, etc.
------------------------------------------------------------------
8. ODBC Considerations
8.1 What is ODBC?
Open DataBase Connectivity (ODBC) is an industry standard for
the application-to-relational database interface. It allows
the customer to use the database of their choice with an
off-the-shelf application like WDI Client 3.2. For example, if
you would rather that WDI Client 3.2 store its data on your LAN
database server, you can do that. It does not matter which
database is running on your server (DB2 Version 2, SQL Server,
etc.) as long as that database is ODBC compliant, and they provide
you with an ODBC driver that you can load onto the computers that
are running WDI Client 3.2. Most relational databases that you can
purchase today provide this capability.
8.2 What does it mean to be ODBC Compliant?
The topic of ODBC compliance is a complex one. There is more than
one version of the ODBC standard and there are various levels of
compliance (core, minimum and extended). Finally, there are some
small ambiguities in the standard. As a result, it is not possible
to guarantee that any database that claims ODBC compliance will
work with WDI Client 3.2. For information on databases that we know
won't work with WDI Client 3.2, call technical support.
8.3 How is ODBC used in configuring your WDI Client implementation?
ODBC is also fundamental to the Client/Server configuration of
WDI Client. ODBC is used to access the MVS DB2 database of
WebSphere Data Interchange Host 3.2. Therefore your Client/Server
environment must include an ODBC Client driver for MVS DB2. This
may be implemented as two separate programs: an ODBC RPC
(Remote Procedure Call) client driver on the PC with WDI Client 3.2
and an ODBC driver on either a LAN database server, or on the MVS system
with DB2. As a result of using ODBC for access to DB2, any Client/Server
environment that supports ODBC clients and MVS DB2 servers can be used
with WDI Client and Host 3.2. As discussed previously, the topic of
ODBC compliance is complex, so contact technical support for information
on any Client/Server environments that we know won't work with
WebSphere Data Interchange 3.2.
For information on your database servers and/or Client/Server
environments we suggest you contact your I/S professionals. The
people that can help you are most likely associated with your LAN
or Database Administration departments.
8.4 What type of system is the LAN database server -- OS, Database,
version of both, etc.
DB2 Connect Enterprise Edition supports OS/2, Windows NT, Windows 2000,
AIX, HP-UX, Sun Solaris, NUMA-Q and Linux operating environments. We
have WDI Client customers running Enterprise Edition on AIX and NT, and
we have WDI Client working with DB2 Connect Personal Edition.
8.5 Where do the ODBC drivers need to be?
For DB2 Connect Personal Edition all drivers/software is on the PC.
For Enterprise Edition, DB2 Client, also known as Client Application
Enabler (CAE), is installed on each PC to provide the needed drivers.
8.6 How is an ODBC Data Source Name setup in Windows?
After you have installed the appropriate ODBC drivers on the PCs
that are running WDI Client 3.2, you must configure them using ODBC
Manager. ODBC Manager is found in Settings/Control Panel.
WDI Client 3.2 is a 32 bit application, so it is recommended that
you use 32 bit ODBC drivers.
ODBC Manager maps Data Source Names (DSNs) to ODBC drivers. WDI Client
has one DSN for configuration information called "WDIClient32CFG".
It also has one DSN for each System that you define. You decide
what these DSNs are. WDI Client is shipped with one System called
"Development". The DSN associated with it is "WDIClient32Dev".
Another DSN associated with the product is "ADFTemp32 MP".
See the documentation or help for the Systems topic for
information on how to define Systems to WDI Client.
If you should experience any trouble printing data formats, do
the following. Go into ODBC and select "ADFTemp32 MP".
Set the location in the ODBC administrator to the location where
the product was installed and click on OK. The report should now
print without problem. The Data Format report is the only report
that uses 'ADFTemp32 MP' as a data source
To enable Client/Server mode, you must associate your DSNs with
your Client/Server ODBC driver within ODBC manager. Go into the
32-bit ODBC manager and press the "Add" button to create your
Client/Server mode DSN. Select your Client/Server driver from the
"Installed ODBC Drivers" list. Next, name your new Client/Server
DSN and provide any required parameters specific to your driver.
To assist you in determining the correct parameters for your driver
we have included parameters that we have tested below:
DB2 Connect Personal Edition
System Schema = SYSIBM
Schema List = "EDIENU32"
Filters = Table, View, Synonym, System tables, Alias
SQLID = The Authorization ID that should be used to connect
to the database
Database Name = EDIEC32E
Transactions:
Remote Unit of Work = Yes
Autocommit = Yes
Cursor hold = Yes
Connect Mode = Share
Max number of connects = 0
Isolation Level = Cursor stability
Type Handling:
Graphic data types = 0
Treat binary datatypes as binary
Treat LOB datatypes as Large Object Binary
Maximum LOB data size = <default value>
8.7 Can you use DB2 Connect since its a DB2 database instead of using
ODBC?
You can use DB2 Connect because it supports ODBC. Only ODBC is used
by WDI Client to access DB2 databases. Tested and recommended
version of DB2 Connect is V7.2.
------------------------------------------------------------------
9. Transaction Store Considerations
The Transaction Store is maintained by the WebSphere Data Interchange
Server and the data in the Transaction Store is not available to
WDI Client unless the user is in Client/Server mode.
On the Transactions List window in the Transaction Store Functional Area,
not all fields available in the WebSphere Data Interchange Transaction
Store are displayed in WDI Client. In the Interchanges List window,all
fields are displayed, but only enveloped transactions are included.
------------------------------------------------------------------
10. Multi-user Database Considerations
- When you first install WDI Client, you use the TYPICAL option to
install all components, including the default databases and
ODBC drivers. WDI Client is installed as a single user
database. If you take steps to reconfigure your database setup
for multi-user, then you should exercise caution whenever you
re-install WDI Client. If you re-install using the TYPICAL option
again, you will overwrite your databases and drivers with the
defaults. In this scenario, you should use the CUSTOM option during
re-installation. This will allow you to choose the components that
will be installed.
- When creating the multi-user environment, make sure that the
drivers go in the proper System directories. The UNINSTALL may
not remove drivers.
- Make sure that the server drivers are from the same version
of the database product from which the database(s) were created.
------------------------------------------------------------------
11. Middleware, Upload/Download Considerations
Data on a PC is stored in ASCII format while data on an MVS host
is stored in EBCDIC format. When data is moved from a PC to a host
(or vice versa) the data must be converted from ASCII to EBCDIC
(or EBCDIC to ASCII). This type of conversion occurs whenever you
upload or download data using a file transfer program like IND$FILE
or when you access data in client/server mode using a middleware package.
Conversion problems can occur whenever you move data between a PC
and a host computer. These problems usually occur when the file
transfer software converts a character to a value you don't expect.
It is particularly important that the file transfer or middleware
software does not change the value of the hex '01' character since
this character is used as a delimiter in the DataInterchange profiles.
If you are using another software product to move data between the PC
and Host, verify that it does not alter the hex '01' character.
To determine if there is a problem with the hex '01' character,
use WDI Client with a middleware connection to the host database.
Create a receive usage - specifying the receiver, agency, version and
release fields. Save the usage and close the Receive Map Usage editor.
Then open the editor for the newly created receive usage. If the agency,
version and release fields appear in the correct place, the conversion
performed by the middleware is not a problem with regards to the
hex '01' character. If these fields all appear in the 'receiver'
field, then the hex '01' character is being changed in either
(or both) the EBCDIC or ASCII conversion tables.
In standalone mode, files are uploaded and downloaded using file
transfer software. During a download to the PC from the host or an
upload from the PC to the host, an EBCDIC/ASCII conversion occurs.
We have seen instances where a character does not convert to the
expected EBCDIC character or the expected ASCII character. For
instance, a character vertical bar (|) on the host converted to a
character double-quote (") on the PC. You must refer to the product
that is used in the download/upload procedure to determine how to
alter the EBCDIC/ASCII conversion. Again, verify that the hex '01'
character is not altered during data transfer.
------------------------------------------------------------------
12. Creating Multiple PC database configurations
WDI Client is distributed with a single set of databases. The
databases are WDIClient32CFG.MDB, and WDIClient32Dev.MDB.
They appear in the installation directory after a typical installation.
They contain only default data when installed.
If you would like to create a second database, i.e. have
a DEVELOPMENT System and a TEST System, then follow these instructions:
? a) copy the file WDIClient32Dev.MDB to WDIClient32Dev2.MDB.
(note WDIClient32CFG.MDB need not be copied since it contains tables
common to all 'Systems').
b) create the ODBC data definitions for the new database;
to do this:
- click on the Settings option of the Windows Start menu
- in the Settings sub-menu, select the Control Panel option
- from the CONTROL PANEL folder, select the 32bit ODBC icon or
Administrative Tools ->Data Sources (ODBC) whichever is available on
your system; the "ODBC Data Sources Administrator" window will appear
- click on ADD, select Microsoft Access (*.mdb) drivers, then FINISH
-The ODBC Microsoft Access Setup diaglog is displayed. Fill in this dialog
and press the OK button. For example, to create a new database entry
do the following:
- type in a Data Source Name, e.g. TestSys
- type in a Description, e.g. test System
- click on the Select button (a Select database window appears)
- select a database file - this is the file name of the copied
database, e.g. c:\program files\ibm\WDI Client v3.2\wdiclient32dev2.mdb
- click on OK to save the entry
c) setup the System definition in WDI Client;
- select VIEW from the WDI Client toolbar
- select Systems
- when the list appears, select the New icon on the toolbar
- create a System entry as follow:
- type a System Name - e.g. TEST
- select the Server Platform corresponding to the WebSphere Data
Interchange Server
- type the Data Source Name (this is the same name as created in
(b) above) e.g. TestSys
- If you are accessing a shared database, such as DB2, enter the
Database Qualifer
- select a background frame color to associate with the System
- click on SAVE to save the entry
d) after all Systems have been created, exit WDI Client and reenter the
product to make the System(s) active
------------------------------------------------------------------
13. Fixes included in this version
WebSphere Data Interchange Client v3.2 incorporates all fixes through:
-FIX PACK 10 for DataInterchange client 3.1 and WebSphere Data Interchange
for Multiplatforms v3.1
-FIX PACK 2 for DataInterchange Client v4.1
------------------------------------------------------------------