On 1/06/2021 1:56 am, Colin Paice wrote:
1. The SMF 92-59 records say there are 14 sections - but there is data
for only 13 sections. The field is SMF92DON-1
I had a look at my data and I can see the same thing in my 92-59
records. If there are 14 sections, the 14th section is zeros apart from
the timestamp. I only see problems in records with 14 sections. I also
have records with 12 or 13 sections, they don't have the problem.
I don't see a partially blank name, the entire section looks like it
hasn't been filled in. (The names are at the end of each section, so
might look like it belongs with the next empty section if you are
eyeballing a dump.)
2. In the SMF 92-11 it reports data on the individual files used. It
reports the file as used, for example ./write.c I expected it to say
/u/adcd/write.c. The data as is, is pretty useless, as I do not know which
write.c was used. Other records have /usr/lib/nls/msg/C/fsumrcat.cat as
expected (because that is what the program used)
This is unfortunate, but I think it reflects the information available
at the point the record is written. Given filesystem links etc. it may
not even be possible to be sure of the path used to open a file if a
relative path is used. The inode number and device number is probably
the true identifier of a file.
You can probably make reasonable guesses about a relative path by
looking at directory read records from the same task.
--
Andrew Rowley
Black Hill Software
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
