[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference orarep::nomahs::dbintegrator_public_public

Title:DB Integrator Public Conference
Notice:Database Integration - today! Kit/Doc info see note 36
Moderator:BROKE::ABUGOV
Created:Mon Sep 21 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1171
Total number of notes:5187

1039.0. "Bugcheck and Performance." by IB002::BERNABE () Wed Mar 27 1996 13:38

T.RTitleUserPersonal
Name
DateLines
1039.1BROKE::WHITEThu Mar 28 1996 09:4131
1039.2Only from precompiled program!!!!IB002::BERNABEThu Mar 28 1996 15:2216
1039.3BROKE::WHITEThu Mar 28 1996 16:454
1039.4Available tomorrow.IB002::BERNABEThu Mar 28 1996 17:455
1039.5Traces and codes.IB002::BERNABEFri Mar 29 1996 05:12491
1039.6BROKE::WHITEFri Mar 29 1996 11:3916
1039.7Dynamic SQL is the answer.ORAREP::IB002::BERNABETue Apr 09 1996 10:247
    Well, unfortunately COBOL does not have a DATE data type. It uses the
    equivalent to char(23).
    But the good news is that it is very easy to run dynamic SQL from
    COBOL, and it works perfectly; DBI pushes the whole condition.
    
    	Thanks a lot.
    	Miguel Bernab�.
1039.8ReadCommited from MS-Access?ORAREP::IB002::BERNABETue Apr 09 1996 10:307
    Regarding .1 -> READ COMMITED to avoid -914.
    It works fine from SQL$ or a program. But how can I force it from
    MS-Access? I have tried several ways, including passthru, but always
    failed.
    
    Thanks in advance.
    Miguel Bernab�.
1039.9BROKE::WHITETue Apr 09 1996 17:2210
At one time the answer was that you could not change the default isolation
level settings from a desktop client like ms-access.  I don't know if there
have been ease-of-use changes made to the common components to allow this.

One site I dealt with fixed this by rebinding the DB2 server packageset/plans
so that they never ran with repeatable read.  That way all requests against
that instance of the server would run under the cursor stability setting
and locking would not be an issue.

This suited their needs, but your milage may vary....
1039.10BROKE::WHITETue Apr 09 1996 17:386
Check out the published features for RDB 7 and you'll find a SQL Services
feature that allows a SQL Services Server to have an "init" procedure.  Sounds
like that would allow you to set the default transaction semantics to something
less restrictive.

Of course, you'll have to wait til RDB 7 ships before you can use it.