PK65873: BATCH IMPORT OF STANDARD DATA ABENDS, WHEN TRANSACTION ID SPECIFIED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When importing standard data using batch and specifying a
  specific transaction ID to import.  WDI 3.2 on z/OS reports
  the follow message:
  .
  FF0588 Command: PERFORM IMPORT WHERE CTLFILE(IMPORT)
  EI0047 ****** Importing Standard X12V4R3 ******
  EI0049 Standard X12V4R3 has been replaced in the data base.
  EI0049 Transaction set X12V4R3 820 has been replaced in 820 has
  been in the data base.
      Message: EI0012 Severity: 12
  Data Base error--Function = 0024, DB2 Table = EDIVSCSU, Key =
  820 HBPR, DB2 return code = 00012,-0530. ****EI_LOC=03709,
  CB_RC=00012, CBEC=-0530
  EI0044 No record in import file matches the key ID X12V4R3 in
  category 1.
  FF0514 Import processing has completed successfully on behalf of
  a PERFORM IMPORT
  .
  The standard seems to import, however when you view in the WDI
  3.2 Client, only the standard details are seen.  That is no
  element records for the transaction have been imported.  This
  same issue occurs in WDI 3.2 Multiplatform batch imports.
  .
  TESTCASE FILES CAN BE PROVIDE ON REQUEST.
  .
  KEYWORDS: WDI, IMPORT, BATCH, STANDARD, TRANSACTION
  

Local fix

• Option 1).  Use the WDI 3.2 client to select only the 820
  transaction to import from the X12V4R3.eif file into the
  database.
  
  Option 2).  Use the WDI 3.2 client to select only the 820
  transaction to import from the X12V4R3.eif file, into the
  development database.  Then export only the X12V4R3 820 standard
  out of the development DB into a new .eif file.  You can then
  import without specifying the "820" transaction on the CTLFILE
  for position 85.  When you do not specify a transaction, then
  all transactions in the standard are imported.  Since only the
  820 transaction would be in the new eif file, you would the only
  would get only desired 820 transaction imported.
  

Problem summary

• When importing standard data using batch and specifying a
  specific transaction ID to import.  WDI 3.2 on z/OS reports
  the follow message:
  .
  FF0588 Command: PERFORM IMPORT WHERE CTLFILE(IMPORT)
  EI0047 ****** Importing Standard X12V4R3 ******
  EI0049 Standard X12V4R3 has been replaced in the data base.
  EI0049 Transaction set X12V4R3 820 has been replaced in 820 has
  been in the data base.
  Message: EI0012 Severity: 12
  Data Base error--Function = 0024, DB2 Table = EDIVSCSU, Key =
  820 HBPR, DB2 return code = 00012,-0530. ****EI_LOC=03709,
  CB_RC=00012, CBEC=-0530
  EI0044 No record in import file matches the key ID X12V4R3 in
  category 1.
  FF0514 Import processing has completed successfully on behalf of
  a PERFORM IMPORT
  .
  The standard seems to import, however when you view in the WDI
  3.2 Client, only the standard details are seen.  That is no
  element records for the transaction have been imported.  This
  same issue occurs in WDI 3.2 Multiplatform batch imports.
  

Problem conclusion

• Import by Transaction doesn't work in batch when on DB2.
  The DB2 referential integrity rules added to the Standards DB
  Tables require that the import file be in Y1, Y2, Y4, Y6 order
  to get header objects added before details (Y3, Y5, Y7). The
  Import by transaction code requires a Y1 Y2 Y3 Y4 Y5 order so
  that segments and elements specific to the transaction can be
  identified. 3.3 documentation implies that EXPORT can handle
  export by transaction, but import is not mentioned for standards
  - for a reason.
  WDI will be changed to prevent the abend that occurred when
  a transaction was requested to be imported. The code will also
  attempt to import a standard transaction, but it will include
  all segments and elements of the standard (Y4 and Y6). Only
  required transactions (Y2) and details (Y3, Y5) are imported
  so the space required will be signficantly reduced.
  The best option is to use the WDI Client to import a
  single standard transaction. The Client uses a different
  technique to import and thus handles the selection and
  DB2 referential integrity constraints better.
  

Temporary fix

Comments

• Include in WDI 3.2 CSD27
  Include in WDI 3.3 SPF2
  WDI 3.3 APAR is PKxxxxx
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

  PK64573

• APAR is sysrouted TO one or more of the following:

  UK36376

Modules/Macros

• C        EDIEIRW  EDIEIRW
  

Fix information

• Fixed component name

  WEBS DI ZOS

• Fixed component ID

  5655I4003

Applicable component levels

• R330 PSY UK36376

     UP09/01/29 P F901

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.