PM72610: XQE-DAT-0001 DATA SOURCE ADAPTER ERROR ENABLING DQM WITH PARAMETER MAPS

APAR status

• Closed as suggestion for future release.

Error description

• While creating a package using parameter maps, and enabling
  dynamic query mode, the following error message is received:
             ??
                       ??Error :
                                 ??XQE-DAT-0001 Data source
  adapter error:
  ??"PRODUCT.PRODUCT_NUMBER" is not valid in the context where it
  is used..  ??SQLCODE=-206, SQLSTATE=42703, DRIVER=3.53.95
  ????This issue does not occur, if you remove usage of parameter
  maps, or without DQM
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• The Cognos software is behaving as designed.
  
  The problem is not related to parameter mapping. The following d
  efault SQL in the Go Sales FM model (which was used for the test
  case associated with this APAR) will execute successfully in bot
  h DQM (dynamic query mode) and CQM (compatible query mode):
  
  "Select * from [Go Sales].PRODUCT"
  
  However, if the FM expression is modified in either of the follo
  wing ways (the first one is what was done in the testcase) then
  an error will be encountered in both DQM and CQM.:
  
  1) Select  * from  [Go Sales].PRODUCT where PRODUCT_NUMBER=#$PAR
  1{'SRC'}#
  
  2) Select   * from  [Go Sales].PRODUCT where PRODUCT_NUMBER = 11
  10
  
  Error message:  "PRODUCT.PRODUCT_NUMBER" is not valid in the con
  text mean could not select GODB0510.PRODUCT.PRODUCT_NUMBER from
  GOSL0510.PRODUCT table.
  
  Note the following section from the DB2 documentation:
  +++++
  When qualifying a column with the exposed table name form of a t
  able designator, either the qualified or unqualified form of the
   exposed table name can be used. However, the qualifier used and
   the table used must be the same after fully qualifying the tabl
  e name or view name and the table designator
  +++++
  
  When the user does not qualify the column "PRODUCT.PRODUCT_NUMBE
  R",  DB2 will qualify it using CURRENT SQLID. Therefore if the u
  ser is using GODB0510 as the user ID to connect ot DB2,then the
  column will be qualified as "GODB0510.PRODUCT.PRODUCT_NUMBER".
  
  Note that the DB2 standard also specifies that if the table does
  n't have a correlation name, the column should be qualified with
   the exposed table name, which is the qualified name if it is in
  deed qualified.
  
  The issue associated with this APAR will not be encountered unle
  ss one is modifying the default SQL in FM, but if modifying that
   SQL is required then the proper solution to achieve the desired
   results in DQM is one of the following:
  
  1.   Add a correlation name:
   Select   * from  [Go Sales].PRODUCT PRODUCT where PRODUCT_NUMBE
  R = #$PAR1{'SRC'}#
  
  2.  Qualify the column:
  Select GOSL0510.PRODUCT.PRODUCT_NUMBER, .... from [Go Sales].PRO
  DUCT  where GOSL0510.PRODUCT.PRODUCT_NUMBER = #$PAR1{'SRC'}#
  
  ==== Yan, Tracy (H.) on 18 September 2012 15:16:03 ====
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels