HiI need to do the following for Japanese users, All client access are setup
with host code page 939, and there job is setup to 65535,
I need to change there job to CCSID 37 to send emails using MMAIL and then
change it back to 65535 as it was before,

But when i do chgjob ccsid(37) send emails and then again chgjob
ccsid(65535) i start getting this error?

Is there a work around, if you see documentation of MMAIL it says MMAIL wont
work with CCSID 65535 so all these changes.

Any suggestions?

Ashish

On Tue, Aug 25, 2009 at 10:47 AM, David Gibbs <david@xxxxxxxxxxxx> wrote:

Ashish Kulkarni wrote:
For the Japanese users, when they change CCSID to 37 and back to 65535
they
run into this error,

The error says "Device is not a DBCS device" is this some thing related
to
V5R3 and fixed in next version or some thing related to client access?

Japanese text needs a specific device configuration in order to display in
a CA/400 device properly.

For CCSID 5035, we use host code page 939 Japanese Latin Extended
For CCSID 5026, we use host code page 930 Japanese Katakana Extended.

Host code page is accessed by using the Communication menu and selecting
the Configure option.

Changing the CCSID on the fly, especially when using an english session,
will *NOT* work.

david

--
IBM i on Power - For when you can't afford to be out of business
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].