How to re-migrate WDI 3.2.1 data to WDI 3.3 for z/OS

Technote (FAQ)


Question

What is the best way to re-migrate all WDI 3.2.1 EDI standards, ADFs, maps, etc. after already having done so via EDIJEXPD?

Cause

Not having current WDI 3.3 for z/OS maintenance led to various conversion issues when migrating from WDI 3.2 to WDI 3.3. What steps should be taken to re-migrate all WDI 3.2 data over again to WDI 3.3 ?

Answer

If EDI standards, ADFs, or maps encounter unexpected conversion problems during the first execution of WDI 3.3 installation JCL, EDIJEXPD, the following steps should be taken to re-migrate the data. See WDI 3.3 Installation Guide for z/OS for references to "Step" numbers below.

  • Apply maintenance (PTFs) to existing SMP/E zone (Step 10).
  • Drop WDI 3.3 EDIDB33E database to start over. This may also be important to reduce the amount of elapsed and CPU time that will otherwise occur during re-import of EDI standards within STEP004 of EDIJEXPD. Because when removing EDI standards, WDI extensively uses DB2 cascade deletes with foreign key relationships, thus significantly increasing CPU time required as compared to when starting over with a new database. (See note below for adding new indexes to greatly improve standards DELETE performance.)
  • Re-run Step 11. Creating Version 3.3 Repository DB2 Objects. Simply re-run your modified EDISDB2 member beginning with the "CREATE DATABASE EDIDB33E..." statement.
  • Re-run Steps 12 - 18 using your already modified JCL.

If you do not wish to re-export the data from your WDI 3.2.1 system, then no need to run Step 17 again to rebuild the control file.

Run Step 18, EDIJEXPD, using previously modified JCL. If you do not wish to re-export the data from your WDI 3.2 system, you can skip JCL STEP001, STEP002, and STEP003. After successful completion of EDIJEXPD, be sure to run DB2 runstats again, job EDIJRNST.

  • Re-run Step 21. Migrate operational data (See APPENDIX B) if you wish to also re-migrate transaction store and management reporting data.

Note: Use SPUFI to add new indexes as follows (as provided under APAR PM06927) 
SET CURRENT SQLID='EDIENU33';

CREATE INDEX EDIENU33.EDISTDSGDV
 ON EDIENU33.EDISTDSGD(STDID,DEID)
 USING STOGROUP EDISG332
   PRIQTY 1000
   SECQTY 400
   ERASE NO
 BUFFERPOOL BP0
 CLOSE NO;

CREATE INDEX EDIENU33.EDISTDTXDV
 ON EDIENU33.EDISTDTXD(STDID,SEGID)
 USING STOGROUP EDISG332
   PRIQTY 1000
   SECQTY 400
   ERASE NO
 BUFFERPOOL BP0
 CLOSE NO;


Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Data Interchange
WDI 3.2 for z/OS

Software version:

3.2, 3.2.1, 3.3

Operating system(s):

z/OS

Reference #:

1209342

Modified date:

2013-01-25

Translate my page

Machine Translation

Content navigation