On 07/14/2008 11:07:41 AM Alan Altmark wrote:
> On Monday, 07/14/2008 at 10:58 EDT, Douglas Wooster/Raleigh/[EMAIL PROTECTED]
> wrote:
> > On 07/14/2008 12:35:26 AM Alan Altmark wrote:
> > > OPENVM GETBFS and PUTBFS, as well as XEDIT, allow you to specify the
> > > end-of-line sequence. The defaul
On Monday, 07/14/2008 at 10:58 EDT, Douglas Wooster/Raleigh/[EMAIL PROTECTED]
wrote:
> On 07/14/2008 12:35:26 AM Alan Altmark wrote:
> > OPENVM GETBFS and PUTBFS, as well as XEDIT, allow you to specify the
> > end-of-line sequence. The default is NL (0x15). You can also specify
> > CRLF (0x0D25),
On 07/14/2008 12:35:26 AM Alan Altmark wrote:
> On Thursday, 07/10/2008 at 01:02 EDT, Douglas Wooster/Raleigh/[EMAIL
> PROTECTED]
> wrote:
> > I got this after I sent my last post. Being a z/OS Unix user,
> > I sure *wish* conversions would consistently do EBCDIC NL (x'15')
> > to/from ASCII LF (
On Thursday, 07/10/2008 at 01:02 EDT, Douglas Wooster/Raleigh/[EMAIL PROTECTED]
wrote:
> I got this after I sent my last post. Being a z/OS Unix user,
> I sure *wish* conversions would consistently do EBCDIC NL (x'15')
> to/from ASCII LF (x'0A') instead of EBCDIC NL to/from ISO8859-1
> NEL (x'85')
On 07/10/2008 12:54:12 PM Stephen Frazier wrote:
> The reason for EBCDIC codepoints 15 and 25 is to be compatible
> with the IBM Selectric Typewriter. One of them would roll the
> paper forward a line with out moving the type ball. The other
> would put the type ball at the beginning of the next l
I got this after I sent my last post. Being a z/OS Unix user,
I sure *wish* conversions would consistently do EBCDIC NL (x'15')
to/from ASCII LF (x'0A') instead of EBCDIC NL to/from ISO8859-1
NEL (x'85'), even though I can understand why that might not be
technically correct. Or that z/OS Unix wo
The reason for EBCDIC codepoints 15 and 25 is to be compatible with the IBM
Selectric Typewriter.
One of them would roll the paper forward a line with out moving the type ball.
The other would put
the type ball at the beginning of the next line. Also their is another
codepoint 0A that moved the
On 07/10/2008 12:24:53 AM, Alan Altmark wrote:
> On Wednesday, 07/09/2008 at 07:33 EDT, Douglas Wooster/Raleigh/[EMAIL
> PROTECTED]
> wrote:
> > Added one more line separator to the list below. It usually burns me
> > when I use iconv.
> >
> :
> > NEL - New/Next Line (ASCII x'85'). May see thi
On Thursday, 07/10/2008 at 11:48 EDT, "Fargusson.Alan"
<[EMAIL PROTECTED]> wrote:
> NEL is defined in ISO8859-1 as code point 0x85. In 8859-1 there are
control
> characters in the range of 0x80 to 0x9f as well as 0x00 to 0x1f. Lots
of
> documentation on 8859-1 skip the control characters, so many
--Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Alan Altmark
Sent: Wednesday, July 09, 2008 9:25 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: line end characters (was SFTP versus FTP)
On Wednesday, 07/09/2008 at 07:33 EDT, Douglas Wooster/Raleigh/[EMAIL PROTEC
On Wednesday, 07/09/2008 at 07:33 EDT, Douglas Wooster/Raleigh/[EMAIL PROTECTED]
wrote:
> Added one more line separator to the list below. It usually burns me
> when I use iconv.
>
:
> NEL - New/Next Line (ASCII x'85'). May see this when EBCDIC
> data is translated to ASCII, as with iconv.
NEL
mmand to translate them
> and transform the end-of-line characters.
>
>
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf
> Of Edmund R. MacKenty
> Sent: Wednesday, July 09, 2008 1:02 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: SFTP versus F
MARIST.EDU
Sent by: Linux cc
on 390 Port
<[EMAIL PROTECTED] Subject
IST.EDU> Re: SFTP versus FTP
07/09/2008
fixed
Thanks again for all the help I got.
Tomasz
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Stewart
Thomas J
Sent: Wednesday, July 09, 2008 1:16 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: SFTP versus FTP
For reference, these are what you'll be
Sent by: Linux cc
on 390 Port
<[EMAIL PROTECTED] Subject
IST.EDU> Re: SFTP versus FTP
07/09/2008
02:02 PM
Please respond to
Linux on 390 Por
s of options for that. We do some transfers where we do
binary FTP them to z/OS and then use the iconv and Unix System Services cp
command to translate them and transform the end-of-line characters.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Edmund R.
Tomasz writes:
> I have a file on Unix server. When I transfer that file from Unix to Linux
> using FTP - I'm getting file with the same size.
> When I use SFTP, I'm getting file smaller by 79 bytes. The file has 79
> lines.
> That file is then FTP from Linux to z/OS - using FTP batch job on z/O
On 07/09/2008 01:00:22 PM, Szwed, Tomasz A CIV USMEPCOM wrote:
> I have a file on Unix server. When I transfer that file from Unix to
Linux
> using FTP - I'm getting file with the same size.
> When I use SFTP, I'm getting file smaller by 79 bytes. The file has 79
> lines.
> That file is then FTP
On Wednesday 09 July 2008 13:00, Szwed, Tomasz A CIV USMEPCOM wrote:
> I have a file on Unix server. When I transfer that file from Unix to Linux
>using FTP - I'm getting file with the same size.
>When I use SFTP, I'm getting file smaller by 79 bytes. The file has 79
>lines.
>That file is then FT
I have a file on Unix server. When I transfer that file from Unix to Linux
using FTP - I'm getting file with the same size.
When I use SFTP, I'm getting file smaller by 79 bytes. The file has 79
lines.
That file is then FTP from Linux to z/OS - using FTP batch job on z/OS (using
"get" command).
20 matches
Mail list logo
