*** *** (C) Copyright International Business Machines Corp. 2002. *** All Rights Reserved *** Licensed Materials - Property Of IBM *** *** Welcome to WebSphere Data Interchange Version 3.2 - CSD3 *** Installation Instructions for CSD3********************** Please reference a separate document available on our web site which details the enhancements made that are included in this CSD, as well as any special instructions for installation. March 2003 - CSD3 The following problems have been resolved on this CSD. CSDs are cumulative, so this CSD will include fixes from previous CSDs unless otherwise noted. P8009529 - IC35249 INBOUND EDI MESSAGES REPORT ERROR IN WRONG POSITION P8009561 0 ENVELOPING ON INBOUND CREATES FUNCTIONAL ACKS WITH ISA HEADER. ISA SHOULD NOT BE CREATED. P8009080 DOC TR0025 DUPLICATE TRANSACTION HAS BEEN DETECTED P8009545 - IC35337 AN ABEND OCCURS WHEN A MAP COMMAND REFERENCES A NON-EXISTENT SUBELEMENT OF A COMPOSITE DATA ELEMENT. P8009577 - IC35618 HIPAA VALIDATION MAPS DO NOT SHOW ALL ERRORS IF MORE THAN 1 TYPE EXISTS IN THE SAME SEGMENT. P8009569 TRANSACTION STORE FOR DT MAPS P8009590 - IC35700 ADF TO XML AND XML TO ADF TR0016 ISSUED FOR SEND/RECEIVE MAPS WITH SPECIAL LANGUAGE CHARACTERS AS INPUT. P8009582 - IC35672 WDIADAPTER FAILS AFTER PROCESSING NUMEROUS MESSAGES IN THE SAME INSTANCE. P8009583 - IC35674 EDI TO ADF RECEIVE TRANSLATION FAILS WITH TR0051 WHEN INPUT EXCEEDS 32K AND NO CRLF CHARACTERS. P8009604 ADD EDITRACE TO OPEN PLATFORMS P8009596 - IC35730 XML OUTPUT MSG > 32K ADDS EXTRA CARRIAGE RETURN CAUSING THE XML DATA TO BE NOT WELL FORMED. P8009597 - IC35736 HIPAA VALIDATION MAP IS NOT PROCESSING OR RECOGNIZING LAST LOOP IN THE STANDARD WHEN PRESENT IN THE DATA. P8009606 - IC35815 INVALID RFH2 HEADER GENERATED WHEN INPUT RFH2 CONTAINS NON-NATIVE CCSID. P8009562 SIGNAL 11 - TRANSFORM - ADF2EDI - ADF PARSER P8009610 - IC35843 WDIADAPTER ABENDS DURING ADF TO XML PROCESSING WHEN TRANSLATING CERTAIN INPUT FILES. P8009627 - IC35941 RESIDUAL OUTPUT IN REPEATING SEGMENT IN A TARGET BASED XML TO EDI MAP. P8009607 - IC35827 UNB AND UNH ENVELOPE HEADERS INCORRECT WHEN RUNNING UNDER AIX. P8009647 - IC36002 ADF TO XML (SEND MAP) ENCOUNTERS TR0852 'NO TEXT FOUND FOR MESSAGE TR0852 IN MESSAGE FILE EDIMSG' ************************************************************** *** END OF WebSphere Data Interchange V3.2 CSD3 README.TXT *** ************************************************************** *** Installation Instructions for CSD2********************** If you have not installed CSD1 previously, that is fine - all CSDs are cumulative, but you will need to follow the installation instructions under CSD1 details. If you are installing CSD2 over CSD1 - all that is required for you to do after installation is a bind. Bind the new executables to the database ---------------------------------------- You must bind the new executables to your database. The following steps will run the bind step using the new bind files that were included in CSD2. 1) Change directory to the bind directory 2) Issue the command: db2 -tf bindgrnt.fil -l bind.log This process will BIND the WebSphere Data Interchange V3.2 DB2 packages and GRANT execute authority to public. If you changed the bindgrnt.fil script during the initial DB2 setup to specify a different user or group of users instead of "public", then this command will BIND the DB2 packages and GRANT execute authority to that id or group instead. ************************************************* February 2003 - CSD2 The following problems have been resolved on this CSD. CSDs are cumulative, so this CSD will include fixes from previous CSDs unless otherwise noted. P8009101 PERFORM REMOVE TRANSACTIONS LOCKING OUT TRANSLATOR WITH INTERMITTENT DEADLOCKS AND TIMEOUTS. FF0457 ALSO OCCURS. P8009458 VARIOUS ISSUES WITH CONTRL FUNCTIONAL ACKNOWLEDGEMENT. RECEIVE MAP USAGE SET TO CONTV21. P8009237 PERFORM ENVELOPE FAILS WITH TR0836 BECAUSE HOST STANDARD NOT FOUND IN EDIVSCST. HOST STANDARD SHOULD NOT BE REQUIRED. P8009441 CONTRL message generated for CONTV21 contains incorrect value of "8" in DE 0083 Action Code in the UCM. The action code should be "7". P8009438 ABEND OCCURS IF A DUPLICATE GROUP IS DETECTED P8009151 The problem was caused by the fact that no file was associated with the DD name OUTMSG. When the following set file command was added to the command file the VN1045 error went away. set file(OUTMSG, baseout.msg) The error handling was changed so that better error message would be generated (VN1007 unable to open file) in this condition. P8009229 WHEN TR0016 ISSUED ALONG WITH TR0008 THE CONDITION IS NOT REFLECTED IN THE FA. P8009491 NULL CHARACTER AT END OF EDIFACT UNA SEGMENT p8009499 ADF OUTPUT INCORRECT WITH STRUCTURE REPEAT 22 p8009527 WDI 3.2 MP SERVER INSTALL SCRIPT LINE MISSING FOR EDIUTCU CAUSES UT0055 SEVERITY 08 SQL CODE -805 P8009505 NULL CHARACTERS ADDED TO FILE DURING NETWORK TRANSFERS WHEN A XML FILE IS BEING CREATED WITHIN WEBSPHERE DATA INTERCHANGE NULL CHARACTERS ARE ADDED TO THE END P8009542 For EDI->XML data transformation maps, output data being written to an MQSeries queue is being truncated when the output xml data reaches a certain size, roughly 4-5K. P8009437 Create a PERFORM DELETE USAGE command with the following keywords: a) DIR (X) where X can be S(send) or R(receive), default is R send and receive b) TPTID(xxx) where xxx is the Mapname, 30 characters send and receive c) TPID(xxx) where xxx is the internal Trading partner ID, 35 bytes send d) TPNICKN(xxx) where xxx is the EDI Trading Partner Nickname (profile send and receive e) APPLTPID(xxx) where xxx is the Application Trading Partner nickname, send and receive, this is a new keyword f) APPSNDID(xxx) where xxx is the Application Sender ID, 35 characters receive g) AGENCY(xxx) where xxx is the responsible agency code, 8 characters, default is blank h) VERSION(xxx) where xxx is the version, 8 characters, default is blank i) REL(xxx) where xxx is the release, 8 characters, default is blank j) APPRECID(xxx) where xxx is the Application Receiver ID, 35 characters receive The PERFORM DELETE USAGE will have the following syntax: format for send usage PERFORM DELETE USAGE WHERE DIR(S) TPTID(mapname) APPLTPID(atpid) TPNICKN(etpid) TPID(intpid) format for receive usage PERFORM DELETE USAGE WHERE DIR(R) TPTID(mapname) APPLTPID(atpid) TPNICKN(etpid) APPSNDID(appsenderid) || APPRECID(appreceiverid) AGENCY(agency) VERSION(version) REL(release) format to delete all usages for a given map PERFORM DELETE USAGE WHERE DIR(S/R) TPTID(mapname) All values that are not required will default to blank. DIR will default to R. If both APPSNDID and APPRECID are entered, APPSNDID will be used. P8009404 IF A TRANSLATION TABLE IS CREATED WITH MORE THAN 407 ENTRIES AND IT IS COPIED TO A NEW TABLE, ONLY 407 ENTRIES ARE COPIED. P8009502 WHEN XML FILE IS BEING CREATED IN WDI, WDI DOES NOT ESCAPE RESERVED XML CHARACTERS P8009540 EDIFACT DATA TAGGED ONTO THE END OF A SUCCESSFUL XML USING SEND/ RECEIVE MAPS. THE PROBLEM OCCURS WHEN THE XML DATA PRODUCED HAS FEWER BYTES THAN THE EDIFACT DATA CREATED IN THE TRANSLATION PROCESS, A RARE EVENT WHEN CONSIDERING XML TAG LENGTH. P8009174 When a type of MQ is specified on an ADF WDI currently writes the file out to a MQSeries queue one record per-messaage. This needs to be changed so that the entire file is written out to the queue as a single MQSeries message. P8009495 CTL NUMS HAVE LEADING ZEROS IN GS, GE, ST,SE P8009168 IMPORT 3.1 MAP INTO 4.1 OR WDI 3.2 GETTING DB ERROR P8009494 EXPORT LOOPS FOR HEAVILY REPEATED MAPPINGS P8009487 PERFORM EXPORT 4.1 DT MAPS SOURCE DOC NOT EXPORTING P8009524 MIGRATE DI 4.1 TO WDI 3.2 EXPORT DTD FAILS DB ERROR 8,12 P8009532 EXPORT TABLES WITH CORRUPT RECLN FIELD ABENDS P8009547 DELFILE WILL NOT BE DELETED FOR A TRANSLATION WARNING P8009475 OUTBOUND JOB ABENDING WITH OC4 P8009522 CUSTOMER MIGRATED FROM 3.1 TO 4.1 AND BATCH JOB (SEND/RCV) NOW GETTING FF0475. CUSTOMER ON CICS TS 2.2 P8009541 TR0052 message is issued for each GID segment P8009543 SPLITTING OF OUTPUT XML ONEMSG(Y) IN PERFORM TRANSFORM COMMAND IS NOW VALID P8009546 VALIDATION ERRORS NOT REPORTED IN CONTRL MESSAGE P8009566 EDI TO XML TRANSFORM FAILS WHEN INPUT ISA CONTAINS MULTIPLE GS ENVELOPES WITH DIFFERENT EDI TRANSACTION TYPES. ************************************************************** *** END OF WebSphere Data Interchange V3.2 CSD2 README.TXT *** ************************************************************** November 2002 - CSD1 The following problems have been resolved on this CSD: - ADDED "SEGMENTATION ALLOWED" AND "LOGICAL ORDER" FLAG TO THE MQPUTS - IF UNABLE TO OPEN DESIGNATED FILE WRITE TO EXCEPTION FILE - EDI TO ADF WITH 2 AND Z2 DATA INCORRECT - EXTRA DELIMITERS GENERATED IN UNB SEGMENT - EDI PARSER IGNORES SUBELEMENT DLM IF UNA WITHOUT REP DLM - EDIFACT USAGE INDICATOR '1' NOT RECOGNIZED AS TEST - MISSING SE SEGMENT CAUSES ABEND IN VALIDATION NODE - VALIDATION NODE - APPLY SUBELEMENT SYNTAX NOTES CORRECTLY - SPACES BETWEEN ELEMENTS OF THE RFH2 FOLDER - REPEATING SEG IN LOOP INCORRECT IN THE AMM - XML GEN REPORTS ERROR AMM0011 - VALIDATION NODE - CALL CALIDATION MAP ON OUTPUT - VALIDATION NODE - ERRONEOUS TR0052 FROM NESTED HL LOOP - RU0001 NO ACTIVE RULE WHEN 2 DTDS WITH SAME ROOTELEMENT - DB2 VIEWS NEED TO BE ADDED TO GRNTEC32.DDL - MISSING EDIPSTV, EDIPSTT ENTRIES IN LOAD DATA - MISSING VALIDATION MAP OUTVALMAP ON SAMPLE RULE - MQ ERROR 2012 (MQRC_ENVIRONMENT_ERROR) ON AIX - EDI GENERATOR NOT PROCESSING SEG ELEMENTS CORRECTLY - RFH2 HEADER FOR OUTPUT MSG INCORRECT IF ORIGINATED IN JMS ************************************************************** *** Special installation instructions for CSD1 *** ************************************************************** If you installed CSD1 before setting up your database, then you do NOT need to do any special installation steps for CSD1. The CSD1 changes will be included when you create and load the database using the normal installation steps. Bind the new executables to the database ---------------------------------------- You must bind the new executables to your database. The following steps will run the bind step using the new bind files that were included in CSD1. 1) Change directory to the bind directory 2) Issue the command: db2 -tf bindgrnt.fil -l bind.log This process will BIND the WebSphere Data Interchange V3.2 DB2 packages and GRANT execute authority to public. If you changed the bindgrnt.fil script during the initial DB2 setup to specify a different user or group of users instead of "public", then this command will BIND the DB2 packages and GRANT execute authority to that id or group instead. Load data updates ----------------- If you created the database using the base release of WDI 3.2, then later installed CSD1, you should run the loadcsd1.ddl script to update your existing data. If there are steps that you do not want to do, you can comment out the import line by placing a "--" at the beginning of the line. Comments within the script describe what each of the steps will do. To run the script to update the load data for CSD1, do the following: 1) Change directory to the ixf directory 2) Issue the following command: db2 -tf loadcsd1.ddl This process will load the updated messages into the DB2 table, create the UNOA, UNOB, and UNOC code list (validation) tables, add entries to tables that were left empty in the original load data (including the CHARSET code list table), and correct an error on the rule for the sample map. The loading may generate warnings, but it is safe to ignore them. Also, it is normal for many rows may be rejected, because the script does not replace existing code list and translation tables and entries. Table/view permission updates ----------------------------- The grntec32.ddl script was updated to allow PUBLIC access to the database views. Previously, PUBLIC access was only granted to the tables, not the views. Without the proper permissions on the views, users may get authorization errors when performing certain functions with WDI Client. To correct this, the user must run the updated grntec32.ddl script. To run the script: 1) Change directory to the ddl directory 2) If you wish to allow PUBLIC access to the tables and views, go on to step 3. If you wish to grant permission only to specific userids or a group of authorized users, edit the grntec32.ddl script and change "PUBLIC" to the user or group or users that should have access. 3) Issue the following command: db2 -tf grntec32.ddl -l grntec32.log This script can be run against the existing database, even if it has already been run before. ************************************************************** *** END OF WebSphere Data Interchange V3.2 CSD1 README.TXT *** ************************************************************** *** *** (C) Copyright International Business Machines Corp. 2002. *** All Rights Reserved *** Licensed Materials - Property Of IBM *** *** Welcome to WebSphere Data Interchange Version 3.2 *** *** *** For information on how to set up WebSphere MQ for WebSphere Data Interchange see the wdi_mq_setup.txt file in the samples directory. On Windows platforms the WebSphere MQ Services Trigger Monitor does not fully support PROCESS definitions that contain file paths having embedded blank characters e.g. "C:\Program files\". Instead run the WebSphere MQ trigger monitor program runmqtrm as described in wdi_mq_setup.txt. *** Install instructions for WebSphere Data Interchange V3.2 1) Perform subsequent steps as a user with DB2 administrator authority. 2) After the InstallShield installation, the directory structure within the installation directory is as follows: bin bind ddl ixf include lib runtime runtime/adf runtime/aex runtime/dicmd runtime/dicts runtime/dtds runtime/edi runtime/eex runtime/fak runtime/prt runtime/qry runtime/rcv runtime/rpt runtime/trk runtime/wrk runtime/xex runtime/xml samples * Additional directories may be created for use by InstallShield. These are used for things like keeping uninstall information, and the Java Virtual Machine binaries. 3) Change directory to the ddl directory 4) Issue the command: db2 create db ediec32e This process will create the database. When this process has completed successfully the database has been built. Once the database has been created, issue the command: altrec32 This process will alter some of the default parameters related to log file size and number of primary and secondary logs. 5) Change to the DB2 directory which contains the bind files for the DB2 utilities. - If installing on Windows, this typically has a name like C:\Program Files\SQLLIB\bnd. - If installing on AIX, this typically has a name like /u//sqllib/bnd, where is the id of the instance owner. (See DB/2 Quick Beginnings "Binding Database Utilities") 6) Issue the following commands: db2 connect to ediec32e db2 bind @db2ubind.lst messages bind.msg grant public db2 bind @db2cli.lst messages clibind.msg grant public db2 connect reset Note for AIX installations: You may need to specify a different file for the messages for example /tmp/bind.msg, if you do not have write authority to the current directory. 7) Change the current directory back to the ddl directory. 8) Issue the command: db2 -tf ediec32.ddl -l ec32.log This process creates the WebSphere Data Interchange V3.2 tables, indices, views, etc. 9) The next step will issue GRANT statements necessary for DI Client access to the newly created tables. The default is to issue GRANTs to public. You may wish to change public to specific userids or a group of authorized users. 10) Issue the commands: db2 -tf grntec32.ddl -l grntec32.log 11) Change directory to the ixf directory 12) Issue the following command: loadec32 This process will load initial data into the DB2 tables. The loading may generate warnings, but you can just ignore them. 13) Change directory to the bind directory 14) The next step will issue GRANT statements necessary for WebSphere Data Interchange Server access to the newly created tables. The default within bindgrnt.fil is to issue GRANTs to public. You may wish to change public to specific userids or a group of authorized users. 15) Issue the command: db2 -tf bindgrnt.fil -l bind.log This process will BIND the WebSphere Data Interchange V3.2 DB2 packages and GRANT execute authority to public. 16) The installation for the WebSphere Data Interchange V3.2 is complete. Notes on setting the PATH: For Windows installations, the bin directory for WDI 3.2 is added to the end of your current path. If you have another version of WDI installed on your system, you need to change your path to make sure that the WDI 3.2 bin directory comes before any other versions of WDI in your PATH. If other versions of WDI executables are found in your path, you may receive database errors such as a -818, since the executables from other versions are not bound to the EDIEC32E database. For AIX installations, there is a script in the samples directory that can be used to set up the WDI environment variables. To use this script, enter the command: . setdienv.sh This command can also be run from within your .profile when you login. By using the "." followed by a blank, this will set the variables in the current environment. Otherwise, the environment variables are only set for the duration of the script. *** Install verification steps 1) Change directory to the samples directory 2) Enter the command: wditest This will start a batch file (Windows) or shell script (AIX) to set up environment variables and run a translation using the sample map and data provided. The environment is restored at the end of the test. If the installation is successful, you should see the following output: DI Translator Started, build date: (WDI build date) DI Translator processed your request. DI Translator shutdown If error(s) are written to the console or to the prtfile (in the samples directory), check the messages and take appropriate corrective action. *** Setting up a TCP/IP alias for remote access to AIX databases For improved performance when accessing an AIX database from the WDI Client, use of a TCP/IP alias is suggested. This also prevents certain performance related database errors. To set up a TCP/IP alias for a database do the following steps using an id with db2 sysadm authority: You will need to substitute your local values for the following: is the service name in /etc/services for the DB2 port is the host name for the machine is the tcpip node name you want to define is the database name is the database alias Issue these commands one time for the machine to create the TCP/IP node: db2set DB2COMM=tcpip db2 update dbm cfg using svcename db2 catalog tcpip node remote server Then for each database, you will define an alias by issuing the following command: db2 catalog database as at node For example, if your system had the following local values: db2tcp01 is the service name in /etc/services for the DB2 port wdihost is the host name for the machine wditcp is the tcpip node name you want to define EDIEC32E is the database name WDITCP32 is the database alias you want to use You would issue the following commands: db2set DB2COMM=tcpip db2 update dbm cfg using svcename db2tcp01 db2 catalog tcpip node wditcp remote wdihost server db2tcp01 db2 catalog database EDIEC32E as WDITCP32 at node wditcp When remote DB2 clients connect to the EDIEC32E database, they can use the WDITCP32 alias for the database name. If you want to define additional TCP/IP aliases for that system, you only need to issue the "db2 catalog database" command for the other databases. You do not need to define the node again. For more information, refer to your DB2 documentation. *** Uninstall instructions for WebSphere Data Interchange V3.2 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.2 README.TXT *** *********************************************************