PowerSoft ODBC interface

I used Client Access ODBC Driver (32-bit).
PowerBuilder 5.0.3 and 6.0.

I executed following script:

///////////////////////////////////////////////////
String ls_SQL
DynamicStagingArea l_dsa
DynamicDescriptionArea l_dda

ls_SQL = "CALL PSAVDEPTOR(2, 129, '', '', 'DATA FIELD')"

l_dsa = SQLSA
l_dda = SQLDA

DECLARE l_proc DYNAMIC PROCEDURE FOR l_dsa;
PREPARE l_dsa FROM :ls_SQL;
DESCRIBE l_dsa INTO l_dda;
EXECUTE DYNAMIC l_proc USING DESCRIPTOR l_dda;
///////////////////////////////////////////////////

I got following error:

[     125] "[IBM][Client Access ODBC Driver (32-bit)][DB2/400 SQL]SQL0199 -
Keyword WHERE not expected. Valid tokens: <END-OF-STATEMENT>."



I tryed to find out where is my mistake.
I used ODBC Trace utility.

ODBC Trace Log showed that PowerBuilder's PowerSoft ODBC interface sends
incorrect statement in ODBC's function SQLExecDirect.It sends that statement
"CALL PSAVDEPTOR(2, 129, '', '', 'DATA FIELD') WHERE CURRENT OF
no_current_cursor\ 0"
inspite of my "CALL PSAVDEPTOR(2, 129, '', '', 'DATA FIELD')".

I think that is the main reason of the problem.

Can somebody explain me why after my statement attached this text
" WHERE CURRENT OF no_current_cursor\ 0" ?????
I need explanation from developers of PowerBuilder's PowerSoft ODBC
interface.

The slice of the ODBC Trace Log:
---
PB050           ea:d2   ENTER SQLAllocStmt
                HDBC                0x0032f8f0
                HSTMT *             0x0012df84

PB050           ea:d2   EXIT  SQLAllocStmt  with return code 0 (SQL_SUCCESS)
                HDBC                0x0032f8f0
                HSTMT *             0x0012df84 ( 0x027cc350)

PB050           ea:d2   ENTER SQLExecDirect
                HSTMT               0x027cc350
                UCHAR *             0x0177c948 [      -3] "CALL
PSAVDEPTOR(2, 129, '', '', 'DATA FIELD') WHERE CURRENT OF no_current_cursor\
0"
                SDWORD                    -3

PB050           ea:d2   EXIT  SQLExecDirect  with return code -1 (SQL_ERROR)
                HSTMT               0x027cc350
                UCHAR *             0x0177c948 [      -3] "CALL
PSAVDEPTOR(2, 129, '', '', 'DATA FIELD') WHERE CURRENT OF no_current_cursor\
0"
                SDWORD                    -3

                DIAG [37000] [IBM][Client Access ODBC Driver
(32-bit)][DB2/400 SQL]SQL0199 - Keyword WHERE not expected. Valid tokens:
<END-OF-STATEMENT>. (-199)

                DIAG [37000] [IBM][Client Access ODBC Driver
(32-bit)][DB2/400 SQL]SQL0199 - Keyword WHERE not expected. Valid tokens:
<END-OF-STATEMENT>. (-199)

PB050           ea:d2   ENTER SQLError
                HENV                0x00000000
                HDBC                0x0032f8f0
                HSTMT               0x027cc350
                UCHAR *             0x0177c8ac (NYI)
                SDWORD *            0x0012df84
                UCHAR *             0x0177caf4
                SWORD                      513
                SWORD *             0x0012df7a

PB050           ea:d2   ENTER SQLErrorW
                HENV                0x00000000
                HDBC                0x0032f8f0
                HSTMT               0x027cc350
                WCHAR *             0x0012df30 (NYI)
                SDWORD *            0x0012df84
                WCHAR *             0x0012db30
                SWORD                      512
                SWORD *             0x0012df7a

PB050           ea:d2   EXIT  SQLErrorW  with return code 0 (SQL_SUCCESS)
                HENV                0x00000000
                HDBC                0x0032f8f0
                HSTMT               0x027cc350
                WCHAR *             0x0012df30 (NYI)
                SDWORD *            0x0012df84 (-199)
                WCHAR *             0x0012db30 [     125] "[IBM][Client
Access ODBC Driver (32-bit)][DB2/400 SQL]SQL0199 "
                SWORD                      512
                SWORD *             0x0012df7a (125)

PB050           ea:d2   EXIT  SQLError  with return code 0 (SQL_SUCCESS)
                HENV                0x00000000
                HDBC                0x0032f8f0
                HSTMT               0x027cc350
                UCHAR *             0x0177c8ac (NYI)
                SDWORD *            0x0012df84 (-199)
                UCHAR *             0x0177caf4 [     125] "[IBM][Client
Access ODBC Driver (32-bit)][DB2/400 SQL]SQL0199 - Keyword WHERE not
expected. Valid tokens: <END-OF-STATEMENT>."
                SWORD                      513
                SWORD *             0x0012df7a (125)

PB050           ea:d2   ENTER SQLCancel
                HSTMT               0x027cc350

PB050           ea:d2   EXIT  SQLCancel  with return code 0 (SQL_SUCCESS)
                HSTMT               0x027cc350

PB050           ea:d2   ENTER SQLFreeStmt
                HSTMT               0x027cc350
                UWORD                        1 <SQL_DROP>

PB050           ea:d2   EXIT  SQLFreeStmt  with return code 0 (SQL_SUCCESS)
                HSTMT               0x027cc350
                UWORD                        1 <SQL_DROP>


--

Andrey Leskovoy
http://www.fuib.com/

0
Andrey
8/8/1998 9:01:11 AM
sybase.powerbuilder.database 9855 articles. 2 followers. Follow

1 Replies
542 Views

Similar Articles

[PageSpeed] 8
Get it on Google Play
Get it on Apple App Store

PowerBuilder thinks you are using a dynamic CURSOR rather than a dynamic
PROCEDURE and it bases that on the string that you are preparing.  Try changing
ls_SQL to 'EXECUTE PSAVDEPTOR(...)' rather than 'CALL PSAVDEPTOR(..)'

Jim O'Neil
Sybase Technical Support
joneil@sybase.com

Andrey Leskovoy wrote:

> I used Client Access ODBC Driver (32-bit).
> PowerBuilder 5.0.3 and 6.0.
>
> I executed following script:
>
> ///////////////////////////////////////////////////
> String ls_SQL
> DynamicStagingArea l_dsa
> DynamicDescriptionArea l_dda
>
> ls_SQL = "CALL PSAVDEPTOR(2, 129, '', '', 'DATA FIELD')"
>
> l_dsa = SQLSA
> l_dda = SQLDA
>
> DECLARE l_proc DYNAMIC PROCEDURE FOR l_dsa;
> PREPARE l_dsa FROM :ls_SQL;
> DESCRIBE l_dsa INTO l_dda;
> EXECUTE DYNAMIC l_proc USING DESCRIPTOR l_dda;
> ///////////////////////////////////////////////////
>
> I got following error:
>
> [     125] "[IBM][Client Access ODBC Driver (32-bit)][DB2/400 SQL]SQL0199 -
> Keyword WHERE not expected. Valid tokens: <END-OF-STATEMENT>."
>
> I tryed to find out where is my mistake.
> I used ODBC Trace utility.
>
> ODBC Trace Log showed that PowerBuilder's PowerSoft ODBC interface sends
> incorrect statement in ODBC's function SQLExecDirect.It sends that statement
> "CALL PSAVDEPTOR(2, 129, '', '', 'DATA FIELD') WHERE CURRENT OF
> no_current_cursor\ 0"
> inspite of my "CALL PSAVDEPTOR(2, 129, '', '', 'DATA FIELD')".
>
> I think that is the main reason of the problem.
>
> Can somebody explain me why after my statement attached this text
> " WHERE CURRENT OF no_current_cursor\ 0" ?????
> I need explanation from developers of PowerBuilder's PowerSoft ODBC
> interface.
>
> The slice of the ODBC Trace Log:
> ---
> PB050           ea:d2   ENTER SQLAllocStmt
>                 HDBC                0x0032f8f0
>                 HSTMT *             0x0012df84
>
> PB050           ea:d2   EXIT  SQLAllocStmt  with return code 0 (SQL_SUCCESS)
>                 HDBC                0x0032f8f0
>                 HSTMT *             0x0012df84 ( 0x027cc350)
>
> PB050           ea:d2   ENTER SQLExecDirect
>                 HSTMT               0x027cc350
>                 UCHAR *             0x0177c948 [      -3] "CALL
> PSAVDEPTOR(2, 129, '', '', 'DATA FIELD') WHERE CURRENT OF no_current_cursor\
> 0"
>                 SDWORD                    -3
>
> PB050           ea:d2   EXIT  SQLExecDirect  with return code -1 (SQL_ERROR)
>                 HSTMT               0x027cc350
>                 UCHAR *             0x0177c948 [      -3] "CALL
> PSAVDEPTOR(2, 129, '', '', 'DATA FIELD') WHERE CURRENT OF no_current_cursor\
> 0"
>                 SDWORD                    -3
>
>                 DIAG [37000] [IBM][Client Access ODBC Driver
> (32-bit)][DB2/400 SQL]SQL0199 - Keyword WHERE not expected. Valid tokens:
> <END-OF-STATEMENT>. (-199)
>
>                 DIAG [37000] [IBM][Client Access ODBC Driver
> (32-bit)][DB2/400 SQL]SQL0199 - Keyword WHERE not expected. Valid tokens:
> <END-OF-STATEMENT>. (-199)
>
> PB050           ea:d2   ENTER SQLError
>                 HENV                0x00000000
>                 HDBC                0x0032f8f0
>                 HSTMT               0x027cc350
>                 UCHAR *             0x0177c8ac (NYI)
>                 SDWORD *            0x0012df84
>                 UCHAR *             0x0177caf4
>                 SWORD                      513
>                 SWORD *             0x0012df7a
>
> PB050           ea:d2   ENTER SQLErrorW
>                 HENV                0x00000000
>                 HDBC                0x0032f8f0
>                 HSTMT               0x027cc350
>                 WCHAR *             0x0012df30 (NYI)
>                 SDWORD *            0x0012df84
>                 WCHAR *             0x0012db30
>                 SWORD                      512
>                 SWORD *             0x0012df7a
>
> PB050           ea:d2   EXIT  SQLErrorW  with return code 0 (SQL_SUCCESS)
>                 HENV                0x00000000
>                 HDBC                0x0032f8f0
>                 HSTMT               0x027cc350
>                 WCHAR *             0x0012df30 (NYI)
>                 SDWORD *            0x0012df84 (-199)
>                 WCHAR *             0x0012db30 [     125] "[IBM][Client
> Access ODBC Driver (32-bit)][DB2/400 SQL]SQL0199 "
>                 SWORD                      512
>                 SWORD *             0x0012df7a (125)
>
> PB050           ea:d2   EXIT  SQLError  with return code 0 (SQL_SUCCESS)
>                 HENV                0x00000000
>                 HDBC                0x0032f8f0
>                 HSTMT               0x027cc350
>                 UCHAR *             0x0177c8ac (NYI)
>                 SDWORD *            0x0012df84 (-199)
>                 UCHAR *             0x0177caf4 [     125] "[IBM][Client
> Access ODBC Driver (32-bit)][DB2/400 SQL]SQL0199 - Keyword WHERE not
> expected. Valid tokens: <END-OF-STATEMENT>."
>                 SWORD                      513
>                 SWORD *             0x0012df7a (125)
>
> PB050           ea:d2   ENTER SQLCancel
>                 HSTMT               0x027cc350
>
> PB050           ea:d2   EXIT  SQLCancel  with return code 0 (SQL_SUCCESS)
>                 HSTMT               0x027cc350
>
> PB050           ea:d2   ENTER SQLFreeStmt
>                 HSTMT               0x027cc350
>                 UWORD                        1 <SQL_DROP>
>
> PB050           ea:d2   EXIT  SQLFreeStmt  with return code 0 (SQL_SUCCESS)
>                 HSTMT               0x027cc350
>                 UWORD                        1 <SQL_DROP>
>
> --
>
> Andrey Leskovoy
> http://www.fuib.com/



0
Jim
8/17/1998 12:37:32 PM
Reply:

Similar Artilces:

Powersoft Oracle database interface
I am installing Power Builder 6.0 Desktop on Windows NT and want to install the Powersoft Oracle database interface. However, I do not see this option available in the setup program. How do I install the Oracle database interface? BP Hi B. The Desktop version only supports ODBC connections. HTH -- - Eric Aling [TeamPS], Cypres Informatisering bv, The Netherlands Eric's Home & PB Site @ http://utopia.knoware.nl/users/cypr115 B. Power <brenda@compusult.nf.ca> wrote in message kbyvkugG#GA.161@forums.powersoft.com... >I am installing Power Builder...

Powersoft Oracle database interface
I am installing Power Builder 6.0 Desktop on Windows NT and want to install the Powersoft Oracle database interface. However, I do not see this option available in the setup program. How do I install the Oracle database interface? BP Desktop version is limited to ODBC connectivity AND within ODBC to the drivers shipped with PB I hope for you that there is an oracle odbc driver shipped with powerbuilder. HTH B. Power wrote in message ... >I am installing Power Builder 6.0 Desktop on Windows NT and want to install >the Powersoft Oracle database interface. However,...

Loading powersoft database interface
I have problems trying to create a profile after installing native database drivers from PB. I get an error saying 'Unable to load the requested powersoft database interface. Please make sure both the interface and the client software are installed properly'. I was running Oracle 7.3 and Oracle 8 through oracle 8.4 client for more than 4 months now. I wanted to install the whole PB 6.5 product as I was interested in looking into powerj. Somehow something got messed and powerbuilder is unable to load the interface. I tried uninstalling and installing bothe PB6.5 and oracl...

database interfaces in powerbuilder 10
I installed powerbuilder 10 with the default configurations. When I went to connect to my microsoft sql server database, I noticed that 10 didnt have a MSS Microsoft SQL Server database interface. How do I add it? Did I miss a selection during installation? Please email back at wahidta@friedfrank.com Thanks, Tashfin Wahid As far as I know, for 10 you would use the ADO.net driver to connect to MS Sql Server. That is the way the MS is going for their database connectivity, so no native driver included. So you would create a datasource on your local machine and configure the ...

Powerbuilder and ODBC connection to Progress database
We are trying to connect an application to a Progress database. Our application is written in PB 5.04. We have version 8.3E of Progress and would like to establish an ODBC connection to our application. We are able to connect to Progress but not in Powerbuilder or through our application. Does anyone have any suggestions? Thanks, Carol Burrows DBC SMARTSoftware, Inc carol_burrows@dbcsmartsoftware.com When you cannot connect, what error do you get? Can you connect outside of PowerBuilder via ODBC using MS Query or some other tool. The newer versions of ODBC Administrat...

cannot access powerbuilder configure odbc or databases
After installing powerbuilder 5.0 on NT4 sp3 .... and then go into powerbuilder and click on configure odbc and get the infinite hourglass Could anyone tell me what the problem could be ? I've tried to uninstall (which has never been successful and i end up deleting the directories and do a regclean) and re-installing it. And i still get the same results. Dist, Can you get to the ODBC setup through the control panel? Also, try reinstalling (no need to uninstall) PB and verifying that you install all required ODBC drivers. You may also have to go to the "Native Driv...

Not Seeing ODBC Database Interface under PB10
Running under PowerBuilder 10.2.1 Build 9761. I just noticed that when I select the DB Profile button to view my installed database interfaces, a section for ODBC is not there. Under my PB9 installation, I see a node titled ODB ODBC. From there I can see my ODBC configurations. FWIW, I can run my app, and attach to an ODBC DSN just fine. Probably been running PB10 here for the last 6 months and haven't even noticed this until today (was trying to connect to one of our test db's). Can anybody point me in the right direction on this? I've looked under every n...

PowerBuilder Database Interfaces (please help)
I have been working with PowerBuilder 7.0 professional edition for awhile now and I have notice that I regulary receive the following errors: 1// DBMS ODBC is not supported in your current installation. 2// There are no database interface currently installed. I can reinstall powerbuilder and my database interface but after I open powerbuilder and create my connection and close powerbuilder again I receive the same errors. With these erors I can not connect to my data base and create data windows. Now reciently I have notice that even when I reinstall powerbuilder I will re...

PowerBuilder 6.5 issues with an ODBC connection to a Database
PowerBuilder 6.5 Build 444 Windows XP ********** ALSO SEE ATTACHMENTS ************ I am working on the project that we talked about in April. We are hoping the client will be convinced to go to PowerBuilder 10.5, but at this moment I am stuck in the 6.5 world. We are using a new database by HP in which it is a Non Stop System. It is an ODBC connection (ver. 3) with the drivers developed by HP. It is SQL '9x compliant ( ANSI SQL:99 ). After connecting I get errors when trying to retrieve a datawindow. The first time when opening the Pre- View I get data because of the ...

Problems with Powerbuilder accesing an Acces Database via ODBC
I've developed an application with PB60, under windows NT Wk. 4.0 I compiled it and tested it under WNT Wrokstation 4.0 and it worked fun. Afetr it, I re-compiled and regenerated the application under W95, and when I tried to execute the .exe file compiled, I couldn�t acces the database, and I catched this error when trying to connect the SQLCA: "DBMS ODBC is not supported in your current Instalation". Moreover, if I run the application with the "RUN" painter, it works ok! I get the parameters to connect from an .INI file, which is in the same directory that t...

[Pervasive][ODBC Client Interface][LNA][Pervasive][ODBC Engine Interface]Invalid date, time or timestamp value. error
Hi everyone, have a problem with this line of code:  thisquery = "select type as tender from dlpaid where stor = '"&istor&"' and tran = '"&itran&"' and till = '"&itill&"' and date1 = '"&right(idate, 4)&"-"&right(left(idate, 5), 2)&"-"&left(idate, 2)&"'  "set ConnRsOrig =oconnPV.execute(thisquery) This error occurs sometimes but not all the time: Refund Checking fault occurredMicrosoft OLE DB Provider for ODBC Drivers error '800...

Web resources about - PowerSoft ODBC interface - sybase.powerbuilder.database

Powersoft K Series at the Core of the 'Desert Underground' as Moontribe Collective Celebrates its 22nd ...
August 13, 2015 · Camarillo, Calif. – Before the dawn of the mainstream, there was the desert underground. The highly passionate, non-commercial ...

Powersoft K Series at the Core of the 'Desert Underground' as Moontribe Collective Celebrates its 22nd ...
Whump Sound Brings High Quality, Reliable Audio to Full Moon Desert Gatherings, Where Love for Electronic Music and Desert Atmosphere Prevails ...

Hummingbird Media (@HummingbirdBuzz) on Twitter
... Explorer. Learn more here Hummingbird Media @ HummingbirdBuzz New York, USA Public Relations for Sennheiser, Moog, BAE Audio, Neumann, Powersoft, ...

Larry Ellison - Wikipedia, the free encyclopedia
Lawrence Joseph "Larry" Ellison (born August 17, 1944 in The Bronx , New York City , New York ) is the co-founder and chief executive officer ...

Lift Vertige, root-uplifting gel - couture styling Kérastase
Lift Vertige elevates roots with subtlety, for a guaranteed “higher hair” effect, delicate softness, shine.

Future High Street Summit Leicester
An up to date list of all the networking events for the computer and IT community

Atari Legend - Legends never die!
Atari Legend : The number 1 Atari ST resource on the web

Feature: The 'complicated algorithm' of great festival sound
The festival circuit remains a vital revenue generator for audio firms, but is hardly free of challenges, as David Davies discovers.

Void powers Chase and Status' Welsh warehouse gig
Arcline system for Cardiff EDM event provided by Spartan Audio.

Defunct Audio Manufacturers - Al - audiotools.com.
Information on defunct audio equipment manufacturers with names starting with Al

Resources last updated: 12/25/2015 4:14:24 AM