v16.0.0.2419

The use of the InitString connection parameters is one of the recommended methods of implementing OEM authentication, but except in the simplest scenarios there seem to be issues.

Say my OEM connection key is

CONNECTION_AUTHENTICATION='Company=MyCo;Application=MyApp;Signature=000fa55157edbxxxxxxxxxxxxxx'

If I have an InitString like this:

InitString="SET TEMPORARY OPTION CONNECTION_AUTHENTICATION='Company=MyCo;Application=MyApp;Signature=000fa55157edbxxxxxxxxxxxxxx';" 

it works fine and I see the details showing in Sybase Central under Connection | Properties |Extended Information.

InitString seems quite happy to execute multiple commands eg

InitString="CREATE VARIABLE MyTest char(4);set MyTest = 'Blah';"

But if other commands are combined with setting the CONNECTION_AUTHENTICATION, then the CONNECTION_AUTHENTICATION fails. Commands before the SET TEMPORARY OPTION command work, even though the SET doesn't. Any commands after the SET don't get executed ie

InitString="CREATE VARIABLE MyTest char(4);set MyTest = 'Blah'; SET TEMPORARY OPTION CONNECTION_AUTHENTICATION='Company=MyCo;Application=MyApp;Signature=000fa55157edbxxxxxxxxxxxxxx';"

successfully creates and populates the variable but the SET OPTION fails. With:

InitString="SET TEMPORARY OPTION CONNECTION_AUTHENTICATION='Company=MyCo;Application=MyApp;Signature=000fa55157edbxxxxxxxxxxxxxx';CREATE VARIABLE MyTest char(4);set MyTest = 'Blah'; "

the variable isn't created, nor does the SET OPTION work.