I am not positive of the affect of running the double byte version in the same partition, but I do know that when running "regular" BPCS/LX on the same partition there are not any problems. The only caveat is that names of the libraries MUST be unique, i.e. there must be only one (1) BPCSO on the partition. At one time I had 4 versions running on the same partition.

Hope that this helps.

Can anyone else answer the question about double byte on the same partition?

Dan Sweeney - Sr Technical Consultant
PHOENIX Business Consulting, Inc.
Cell: 860.490.6712

-----Original Message-----
From: bpcs-l-bounces+dsweeney=phoenixbcinc.com@xxxxxxxxxxxx [mailto:bpcs-l-bounces+dsweeney=phoenixbcinc.com@xxxxxxxxxxxx] On Behalf Of Moy, Bill
Sent: Tuesday, February 17, 2009 10:08 AM
To: bpcs-l@xxxxxxxxxxxx
Subject: [BPCS-L] Running LX alongside 6.1


Does anyone know if there are any issues or concerns with
running both LX and 6.102 on the same box in the same partition? We are
not currently running double byte to support Chinese, but are looking to
use it for LX. Does this cause any additional problems. We are thinking
about implementing LX to support our China facility, while keeping the
NA facility's on 6.1.


Bill Moy
Invensys Controls

630 260-3303

Invensys is an ENERGY STAR partner

Visit: http://www.Invensys.com <http://www.invensys.com/>


This email and any attachments are confidential and may also be
privileged. If you are not the named recipient, or have otherwise
received this communication in error, please delete it from your inbox,
notify the sender immediately, and do not disclose the contents to any
other person or use them for any purpose, or store them in any medium.
Thank you for your cooperation.

This thread ...


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

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