In Unidata (v6.x) you can issue the command BUILD.INDEX MYFILE ALL. With the
KEYWORD ALL it's builds/rebuilds all the indexes that have been created on
the file.  I would hate to have to remember that INDEX_1 is say, Customer
Name, verus a dictionary named CUST_NAME.

I would agree with others, I rarely had any need to rebuild any indexes with
Unidata, other than part of a file resizing/space considerations.

Donald Verhagen
People 2.0

 



> -----Original Message-----
> From: u2-users-boun...@listserver.u2ug.org 
> [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of 
> Bill Haskett
> Sent: Thursday, July 16, 2009 4:52 PM
> To: U2 Users List
> Subject: Re: [U2] More questions on indexing
> 
> Brad:
> 
> I've defined indexes in my files with dictionary items like 
> "INDEX_1", 
> etc.  Thus only these dictionaries are ever used for 
> indexing.  A file 
> may have 4 or 5 indexes (INDEX_1 - INDEX_4).
> 
> I wrote another program to do the indexing for a single file or an 
> entire account by executing the command...
> 
> :ACCT-INDEX  CUSTFILE  -IINDEX_
> 
> ...which will create all the indexes on the CUSTFILE.  Also, my 
> dictionary listing will show these indexes separately so it 
> looks like:
> 
> Dictionary of File: APPO                              
> 13:48:38 Jul 16 2009
> Dict Name...... Typ # Col-Heading.... Field-Def... Conversion.. Formt 
> Assoc...
> 
> @UQ             Phr                   VENDNO CLIEN
>                                       TNO DISSUE A
>                                       UTH DESCT DC
>                                       LOSED
> INDEX_1         Indx                  IF DCLOSED N            
>   18L   S
>                                       E "" THEN CL
>                                       IENTNO "R(%4
>                                       )" : UNITNO
>                                       "R(%7)" : SE
>                                       QNO "R(%7)"
> @ID             D 0   APPO                                    
>   6R    S
> PONO            D 0   PO#                                     
>   7R    S
> VENDNO          D 1   VEND#                                   
>   5R    S
> CLIENTNO        D 2   CLNT                                    
>   4R    S
> 
> 
> We don't normally rebuild indexes on UD v7.1 or v7.2.
> 
> HTH,
> 
> Bill
> 
> --------------------------------------------------------------
> ----------
> bradley.sch...@usbank.com said the following on 7/16/2009 1:18 PM:
> > Thanks, Rod. One more thing. I've written a test program to 
> simplify index 
> > creation and building. When I run it under type U or type P using 
> > BUILD.INDEX or BUILD-INDEX, it gives me the "Enter <New line> to 
> > continue..." prompt after each screen of *'s. Definitely 
> not desirable for 
> > an automated process. It doesn't do this at TCL. 
> >
> > How can I work around this? I'd rather not throw a bunch of DATA 
> > statements in there.
> >
> >
> > EXECUTE 'DELETE.INDEX LS.INV.NUM N.CONTRACT.KEY'
> > DATA 20
> > EXECUTE 'CREATE.INDEX LS.INV.NUM N.CONTRACT.KEY'
> > EXECUTE 'BUILD.INDEX LS.INV.NUM N.CONTRACT.KEY'
> >
> >
> > TIA,
> > Brad.
> >
> >   
> >> Please respond to U2 Users List
> >>
> >>  I think Oracle's indexing scheme is much more complicated that
> >> Unidata's, so I don't think you can compare the two. I do 
> rebuild some
> >> of the dynamic files on occasion to get some space back. Other than
> >> that, I leave them alone and haven't had problems. - Rod
> >>
> >>     
> >
> >
> >   
> >> Research continues and I have more question for the group: 
> my Oracle 
> >> buddies rebuild their indexes at least weekly. Seems to be a best 
> >> practice. Seems odd to not be able to trust that your 
> index is correct.
> >> Is 
> >> this a concern for ud 7.1? 
> >>
> >> TIA,
> >> Brad.
> >>
> >> ud 7.1
> >> AIX 5.3
> >> U.S. BANCORP made the following annotations
> >>     
> >
> > U.S. BANCORP made the following annotations
> > 
> ---------------------------------------------------------------------
> > Electronic Privacy Notice. This e-mail, and any 
> attachments, contains information that is, or may be, covered 
> by electronic communications privacy laws, and is also 
> confidential and proprietary in nature. If you are not the 
> intended recipient, please be advised that you are legally 
> prohibited from retaining, using, copying, distributing, or 
> otherwise disclosing this information in any manner. Instead, 
> please reply to the sender that you have received this 
> communication in error, and then immediately delete it. Thank 
> you in advance for your cooperation.
> >
> >
> >
> > 
> ---------------------------------------------------------------------
> >
> > _______________________________________________
> > U2-Users mailing list
> > U2-Users@listserver.u2ug.org
> > http://listserver.u2ug.org/mailman/listinfo/u2-users
> >   
> _______________________________________________
> U2-Users mailing list
> U2-Users@listserver.u2ug.org
> http://listserver.u2ug.org/mailman/listinfo/u2-users



_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users

Reply via email to