Sponsored Content
Full Discussion: EBCDIC to ASCII conversion
Top Forums UNIX for Advanced & Expert Users EBCDIC to ASCII conversion Post 303032729 by Don Cragun on Friday 22nd of March 2019 05:00:47 PM
Old 03-22-2019
I'm fully familiar of what packed decimal and zoned decimal are. But knowing how to interpret fields encoded in those formats if you don't know record boundaries and field boundaries is a wild guessing game.

I didn't know that a copybook was another language's name for what the C language calls an include file (thank you jgt).

Fortunately, I haven't had to use COBOL since 1975. I'm also fully aware that the UNIX dd utility was a joke showing how versatile UNIX utilities were and could even be made to use operands that were familiar to programmers used to writing IBM System 360 Job Control Language (JCL) card decks instead of all of the supposedly "confusing" single letter utility options used on most UNIX utilities. If you've never written JCL, the JCL DD statements described where various input and output files were to be found and/or placed for whatever job was to be run by that JCL deck and, especially if the file resided on a magnetic tape, the size of the blocks that were to be read from or written to the device used to access that file. Unfortunately (or fortunately, depending on how much you like JCL), the utility proved very useful when transferring files between UNIX systems and mainframes and we're still stuck with that syntax today.

But enough of this digression.

swapna_1990 has a file containing some EBCDIC text and some packed decimal, zoned decimal, or other binary data mixed in and wants it converted to ASCII text and "normal data" that is readable. Whether that data comes from a mainframe or from a C program written on a UNIX, Linux, or BSD system doesn't really matter. If you don't know the format of the data you're reading including field lengths or separators, field types, and record lengths or separators; then you don't know how to process that data. Until we get the data format from swapna_1990's customer, there is nothing we can do to guess at how that data could be extracted nor what tools might need to be used to do so. The fact that it came from a mainframe makes a COBOL program an obvious guess at something that might work. But from what we know so far, if swapna_1990 is extremely lucky, it is possible that a dd command coupled with output piped through some awk code might be able to work wonders. (Not highly likely, but there is a chance.)
 

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. Solaris

EBCDIC to ASCII Binary conversion issue on Solaris i-series Unix

Hi All, I am facing EBCDIC to ASCII Binary conversion on Solaris i-series Unix system. However this is working fine on Solaris Sparc Unix system. Input file having EBCDIC format does not work on Solaris i-series Unix system. Could you please tell me, what will be the root cause for same? (14 Replies)
Discussion started by: amodkavi
14 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. Programming

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) (19 Replies)
Discussion started by: tostay2003
19 Replies

7. UNIX for Dummies Questions & Answers

EBCDIC TO ASCII Conversion through UNIX Command

Hi All , I have a mainframe file which contains the data in EBCDIC unreadable format.I have downloaded this raw unreadable file from mainframe system to windows in text format then I pushed to Unix system.Now I want to convert this file to ASCII readable format file in unix.Can anyone advise me... (2 Replies)
Discussion started by: STCET22
2 Replies

8. 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

9. 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

10. 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
DD(1)							    BSD General Commands Manual 						     DD(1)

NAME
dd -- convert and copy a file SYNOPSIS
dd [operands ...] DESCRIPTION
The dd utility copies the standard input to the standard output. Input data is read and written in 512-byte blocks. If input reads are short, input from multiple reads are aggregated to form the output block. When finished, dd displays the number of complete and partial input and output blocks and truncated input records to the standard error output. The following operands are available: bs=n Set both input and output block size to n bytes, superseding the ibs and obs operands. If no conversion values other than noerror, notrunc or sync are specified, then each input block is copied to the output as a single block without any aggregation of short blocks. cbs=n Set the conversion record size to n bytes. The conversion record size is required by the record oriented conversion values. count=n Copy only n input blocks. files=n Copy n input files before terminating. This operand is only applicable when the input device is a tape. ibs=n Set the input block size to n bytes instead of the default 512. if=file Read input from file instead of the standard input. iseek=n Seek on the input file n blocks. This is synonymous with skip=n. obs=n Set the output block size to n bytes instead of the default 512. of=file Write output to file instead of the standard output. Any regular output file is truncated unless the notrunc conversion value is specified. If an initial portion of the output file is seeked past (see the oseek operand), the output file is truncated at that point. oseek=n Seek on the output file n blocks. This is synonymous with seek=n. seek=n Seek n blocks from the beginning of the output before copying. On non-tape devices, an lseek(2) operation is used. Otherwise, existing blocks are read and the data discarded. If the user does not have read permission for the tape, it is positioned using the tape ioctl(2) function calls. If the seek operation is past the end of file, space from the current end of file to the specified offset is filled with blocks of NUL bytes. skip=n Skip n blocks from the beginning of the input before copying. On input which supports seeks, an lseek(2) operation is used. Other- wise, input data is read and discarded. For pipes, the correct number of bytes is read. For all other devices, the correct number of blocks is read without distinguishing between a partial or complete block being read. conv=value[,value ...] Where value is one of the symbols from the following list. ascii, oldascii The same as the unblock value except that characters are translated from EBCDIC to ASCII before the records are converted. (These values imply unblock if the operand cbs is also specified.) There are two conversion maps for ASCII. The value ascii specifies the recommended one which is compatible with AT&T System V UNIX. The value oldascii specifies the one used in historic AT&T UNIX and pre-4.3BSD-Reno systems. block Treats the input as a sequence of newline or end-of-file terminated variable length records independent of input and output block boundaries. Any trailing newline character is discarded. Each input record is converted to a fixed length output record where the length is specified by the cbs operand. Input records shorter than the conversion record size are padded with spaces. Input records longer than the conversion record size are truncated. The number of truncated input records, if any, are reported to the standard error output at the completion of the copy. ebcdic, ibm, oldebcdic, oldibm The same as the block value except that characters are translated from ASCII to EBCDIC after the records are converted. (These values imply block if the operand cbs is also specified.) There are four conversion maps for EBCDIC. The value ebcdic specifies the recommended one which is compatible with AT&T System V UNIX. The value ibm is a slightly different mapping, which is compatible with the AT&T System V UNIX ibm value. The values oldebcdic and oldibm are maps used in his- toric AT&T UNIX and pre-4.3BSD-Reno systems. lcase Transform uppercase characters into lowercase characters. noerror Do not stop processing on an input error. When an input error occurs, a diagnostic message followed by the current input and output block counts will be written to the standard error output in the same format as the standard completion message. If the sync conversion is also specified, any missing input data will be replaced with NUL bytes (or with spaces if a block oriented conversion value was specified) and processed as a normal input buffer. If the sync conversion is not specified, the input block is omitted from the output. On input files which are not tapes or pipes, the file offset will be posi- tioned past the block in which the error occurred using lseek(2). notrunc Do not truncate the output file. This will preserve any blocks in the output file not explicitly written by dd. The notrunc value is not supported for tapes. osync Pad the final output block to the full output block size. If the input file is not a multiple of the output block size after conversion, this conversion forces the final output block to be the same size as preceding blocks for use on devices that require regularly sized blocks to be written. This option is incompatible with use of the bs=n block size specifica- tion. sparse If one or more output blocks would consist solely of NUL bytes, try to seek the output file by the required space instead of filling them with NULs, resulting in a sparse file. swab Swap every pair of input bytes. If an input buffer has an odd number of bytes, the last byte will be ignored during swap- ping. sync Pad every input block to the input buffer size. Spaces are used for pad bytes if a block oriented conversion value is specified, otherwise NUL bytes are used. ucase Transform lowercase characters into uppercase characters. unblock Treats the input as a sequence of fixed length records independent of input and output block boundaries. The length of the input records is specified by the cbs operand. Any trailing space characters are discarded and a newline character is appended. Where sizes are specified, a decimal, octal, or hexadecimal number of bytes is expected. If the number ends with a ``b'', ``k'', ``m'', ``g'', or ``w'', the number is multiplied by 512, 1024 (1K), 1048576 (1M), 1073741824 (1G) or the number of bytes in an integer, respec- tively. Two or more numbers may be separated by an ``x'' to indicate a product. When finished, dd displays the number of complete and partial input and output blocks, truncated input records and odd-length byte-swapping blocks to the standard error output. A partial input block is one where less than the input block size was read. A partial output block is one where less than the output block size was written. Partial output blocks to tape devices are considered fatal errors. Otherwise, the rest of the block will be written. Partial output blocks to character devices will produce a warning message. A truncated input block is one where a variable length record oriented conversion value was specified and the input line was too long to fit in the conversion record or was not newline terminated. Normally, data resulting from input or conversion or both are aggregated into output blocks of the specified size. After the end of input is reached, any remaining output is written as a block. This means that the final output block may be shorter than the output block size. If dd receives a SIGINFO (see the status argument for stty(1)) signal, the current input and output block counts will be written to the stan- dard error output in the same format as the standard completion message. If dd receives a SIGINT signal, the current input and output block counts will be written to the standard error output in the same format as the standard completion message and dd will exit. DIAGNOSTICS
The dd utility exits 0 on success, and >0 if an error occurs. SEE ALSO
cp(1), tr(1) STANDARDS
The dd utility is expected to be a superset of the IEEE Std 1003.2 (``POSIX.2'') standard. The files operand and the ascii, ebcdic, ibm, oldascii, oldebcdic and oldibm values are extensions to the POSIX standard. BSD
January 13, 1994 BSD
All times are GMT -4. The time now is 04:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy