RE: [U2] UD: Indexes

2008-06-12 Thread Bill Haskett
As a follow up, here's an index that was corrupted earlier:

2 Dev (0)- LIST-INDEX ARTMASTER
Alternate Key Index Details for File ARTMASTER  Page   1

File..  ARTMASTER
Alternate key length..  45
Node/Block size...  4K
OV blocks.  1 (0 in use, 0 overflowed)
Indices...  3 (0 D-type)
Index updates.  Enabled, No updates pending

Index-Name..  F-type K-type Built Empties Dups In-DICT S/M F-no/VF-expr
INDEX_1   V  TxtYes   Yes Yes  Yes M   SUBR( '-CATS', S
   UBR( T.LFM, NI
   D, @FILE.NAME, @
   RECORD ), REUSE(
OCONV( *OCONV(
   @ID, 'G1*1' )*,
   'MR%7' ) ) )
INDEX_2   V  TxtYes   Yes Yes  Yes M   SUBR( '-CATS', S
   UBR( T.CLLFM,
   NID, @FILE.NAME,
@RECORD, @ID ),
REUSE( OCONV( *
   OCONV( @ID, 'G1*
   1' )*, 'MR%7' )
   ) )
INDEX_3   V  TxtYes   Yes Yes  Yes M   OCONV( *OCONV( @
   ID, 'G*1' )*, 'M
   R%4' ) : EXTRACT
   ( PHADD, 1, 1, 0
)


Thanks,

Bill


-Original Message-
From: [EMAIL PROTECTED] [mailto:owner-u2-
[EMAIL PROTECTED] On Behalf Of Bill Haskett
Sent: Thursday, June 12, 2008 5:38 PM
To: u2-users@listserver.u2ug.org
Subject: [U2] UD: Indexes

Has anyone had trouble with UniData indexes?  We moved an application from
D3 to UD and it's been reported that indexes are needing to be rebuilt on 
a recurring basis.

We created a program that will delete the index then rebuild it for needed
dictionary items.  After this program is run everything works fine, until
the next time.

Any thoughts would be appreciated.  Thanks,

Bill Haskett
Advantos Systems, Inc.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] UD: Indexes

2008-06-12 Thread Colin Alfke
Bill;

We haven't had trouble since an early version of version 6 had an overly
optimized version of udtsort.

Are any of those subroutines returning data from a remote file? UniData
doesn't have a link to the remote file to know when it's updated so the index
won't be updated.

Are they supposed to be multivalued?

hth
Colin Alfke
Calgary Canada

 From: wphaskett

 As a follow up, here's an index that was corrupted earlier:

 2 Dev (0)- LIST-INDEX ARTMASTER
 Alternate Key Index Details for File ARTMASTER  Page   1

 File..  ARTMASTER
 Alternate key length..  45
 Node/Block size...  4K
 OV blocks.  1 (0 in use, 0 overflowed)
 Indices...  3 (0 D-type)
 Index updates.  Enabled, No updates pending

 Index-Name..  F-type K-type Built Empties Dups In-DICT S/M
F-no/VF-expr
 INDEX_1   V  TxtYes   Yes Yes  Yes M
 SUBR( '-CATS', SUBR( T.LFM, NID, @FILE.NAME, @RECORD ),
 REUSE(OCONV( *OCONV(@ID, 'G1*1' )*,'MR%7' ) ) )

 INDEX_2   V  TxtYes   Yes Yes  Yes M
 SUBR( '-CATS', SUBR( T.CLLFM,NID, @FILE.NAME,@RECORD, @ID ),
 REUSE(
OCONV( *OCONV( @ID, 'G1*1' )*, 'MR%7' )))
 INDEX_3   V  TxtYes   Yes Yes  Yes M
 OCONV( *OCONV( @ID, 'G*1' )*, 'MR%4' ) : EXTRACT( PHADD, 1, 1, 0)


 Thanks,

 Bill


 -Original Message-
 
 Has anyone had trouble with UniData indexes?  We moved an application from
 D3 to UD and it's been reported that indexes are needing to be rebuilt on
 a recurring basis.
 
 We created a program that will delete the index then rebuild it for needed
 dictionary items.  After this program is run everything works fine, until
 the next time.
 
 Any thoughts would be appreciated.  Thanks,
 
 Bill Haskett
 Advantos Systems, Inc.


_
Find hidden words, unscramble celebrity names, or try the ultimate crossword
puzzle with Live Search Games. Play now!
http://g.msn.ca/ca55/212
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] UD: Indexes

2008-06-12 Thread Bill Haskett
Kevin:

Building a name in last, first mi format.  A list looks like:

2 Dev (0)- LIST ARTMASTER INDEX_2
LIST ARTMASTER INDEX_2 21:44:57 Jun 12 2008 1
ARTMASTER... INDEX_2.

260*50/6 0260PETTY, MICHAEL J  DEENA M00050/6
400*48   0400NELSON, MATTHEW048
260*35/3 0260MILLER, BRUCE00035/3
135*4712 0135MARTIN, ROBERT K  MARY L0004712
.
.

The 1st 4 bytes are from the key.  The next data is the name (built by the 
subroutine
T.LFM from an address book) followed by the 2nd part of the key.  It doesn't 
matter
if the address book data (the secondary file) is changed because if it is then 
a flag
is set and the ARTMASTER file (the primary file) is reindexed upon the next 
login
by anyone.

Bill

-Original Message-
From: [EMAIL PROTECTED] [mailto:owner-u2-
[EMAIL PROTECTED] On Behalf Of Kevin King
Sent: Thursday, June 12, 2008 9:41 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] UD: Indexes

What exactly are these subroutines doing?

On Thu, Jun 12, 2008 at 6:51 PM, Bill Haskett [EMAIL PROTECTED]
wrote:

 As a follow up, here's an index that was corrupted earlier:

 2 Dev (0)- LIST-INDEX ARTMASTER
 Alternate Key Index Details for File ARTMASTER  Page   1

 File..  ARTMASTER
 Alternate key length..  45
 Node/Block size...  4K
 OV blocks.  1 (0 in use, 0 overflowed)
 Indices...  3 (0 D-type)
 Index updates.  Enabled, No updates pending

 Index-Name..  F-type K-type Built Empties Dups In-DICT S/M
 F-no/VF-expr
 INDEX_1   V  TxtYes   Yes Yes  Yes M   SUBR(
 '-CATS', S
   UBR( T.LFM,
 NI
   D, @
 FILE.NAME, @
   RECORD ),
 REUSE(
OCONV(
 *OCONV(
   @ID, 'G1*1'
 )*,
   'MR%7' ) ) )
 INDEX_2   V  TxtYes   Yes Yes  Yes M   SUBR(
 '-CATS', S
   UBR(
 T.CLLFM,
   NID, @
 FILE.NAME,
@RECORD, @ID
 ),
REUSE(
 OCONV( *
   OCONV( @ID,
 'G1*
   1' )*, 'MR%7'
 )
   ) )
 INDEX_3   V  TxtYes   Yes Yes  Yes M   OCONV(
 *OCONV( @
   ID, 'G*1' )*,
 'M
   R%4' ) :
 EXTRACT
   ( PHADD, 1,
 1, 0
)


 Thanks,

 Bill


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:owner-u2-
 [EMAIL PROTECTED] On Behalf Of Bill Haskett
 Sent: Thursday, June 12, 2008 5:38 PM
 To: u2-users@listserver.u2ug.org
 Subject: [U2] UD: Indexes
 
 Has anyone had trouble with UniData indexes?  We moved an application from
 D3 to UD and it's been reported that indexes are needing to be rebuilt on
 a recurring basis.
 
 We created a program that will delete the index then rebuild it for needed
 dictionary items.  After this program is run everything works fine, until
 the next time.
 
 Any thoughts would be appreciated.  Thanks,
 
 Bill Haskett
 Advantos Systems, Inc.
 ---
 u2-users mailing list
 u2-users@listserver.u2ug.org
 To unsubscribe please visit http://listserver.u2ug.org/




--
-Kevin
http://www.PrecisOnline.com
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: {Blocked Content} RE: [U2] UD indexes and UniQuery - redux

2007-08-31 Thread Bill Haskett
Colin:

None of our indexes work with UniQuery.  Most of our indexes, like yours, were
designed on D3 and, thus, are multi-key, so to speak.  The interesting point is 
none
of our four new installations of UD (and our converted software and data) works 
with
UniQuery against indexes.

The indexes work correctly in BASIC so I know the index is built properly (I've
deleted and rebuilt the index, made sure the X_GLPOST file was gone (it was),
several times).

I'm thinking it could be with the UDT.OPTIONS.  I've contacted IBM on this and 
after
some false starts I finally got to someone who tested this out.  They couldn't
reproduce the errors so they called me.  After further review I indicated I
suspected, since all of our installations were having this problem, 
UDT.OPTIONS.  I
gave IBM the UDT.OPTIONS I set and when they set them they were able to 
reproduce the
same problem.  I've discovered the issue surfaces when setting UDT.OPTIONS 69 
ON and
SORT.TYPE to a non-zero value.  If I set UDT.OPTIONS 69 OFF, then I can keep
SORT.TYPE to a non-zero value (I use 2).

So, it seems UniQuery really doesn't use the indexes when UDT.OPTIONS 69 ON and
SORT.TYPE is non-zero.  We should figure out some kind of resolution.

Thanks,

Bill

-Original Message-
From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of 
[EMAIL PROTECTED]
Sent: Thursday, August 30, 2007 8:51 PM
To: u2-users@listserver.u2ug.org
Subject: {Blocked Content} RE: [U2] UD indexes and UniQuery - redux

Bill;

We use them all the time. They make a huge difference (especially on the
older, slower systems).

I don't know about the exact alternate key thing. I use the below format and
it works things come back quickly. It's the other way that doesn't work
(SELECT NAMES WITH INDEX_1 = [JOHN).

It does take longer if there is a large data set to return.

I just tried it on both UD 6.0.12 and 7.1.5PE.

Problems I've seen with an index:
1. early 5 version had a bad udtsort.exe and the index was not built properly
2. file being actively updated when the index was built
3. index was created but not actually built.
4. bad characters in the data (not so much a problem with the index)

Deleting the index (making sure the x_ file is gone in the OS) and recreate
and rebuild has always solved the problems. Note that we don't usually do
text searches like this. We generally use the index for client numbers,
timekeepers, fiscal period, invoice etc. Our application started on Pick
before they had indexes so we have our own cross-reference file for text
searches. We also don't have *really* large files. 99% are under the 2GB
threshold and only a handful of clients have anything larger. I think the
largest is around 4-5GB and I use the index on it all the time - really fast.

Sorry this wasn't much help.
Colin Alfke
Calgary Canada



From: Bill Haskett

I've been having problems getting UniQuery to use defined (and built) indexes
in UniData.  IBM has informed me that UniQuery does not use indexes unless the
exact alternate key is used.  e.g.

:SELECT NAMES WITH INDEX_1 = JOHNS]
 or
:select NAMES WITH INDEX_1 LIKE JOHNS...

...does not use the index.  IBM says using:

:SELECT NAMES WITH INDEX_1 = JOHNSON, RON

...will work.  However, this doesn't work on my system (UD v7.1.9).  All of my
index testing works fine in UniVerse, i.e. Retrieve selections use the defined
indexes and returns all selects immediately.

Does UniQuery use indexes in UniData?

Thanks,

Bill
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


{Blocked Content} RE: [U2] UD indexes and UniQuery - redux

2007-08-30 Thread colin.alfke
Warning: This message has had one or more attachments removed
Warning: (not named).
Warning: Please read the AngelicHost-Attachment-Warning.txt attachment(s)
for more information.

Bill;

We use them all the time. They make a huge difference (especially on the
older, slower systems).

I don't know about the exact alternate key thing. I use the below format and
it works things come back quickly. It's the other way that doesn't work
(SELECT NAMES WITH INDEX_1 = [JOHN).

It does take longer if there is a large data set to return.

I just tried it on both UD 6.0.12 and 7.1.5PE.

Problems I've seen with an index:
1. early 5 version had a bad udtsort.exe and the index was not built properly
2. file being actively updated when the index was built
3. index was created but not actually built.
4. bad characters in the data (not so much a problem with the index)

Deleting the index (making sure the x_ file is gone in the OS) and recreate
and rebuild has always solved the problems. Note that we don't usually do
text searches like this. We generally use the index for client numbers,
timekeepers, fiscal period, invoice etc. Our application started on Pick
before they had indexes so we have our own cross-reference file for text
searches. We also don't have *really* large files. 99% are under the 2GB
threshold and only a handful of clients have anything larger. I think the
largest is around 4-5GB and I use the index on it all the time - really fast.

Sorry this wasn't much help.
Colin Alfke
Calgary Canada



From: Bill Haskett

I've been having problems getting UniQuery to use defined (and built) indexes
in
UniData.  IBM has informed me that UniQuery does not use indexes unless the
exact
alternate key is used.  e.g.

:SELECT NAMES WITH INDEX_1 = JOHNS]
 or
:select NAMES WITH INDEX_1 LIKE JOHNS...

...does not use the index.  IBM says using:

:SELECT NAMES WITH INDEX_1 = JOHNSON, RON

...will work.  However, this doesn't work on my system (UD v7.1.9).  All of my
index
testing works fine in UniVerse, i.e. Retrieve selections use the defined
indexes and
returns all selects immediately.

Does UniQuery use indexes in UniData?

Thanks,

Bill
This is a message from the MailScanner E-Mail Virus Protection Service
--
The original e-mail attachment winmail.dat
was believed to be infected by a virus and has been replaced by this warning
message.

If you wish to receive a copy of the *infected* attachment, please
e-mail helpdesk and include the whole of this message
in your request. Alternatively, you can call them, with
the contents of this message to hand when you call.

At Thu Aug 30 20:35:02 2007 the virus scanner said:
   Could not parse Outlook Rich Text attachment

Note to Help Desk: Look on the AngelicHost MailScanner in
/home/virtual/site2/fst/var/spool/mail.quarantine/20070830 (message
l7V3Z0Ks003173).
--
Postmaster
MailScanner thanks transtec Computers for their support
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] UD Indexes

2006-04-12 Thread Simon Lewington
Bill Haskett ...
 I'm running UD v7.1 and got an error message from within a BASIC program
 like:

  In E:\DataTrust\DTA\BP\BP\_TRREC at line 1161 - is not an indexed/legal
 field.

 ..caused by the BASIC statement:

  SETINDEX NAME.KEY, A.CODE ON ARTDESC
...
 Am I correct in assuming that UniData won't accept a - in the indexed
 field?

Nope

 What's up with this?

You've accidentally set NAME.KEY = - instead of INDEX_1.

Simon
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] UD Indexes

2006-04-12 Thread Bill Haskett
Simon:

Thanks very much.  I'll pursue this immediately.  :-)

Bill
 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of 
 Simon Lewington
 Sent: Wednesday, April 12, 2006 1:35 AM
 To: u2-users@listserver.u2ug.org
 Subject: Re: [U2] UD Indexes
 
 Bill Haskett ...
  I'm running UD v7.1 and got an error message from within a 
  BASIC program like:
 
   In E:\DataTrust\DTA\BP\BP\_TRREC at line 1161 - is not 
   an indexed/legal field.
 
  ...caused by the BASIC statement:
 
   SETINDEX NAME.KEY, A.CODE ON ARTDESC
  ...Am I correct in assuming that UniData won't accept 
  a - in the indexed field?
 
 Nope
 
  What's up with this?
 
 You've accidentally set NAME.KEY = - instead of INDEX_1.
 
 Simon
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/