|
View previous topic :: View next topic
|
| Author |
Message |
BlackScreen_Hustle
New User
Joined: 20 May 2024
Posts: 9
Location: India
|
|
|
|
We have a file sent in binary mode which we want to encode back to ebcdic.
The flow of data is Mainframe1 sends file in binary mode > MFT transfers in binary mode > Mainframe2. How can I decode this file back to ebcdic data ? The file looks like below -
| Code: |
********************************* Top of Data **********************************
@..........................@.........@@...@.........@@@@@@@......@@@@@@..@......
......@@@@@@@@@@@@@@@@@@@@@..........................................@..........
...............@@@@@@@@@@@@@.........@......@.........@@@@@@..@.............@@@@
@@@@@@@@@@@@@@@@@@@.......................................@.....................
.......@@@@@@@@@@.....@@@@@@@@@@@@@@@......@@@@@@..@............@@@@@@@@@@@@@@@@
@@@@@..........................................@.........................@@@@@@@
@@@@@@.........@......@.........@@@@@@..@.............@@@@@@@@@@@@@@@@@@@@@@@...
....................................@............................@......@@@..... |
|
|
| Back to top |
|
 |
sergeyken
Senior Member
Joined: 29 Apr 2008
Posts: 2051
Location: USA
|
|
|
|
1. If the original dataset was NOT EBCDIC TEXT DATASET, then it cannot be converted "back to EBCDIC".
2. If the original dataset was REALLY EBCDIC TEXT DATASET, then after two binary transfers it should remain an EBCDIC TEXT DATASET.
3. How the initial dataset looks like, before the first FTP?
4. Please, present all actual code used for this transfer game, plus input/output data view before/after each transfer, and in hex notation.
But even better - initially investigate each of your steps by yourself. |
|
| Back to top |
|
|
BlackScreen_Hustle
New User
Joined: 20 May 2024
Posts: 9
Location: India
|
|
|
|
| sergeyken wrote: |
1. If the original dataset was NOT EBCDIC TEXT DATASET, then it cannot be converted "back to EBCDIC".
2. If the original dataset was REALLY EBCDIC TEXT DATASET, then after two binary transfers it should remain an EBCDIC TEXT DATASET.
3. How the initial dataset looks like, before the first FTP?
4. Please, present all actual code used for this transfer game, plus input/output data view before/after each transfer, and in hex notation.
But even better - initially investigate each of your steps by yourself. |
The original Mainframe file is an EBCDIC text. But it's coming to us as I have shown above. |
|
| Back to top |
|
|
sergeyken
Senior Member
Joined: 29 Apr 2008
Posts: 2051
Location: USA
|
|
|
|
| BlackScreen_Hustle wrote: |
| sergeyken wrote: |
1. If the original dataset was NOT EBCDIC TEXT DATASET, then it cannot be converted "back to EBCDIC".
2. If the original dataset was REALLY EBCDIC TEXT DATASET, then after two binary transfers it should remain an EBCDIC TEXT DATASET.
3. How the initial dataset looks like, before the first FTP?
4. Please, present all actual code used for this transfer game, plus input/output data view before/after each transfer, and in hex notation.
But even better - initially investigate each of your steps by yourself. |
The original Mainframe file is an EBCDIC text. But it's coming to us as I have shown above. |
Please, present all actual code used for this transfer game, plus input/output data view before/after each transfer, and in hex notation.
But even better - initially investigate each of your steps by yourself. |
|
| Back to top |
|
|
BlackScreen_Hustle
New User
Joined: 20 May 2024
Posts: 9
Location: India
|
|
|
|
Hi All,
We did some investigation and there was some issue in MFT settings. Once they sent the file in binary, we got the right data. Thanks for all the replies. |
|
| Back to top |
|
|
|
|
