If none of your data are binary, all character data use the same EBCDIC code page and all the characters exist in the target code page then that will work as far as visual fidelity is concerned. If you intend to use the data with a language processor then you also need to ensure that it supports the code point assignments of that code page. As an example, some implementations of REXX expect ¬ at 'AA'X while others expect it at 'AC'X.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Paul Gilmartin [[email protected]] Sent: Sunday, January 31, 2021 9:19 AM To: [email protected] Subject: Re: Inspecting and extracting from /OS transportable files on other platforms? On Sat, 30 Jan 2021 17:35:57 +0100, Bernd Oppolzer wrote: > >The problem is not at the client side (ASCII codepages); >the problem is that the EBCDIC codepages in Europe have the >exclamation point (!) at the place, where the American EBCDIC has |, >and so, if you transfer from an European EBCDIC codepage (273, for >example), >which is standard here in Europe, you will get exclamation points >instead of | >on the PC. > I'd expect the other way around: that I'd get '|' where an exclamation point appears in CP 273. But is there a case where FTP SITE SBDataconn does not suffice with built-in code pages? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
