SET LOCK FILE UPDATE

Deskin, Bob Bob.Deskin@Cognos.COM
Wed, 15 Jan 2003 12:40:03 -0500


If there are no OUTPUT statements and you have SET FILE LOCK UPDATE, then
nothing gets locked. At least that's what it's supposed to do.

Bob Deskin              
PowerHouse Web Product Manager, Application Development Tools, Cognos Inc.
bob.deskin@cognos.com (613) 738-1338 ext 7268 FAX: (613) 727-1178
3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9 CANADA


-----Original Message-----
From: Leonard_Berkowitz@harvardpilgrim.org
[mailto:Leonard_Berkowitz@harvardpilgrim.org]
Sent: Wednesday, January 15, 2003 12:10 PM
To: powerh-l@lists.swau.edu
Subject: SET LOCK FILE UPDATE


MPE/iX 6.5; PowerHouse 8.19C

>From the manual:

SET LOCK FILE

"Individual locks are applied for each dataset involved. Datasets not
mentioned are not locked."

UPDATE

"The SET LOCK UPDATE statement specifies that locking is applied only for
the duration of each individual update. Since the SET LOCK UPDATE statement
lets other users change the data betwen the time the data record is read
and the time it is updated by QTP...[checksum is used to compare the images
of the record in play]"

We have a program into which SET LOCK FILE UPDATE was added several months
after being installed into production, apparently (not sufficient
documentation in the program <sigh!>) to keep the environment stable for
the duration of the RUN. In fact, there is no UPDATE verb in the program at
all.

Here is the question: Is any entity, in fact, locked since no updating
occurs?

Thanks.
--
Leonard S. Berkowitz
Perot Health Care Systems
(Harvard Pilgrim Health Care account)
voice: 617-509-1212
fax: 617-509-1955
pager: 781-226-2431

= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.swau.edu
Subscribe: "subscribe" in message body to powerh-l-request@lists.swau.edu
Unsubscribe: "unsubscribe" in message body to
powerh-l-request@lists.swau.edu
http://lists.swau.edu/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.

This message may contain privileged and/or confidential information.  If you
have received this e-mail in error or are not the intended recipient, you
may not use, copy, disseminate or distribute it; do not open any
attachments, delete it immediately from your system and notify the sender
promptly by e-mail that you have done so.  Thank you.