What problem are you trying to solve?
By reading the current PTF cover letter for 540 at
http://www-912.ibm.com/s_dir/sline003.nsf/2d3aff1c6b4d6ce086256453000d971e/9d2cbc7b715949d48625741f006f2b3a?OpenDocument
I can see there was the following:
C0292540
C0117540
C9321540
But that doesn't even go back as far as your one system. If all you are
doing is gathering data to say "You are x levels behind" then you're
battling an ostrich with it's head in the sand. You have enough of that
ammo with what levels you can record, length of time since last cume, etc.
I set up one system with a weekly CL to do the following:
SNDPTFORD PTFID((*CUMPKG))
INSPTF LICPGM((*ALL)) DEV(*SERVICE) INSTYP(*DLYALL)
SNDPTFORD PTFID((*HIPERGRP))
INSPTF LICPGM((*ALL)) DEV(*SERVICE) INSTYP(*DLYALL)
SNDPTFORD PTFID((*DB2GRP))
INSPTF LICPGM((*ALL)) DEV(*SERVICE) INSTYP(*DLYALL)
SNDPTFORD PTFID((*BRSGRP))
INSPTF LICPGM((*ALL)) DEV(*SERVICE) INSTYP(*DLYALL)
SNDPTFORD PTFID((*JVAGRP))
INSPTF LICPGM((*ALL)) DEV(*SERVICE) INSTYP(*DLYALL)
SNDPTFORD PTFID((*HTTPGRP))
INSPTF LICPGM((*ALL)) DEV(*SERVICE) INSTYP(*DLYALL)
SNDPTFORD PTFID((*PFRGRP))
INSPTF LICPGM((*ALL)) DEV(*SERVICE) INSTYP(*DLYALL)
Then their weekly IPL did the actual apply.
Some of those groups may not exist on older versions of the OS but they're
on 7.1. Using names instead of numbers (if available) allows the same CL
to work across releases.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.