This seems to be a common issue recently (not just FTP). We have several
emulators in here that showed various similar issues.

We used to code page 37 for our C code. The emulator QWS3270 used to
handle this OK (this emulator was the original one used for development
of the system here back in the mid 90s). Software AG Entire Connection
didn't handle C code well at all (typically the [] characters. They
eventually supplied a patch (several months later). We eventually
upgraded QWS3270 to the current version. It worked OK with code page
1047 but Ctrl/C and Ctrl/V didn't work with those characters. Jolly
Giant (QWS3270) shipped us a patch within one day to fix that problem.
As far as FTP goes, we use the DOS based command line FTP program and
have the MF translate the characters. Haven't seen a problem there but
don't FTP to the MF very often (mostly download with FTP for printouts)
and haven't seen any problems that way.

K

-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Nash
Sent: Wednesday, June 14, 2006 11:18 AM
To: [email protected]
Subject: Re: Looking for some 'alternatives'

On Tue, Jun 13, 2006 at 12:11:17PM -0400, Alan Altmark wrote:
> On Tuesday, 06/13/2006 at 10:15 AST, Yu Safin <[EMAIL PROTECTED]>
> wrote:
> > I need to point this out to our zOS guy.  Where do you stipulate
> > "EBCDIC NL"?  I suspect it is under the zOS USS and not on the FTP
> > client, correct?
>
> When you select the POSIX translation table (host code page 1047 if
> you want to select codepages instead), it will take care of
> translating ASCII LF to EBCDIC NL for you.  There is no explicit
> specification of NL.  The other [non-POSIX] translation tables will
> translate ASCII LF (0x0A) to EBCDIC LF (0x25), which tended [even
> today?] to upset readline/writeline functions in Java.

Has anyone noticed other characters getting mistranslated when ftp
uploading to z/OS? I had some trouble with ASCII punctuation in a C
program-- e.g., the `_' character was coming through untranslated and
the 0x5F code point isn't valid for a C program. I ended up using perl
and iconv to convert the file to codepage 1047 on my workstation and
then uploading the files in binary mode.

Seemed to work quite reliably, but what a pain.

-nash

--

"the lyf so short, the craft so long to lerne."
                    - Geoffrey Chaucer

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to