Contains an engine-specific warning message
Most engines supply a mechanism for signalling an unusual, but non-fatal condition. Some engines uses a warning array or byte. These engines do not supply warning messages and therefore do not use
@dmengwarnmsg. Others use a code and message for low-severity errors. Refer to the Database Drivers for engine-specific information and an example.
By default, Panther ignores warnings. If an application needs to alert users to warning codes or messages, it must use a JPL or C function to check for them. There is no default warning handler. The most efficient way to process warning values is with an installed exit handler.