AIX 5L Problem Determination - IBM Redbooks

9.5.1 Trace hook IDs
The events traced are referenced by hook identifiers. Each hook ID uniquely
refers to a particular activity that can be traced.
Hook IDs are defined in the /usr/include/sys/trchkid.h file. When tracing, you can
select the hook IDs of interest by using the trace -j command, and exclude
others that are not relevant to your problem by using the trace -k command.
The following example is extracted from the trchkid.h file:
...
#define HKWD_SYSC_MKDIR 0x15600000
#define HKWD_SYSC_MKNOD 0x15700000
#define HKWD_SYSC_MNTCTL 0x15800000
#define HKWD_SYSC_MOUNT 0x15900000
#define HKWD_SYSC_NICE 0x15a00000
#define HKWD_SYSC_OPEN 0x15b00000
#define HKWD_SYSC_OPENX 0x15c00000
#define HKWD_SYSC_OUNAME 0x15d00000
#define HKWD_SYSC_PAUSE 0x15e00000
#define HKWD_SYSC_PIPE 0x15f00000
#define HKWD_SYSC_PLOCK 0x16000000
#define HKWD_SYSC_PROFIL 0x16100000
#define HKWD_SYSC_PTRACE 0x16200000
#define HKWD_SYSC_READ 0x16300000
#define HKWD_SYSC_READLINK 0x16400000
#define HKWD_SYSC_READX 0x16500000
#define HKWD_SYSC_REBOOT 0x16600000
#define HKWD_SYSC_RENAME 0x16700000
#define HKWD_SYSC_RMDIR 0x16800000
...
When specifying the hook ID to the trace command, only the three left-most
digits should be specified. From the preceding example, when the open system
call is traced, the ID 15b must be specified.
Specifying relevant (or irrelevant) hook IDs can be difficult at this time since you
do not know the actual cause of the problem. If source code access to the
application is available or the developer is known, then this can be helpful for
specifying useful hook IDs.
Note: Specifying useful hook IDs can reduce the mount of data significantly
and make the analysis part of the problem easier.
212 IBM ^ Certification Study Guide - AIX 5L Problem Determination Tools and Techniques