Re: XMITIP - NLS support for Arabic character
Yes not friendly I know the CSSMTPAafter 2.4 support MBCS(multi byte character set). So I can try defining a new UNICODE MBCS set. I have been looking for an example in unicode service guide to define MBCS code page but there is no example in it or any explanation Is there any manual which talks about defining MBCS code page ? Peter On Thu, 20 May, 2021, 5:42 am Paul Gilmartin, < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Tue, 11 May 2021 10:21:28 +0400, Peter wrote: > > > >I understand CSSMTPA Doesnt support IBM-420 , but I guess ICONV services > >can be used to define a new arabic code page. > > > Not 420-friendly? > > -- gil > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMITIP - NLS support for Arabic character
On Tue, 11 May 2021 10:21:28 +0400, Peter wrote: > >I understand CSSMTPA Doesnt support IBM-420 , but I guess ICONV services >can be used to define a new arabic code page. > Not 420-friendly? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMITIP - NLS support for Arabic character
On Mon, 17 May 2021 19:30:42 +, Chris Hoelscher wrote: >Aladdin - he was an Arabic character, wasn't he!!! > No. Arabian. I found a reference that mentions both UTF-8 (IBM-1208) and CSSMTP, but not exactly together: ftp://public.dhe.ibm.com/s390/zos/racf/pdf/ny_naspa_2019_05_14_whats_new_in_zos_v2r4.pdf (Extracted from: https://www.google.com/url?sa=t=j==s=web==2ahUKEwjMhY3MttTwAhVFWs0KHasJAoEQFjAGegQIBxAD=ftp%3A%2F%2Fpublic.dhe.ibm.com%2Fs390%2Fzos%2Fracf%2Fpdf%2Fny_naspa_2019_05_14_whats_new_in_zos_v2r4.pdf=AOvVaw0kYULaFz-AXjmQEH7hcKV4 ) 2019? FTP!? (https://... works alike. Would that IBM could be so clever with its HOLDDATA page.) -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMITIP - NLS support for Arabic character
Aladdin - he was an Arabic character, wasn't he!!! Chris Hoelscher Lead Sys DBA IBM Global Technical Services on assignmemt to Humana Inc. T 502.476.2538 or 502.407.7266 -Original Message- From: IBM Mainframe Discussion List On Behalf Of Paul Gilmartin Sent: Monday, May 17, 2021 11:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [IBM-MAIN] XMITIP - NLS support for Arabic character [External Email: Use caution with links and attachments] On Sun, 16 May 2021 20:31:13 +0400, Peter wrote: > >I am using XMITIP plus TXT2PDF for getting PDF and excel Files in >Arabic (CSSMTP being used), But when the PDF or spreadsheet reaches the >outlook email box the PDF or Spreadsheet contents are intact but the >email body has a ARABIC in Junk format. I believe XMITIP has NLS >facility to generate Arabic support but I dont know where to start. > Have you tried simply transmitting the PDF as BINARY? What format are the spreadsheets: o .csv? o .xlsx? o other (specify)? If .csv, try: iconv -f IBM-420 -t UTF-8 csv.utf-8 echo $? ... then transfer the converted .csv in BINARY to your desktop and open it. >Can i use ICONV to define a new IBM-420 codepage ? If so Should i get >those Hex values as input file to generate Code page for IBM-420 using >ICONV > following links from https://urldefense.com/v3/__https://www.lbdsoftware.com/tcpip.html__;!!IfVdvpvC!Foj6Kuu8xqCvyLt73H7ktkenJWJLiEMdN13HYGseSRYsOgXpKgmG8CSqQMNgdEeo$ I find a downloadable txt2pdf-19.113.tar.gz. In there, I find: 1049 $ ( cd txt2pdf-19.113/ucm & cat read* & ls -lrt ) These are some sample UCM files that can be used for encoding PDFs in other than Adobe WinAnsiEncoding. The full store of UCMs can be found at: https://urldefense.com/v3/__http://source.icu-project.org/repos/icu/data/trunk/charset/data/ucm/__;!!IfVdvpvC!Foj6Kuu8xqCvyLt73H7ktkenJWJLiEMdN13HYGseSRYsOgXpKgmG8CSqQDgwvfrw$ total 56 -rwxr-xr-x@ 1 paulgilm staff 6342 Apr 17 2009 ibm-1047_P100-1995.ucm -rwxr-xr-x@ 1 paulgilm staff 6326 Apr 17 2009 ibm-1025_P100-1995.ucm -rwxr-xr-x@ 1 paulgilm staff 6342 Apr 17 2009 ibm-1026_P100-1995.ucm -rwxr-xr-x@ 1 paulgilm staff 216 Apr 17 2009 readme.txt The doc suggests the .ucm are for code page translation. All three bear IBM copyright notices. Perhaps IBM can supply an ibm-420.ucm file. The icu-project.org URL seems outdated. The code is Rexx. >I also understand CUNRCSM can also help to achieve the same but I never >used it. Does anyone has experience using CUNRCSM along with >XMITIP(CSSMTP) to use Arabic font to do ? > I don't know it. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. Humana Inc. and its subsidiaries comply with applicable Federal civil rights laws and do not discriminate on the basis of race, color, national origin, ancestry, age, disability, sex, marital status, gender, sexual orientation, gender identity, or religion. Humana Inc. and its subsidiaries do not exclude people or treat them differently because of race, color, national origin, ancestry, age, disability, sex, marital status, gender, sexual orientation, gender identity, or religion. English: ATTENTION: If you do not speak English, language assistance services, free of charge, are available to you. Call 1‐877‐320‐1235 (TTY: 711). Español (Spanish): ATENCIÓN: Si habla español, tiene a su disposición servicios gratuitos de asistencia lingüística. Llame al 1‐877‐320‐1235 (TTY: 711). 繁體中文(Chinese):注意:如果您使用繁體中文,您可以免費獲得語言援助 服務。請致電 1‐877‐320‐1235 (TTY: 711)。 Kreyòl Ayisyen (Haitian Creole): ATANSION: Si w pale Kreyòl Ayisyen, gen sèvis èd pou lang ki disponib gratis pou ou. Rele 1‐877‐320‐1235 (TTY: 711). Polski (Polish): UWAGA: Jeżeli mówisz po polsku, możesz skorzystać z bezpłatnej pomocy językowej. Zadzwoń pod numer 1‐877‐320‐1235 (TTY: 711). 한국어 (Korean): 주의: 한국어를 사용하시는 경우, 언어 지원 서비스를 무료로 이용하실 수 있습니다. 1‐877‐320‐1235 (TTY: 711)번으로 전화해 주십시오. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMITIP - NLS support for Arabic character
On Sun, 16 May 2021 20:31:13 +0400, Peter wrote: > >I am using XMITIP plus TXT2PDF for getting PDF and excel Files in Arabic >(CSSMTP being used), But when the PDF or spreadsheet reaches the outlook >email box the PDF or Spreadsheet contents are intact but the email body has >a ARABIC in Junk format. I believe XMITIP has NLS facility to generate >Arabic support but I dont know where to start. > Have you tried simply transmitting the PDF as BINARY? What format are the spreadsheets: o .csv? o .xlsx? o other (specify)? If .csv, try: iconv -f IBM-420 -t UTF-8 csv.utf-8 echo $? ... then transfer the converted .csv in BINARY to your desktop and open it. >Can i use ICONV to define a new IBM-420 codepage ? If so Should i get those >Hex values as input file to generate Code page for IBM-420 using ICONV > following links from https://www.lbdsoftware.com/tcpip.html I find a downloadable txt2pdf-19.113.tar.gz. In there, I find: 1049 $ ( cd txt2pdf-19.113/ucm & cat read* & ls -lrt ) These are some sample UCM files that can be used for encoding PDFs in other than Adobe WinAnsiEncoding. The full store of UCMs can be found at: http://source.icu-project.org/repos/icu/data/trunk/charset/data/ucm/ total 56 -rwxr-xr-x@ 1 paulgilm staff 6342 Apr 17 2009 ibm-1047_P100-1995.ucm -rwxr-xr-x@ 1 paulgilm staff 6326 Apr 17 2009 ibm-1025_P100-1995.ucm -rwxr-xr-x@ 1 paulgilm staff 6342 Apr 17 2009 ibm-1026_P100-1995.ucm -rwxr-xr-x@ 1 paulgilm staff 216 Apr 17 2009 readme.txt The doc suggests the .ucm are for code page translation. All three bear IBM copyright notices. Perhaps IBM can supply an ibm-420.ucm file. The icu-project.org URL seems outdated. The code is Rexx. >I also understand CUNRCSM can also help to achieve the same but I never >used it. Does anyone has experience using CUNRCSM along with XMITIP(CSSMTP) >to use Arabic font to do ? > I don't know it. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMITIP - NLS support for Arabic character
On Sun, 16 May 2021 20:31:13 +0400, Peter wrote: > >I am using XMITIP plus TXT2PDF for getting PDF and excel Files in Arabic >(CSSMTP being used), But when the PDF or spreadsheet reaches the outlook >email box the PDF or Spreadsheet contents are intact but the email body has >a ARABIC in Junk format. I believe XMITIP has NLS facility to generate >Arabic support but I dont know where to start. > The TXT2PDF Users Guide at: http://www.lbdsoftware.com/tcpip.html http://www.lbdsoftware.com/TXT2PDF-User-Guide.pdf https://homerow.net/rexx/txt2pdf/ for downloads and samples. ... has some hint of UNICODE support. It's probably not easy. A lost motorist asked a New England farmer for help" "How can I get to Boston?" "If I was you, I wouldn't start from here!" -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMITIP - NLS support for Arabic character
What about bidi conversion services? <https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R4sa380680/$file/cunu100_v2r4.pdf> -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Paul Gilmartin [000433f07816-dmarc-requ...@listserv.ua.edu] Sent: Sunday, May 16, 2021 11:26 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: XMITIP - NLS support for Arabic character On Sun, 16 May 2021 09:06:10 -0500, Joel C. Ewing wrote: > >I don't know whether CSSMTP employs EBCDIC to ASCII conversion for >everything or has the smarts to restrict that conversion to headers and >ordinary text. If for everything, then obviously the only way to send >UTF-8 via XMITIP, JES and CSSMTP would be for XMITIP to put it in the >email body as a base-64 encoded segment. > https://secure-web.cisco.com/1Og8XVlkbqxNKTpA4EzFq6H7i4U33pA3oAiT6MRd_8VVAvh2Y5ubNAqE-iCvQEU77Crro_ltesqbX6YuSwj9YqWIOlBhdLO1nZdYaNnNgDd_snG5KPDzTbpgLNSzPGzVuGfYpsgKYs4PvRF7Fy0CTm2r2Xvt3Pd6MRv46mB1sZEuPcXKllVkFuJc2ZyG0mKuwQ0zN0I6r-Ew4SOHKwy8gjWZ90gzBwxxfjJpEwe0YPorwnAtdQwCAGmjgQ6SXRfpTX4Oa6szd4uaWbrhEsPiZElnHzWKHEqoBdJzhS1soANXwLzBOmGgYbdxCZMma1PmQGSLMdZOKKiO3Z_1VNdOd7Du_QX1WqSH9AuAMpsn5hgDAolAqjVWJCiAhetALZlcL57l84wPUKMbIN2wz24oPeDdwI64Lu1U_NjuAfPHrurftHA7A3DcKmO1lOY6neLVP/https%3A%2F%2Fwww.lbdsoftware.com%2FXMITIP-Guide.pdf Note that all data on the mainframe is stored in the EBCDIC character set and is translated to the ASCII character set during the transmission. Any data that should not be translated should be attached in Binary format. Possibly: iconv -f IBM-420 -t UTF-8 Then transmit as BINary. You might yet be frustrated because IBM mainframes (I believe) store Arabic, etc. text backwards. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMITIP - NLS support for Arabic character
> The IBM-MAIN LISTSERV is not RFC 2047 savvy. Then I assume that it's also not RFC 5335 savvy :-( -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Paul Gilmartin [000433f07816-dmarc-requ...@listserv.ua.edu] Sent: Sunday, May 16, 2021 12:05 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: XMITIP - NLS support for Arabic character On Sun, 16 May 2021 10:26:25 -0500, Paul Gilmartin wrote: >... >https://secure-web.cisco.com/10-9O4qCa7_vMf2YZ4R5r0f37sYvyc0NARfLKcDBC8nnijgiQbZTekOlWUh42br7RjZr1OHzSB6-_jfR9kMMabW-IOIpoHysCdKtvGkxPVuEVoc6XJIgWqfbv6e0pgImFAX-Zf06oGNvz-iL8osGVF3rkQ1FV7BM8QWJIPyi6I2ozsZ1wkO-vgyMkKviEMteNAjodWa2DlSHEjDNhkeuh0UQASqLVKR2KE9pUSj0mxIUNJ3rf6eGkTG-iIcJYrMJ6gx1vDCWRSDU4FoFRzecQ1DU3zggBOh8I6KD1WO8fnzckESnPX4cU34BJgZCNXCoGmaWt4w_LiG7B1n2i8rCVPyCwEnO8RfDlLIyeQEIg13IAO7kxVTNakKuHxHLsc_MYbFFtmd9y5BNYacznByUvb7tDDF8BO-9ixNewRNZigdtIPfaXIf-ILeUXB_nDMAlf/https%3A%2F%2Fwww.lbdsoftware.com%2FXMITIP-Guide.pdf >Note that all data on the mainframe is stored in the EBCDIC character set >and is translated to the ASCII character set during the transmission. >Any data that should not be translated should be attached in Binary format. > (More): o Note that since EBCDIC is a 256-character set and ASCII is 128, there is inevitable loss of information. o It doesn't specify *which* EBCDIC character set (there are many, not "the".) >Possibly: iconv -f IBM-420 -t UTF-8 >Then transmit as FORMAT BINary. > >You might yet be frustrated because IBM mainframes (I believe) >store Arabic, etc. text backwards. On Sun, 16 May 2021 09:06:10 -0500, Joel C. Ewing wrote: >Terminology Clarification: UTF-8 is of course just one representation >of the Unicode codeset, not the codeset itself. UTF-8 has the advantage >that characters in standard ASCII charset have identical byte >representation in UTF-8, which makes possible some use of UTF-8 even in >email headers. > Use of encoded non-ASCII characters in headers requires considerable gyrations. See section 2 of RFC 2047. The IBM-MAIN LISTSERV is not RFC 2047 savvy. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMITIP - NLS support for Arabic character
Non-ASCII text should be relegated to MIME attachments unless your message header specifies a charset. As always, the hard question is what CSSMTP handles correctly. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Peter [dbajava...@gmail.com] Sent: Sunday, May 16, 2021 12:31 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: XMITIP - NLS support for Arabic character Hello Paul, I am using XMITIP plus TXT2PDF for getting PDF and excel Files in Arabic (CSSMTP being used), But when the PDF or spreadsheet reaches the outlook email box the PDF or Spreadsheet contents are intact but the email body has a ARABIC in Junk format. I believe XMITIP has NLS facility to generate Arabic support but I dont know where to start. Can i use ICONV to define a new IBM-420 codepage ? If so Should i get those Hex values as input file to generate Code page for IBM-420 using ICONV I also understand CUNRCSM can also help to achieve the same but I never used it. Does anyone has experience using CUNRCSM along with XMITIP(CSSMTP) to use Arabic font to do ? On Sun, May 16, 2021 at 4:38 PM Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Sun, 16 May 2021 11:22:11 +0400, Peter wrote: > > > >I did but file.txt is empty, but the command executed successfully > > > >On Sun, 16 May, 2021, 11:01 am Mike Schwab wrote: > > > >> The Greater than symbol sends the output to the file. > >> Try again without the Greater than symbol so it is the output file. > >> > Rather, I believe Peter understood the iconv syntax correctly. > > >> On Sun, May 16, 2021 at 1:36 AM Peter wrote: > >> > > >> > I used this command from OMVS > >> > > >> > iconv -f IBM-420 -t IBM-1047 file.txt>file.txt.converted > >> > > >> > I see the converted file is empty, Should I have file.txt populated > with > >> > ARABIC codes in it ? > >> > > Yes. Is that what you have? > > Translating -f IBM-420 -t IBM-1047 is futile because most of the > characters in IBM-420 don't exist in IBM-1047. > > Describe your problem in detail. Do you have a file in IBM-420 that you > want > to mail? Could you even post a sample to this list? Something like: > تماثيل الحدائق > (selected randomly from the Web.) > > z/OS may make it unnecessarily difficult for you because z/OS > stores Arabic text backwards. > > > >> > On Tue, 11 May, 2021, 8:02 pm Paul Gilmartin wrote: > >> >... > >> > > >I have never used ICONV services before, is there a document which > helps to > >> > > >understand the usage of ICONV ? > >> > > > >> > https://www.ibm.com/docs/en/zos/2.4.0?topic=scd-iconv-convert-characters-from-one-code-set-another > >> > https://www.ibm.com/docs/en/zos/2.4.0?topic=functions-iconv-code-conversion > >> > https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R3sa380680?OpenDocument > >> > > > >> > > >On Sun, 9 May, 2021, 9:11 pm Lizette Koehler wrote: > >> > > > > >> > > >> I might recommend a review of the website > >> > > >> http://secure-web.cisco.com/1hegoxil4V0fPcjOe52OQr-uLQl7-WqZGwrQZ9dbuADhj_JfpvsqeU4gWl8WfulAQ-MGSooHNr1WUJb_GDJT5_shatD-mDLAMKA1HrsR5oyyBpBVFwseCtFL4mDLi3ACjVV_ebXaGxXpEgrwaDlrEGskf5Iv5g21c6TPelsczKFUNNbSIY6tmPUDqKirEWk3M0DOxQ2WhlNcylM-xVlWoLhWOvneAon4t8WDdr0253DVehZ69IoWH2O0vn-Alj7jZOUKJHmUj71uuZpB7UsR8O9ig5S18XqlsZUT6w4bMpAqKn7fWXxI1hgSiZ0WHL5ZLEI_fd-Y1oF_zHw0dRodXGr8SqXwrzNWF543B6MdJBX1nKBf63GOSmCKRCSHa8BAMx-r-Z6_FzioiZwtp6GMuI4pHTwTfdJ2lkXoO__cO10HJ7ZBckwGiDVJmU9nJ72ge/http%3A%2F%2Flbdsoftware.com%2Fxmitip.html > >> > > >> . See if there is any help > there > > -- gil > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMITIP - NLS support for Arabic character
Hello Paul, I am using XMITIP plus TXT2PDF for getting PDF and excel Files in Arabic (CSSMTP being used), But when the PDF or spreadsheet reaches the outlook email box the PDF or Spreadsheet contents are intact but the email body has a ARABIC in Junk format. I believe XMITIP has NLS facility to generate Arabic support but I dont know where to start. Can i use ICONV to define a new IBM-420 codepage ? If so Should i get those Hex values as input file to generate Code page for IBM-420 using ICONV I also understand CUNRCSM can also help to achieve the same but I never used it. Does anyone has experience using CUNRCSM along with XMITIP(CSSMTP) to use Arabic font to do ? On Sun, May 16, 2021 at 4:38 PM Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Sun, 16 May 2021 11:22:11 +0400, Peter wrote: > > > >I did but file.txt is empty, but the command executed successfully > > > >On Sun, 16 May, 2021, 11:01 am Mike Schwab wrote: > > > >> The Greater than symbol sends the output to the file. > >> Try again without the Greater than symbol so it is the output file. > >> > Rather, I believe Peter understood the iconv syntax correctly. > > >> On Sun, May 16, 2021 at 1:36 AM Peter wrote: > >> > > >> > I used this command from OMVS > >> > > >> > iconv -f IBM-420 -t IBM-1047 file.txt>file.txt.converted > >> > > >> > I see the converted file is empty, Should I have file.txt populated > with > >> > ARABIC codes in it ? > >> > > Yes. Is that what you have? > > Translating -f IBM-420 -t IBM-1047 is futile because most of the > characters in IBM-420 don't exist in IBM-1047. > > Describe your problem in detail. Do you have a file in IBM-420 that you > want > to mail? Could you even post a sample to this list? Something like: > تماثيل الحدائق > (selected randomly from the Web.) > > z/OS may make it unnecessarily difficult for you because z/OS > stores Arabic text backwards. > > > >> > On Tue, 11 May, 2021, 8:02 pm Paul Gilmartin wrote: > >> >... > >> > > >I have never used ICONV services before, is there a document which > helps to > >> > > >understand the usage of ICONV ? > >> > > > >> > https://www.ibm.com/docs/en/zos/2.4.0?topic=scd-iconv-convert-characters-from-one-code-set-another > >> > https://www.ibm.com/docs/en/zos/2.4.0?topic=functions-iconv-code-conversion > >> > https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R3sa380680?OpenDocument > >> > > > >> > > >On Sun, 9 May, 2021, 9:11 pm Lizette Koehler wrote: > >> > > > > >> > > >> I might recommend a review of the website > >> > > >> http://lbdsoftware.com/xmitip.html . See if there is any help > there > > -- gil > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMITIP - NLS support for Arabic character
On Sun, 16 May 2021 10:26:25 -0500, Paul Gilmartin wrote: >... >https://www.lbdsoftware.com/XMITIP-Guide.pdf >Note that all data on the mainframe is stored in the EBCDIC character set >and is translated to the ASCII character set during the transmission. >Any data that should not be translated should be attached in Binary format. > (More): o Note that since EBCDIC is a 256-character set and ASCII is 128, there is inevitable loss of information. o It doesn't specify *which* EBCDIC character set (there are many, not "the".) >Possibly: iconv -f IBM-420 -t UTF-8 >Then transmit as FORMAT BINary. > >You might yet be frustrated because IBM mainframes (I believe) >store Arabic, etc. text backwards. On Sun, 16 May 2021 09:06:10 -0500, Joel C. Ewing wrote: >Terminology Clarification: UTF-8 is of course just one representation >of the Unicode codeset, not the codeset itself. UTF-8 has the advantage >that characters in standard ASCII charset have identical byte >representation in UTF-8, which makes possible some use of UTF-8 even in >email headers. > Use of encoded non-ASCII characters in headers requires considerable gyrations. See section 2 of RFC 2047. The IBM-MAIN LISTSERV is not RFC 2047 savvy. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMITIP - NLS support for Arabic character
On Sun, 16 May 2021 09:06:10 -0500, Joel C. Ewing wrote: > >I don't know whether CSSMTP employs EBCDIC to ASCII conversion for >everything or has the smarts to restrict that conversion to headers and >ordinary text. If for everything, then obviously the only way to send >UTF-8 via XMITIP, JES and CSSMTP would be for XMITIP to put it in the >email body as a base-64 encoded segment. > https://www.lbdsoftware.com/XMITIP-Guide.pdf Note that all data on the mainframe is stored in the EBCDIC character set and is translated to the ASCII character set during the transmission. Any data that should not be translated should be attached in Binary format. Possibly: iconv -f IBM-420 -t UTF-8 Then transmit as BINary. You might yet be frustrated because IBM mainframes (I believe) store Arabic, etc. text backwards. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMITIP - NLS support for Arabic character
UTF-8 is a transform of Unicode that has been endorsed by the IETF; see RFC 5198. Over time, support will become increasingly critical. Do not see RFC 4042. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Joel C. Ewing [jce.ebe...@cox.net] Sent: Sunday, May 16, 2021 10:06 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: XMITIP - NLS support for Arabic character Terminology Clarification: UTF-8 is of course just one representation of the Unicode codeset, not the codeset itself. UTF-8 has the advantage that characters in standard ASCII charset have identical byte representation in UTF-8, which makes possible some use of UTF-8 even in email headers. I don't know whether CSSMTP employs EBCDIC to ASCII conversion for everything or has the smarts to restrict that conversion to headers and ordinary text. If for everything, then obviously the only way to send UTF-8 via XMITIP, JES and CSSMTP would be for XMITIP to put it in the email body as a base-64 encoded segment. The most complete solution for full-function email from z/OS a decade ago was to pass the email directly to an SMTP server on a Unix or Windows platform. That may still be true. JC Ewing On 5/16/21 8:11 AM, Joel C. Ewing wrote: > I think there is a misconception here about codesets. iconv converts > characters in one codeset to corresponding characters in another codeset > , PROVIDED the character exists in the other codeset. The character > codes supported in the target codeset are by definition fixed. If > there is no corresponding character code in the target codeset, you > would expect the original character to vanish. > > What is needed is some way for XMITIP to support using Unicode UTF-8 in > an email within the constraints of the EBCDIC character codeset expected > by JES and by the parameters to XMITIP. You could then in theory send > email containing any national EBCDIC codeset by using iconv to convert > any special language codeset to UTF-8 and send it as UTF-8 characters > > It should at least be possible to tell XMITIP to use a file in UTF-8 > codeset for the email body and have XMITIP use base-64 encoding for the > email body like was forced in past years (and even occasionally today) > by some email transfer agents that don't advertise support for 8-bit > characters. Perhaps there is not even a serious conflict with just > telling XMITIP that its email data is to be handled as UTF-8 and having > XMITIP put it in in the JES queue as UTF-8 with appropriate header > information, assuming that such can be handled by the z/OS email address > space without problems. > > Support for generating an email with content that is UTF-8 could > certainly be added to XMITIP in some form. Formatting the email > manually with the required control information is certainly another > possibility, but would be a pain to be avoided. > Joel C Ewing > > On 5/16/21 2:22 AM, Peter wrote: >> Hello >> >> I did but file.txt is empty, but the command executed successfully >> >> On Sun, 16 May, 2021, 11:01 am Mike Schwab, wrote: >> >>> The Greater than symbol sends the output to the file. >>> Try again without the Greater than symbol so it is the output file. >>> >>> On Sun, May 16, 2021 at 1:36 AM Peter wrote: >>>> Hello Paul >>>> >>>> I used this command from OMVS >>>> >>>> iconv -f IBM-420 -t IBM-1047 file.txt>file.txt.converted >>>> >>>> I see the converted file is empty, Should I have file.txt populated with >>>> ARABIC codes in it ? >>>> >>>> Peter >>>> >>>> On Tue, 11 May, 2021, 8:02 pm Paul Gilmartin, < >>>> 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: >>>> >>>>> On Tue, 11 May 2021 10:21:28 +0400, Peter wrote: >>>>> >>>>>> Hi >>>>>> >>>>>> I understand CSSMTPA Doesnt support IBM-420 , but I guess ICONV >>> services > ... > -- Joel C. Ewing -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMITIP - NLS support for Arabic character
Terminology Clarification: UTF-8 is of course just one representation of the Unicode codeset, not the codeset itself. UTF-8 has the advantage that characters in standard ASCII charset have identical byte representation in UTF-8, which makes possible some use of UTF-8 even in email headers. I don't know whether CSSMTP employs EBCDIC to ASCII conversion for everything or has the smarts to restrict that conversion to headers and ordinary text. If for everything, then obviously the only way to send UTF-8 via XMITIP, JES and CSSMTP would be for XMITIP to put it in the email body as a base-64 encoded segment. The most complete solution for full-function email from z/OS a decade ago was to pass the email directly to an SMTP server on a Unix or Windows platform. That may still be true. JC Ewing On 5/16/21 8:11 AM, Joel C. Ewing wrote: > I think there is a misconception here about codesets. iconv converts > characters in one codeset to corresponding characters in another codeset > , PROVIDED the character exists in the other codeset. The character > codes supported in the target codeset are by definition fixed. If > there is no corresponding character code in the target codeset, you > would expect the original character to vanish. > > What is needed is some way for XMITIP to support using Unicode UTF-8 in > an email within the constraints of the EBCDIC character codeset expected > by JES and by the parameters to XMITIP. You could then in theory send > email containing any national EBCDIC codeset by using iconv to convert > any special language codeset to UTF-8 and send it as UTF-8 characters > > It should at least be possible to tell XMITIP to use a file in UTF-8 > codeset for the email body and have XMITIP use base-64 encoding for the > email body like was forced in past years (and even occasionally today) > by some email transfer agents that don't advertise support for 8-bit > characters. Perhaps there is not even a serious conflict with just > telling XMITIP that its email data is to be handled as UTF-8 and having > XMITIP put it in in the JES queue as UTF-8 with appropriate header > information, assuming that such can be handled by the z/OS email address > space without problems. > > Support for generating an email with content that is UTF-8 could > certainly be added to XMITIP in some form. Formatting the email > manually with the required control information is certainly another > possibility, but would be a pain to be avoided. > Joel C Ewing > > On 5/16/21 2:22 AM, Peter wrote: >> Hello >> >> I did but file.txt is empty, but the command executed successfully >> >> On Sun, 16 May, 2021, 11:01 am Mike Schwab, wrote: >> >>> The Greater than symbol sends the output to the file. >>> Try again without the Greater than symbol so it is the output file. >>> >>> On Sun, May 16, 2021 at 1:36 AM Peter wrote: Hello Paul I used this command from OMVS iconv -f IBM-420 -t IBM-1047 file.txt>file.txt.converted I see the converted file is empty, Should I have file.txt populated with ARABIC codes in it ? Peter On Tue, 11 May, 2021, 8:02 pm Paul Gilmartin, < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Tue, 11 May 2021 10:21:28 +0400, Peter wrote: > >> Hi >> >> I understand CSSMTPA Doesnt support IBM-420 , but I guess ICONV >>> services > ... > -- Joel C. Ewing -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMITIP - NLS support for Arabic character
It might be desirable to have an encoding option in XMITIP when generating MIME attachments with charset=utf-8. A file containg a lot of ASCII text would be much more compact encoded with QP (ptui!) than with BASE64. All of this, of course, assumes that CSSMTP won't mess it up. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Joel C. Ewing [jce.ebe...@cox.net] Sent: Sunday, May 16, 2021 9:11 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: XMITIP - NLS support for Arabic character I think there is a misconception here about codesets. iconv converts characters in one codeset to corresponding characters in another codeset , PROVIDED the character exists in the other codeset. The character codes supported in the target codeset are by definition fixed. If there is no corresponding character code in the target codeset, you would expect the original character to vanish. What is needed is some way for XMITIP to support using Unicode UTF-8 in an email within the constraints of the EBCDIC character codeset expected by JES and by the parameters to XMITIP. You could then in theory send email containing any national EBCDIC codeset by using iconv to convert any special language codeset to UTF-8 and send it as UTF-8 characters It should at least be possible to tell XMITIP to use a file in UTF-8 codeset for the email body and have XMITIP use base-64 encoding for the email body like was forced in past years (and even occasionally today) by some email transfer agents that don't advertise support for 8-bit characters. Perhaps there is not even a serious conflict with just telling XMITIP that its email data is to be handled as UTF-8 and having XMITIP put it in in the JES queue as UTF-8 with appropriate header information, assuming that such can be handled by the z/OS email address space without problems. Support for generating an email with content that is UTF-8 could certainly be added to XMITIP in some form. Formatting the email manually with the required control information is certainly another possibility, but would be a pain to be avoided. Joel C Ewing On 5/16/21 2:22 AM, Peter wrote: > Hello > > I did but file.txt is empty, but the command executed successfully > > On Sun, 16 May, 2021, 11:01 am Mike Schwab, wrote: > >> The Greater than symbol sends the output to the file. >> Try again without the Greater than symbol so it is the output file. >> >> On Sun, May 16, 2021 at 1:36 AM Peter wrote: >>> Hello Paul >>> >>> I used this command from OMVS >>> >>> iconv -f IBM-420 -t IBM-1047 file.txt>file.txt.converted >>> >>> I see the converted file is empty, Should I have file.txt populated with >>> ARABIC codes in it ? >>> >>> Peter >>> >>> On Tue, 11 May, 2021, 8:02 pm Paul Gilmartin, < >>> 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: >>> >>>> On Tue, 11 May 2021 10:21:28 +0400, Peter wrote: >>>> >>>>> Hi >>>>> >>>>> I understand CSSMTPA Doesnt support IBM-420 , but I guess ICONV >> services ... -- Joel C. Ewing -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMITIP - NLS support for Arabic character
I think there is a misconception here about codesets. iconv converts characters in one codeset to corresponding characters in another codeset , PROVIDED the character exists in the other codeset. The character codes supported in the target codeset are by definition fixed. If there is no corresponding character code in the target codeset, you would expect the original character to vanish. What is needed is some way for XMITIP to support using Unicode UTF-8 in an email within the constraints of the EBCDIC character codeset expected by JES and by the parameters to XMITIP. You could then in theory send email containing any national EBCDIC codeset by using iconv to convert any special language codeset to UTF-8 and send it as UTF-8 characters It should at least be possible to tell XMITIP to use a file in UTF-8 codeset for the email body and have XMITIP use base-64 encoding for the email body like was forced in past years (and even occasionally today) by some email transfer agents that don't advertise support for 8-bit characters. Perhaps there is not even a serious conflict with just telling XMITIP that its email data is to be handled as UTF-8 and having XMITIP put it in in the JES queue as UTF-8 with appropriate header information, assuming that such can be handled by the z/OS email address space without problems. Support for generating an email with content that is UTF-8 could certainly be added to XMITIP in some form. Formatting the email manually with the required control information is certainly another possibility, but would be a pain to be avoided. Joel C Ewing On 5/16/21 2:22 AM, Peter wrote: > Hello > > I did but file.txt is empty, but the command executed successfully > > On Sun, 16 May, 2021, 11:01 am Mike Schwab, wrote: > >> The Greater than symbol sends the output to the file. >> Try again without the Greater than symbol so it is the output file. >> >> On Sun, May 16, 2021 at 1:36 AM Peter wrote: >>> Hello Paul >>> >>> I used this command from OMVS >>> >>> iconv -f IBM-420 -t IBM-1047 file.txt>file.txt.converted >>> >>> I see the converted file is empty, Should I have file.txt populated with >>> ARABIC codes in it ? >>> >>> Peter >>> >>> On Tue, 11 May, 2021, 8:02 pm Paul Gilmartin, < >>> 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: >>> On Tue, 11 May 2021 10:21:28 +0400, Peter wrote: > Hi > > I understand CSSMTPA Doesnt support IBM-420 , but I guess ICONV >> services ... -- Joel C. Ewing -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMITIP - NLS support for Arabic character
Are you saying that file.text is empty? If so, file.txt>file.txt.converted should not be empty. Theoretically you should get the same results with these two commands: conv -f IBM-420 -t IBM-1047 file.txt >file.txt.converted conv -f IBM-420 -t IBM-1047 file.txt.converted -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Peter [dbajava...@gmail.com] Sent: Sunday, May 16, 2021 2:35 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: XMITIP - NLS support for Arabic character Hello Paul I used this command from OMVS iconv -f IBM-420 -t IBM-1047 file.txt>file.txt.converted I see the converted file is empty, Should I have file.txt populated with ARABIC codes in it ? Peter On Tue, 11 May, 2021, 8:02 pm Paul Gilmartin, < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Tue, 11 May 2021 10:21:28 +0400, Peter wrote: > > >Hi > > > >I understand CSSMTPA Doesnt support IBM-420 , but I guess ICONV services > >can be used to define a new arabic code page. > > > >I have never used ICONV services before, is there a document which helps > to > >understand the usage of ICONV ? > > > > https://www.ibm.com/docs/en/zos/2.4.0?topic=scd-iconv-convert-characters-from-one-code-set-another > https://www.ibm.com/docs/en/zos/2.4.0?topic=functions-iconv-code-conversion > > https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R3sa380680?OpenDocument > > >On Sun, 9 May, 2021, 9:11 pm Lizette Koehler wrote: > > > >> I might recommend a review of the website > >> http://secure-web.cisco.com/1_aGY3mtUxG8DIf-qoeIW_AtASqqQo5e9rCmD6jmn8767SfOD_r1Re4kOcrfbesYu1wKKWIbpo9RRWAt2cM3fitWdLH2lSEEWbiqKNelwUF21qH4LJdWdujLZqbf6DoqBFvEaxJJclm13tQsqdQp543HBfjvQF84VZaDoPkS5J8f_rMl6EhN-0deeb-S9hoxwaVIlaqdmIEgKnf8T7a_Cjr7wLQnzhO49dHEgl8VEoMVKgSNQifYfkZ3U7EKIOc4sHJ_e0SxkN7Lq1ZkCeARisjldzEqpCsnbMalcc_Vk_O2XmPdwctpVkQkmxVn0nAMHjn9G7fmhWZFL1OlAVU1je_BwudLTZZEHqnCaMy0txzO8hqimzAIzbrqc6ocDCcPd_1WSzhW7z3Tlbrlzm-SsI0-S2HYX2vDg9RGCMLIf5NyA1ZIfFdUeZMmAcbzFFP7T/http%3A%2F%2Flbdsoftware.com%2Fxmitip.html > >> . See if there is any help there > >>... > > -- gil > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMITIP - NLS support for Arabic character
On Sun, 16 May 2021 11:22:11 +0400, Peter wrote: > >I did but file.txt is empty, but the command executed successfully > >On Sun, 16 May, 2021, 11:01 am Mike Schwab wrote: > >> The Greater than symbol sends the output to the file. >> Try again without the Greater than symbol so it is the output file. >> Rather, I believe Peter understood the iconv syntax correctly. >> On Sun, May 16, 2021 at 1:36 AM Peter wrote: >> > >> > I used this command from OMVS >> > >> > iconv -f IBM-420 -t IBM-1047 file.txt>file.txt.converted >> > >> > I see the converted file is empty, Should I have file.txt populated with >> > ARABIC codes in it ? >> > Yes. Is that what you have? Translating -f IBM-420 -t IBM-1047 is futile because most of the characters in IBM-420 don't exist in IBM-1047. Describe your problem in detail. Do you have a file in IBM-420 that you want to mail? Could you even post a sample to this list? Something like: تماثيل الحدائق (selected randomly from the Web.) z/OS may make it unnecessarily difficult for you because z/OS stores Arabic text backwards. >> > On Tue, 11 May, 2021, 8:02 pm Paul Gilmartin wrote: >> >... >> > > >I have never used ICONV services before, is there a document which >> > > >helps to >> > > >understand the usage of ICONV ? >> > > >> https://www.ibm.com/docs/en/zos/2.4.0?topic=scd-iconv-convert-characters-from-one-code-set-another >> https://www.ibm.com/docs/en/zos/2.4.0?topic=functions-iconv-code-conversion >> https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R3sa380680?OpenDocument >> > > >> > > >On Sun, 9 May, 2021, 9:11 pm Lizette Koehler wrote: >> > > > >> > > >> I might recommend a review of the website >> > > >> http://lbdsoftware.com/xmitip.html . See if there is any help there -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMITIP - NLS support for Arabic character
Hello I did but file.txt is empty, but the command executed successfully On Sun, 16 May, 2021, 11:01 am Mike Schwab, wrote: > The Greater than symbol sends the output to the file. > Try again without the Greater than symbol so it is the output file. > > On Sun, May 16, 2021 at 1:36 AM Peter wrote: > > > > Hello Paul > > > > I used this command from OMVS > > > > iconv -f IBM-420 -t IBM-1047 file.txt>file.txt.converted > > > > I see the converted file is empty, Should I have file.txt populated with > > ARABIC codes in it ? > > > > Peter > > > > On Tue, 11 May, 2021, 8:02 pm Paul Gilmartin, < > > 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > > > > > On Tue, 11 May 2021 10:21:28 +0400, Peter wrote: > > > > > > >Hi > > > > > > > >I understand CSSMTPA Doesnt support IBM-420 , but I guess ICONV > services > > > >can be used to define a new arabic code page. > > > > > > > >I have never used ICONV services before, is there a document which > helps > > > to > > > >understand the usage of ICONV ? > > > > > > > > > > > https://www.ibm.com/docs/en/zos/2.4.0?topic=scd-iconv-convert-characters-from-one-code-set-another > > > > https://www.ibm.com/docs/en/zos/2.4.0?topic=functions-iconv-code-conversion > > > > > > > https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R3sa380680?OpenDocument > > > > > > >On Sun, 9 May, 2021, 9:11 pm Lizette Koehler wrote: > > > > > > > >> I might recommend a review of the website > > > >> http://lbdsoftware.com/xmitip.html . See if there is any help > there > > > >>... > > > > > > -- gil > > > > > > -- > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > -- > Mike A Schwab, Springfield IL USA > Where do Forest Rangers go to get away from it all? > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMITIP - NLS support for Arabic character
The Greater than symbol sends the output to the file. Try again without the Greater than symbol so it is the output file. On Sun, May 16, 2021 at 1:36 AM Peter wrote: > > Hello Paul > > I used this command from OMVS > > iconv -f IBM-420 -t IBM-1047 file.txt>file.txt.converted > > I see the converted file is empty, Should I have file.txt populated with > ARABIC codes in it ? > > Peter > > On Tue, 11 May, 2021, 8:02 pm Paul Gilmartin, < > 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > > > On Tue, 11 May 2021 10:21:28 +0400, Peter wrote: > > > > >Hi > > > > > >I understand CSSMTPA Doesnt support IBM-420 , but I guess ICONV services > > >can be used to define a new arabic code page. > > > > > >I have never used ICONV services before, is there a document which helps > > to > > >understand the usage of ICONV ? > > > > > > > https://www.ibm.com/docs/en/zos/2.4.0?topic=scd-iconv-convert-characters-from-one-code-set-another > > https://www.ibm.com/docs/en/zos/2.4.0?topic=functions-iconv-code-conversion > > > > https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R3sa380680?OpenDocument > > > > >On Sun, 9 May, 2021, 9:11 pm Lizette Koehler wrote: > > > > > >> I might recommend a review of the website > > >> http://lbdsoftware.com/xmitip.html . See if there is any help there > > >>... > > > > -- gil > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMITIP - NLS support for Arabic character
Hello Paul I used this command from OMVS iconv -f IBM-420 -t IBM-1047 file.txt>file.txt.converted I see the converted file is empty, Should I have file.txt populated with ARABIC codes in it ? Peter On Tue, 11 May, 2021, 8:02 pm Paul Gilmartin, < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Tue, 11 May 2021 10:21:28 +0400, Peter wrote: > > >Hi > > > >I understand CSSMTPA Doesnt support IBM-420 , but I guess ICONV services > >can be used to define a new arabic code page. > > > >I have never used ICONV services before, is there a document which helps > to > >understand the usage of ICONV ? > > > > https://www.ibm.com/docs/en/zos/2.4.0?topic=scd-iconv-convert-characters-from-one-code-set-another > https://www.ibm.com/docs/en/zos/2.4.0?topic=functions-iconv-code-conversion > > https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R3sa380680?OpenDocument > > >On Sun, 9 May, 2021, 9:11 pm Lizette Koehler wrote: > > > >> I might recommend a review of the website > >> http://lbdsoftware.com/xmitip.html . See if there is any help there > >>... > > -- gil > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMITIP - NLS support for Arabic character
On Tue, 11 May 2021 10:21:28 +0400, Peter wrote: >Hi > >I understand CSSMTPA Doesnt support IBM-420 , but I guess ICONV services >can be used to define a new arabic code page. > >I have never used ICONV services before, is there a document which helps to >understand the usage of ICONV ? > https://www.ibm.com/docs/en/zos/2.4.0?topic=scd-iconv-convert-characters-from-one-code-set-another https://www.ibm.com/docs/en/zos/2.4.0?topic=functions-iconv-code-conversion https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R3sa380680?OpenDocument >On Sun, 9 May, 2021, 9:11 pm Lizette Koehler wrote: > >> I might recommend a review of the website >> http://lbdsoftware.com/xmitip.html . See if there is any help there >>... -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMITIP - NLS support for Arabic character
Hi I understand CSSMTPA Doesnt support IBM-420 , but I guess ICONV services can be used to define a new arabic code page. I have never used ICONV services before, is there a document which helps to understand the usage of ICONV ? On Sun, 9 May, 2021, 9:11 pm Lizette Koehler, wrote: > I might recommend a review of the website > http://lbdsoftware.com/xmitip.html . See if there is any help there > > Second, you probably want to contact the owner of the product. It would > be a better place for these types of questions. > > This is not a vendor product, but something someone wrote and provided to > the universe which was very kind. > > So it front ends SMTP. That would make me ask the questions, are you > using Arabic in any of your current applications? Do you have the code > pages available for Arabic? Do you have CICS/IMS screens in Arabic? Do > you currently create reports in Arabic? All SMTP would do is send your > text data written in Arabic to another location/function I would suspect > that you might need to set up something in SMTP for Arabic. > > By using internet search with words XMITIP ARABIC > > I found this entry, there are probably more ( this link is from you in > 2019) > > https://www.mail-archive.com/ibm-main@listserv.ua.edu/msg88621.html > > > > You have not said what issue you are seeing with setting up Arabic. That > would also be helpful to know. > > Do you have the code page available for Arabic > Do you write other text/files/screens with Arabic > What happens when you try to send with XMITIP and ARABIC > Are you able to see and read the Arabic on the mainframe? > What application are you sending to that the Arabic is not valid? > > > > Lizette > > > -Original Message- > From: IBM Mainframe Discussion List On Behalf > Of Peter > Sent: Sunday, May 9, 2021 9:09 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: XMITIP - NLS support for Arabic character > > Hello, > > Cross posted > > Is there anyone who has successfully used XMITIP NLS to build arabic > character on email body ? > > Peter > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMITIP - NLS support for Arabic character
On 2021-05-09, at 10:08:45, Peter wrote: > > Cross posted > > Is there anyone who has successfully used XMITIP NLS to build arabic > character on email body ? > Hmmm... In "XMITIP User Reference Guide" I see merely: Note that all data on the mainframe is stored in the EBCDIC character set and is translated to the ASCII character set during the transmission. Any data that should not be translated should be attached in Binary format. That's pretty meager. It fails to state: o What EBCDIC code page is presumed, nor whether the user has any choice. o How characters with no ASCII equivalent are treated. (128/256) Is your Arabic data IBM-420? What if the source is Roman with Arabic insertions? I understand that mainframes tend to store Arabic text backwards. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: XMITIP - NLS support for Arabic character
I might recommend a review of the website http://lbdsoftware.com/xmitip.html . See if there is any help there Second, you probably want to contact the owner of the product. It would be a better place for these types of questions. This is not a vendor product, but something someone wrote and provided to the universe which was very kind. So it front ends SMTP. That would make me ask the questions, are you using Arabic in any of your current applications? Do you have the code pages available for Arabic? Do you have CICS/IMS screens in Arabic? Do you currently create reports in Arabic? All SMTP would do is send your text data written in Arabic to another location/function I would suspect that you might need to set up something in SMTP for Arabic. By using internet search with words XMITIP ARABIC I found this entry, there are probably more ( this link is from you in 2019) https://www.mail-archive.com/ibm-main@listserv.ua.edu/msg88621.html You have not said what issue you are seeing with setting up Arabic. That would also be helpful to know. Do you have the code page available for Arabic Do you write other text/files/screens with Arabic What happens when you try to send with XMITIP and ARABIC Are you able to see and read the Arabic on the mainframe? What application are you sending to that the Arabic is not valid? Lizette -Original Message- From: IBM Mainframe Discussion List On Behalf Of Peter Sent: Sunday, May 9, 2021 9:09 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: XMITIP - NLS support for Arabic character Hello, Cross posted Is there anyone who has successfully used XMITIP NLS to build arabic character on email body ? Peter -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
