Topic
  • 7 replies
  • Latest Post - ‏2013-05-10T19:17:30Z by krmilligan
SystemAdmin
SystemAdmin
3129 Posts

Pinned topic ODBC & CURRENT FUNCTION PATH Parameter

‏2007-07-18T15:11:51Z |
Hi All,

I'm ODBC'ing to an V5R3 iSeries.
I need to set the CURRENTFUNCTIONPATH parameter inside the connection string, but no effect is shown.

Clue, anyone?

Thanks,
Eden.
Updated on 2007-08-06T15:22:06Z at 2007-08-06T15:22:06Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    3129 Posts

    Re: ODBC & CURRENT FUNCTION PATH Parameter

    ‏2007-07-31T21:45:59Z  
    Which ODBC driver are you using? I don't recall that CURRENTFUNCTIONPATH is a
    supported connection keyword with the iSeries Access for ODBC driver.

    edeniko@netvision.net.il wrote:
    > Hi All,
    >
    > I'm ODBC'ing to an V5R3 iSeries.
    > I need to set the CURRENTFUNCTIONPATH parameter inside the connection string, but no effect is shown.
    >
    > Clue, anyone?
    >
    > Thanks,
    > Eden.
  • SystemAdmin
    SystemAdmin
    3129 Posts

    Re: ODBC & CURRENT FUNCTION PATH Parameter

    ‏2007-08-01T07:32:09Z  
    Which ODBC driver are you using? I don't recall that CURRENTFUNCTIONPATH is a
    supported connection keyword with the iSeries Access for ODBC driver.

    edeniko@netvision.net.il wrote:
    > Hi All,
    >
    > I'm ODBC'ing to an V5R3 iSeries.
    > I need to set the CURRENTFUNCTIONPATH parameter inside the connection string, but no effect is shown.
    >
    > Clue, anyone?
    >
    > Thanks,
    > Eden.
    Hi Kent,

    I'm using Client Access V5R4 Driver.
    You are correct, I didn't find any documented keyword to set the "current function path".

    Any alternative / Undocumented :-) feature?

    Thanks,
    Eden.
  • SystemAdmin
    SystemAdmin
    3129 Posts

    Re: ODBC & CURRENT FUNCTION PATH Parameter

    ‏2007-08-02T13:32:38Z  
    Hi Kent,

    I'm using Client Access V5R4 Driver.
    You are correct, I didn't find any documented keyword to set the "current function path".

    Any alternative / Undocumented :-) feature?

    Thanks,
    Eden.
    So I take it you don't want to execute the Set Path SQL statement in your
    application?

    What values are you specifying for the DefaultLibraries or Naming connection
    properties?
    edeniko@netvision.net.il wrote:
    > Hi Kent,
    >
    > I'm using Client Access V5R4 Driver.
    > You are correct, I didn't find any documented keyword to set the "current function path".
    >
    > Any alternative / Undocumented :-) feature?
    >
    > Thanks,
    > Eden.
  • SystemAdmin
    SystemAdmin
    3129 Posts

    Re: ODBC & CURRENT FUNCTION PATH Parameter

    ‏2007-08-05T12:13:32Z  
    So I take it you don't want to execute the Set Path SQL statement in your
    application?

    What values are you specifying for the DefaultLibraries or Naming connection
    properties?
    edeniko@netvision.net.il wrote:
    > Hi Kent,
    >
    > I'm using Client Access V5R4 Driver.
    > You are correct, I didn't find any documented keyword to set the "current function path".
    >
    > Any alternative / Undocumented :-) feature?
    >
    > Thanks,
    > Eden.
    True, I can't perform a "set current function path" due to application issues.

    DefaultLibraries is left blank (As far as I understand it's a diffrent attribute then "Current Function Path").
    Also, I've never used "Naming connection" attribute.
  • SystemAdmin
    SystemAdmin
    3129 Posts

    Re: ODBC & CURRENT FUNCTION PATH Parameter

    ‏2007-08-06T15:22:06Z  
    True, I can't perform a "set current function path" due to application issues.

    DefaultLibraries is left blank (As far as I understand it's a diffrent attribute then "Current Function Path").
    Also, I've never used "Naming connection" attribute.

    Do you use unqualified table & view references in your application? If so, do
    your UDFs and tables/views reside in the same schema?
    edeniko@netvision.net.il wrote:
    > True, I can't perform a "set current function path" due to application issues.
    >
    > DefaultLibraries is left blank (As far as I understand it's a diffrent attribute then "Current Function Path").
    > Also, I've never used "Naming connection" attribute.
    >
    >
  • bluish
    bluish
    19 Posts

    Re: ODBC & CURRENT FUNCTION PATH Parameter

    ‏2013-05-10T12:22:21Z  

    Do you use unqualified table & view references in your application? If so, do
    your UDFs and tables/views reside in the same schema?
    edeniko@netvision.net.il wrote:
    > True, I can't perform a "set current function path" due to application issues.
    >
    > DefaultLibraries is left blank (As far as I understand it's a diffrent attribute then "Current Function Path").
    > Also, I've never used "Naming connection" attribute.
    >
    >

    Hello, I have the same problem.

    With ODBC I can specify current schema with DBQ keyword.. but how can I specify current path?

    Without this I must qualify every reference to stored procedures or functions in SQL statements.

    Many thanks!

  • krmilligan
    krmilligan
    450 Posts

    Re: ODBC & CURRENT FUNCTION PATH Parameter

    ‏2013-05-10T19:17:30Z  
    • bluish
    • ‏2013-05-10T12:22:21Z

    Hello, I have the same problem.

    With ODBC I can specify current schema with DBQ keyword.. but how can I specify current path?

    Without this I must qualify every reference to stored procedures or functions in SQL statements.

    Many thanks!

    What value are using for DBQ keyword?  What naming mode are you using *SYS or *SQL?

     

    This article explains how SQL Path is set by default:

    http://www.ibm.com/developerworks/ibmi/library/i-system_sql2/index.html