Re: Copying from/to qntc performance -- MIDRANGE-L

Subject: Re: Copying from/to qntc performance
From: CRPence <crpbottle@xxxxxxxxx>
Date: Tue, 30 Jun 2015 09:15:50 -0600
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 29-Jun-2015 13:35 -0600, Alan Cassidy wrote:

<<SNIP>>
FTP was my first thought but they had already started the project
with the QNTC share before they involved me. (-:

The FTP allows the server to be local to the client, so the speed of an /image/ transfer using FTP PUT locally to the /QNTC [logged in to the local FTP server as the appropriate user] could be compared against the Copy To Stream File (CPYTOSTMF); I would expect almost no difference.

As already suggested, the FTP between the IBM i FTP client to the Win FTP server should easily best writing\reading via /QNTC.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.