Oninit cdi / Archive
Talk to an expert →

Re: EGL support for ESQL/C?

Posted in 2005

Topics: Connectivity: ESQL/C, 4GL & Embedded SQL

malc_p@btinternet.com — — source: Usenet: comp.databases.informix

Ahem. Back to the subject.... I had a reply from IBM (good quick response, very satisfying) as follows: "The limitation you seen in the conversion guide are relating to the conversion tool itself, EGL can support esql/c functions with some limitations. when you have a 4GL program that calls ESQL/C functions then there is a likely chance that you have a connection sharing happening between 4GL and ESQL/C ... if that is the case then it is NOT SUPPORTED IN EGL. EGL can still call ESQL/C functions that are in native shared library at runtime, but ESQL/C functions have to have its own connection handle to the database, connection handle used by EGL cannot be used." So we'll be ok as the cursors in our ESQL/C code are self contained. So how do I go about getting a change request in for the following line in the conversion guide, from: "I4GL programs that call ESQL/C are not supported". to: "I4GL programs that call ESQL/C are supported under the following conditions......". Cheers Malc

↪ replying to malc_p@btinternet.com
June C. Hunt — — source: Usenet: comp.databases.informix

<malc_p@btinternet.com> wrote: > Ahem. Back to the subject.... > I had a reply from IBM (good quick response, very satisfying) as > follows: > > "The limitation you seen in the conversion guide are relating to the > conversion tool itself, EGL can support esql/c functions with some > limitations. > when you have a 4GL program that calls ESQL/C functions then there is > a likely chance that you have a connection sharing happening between > 4GL and ESQL/C ... if that is the case then it is NOT SUPPORTED IN EGL. > EGL can still call ESQL/C functions that are in native shared library > at runtime, but ESQL/C functions have to have its own connection > handle to the database, connection handle used by EGL cannot be used." > > So we'll be ok as the cursors in our ESQL/C code are self contained. > > So how do I go about getting a change request in for the following line > in the conversion guide, from: > "I4GL programs that call ESQL/C are not supported". > to: > "I4GL programs that call ESQL/C are supported under the following > conditions......". Send email to docinf@us.ibm.com. I've had contact with the documentation folks a number of times and always get a quick, thoughtful response. -- June Hunt

Glossary