HP3000-L Archives

May 1995, Week 3

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:
Doug Myers <[log in to unmask]>
Reply To:
Doug Myers <[log in to unmask]>
Date:
Sat, 20 May 1995 00:08:14 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
Martin Knapp ([log in to unmask]) wrote:
: Luc Sierens wrote:
 
: >The thing WE are worried about is: what locking level is used by
: >Powerbuilder using Image/SQL? Would it coexist happily with BBXL
: >programs locking at item level? Anyone got experience with this?
 
: The first thing you need to be aware of is that while you are still
: on MPE/iX 4.0 you are most likely to be using ALLBASE "F" as the
: IMAGE/SQL interface, and in this case there is only one kind of
: locking: a full lock on the entire dataset.
 
: If you are going to get into this seriously, I would recommend
: upgrading to MPE/iX 5.0 before going any further.
 
Martin is correct that the "F0" version of Image/SQL only supports
dataset level locking.  But even if you get up on MPE/iX 5.0, you
will still get only the F0.26 version of Image/SQL.  Image/SQL
supports predicate level locking in version G0.05 which is available
from the response center as general release patch ATCHX36.  This
patch can be installed on either MPE/iX 4.0 or 5.0.  However, if
you want to run this on 4.0, you will also need a Turbo/Image patch
TIXGXW8.  In general, it is still a good idea to upgrade to 5.0.
 
Doug Myers
Database Lab
Commercial Systems Division
Hewlett-Packard

ATOM RSS1 RSS2