IGNORING CONVERSION ERRORS of OPEN DATASET

[Former Member]

We've successfully upgraded + converted SAP ECC 5.0 Non-Unicode to SAP ECC 6.0 Unicode system. We also made necessary adjustment for OPEN DATASET.

In ECC 5.0 Non-Unicode system, if there is any conversion error, SAP will ignore the error and generate the text file with corrupted char. But in ECC 6.0 Unicode system, dump will happen if there is any conversion error, no file is going to be generated.

We understand we can avoid this error by using IGNORING CONVERSION ERRORS options, but I am curious is there a global setting which can set this attribution to "IGNORING CONVERSION ERRORS"?

Thanks

James

[Former Member]

We've successfully upgraded + converted SAP ECC 5.0 Non-Unicode to SAP ECC 6.0 Unicode system. We also made necessary adjustment for OPEN DATASET.

In ECC 5.0 Non-Unicode system, if there is any conversion error, SAP will ignore the error and generate the text file with corrupted char. But in ECC 6.0 Unicode system, dump will happen if there is any conversion error, no file is going to be generated.

We understand we can avoid this error by using IGNORING CONVERSION ERRORS options, but I am curious is there a global setting which can set this attribution to "IGNORING CONVERSION ERRORS"?

Thanks

James

[pranab_kumarjha]

Hi Gang Yang,

As far as I remember this becomes a manual activity for custom programs for Open Dataset.

I dont think there is a universal setting for this. For one of my client back in 2008, we have to manually change every place where Open Dataset was called.

[Former Member]

It already took time for us to add non-unicode option specifically. But we do not realize SAP change this behaviors at that time, this means we must re-change all open dataset statement again.

[former_member427106]

Hi Guys,

As I checked here, there is no global setting in SAP side to correct it. But did you tried to change the settings in Operational System?

I'm facing this issue when moving the SAP application server from Unix to Linux.