<!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman";} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-size:10.0pt; mso-ansi-font-size:10.0pt; mso-bidi-font-size:10.0pt;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --> <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman";} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-size:10.0pt; mso-ansi-font-size:10.0pt; mso-bidi-font-size:10.0pt;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --> Hi, We are trying to FTP Special characters like ]¬|![¢^ from Mainframe to Windows server which runs on Windows platform. The FTP is working fine but the characters are getting displayed differently there as: Ù^|!  ›µ when we would like to see as originally sent ]¬|![¢^ This holds the same vice versa. The FTP in this case is handled by Microsoft FTP Service which we can see from the below logs. This is similar to the FTP Process we do from Command prompt where we can FTP to/from Mainframe from our Normal desktop session. The characters in Mainframes are stored in EBCDIC Format and in Windows the same accepts only ASCII Format. We use EBCDIC Codepage of 1140 to store our data in Mainframes. We need to see the special characters display correctly as it was sent. Please find the logs when we tried to FTP from Mainframe to the Windows Server using the Mainframe Batch JCL: The below command were given: SITE SBD=(IBM-1140,ISO8859-1) PUT 'DDPCN.ODS.IBASE1.TEST1' IBASEEXT_TEST.TXT QUIT We see that it is not able to accept commands like: TYPE E ( Which will set the Transfer type to EBCDIC) which when given says: TYPE E not implemented and also not able to accept the SITE Command which we give in Mainframe: EZA1736I SITE SBD=(IBM-1140,ISO8859-1) EZA1701I >>> SITE SBD=(IBM-1140,ISO8859-1) 500 'SITE SBD=(IBM-1140,ISO8859-1)': command not understood Could you please check and let us know how we would be able to transfer the special characters from Mainframe to Windows and vice versa and have it displayed as exactly the same. We are doing the DB2 Upgrade on our Mainframe DB2 systems and we would need to have this fixed before we can proceed with the same. Any help on this would be appreciated <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman";} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline; text-underline:single;} a:visited, span.MsoHyperlinkFollowed {mso-style-noshow:yes; mso-style-priority:99; color:purple; mso-themecolor:followedhyperlink; text-decoration:underline; text-underline:single;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-size:10.0pt; mso-ansi-font-size:10.0pt; mso-bidi-font-size:10.0pt;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} -->

Adding further info for this: <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman";} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline; text-underline:single;} a:visited, span.MsoHyperlinkFollowed {mso-style-noshow:yes; mso-style-priority:99; color:purple; mso-themecolor:followedhyperlink; text-decoration:underline; text-underline:single;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-size:10.0pt; mso-ansi-font-size:10.0pt; mso-bidi-font-size:10.0pt;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --> Adding some info from IBM Links which says that the errors we are getting are from MS FTP Server not recognizing the SITE Command, which we need to confirm the Microsoft FTP Server will accept. It may have a different format than how the Mainframe FTP Server requires. We would need to review the Microsoft FTP Server docs for details on how to configure and code the SITE Command. The link below may help on how to configure the global settings for FTP Server and also for FTP Clients. http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/31c2427c-c0a5-49fa-9e03-823f34fba3e8.mspx?mfr=true Please check and let us know how this Global settings needs to be set on a Windows Server or our Normal Desktop session in our PC

<!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman";} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-size:10.0pt; mso-ansi-font-size:10.0pt; mso-bidi-font-size:10.0pt;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --> The Corresponding FTP logs captured were: EZA1736I FTP EZY2640I Using 'TCPPARMS(FTPDATA)' for local site configuration parameters. EZA1450I IBM FTP CS V1R9 220 Microsoft FTP Service EZA1460I Command: EZA1736I SITE SBD=(IBM-1140,ISO8859-1) EZA1701I >>> SITE SBD=(IBM-1140,ISO8859-1) 500 'SITE SBD=(IBM-1140,ISO8859-1)': command not understood EZA1460I Command: EZA1736I PUT 'DDPCN.ODS.IBASE1.TEST1' IBASEEXT_TEST.TXT EZA1701I >>> SITE VARrecfm LRECL=628 RECFM=VB BLKSIZE=27998 500 'SITE VARrecfm LRECL=628 RECFM=VB BLKSIZE=27998': command not understood EZA1701I >>> PASV 227 Entering Passive Mode (161,228,63,69,16,84). EZA1701I >>> STOR IBASEEXT_TEST.TXT 125 Data connection already open; Transfer starting. EZA1485I 9018156 bytes transferred - 10 second interval rate 890.24 KB/sec - Ove 226 Transfer complete. EZA1617I 12637062 bytes transferred in 13.840 seconds. Transfer rate 913.08 Kby EZA1460I Command: EZA1736I QUIT EZA1701I >>> QUIT 221

Hi, As this issue is related to IIS, I suggest discussing it in our IIS forum. They are the best resource to troubleshoot this issue. http://forums.iis.net/ BrentPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

The issue has been resolved. When we do FTP from Mainframe to Windows and vice versa using the Windows Command Prompt in our PC or in a Windows Batch job, we would need to enter the QUOTE SITE command as below after typing the userid and Password. quote site sbd=(IBM-1140,ISO8859-1) after which we can enter our PUT Commands. The Transfer type will remain the default which is ASCII mode. The Special characters will display correctly as it was sent. When we use the Mainframe Batch JCL or session to transfer files to windows, we would need to enter the LOCSITE Command as below after typing the userid and password. locsite sbdataconn=(IBM-1140,ISO8859-1) after which we can enter our PUT Commands after which the Special characters will display correctly.

Thanks a lot for sharing.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.