I do not think so. How would SFS know that a second PUT was to be done?
Also, what would it do if the second were to fail? I hope it makes them
separate work units.
 

Regards, 
Richard Schuh 

 

 


________________________________

        From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Stracka, James (GTI)
        Sent: Friday, February 29, 2008 9:13 AM
        To: IBMVM@LISTSERV.UARK.EDU
        Subject: Re: FTP x86 to SFS
        
        
        Could it be that SFS considers this one unit of work and is not
closing the files until the complete FTP ends?

                -----Original Message-----
                From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Schuh, Richard
                Sent: Friday, February 29, 2008 12:07 PM
                To: IBMVM@LISTSERV.UARK.EDU
                Subject: FTP x86 to SFS
                
                

                I have a process that FTPs two files from a WinXP
machine to an SFS directory. The sequence of events is 

                1. A small file, 10-15 short (<80 bytes, each) records
is created on the pc. 
                2. Immediately thereafter, an FTP is started by the
script that created the small file. It contains two PUTs, one after the
other. The first sends the newly created small file; the second sends a
file of nearly 10,000 records ranging in size from 150 to 800 bytes. 

                
                I have noticed that sometimes, infrequently, the large
file arrives first. This transfer is done over an internal network.
Tracert from the pc to VM always shows the same 7 hops; from VM to the
pc, the same in reverse order.

                Is there anything that explains this as normal behavior?
Or has Chuckie struck? 

                I would love to do the transfer with a virtual machine
as the client, but the large file is inaccessible from any pc on the
network that is running an approved FTP server. Unapproved FTP servers
are frowned upon by Infosec, and thus, by management.

                Regards,
                Richard Schuh 


________________________________

        This message w/attachments (message) may be privileged,
confidential or proprietary, and if you are not an intended recipient,
please notify the sender, do not use or share it and delete it. Unless
specifically indicated, this message is not an offer to sell or a
solicitation of any investment products or other financial product or
service, an official confirmation of any transaction, or an official
statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may
monitor, review and retain e-communications (EC) traveling through its
networks/systems. The laws of the country of each sender/recipient may
impact the handling of EC, and EC may be archived, supervised and
produced in countries other than the country in which you are located.
This message cannot be guaranteed to be secure or error-free. This
message is subject to terms available at the following link:
http://www.ml.com/e-communications_terms/. By messaging with Merrill
Lynch you consent to the foregoing.
________________________________

         

Reply via email to