UPDATE Procedure Generation (was OpenVMS Differences Document )

[Deskin, Bob]

So my choice of program parameter keywords was too simplistic. Wouldn't be
the first time.

I did some additional playing (or testing if you're talking to my boss).
First off, the 8.xx approach is the same throughout the 8 series and is also
the same as 7.29/7.23/7.33. 7.10 is different. There is additional logic for
IMAGE databases but there is none for relational databases. Unfortunately
due to lack of time, 8.30 and 8.39 will not have anything changed for
relational (sorry Bill). We will keep that in mind for 8.4x.

What we need to do for the 8.30 project is provide the ability for 7.10
users to retain that approach to UPDATE procedure generation if they so
desire. If I have my way, that approach will not be available to any other
platforms because we don't want to confuse things. So in fact, this
discussion is only relevant to OpenVMS customers (sorry John, but feel free
to comment anyway).

I grant you that the words TOPDOWN and BOTTOMUP are too simplistic. They
weren't necessarily aimed at the declared file order, but at the implied
QUICK transaction structure. If we look only at indexed files, in 7.10 the
PUT verb sequence in most cases is in the order of the FILE statements. At
least for MASTER, PRIMARY, DETAIL, and SECONDARY. If you put a SECONDARY
before the PRIMARY, the PRIMARY is first. So really the order is MASTER,
PRIMARY, DETAIL/SECONDARY, DELETE. I didn't test any others. If you look at
the implied QUICK transaction structure with the MASTER or PRIMARY at the
top, then this is TOPDOWN or at least TOPOFSTRUCTUREFIRST (which is much too
long).

In 8.10 and 8.20 (and 7.29, 8.19, 8.29, 8.39 etc), the order is reversed.
However, within one type of file (like SECONDARY) the order is the sequence
of FILE statements (top down). So the overall order is DETAIL, SECONDARY (in
top-down order), DELETE, PRIMARY, MASTER. This is what I meant by BOTTOMUP
or at least TOPOFSTRUCTURELAST.

I have not tested SECONDARY OCCURS WITH DETAIL or DELETE OCCURS WITH and so
on.

So I need two words to describe the way we generate UPDATE procedures. They
must make sense to the OpenVMS folks and hopefully will not be used by the
rest of you.

Any ideas?

Bob Deskin              
PowerHouse Web Product Manager and Senior Product Advisor
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: Hamilton, Allison [mailto:Allison.Hamilton@Cognos.COM]
Sent: August 1, 2000 12:56 PM
To: 'Pickering, John (NORBORD)'; Hamilton, Allison
Cc: 'Powerhouse List'
Subject: RE: OpenVMS Differences Document


Yes, it is the same. I think that bottomup comes from some of the
dependencies when you have masters, they have to go first, or something. I'm
not an HP officionado any more.  When Bob returns he can probably respond
with more specifics.

-----Original Message-----
From: Pickering, John (NORBORD) [mailto:PICKERIJ@norbord.com]
Sent: Tuesday, August 01, 2000 12:41 PM
To: 'Hamilton, Allison'
Cc: 'Powerhouse List'
Subject: RE: OpenVMS Differences Document


<snip good formatnumber stuff of which I have long been jealous>

>Regarding Bottomup and Topdown - perhaps the interpretation of the
>terms is confusing and we should choose something else.  The default
>order will be the same as what exists already in 8.2x (including 8.29),
>which takes into consideration IMAGE requirements. 

Since I don't have 8.29 I don't know what the sequence is. Is it the same as
8.19?

I would call the sequence in 8.19 "topdown". If there are no Image manual
masters then the put statements in the update procedure will be generated in
the order in which the file statements appear in the Qdesign source -- from
the top (or first) of the source down to the bottom (or end) of the source
-- i.e. "Topdown". If this has not changed then I think you should indeed
think up new keywords.

Regards,
JWP
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
This list is closed, thus to post to the list, you must be a subscriber.
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
This list is closed, thus to post to the list, you must be a subscriber.
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
This list is closed, thus to post to the list, you must be a subscriber.