Rational Developer for System z
PL/I for Windows, Version 7.6, Programming Guide

Error messages

Error messages can come from the following sources:

An error reported on an ODBC driver has the following format:

[vendor] [ODBC_component] message

ODBC_component is the component in which the error occurred. For example, an error message from INTERSOLV's SQL Server driver would look like this:

[INTERSOLV] [ODBC SQL Server driver] Login incorrect.

If you get this type of error, check the last ODBC call your application made for possible problems or contact your ODBC application vendor.

An error that occurs in the data source includes the data source name, in the following format:

[vendor] [ODBC_component] [data_source] message

With this type of message, ODBC_component is the component that received the error from the data source indicated. For example, you may get the following message from an Oracle data source:

[INTERSOLV] [ODBC Oracle driver] [Oracle] ORA-0919: specified 
length too long for CHAR column

If you get this type of error, you did something incorrectly with the database system. Check your database system documentation for more information or consult your database administrator. In this example, you would check your Oracle documentation.

The Driver Manager is an application that establishes connections with drivers, submits requests to drivers, and returns results to applications. An error that occurs in the Driver Manager has the following format:

[vendor] [ODBC DLL] message

vendor can be Microsoft or INTERSOLV. For example, an error from the Microsoft Driver Manager might look like this:

[Microsoft] [ODBC DLL] Driver does not support
this function

Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)