AUTOPAT used to add the entries in HPSWINFO as well.

If they are missing then probably because
* the patch is only written to be applied using PatchIX,
* the patch failed
* the HPSWINFO file couldn't be expanded during the process for any reason

Best regards, Andreas Schmidt, CSC, Germany





John Burke <[log in to unmask]>@RAVEN.UTC.EDU> on 20/03/2002 01:24:56

Please respond to John Burke <[log in to unmask]>

Sent by:  HP-3000 Systems Discussion <[log in to unmask]>


To:   [log in to unmask]
cc:
Subject:  Re: [HP3000-L] patched or not??


Autopat? Tsk, tsk. Should have used patchix! In which case it will update
hpswinfo. It's been so long since I used autopat, I don't recall if it
updates hpswinfo.

As for psswinvp, the command file in 6.5 is broken, the correct calling
sequence is:

[3]:type psirpt.pred.sys
file psilist=$stdlist
run psswinvp.pred.sys;xl='xl.pred.sys,diagxl.pred.sys'

John

> From: Donna Garverick [mailto:[log in to unmask]]
>
> so we're applying post-6.5pp3 reactive patches using
> autopat....and we think (but are really wondering....) that
> we're done.  if we look in hpswinfo, the last entry is for
> pp3 -- not the reactives.  in patchxl, i find a file
> 'logok'....and the top of it is:
>
> :print logok.patchxl
> AUTOPAT - Patches below installed by xxxxx THU, MAR 14,
> 2002  3:42 PM
> Patch ID  SR Number   - Module Identity
> Timestamp
> ========  ===========   =============================
> =========
>
> shouldn't have something been added to hpswinfo by autopat?
> is there a step waiting to be done?  (and no, i didn't do
> this....else i wouldn't be asking)           - d
>
> btw -- psswinvp.pred appears to be non-functioning (won't
> say 'broke'....won't tell you what i'm thinking on that
> topic either :-)
>

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *