Often there is need to combine DB2 diagnostic data with OS. Here are few useful commands and utilities you can use on different platforms..
| AIX | HP-UX | Solaris | Linux |
OS level | /usr/sbin/oslevel | /usr/bin/uname -a | /usr/bin/uname -a | /bin/uname -a |
Software | /usr/bin/lslpp -ah | /usr/sbin/swlist -v | /usr/bin/showrev -p | /bin/rpm -qa |
CPUs | /usr/sbin/lsdev -C (grep proc) | /usr/sbin/ioscan (grep processor) | /usr/sbin/psrinfo -v | /bin/dmesg (grep CPU) |
Memory | /usr/sbin/lsattr -El sys0 (grep realmem) /usr/samples/kernel/vmtune | /usr/sbin/dmesg (grep Physical) | /usr/sbin/prtconf (grep Memory) | /bin/dmesg (grep Memory) /usr/bin/free |
IPC resources | Ipcs | /usr/sbin/kmtune SAM GUI tool | /usr/sbin/sysdef -i /etc/system (file) | /usr/bin/ipcs -l |
User limits | ulimit -a /etc/security/limits (file) | ulimit -a | ulimit -a | ulimit -a |
User environment | Set | Set | Set | Set |
Windows NT has a nice interface for obtaining system information:
winmsd /af
On Windows 2000® and XP®:
<OSdrv>:\Program Files\Common Files\Microsoft Shared\MsInfo\Msinfo32
/report
This command does not report on installed software. One way to obtain this information is
to export the registry (at least the HKEY_LOCAL_MACHINE\SOFTWARE branch) to a
file by using the regedit tool.
System error and message logs on UNIX®
The following table shows where the logs are located on different UNIX platforms.
| AIX | HP-UX | Solaris | Linux |
Error / Message Logs | /usr/bin/errpt -a | /var/adm/syslog/syslog.log /usr/sbin/dmesg | /var/log/messages* | /var/adm/messages* |