SEO

Group,

We have an obsolete MFG/PRO Version 9.0 SP4 application that is currently
running on Progress version 8.3. We need to replace the hardware which is
very old, and will be upgrading the O/S, so keeping this version of
Progress is probably not an option. Does anyone know if there will be any
issues upgrading to Progress version 9?

Since the app is obsolete and only occasionally used for inquiry, we want
to do as little as possible. Compiling the code is expected, but what about
database converions? There are 51 active databases on this host - sheesh!

Thanks,
Julie

Hi Julie,

First off, I'm not a DBA and it's not my specialty and I also think you
should bring it up on the PEG.COM email group, you can even speak with
some of the Progress Software engine crew and some Progress VP's. I
think, this USENET forum is the most dead of the Progress forums and in
this respect it's even doing a mis-service.

I don't know if you're also moving to a diff platform and O/S and then
there are some option you may not be able to use. I think, the
conversion utility and the binary dump and load won't work in this
case.

AFAIK, the options are either the conversion utility especially if you
have a limited window of time for completing the conversion.

There are also a binary and ASCII dump and load. I.e. dumping the data
into files and loading them into the new database. You should do a dump
and load every once in a while to defrag and descatter ( is that even a
word ?? ) compact indices etc., in general compact and boost
performance especially if it hasn't been done in a long while.

Maybe you should try a multi-threaded ASCII dump and load. That will
work no matter what's the case. Which brings me to my next question
what's the database sizes ?

Besides that there are other things to consider, complications usually
tend to popup in our line of work. Like checking if any source files
are missing or the compiled r-code are diff from the source code ? I've
seen lot's of places where the source code was poorly managed
especially if there's been a substantial amount of customization.

So too sum things up, Let's continue this discussion on PEG.COM ( again
it's an email group not a website/forum i.e. you send and recieve email
) and we need more specifics i.e. exact versions, new O/S hardware,
database sizes etc. HTH



Julie Warden wrote:

> Group,
>
> We have an obsolete MFG/PRO Version 9.0 SP4 application that is currently
> running on Progress version 8.3. We need to replace the hardware which is
> very old, and will be upgrading the O/S, so keeping this version of
> Progress is probably not an option. Does anyone know if there will be any
> issues upgrading to Progress version 9?
>
> Since the app is obsolete and only occasionally used for inquiry, we want
> to do as little as possible. Compiling the code is expected, but what about
> database converions? There are 51 active databases on this host - sheesh!
>
> Thanks,
> Julie

In article <Xns96EF61BABCFC6JulieWarden@140.99.99.130>,
Julie Warden <Julie_Warden@spamfreeHotmail.com> wrote:

> Group,
>
> We have an obsolete MFG/PRO Version 9.0 SP4 application that is currently
> running on Progress version 8.3. We need to replace the hardware which is
> very old, and will be upgrading the O/S, so keeping this version of
> Progress is probably not an option. Does anyone know if there will be any
> issues upgrading to Progress version 9?
>
> Since the app is obsolete and only occasionally used for inquiry, we want
> to do as little as possible. Compiling the code is expected, but what about
> database converions? There are 51 active databases on this host - sheesh!
>
> Thanks,
> Julie

You should be pretty safe on the database upgrade.

It's the 4GL upgrade you need to watch out for.

http://psdn.progress.com/library/whi.../character_app
s.pdf


Do you have source or is it encrypted source code? If encrypted you may
need to get with QAD to pull in the changes that might be needed.

--
Available for Hire! http://amduus.com/Resumes/

Scott Auge <scott_auge@yahoo.com> wrote in
news:scott_auge-1EAC3E.08254117102005@news1.west.earthlink.net:

> In article <Xns96EF61BABCFC6JulieWarden@140.99.99.130>,
> Julie Warden <Julie_Warden@spamfreeHotmail.com> wrote:
>
>> Group,
>>
>> We have an obsolete MFG/PRO Version 9.0 SP4 application that is
>> currently running on Progress version 8.3. We need to replace the
>> hardware which is very old, and will be upgrading the O/S, so keeping
>> this version of Progress is probably not an option. Does anyone know
>> if there will be any issues upgrading to Progress version 9?
>>
>> Since the app is obsolete and only occasionally used for inquiry, we
>> want to do as little as possible. Compiling the code is expected, but
>> what about database converions? There are 51 active databases on this
>> host - sheesh!
>>
>> Thanks,
>> Julie
>
> You should be pretty safe on the database upgrade.
>
> It's the 4GL upgrade you need to watch out for.
>
> http://psdn.progress.com/library/whi...cs/character_a
> pp s.pdf
>
>
> Do you have source or is it encrypted source code? If encrypted you
> may need to get with QAD to pull in the changes that might be needed.
>


Thanks Guys,

It turns out when I wrote a little script to see who was in each db that
was up, I got 3 users out of the 51 DBs with an hour of monitoring. It
turns out the plant is closed, so our goal is to spend as close to zero
hours on this project.

I think we're going to scrounge some slightly newer HP hardware and
determine what is the oldest HP O/S that'll run on it, then install that
and just get the app up with as little effort as possible. The
installation looks like a tar pit, no standard directory structures for
these folks.

Thanks again for your input, and I guess next time I'll post to PEG.com.

Sincerely,
Julie