Re: FTP from VSE to iseries

Using Block mode transport is a requirement for homogeneous record transfer of database file data via FTP, for if\when the file might contain any binary data that appears to be /stream mode/ delimiters; e.g. any of packed, varlen, integer, hex\binary data types are likely to include such characters, but others possibly also. Using BLOCK mode is functional in my experience, even for transport from other IBM EBCDIC systems. However it is not AFaIK, officially supported; see for example:
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/topic/rzaiq/rzaiqreferencedt1.htm
http://archive.midrange.com/midrange-l/200806/msg01114.html

Regards, Chuck

Panayiotis Petrou wrote:

We tried various options and have been able bypass the problem
with the following options. Thanks for your help.

EBCDIC MODE B LSITE LRECL 7250 CD SPTOOLS PUT %L4FEACT,ESDS,F L4FEACT
Simon Coulter wrote:

On 29/04/2010, at 3:11 PM, Panayiotis Petrou wrote:

Has anyone transferred data containing packed fields and how did you get around issues like the new line character x'15'

Transferring in Binary mode should resolve that. Although given
that both systems are EBCDIC then I'd expect EBCDIC mode to work too.

What sort of file are your transmitting? Given that it contains
packed- numeric fields it is likely a database file and
therefore has a fixed length. Isn't there a way to tell the VSE
system to expect fixed- length records? There must be
VSE-specific commands exposed through the VSE FTP server that
allow you to define characteristics of the transfer much as
OS/400 FTP supports TRIM, LISTFMT, NULLFLDS, and CRTCCSID. Run
HELP SERVER from within the OS/400 FTP client for more
information.

A quick Google search suggest that something like the VSE
command
DEFINE FILE ... RECFM=F LRECL=record-size
might do it.

I did that Google search about half an hour after the original message arrived here and IT WAS ALREADY IN GOOGLE!!! How good
is that? Midrange-L must be a high-traffic watched site.