DBP Parameters
The PPJ Framework supports a limited set of the DBP_ parameters that are supported in SAL applications. Most of the database parameters used in the original SQLWindows/Team Developer application correspond to standard ADO.NET properties, or are database-specific parameters that must be configured in the connection string defined in sql.config.
Currently the PPJ Framework supports the following parameters:
| DBP_BRAND | Returns the value defined in sql.config for the brand attribute. |
| DBP_VERSION | Returns the value defined in sql.config for the version attribute. |
| DBP_LOCKWAITTIMEOUT | Returns/Sets the timeout value. |
| DBP_AUTOCOMMIT | Turns on/off autocommit mode. |
| DBP_ISOLEVEL | Returns/Sets the isolation level string. |
| DBP_PRESERVE | Turns on/off result set mode. |
Any other parameter is not supported. At runtime, if the application uses an unsupported parameter, a warning will be logged in the output window (if debugging) and in the log file if the application is started with the /log startup argument.
Verify the Effective Behavior
This is a historical supported subset. Check the installed API and the diagnostic output for each parameter used by the source application. Setting a parameter without an error is not enough: verify timeout, isolation, autocommit, and result-set behavior at the database.
Provider brand and version values come from configuration and should not be treated as a live capability probe. Lock-wait timeout, command timeout, and connection timeout can be distinct provider concepts.