RE: Difference between Client Access file transfer and FTP

["Draper, Dale" <dale.draper@xxxxxxxxxxxx>]

This is from the CAWIN help file, you can create a *.bat file to do
downloads from the AS400. Without using ROBOTCLIENT, use the native NT or
WIN95 scheduler to run your CA .TTO file.

_+_+_+_+_+_+_+_+

RTOPCB

Use this command from a DOS prompt or as an entry in a batch file (.BAT
files). RTOPCB will run a previously saved data transfer request (.TTO
files) to send data from the AS/400 system to the PC.

Syntax

RTOPCB [/S] [[[filename] [/C] [...]] | [[/F] [list file]]]


/S      Show transfer statistics.
filename        An AS/400 to PC transfer request (.TTO), a Rumba file
transfer request (.RTO), or a Windows 3.1 transfer request (*.dt) file.
/C      Process next file independent of previous file.
/F      Process files within list file (one filename per line).
List file       A file containing a list of transfer files to process
Examples

RTOPCB c:\temp\test.tto
RTOPCB /S c:\temp\test.tto /C c:\temp\trans.tto
RTOPCB /S /F c:\temp\transfer
        
Your NT server has the capability to schedule jobs, so after you make your
*.TTO file, merely schedule your *.bat file to run when you want.       

(Caveat: I have not yet done this, I expect to within the month)


Dale Draper
Sega Enterprises
650-632-7555
dale.draper@seu.sega.com


> -----Original Message-----
> From: John Cirocco [SMTP:JCirocco@gw.ctg.com]
> Sent: Friday, January 15, 1999 5:32 AM
> To:   MIDRANGE-L@midrange.com
> Subject:      Difference between Client Access file transfer and FTP
> 
> Hello,
> 
>    I am hoping someone here can help me.  I have a process that is
> transfering files from a /400 to an NT server via Client Access file
> transfer.  The transfer is kicked off via RobotClient.  It has been in
> place a while and we constantly have problems because RobotClient is 16bit
> and requires a router session.  So, to improve our process we decided to
> change the job to send the file directly via FTP.  
> 
>    What we found out was the original file transfers were not sending the
> data correctly.  What was a 3 byte zoned numeric was actually transfered
> with CA as a 4 byte field where the numeric fields were filled with BLANKS
> and not ZEROs.  When we transfer with FTP, the files as sent correctly.  I
> know I need to re-create my SQL Server imports for the "new" file layouts
> but I am extreamly curious as to why CA pads my ASCII file with blanks and
> adds an extra position.
> 
> Any help and sedatives will be greatly appreciated...
> 
> John
>  
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---