To set up the EDAPARMS parameter file, create a data set named qualif.EDAPARMS
* EDAPARMS file ERRNUM = errornum EDASERVER = defserver DBMS = database_type DECIMAL = decimal_point_type DATE = date_format ENABLE = trace_level WORKTABLE = worktablename . . . WORKTABLE = worktablename
where:
Denotes comments within the EDAPARMS file. An asterisk (*) in column one identifies the line as a comment. More than one comment is possible within the EDAPARMS file.
Represents an Extender for Db2 error number. The value supplied must be an integer within the range -2147483647 to 2147483648. (-901) is the default value; the Extender for Db2 uses it for server error codes that cannot be mapped to Db2 error codes. It is recommended that you assign a negative three- or four-digit number for simplicity. Avoid using a valid Db2 error code.
If more than one ERRNUM is defined, the last definition is used.
Is the default server for unresolved partially-qualified tables. Verify that this server is defined in both client and server communications configuration files. This field can be up to eight bytes in length.
If more than one EDASERVER is defined, the last definition is used.
If the EDASERVER keyword references a server not defined in the communications configuration file, an error message is produced.
There are three valid values for this parameter.
Value |
Description |
---|---|
BOTH |
Enables the Extender to access both the local database subsystem and databases residing on the server. BOTH is the default value. |
NATIVE |
Enables the Extender to access only the local database subsystem and prohibits access to databases residing on the server. |
EDA |
Enables the Extender to access only databases residing on the server and prohibits access to the local database subsystem. |
If more than one DBMS is defined, the last definition is used.
Enables you to specify whether you want a period or a comma for the decimal point in a numeric value. PERIOD is the default value. If you specify the value COMMA here, it allows either a period or a comma to be used as the decimal point.
If more than one DECIMAL is defined, the last definition is used.
Enables you to specify the output format of a date field. There are four valid values for this parameter.
Value |
Description |
---|---|
ISO |
The output format is YYYY-MM-DD. For example, the output could be: 1992-05-21. ISO is the default value. |
USA |
The output format is MM/DD/YYYY. For example, the output could be: 05/21/1992. |
EUR |
The output format is DD.MM.YYYY. For example, the output could be: 21.05.1992. |
JIS |
The output format is YYYY-MM-DD. For example, the output could be: 1992-05-21. |
If more than one DATE is defined, the last definition is used.
Enables several levels of tracing for Db2 Extender. API traces are written to DDNAME FSTRACE and all other traces are written to DDNAME QXTRACE (dynamically allocated when needed). Possible trace values are:
Value |
Description |
---|---|
MESSAGES |
Corresponds to the EDALOG file used in earlier releases. Users can record all warning and error messages originating from the server or the Extender for Db2. EDALOG is useful if a display or output of warnings and messages is desired. This trace is especially useful for Db2 application products that do not use the DSNTIAR message formatting facility. |
SQLTRACE |
Corresponds to the QXSQLTRC file used in earlier releases. Displays the SQL statement types (NATIVE or EDA). In addition, users can see how a statement string is physically prepared for dispatching. |
RDITRACE |
This is the main component trace for Db2 Extender. It shows the inputs received, the processing of SQLDA, and the proper handling of every query and its results. |
PRSTRACE |
SQL Parser output. Displays command type (for example, SELECT, INSERT, UPDATE, etc.), number of tables, and table names. |
APITRACEx |
Where x is from 1 to 9 API trace levels. It can be enabled separately for levels 1 to 9. |
Is the name of a product worktable (for example, Q.PROFILE). The Extender directs all requests referencing these worktables to Db2. More than one WORKTABLE keyword definition can exist in the EDAPARMS file. For more information on naming conventions and worktables, see Using the Extender for DB2 and SQL.
WebFOCUS | |
Feedback |