HP3000-L Archives

June 1999, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Ken Vickers <[log in to unmask]>
Reply To:
Ken Vickers <[log in to unmask]>
Date:
Wed, 23 Jun 1999 18:39:31 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (68 lines)
Sorry folks I should have put the answer to the list,
but the answer to Leonard's problem was that if you try to do an OPEN CURSOR
with KEEP CURSOR WITH NOLOCKS it fails if any tables are really TurboIMAGE
datasets!

Ken Vickers

LINKWAY Development and Support
__________________________________
Computing Solutions Limited
International Toll Free 00 800 00 3000 00
Tel. +44 1905 794400
Fax. +44 1905 794464
mailto:[log in to unmask]
http://www.csllink.com
__________________________________

-----Original Message-----
From: Gary L. Biggs <[log in to unmask]>
To: [log in to unmask] <[log in to unmask]>
Date: 23 June 1999 17:39
Subject: Re: Allbase DBERR 13502 help requested


>I'm not familiar with the PARTICULAR error message, but, if you open cursor
>is attempting to lock BOTH the ALLBASE and IMAGE/SQL tables in any manner
or
>fashion, your OPEN will fail. A single transaction cannot span both ALLBASE
>and IMAGE/SQL environments because of the lack of lock coordination
>(deadlock detection) between the 2 products. You can lock ALLBASE tables or
>IMAGE/SQL
>tables but not both. This is one of the challenges of this technology!
>
>
>
>At 10:34 AM 6/23/99 -0400, you wrote:
>><<Command not allowed on TurboIMAGE table.  (DBERR 13502)  >>
>>
>>In a COBOL program, the user is attempting and OPEN CURSOR and gets the
>above error.
>>The SELECT that is embedded in the CURSOR is selecting several columns
>from three
>>tables, one a native Allbase table and two TurboImage attached datasets
>(tables). The
>>columns are defined with aliases.
>>
>>Why are we getting this error? Is OPEN CURSOR not allowed when a
>TurboImage dataset
>>(table) is involved? Is the error caused because of the JOIN of a native
>Allbase
>>table with the TurboImage tables? Is the error caused by the use of
aliases?
>>
>>Many thanks.
>>========================
>>Leonard S. Berkowitz
>>mailto:[log in to unmask]
>>phone: (617) 972-9400 ext. 3250
>>fax:   (617) 923-5555
>>
>Gary L. Biggs, N5TTO
>[log in to unmask]
>Interex SIG Allbase Chair, 1999 HamCom Program Chair
>
>"Abandon all hope, Ye who Inter(net) here" --
>Dante, over the portal(router) to Hell
>

ATOM RSS1 RSS2