SourcePro DB handles errors differently depending upon how they are generated. The following sections describe error messages used with the DB Access Module for DB2 CLI.
When an error or warning is generated by an Access Module call to the DB2 CLI, information about the event is retrieved via a call to SQLGetDiagRec() and transferred to an RWDBStatus. This RWDBStatus object is passed as a parameter to the installed error handler. RWDBStatus uses the following format to describe events reported by DB2 CLI:
errorCode: RWDBStatus::serverError if an error occurred, or RWDBStatus::ok if a warning is being generated, or RWDBStatus::notConnected if a communication error occurred indicated by a SQLSTATE code of 08XXX; for example, "08001"
message: "SQL call failed." if an error occurred, or "Success with info" if a warning is being generated.
vendorMessage1: The SQLSTATE code; for example, "21S01".
vendorMessage2: The diagnostic message.
vendorError1: The native error code.
vendorError2: The SQLRETURN code from the failed SQL function.
An application can use the mapping shown above to write an error handler that reports errors on cerr and issues warnings on clog. For example:
void myErrorHandler(const RWDBStatus& stat)
{
if (stat.errorCode() != RWDBStatus::ok) // Errors
cerr << stat.vendorMessage2();
else // Warnings
clog << stat.vendorMessage2();
}
|
All errors associated with the status will be reported.
Copyright © Rogue Wave Software, Inc. All Rights Reserved.
The Rogue Wave name and logo, and SourcePro, are registered trademarks of Rogue Wave Software. All other trademarks are the property of their respective owners.
Provide feedback to Rogue Wave about its documentation.