[+] enlarge |
IBM 6475399 Print ribbon
The IBM 6475399 Print ribbon is an ideal accessory for your printer. High... More |
- 1.Extended Binary Coded Decimal Interchange Code - Wikipedia, the free ...
- EBCDIC descended from the code used with punched cards and the corresponding six ... EBCDIC was devised in 1963 and 1964 by IBM and was announced with the release of ...
- http://en.wikipedia.org/wiki/E
BCDIC
- 2.The Apache EBCDIC Port
- EBCDIC-related conversion functions ... EBCDIC stands for Extended Binary-Coded-Decimal Interchange Code and is the ... is needed for any EBCDIC based machine. ...
- http://httpd.apache.org/docs/e
bcdic.html
 |
What are the differences Please don't provide wiki
links. I can get them myself!
|
|
 |
|
|
 |
Technical comparison between ASCII and EBCDIC http://www.dynamoo.com/technic al/ascii-ebcdic.htm |
|
|
|
|
|
Why will the ASCII and EBCDIC |
|
|
|
|
|
I believe most of the concerns surround language and symbol support. The original standards were very English language focused. |
|
|
|
|
|
How can I ftp an EBCDIC file I am in the middle of a
migration from our mainframe.
We currently use CA's
TCPAccess product for ftp and
telnet. To cut costs I want to
eliminate TCPAccess and use
IBM's TCPIP stack. I have
"snake files" on the mainframe
that look like 80 byte records
but are in reality one big
record that spans multiple
80-byte records. When I ftp
using FTP2 under TCPAccess,
the file is present to Unix as
one big record. When I ftp
using IBM's product, it
inserts a CR-LF at the end of
each 80-byte record. I had
used an XLATE table in CA's
product to eliminate the CR-LF
but cannot find a way to
eliminate them under IBM. BTW,
I am running z/OS 1.4 and
cannot upgrade the OS to 1.7
or 1.8 due to HW constraints
so I am stuck with an
unsupported OS. I am dumping
redundant SW to save $ thru
the end of the project.
|
|
|
|
|
|
I have done this in the past with my company when we were pulling B2B data from a vendor. Please contact me as I am attempting to contact the PM who actually did the coding around the FTP script. If I remember right, we needed to QUOTE SITE a command to the mainframe box to specifically tell that system how to transfer the file in terms of record length and record termination. Again, contact me and I will get the info. |
|
|
|
|
* Indicates a required fieldAdd your knowledge or ask a question:
