Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Interpret snap.pax.Z 1
- Thread starter aixquest
- Start date
-
1
- #2
you want to call IBM's AIX support in your local and have them do the dump analysis. They are trained and have a database with more relevant items than goggle has. Also, if this crash is not one that has happened before then they can have you ftp it to them and a developer will look at it and perhaps write a fix to AIX.
If you really want to do preliminary analysis then post your errpt entry for the crash and I'll guide you through a little.
or
start page 296 of
and read about how to use kdb
here is an in-depth article
if you have years programming in C then dump analysis will be a snap otherwise priliminary dump analysis is determining type of dump and then run some info through
'for matching APARs
hope this helps
LarryBoy
If you really want to do preliminary analysis then post your errpt entry for the crash and I'll guide you through a little.
or
start page 296 of
and read about how to use kdb
here is an in-depth article
if you have years programming in C then dump analysis will be a snap otherwise priliminary dump analysis is determining type of dump and then run some info through
'for matching APARs
hope this helps
LarryBoy
The snap command just runs a bunch of commands and outputs to /tmp/ibmsupt, the .Z file is just the compressed output of the directory. What is collected depends on the switches used, it will collect things like lslpp -hac, instfix -i, lscfg -vp, errpt -a, etc.
If you want to interpret the errpt permenant hardware errors run advanced diags (diag command) in problem determination and it will give you the associated SRN or SRC and the location of the failing device if appropriate. Otherwise you will need to google.
snap command:
Have a search on the above site for software problems.
Search here for hardware info, for things like SRNs (service request numbers) and SRCs (service request codes) Hardware location codes, etc:
If you want to interpret the errpt permenant hardware errors run advanced diags (diag command) in problem determination and it will give you the associated SRN or SRC and the location of the failing device if appropriate. Otherwise you will need to google.
snap command:
Have a search on the above site for software problems.
Search here for hardware info, for things like SRNs (service request numbers) and SRCs (service request codes) Hardware location codes, etc:
- Status