Re: BPCS 6002===>>6101 UPGRADE -- BPCS-L

Guys,

Thanks for all of your input.

Is there one Net Change document from 6002 to 6101.  If not, do you
have one compiled for your upgrade that you can share with us.  It appears
that I will have to get net change for 6004, 61 and 6101.

Thanks,

Oludare

----- Original Message -----
From: "Gordon S. Royle" <groyle@cott.com>
To: <BPCS-L@midrange.com>
Sent: Wednesday, November 15, 2000 11:37 AM
Subject: Re: BPCS 6002===>>6101 UPGRADE


> Hi Oludare
>
> <snip>
>
> Now these:
>
> 1.    How did you go about figuring out what file layouts have change
> between 6002, and 6101.
> 2.    What do you think of my idea of installing 6002 in TEST and upgrade
to
> 6101 in TEST while I'm
>        running 6002 in PRODUCTION.
> 3.    What is the solution to the 1M records issue.
> 4.    Do I need to look at any information at 6004 and/or 61 for this
> process. If yes, what info.
> 5.    Is it true that you can install CS and MM on the same box and have
> selective installation for users.
>
> <end>
>
> I can't help with 1 through 4 because we started at 6.1.01, but I can
offer
> some insight on number 5. We currently have both CS and MM installed and
it
> is user selectable (or at least workstation selectable). In addition, we
have
> the dubious requirement to provide the user with a choice of French or
> English. Our original mandate was to provide both CS and MM services on an
> on-going basis but we are re-thinking that approach for the following
reasons.
>
> From a development standpoint, you must modify/develop at the point of the
> original source (ie ODW, AS/SET, RPG). Anything developed in ODW is ported
to
> AS/SET so you can maintain both CS and MM processes. However, something
> developed in AS/SET can not be easily ported backwards to ODW. Version
> control will also be a real issue as the ODW repository and the AS/SET
> repository are on different platforms.
>
> From a BMR standpoint, the BMR's for CS are not always the same BMR's for
MM.
> Great care must be taken when applying any BMR. CS BMR's must be
thoroughly
> tested before they are put in production. I've installed CEA BMR's on my
> local PC and had to take them out again because they a) didn't solve the
> problem b) created other problems c) miscellaneous. The best way to remove
a
> BMR is to re-install the BPCS client. This is not bad for one PC but !@#$%
if
> you have to do it on 2 or 3 hundred.
>
> I guess the moral of the story is do your testing, make a choice between
CS
> and MM, and have some fun.
>
> Gord
>
>
>
>
>
> _______________________________________________________________
>
> Cott - The Leader in Premium Retailer Brand Beverage Innovation.
> _______________________________________________________________
> +---
> | This is the BPCS Users Mailing List!
> | To submit a new message, send your mail to BPCS-L@midrange.com.
> | To subscribe to this list send email to BPCS-L-SUB@midrange.com.
> | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner: dasmussen@aol.com
> +---

+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---