PK94606: ADF TO EDI DT PROCESSING DOES NOT WRITE ADF INPUT TO EXCEPTION FILE UPON ENCOUNTERING VALIDATION ERRORS ON EDI SIDE.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Environment: WDI 3.2.1 for z/OS with current maintenance.
  
  WDI Data transformation processing of ADF to EDI does not write
  failed input ADF transactions to the exception file when
  EDI validation errors (severity 08) are encountered.  In this
  case, there are 3 ADF transactions in the input file. The first
  is clean, the 2nd and 3rd encounter:
  
  Message: TR0011 Severity: 08
   The standard defines data elements SAC02, SAC03 as required,
   but all are missing from the transaction.  At least one must
   be present.
  
  The severity of the error depends on the map rule,
  "Acceptable error level".  If no segment or element level
  errors are allowed, then the above msg results in severity 08.
  The expectation is that the first good transaction is
  transalted and output to the EDI file while the 2nd and 3rd
  are skipped and not written to the output. This is working
  properly.  The problem is that the for the two failed
  tranasctions, the ADF data is not being copied to the excpetion
  file (dd FFSEXCP).
  
  Note: ADF input transaction which encounter RU0001 (rule not
  found) are written to the exception file, as expected.
  
  Keywords: rc8 rc08 condition code 8 08 sev8 severity8 excpfile
  
  Test files:
  On GSA:
  O855X4010_edited.eif
  prtfile_0713a.txt
  On Ralvsk:
  KIRKWOO.PMR74522.APPLIN.FB1063
  KIRKWOO.PMR74522.APPLIN.FB1063.ALLBAD
  KIRKWOO.PMR74522.JCL
  

Local fix

Problem summary

• ADF to EDI DT processing does not write ADF input to
  the exception file upon encountering validation errors
  on the EDI side.
  

Problem conclusion

• Whether or not input data is written to the exception
  file is predicated on a flag value returned to the Utility
  from the Message Broker. In the case of output validation
  errors, this flag was not being set. The code will be
  changed to set this flag when an output validation error
  causes the data transformation to fail.
  

Temporary fix

Comments

• Applies to all platforms, 3.2 CSD29, 3.3 SFP3
  WDI 3.3 APAR is PKxxxxx
  

APAR Information

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

  PK92279

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

  UK49565

Modules/Macros

• CPP      EDIMBCNI EDIMBCNI EDIVAICL EDIVAICL
  H        EDIUTHDR EDIUTHDR
  

Fix information

• Fixed component name

  WEBS DI ZOS

• Fixed component ID

  5655I4003

Applicable component levels

• R330 PSY UK49565

     UP09/10/15 P F910

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.