Hi. Does anyone know a tool out there that can convert "packed" EBCDIC
into ASCII ? I'm receiving this data from MVS, and doing the conversion
on Solaris 2.5.1. Any help provided would be greatly appreciated.
> Hi. Does anyone know a tool out there that can convert "packed" EBCDIC
> data file
> into ASCII ? I'm receiving this data from MVS, and doing the conversion
> on Solaris 2.5.1. Any help provided would be greatly appreciated.
Advanced Technology Center
Laguna Hills, California
If you data contains "packed" decimal, you have to write a custom
program to convert the data.
Hemant Shah, LIDP Inc. /-------------------\ ^~~~~^
Voice: +1 630 960 0133 x 664 |TECHNOLOGY | | |
Fax: +1 630 960 0717 |No place for wimps | o|-OO-|o
\-------------------/ | |
-----------------[DO NOT SEND UNSOLICITED BULK E-MAIL]------------------
I haven't lost my mind, Above opinions are mine only.
it's backed up on tape somewhere. Others can have their own.
ATTENTION: Despite Any Other Listing of Product Contents Found Here-
on, the Consumer is Advised That, in Actuality, This Product Consists
Of 99.9999999999% Empty Space.
It may be easier to output the data in EBCDIC text form on the MVS
system, as programs there have easy ways of dealing with packed data.
The size of the data will expand, but it will be much easier to
translate pure text data.
OS: AIX4.3.3 ML09
I am trying to read a tape  created on an IBM OS/VS 370 in EBCDIC
using block size 7735 and record length 595. When I use the following dd
dd if=/dev/rmt2 of=ascii.data conv=ascii ibs=7735 cbs=595
everything works fine until it encounters nulls (0x00) in the data
stream. When these occur, they are always at position 390 for a lngth of
20. When the nulls are encountered, dd skips the remainder of the current
record and concatenates the following record, beginning in position 390
for a total of 990 bytes.
If I first read the data from tape to disk without the conversion:
dd if=/dev/rmt2 of=data.ebcdic ibs=7735
and then convert using a second dd command:
dd if=data.ebcdic of=data.ascii conv=ascii cbs=595
it works fine, handling the nulls as other data.
Has anyone observed this [peculiar] behavior and do you have a better way
of handling it?