Re: OCOPY fails to convert text

2014-03-04 Thread Shmuel Metz (Seymour J.)
In 5223415504632809.wa.paulgboulderaim@listserv.ua.edu, on 03/03/2014 at 05:07 PM, Paul Gilmartin paulgboul...@aim.com said: But, is there a convenient alternative collective term designating those 8-bit character sets in which 'A' is 0x41; '0' is 0x30, etc.? Perhaps Shmuel can, in a more

Re: OCOPY fails to convert text

2014-03-04 Thread Tony Harminc
On 3 March 2014 20:54, Farley, Peter x23353 peter.far...@broadridge.com wrote: GIYF. I refer you to these Wikipedia references, the first of which makes it quite clear that iso-8859-1 is definitely NOT Windows, though it does call it ASCII-based; and the second of which is a nice reference

Re: OCOPY fails to convert text

2014-03-04 Thread Paul Gilmartin
On Tue, 4 Mar 2014 12:24:41 -0500, Tony Harminc wrote: On 3 March 2014 20:54, Farley, Peter x23353 wrote: GIYF. I refer you to these Wikipedia references, the first of which makes it quite clear that iso-8859-1 is definitely NOT Windows, though it does call it ASCII-based; and the second of

Re: OCOPY fails to convert text

2014-03-04 Thread Shmuel Metz (Seymour J.)
In 2783130373802539.wa.paulgboulderaim@listserv.ua.edu, on 03/04/2014 at 12:21 PM, Paul Gilmartin paulgboul...@aim.com said: I think I'll go with ASCII-based until Shmuel objects. And long thereafter. That would be impossible. -- Shmuel (Seymour J.) Metz, SysProg and JOAT

Re: OCOPY fails to convert text

2014-03-03 Thread Shmuel Metz (Seymour J.)
In 60A88FF084694521B417F4096A824778@barryf93b83d71, on 03/01/2014 at 09:44 PM, retired mainframer retired-mainfra...@q.com said: Look at the meaning of the convert operand in UNIX System Services Command Reference. YES specifies conversion table BPXFX000 which, unless you have changed it, is

Re: OCOPY fails to convert text

2014-03-03 Thread Mark Yuhas
Thank you for the tip. However, I had to change the OCOPY statement to: ocopy indd(filein) outdd(fileout) , text convert('sys1.linklib(BPXFX311)') pathopts(use) FROM1047 Without the FROM1047, no conversion. Curiously, I OCOPYd a simple text file with the new format. OCOPY did not convert.

Re: OCOPY fails to convert text

2014-03-03 Thread retired mainframer
:: -Original Message- :: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On :: Behalf Of Shmuel Metz (Seymour J.) :: Sent: Sunday, March 02, 2014 3:31 PM :: To: IBM-MAIN@LISTSERV.UA.EDU :: Subject: Re: OCOPY fails to convert text

Re: OCOPY fails to convert text

2014-03-03 Thread Tony Harminc
On 2 March 2014 18:30, Shmuel Metz (Seymour J.) shmuel+ibm-m...@patriot.net wrote: [1] Does IBM have a z/OS code page for ISO 8859-15 yet? IBM has produced only two code pages for Latin-9; one ASCIIish (923) and one EBCDIC (924). Tony H.

Re: OCOPY fails to convert text

2014-03-03 Thread Paul Gilmartin
On Mon, 3 Mar 2014 14:32:43 -0800, retired mainframer wrote: :: :: ISO 8859-1[1] is Latin 1, not ASCII. From the UNIX Systems Services Command Reference: BPXFX311. Specifies an ASCII-EBCDIC conversion table to convert between code pages ISO8859-1 and IBM-1047. It doesn't matter what the

Re: OCOPY fails to convert text

2014-03-03 Thread Farley, Peter x23353
@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Monday, March 03, 2014 6:08 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: OCOPY fails to convert text On Mon, 3 Mar 2014 14:32:43 -0800, retired mainframer wrote: :: :: ISO 8859-1[1] is Latin 1, not ASCII. From the UNIX Systems Services Command

Re: OCOPY fails to convert text

2014-03-01 Thread retired mainframer
Look at the meaning of the convert operand in UNIX System Services Command Reference. YES specifies conversion table BPXFX000 which, unless you have changed it, is an alias for BPXFX111 which converts between IBM-037 and IBM-1047, both of which are EBCDIC. You probably need to specify BPXFX311