FTP ASCII file from Windows to Mainframe (iSeries) — special characters
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I have a text file created on a Windows machine, the page coding used on the file is 1252
This file is then ftp'd to an iSeries machine for processing
As far as I can see, it appears on the iSeries. It has a CCSID of 037.
Sometimes this file contains French characters (e.g. é). When this happens, the FTP will fail with a truncation error as the french character gets converted to some extra junk: �.
The file is fixed block so the line does get truncated due to the one character turning into 3.
I can convert the French characters to characters without the accents before sending but would prefer to keep everything intact. So is there a way to retain them and send the file over properly?
I'm very green on iSeries, mainly a Windows guy.
windows ftp mainframe
migrated from stackoverflow.com Oct 6 '12 at 14:24
This question came from our site for professional and enthusiast programmers.
add a comment |
I have a text file created on a Windows machine, the page coding used on the file is 1252
This file is then ftp'd to an iSeries machine for processing
As far as I can see, it appears on the iSeries. It has a CCSID of 037.
Sometimes this file contains French characters (e.g. é). When this happens, the FTP will fail with a truncation error as the french character gets converted to some extra junk: �.
The file is fixed block so the line does get truncated due to the one character turning into 3.
I can convert the French characters to characters without the accents before sending but would prefer to keep everything intact. So is there a way to retain them and send the file over properly?
I'm very green on iSeries, mainly a Windows guy.
windows ftp mainframe
migrated from stackoverflow.com Oct 6 '12 at 14:24
This question came from our site for professional and enthusiast programmers.
Try setting your CCSID to 500 (See: iSeries CCSID)
– NealB
Oct 4 '12 at 15:45
Thanks, I changed the CCSID to 500 and same result Oddly I just found that our production env already was 500 but in test it was 37 for some reason, both are now 500 and no luck
– MikeM
Oct 4 '12 at 16:05
1
How about converting the file to UTF-8, and send it as binary?
– neu242
Oct 8 '12 at 6:30
add a comment |
I have a text file created on a Windows machine, the page coding used on the file is 1252
This file is then ftp'd to an iSeries machine for processing
As far as I can see, it appears on the iSeries. It has a CCSID of 037.
Sometimes this file contains French characters (e.g. é). When this happens, the FTP will fail with a truncation error as the french character gets converted to some extra junk: �.
The file is fixed block so the line does get truncated due to the one character turning into 3.
I can convert the French characters to characters without the accents before sending but would prefer to keep everything intact. So is there a way to retain them and send the file over properly?
I'm very green on iSeries, mainly a Windows guy.
windows ftp mainframe
I have a text file created on a Windows machine, the page coding used on the file is 1252
This file is then ftp'd to an iSeries machine for processing
As far as I can see, it appears on the iSeries. It has a CCSID of 037.
Sometimes this file contains French characters (e.g. é). When this happens, the FTP will fail with a truncation error as the french character gets converted to some extra junk: �.
The file is fixed block so the line does get truncated due to the one character turning into 3.
I can convert the French characters to characters without the accents before sending but would prefer to keep everything intact. So is there a way to retain them and send the file over properly?
I'm very green on iSeries, mainly a Windows guy.
windows ftp mainframe
windows ftp mainframe
asked Oct 4 '12 at 14:28
MikeM
migrated from stackoverflow.com Oct 6 '12 at 14:24
This question came from our site for professional and enthusiast programmers.
migrated from stackoverflow.com Oct 6 '12 at 14:24
This question came from our site for professional and enthusiast programmers.
Try setting your CCSID to 500 (See: iSeries CCSID)
– NealB
Oct 4 '12 at 15:45
Thanks, I changed the CCSID to 500 and same result Oddly I just found that our production env already was 500 but in test it was 37 for some reason, both are now 500 and no luck
– MikeM
Oct 4 '12 at 16:05
1
How about converting the file to UTF-8, and send it as binary?
– neu242
Oct 8 '12 at 6:30
add a comment |
Try setting your CCSID to 500 (See: iSeries CCSID)
– NealB
Oct 4 '12 at 15:45
Thanks, I changed the CCSID to 500 and same result Oddly I just found that our production env already was 500 but in test it was 37 for some reason, both are now 500 and no luck
– MikeM
Oct 4 '12 at 16:05
1
How about converting the file to UTF-8, and send it as binary?
– neu242
Oct 8 '12 at 6:30
Try setting your CCSID to 500 (See: iSeries CCSID)
– NealB
Oct 4 '12 at 15:45
Try setting your CCSID to 500 (See: iSeries CCSID)
– NealB
Oct 4 '12 at 15:45
Thanks, I changed the CCSID to 500 and same result Oddly I just found that our production env already was 500 but in test it was 37 for some reason, both are now 500 and no luck
– MikeM
Oct 4 '12 at 16:05
Thanks, I changed the CCSID to 500 and same result Oddly I just found that our production env already was 500 but in test it was 37 for some reason, both are now 500 and no luck
– MikeM
Oct 4 '12 at 16:05
1
1
How about converting the file to UTF-8, and send it as binary?
– neu242
Oct 8 '12 at 6:30
How about converting the file to UTF-8, and send it as binary?
– neu242
Oct 8 '12 at 6:30
add a comment |
1 Answer
1
active
oldest
votes
What you are dealing with is that Windows-1252 usually claims to be ISO-8859-1 Latin-1, but it really isn't. There is a small section - like sixteen code points or so - that Microsoft has decided to use for characters like typographic quotation marks (aka. "smart quotes") instead.
My best guess is that your transfer software (either by configuration or developer's decision) assumes that Win-1252 is equal to ISO-8859-1. Fix that (if possible) and you fix the problem.
edited Oct 8 '12 at 6:22
Indrek
20.7k117484
answered Oct 8 '12 at 5:56
JoeZitzelbergerJoeZitzelberger
111
BTW, the accented E is in the problem code plane...sorry I didn't mention that in the original answer.
– JoeZitzelberger
Oct 8 '12 at 5:58
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f484260%2fftp-ascii-file-from-windows-to-mainframe-iseries-special-characters%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
What you are dealing with is that Windows-1252 usually claims to be ISO-8859-1 Latin-1, but it really isn't. There is a small section - like sixteen code points or so - that Microsoft has decided to use for characters like typographic quotation marks (aka. "smart quotes") instead.
My best guess is that your transfer software (either by configuration or developer's decision) assumes that Win-1252 is equal to ISO-8859-1. Fix that (if possible) and you fix the problem.
edited Oct 8 '12 at 6:22
Indrek
20.7k117484
answered Oct 8 '12 at 5:56
JoeZitzelbergerJoeZitzelberger
111
BTW, the accented E is in the problem code plane...sorry I didn't mention that in the original answer.
– JoeZitzelberger
Oct 8 '12 at 5:58
add a comment |
What you are dealing with is that Windows-1252 usually claims to be ISO-8859-1 Latin-1, but it really isn't. There is a small section - like sixteen code points or so - that Microsoft has decided to use for characters like typographic quotation marks (aka. "smart quotes") instead.
My best guess is that your transfer software (either by configuration or developer's decision) assumes that Win-1252 is equal to ISO-8859-1. Fix that (if possible) and you fix the problem.
edited Oct 8 '12 at 6:22
Indrek
20.7k117484
answered Oct 8 '12 at 5:56
JoeZitzelbergerJoeZitzelberger
111
BTW, the accented E is in the problem code plane...sorry I didn't mention that in the original answer.
– JoeZitzelberger
Oct 8 '12 at 5:58
add a comment |
What you are dealing with is that Windows-1252 usually claims to be ISO-8859-1 Latin-1, but it really isn't. There is a small section - like sixteen code points or so - that Microsoft has decided to use for characters like typographic quotation marks (aka. "smart quotes") instead.
My best guess is that your transfer software (either by configuration or developer's decision) assumes that Win-1252 is equal to ISO-8859-1. Fix that (if possible) and you fix the problem.
edited Oct 8 '12 at 6:22
Indrek
20.7k117484
answered Oct 8 '12 at 5:56
JoeZitzelbergerJoeZitzelberger
111
What you are dealing with is that Windows-1252 usually claims to be ISO-8859-1 Latin-1, but it really isn't. There is a small section - like sixteen code points or so - that Microsoft has decided to use for characters like typographic quotation marks (aka. "smart quotes") instead.
My best guess is that your transfer software (either by configuration or developer's decision) assumes that Win-1252 is equal to ISO-8859-1. Fix that (if possible) and you fix the problem.
edited Oct 8 '12 at 6:22
Indrek
20.7k117484
answered Oct 8 '12 at 5:56
JoeZitzelbergerJoeZitzelberger
111
edited Oct 8 '12 at 6:22
Indrek
20.7k117484
edited Oct 8 '12 at 6:22
Indrek
20.7k117484
edited Oct 8 '12 at 6:22
Indrek
20.7k117484
20.7k117484
answered Oct 8 '12 at 5:56
JoeZitzelbergerJoeZitzelberger
111
answered Oct 8 '12 at 5:56
JoeZitzelbergerJoeZitzelberger
111
answered Oct 8 '12 at 5:56
JoeZitzelbergerJoeZitzelberger
111
111
BTW, the accented E is in the problem code plane...sorry I didn't mention that in the original answer.
– JoeZitzelberger
Oct 8 '12 at 5:58
add a comment |
BTW, the accented E is in the problem code plane...sorry I didn't mention that in the original answer.
– JoeZitzelberger
Oct 8 '12 at 5:58
BTW, the accented E is in the problem code plane...sorry I didn't mention that in the original answer.
– JoeZitzelberger
Oct 8 '12 at 5:58
BTW, the accented E is in the problem code plane...sorry I didn't mention that in the original answer.
– JoeZitzelberger
Oct 8 '12 at 5:58
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f484260%2fftp-ascii-file-from-windows-to-mainframe-iseries-special-characters%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Try setting your CCSID to 500 (See: iSeries CCSID)
– NealB
Oct 4 '12 at 15:45
Thanks, I changed the CCSID to 500 and same result Oddly I just found that our production env already was 500 but in test it was 37 for some reason, both are now 500 and no luck
– MikeM
Oct 4 '12 at 16:05
1
How about converting the file to UTF-8, and send it as binary?
– neu242
Oct 8 '12 at 6:30