How to trap the SQL error messages in BO

We are using BO 4.1.3 with DB2/MVS on mainframe.Our gateway is Sybase Direct connect.
The DB2 governer is reduced to 3 minutes of CPU time from 5 minutes recently and the time limit set in BO universe is 25 minutes. Whenever the query either crosses any of the limits we used to get a ‘Partial result’ message in BO.
I have a query which is bringing different number of rows evry time we run and not giving me ‘Partial Result’ message.We monitored this query both in BO and DB2 and found out that at DB2 the query is ending in SQL ERROR CODE -905(Resource limit has been exceeded).
I would like to trap this message and show it in BO so that the user is aware that query hasn’e brought back all the rows.

Help in this regards will be highly appreciated.


Listserv Archives (BOB member since 2002-06-25)

I am not familiar with Sybase but we have always applied the trick in NT to trace ODBC.

By doing so you get to see each SQL statement and from there you can correct.

Hope this helped.

Have a nice weekend

Maarten
__________________________________________________ Netmining NV/SA - http://www.netmining.com

mySupervisor - administrate via the web your BO users more info at http://www.mysupervisor.com __________________________________________________


Listserv Archives (BOB member since 2002-06-25)

We are using BO 4.1.3 with DB2/MVS on mainframe.Our gateway is Sybase Direct connect.
BO and DB2 and found out that at DB2 the query is ending in SQL ERROR CODE -905(Resource limit has been exceeded).
I would like to trap this message and show it in BO so that the user is aware that query hasn’e brought back all the rows.

We had a similar issue in the initial stages when we rolled out BO v4.1.3. Then we upgraded our Sybase Direct connect version and also made changes to the CPU limit and I have’nt seen that since.

-Sai


Listserv Archives (BOB member since 2002-06-25)