Quick: superfluous update records

[Deskin, Bob]

I'm assuming you're using IMAGE. It depends on your screen structure. If you
look at the standard UPDATE procedure, you'll see that it does a PUT for new
records and then later does a PUT to update. That's because IMAGE requires
master dataset records to be added before corresponding detail dataset
records (for those of you who are not MPE/iX people, we're talking IMAGE
master-detail datasets and not QUICK MASTER DETAIL files). If you change the
content of the master record while updating the details, for example from an
ITEM FINAL, then you may well do an update on the master giving you two
PUTs.

By the way, if you're adding to an IMAGE master in QTP, it automatically
does an ADD and an UPDATE when you use an OUTPUT ADD for the same reason. A
typical sequence is

OUTPUT image-detail ADD
OUTPUT image-master ADD AT key-item

Since you need the IMAGE master before you can add the details, QTP adds the
master with key values only AT START OF key-item, and then updates AT "end
of" key-item.

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: Friday, May 04, 2001 9:34 AM
To: powerh-l@lists.swau.edu
Subject: Quick: superfluous update records




HP3000; PowerHouse v. 8.19

Our major application uses Quick screens. Recently we have installed the
Bridge
product (a subset or superset of Quest's Netbase) that creates transaction
logging files. Now that we have these files, we have spent some time
analyzing
transactions.

One phenomenon that we have noticed is that there is a huge number of update
transactions. The before-image of the record is mostly spaces, with only the
key
values present. The after-image, of course, is all of the data that the user
entered.

Quite a lot of I/O overhead, I would say.

The question is: Is this S.O.P. for Quick or is there something in the
application that if forcing incomplete records to be written to the data
base
and then updated?
===================
Leonard S. Berkowitz
Perot Health Care Systems
(Harvard Pilgrim Health Care account)
voice: 617-509-1212
fax:   617-509-3737
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.