sql default schema

Hello,

when using embedded SQL in JVM-Cobol I do have the problem that most of the existing Cobolsources (> 8000) do not have the "FullQualified"  Tablename in the FROM Clause of their SQL-Statements.

With "native" Cobol it takes the username as the default Schema Qualifier. And if this is not sufficent it is possible to set QUALIFIER (as an SQL-Compiler Option).

This is not working with managed Cobol anymore. 

I do want to avoid the need to change all SQL-Statements to fully qualify the tablename. 

Does anybody have the same problem and if yes .... maybe a solution ?

Kind regards

Michael

Parents
  • Hi Michael,

    I spoke to development regarding this and for managed JVM code the connection properties are not controlled by OpenESQL but need to be set within the connection definition itself.

    Using ‘schemaName=x;’ in the connection URL works with Simple-JNDI data sources, We have tested this configuration in-house.

    Looking at the JBoss AS 7 docs it looks as though JBoss data sources have a very restricted set of properties that you can set, so this may not be possible as a simple ‘pass through’ property.

    We did notice a “new-connection-sql”  tag in www.ironjacamar.org/.../datasources_1_0.xsd , where you can pass off commands to the DBMS vendor before giving the connection to the application.

    That may help, if this cannot be set-up as a connection attribute/property (as you are trying to do now)

    Question: have you tried to use this same connection from a Java application instead of COBOL?

    If the same problem occurred then that would indicate that this was a JBoss problem instead of an OpenESQL issue.

    We would then recommend that you contact the folks at JBoss to see what they recommend.

    Thanks.

Reply
  • Hi Michael,

    I spoke to development regarding this and for managed JVM code the connection properties are not controlled by OpenESQL but need to be set within the connection definition itself.

    Using ‘schemaName=x;’ in the connection URL works with Simple-JNDI data sources, We have tested this configuration in-house.

    Looking at the JBoss AS 7 docs it looks as though JBoss data sources have a very restricted set of properties that you can set, so this may not be possible as a simple ‘pass through’ property.

    We did notice a “new-connection-sql”  tag in www.ironjacamar.org/.../datasources_1_0.xsd , where you can pass off commands to the DBMS vendor before giving the connection to the application.

    That may help, if this cannot be set-up as a connection attribute/property (as you are trying to do now)

    Question: have you tried to use this same connection from a Java application instead of COBOL?

    If the same problem occurred then that would indicate that this was a JBoss problem instead of an OpenESQL issue.

    We would then recommend that you contact the folks at JBoss to see what they recommend.

    Thanks.

Children
No Data