Re: FTP conversion Extended ASCII to EBCDIC
On Thu, 5 Mar 2015 17:51:28 -0600, Bill Godfrey bgodfrey...@gmail.com wrote: On Thu, 5 Mar 2015 17:21:01 -0600, Bill Godfrey wrote: On Thu, 5 Mar 2015 18:15:07 +, David Booher wrote: I have noticed when you are transferring a windows file containing a not character (x'AC') using ASCII transfer to the mainframe, it gets converted to backslash ( \ x'B7') when stored. Is there any way to get the extended Windows ASCII characters to transfer correctly? I suspect that the default SBDATACONN at your site is (1047,IBM-850), which would translate x'AC' (which is the 1/4 character in codepage 850) to x'B7' (which is the 1/4 character in code page 1047). If you use quote site sbdataconn=(IBM-1047,ISO8859-1) (if your transfer is started from the windows end) then x'AC' will be translated to x'E0' which is the not character in codepage 1047. Correction: to x'B0' which is the not character in codepage 1047. I don't know which codepage you have that tells you x'B7' is a backslash. I assumed you were using FTP, but now I see you never mentioned FTP. If your file transfer is being done by your 3270 terminal program using IND$FILE, then I don't know of any options for that method that would make it use a different translate table than the built-in one that translates x'AC' to x'B7'. Bill -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP conversion Extended ASCII to EBCDIC
Yes, I need to pay more attention to the hex it is being translated to -vs- the characters I'm seeing because the emulator does play a role here as well. Thanks. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Charles Mills Sent: Thursday, March 05, 2015 6:48 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: FTP conversion Extended ASCII to EBCDIC There are two layers here. You can't say it gets converted to a backslash. More correctly it hets translated to a code point that your emulator displays as a backslash. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP conversion Extended ASCII to EBCDIC
In blu437-smtp45b638807eb09d048f7494da...@phx.gbl, on 03/05/2015 at 12:53 PM, Tony's Outlook via Mozilla tbabo...@outlook.com said: Apart from some occasional flames, IBM-MAIN is nothing but a large FAQ. Too large to be a FAQ, and too many obscure questions[1]. What am I missing here? The size, for one. A FAQ is is small document, limited to frequent questions. It is not a compilation of every question ever asked, including those that are relevant[1] only for a short window. [1] Questions that are only relevant for a brief window or that are obscure may be extremely important at the time they are posted, but they don't belong in a FAQ list. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP conversion Extended ASCII to EBCDIC
In 08ef7d7816b3b642a380513303a2d77b45b03...@alvmbxw01.prod.quest.corp, on 03/05/2015 at 06:15 PM, David Booher david.boo...@software.dell.com said: I have noticed when you are transferring a windows file What code page are you using on windoze containing a not character ( ¬ x'AC') using ASCII transfer to the mainframe, it gets converted to backslash ( \ x'B7') when stored. Does it als translate '5C' (\) to 'B7' (\)? Is there any way to get the extended Windows ASCII characters to transfer correctly? What translate table did you specify? Exactly what FTP commands did you use? -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP conversion Extended ASCII to EBCDIC
Thank you for providing a very tactful and useful answer. Dave -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Giovanni Bozzetti Sent: Thursday, March 05, 2015 12:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: FTP conversion Extended ASCII to EBCDIC You can look some table sample in TCPIP.SEZATCPX has many source tables and you can add one for you You can use CONVXLAT to create an image to load and normally you can save it as TCPIP.STANDARD.TCPXLBIN or TCPIP.yourname.TCPXLBIN Here the JCL, You have some FTP command that load or you can put in TCPIP.FTP.DATA //ST1 EXEC PGM=CONVXLAT, // PARM='''TCPIP.SEZATCPX(US)'' ''TCPIP.US.TCPXLBIN''' //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY,BLKSIZE=80 // Giovanni System programmer -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP conversion Extended ASCII to EBCDIC
On Thu, 5 Mar 2015 10:34:55 -0800, Bill Johnson wrote: 1208 might be the best bet. That's UTF-8, which might well be the best bet (would be for Linux). Also look at the SBDATACONN and MBDATACONN commands. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP conversion Extended ASCII to EBCDIC
On Thu, 5 Mar 2015 18:15:07 +, David Booher wrote: I have noticed when you are transferring a windows file containing a not character (x'AC') using ASCII transfer to the mainframe, it gets converted to backslash ( \ x'B7') when stored. Is there any way to get the extended Windows ASCII characters to transfer correctly? I suspect that the default SBDATACONN at your site is (1047,IBM-850), which would translate x'AC' (which is the 1/4 character in codepage 850) to x'B7' (which is the 1/4 character in code page 1047). If you use quote site sbdataconn=(IBM-1047,ISO8859-1) (if your transfer is started from the windows end) then x'AC' will be translated to x'E0' which is the not character in codepage 1047. I don't know which codepage you have that tells you x'B7' is a backslash. Bill -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP conversion Extended ASCII to EBCDIC
On Thu, 5 Mar 2015 17:21:01 -0600, Bill Godfrey wrote: On Thu, 5 Mar 2015 18:15:07 +, David Booher wrote: I have noticed when you are transferring a windows file containing a not character (x'AC') using ASCII transfer to the mainframe, it gets converted to backslash ( \ x'B7') when stored. Is there any way to get the extended Windows ASCII characters to transfer correctly? I suspect that the default SBDATACONN at your site is (1047,IBM-850), which would translate x'AC' (which is the 1/4 character in codepage 850) to x'B7' (which is the 1/4 character in code page 1047). If you use quote site sbdataconn=(IBM-1047,ISO8859-1) (if your transfer is started from the windows end) then x'AC' will be translated to x'E0' which is the not character in codepage 1047. Correction: to x'B0' which is the not character in codepage 1047. I don't know which codepage you have that tells you x'B7' is a backslash. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP conversion Extended ASCII to EBCDIC
There are two layers here. You can't say it gets converted to a backslash. More correctly it hets translated to a code point that your emulator displays as a backslash. CharlesSent from a mobile; please excuse the brevity Original message From: Bill Godfrey bgodfrey...@gmail.com Date: 03/05/2015 3:21 PM (GMT-08:00) To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: FTP conversion Extended ASCII to EBCDIC On Thu, 5 Mar 2015 18:15:07 +, David Booher wrote: I have noticed when you are transferring a windows file containing a not character (x'AC') using ASCII transfer to the mainframe, it gets converted to backslash ( \ x'B7') when stored. Is there any way to get the extended Windows ASCII characters to transfer correctly? I suspect that the default SBDATACONN at your site is (1047,IBM-850), which would translate x'AC' (which is the 1/4 character in codepage 850) to x'B7' (which is the 1/4 character in code page 1047). If you use quote site sbdataconn=(IBM-1047,ISO8859-1) (if your transfer is started from the windows end) then x'AC' will be translated to x'E0' which is the not character in codepage 1047. I don't know which codepage you have that tells you x'B7' is a backslash. Bill -- 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: FTP conversion Extended ASCII to EBCDIC
1208 might be the best bet. On Thu, 3/5/15, David Booher david.boo...@software.dell.com wrote: Subject: FTP conversion Extended ASCII to EBCDIC To: IBM-MAIN@LISTSERV.UA.EDU Date: Thursday, March 5, 2015, 1:15 PM I have noticed when you are transferring a windows file containing a not character ( ¬ x'AC') using ASCII transfer to the mainframe, it gets converted to backslash ( \ x'B7') when stored. Is there any way to get the extended Windows ASCII characters to transfer correctly? David Booher Mainframe Systems Programmer Dell | Database Management, Quest Software office +1 630-836-3196, fax +1 630-836-4099 Quest Software is now a part of Dell -- 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: FTP conversion Extended ASCII to EBCDIC
We need an IBM-MAIN FAQ. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Bill Johnson Sent: Thursday, March 05, 2015 10:35 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: FTP conversion Extended ASCII to EBCDIC 1208 might be the best bet. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
FTP conversion Extended ASCII to EBCDIC
I have noticed when you are transferring a windows file containing a not character ( ¬ x'AC') using ASCII transfer to the mainframe, it gets converted to backslash ( \ x'B7') when stored. Is there any way to get the extended Windows ASCII characters to transfer correctly? David Booher Mainframe Systems Programmer Dell | Database Management, Quest Software office +1 630-836-3196, fax +1 630-836-4099 Quest Software is now a part of Dell -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP conversion Extended ASCII to EBCDIC
Sounds like a translation table problem. There are many built in translation tables, and if none of those doesn't work, you can create your own. Look for the CONVXLAT command. Gadi From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of David Booher [david.boo...@software.dell.com] Sent: 05 March 2015 20:15 To: IBM-MAIN@LISTSERV.UA.EDU Subject: FTP conversion Extended ASCII to EBCDIC I have noticed when you are transferring a windows file containing a not character ( ¬ x'AC') using ASCII transfer to the mainframe, it gets converted to backslash ( \ x'B7') when stored. Is there any way to get the extended Windows ASCII characters to transfer correctly? David Booher Mainframe Systems Programmer Dell | Database Management, Quest Software office +1 630-836-3196, fax +1 630-836-4099 Quest Software is now a part of Dell -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN לשימת לבך, בהתאם לנהלי חברת מלם מערכות בעמ ו/או כל חברת בת ו/או חברה קשורה שלה (להלן : החברה) וזכויות החתימה בהן, כל הצעה, התחייבות או מצג מטעם החברה, מחייבים מסמך נפרד וחתום על ידי מורשי החתימה של החברה, הנושא את לוגו החברה או שמה המודפס ובצירוף חותמת החברה. בהעדר מסמך כאמור (לרבות מסמך סרוק) המצורף להודעת דואר אלקטרוני זאת, אין לראות באמור בהודעה אלא משום טיוטה לדיון, ואין להסתמך עליה לביצוע פעולה עסקית או משפטית כלשהי. Please note that in accordance with Malam and/or its subsidiaries (hereinafter : Malam) regulations and signatory rights, no offer, agreement, concession or representation is binding on the Malam, unless accompanied by a duly signed separate document (or a scanned version thereof), affixed with the Malam seal. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FTP conversion Extended ASCII to EBCDIC
You need to use the proper CCSID. On Thu, 3/5/15, David Booher david.boo...@software.dell.com wrote: Subject: FTP conversion Extended ASCII to EBCDIC To: IBM-MAIN@LISTSERV.UA.EDU Date: Thursday, March 5, 2015, 1:15 PM I have noticed when you are transferring a windows file containing a not character ( ¬ x'AC') using ASCII transfer to the mainframe, it gets converted to backslash ( \ x'B7') when stored. Is there any way to get the extended Windows ASCII characters to transfer correctly? David Booher Mainframe Systems Programmer Dell | Database Management, Quest Software office +1 630-836-3196, fax +1 630-836-4099 Quest Software is now a part of Dell -- 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: FTP conversion Extended ASCII to EBCDIC
Apart from some occasional flames, IBM-MAIN is nothing but a large FAQ. What am I missing here? On 3/5/2015 12:47 PM, Charles Mills wrote: We need an IBM-MAIN FAQ. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Bill Johnson Sent: Thursday, March 05, 2015 10:35 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: FTP conversion Extended ASCII to EBCDIC 1208 might be the best bet. -- 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: FTP conversion Extended ASCII to EBCDIC
You can look some table sample in TCPIP.SEZATCPX has many source tables and you can add one for you You can use CONVXLAT to create an image to load and normally you can save it as TCPIP.STANDARD.TCPXLBIN or TCPIP.yourname.TCPXLBIN Here the JCL, You have some FTP command that load or you can put in TCPIP.FTP.DATA //ST1 EXEC PGM=CONVXLAT, // PARM='''TCPIP.SEZATCPX(US)'' ''TCPIP.US.TCPXLBIN''' //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY,BLKSIZE=80 // Giovanni System programmer -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of David Booher Sent: Thursday, March 05, 2015 03:15 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: FTP conversion Extended ASCII to EBCDIC I have noticed when you are transferring a windows file containing a not character ( ¬ x'AC') using ASCII transfer to the mainframe, it gets converted to backslash ( \ x'B7') when stored. Is there any way to get the extended Windows ASCII characters to transfer correctly? David Booher Mainframe Systems Programmer Dell | Database Management, Quest Software office +1 630-836-3196, fax +1 630-836-4099 Quest Software is now a part of Dell -- 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
