This parameter allows you to specify the fully qualified path for the diagnostic information file for the CF
Starting in Version 10.1, the cf diagnostic data directory path writes to a private db2diag.log for each CF by default. To revert to the behavior of previous releases, in which the diagnostic data for the CF is written to the same directory, specify the cf_diagpath with a pathname and no token.
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.