IC61561: JOURNAL DOES NOT USE DIAGPATH WHEN VIEWING THE NOTIFY LOG

DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• The tab where you can view the notification log in Journal is
  always looking under $INSTHOME/sqllib/dump/*.nfy to populate the
  view.
  
  Whenever DIAGPATH is not set it should pick from default path
  i.e $INSTHOME/sqllib/db2dump/*.nfy else it should pick from the
  path configured in DIAGPATH
  

Local fix

• To view the log in Journal, use the default DIAGPATH of
  $INSTHOME/sqllib/db2dump
  

Problem summary

• JOURNAL DOES NOT USE DIAGPATH WHEN VIEWING THE NOTIFY LOG
  

Problem conclusion

• First fixed in DB2 LUW v9.7 Fixpak 1
  

Temporary fix

• To view the log in Journal, use the default DIAGPATH of
  $INSTHOME/sqllib/db2dump
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  IZ35790

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  DB2 FOR LUW

• Fixed component ID

  DB2FORLUW

Applicable component levels

• R970 PSN

     UP