AnsweredAssumed Answered

What is the correct attributes for R17 ODBC dsnles connection string

Question asked by Tarig on Aug 10, 2017
Latest reply on Aug 11, 2017 by dilda02

I have a connection string with the following attributes for ODBC R16

 

driver=CA-IDMS;UID=*****;PWD=*****;DICT=****;NODE=********;server=*****.*****.com;port=1202

 

This works for R16 but when I switch the driver to the R17 I get a invalid plist error

driver=CA IDMS;UID=*****;PWD=*****;DICT=****;NODE=********;server=*****.*****.com;port=1202

The following is from a trace.

 

16:54:10.590 P:00000B20 T:00000398 <CciInit(IDMS00000B2000000400)
16:54:10.590 P:00000B20 T:00000398 LockTcp()
16:54:10.590 P:00000B20 T:00000398 LockTcp() exit
16:54:10.590 P:00000B20 T:00000398 BuildOid()
16:54:10.590 P:00000B20 T:00000398 <BuildOid(): bad parameters>
16:54:10.590 P:00000B20 T:00000398 parms = 000000009535B128>
16:54:10.590 P:00000B20 T:00000398 UnlockTcp()
16:54:10.590 P:00000B20 T:00000398 PostError(000000D89535B160): SysErrP = 20 Host = 0 PC = 84 Detail = 0
16:54:10.590 P:00000B20 T:00000398 PostError: CCI9037 Invalid PLIST specified
16:54:10.590 P:00000B20 T:00000398 <CciInit(IDMS00000B2000000400): Error>

 

I would like to have my .net applications run in 64 bit mode without reliance on the ODBC admin

Outcomes