DB2 Connect and db2syscs.exe, db2diag.log

Philip Gunning

DB2 Connect and db2syscs.exe, db2diag.log
Delete it (db2diag.log)and it will be recreated as needed. Before you do
that, go to the end and find out what is causing the problem. Then take
that info and pursue with IBM. You can also run a CLI or DRDA trace but if
you have high CPU then that is probably not in your best interest at this
time. Check mstr and dist address space on host for associated errors.
Rgds, pg

Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm