Subject: RE: FTP VSE-to-VSE with CSI TCP-IP 1.5E
From: Don Stoever (don@e-vse.com)
Date: Thu Jun 05 2008 - 11:47:07 EDT
I am waiting for a more definitive reply from our Dr.D development, but Dr.D
backups use record format undefined. The following is from the 1.5F $README
about FTP and DR.D backups:
* Support has been added for sequential disk files defined with a record
format of "undefined". This permits, for example, transfer of Dr.D backup
files from and to a PC-based FTP server, as shown below:
Using "record structure", as defined in the FTP RFC's:
BINARY
LQUOTE STRU R
PUT %DRDBUPV,SAM,UN,32768 FTPBPTUN.BJB
...
BINARY
LQUOTE STRU R
GET FTPBPTUN.BJB %DRDREST,SAM,UN,32768
...
Using an internally-defined structure
BINARY
PUT %DRDBUPV,SAM,UX,32768 FTPBPTUX.BJB
...
BINARY
GET FTPBPTUX.BJB %DRDREST,SAM,UX,32768
...
Both of the examples show above are applicable to any other sequential disk file
with a record format of "undefined".
Thanks,
Don
-----Original Message-----
From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf Of Kevin
Corkery
Sent: Thursday, June 05, 2008 10:37 AM
To: VSE Discussion List
Subject: FTP VSE-to-VSE with CSI TCP-IP 1.5E
I have a variable blocked SAM-ESDS (actually a Dr "D" backup) that I want to FTP
from one VSE system to another. I've been playing around with it and get real
close except that there's imbedded X'15's in the data that the receiving system
keeps interpreting as a record delimiter and trashes the logical record. What I
need to for the source system to transmit each logical record to the target
system with complete transparency and the target system to write the data the
same as it is on the sending system. Any ideas? The best bet here would be
for someone in DoctorD support to give me the secret decode ring.
--
Kevin Corkery
Independent Consultant
Voorhees, New Jersey
This archive was generated by hypermail 2b25 : Sun Jul 27 2008 - 05:05:07 EDT