From your original post, it looks like maybe there is some sort of Apache oddity with using QNTC to copy large files. Maybe there is an Apache or QNTC PTF available for this issue. Have you checked ?
For our Image Server/400 software we always store our IFS files in ASCII format and both Classic and Apache web servers publish them just fine, even via QNTC.
Why not just stick with the classic HTTP if it works for your needs ?
If interested in discussing your needs and the potential use of our Image Server/400 software as the underlying engine for this project, contact me directly off-list.
Hope this helps.
RJS Software Systems Inc.
Web Site: http://www.rjssoft.com
Tel: (952) 898-3038
Fax: (952) 898-1781
Date: Sat, 31 Jan 2004 06:23:02 -0000
From: "jrock64rose" <jrock64rose@...>
Subject: Re: problem with QNTC
See my Question #2843 for some of the symptoms.
The conclusion that I came to is the following.
All the data stored on the IFS is stored in EBCIC format.
So when a page is served it is converted to ASCII before being sent
to the browser.
Now the twist. ALL data stored on a WINdows server is already in
ASCII format but APACHE still does what it thinks is a EBCDIC to
The HTTP server must have had logic telling it not to convert
documents from QNTC. Apache does not.
This is my guess at what the bug is, but even as a business partner
I do not know who to report it to.
Is there even a single occurance support line option to hande this
if we chose to pay them to fix their bug??
Let me know if you have better results and can get it working.
I currently have a 25GB image database that I would like to offload
and we are presently bidding on a 1.3TB yes terrabyte image