Hi Sean,

It seems to me that you are answering in references to the QCCSID setting, but my question about your statement regarding the host code page and the BPCS MLS setting for a user ... I was referring to your statement about needing to change host code page settings for the user depending on what files they were typing into and your statement that that would be difficult to manage, but then your reply below talks about logging a call with Infor asking about QCCSID and being given a document from 2005 - and of course this does not necessarily relate to the new enhancement in MLS set up in BPCS users, so I am getting a bit confused.

Be aware that any 2005 document you are referencing would not talk
about the new ERP LX MLS support, as MLS support using Unicode
extension files in LX was released in 2008 and I came up with that design concept,
so I know in 2005 this did not exist yet. I am not sure exactly which document of mine that you are referencing since I wrote quite a few. If you can give me the title and the paragraph that is causing your concern about needing to switch host code pages back and forth that would help.


Genyphyr Novak
iSeries technical consultant
+33 662 15 02 02

message: 1
date: Fri, 15 May 2009 21:52:44 +0100
from: "McGovern, Sean" <Sean.McGovern@xxxxxxxxxxxx>
subject: Re: [BPCS-L] ERP LX MLS set up for users ... was BPCS-L
Digest, Vol 7, Issue 60


When I logged the QCCSID question with Infor, I was supplied with a document (written by yourself in 2005, I think), which is how my statement came about. I'll dig out the document on Monday and take another look.

I'm certainly aware of the invariant character issue. One area where this cropped up, we have the need to maintain shipping document texts in the language of the country that the shipping documents are being sent. Tthese texts are entered into the system by the same users at the same PCs. Not a good situation. The solution was to store the texts in Unicode tables, and use iSeries Access for Web rather than iSeries Access for Windows (which doesn't support Unicode).



From: bpcs-l-bounces+sean.mcgovern=covidien.com@xxxxxxxxxxxx on behalf of Genyphyr Novak
Sent: Fri 15/05/2009 19:19
To: bpcs-l@xxxxxxxxxxxx
Subject: Re: [BPCS-L] ERP LX MLS set up for users ... was BPCS-L Digest,Vol 7, Issue 60

Hi Sean,

You made the statement " But it seems that the host-code page should be set differently depending on whether the user is performing database events against the MLS files or against the rest of the BPCS files.". Where do you find that in the documentation or what leads you to that conclusion - I am not sure it's accurate ?

Normally the user should be set up in BPCS with the MLS language setting on their user profile (in BPCS and ideally that same setting should be used on the iSeries user profile if it makes sense in your installation) that will reflect their desired input to the MLS enabled extension files. If they do not have any particular issues with the characters available in code page 937, that is the default setting for the database and should be used for the user.

Note that when working with the rest of the BPCS files, the input of characters not part of the Invariant code page, and not part of the database CCSID (default 937) will cause issues in data storage and retrieval between users with different CCSID settings. I believe this is also part of the documentation but am not certain everyone fully understands the implication of this when doing end-user education. This is something you should also test in your set up if you deal with languages such as Swedish, Norwegian, Polish, Czech etc. which user CCSIDs that contain characters which are not part of the 937 CCSID.

Take care,

Genyphyr Novak
iSeries technical consultant
Chamonix France
+33 662 15 02 02

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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

This mailing list archive is Copyright 1997-2021 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.