Typically when working with DB2, a problem is manifested by an error message. The error message may be reported immediately to the user, or it may be stored in some diagnostic file like the administration notification log or the db2diag.log (these diagnostic files are discussed in section 17.4, DB2 First Failure Data Capture).
Figures 17.2 and 17.3 show examples of DB2 reporting problems immediately after executing an operation. In Figure 17.2, after clicking on the instance
MYINST in the object tree of the Control Center, getting the DB2 message SQL1032N indicates that this instance has not started.
section 17.7, The DB2 Trace Facility).
![[View full size image]](/image/library/english/13748_17fig02_alt.jpg;382543){kind=link}