Version: II 2.6/0305 (hpb.us5/00)
OS: HP-UX 11.11

We have an abf application that does session switching through an esqlc
procedure. When it tries to connect to a vnode that has a 6.4
installation on the other end the connection fails. From isql or sql
command prompt there is no problem connecting to a 6.4 installation from
2.6 through the same vnode. Is this a feature or a bug?

The sqlcode is -39100 (which has no meaningful description).

The E_ error message is: E_US0022 Either the flag format or one of the
flags is incorrect, or the parameters are not in proper order.

The application logs certain data to a log file among which is the
connect string, so I know the connect string is in the right order. If
we change the vnode definition to point to a 2.6 database there is no error.

Thanks

Dennis
d underscore roesler at agilent dot com

At 10:36 AM -0500 3/9/2005, Dennis Roesler wrote:
I seem to recall running into this back when OI 1.2 was new. I suspect
it's sort-of a feature. What's doing the connection, ABF or esqlc?

Our situation was that since there was no ABF session switching in 6.4,
the app called an ESQLC procedure that did the switching. This broke
when 1.2 came along. We changed the app to use the ABF supplied features
for session switching and that made it work, so we never bothered to
figure out what was going on.

Karl

Karl & Betty Schendel wrote:
Yes :-). An ABF application is calling an esqlc procedure that is
defined in a library linked with the link-options functionality.

We are doing this where possible in other places in the abf applications.

I was just curious if there was a known reason why a connect would work
in isql/sql but not in esqlc.

Dennis