The following guidelines are helpful when using the
EDAPARMS file.
- Assign an ERRNUM if an application-specific error code is
desired for all server errors that cannot be mapped to the local Db2
subsystem error code set.
- Assign an EDASERVER for the default destination for requests
containing partially-qualified table names (two-part names) to be
a specific server. If EDASERVER is omitted, the local Db2 subsystem
is the default destination for requests containing partially-qualified
table names. When an EDASERVER is assigned, it can be overridden by
using an explicit SQL CONNECT TO verb to connect to the desired
server for partially-qualified table names. The EDASERVER keyword
is for default, unresolved destinations to assign to requests containing
partially-qualified table names. For more information, see Connecting to Multiple Servers.
- Assign WORKTABLEs if you have already assigned an EDASERVER,
but want to send requests containing specific partially-qualified
table names to the local Db2 subsystem. WORKTABLEs can be product-specific
partially-qualified table names that reside in the local Db2 subsystem
from a product installation. Essentially, the WORKTABLE keyword
overrides the effects of an EDASERVER assignment for partially-qualified
table names for product-specific tables. You can assign a WORKTABLE
without an EDASERVER assignment present. However, this is not necessary,
as the default destination for partially-qualified tables is the
local Db2 subsystem.
- To allocate the EDAPARMS file when using the Extender for Db2,
add the following statement to the client CLIST
ALLOC F(EDAPARMS) DA('qualif.EDAPARMS') SHR
or
add the following statement to the client JCL:
//EDAPARMS DD DSN=qualif.EDAPARMS,DISP=SHR