Nikolai,

The terms Upload and Download are often confused.  Let's be more direct. 
You said that you are attempting to send the file FROM your z/VM 4.4 
system TO a Windows disk.  Then post below displayed results of a QUERY 
DISK command before and after the failed attempt.  That seems to imply 
that you are trying to send the file TO the VM system.

That makes it seems as though you are really attempting to send the file 
FROM a PC TO a VM system. 

If that is the same, you may be caught be an undocumented 2G limit on FTP 
transfers INTO VM.  We experienced that in VM/ESA 2.4.0.  It is described 
in the IBMVM-L thread beginning Tue, 28 Aug 2007 17:27:04 -0500 with the 
Subject: Augh

The following URL should get you to the start of that thread:
http://listserv.uark.edu/scripts/wa.exe?A2=ind0708&L=IBMVM&D=0&I=-3&X=0444AA37681B11D21A&Y=Mike.Walter%40hewitt.com&P=73906&F=P

If you really are trying to send the file to your old z/VM 4.4 system, it 
may be exposed to that same undocumented design limit.  If that is the 
case, an upgrade would certainly correct the problem.

Mike Walter
Hewitt Associates
The opinions expressed herein are mine alone, not my employer's.






"Nikolai Dorozhko" <[email protected]> 

Sent by: "The IBM z/VM Operating System" <[email protected]>
07/01/2010 10:48 AM
Please respond to
"The IBM z/VM Operating System" <[email protected]>



To
[email protected]
cc

Subject
Re: Large file transfer capacity






Hello David, 
The  Q disk was after abort,   I used the same disk from what the file was 
downloaded,   full  3390-3  without cyl 0. 

Nikolai. 



"Wakser, David" <[email protected]> 
01.07.2010 18:30 


To
<[email protected]> 
cc

Subject
RE: Large file transfer capacity








Not virtual storage ? disk size. It looks like the VM disk was too small 
to receive the file. Is the Q DISK issued AFTER the FTP aborted? I think 
you will need to use SFS if you require more than 1 pack of a disk size in 
VM. 
  
David Wakser 
  
From: [email protected] [mailto:[email protected]] 
Sent: Thursday, July 01, 2010 11:25 AM
To: Wakser, David
Subject: RE: Large file transfer capacity 
  
Hello David, 

>On the IND$FILE upload, are you running out of space and is that why the 
upload fails? 

Do you mean that i should define a large virtual storage? 

That is my PC ftp screen rip.  Sorry,  it speaks Russian.   >Netout : 
Abort of connection by  other computer   



q disk x       
LABEL  VDEV M  STAT   CYL TYPE BLKSZ   FILES  BLKS USED-(%) BLKS LEFT  BLK 
TOTAL 
ADF    ADF  X   R/O  3338 3390 4096        1     526004-88      74836 
600840 
 
file on disk after abort 

DISK74E  ARC      X1 V       8192     262147     524415  7/01/10 16:37:52 




Nikolai 




"Wakser, David" <[email protected]> 
01.07.2010 18:01 


To
"Nikolai Dorozhko" <[email protected]> 
cc

Subject
RE: Large file transfer capacity

  









I saw your post. On the IND$FILE upload, are you running out of space and 
is that why the upload fails? On the FTP, were there any messages? I 
cannot recall if there are any limitations possible in the FTP setup, but 
it COULD be stopped by a firewall. Is that possible? 
 
David Wakser 
 
From: The IBM z/VM Operating System [mailto:[email protected]] On 
Behalf Of Nikolai Dorozhko
Sent: Thursday, July 01, 2010 10:59 AM
To: [email protected]
Subject: Large file transfer capacity 
 
Hello collegues, developers. 

Trying to download/upload   a CMS binary file > 2G to PC   under  z/VM 
4.4. 

VM FTP aborts when transfer  reaches 2G, 

IND$FILE downloads , but does not upload. 

What to do ?   Will  the new VM releases help?     


Nikolai Dorozhko,
IBA, Minsk, Belarus
e-mail: [email protected] 
Confidentiality Note: This e-mail, including any attachment to it, may 
contain material that is confidential, proprietary, privileged and/or 
"Protected Health Information," within the meaning of the regulations 
under the Health Insurance Portability & Accountability Act as amended. If 
it is not clear that you are the intended recipient, you are hereby 
notified that you have received this transmittal in error, and any review, 
dissemination, distribution or copying of this e-mail, including any 
attachment to it, is strictly prohibited. If you have received this e-mail 
in error, please immediately return it to the sender and delete it from 
your system. Thank you. 
Confidentiality Note: This e-mail, including any attachment to it, may 
contain material that is confidential, proprietary, privileged and/or 
"Protected Health Information," within the meaning of the regulations 
under the Health Insurance Portability & Accountability Act as amended. If 
it is not clear that you are the intended recipient, you are hereby 
notified that you have received this transmittal in error, and any review, 
dissemination, distribution or copying of this e-mail, including any 
attachment to it, is strictly prohibited. If you have received this e-mail 
in error, please immediately return it to the sender and delete it from 
your system. Thank you. 




The information contained in this e-mail and any accompanying documents may 
contain information that is confidential or otherwise protected from 
disclosure. If you are not the intended recipient of this message, or if this 
message has been addressed to you in error, please immediately alert the sender 
by reply e-mail and then delete this message, including any attachments. Any 
dissemination, distribution or other use of the contents of this message by 
anyone other than the intended recipient is strictly prohibited. All messages 
sent to and from this e-mail address may be monitored as permitted by 
applicable law and regulations to ensure compliance with our internal policies 
and to protect our business. E-mails are not secure and cannot be guaranteed to 
be error free as they can be intercepted, amended, lost or destroyed, or 
contain viruses. You are deemed to have accepted these risks if you communicate 
with us by e-mail. 

Reply via email to