> The server system, as it happens, reported that FTPSERVE had been forced 
by SYSTEM after 2G were transferred.  
Ah, well... that's new information.  The error I saw was a 'disk full' 
condition (even though the filespace had 3 3390-9 DASD) after 2G sent to 
VM.

Obviously, this is a different situation.  <In my best Gilda Radner voice: 
never mind>

Any other messages on the FTPSERVE console?  (Yeah, I know you already 
checked, but it obviously never hurts to ask for other evidence)

Mike Walter 
Hewitt Associates 
Any opinions expressed herein are mine alone and do not necessarily 
represent the opinions or policies of Hewitt Associates.



"Adam Thornton" <[EMAIL PROTECTED]> 

Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>
08/28/2007 10:57 PM
Please respond to
"The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>



To
IBMVM@LISTSERV.UARK.EDU
cc

Subject
Re: Augh







On Aug 28, 2007, at 6:09 PM, Mike Walter wrote:


Well, there **used** to be an undocumented 2G limit to FTP transfers into 
VM.  The error messages indicated that the disk was full. 
But that was supposed to have been fixed a long time ago. 

Are you 100% positive that you are using the current CMS FTP client and 
server code (can't remember the guilty party) - nothing "leftover" lying 
around? 


I'm pretty sure it was current.

The server system, as it happens, reported that FTPSERVE had been forced 
by SYSTEM after 2G were transferred.  It's a 5.2 system with pretty close 
to the current maintenance on it.

Adam


 
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.


Reply via email to