How do you display w/c Patch Level you are in now.

[f. halili]

I installed the DEC2004 bundles today. I can see the BUNDLES if I do a:

# swlist -l bundle
GOLDAPPS11i B.11.11.0412.5 Gold Applications Patches for HP-UX 11i v1, December 2004
GOLDBASE11i B.11.11.0412.5 Gold Base Patches for HP-UX 11i v1, December 2004

====
I tried to check my current patch level with this command:

# swlist -l bundle -a state -a revision HPUX\*

HPUX11i-OE B.11.11.0209
HPUXBase64 B.11.11
HPUXBaseAux B.11.11.0209

The 11.11.0209 is the same I get before and after the install.

===

What's the command to list the machine's current patch level?

Thanks,
f. halili

[Geoff Wild]

The core HP-UX doesn't really have a ptch rev - if that's what you are looking for (like Sloaris)...

How about :

what /stand/vmunix |more

That will show you all patches for different components...

Rgds...Geoff

[Pete Randall · Accepted solution]

I use "swlist -l bundle |grep -i patch".


Pete

[Bill Hassell]

There is no real conceopt of a patch level (aka, service pack on Windows). The GOLD patch collection is a bundle and does represent literally hundreds of patches. But there may be patches to specific parts of the OS that are not common (ie, SNA networking, MCSG clustering, APA network clustering, etc) and these do not get reflected in the kernel. The best way to see the installed patches is: swlist -l patch. But as you'll see, there will be hundreds of lines of output.

So the month/year (Dec 2004) patch bundle is about the best nomenclature to use in defining a patch level.

[Jeff Schussele]

Hi,

You'll also note in the revision numbering schema for those patch bundles that the date is embedded - i.e.:

B.11.11.0412.5

The 04 is year - the 12 is month & I even think the 5 is day - but I'm not positive on day.

This also works for the core release as well - in your case it would have been Sept 2002.

HTH,
Jeff

[Sandman!]

Since the bundle shows up in the swlist command, you have to drill down the SD tree in order to locate the associated patches. To do that type the following command:

# swlist -l patch GOLDAPPS11i

this should give a listing of all the patches that were included in the Dec2004 bundle.

cheers!

[Tim D Fulford]

HP patching is slightly eclectic, but is based on sound logic, and not too difficult to understand. There are very good reason for not having a fixed levels of patching in HP-UX
1 - Some patches are released for varius aplications, so you would not want to install a patch for an application you do not have
2 - Some patches are for specific H/W (e.g. LAN types etc). Ah=gain you would not want to install patches for H/W you do not have.

The nearest you can get is to put the Golden Patches on the system every few months and then you will be patched to a date (say Dec 2004)

Patches/Applications are split into various levels

bundles - this is a group of products (or patches applications)
products - this is a list of the product sets, either single or part of a bundle. Pure patchs would constitut a product e.g. PHKL_25212
filesets - each product is made up of one or more filesets
files - each fileset has a list of one or more files

Using the above definitions you can zoom in to the level of detail required, right down to what files a patch or application consists of.. swlist is the commad you use to do this with the various switches....

Quick list
# swlist
This will show you all the bundles (patch + application). Any product NOT in a bundle is listed too (e.g. a patch). You can easily sift through this, it is only about 50-100 lines normally

Full list
# swlist -l product
this breaks up all the buddles into its constituent products and patchs. This output can be far bigger say 150-300 lines

Check state of patches that are not configured
# swlist -a state -l fileset | egrep -v "configured|^#|^$"
This lists all filesets that are not configured, e.g. in the installed, corrupt or partila state. This is a very good check to do after installing a patch. Do note that instaled means the fileset has been correctly installed, but NOT configured for use, e.g. the fileset is not active _YET_.

regards

Tim