One other possible solution to Richard's FTP problem would
be to use the (undocumented) PIPE "ftpget" stage. It's
contained in the INSTPIPE MODULE file on z/VM 5.x and an
example of it's use can be seen on line 231 in the DVDPRIME
EXEC. It's how IBM loads the installation material to z/VM
from an FTP server.....

I offered to document the FTPGET stage for general use to
the folks in Endicott, as I think having it more widely
available would be a "Good Thing" (tm, M. Stewart), but I
never got a response back.....sigh....

Have a good one.

DJ
----- Original Message Follows -----
From: "Jones, Zachary" <[EMAIL PROTECTED]>
To: [email protected]
Subject: Re: FTP Linux - CMS
Date: Tue, 6 Mar 2007 08:10:36 -0500

> Richard,
> 
> Setting the ftp download type to ASCII will do the
> automatic conversion to and from ASCII/EBCDIC.
> Then you use the ftp locsite command to set the fixed
> length.
> 
> So do the below then your get and it will be in the format
> you want. (fix length 80 example).
> 
> ASCII
> LOCSITE FIX 80 
> 
> Now do your get command.
> 
> 
> Zachary Jones
> Operations Systems Analyst
> Northrop Grumman 
> City of Grand Rapids Michigan
> 
> 
> 
> On Mon, 2007-03-05 at 15:56 -0800, Schuh, Richard wrote:
> 
> > We have a need to transfer text files (extension of TXT)
> > from Linux (running in an IFL LPAR) to CMS. The FTP is
> > to be initiated by the CMS user. The files are ASCII, as
> > you might expect. The lines/records end in a LineFeed
> > (0A). I have not been able to come up with a way to
> translate the data from ASCII to EBCDIC and write the
> > records to a CMS file in the FTP. I can transfer the
> > file as "BINARY F nn" records and pass the resultant
> > file through a pipe ("PIPE < file | strip trailing 00 |
> deblock linend 0a | xlate a2e | > newfile") that does the
> > job, but it seems that there ought to be a way to
> > accomplish the entire job in FTP. Everything I have
> > tried other than the "BINARY F nn" results in a message
> > that the stream is too big.  
> > What am I missing?
> > 
> > Regards,
> > Richard Schuh 
> > 
> > 
> 

Reply via email to