Two similar techniques come to mind - 
depending upon whether your users 
login to a NT/Windows network

(1) Get the user to save the file in a dedicated network directory 

eg q:\HPtoPC\TESTFILE

(2a) Have a reflection or minisoft script running in your Ops room that polls that directory 
every 20 seconds or so and automatically transfers the file to 
the HP to a fixed file name and then processes the file. 

I can send you a sample script. 

or 

(2b) Get your network guys to configure an FTP server on the network and the 
application can run FTP.ARPA.SYS directly to pull the file onto the HP. 

Each of the above solutions have their advantages and disadvantages. 

>>> Jim Phillips <[log in to unmask]> 18/01/00 19:09:57 >>>
john edwards <[log in to unmask]> writes:

> The users prepare files on their PC's and transfer
> them to the 3k using relections file transfer. They
> then stream a job to process the files. The job
> expects the files to be in a special group with a
> standard naming convention. There is a menu program
> that allows them to drop into MPE for the transfer and
> to stream the job.
> I hate this.
>
> What I would like is:
> 1) transfer the PC data into a temporary file of a
> specific name.
> 2) run the programs on line to process the temporary
> file.
>
> Running the programs on line is no problems, but how
> can I control the destination file name and location?
>
> Any suggestions greatfully received.
>

We use Minisoft MS92 to do exactly th same thing.  In fact our files come
from handheld bar code scanners that are uploaded to the PC and then
uploaded to the HP.  What we do is to invoke the MS92 script language that
performs all the PC file renames (the file is originally uploaded to the PC
in a known file name and subdirectory), HP file equates, and the actual file
transfer.  We also have one user who uploads CSV files from Excel (they come
from the customer like that, Wirt!) which we load into the data base using a
COBOL program.  In this case, the file is different each time.  We prompt
the user for the fully-qualified file name (on the PC) and upload it to a
known file name on the HP.  Of course, in this case, we hold the data in a
temporary data set (for user review) before committing the data to the HP.

I know this doesn't help you if you don't have MS92, but you should be able
to do the same type of things with Reflection.


PS to Wirt:  This is the kind of functionality we will need in QCTerm as
well.


Jim Phillips                            Manager of Information Systems
E-Mail: [log in to unmask]     Therm-O-Link, Inc.
Phone: (330) 527-2124                   P. O. Box 285
  Fax: (330) 527-2123                   Garrettsville, Ohio  44231