EBCDIC to ASCII conversion

Hello experts,
i'm performing EBCDIC to ASCII conversion in our system and the export (command R3SETUP dbextr.r3s) terminates with the error :
EXP) TABLE: "MCDYNTYPEN"
(EXP) TABLE: "MCDYNUM"
DbSl Trace: Error -904 in function exec_cached_fetch
(EXP) ERROR: DbSlExeRead: rc = 99, table "MCHA"
(SQL error -904)
error message returned by DbSl:
DbSl Trace: SQL error -904 with reason code 13
Resource limit exceeded. Job=323987/DEVCPC/R3LOAD
#STOP: 20100416175601
Thank you,

Once more the installation stopped with error...
ERROR 2010-07-07 17:33:50 DBR3LOADEXEC_IND_DB4ASCII R3loadPrepare:0
Child exited with error: rc = 2
child_pid = 3
See logfile SAPAPPL0.log for further information
ERROR 2010-07-07 17:34:33 DBR3LOADEXEC_IND_DB4ASCII R3loadPrepare:0
Child exited with error: rc = 2
child_pid = 3
See logfile SAPAPPL1_10.log for further information
.ERROR 2010-07-07 17:36:01 DBR3LOADEXEC_IND_DB4ASCII R3loadPrepare:0
Processes started: 46
Ended with error: 2
load tool ended with error.
See above SAP*.log errors.
Error: Can not unlock the LogWriter.
Possible reasons:
No permissions to set the lock
Error: Can not lock the LogWriter.
Possible reasons:
No permissions to set the lock
Error: Can not unlock the LogWriter.
ERROR 2010-07-07 17:36:04 DBR3LOADEXEC_IND_DB4ASCII InstallationDo:0
Phase failed.
The message in "SAPAPPL0.log" is that
"(IMP) ERROR: SQL statement failed: DROP TABLE "MCHA"
MCHA in *LIBL not table, view, or physical file.
" and in "SAPAPPL1_10.log" is
"#Trying to create primary key "S602+0"
(IMP) ERROR: CREATE statement failed for object "S602"
     (ALTER TABLE R3DEVDATA/"S602" ADD CONSTRAINT "S602+0" PRIMARY KEY ( "MANDT", "SSOUR", "VRSIO", "SPMON", "SPTAG", "SPWOC", "SPBUP", "VKORG", "VTWEG", "ZZIDIWTIS", "PRODH", "MATNR", "WERKS" ))
DbSlExecute: rc = 99
(SQL error -603)
error message returned by DbSl:
Unique index cannot be created because of duplicate keys. "

Similar Messages

Downtime for EBCDIC to ASCII conversion

Hello,
we have performed successfully an EBCDIC to ASCII conversion for a client's development system.
The total downtime was about 24 hours.
The customer though, refuses to have downtime of their production system, since it severely affects their systems.
Is there a possibility not to have any downtime for an EBCDIC to ASCII conversion ?
We were thinking as alternatives to build a second productive system, do the conversion there and after finishing, to apply journal receivers from the real production system. This would minimize their downtime to the backup time of the production system and the time needed to apply the journal receivers ?!?
Has anyone performed such a task ?
Would this be feasible (we would have to apply journals from an EBCDIC system to an ASCII system)
Thank you very much
Katerina Psalida

Hi Katerina,
applying journal changes from the EBCDIC system to the ASCII system will not work for several reasons, primarily because the journal keeps track of the journaled tables through an internal journal ID, which will not be the same after the EBCDIC to ASCII conversion. Technically it would not work because the data in the journal entries is kept very low-level, so a conversion from EBCDIC to ASCII during apply is not implemented. Also, the journal entries are based on the relative record numbers in the table, and after the conversion, the relative record numbers will not necessarily be the same.
I am not aware of a zero-downtime conversion option. You can speed up the conversion if you use the "Inplace" conversion option. Did you use that when you measured the 24 hours downtime at the test system? If not, you should give the Inplace option a try. Depending on your data, it could reduce the downtime significantly.
Kind regards,
Christian Bartels.

Convert JMS Headers from EBCDIC to ASCII when using JMS Bridge (WLS - WMQ)

I have a Java app on Weblogic 11g using a Message Bridge to talk JMS with IBM Websphere MQ. The MQ server is running on IBM z/OS platform which uses EBCDIC encoding. I need to use the Weblogic message selector feature to filter messages on the bridge coming from Websphere MQ. But the JMS Headers of MSGs posted by WMQ are in EBCDIC format. How can I instruct MQ to convert the msg headers to ASCII before put on the bridge? Is there any flag on bindings config file? Or can I set some WMQ specific header before sending the msg on WLS side?
Thanks in advance.

Hi,
Such option is not possible in weblogic but I think this property will help you with in MQ.
Property - Convert EBCDIC newline
Description - EBCDIC code pages contain a new line (NL) character that is not supported by the ASCII code pages (although some ISO variants of ASCII contain an equivalent). If messages are sent from a system that uses EBCDIC code pages (for example, a z/OS system) to a system that uses ASCII, you can control how the EBCDIC newline character is converted into ASCII format.
The default value is NL_TO_LF, which means that the EBCDIC NL character (X'15') is converted to the ASCII line feed character LF (X'0A') for all EBCDIC to ASCII conversions. To convert the EBCDIC NL character according to the conversion tables on your operating system, click TABLE. Note that the results of a TABLE conversion can vary from platform to platform and from language to language; even on the same platform the results might vary if you use different coded character set identifiers (CCSIDs). To convert ISO CCSIDs using the TABLE method and use the NL_TO_LF method for all other CCSIDs, click ISO.
Registry Stanza Key - ConvEBCDICNewline
Also, the MQSeries (not MQSC) adapter provides the data conversion property may handle this conversion as well.
Regards,
Kal

Reg EBCDI to ASCII conversion

Hi,
our project is converting from EBCDIC to ASCII conversion,
we need to some changes for the programs, shown in T-CODE SLIN, if any one have any document , please help me in this regard how to correct the changes required.
Regards.
venkat

hi
data:pack type p deimals 2.
first pass char value to pack and then from pack pass it to floting point variable.
Regards
Neha

EBCDIC to ASCII data conversion

Hi,
We have JDE system as source to bring data into BW. Howvever the format of the data is in EBCDIC and the data looks junk with out converting the same to ASCII.
A quick research showed me that there are 3rd party tools to convert the data from EBCDIC to ASCII.
Just wondering whether is there a function in BW system which takes care of this conversion?
any thoughts? did any one come across this situation ?
Inputs appreciated.
Regards

Hi
Thanks for your response.
Now where this class has to be applied ?...
what does exactly this class do? can you share some insights on this ?
Thanks

GUIA Conversion EBCDIC to ASCII

Dear Gurus!!
I'm needing a manual or guide of the conversión EBCDIC to ASCII in the V5R3M0 iSeries. i570.
Can you help me?
Best Regards.
Luis

Hi Morga,
it has nothing to do with the OS release. You can stay on EBCDIC because of that as you found out.
But:
All release newer than 4.6D are in ASCII and UNICODE ONLY!
=> If you want to upgrade to e.g. ECC 6.0, you MUST convert to ASCII first ...
hope this helps,
Regards
Volker Gueldenpfennig, consolut.gmbh
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

EBCDIC - ASCII Conversion for XI File Adapters

All:
Does XI File Adpater have built-in capability to convert EBCDIC to ASCII and vice versa? We also need to handle pack decimals. All mainframe file based integration scenarios require this capability.
If there's no built-in capability available, are there any Java APIs available from SAP XI bundle some where.
Thanks and appreciate your feedback.

Hi,
Unfortunately, there is no built-in EBCDEC-ASCII conversion in XI. There are examples when you do a search on GOOGLE.
The java function can be used in either java mapping or adapter user-module.
Regards,
Bill

Convert EBCDIC to ASCII and ASCII to EBCDIC in PI7.0 SP14

Wea re going to be implementing PI7.0 SP14.
I am writing the technical specification for an inbound/outbound interface into/out of ECC 6.0!
I need to convert the File that is created out of SAP into EBCDIC in PI and for the inbound convert the file from EBCDIC into ASCII for import into ECC.
I have more than one way to this...
The ways I have found so far are:
Use MessageTransformBean, use TextCodepageConversionBean, XmlAnonymizerBean, using the File Encoding field on the File/FTP Adapter, XSLT mapping or Java mapping!
I have checked the OSS Note 821267, but this doesn't help.
I am sure all these methods have pros and cons...
What would be the most efficient method of changing this? It will be running hourly and have upto 6000 entries an hour - each way!

Hi Barry,
I think the most efficient way in my thinking is XSLT and Java mapping.
For java mapping u just need to get thye jar file.I believe that the encoding cp285 / cp500 is EBCIDIC. Try printing
byte [] msg = .. // whatever
System.out.println(new String(msg, "cp285"));
if you get an exception saying Cp285 is unknown you may need an international version of the JRE, depends on the version you're using.
Also u can use this in reverse.
Please see this post:
Re: Handling Packed decimals in XI
regards
Aashish Sinha
Edited by: Aashish Sinha on Mar 25, 2008 6:07 PM

Binary to Ascii conversion

Dear experts,
For BINARY to ASCII conversion, please give me some example programs (using methods).
Thanks a lot in advance.
Regards,
Matt

Hi,
I think this link will be useful for you. Please go throught this link....
http://help.sap.com/saphelp_erp2004/helpdata/en/d6/0dba8f494511d182b70000e829fbfe/frameset.htm
Hope it will helps

Time comparision of ASCII conversion VS Unicode conversion

In general how does the runtime of a Unicode conversion compare to that of the ASCII conversion? For example, you perform the Unicode conversion on the same hardware on which you completed the ASCII conversion. The ASCII conversion takes 20 hours. Does the Unicode conversion take a similiar time?
thanx
Mark

Hi Mark,
first an answer, that comes only now, because my user was somehow locked or whatever ...
How long does it take compared to the ASCII CPC ?
As you are a latin-1 customer I guess, you could make use of the InPlace version in both attempts.
The InPlace Unicode CPC Export will take 6-7h or the time of the Ascii Export if this was longer. The reload will take about 3h only.
The major problem is on some other edge:
The combined upgrade only works fine if you run all the scans and this will take several days ... even when they are "pretty useless" in your case. Therefore, I would recommend an ECC6 upgrade without unicode and then the unicode conversion directly afterwards - in a short special technique, that I used several times already.
If it is "just" from 4.6C ASCII to ECC 6.0 Unicode, the week will be fully sufficient including all backups - which can sometimes run in parallel. (at least with my ideas)
I did something like that from 4.6B ASCII to ecc5 Unicode on one weekend from friday evening until sunday afternoon. (for sure, depending on the systemsize)
Regards
Volker Gueldenpfennig, consolut.gmbh
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

Ebcdic to ascii file translation woes

I am trying to convert an ebcdic file into an ascii file but i am running into some difficulties.
The translation works fine, but it outputs everything onto one line when opened up in notepad on NT, with a symbol "ٱ" where a new line should be. When the same file is pasted into WordPad these sybols are interpreted into new lines.
Is there a way i can get the sybols replaced by new lines when opened up in Notepad?
import java.io.*;
class FileReaderDemo2
     public static void main (String args[])
          try
               //create and input stream reader froman ebcdic file
               FileInputStream inputStream = new FileInputStream ("input.ebc");
               //convert from ebcidic to unicode
               InputStreamReader inputReader = new InputStreamReader(inputStream,"Cp500");
               //attach a buffer to it
               BufferedReader buffReader = new BufferedReader (inputReader);
               System.out.println("Character Encoding is: " + inputReader.getEncoding());
               //output file in ascii Cp1252 from unicode
               OutputStreamWriter outWriter = new OutputStreamWriter(new FileOutputStream("Output2.txt"),"Cp1252");
               String str = null;
               while ((str = buffReader.readLine()) !=null)
                    outWriter.write(str +"\n");
               inputReader.close();
               inputStream.close();
               outWriter.close();
          catch (Exception e)
               System.out.println("Exception: " + e);

Thanks for that.
I need to do the reverse now, so i have a ascii file i need to convert to ebcidic. Once again the conversion works ok but the output is all on one line.
I've tried
outWriter.write(str + "\n");
and
outWriter.write(str + "\r\n");
and
outWriter.write(str + System.getProperty("line.separator"));
But none of them seem to work.

EBCDIC to ANSI Conversion

Hi,
We have a question from the partner and they want to know how the data from mainframe can be converted from EBCDIC to ANSI format?
Any pointer would be helpful.
Thanks
Umesh

Check out the DB2 z/OS Installation & Setup guide (...and, I think you mean ASCII and not ANSI...)
If you use a typical GG capture process + data pump to send data to/from z/OS to/from unix/linux/windows, then GoldenGate v10+ should automatically convert between ASCII and EBCDIC when the pump sends the data to the remote trail. (It's been a while since I've tried.... But you can use logdump to verify if you have the environment to test with.) See the limitations in the aforementioned guide (e.g., multi-byte characters are not converted, unicode is not converted).
Also, you may have to explicitly add in a conversion parameter if going to/from Nonstop... if you are, see the GG win/unix upgrade instructions for GG v11. It's just one parameter that I'm omitting here so as not to confuse the issue.
Note also that if you're using logdump, there are specific ebcdic commands you can use to view trail data & trail header info on z/OS. Just type "help" in logdump on z/OS for all the options.
If you're attempting to convert any of the unsupported data types -- then you'll probably have to do it in the database post-replication (e.g., Oracle DB has functions to do this), such as loading a staging table with the ebcdic data that is in turn processed and loads your ascii table. (There are probably a number of ways to accomplish this with varying degrees of complexity.)
Cheers,
-m

Problem in converting EBCDIC to ASCII in ODI

Hi All,
I am new to ODI.
I am trying to convert EBCDIC file to ASCII using ODI. Each of my record is of length 140. There is no record separator, but in ODI we need to specify record separator.
So how do i convert this file.
I am using jdbc:snps:dbfile?ENCODING=cp037 in my data server.
IS there any way by which i can tell ODI that the next record is after 140 characters???
Thanks

Yeah, I ended up going the Jython route.
First I created a procedure called "ftpGetEbcdicFile" that takes the following options:
1 Remote Server
2 Remote Login
3 Remote Password
4 Remote Directory
5 Remote Filename
6 Local Directory
7 Local Filename
8 Record Size
This procedure has 2 commands/steps:
ftpGetBinary:
import snpsftp
# Retrieve procedure parameters
remoteServer = '<%=odiRef.getOption("Remote Server")%>'
remoteLogin = '<%=odiRef.getOption("Remote Login")%>'
remotePassword = '<%=odiRef.getOption("Remote Password")%>'
remoteDirectory = '<%=odiRef.getOption("Remote Directory")%>'
remoteFilename = '<%=odiRef.getOption("Remote Filename")%>'
localDirectory = '<%=odiRef.getOption("Local Directory")%>'
localFilename = '<%=odiRef.getOption("Local Filename")%>'
# Build full file paths
remotePath = remoteDirectory + "/" + remoteFilename
localPath = localDirectory + "/" + localFilename
# Execute ftp
ftp = snpsftp.SnpsFTP(remoteServer, remoteLogin, remotePassword)
try:
     ftp.get(remotePath, localPath, 'BINARY')
finally:
     ftp.close()
and insertNewlines:
# Retrieve procedure parameters
localDirectory = '<%=odiRef.getOption("Local Directory")%>'
localFilename = '<%=odiRef.getOption("Local Filename")%>'
recordSize = <%=odiRef.getOption("Record Size")%>
localPath = localDirectory + "/" + localFilename
# There is probably a better way to do this
tmpPath = localDirectory + "/" + localFilename + "~"
inputFile = open(localPath, 'rb')
outputFile = open(tmpPath, 'wb')
while 1:
     line = inputFile.read(recordSize)
     if line:
          outputFile.write("%s%c" % (line, 0x15))
     else:
          break
outputFile.close()
inputFile.close()
Then I created package that calls the procedure with the desired options. It still needs some work, but I think it will get the job done for now.
Any advice or corrections from the ODI gurus out there?

String to Packed ASCII conversion

Hi,
Can anyone provide any examples or Algorithm to convert 'ASCII' to 'Packed ASCII'
Packed ASCII format is used in HART protocol
Thanks.

Hi,
Packed ASCII is noting but a data compression technique.
HART makes limited use of data compression in the form of Packed ASCII. Normally, there are 256 possible ASCII characters, so that a full byte is needed to represent a character. Packed ASCII is a subset of full ASCII and uses only 64 of the 256 possible characters. These 64 characters are the capitalized alphabet, numbers 0 through 9, and a few punctuation marks. Many HART parameters need only this limited ASCII set, which means that data can be compressed to 3/4 of normal. This improves transmission speed, especially if the textual parameter being communicated is a large one.
    Since only full bytes can be transmitted, the 3/4 compression is fully realized only when the number of uncompressed bytes is a multiple of 4. Any fractional part requires a whole byte. Thus, if U is the number of uncompressed bytes, and T the number of transmitted bytes; find T = (3*U)/4 and increase any fractional part to 1. As examples, U = 3, 7, 8, and 9 result in T = 3, 6, 6, and 7.
    The rule for converting from ASCII to Packed ASCII is just to remove bits 6 and 7 (two most significant). An example is the character "M". The full binary code to represent this is 0100,1101. The packed binary code is 00,1101. The rules for conversion from packed ASCII back to ASCII are (1) set bit 7 = 0 and (2) set bit 6 = complement of packed ASCII bit 5.
    Note that, with some exceptions, HART Slaves don't need to do the compression or know anything about the compression. They simply store and re-transmit the already compressed data. Again, this is an instance where the more difficult software is placed in the device (Master) that is more capable of dealing with it.
Thanks and Regards
Himanshu Goyal
Thanks and Regards
Himanshu Goyal | LabVIEW Engineer- Power System Automation
Values that steer us ahead: Passion | Innovation | Ambition | Diligence | Teamwork
It Only gets BETTER!!!

Convert EBCDIC to ASCII

Hi all,
We are using XI 3.0 SP 10 and I have a scenario where I only need to retrieve a file (via FTP) and deliver it to a file share inhouse. There is no need for any mappings etc. But the file Iam retrieving is in EBCDIC and I would need to convert this into ASCII when delivering to fileshare. I have set up the communication channels and this works fine. But what would be the easiest way to convert the EBCDIC file to ASCII?
Regards,
Fredrik

Hi Fredrik,
There is an alternate way of acehiving the same using a java program in the operatingsystem command option of File adapter.
Steps:
1. Write a java program to read EBCDIC file and convert into ASCII file(Using codepages).
2.Create a jar for the above program and store it in a server directory.
3.Write one shell script/batch file call the java program and send command line parameters as filenames.
4.In XI File adapter -Operating system command use the Shellscript/Batch file name (Complete path)and give %F for filenames
Eg. /usr/sap/serverdir/convert.sh %F %F
For more details refer the following link:
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm">XI File adapter</a>
Regards,
Ananth

EBCDIC to ASCII conversion

Similar Messages

Maybe you are looking for