|
View previous topic :: View next topic
|
| Author |
Message |
morpheus007
New User
Joined: 27 Dec 2005
Posts: 58
|
|
|
|
We are trying to extract large VSAM files to flat files and then ftp them to another server.We are facing issues with large files in this.
At exactly 1073741312 bytes the ftp fails and gives an error called 'Broken Pipe'.When I convert this to GB's it comes to about 1GB.Is there any such limit on the size of the file that can be transfered. |
|
| Back to top |
|
 |
mkk157
Active User
Joined: 17 May 2006
Posts: 310
|
|
|
|
Ur assumption may also be right.
Besides that, there is a chance of violation from the file server that u r trying to FTP. Admin is the right person to answer this query. Ask him the Configuration details .
And let us know the final solution for this. |
|
| Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
| morpheus007 wrote: |
| Is there any such limit on the size of the file that can be transfered. |
Not from the z/OS point of view. However, as mkk157 already mentioned, it may be very possible that there is a limit on the server side. |
|
| Back to top |
|
|
diwa_thilak
Active User
.jpg)
Joined: 13 Jul 2006
Posts: 205
Location: At my desk
|
|
|
|
Hi,
May be i can throw some light with respect to my project.
Actually there are many parameters with respect to transmitting a file in Mainframe.
Once such thing is the connection parameter, the destination server sets al imit for the transmission (i.e data connection). If the particular transmission takes more time this data connection will be closed and control connection will be used to exit the server resulting in Broken pipe error.
In that case, you may need to speak to the N/w team to decide about the transmission time (or) spilit the file and transmit them.
Hope i made it clear to you.
Note :
I beleive a compression utility is also available. May be you can check this option as well.
Cheers,
Diwakar
-------------------------
Nobody is Perfect. I am Nobody |
|
| Back to top |
|
|
stodolas
Active Member
Joined: 13 Jun 2007
Posts: 632
Location: Wisconsin
|
|
|
|
I have transferred files up to 11GB from the mainframe. If I am doing it via JCL, then if the job doesn't get any CPU time for longer than the timeout interval, I get the broken pipe error. But since your is always failing at exactly the same size, I assume you have tried running the job at different times of the day.
Note: Compression will not help much in transfer time. An uncompress text file will transfer at extremely high speeds because of the built in compression. But if you zip the file, you will get slower speeds. Your times should be comparable. Try it sometime, take a huge uncompressed file and send it via FTP, look at your k/s speed. Then compress it and try the same, your speed should be lower. |
|
| Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
| Interesting. That's exactly opposite how it used to be when using an SNA network connection. |
|
| Back to top |
|
|
stodolas
Active Member
Joined: 13 Jun 2007
Posts: 632
Location: Wisconsin
|
|
|
|
| My tests were non-mainframe FTP quite a while ago over 14.4 modems to sites with upload ratios. I don't know if it has changed, I probably shouldn't have mentioned information that is 10 years old... |
|
| Back to top |
|
|
diwa_thilak
Active User
Joined: 13 Jul 2006
Posts: 205
Location: At my desk
|
|
|
|
Kevin,
Can you throw some light about the SNA network connection ?
How it handles the FTP process ?
Is my assumption/explanation about FTP file transfer is right ?
Thanks,
Diwakar
-------------------------------
Nobody is Perfect. I am Nobody |
|
| Back to top |
|
|
|
|
