cancel
Showing results for 
Search instead for 
Did you mean: 

Tranports from EBCDIC 46.c to Unicode ECC6.0

gfarmer
Explorer
0 Kudos

Hey

We want import some Transport Request from our EBCDIC 4.6C to our Unicode ECC6.0. But we got always follow Error:

HALT: This program has version 6.14, the file is not an R3trans data file. Please contact the SAP support

We use the last Version of TP and R3trans in both System's.

I've tried to copy the Data and Cofile to other Codepage and import but also not help.

When i do this from our ASCII 4.6C to our Unicode ECC6.0 it will work. They have the same Version of TP and R3TRANS.

Has anybody any Hint for me?

Thank you

Gerhard

Accepted Solutions (0)

Answers (4)

Answers (4)

0 Kudos

Hello Gerhard,

indeed this issue is a little tricky and since I processed now a few messages I created SAP note

1078252

to describe the handling. Unfortunately, it is not yet released and translated but will be soon. The trick is that the Unicode R3trans is able to read ASCII data which the EBCDIC R3trans cannot produce. How does it work?

1. you need an ASCII R3trans version


If you have an ASCII kernel somewhere in your system landscape you need to have at least patch 2317 (46D release), 173 (640 release) or 100 (700 release). It doesn't matter which release you use.

2. adopt the transport profile for the EBCDIC system


Add a line with "SID/R3TRANSOPTIONS = compress=no", where SID is the system ID of the exporting EBCDIC system. Compressed transport files are not allowed here. This needs to be done only once.

3. convert the data file

R3trans -c /usr/sap/trans/data/Rnnnnnn.SID.EBCDIC /usr/sap/trans/data/Rnnnnnn.SID.ASCII

The ASCII R3trans has to be called as above for the conversion. Rnnnnnn.SID.EBCDIC is the data file in EBCDIC coding and Rnnnnnn.SID.ASCII the file in ASCII. You might rename the files in a right manner to keep the original transport order number.

4. import it to the Unicode system

Probably you have to create a new cofile (with command TP 'createcofile ...') and afterwards you can import it to your Unicode system.

Hope this explains the procedure. I will update your customer message once the new SAP note has been released and translated.

Best regards

René Lang

SAP on System i Development

gfarmer
Explorer
0 Kudos

Hey

First of all thanks for your comments.

Second, SAP had not replay yet to my Call

The Solution to move the TA to our ASCCII System and then to the Unicode is not possible for us because the Ebcdic System is our Master Development System and in the ASCII System some things missing.

Lg.

Gerhard

Former Member
0 Kudos

Hi Gerhard,

that's why I asked you to open an OSS ticket ...

It was NOT the "solution" like every consultant could do with importing in ASCII and Exporting again.

The solution was, to use the ASCII R3Trans manually and convert the data file so that Unicode can read it ... but I didn't ask the customer in detail for the steps - if necessary I could do this for you ...

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

gfarmer
Explorer
0 Kudos

Hey Volker

It seems that SAP had Problems to give me a solution for my Problem.

Please could you ask the customer for detail how to convert it?

Lg.

Gerhard

tj_wilkinson2
Participant
0 Kudos

Gerhard, please update us with what you find out from SAP. I've wondered and tried something similar in the past and couldn't get it to work. I assumed it was not possible, but now it sounds like it might be. Thank you.

~TJ

Former Member
0 Kudos

Hi Gerhard and TJ,

What Volker suggested is a valid solution, as always.

We did similar things before - basically export from EBCDIC, import into ASCII, then create another transport from the ASCII with all the objects, and import into Unicode.

If only a few objects are needed, I would ask developer to manually download/upload through PC files if possible.

Best regards,

Victor

Former Member
0 Kudos

Hi Gerhard,

tja ...

you are running into a very bad bug now ... it shopuld work, but it doesn't ;-(((

You should open an OSS message with BC-OP-AS4 and ask for a solution. I do have in mind, that the idea was to use an ASCII system "in between" and to convert the transport there ;-(((

(I do have one other customer, that is going this way ...)

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de