cf_diagpath - diagnostic data directory path for the CF configuration parameter

This parameter allows you to specify the fully qualified path for the diagnostic information file for the CF

Configuration type
Database Manager
Applies to
  • Db2® pureScale®
Parameter type
Configurable offline
Propagation class
Immediate
Default [range]
INSTHOME/sqllib/db2dump/ $m [any valid path name]
Symbols
pathname
A directory path to use instead of the default CF diagnostic data directory.
$h
Resolves to HOST_hostname.
Note: Starting in Version 10, in Db2 pureScale environments, $h refers to the member's home host.
$n
Resolves to NODEnumber
$m
Resolves to DIAGnumber.
/trailing-dir
A single directory, or a directory and sub-directory to trail $h or $n
The following values are available:
  • '"$h"'
  • '"$h/trailing-dir"'
  • '"pathname $h"'
  • '"pathname $h/trailing-dir"'
  • '"$n"'1
  • '"$n/trailing-dir"'
  • '"pathname $n"'
  • '"pathname $n/trailing-dir"'
  • '"$m"'
  • '"$m/trailing-dir"'
  • '"pathname $m"'
  • '"pathname $m/trailing-dir"'
  • '"$h$n"'2
  • '"$h$n/trailing-dir"'
  • '"pathname $h$n"'
  • '"pathname $h$n/trailing-dir"'
  • '"$h$m"'
  • '"$h$m/trailing-dir"'
  • '"pathname $h$m"'
  • '"pathname $h$m/trailing-dir"'

Starting in Db2 version 11.5.6, while in a Db2 pureScale environment, the CF diagnostic data directory path used must contain at least one split token ($h, $n, or $m) to ensure a private log file for each member and CF.

Note: When the cf_diagpath directory is not available, but the alt_diagpath is available, the CF diagnostic logs are placed into the alt_diagpath directory.
Each CF log file name has the following format: 
cfdiag-YYYYMMDDhhmmssuuuuuu.<cf#>.log
However, there is also a single static CF diagnostic log name that always points to the most current CF diagnostic logging file and has the following format:
cfdiag.<cf#>.log
For example, if you listed all of the CF log files, you would see something similar to the following:
$ ls -la cfdiag*
lrwxrwxrwx 1 db2inst1 pdxdb2   35 2011-02-09 15:07 
      cfdiag.128.log -> cfdiag-20110209150733000049.128.log
lrwxrwxrwx 1 db2inst1 pdxdb2   35 2011-02-09 15:10 
      cfdiag.129.log -> cfdiag-20110209151021000040.129.log
-rw-r-xr-- 1 db2inst1 pdxdb2 1271 2011-02-09 15:07 
      cfdiag-20110209150733000049.128.log
-rw-r-xr-- 1 db2inst1 pdxdb2 1271 2011-02-09 15:07 
      cfdiag-20110209150740000082.129.log
-rw-r-xr-- 1 db2inst1 pdxdb2 1274 2011-02-09 15:10 
      cfdiag-20110209151021000040.129.log
In this example, cfdiag.128.log and cfdiag.129.log are symbolic links to the latest versions of the otherwise time stamped log files.

The CF log file looks similar to the db2diag.log file.

1 $n is deprecated and might be removed in a future release.
2 $h$n is deprecated and might be removed in a future release.