HP3000-L Archives

May 1996, Week 1

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:
bob mcgregor <[log in to unmask]>
Reply To:
bob mcgregor <[log in to unmask]>
Date:
Thu, 2 May 1996 11:48:53 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (17 lines)
Thanks for the responses to our QTP Problem.  We detemined that the
process was performing a SET LOCK FILE REQUEST which was locking the
sets for the duration of the request.  We reviewed the options and
the only one that seems more reasonable is SET LOCK FILE UPDATE.  We
contacted Cognos and basically got no assistance as to the
implications of doing this.  In the manual it indicates that if the
checksum determines the record has been changed that transaction is
bit bucketed and the process stops.  Are there any other
implications of the set lock file update that would warrent against
using it?
 
We are also assuming that the above potential of changed records
will be minimal since QTP will re-read and update in one logical
transaction...correct assumption???
 
Thanks Bob

ATOM RSS1 RSS2