I have problem with bind process when i m compliing my test program the plan is binding... however if i take the same producation version its not binding... and the program names are same in test and producation
DSNT252I -DBST DSNTBCM1 BIND OPTIONS FOR PLAN trybb617
ACTION REPLACE RETAIN
DSNT253I -DBST DSNTBCM1 BIND OPTIONS FOR PLAN trybb617
DSNT200I -DBST BIND FOR PLAN trybb617 SUCCESSFUL
DSNX200I -DBST BIND SQL ERROR
USING DB23 AUTHORITY
DSNT201I -DBST BIND FOR PLAN trybb617 NOT SUCCESSFUL
Joined: 14 Oct 2005 Posts: 1188 Location: Bangalore,India
Its Seems the problem with the program as -401 states
THE OPERANDS OF AN ARITHMETIC OR COMPARISON OPERATION ARE NOT COMPARABLE
An arithmetic operation appearing within the SQL statement contains a mixture of numeric and non-numeric operands, or the operands of a comparison operation are not compatible.
One reason for this error is that a field procedure exists on one of the columns. If one column of arithmetic or comparison operation is defined with a field procedure, other columns in the operation must be defined with the same field procedure.
The statement cannot be executed.
Please double check that u are using Prod version & correct Libs
u are rigth my test table has a different struct means i had to change one numeric variable to character..... however i had given the new dclgen override as well..however i dint realise in my sql query i m comparing character variable to comp-3 variable and than fetching the row so i think the bind is not successful.... with Ekta's help i could find this...
Joined: 05 Jun 2009 Posts: 185 Location: Planet Earth
If i am understanding it right, do u mean to say your table structure is different in test and production environments ??? If yes, this should not be the case I suppose. Consider discussing with your site support people to understand why is it so, as this can cause repeated mistake.
We are in the processor of changing our table variable to char.. rigth now in producation it is numeric we want to implement it as char in producation after our testing is over.... so this problem.. our db2 tables are uploaded everday so its impossible to upload test tables everday so the way we test is we run our test program in test envi and prodcaution in test so the input data is same and than we match our files..