Understanding fileset numbering
AnthonyEnglish 270000RKFN Visits (7676)
lslpp -l command, you get output such as this:
deviThe second field (highlighted) shows the numbering of the fileset. The IBM AIX Operating System Release and Service Strategy Details and Best Practices explains what that means. In the section "Changing the M in VMRF", it says:
Starting with AIX 5.3 TL7, any filesets that are updated will get a new ‘M’ in the VRMF. For example, if the bos.rte.lvm fileset was updated, its update in AIX 5.3 TL7 would be 126.96.36.199 and the first update will be 188.8.131.52. The fileset updates won’t necessarily correspond to the SP because an update for fileset bos.rte.lvm might not come out until SP3, but it would be called bos.rte.lvm 184.108.40.206Knowing this can be helpful if you have a listing of filesets. Ordinarily, you'd get a better idea of your AIX Version, by using the command oslevel -s. On the host I'm working on, oslevel reports:
6100-06-01-1043Or, AIX 6.1, Technology Level 6, Service Pack 1 from YYWW (Year 2010, week 43).
Here's how the filesets match up with that. Once again, an extract from lslpp -l:
The first fileset is for the Storage Framework Module (whatever that is!). It's numbered 220.127.116.11 - in other words AIX 6.1 TL 6 SP 1. The USB System Software fileset is 18.104.22.168 - in other words 6.1 TL 6. This particular fileset didn't change when SP 1 came out.
Just as an aside, you have to admire the readability of the AIX release and service delivery strategy page. Click on one of the links and you'll see what I mean. It's so easy to navigate and get to what you want to know.
It gives a quick snapshot of the major points:
"What hasn't changed"
Having a section on what hasn't changed accommodates old and new readers. What a great idea! The web site is a very easy way of digesting new information without having to read through an entire document to hunt for changes.
On the top right of the page is the same information in a single white paper in PDF format. Fine if you want to read the whole thing, but let's face it, we're skimmers, not readers these days.
I hope other key documentation will follow this approach in future. Well done to the guys responsible for the web page.