How to transfer file from Mainframe to UNIX
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 99
- Joined: Mon Sep 03, 2007 7:49 am
- Location: Stockholm, Sweden
also if your file has compressed values on the mainframe then they might get converted to linebreakers or hex null values on unix and you may not be able to read it as you wish.
Good practice is to first (on the mainframe) convert any special charachters or compressions to normal text and then ftp over to unix.
Good practice is to first (on the mainframe) convert any special charachters or compressions to normal text and then ftp over to unix.
-------------------------------------
http://it.toolbox.com/blogs/bi-aj
my blog on delivering business intelligence using agile principles
http://it.toolbox.com/blogs/bi-aj
my blog on delivering business intelligence using agile principles
-
- Premium Member
- Posts: 99
- Joined: Mon Sep 03, 2007 7:49 am
- Location: Stockholm, Sweden
true, however I have had trouble with COMP-3 fields when transfering binary from mainframe to unix using a program called ConnectDirect. After many different trials and errors we decided to "decompress" on the mainframe and send in plain text and got our following programs to function....
-------------------------------------
http://it.toolbox.com/blogs/bi-aj
my blog on delivering business intelligence using agile principles
http://it.toolbox.com/blogs/bi-aj
my blog on delivering business intelligence using agile principles
ArndW wrote:Stefan - I think the ConnectDirect or mainframe issue is that some files can have compressed spaces which are not interpreted/expanded correctly when doing such transfers. The compressed spaces binary ...
what are all the connection details are need for transfer the fail from Mainfram to Unix/local environment.
regards,
Rakesh
Rakesh
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Premium Member
- Posts: 99
- Joined: Mon Sep 03, 2007 7:49 am
- Location: Stockholm, Sweden
ArndW! Is there a way to handle (other than fixing the files before sending) what you are describing?Stefan - I think the ConnectDirect or mainframe issue is that some files can have compressed spaces which are not interpreted/expanded correctly when doing such transfers. The compressed spaces binary ...
-------------------------------------
http://it.toolbox.com/blogs/bi-aj
my blog on delivering business intelligence using agile principles
http://it.toolbox.com/blogs/bi-aj
my blog on delivering business intelligence using agile principles
Only a few operatings sytems will do this. I recall having seen this on PRIMOS and some mainframe system (it might have been Hitachi, but that is only a guess). This won't be an issue for most systems; if you check your mainframe file system documentation you will find out if it does multiple space compression. If it does, and you have COMP-3 or other binary fields, then you will need to do a binary transfer and then do the EBCDIC->ASCII conversion on the server side.