IDMS

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

Hi Tarig,

   The parameters for the ODBC SQLDriverConnect() function for Server r17 can be found at the following DocOps location:   SQLDriverConnect Connection String Format - CA IDMS - 19.0 - CA Technologies Documentation 

Dave

I was able to validate that my key's for the attributes are correct but I am still getting the error. Is there a way to expand the trace message

<BuildOid(): bad parameters> 16:54:10.590 P:00000B20 T:00000398 parms = 000000009535B128>

and

CCI9037 Invalid PLIST specified

It looks like the problem is with the invocation of CCI/PC, which happens under the covers when the CCI Communications protocol is used (which is triggered by the presence of the CCINAME parm) .   Have you specified the CCINAME parm?  If so, have you provided the CCIPORT parm?   Note that if you want to use the 'IDMS' (Wire Protocol) communications protocol (the preferred comm protocol), then you would omit those 2 parms in favor of the HOST and PORT parameters.  I'd need to see a full trace to further assist you.   Maybe you should just open a support case if this continues to be problematic for you.