Excellent. This process would work even better with a tool like NFS/iX
Server on the HP3000 this way the files are accessed. By accessing them you
can read the records and apply the business logic Jon suggests to get them
on a CD. This would mean the files would not even need to be transfered.

-----Original Message-----
From: Jonathan M. Backus
To: [log in to unmask]
Sent: 11/29/01 1:12 PM
Subject: Re: To automate multiple files transfer from HP3000 to PC

Rick,

        That would get the files from the 3000 down to the PC but
doesn't really
address the issue of getting them burned onto a CD.  That is why I
decided
to take the model where the PC was the driver of the whole operation and
pulled the files.  The 3000 was simply a location to get a file from,
which
start the process, but all of the "business logic" or work happened once
the
file was down to the PC or network.  The other option is to have the
3000
push the files, like you described and then you would still have to have
a
PC based process recognize that the files arrived and then do the
processing
against them.

Thanx,
        Jon

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
Behalf Of Clark, Rick
Sent: Thursday, November 29, 2001 4:01 PM
To: [log in to unmask]
Subject: Re: [HP3000-L] To automate multiple files transfer from HP3000
to PC


There are two ways to handle this in FTP from the 3000-
1) Use the MPUT/MGET command with wildcards
2) Use the MPUT/MGET command with indirect file

For example, the files are named NEW01 through NEW35. Using ftp you
would do
a

ftp>MPUT NEW*



or if each file name is different

ftp> MPUT ^file

where ^file contains the list of file names to move over. You can easily
create this file by LISTF >filename if the files are different each
time.


ftp>help mput

Expand wild-cards in the list of local files given as arguments and
do a put for each file in the resulting list.  Instead of using wild-
cards, you may provide an indirect file by preceding that file's
name with the caret symbol (^).  Optionally, build parameters can be
specified if the remote is an MPE/XL system.  The build parameters
will affect each file in the transfer.  In effect, ";build-parms" is
appended to each file name.  Non-MPE/XL FTP Servers will not interpret
the build parameters as intended.  Use the CASE command to force the
resulting file names to contain all lower case letters.

**NOTE** Of course this requires a FTP listener on the pc. We use one
but
the name escapes me right now.

HTH

> -----Original Message-----
> From: Tawny Tran [mailto:[log in to unmask]]
> Sent: Thursday, November 29, 2001 3:44 PM
> To: [log in to unmask]
> Subject: [HP3000-L] To automate multiple files transfer from HP3000 to
> PC
>
>
> Hello Everyone,
>
> We have about 35 files which need to download to pc then copy
> to the CD
> daily.
> Is there any way to automate the task using either Reflection or FTP?
>
> Thanks,
> [log in to unmask]
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *