At 16:43 -0400 on 06/17/2009, John P. Baker wrote about Re: SMF
record data - ALTER gdgbase LIMIT(n):
John,
If you have all of your SMF data, you should be able to find the tracks of
the culprit by scanning for:
SMF66SUB = "UP"
SMF66CNM = "ICF Catalog Dataset Name"
SMF66TYP = "B"
SMF66ENM = "GDG Base Dataset Name"
If it was done months ago, this may involve a lot of processing; it will all
depend on how much frothing at the mouth is going on.
You will probably have to dump the records in char/hex format to show the
change in the generation count, but it should be pretty easy to see once you
have extracted the records.
John P. Baker
That is assuming that the SMF Dump when it happened is still available.
As to dumping them, this is not needed if you just write a quick and
dirty Assembler program to read the SMF files and look for the needed
SMF66 records. Have the program look at the fields instead of
printing and using IEBIBALL. As an alternative, you can pass them
through SORT to fond the records but I am not sure if these fields
are at a constant displacement (as would be required by a SORT SELECT
statement).
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
