This parameter allows you to specify the fully qualified primary path for DB2 diagnostic information.
The primary diagnostic data directory path can contain dump files, trap files, an error log, a notification file, an alert log file, and first occurrence data collection (FODC) packages, depending on your platform.
db2 update dbm cfg using diagpath '"$h"'
which
creates a subdirectory under the default diagnostic data directory
with the host name, as in the following:Default_diagpath/HOST_hostname
db2 update dbm cfg using diagpath '"$h/trailing-dir"'
which
creates a subdirectory under the default diagnostic data directory
with the host name and a trailing directory, as in the following:Default_diagpath/HOST_hostname/trailing-dir
db2 update dbm cfg using diagpath '"pathname $h"'
which
creates a subdirectory under your own specified diagnostic data directory
with the host name, as in the following:pathname/HOST_hostname
db2 update dbm cfg using diagpath '"pathname $h/trailing-dir"'
which
creates a subdirectory under your own specified diagnostic data directory
with the host name and a trailing directory, as in the following:pathname/HOST_hostname/trailing-dir
db2 update dbm cfg using diagpath '"$n"'
which
creates a subdirectory for each partition under the default diagnostic
data directory with the partition number, as in the following:Default_diagpath/NODEnumber
db2 update dbm cfg using diagpath '"$n/trailing-dir"'
which
creates a subdirectory for each partition under the default diagnostic
data directory with the partition number and trailing directory, as
in the following:Default_diagpath/NODEnumber/trailing-dir
db2 update dbm cfg using diagpath '"pathname $n"'
which
creates a subdirectory for each partition under your own specified
diagnostic data directory with the partition number, as in the following:pathname/NODEnumber
db2 update dbm cfg using diagpath '"pathname $n/trailing-dir"'
which
creates a subdirectory for each partition under your own specified
diagnostic data directory with the partition number and trailing directory,
as in the following:pathname/NODEnumber/trailing-dir
db2 update dbm cfg using diagpath '"$h$n"'
which
creates a subdirectory for each logical partition on the host under
the default diagnostic data directory with the host name and the partition
number, as in the following:Default_diagpath/HOST_hostname/NODEnumber
db2 update dbm cfg using diagpath '"$h$n/trailing-dir"'
which
creates a subdirectory for each logical partition on the host under
the default diagnostic data directory with the host name, the partition
number, and a trailing directory, as in the following:Default_diagpath/HOST_hostname/NODEnumber/trailing-dir
db2 update dbm cfg using diagpath '"pathname $h$n"'
which
creates a subdirectory for each logical partition on the host under
your own specified diagnostic data directory with the host name and
the partition number, as in the following:pathname/HOST_hostname/NODEnumber
usr1@boson /home/user1/db2dump->ls -R *
HOST_boson:
HOST_boson:
NODE0000 NODE0001 NODE0002
HOST_boson/NODE0000:
db2diag.log db2eventlog.000 db2resync.log db2sampl_Import.msg events usr1.nfy
HOST_boson/NODE0000/events:
db2optstats.0.log
HOST_boson/NODE0001:
db2diag.log db2eventlog.001 db2resync.log usr1.nfy stmmlog
HOST_boson/NODE0001/stmmlog:
stmm.0.log
HOST_boson/NODE0002:
db2diag.log db2eventlog.002 db2resync.log usr1.nfy
db2 update dbm cfg using diagpath '"pathname $h$n/trailing-dir"'
which
creates a subdirectory for each logical partition on the host under
your own specified diagnostic data directory with the host name, the
partition number and a trailing directory, as in the following:pathname/HOST_hostname/NODEnumber/trailing-dir
db2 get dbm cfg | grep DIAGPATH
A
successfully split diagnostic data directory path returns the values $h, $n,
or $h$n with a preceding blank space.
For example, the output returned is similar to the following:Diagnostic data directory path (DIAGPATH) = /home/usr1/db2dump/ $h$n