I think testfix is actuall for PMR 66067 and not 28556, is tha right?
I will give a test on PMR 66067 and let you know how it works out.

Please read on below for inline comments back to the developers:

-----Original Message-----
From: bungateb@au1.ibm.com <bungateb@au1.ibm.com>
To: Mark Ebling <mark.ebling@HYPERE.COM>; Luther Ananda Miller
Date: Thursday, 14 October 1999 13:13
Subject: PMR 28556

>We have had a reply from the developers on the abovementioned PMR :
>    'After some discussion with other ODBC specialists and some
>    development involvement please see SA85355.  I have attached
>    the testfix for this apar to ISTWORLD as a response to your
>    entry so you should be able to get the testfix.
>    Now more importantly I need you to point the customer to the
>    SQL Reference.  Chapter 2 talks about Language Elements.
>    Under the section labeled Tokens you will find a paragraph
>    about 'spaces'.  This very explicity states that tokens must
>    be followed by 'space'.  For this reason I would recommend to
>    the customer avoid leaving the spaces out in his application.
>    Essentially the customer is counting on the ODBC parser to
>    handle this correctly. There is no guarantee that we will
>    always handle cases like this correctly in our parser.
>    The suggestion is just to make the customer aware and
>    hopefully avoid any future problems for the customer.'

Well, if you guys are going to start quoting books, fine.
I would like to point out section 2.2 of the SQL Reference manual states:
"Tokens, other than string constants and certain delimited identifiers, must
not include a control character or
space. A control character or space can follow a token. A delimiter token, a
control character, or a space
must follow every ordinary token. If the syntax does not allow a delimiter
token to follow an ordinary token,
then a control character or a space must follow that ordinary token. The
following examples illustrate the rule
that is stated in this paragraph."

Please note that also in section 2.2, tabs, carriage returns, and linefeeds
are all defined as control characters. Thus, it is perfectly valid,
according to your SQL Reference, for a CR, LF, Tab or other control
character to follow a token, as well as a space.

You will also find this information in the V4R4 information center
7.htm so it appears to apply to UDB too, which we recently installed using

>This testfix is for file CWBODBC.DLL.
>We recommend that you take the following steps:
>1.  Rename your current copy of CWBODBC.DLL to perhaps CWBODBC.OLD,
>2.  Detach this copy of CWBODBC.DLL to your PC.
>3.  Reboot the PC
>4.  Retest the problem.
>Following is the problem description for SA85355 :
>The Client Access Express ODBC driver will incorrectly report
> the SQL statement type as 'Other' when the statement used TAB
> characters to delimit the tokens rather than spaces.  This
> results in an error when the prepared statement is executed.
> The error reported on the PC is MSGSQL0518 Prepared statement
> not found.  This is a problem in the token parsing so using
> spaces in the SQL statement rather than TABs will circumvent the
> problem.
>Please advise the outcome of this testfix.
>Many thanks..........
>(See attached file: cwbodbc.dll)
> Regards
>   Barbara Bungate
>   Software Service Specialist - IBM Support Centre
>   IBM Australia Limited, 55 Coonara Avenue, West Pennant Hills  NSW  2125.
>   Phone 61-2-9354-4514   Fax  61-2-9894- 0856



| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.