IC98936: TRANSLATION FAILING WITH ODBC:MFC INTERNAL ERRORS WHEN UTILIZING LOOKUP TABLES IN THE MAP.

APAR status

• Closed as fixed if next.

Error description

• Data is not translating as expected or exported data is not the
  same as it had been in patch 2 for Gentran:Server for Microsoft
  Windows version 5.3.1.
  
  Audit log errors:
  
  3-1-204   Error  ODBC: MFC database exception in
  Program/RETCODE: Translation/1009
  MFC internal error: unable to load error string from resource.
  
  3-1-203   Error  ODBC: MFC database exception encountered in
  Translation
  Error: MFC internal error: unable to load error string
       from resource.
  SQL Statement: SELECT
  "PartnerKEY","TableName","Item","Description","Text1","Tex
  t2","T ext3","Text4"  FROM "Lookup_tb" WHERE "PartnerKEY" is
  NULL
  

Local fix

• RTC - 409246
  CF/CF
  No Workaround Available
  

Problem summary

• User Affected: Customers updating Trading Partner Lookup Tables
  during translation.  Problem was limited to the initial release
  of Fix Pack 5.3.1.3.
  

Problem conclusion

• Problem Description: ODBC Connection errors could be reported
  during translation if the map included updates to the Trading
  Partner Lookup Table.
  
  
  Resolution Summary: The Trading Partner Lookup Table DB ODBC
  Connection was changed to remove the use of the Cursor Library.
  The 5.3.1.3 Fix Pack was reissued with the defect correction.
  

Temporary fix

Comments

APAR Information

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

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

Fix information

Applicable component levels

• R531 PSY

     UP