RE: QOpenSys access

The 400 is not on the public internet where the client's client will be
browsing from.

- Dan Bale
(I am *NOT* "Dale"
http://archive.midrange.com/midrange-l/200105/msg00281.html )
SAMSA, Inc.
989-790-0507
DBale@SAMSA.com <mailto:DBale@SAMSA.com>
  Quiquid latine dictum sit altum viditur.
  (Whatever is said in Latin seems profound.)

-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com]On Behalf Of Evan Harris
Sent: Thursday, May 02, 2002 4:04 AM
To: midrange-l@midrange.com
Subject: RE: QOpenSys access


Dan

why do you need to move it ? Why not browse it on the AS/400 ?


>The application is this:  Our AS/400 application builds HTML that shows all
>the scheduled deliveries for all the customers of our client's client (got
>that?).  This app runs once each day after order posting completes.  The
>HTML file is then ready for export.  The plan is that a VB app on the
server
>will FTP-get the HTML file from the 400 and place it on the server, so that
>our client's client can browse this document at their convenience from the
>web.
>
>As I recall, the reason for the VB app is that we won't have public access
>to the server that will host the web page, so we won't be able to run FTP
>from the 400.  This is the grey area for me, and others far more
>knowledgeable than I are saying it has to be this way.  My thinking was
that
>the file probably didn't even need to be moved outside of the QSYS.LIB
>system, but I have no idea what the VB app requires, so at this point, I'm
>just doing what I'm told.