Page 2 of 2
Posted: Tue Jun 16, 2009 11:07 pm
by ray.wurlod
Actually it's not what I said. What I really said is in the words - that I suspect there is a problem establishing login credentials, setting private (manual) transaction handling, or some other connection option.
Posted: Wed Jun 17, 2009 5:47 am
by sjfearnside
Did you try the change to your odbc.ini file I suggested? 'Try setting the 'Location=' parameter in the odbc.ini file to the DB name => DB2DSNQ ...'
Posted: Wed Jun 17, 2009 7:08 am
by chulett
Didn't mean that either one of you actually said that. It just seems to me that we're already well past the point where this should have been handed off to support or at least have them involved as well.
Posted: Tue Jun 23, 2009 2:36 pm
by sjfearnside
Was there a solution found for this problem?
Posted: Fri Jul 28, 2017 10:04 am
by anguila09
Today I saw the same problem.
I did a run with a harcod value instead of the parameter and it worked but did not take the parameters indicated as ?