Thanks to Jeff, Scott and Kirsten for the quick responses ( < 1 hour ! ) Here I was listf'ing on @pat@ and @sys@, but old hpswinfo.pub.sys eluded my memory ... Scott added some good notes on a file in install.sys that y'all might need someday...seems to be the authorative answer to what patches are REALLY on your system. Thanks Again, John (hey, there IS a shift key here!) Brown > ---------- > From: scottm[SMTP:[log in to unmask]] > Reply To: scottm > Sent: Tuesday, October 27, 1998 11:31 PM > To: [log in to unmask] > Subject: Re: what patches do i have??? > > Brown, John wrote: > > > i've been off the 3k for 2 years... venturing into hp-ux > (lost > > > > my shift-key too) ... there used to be a file out in pub.sys which > > 'autopat' appended to every time i added a patch...either the file > is > > gone, or i'm half-blind... something's changed?? maybe i just need > to > > > > grep a different file? this is a 5.5 system... can someone nudge me > > in > > the right direction? > > There are two files that inventory patches. The first one, and the one > you probably > remember, is HPSWINFO.PUB.SYS. This is just a plain old ascii file and > it can be > printed using the print command. > > Unfortunately (or maybe fortunately) it can also be edited with a > standard editor, and > deleted or overwritten quite easily (e.g. by sloppy back-up/recovery > procedures). > > For this reason (in part) a new SW inventory file was created and is > updated/trusted > by Patch/iX. The other file is called PMSWINFO.INSTALL.SYS and it > should > be accurate provided you use Patch/iX exclusively to apply patches. > Given this is not always the case (no comments from the peanut gallery > ;-) the two files are probably most accurate when viewed as an > aggregate. Patch/iX will update both HPSWINFO and PMSWINFO. > > PMSWINFO can only be viewed easily by using Patch/iX (under View > Patches) and by > using Stage/iX for the case where Patch/iX patches were staged (using > the STAGEMAN > list xxx;patches command). > > I hope you are not more confused than you were before you asked..... > > Scott McClellan >