Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

At 21 MAY 1998 11:24:24AM Paxton Scott wrote:

I need to learn about handleing indexes in runtime….

I applied an upgrade with some dictionary additions, so as I understand the upgrade deployment, it copies the whole dictionary, not just specific records. Therefore, if the applied dictionary's indexes are set different from the existing runtime, it is clobbered.

The case I have now, is a runtime that claims to have no indexes (I temporarly use a developement oengine to look around) but, will not let me add any indexes. When I attempt to add indexes, it says it is missing a file (I assume the Bang file) and won't proceed althouogh, it does set field 6 in the dictionary record to 1. It claims the missing file has a date that is a month or so old.

Can I add indexes to a remote runtime using the upgrade process?

How can I add dictionary records to a remote runtime without corrupting indexes?

Thanks, Paxton

I need to understand the system better to untangle it


At 21 MAY 1998 11:04PM Jim Morgan wrote:

I have faced this problem, with deploying Arev upgrades to runtime users across the country. I solved it by including a table called DICTIONARY_MODS (which has a compound key of tablename*fieldname) and including the code below in my upgrade program. Obviously, you need to attach and detach volumes for it to work. I create the records in DICTIONARY_MODS by:

TCL

COPY DICT.tablename fieldname TO:(DICTIONARY_MODS tablename*fieldname

Also, I have used this same code block to create Btree and Crossref indexes by ensuring that the value of field 6 is the dict is "1".

 PERFORM "SELECT DICTIONARY_MODS (S)"
 IF @RECCOUNT THEN
    NUM=@RECCOUNT
    SLIST=NULL$
    FOR J=1 TO NUM
       READNEXT SKEY THEN
          SLIST=SKEY
       END
    NEXT
    FOR J=1 TO NUM
       SKEY =SLIST
       DKEY =FIELD( SKEY , "*" , 2 )
       DFILE=DICT." : FIELD( SKEY , "*" , 1)
       CMD  =RECORDCOPY DICTIONARY_MODS " :  SKEY
       CMD  := " TO: (" : DFILE : SPACE(1)
       CMD  := DKEY : " (OS)"
       PERFORM CMD
    NEXT
 END

At 26 MAY 1998 07:29AM Oystein Reigem wrote:

Jim,

Did that solve Paxton's problems with the indexes??

- Oystein -


At 26 MAY 1998 03:28PM Paxton Scott wrote:

Yes I have a system in place to update dictionary records in AREV. I guess I was asking for confirmation that setting indexing on my development system and copying the dictionary record to the runtime system would in fact cause the runtime system to build the indexes. I think we issued the TCL index command to do that in arev.

Since we don't normally have the tools in OI runtime, I was just checking to understand the correct method of installing an index in an OI runtime. I gather from your comments that all I have to do is insert the dictonary record of the indexed field.


At 28 MAY 1998 07:38AM Cameron Purdy wrote:

Paxton,

I applied an upgrade with some dictionary additions, so as I understand the upgrade deployment, it copies the whole dictionary, not just specific records. Therefore, if the applied dictionary's indexes are set different from the existing runtime, it is clobbered.

If you deploy just the modified dictionary items, then the indexes will be created or removed as necessary in the runtime.

Cameron Purdy

info@revelation.com


At 30 MAY 1998 03:08PM Paxton Scott wrote:

I guess I missed how to select specific dictionary records for deployment. I was under the impression it was the whole dictionary file that had to be deployed.

Is there a form for selecting specific records to be deployed or do I need to develop that myself?


At 01 JUN 1998 08:05AM Cameron Purdy wrote:

Paxton,

I guess I missed how to select specific dictionary records for deployment. I was under the impression it was the whole dictionary file that had to be deployed. Is there a form for selecting specific records to be deployed or do I need to develop that myself?

They are DBColumn entities. You should just be able to select them for an RDK upgrade view.

Cameron Purdy

info@revelation.com


At 01 JUN 1998 08:05AM Cameron Purdy wrote:

Paxton,

I guess I missed how to select specific dictionary records for deployment. I was under the impression it was the whole dictionary file that had to be deployed. Is there a form for selecting specific records to be deployed or do I need to develop that myself?

They are DBColumn entities. You should just be able to select them for an RDK upgrade view.

Cameron Purdy

info@revelation.com


At 05 JUN 1998 12:03AM Jim Morgan wrote:

Oystein

Sorry I've been offline for a couple of weeks.

He hasn't said yes/no.

I know I was surprised at how well the technique works in Arev. Until I stumbled across it while looking to the solution to a completely different problem, I had used code that involved file copy of "dummy" to !datafile where I had created dummy by creating indexes on a development system with the data file empty of records andf then copying !datafile to dummy. It was messy to say the least.

Jim

View this thread on the Works forum...

  • third_party_content/community/commentary/forums_works/a07041c0b8461f858525660b0054a1d0.txt
  • Last modified: 2023/12/30 11:57
  • by 127.0.0.1