HP3000-L Archives

February 1996, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jon Cohen <[log in to unmask]>
Reply To:
Jon Cohen <[log in to unmask]>
Date:
Fri, 26 Jan 1996 21:08:46 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (76 lines)
Gilles Schipper <[log in to unmask]> wrote:
>I just received Powerpatch #4 and read the "READ BEFORE INSTALLING".
>
>Is it just me, or is anybody else more than a bit bewildered?
>
 
<snip>
 
>
>The reality is that you may be facing a backdate to 4.0 (which - for all
>intents and purposes is an INSTALL), and then gingerly re-updating to
>5.0 in very small steps and re-applying any individual patches and
>subsys and/or add-on tapes - in a very specific order, and with several
>cslt creation and update cycles along the way.
 
Huh?  Now I'm the one who is bewildered!  I am unaware of any scenario
that would require you to backdate to 4.0 EVER.  The worst case scenario
is this:  your XL0.LIB.SYS has been stepped on by the application of
some patches (remember, not all patches impact the XL SOM).  In this
case, you will need to correct the XL0 file (using the instructions
provided), and after that point, you may been to reapply your patches
using AUTOPAT.  We regret that we cannot make this easier for you, but
we cannot determine which patches you have applied.  Remember, some
3rd party (non-HP) patches might have also contributed to this
situation.
 
   I guess you system managers out there should take a note:  we
   at HP cannot control the patches you install, so you should
   put into place a process to track & archive your patches.
 
Finally, as to patch installation order -- our patches are cumulative,
meaning that any patch to a module of FOS will also contain all the
previous patch changes to that same module.  Further, our patch
installation tools (AUTOPAT and HPINSTAL) are intelligent enough to
avoid installing an old patch over a newer, better one.  So, although
it is best to install your patches in order, it isn't a problem if
you install the patches out of order, as long as you install all of
your patches.
 
<snip>
 
 
>For example, a customer recently received a package containing an add-on
>tape (for Glance/iX) and a powerpatch tape (Express 3). The accompanying
>instructions stated to determine if Express 3 had already been installed
>by issuing the :SHOWME command, and looking for C.50.03. This will only
>be true for systems that were shipped from the factory with this
>powerpatch integrated.  All other systems will show C.50.00, whether or
>not Express 3 has been installed. So, if followed to the letter, these
>instructions could have led to problems.
 
You are right on this one -- a :SHOWME is an insufficient check to
determine whether you are running Express 3.  I'll have to look into
this one.
 
>
>Now, to a different matter.
>
>Further on in the "READ BEFORE INSTALLING", there's a blurb about
>ALLBASE/SQL customers updating to version G1.
 
I'm going to ask the ALLBASE folks to respond this your concerns
separately.
 
 
>---------------------------------------------------------------------
>   Gilles Schipper                    Voice:      905/889-3000
>   GSA Inc.                           Fax:        905/889-3001
>   300 John Street, Box 87651         Internet:   [log in to unmask]
>   Thornhill, ON  Canada  L3T 7R4     Compuserve: 71203,474
>---------------------------------------------------------------------
 
 
Jon Cohen
HP -- Commercial Systems Division

ATOM RSS1 RSS2