Sponsored Content
Full Discussion: Ebcdic to ascii
Top Forums Programming Ebcdic to ascii Post 302911406 by Corona688 on Thursday 31st of July 2014 01:25:55 PM
Old 07-31-2014
EBCDIC can be more complicated than it looks. "blind" converters like dd and the C code above don't take into consideration some obscure multi-byte integer sequences. (This comes up every time, but can I remember what they're called? No...) Can you give us some context please?
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

ascii to ebcdic conversion

Hello, I need a program for ascii to ebsdic conversion. If anybody can help, it'll be greatly appreciated. Thanks. (1 Reply)
Discussion started by: er_ashu
1 Replies

2. UNIX for Dummies Questions & Answers

Conversion from EBCDIC to ASCII

when i try to convert a mainframe EBCDIC file to ASCII ,i dont see correct file this is the source file ... (3 Replies)
Discussion started by: venkatvelpula
3 Replies

3. UNIX for Dummies Questions & Answers

Help! EBCDIC format to ASCII

Hi everyone, I have a 70MB EBCDIC file, with record length 102, block size 32742 and IBM standard label. I commanded dd if=input file of=outputfie ibs=32742 cbs=102 conv=ascii but I still don't get a viewable file under ASCII. Can anyone told me what's the problem? Do I need... (12 Replies)
Discussion started by: hrchl86
12 Replies

4. Shell Programming and Scripting

EBCDIC Format to ASCII

Hi, we have source file with EBCDIC format(Main Frame files) where we receving from source system. I would like to convert the EBCDIC format file to unix systemformat(ex: .csv,txt ) I have wrote script like: dd if=<SRCPATH>yyy.xxx.RB065 of=<SRCPATH>/output.csv ibs=800 cbs=80... (8 Replies)
Discussion started by: koti_rama
8 Replies

5. UNIX for Advanced & Expert Users

Conversion of data - ebcdic to ascii

Hi, I want to convert ebcdic values to ascii values. Are there anyany specific c++ libraries with g++ compiler, which can do it ? gcc version 4.1.2 20080704 (Red Hat 4.1.2-54) (0 Replies)
Discussion started by: tostay2003
0 Replies

6. UNIX for Advanced & Expert Users

Conversion from EBCDIC to Ascii OR unicode

I have a file in my Unix ( SOLARIS ) with EBCDIC format...I want this file to read in ASCII OR unicode...Is it possible with UNIX to convert this file on ASCII OR UNICODE format from EBCDIC format? I was searching through web and found only conversion table :( Request Rejected Below is... (16 Replies)
Discussion started by: joshilalit2004
16 Replies

7. Shell Programming and Scripting

Need help for EBCDIC TO ASCII conversion through UNIX

Hi All , We have a mainframe file which is in EBCDIC format.We dont have direct access to mainframe ,client has provided us the mainframe file in unix box.The mainframe file is containing pact data(COMP1 ,COMP2 etc) which are unreadble.Can anyone suggest me how to convert this kind of ebcdic... (7 Replies)
Discussion started by: STCET22
7 Replies

8. UNIX for Beginners Questions & Answers

Check if file is EBCDIC or ASCII format

So, i have this requirement where i need to check the file format, whether it's EBCDIC or ASCII, and based on format retrieve the information from that file: my file is: file1.txt-->this ebcdic file file2.txt-->ascii file i tried below code: file=file1.txt type="`file $file`" i get... (7 Replies)
Discussion started by: gnnsprapa
7 Replies

9. UNIX for Advanced & Expert Users

EBCDIC to ASCII conversion

Hi, I have a input file which is EBCIDIC and it has packed decimals. Can anyone help me to convert EBCIDIC file to ASCII(Need to convert even Packed decimal values also to normal format). Thanks swapna (12 Replies)
Discussion started by: swapna_1990
12 Replies

10. UNIX for Advanced & Expert Users

EBCDIC to ASCII conversion

Hi, We have a mainframe file which is in EBCDIC format.We dont have direct access to mainframe ,client has provided us the mainframe file.The mainframe file is containing pact data(COMP1 ,COMP2 etc) which are unreadble.Can anyone suggest me how to convert this kind of ebcdic file to ascii... (11 Replies)
Discussion started by: swapna_1990
11 Replies
iconv_intro(5)							File Formats Manual						    iconv_intro(5)

NAME
iconv_intro, iconv - Introduction to codeset conversion DESCRIPTION
Conversion of character encoding from one coded character set (codeset) to another is an operation that often has to be performed by the operating system and some applications. For example, the man command supports codeset conversion to allow one set of reference page files to meet the needs of locales that support the same language and territory but different codesets (see man(1)). The following commands and library interfaces give users and application developers direct access to codeset conversion operations: The iconv command converts characters in a data file from one codeset to another (see iconv(1)). The iconv(), iconv_open(), and iconv_close() functions convert a string of characters from one codeset to another (see iconv(3), iconv_open(3), and iconv_close(3)). The iconv command uses these interfaces to convert characters. There are two types of codeset converters: algorithmic and table. Algorithmic converters, which reside in the /usr/lib/nls/loc/iconv direc- tory, are shared libraries with a predefined entry point for invocation by functions in the libiconv.so library. Algorithmic converters are needed for the conversion of multibyte codesets, in part because table converters cannot handle the required number of character values and also because some of these codesets require complex handling (see NOTES). Algorithmic converters are supplied as part of the operating system product; the internal interfaces that they require are not published for external use. Table converters, which reside in the /usr/lib/nls/loc/iconvTable directory, can be created by using the genxlt command (see genxlt(1)). These converters can support single-byte codesets and up to 256 encoded character values. Names of codeset converters are in the following form: from-codeset_to-codeset For example, the following converter converts values from Super DEC Kanji to Japanese Extended UNIX Code: sdeckanji_eucJP The codeset converters produce an invalid character error in response to characters that cannot be converted from the source codeset to the destination codeset. This error is always produced for character codes that are invalid in the source codeset. However, if the error results from characters that are valid in the source codeset but have no counterparts in the destination codeset, you can eliminate the error by defining the ICONV_DEFSTR environment variable to specify a substitute output string. See the ENVIRONMENT VARIABLES section for more information about using the ICONV_DEFSTR variable. It is possible to convert data directly between two codesets or by way of an intermediate codeset, such as UCS-2, UCS-4, or UTF-8. For con- version of Chinese characters, be aware that the results of converting a Traditional Chinese codeset directly to a Simplified Chinese code- set may not be the same as the results of converting Traditional Chinese first to UCS-2, UCS-4, or UTF-8 and then to Simplified Chinese. ENVIRONMENT VARIABLES
Some codeset converters require more complex algorithms than can be provided through tables. The following environment variables provide control over conversion behavior for different kinds of codeset converters: Controls the behavior for the many-to-one value conversions for conversion of Traditional Chinese (except for Traditional Chinese encoded in Telecode) to Simplified Chinese. The valid settings for this environment variable are as follows: Specifies that the preferred mapping value (the first one in the one-to-many mapping list) is always taken. The batch setting is the ICONV_ACTION default. Specifies that all the possible values are printed to the standard output, enclosed by braces ({ }), so that the user can later manually edit the converted file and select the one to use. Specifies that all the possible values are printed to the standard output except for punctuation symbols, for which only the preferred mapping value is printed. As is true for conv-all, the conv_all_nosym setting prints value choices enclosed by braces so that the converted file can later be edited. Sets byte ordering for UCS-2 or UCS-4 converters only. Valid values are little- endian (the default) or big-endian. Setting this environment variable may be necessary when producing UCS-2 or UCS-4 output that will be processed by codeset converters on platforms other than Tru64 UNIX. Defines the default string to be substituted in output for valid input characters that cannot be converted from the source codeset to the destination codeset. The variable value can be an arbitrary string or a code number. If the value is a code number (for example, 10, 07, 0x10, or, for Unicode converters, U+1234), the corresponding character in the output codeset (to-codeset) is printed. For a given type of codeset conversion, a matching ICONV_DEFSTR_from-codeset_to-codeset variable has precedence over the ICONV_DEF- STR variable without the from-codeset_to-codeset suffix. When defining the variable with the suffix, replace from-codeset_to-code- set with the name of the codeset converter to which the variable applies. The ICONV_DEFSTR variable (defined without the suffix) is used by a converter when no ICONV_DEFSTR_from-codeset_to-codeset variable has been defined specifically for the type of conversion being done. If these variables are not defined or are set to the null string, the characters that cannot be converted are skipped and have no representation in converted output. The following converter-specific restrictions apply to ICONV_DEFSTR* variables: ICONV_DEFSTR* environment variables do not work for converters that convert between Japanese codesets or between Korean codesets. For converters that handle UCS-2, UCS-4 or UTF-8 for- mat, the only valid variable value is a code number (such as U+1234 or 0x10) or a string whose value is a single ASCII character (such as ?). For these converters, any string value other than a single ASCII character is ignored and any characters that cannot be converted have no representation in output. For converters that handle output in UCS-2, UCS-4 or UTF-8 format, characters that can- not be converted and for which no valid ICONV_DEFSTR* value has been defined produce an error condition that aborts the conversion process. Disables generation of the byte-order mark at the beginning of UCS-2 or UCS-4 output. A valid setting is any value other than a null string. By default, or if this variable is set to a null string, the byte-order mark is generated at the beginning of UCS-2 or UCS-4 output. Codeset converters that process UCS-2 or UCS-4 data on platforms other than Tru64 UNIX usually require the byte-order mark. There- fore, the current default behavior of Tru64 UNIX codeset converters produces output that is more likely to be supported as input to codeset converters on other platforms. Use the ICONV_NOBOM variable only if you need backward compatibility with output produced by codeset converters that were included in versions of Tru64 UNIX prior to Tru64 UNIX Version 4.0D. Activates phrase conversion for converters that convert from a Traditional Chinese codeset (except for Traditional Chinese encoded in Telecode) to a Simplified Chi- nese codeset or the reverse. When phrase conversion is activated, a whole phrase in Traditional Chinese is converted to a different phrase in Simplified Chinese or the reverse. If ICONV_PHRCONV is set to mark, the converted phrases are be bracketed by [ and ] to highlight the conversion result for visual checking. The phrase conversion databases in the /usr/share/phrdb directory are normal text files with the same file names as those of the algorithmic converters in /usr/lib/nls/loc/iconv/*. These phrase conversion databases contain entries for phrase conversion pairs. FILES
Algorithmic converters Table converters Phrase conversion databases SEE ALSO
Commands: genxlt(1), iconv(1), phrase(1) Functions: iconv(3), iconv_close(3), iconv_open(3) Others: i18n_intro(5), l10n_intro(5) iconv_intro(5)
All times are GMT -4. The time now is 07:04 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy