I suspect that Scott is correct.  We've used Patch/iX successfully for
several updates, and HPPATH on any of our systems doesn't strictly conform
to Cynthia's example.  We do specify !HPGROUP, PUB, PUB.SYS at some point
in each of them, however.

Lee Gunter          [log in to unmask]




From: Scott McClellan <[log in to unmask]> on 10/02/98 02:39 PM

Please respond to Scott McClellan <[log in to unmask]>


To:   [log in to unmask]
cc:    (bcc: Lee Gunter/BCBSO/TBG)
Subject:  Patch/iX (& HPPATH variable)




> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
> Behalf Of Cynthia Fowler


> FWIW, we installed this patch first on our development box to
> workout any kinks. The only "gotcha" we encountered was due to
> the HPPATH variable redirect for our 3rd party software (NBSpool,
> JMS/3000, etc.). Prior to running Patch/iX, we had to type:
>
>      :SETVAR HPPATH "!HPGROUP,PUB,PUB.SYS"
[remainder deleted...]

I "think" that the real issue is that Patch/iX assumes that "!HPGROUP"
will appear somewhere in the path. If this is the case, your patch
does not need to be set *exactly* as Cynthia describes, but it
must contain "!HPGROUP" somewhere in the path.

I have cc'd Michael Dovano...Michael would you please verify the
statement I made and clarify it (one way or the other) to the
3000-L list.

Also, I have seen messages regarding this problem in the past. I am
not sure if there is an SR written for the problem (if not there
should be) and/or if the problem is already fixed in the most recent
version of Patch/iX.

Michael would you please see take care of the SR (check to see
if one exists and if not write one) and also post back to the
list what the current version of Patch/iX and whether or not
the problem is fixed.

Thanks ...