Genyphyr,

The document is 'National Language Versions Installation Guide V8.3.3'
(not the document I refer to below written by yourself).

The section I need clarification with is as follows: -

"User setup to access ERP LX depends on whether you use the MLS
enhancement.

If you do not use the MLS enhancement, ensure that for all languages,
the Host Code Page setting on the user's 5250 emulator session matches
the CCSID of the Infor ERP LX database tables and the SYS820D System
CCSID is set to *AUTO. These settings must match the CCSID settings of
the NLV translations.

If you use the MLS enhancement, set the user's CCSID to match the NLV
message file CCSID that is assigned to the user. However, the user can
only enter data in their unique language CCSID into the MLS extension
files. Users should use the base language for the installation to write
data into other ERP LX files. Users should use the Invariant Character
set to
ensure the characters they write into the database can be stored
properly and will be able to be read by other users on the system."

We will be using the MLS product. Does the above indicate that the users
host-code page should match the CCSID setting in SYS600 when writing to
the MLS files, and that the host-code page should be set to the database
CCSID when writing to the rest of the database ?

Thanks and regards,
Sean



-----Original Message-----
From: bpcs-l-bounces+sean.mcgovern=covidien.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+sean.mcgovern=covidien.com@xxxxxxxxxxxx] On
Behalf Of McGovern, Sean
Sent: 15 May 2009 21:53
To: BPCS ERP System; bpcs-l@xxxxxxxxxxxx
Subject: Re: [BPCS-L] ERP LX MLS set up for users ... was BPCS-L
Digest,Vol 7, Issue 60

Genyphyr,

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).

Cheers,
Sean

________________________________

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




message: 1
date: Thu, 14 May 2009 09:41:06 +0100
from: "McGovern, Sean" <Sean.McGovern@xxxxxxxxxxxx>
subject: Re: [BPCS-L] BPCS-L Digest, Vol 7, Issue 58

Thanks for the info Debasish,

Sounds like I may have a reason to learn Java, not sure if that is a
good thing. I'm glad AS/SET is going, but not so glad that the AS/SET
generated source is still in use ! But why are you debugging - surely
there are no bugs anymore ?? ;-)

The setup at GSK seems appropriate, QCCSID should be set to whatever is
relevant for the LPAR. What do GSK use for the Western European LPAR,
937 ?

Reading through the Infor NLV documentation again, I see that if the MLS
product is being used, the job CCSID will be changed at the startup of
ERP LX (to match SYS600 settings), thus making the QCCSID irrelevant for
the BPCS users. 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. Not sure
how that is going to be managed ! I guess I just need to get ERP LX
installed and start testing...

Cheers,
Sean
--
This is the BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.

Delivered-To: sean.mcgovern@xxxxxxxxxxxx



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.