Re: Upgrade to 3.5.2b SP2 -- SYSTEM21

Good Morning,
 I just completed a uplift to the base product in a test environment from
3.5.1 to 3.5.2b sp-3. just a couple of this to check depending on your
configuraton. If you are using job management and do not have Fixed assets
you get an erorr on some JC PTF's. One of the Job mgt, install programs was
looking for file FAP20 I think. The other thing would be to check your
library list in your test environment after the uplift is complete. They are
sometimes reset to the live environment library list. I also found it to be
a good idea archive data and reorganize file libraries prior to the uplift.
We also used the Support desk and they were helpful. Their response time was
great. I hope this helps.
see ya:
----- Original Message -----
From: Eric Daniel <edaniel@ameritech.net>
To: <JBAUSERS-L@midrange.com>
Sent: Friday, July 28, 2000 10:45 AM
Subject: Re: Upgrade to 3.5.2b SP2


> Hello Theresa,
>
> The GEAC support desk is correct.  Upgrades can be installed to a single
> application environment.  However the JBA system manager (application
> manager, common functions, machine manager, etc.) controls all application
> environments and this will need to be PTFed to the version that you will
be
> upgrading your "test" application environment to.  Consider the following
> steps:
>
> 1.  Take a complete system backup (just in case).
> 2.  Upgrade all of the system manager applications (this will require
> scheduling as no one can be using JBA at all while this takes place, all
> subsystems down, etc.).
> 3.  Upgrade your "test" application environment.  The PTFs can be
overridden
> to apply to an environment other than the "live" one (this can be done
while
> other users are using the "live" environment, but it does use a
considerable
> amount of system resources).
> 4.  Reapply any mods to the applications in the test environment using the
> new source that the PTF.....Oh wait I forgot that GEAC doesn't supply
source
> anymore (sorry couldn't resist that one).  You may have to get with GEAC
for
> this step or make sure your sales contract states that you are eligible
for
> source code.
>
> Above all else read the directions that are supplied in the product update
> guide that comes with the upgrade software.  I've always found them to be
> useful and will shed light on many of the questions you may still have.
>
> Regards,
>
> Eric Daniel
> Technical Consultant
> Viking Consulting
>
>
> ----- Original Message -----
> From: "Gaffney, Theresa" <Theresa.Gaffney@pollak.com>
> To: <JBAUSERS-L@midrange.com>
> Sent: Friday, July 28, 2000 9:28 AM
> Subject: RE: Upgrade to 3.5.2b SP2
>
>
> > We are just in the planning stage of upgrading to 3.5.2b. Has anyone
tried
> > to install to a test environment?  We have three environments using the
> same
> > source code. We were informed  by Geac that we could install the upgrade
> to
> > just one of our environments without disturbing the live one. I would be
> > interesting in hearing from anyone that has the same scenario.
> >
> >  Thanks
> >
> > -----Original Message-----
> > From: Jim_Hawkins@tsss.com [SMTP:Jim_Hawkins@tsss.com]
> > Sent: Friday, July 28, 2000 8:04 AM
> > To: JBAUSERS-L@midrange.com
> > Subject: Re: Upgrade to 3.5.2b SP2
> >
> >
> > We are in the process of upgrading to 3.5.2b sp2 also (we were
> > supposed to
> > upgrade last weekend in fact).  We have applied to a test world.
> > Issues we
> > have found.....
> > 1. In test world our MPS and MRP are reporting nothing!  Geac
> > support is
> > telling us that this is because of an improper install procedure.
> > We were
> > told (asking several times to be sure) that we could upgrade each
> > application from 3.5.1 to 3.5.2b.  When we were completely to 3.5.2b
> > we
> > could apply sp 1 and sp 2 to each application.  We are now being
> > told that
> > the entire system must go 3.5.2a. then 3.5.2b, then sp1, then sp2...
> > 2.  There are several library list gotchas when applying to a test
> > world
> > (hard coded libraries)
> > 3.  This past weekend we applied to live 3.5.2b--sp2.  As part of
> > our
> > standard upgrade procedure we do testing of the upgraded system
> > prior to
> > allowing users access.  We received an error on PTF  PD-V3-0058! I
> > reviewed
> > the job log but did not see anything out of the ordinary from any
> > other PTF
> > job log I ever looked at.  Turns out we lost all data in OSLPDF3
> > library.
> > All data files were empty!  We tried running several MPS/MRP related
> > programs and had problems up the wazoo.  Numerous file objects did
> > not
> > exist in OSLPDF3 library.  We then discovered that the users had not
> > tested
> > the MRP/MPS in the test world like they had told us they had (#1
> > above).
> > We do not yet have a resolution from GEAC support on what this
> > problem was.
> > We made the decision Sunday afternoon to return to 3.5.1 until we
> > could get
> > some of these issues ironed out.  Will keep the group posted on the
> > resolution.
> >
> >
> >
> >
> >                     Stefan Jansson
> >
> >                     <sjansson@fossil.co        To:
> > "'JBAUSERS-L@midrange.com'"
> >                     m>
> > <JBAUSERS-L@midrange.com>
> >                     Sent by:                   cc:
> >
> >                     owner-jbausers-l@mi        Subject:     Upgrade
> > to 3.5.2b SP2
> >                     drange.com
> >
> >
> >
> >
> >
> >                     07/27/00 06:35 PM
> >
> >                     Please respond to
> >
> >                     JBAUSERS-L
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > We're embarking on a project to upgrade our System/21 software to
> > version
> > 3.5.2b, SP2.  I wonder if anyone else have gone through this, and if
> > they
> > can relate any particular gotchas or things to watch out for.  Any
> > and all
> > feedback would be greatly appreciated.  We're doing it in a separate
> > "world"
> > first, so we have some leeway for errors, but I don't want to take
> > too much
> > advantage of this fact.  We're a Style shop.
> >
> > Technically Yours,
> >
> > Stefan Jansson
> > Fossil
> > Richardson, Tejas
> > +---
> > | This is the JBA Software Users Mailing List!
> > | To submit a new message send your mail to JBAUSERS-L@midrange.com.
> > | To subscribe to this list send email to
> > JBAUSERS-L-SUB@midrange.com.
> > | To unsubscribe from this list send email to
> > JBAUSERS-L-UNSUB@midrange.com.
> > | Questions should be directed to the list owner: doug333@aol.com.
> > +---
> >
> >
> >
> > +---
> > | This is the JBA Software Users Mailing List!
> > | To submit a new message send your mail to JBAUSERS-L@midrange.com.
> > | To subscribe to this list send email to
> > JBAUSERS-L-SUB@midrange.com.
> > | To unsubscribe from this list send email to
> > JBAUSERS-L-UNSUB@midrange.com.
> > | Questions should be directed to the list owner: doug333@aol.com.
> > +---
> > +---
> > | This is the JBA Software Users Mailing List!
> > | To submit a new message send your mail to JBAUSERS-L@midrange.com.
> > | To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com.
> > | To unsubscribe from this list send email to
> JBAUSERS-L-UNSUB@midrange.com.
> > | Questions should be directed to the list owner: doug333@aol.com.
> > +---
>
> +---
> | This is the JBA Software Users Mailing List!
> | To submit a new message send your mail to JBAUSERS-L@midrange.com.
> | To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
JBAUSERS-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner: doug333@aol.com.
> +---
>

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