View previous topic :: View next topic
|
Author |
Message |
nithyaroslin
New User
Joined: 29 Jan 2008 Posts: 14 Location: Chennai
|
|
|
|
Hi,
We ftp a mainframe file to unix server. Instead of [ and ] we are getting junk characters in unix server |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
Hi,
How do you conclude they are junk? |
|
Back to top |
|
|
nithyaroslin
New User
Joined: 29 Jan 2008 Posts: 14 Location: Chennai
|
|
|
|
Hi,
It was not in readable format. But the same chars are subtituted for [ and ] respectively. |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
Most Unix systems require ASCII data. You could use the Unix System Services (USS) editor to view the ASCII file directly, or use USS iconv command to convert back to EBCDIC to view, or download in binary to a PC and use a text editor to view the data ... perhaps if you can clarify what you're looking for? |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
The square brackets are not standard EBCDIC characters. Your file may be defined using one codeset while another codeset is being used to download the data; this could cause the square brackets to be incorrectly translated.
Go to the IBM web site and search on EBCDIC square bracket -- there's over 500 hits and will tell you everything you want to know about code pages and brackets. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
You first need to ensure that there are only text characters in the file to be sent from the mainframe (no packed-decimal or binary signed zoned-decimal numerics).
There are multiple examples of ftp jcl in the forum. This is one:
ibmmainframes.com/viewtopic.php?t=337&highlight=ftp |
|
Back to top |
|
|
nithyaroslin
New User
Joined: 29 Jan 2008 Posts: 14 Location: Chennai
|
|
|
|
Hi,
Thank you... We were not able to send [ or ] as this was not standard characters. We were not able to keyin these characters as well in our datasets... So we changed this to { and }.
Regards,
Nithya |
|
Back to top |
|
|
|