that the index was keyed by
the ORDER NUMBER...
But I haven't
- Original Message -
From: Charles Stevenson
Date: Wednesday, March 4, 2009 4:45 pm
Subject: Re: [U2] Universe Index not working
To: u2-users@listserver.u2ug.org
In a prior release 10.0 or earlier, I encountered a problem
Brian
Initially testing confirms that a R versus L is the problem.
thanks.
Roger
Original Message -
From: Brian Leach
Date: Thursday, March 5, 2009 5:41 am
Subject: Re: [U2] Universe Index not working
To: u2-users@listserver.u2ug.org
Hi
Over the past months we've seen a number
For starters I'd try INVOICE = FIELD(@ID,'.',3,2)
ro...@optonline.net wrote:
AIX 5.3 Universe 10.2.4 300+ user license
Moved from older aix/universe 9.5 to current one in September 2008.
No index problems.
File contains 1.5 million records. key = company number * customer
Try LIST FILE REQUIRE.INDEX WITH INVOICE EQ 1000123.2
The REQUIRE.INDEX sometimes throws an error message when there's a
problem that wouldn't otherwise be shown... although my experience is
with unidata, not universe.
Also your dict item has a couple of typos I think, it's a retype rather
than
Shouldn't dictionary #2
Be FIELD(FIELD(@ID,'*',2),'.',3,2)
Instead of
FIELD(FIELD(@ID,'*',3),'.',2.2)
This will return
1123.2
Don't know why some selects worked.
Regards,
Kishor Parmar
-Original Message-
From: owner-u2-us...@listserver.u2ug.org
In a prior release 10.0 or earlier, I encountered a problem that could
corrupt an index if a write was issued without an explicit readu preceding
it. I don't think IBM ever corrected that because writing without
explicitly locking is Bad Form.
If I remember, when process A holds a lock on a
haven't
- Original Message -
From: Charles Stevenson
Date: Wednesday, March 4, 2009 4:45 pm
Subject: Re: [U2] Universe Index not working
To: u2-users@listserver.u2ug.org
In a prior release 10.0 or earlier, I encountered a problem that could
corrupt an index if a write was issued without
