PO03292: IBASE IS NOT STORING IMPORT SPECIFICATIONS IN A LOCALE-INDEPENDENT FORM. THERE IS A BUG IN THE

APAR status

• Closed as fixed if next.

Error description

• Problem occurs for any non English Locale. If import
  specifications, created with ibase 891,  are using
  transformations.  then when they are opened up with version
  895, i2 ibase 895 errors with a Type mismatch error error 13
  
  Fehler #13 trat auf:
  id5ImportExport
  id5ImportExport - CTFActionCondition:Initialise
  id5ImportExport - IidTransformAction:Initialise
  id5ImportExport - CTransformField:Initialise
  CTransforms:Initialise
  idTransformer:Initialise
  idImportSource:Initialise
  idImport:Initialise
  FImport:LoadExistingSpecification
  

Local fix

• Here are the SQL statements that they needed to run on their
  database in order to fix their import specifications:
  
  UPDATE _DataStore SET Data = CAST(REPLACE(CAST(Data AS
  nvarchar(max)),'=Wahr<','=True<') AS ntext)
  WHERE RecordType = 30
  
  UPDATE _DataStore SET Data = CAST(REPLACE(CAST(Data AS
  nvarchar(max)),'=Falsch<','=False<') AS ntext)
  WHERE RecordType = 30
  
  Note 1.) Every time they get an identical Type Mismatch error
  they will need to re-run these SQL statements; this will occur
  whenever a user with a 'broken' machine tries to open or run an
  import specification that has been saved or updated by a user
  with a 'non-broken' machine
  Note 2.) We would require a different translation for
  true/false for each language affected if a different language
  (Polish, Slovak etc) was being used than for German as was the
  locale in this instance.
  

Problem summary

• A workaround has been provided.  The defect is logged for the
  next release.
  

Problem conclusion

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:

Modules/Macros

• NA
  

Fix information

Applicable component levels

• R895 PSY

     UP