× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



The syntax is correct...when I use *SYS vs *SQL syntax...i get a different error that states:

Cause . . . . . : An error occurred during a text search administrative
procedure. The reason code is 314. The text returned is: TOKEN
'THELIB/TESTFILE(wbxxml)' IS UNEXPECTED. CHECK THE COMMAND SYNTAX..

When running:

CALL SYSPROC/SYSTS_CREATE ('TEXTINDEXES', 'TXTINDEX',
'THELIB/TESTFILE(wbxxml)', 'FORMAT INSO')

Good guess though. So we are still at the original question concerning the "missing schema".

I am unfamiliar with OmniFind too. When I attended the RPG&DB2 Summit in Ft. Worth last March, Kent Mulligan from IBM had a session on the product. It looked like a solution to some of our longer running text searches, so I thought I'd look into it. After all...it is a freebie from IBM. So I've been trying to get the whole thing to work...without a great deal of luck. :-)


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bob P. Roche
Sent: Friday, September 10, 2010 3:43 PM
To: Midrange Systems Technical Discussion
Subject: RE: OmniFind product question

I'm not familiar with OmniFind so this may be completely off base, but is
the syntax your using correct? LIB.FILE. I'm used to LIB/FILE. If you are
using IFS style syntax isn't it LIB.lib.FILE.fil.MEMEBER.mbr or something
similar. where you have to say what each part is with a DOS type
extension?



From:
"Needles,Stephen J" <SNEEDLES@xxxxxxxxxxxxx>
To:
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date:
09/10/2010 03:32 PM
Subject:
RE: OmniFind product question
Sent by:
<midrange-l-bounces@xxxxxxxxxxxx>



It is explicitly named...so it shouldn't need to be in the library list.

But just in case...i tested this idea...same result.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Morgan, Paul
Sent: Friday, September 10, 2010 3:07 PM
To: Midrange Systems Technical Discussion
Subject: RE: OmniFind product question

Steve,

Is the Schema in the library list?

Paul

Principal Programmer Analyst
IS Supply Chain/Replenishment


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Needles,Stephen J
Sent: Friday, September 10, 2010 3:42 PM
To: Midrange Systems Technical Discussion
Subject: RE: OmniFind product question

"THELIB" was created using the CRTLIB command and the documentation
indicates that a "schema" can be defined this way.

Now my question is; which reference to "THELIB" is wrong? The indication
of where the new index is to live? Or the notation describing the file on
which to build the index?

I did a test.

I created a new schema named TEXTINDEXES and retried the create command:

CALL SYSPROC/SYSTS_CREATE ('TEXTINDEXES', 'TXTINDEX',
'THELIB.TESTFILE(wbxxml)', 'FORMAT INSO')

It failed; same error as before simply replacing the TEXTINDEXES for
THELIB. So I tried the OS name... TEXTI00001...

CALL SYSPROC/SYSTS_CREATE ('TEXTI00001', 'TXTINDEX',
'THELIB.TESTFILE(wbxxml)', 'FORMAT INSO')

And received the same error...it seems not to matter if CRTLIB or CREATE
SCHEMA is used to define the "library/schema".

But we did establish that the error is encountered when looking for the
schema in which to create the new index.

steve


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Morgan, Paul
Sent: Friday, September 10, 2010 1:27 PM
To: Midrange Systems Technical Discussion
Subject: RE: OmniFind product question

Steve,

Is THELIB actually a Schema or just a Library? A Schema is more than a
Library. Was THELIB created with a CREATE SCHEMA SQL statement?

Paul

Principal Programmer Analyst
IS Supply Chain/Replenishment

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Needles,Stephen J
Sent: Friday, September 10, 2010 1:49 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: OmniFind product question

I apologize if this is not the correct place to post a question such as
this...but I found nothing else that I considered an alternative.

I am trying to evaluate the OmniFind product from IBM and I am
encountering a problem when creating an index.

The product has a generic SQ20427 error message that seems to be a
catchall for whenever "An error occurred during a text search
administrative procedure" occurs. The rest of the message supposedly
spells out the "real" problem...which is...

The reason code is 339. The text returned is: THE SCHEMA 'THELIB' IS NOT
EXISTDB2 ERROR: 462 Procedure or user-defined function
OBJECT_STATISTICS in QSYS2 returned a warning SQLSTATE.õà+. FILE
/QSYS.LIB/QTEMP.LIB/TEMPFILE.FILE/DSXDBCAT.MBR:1720..

However, THELIB does exist on this machine.

This is what I am running:

CALL SYSPROC/SYSTS_CREATE ('THELIB', 'txtindex',
'THELIB.testfile(wbxxml)', 'FORMAT INSO')

Anyone got any insights? I found nothing useful via Google.

Thanks!

steve


==============================================================================
This communication, including attachments, is confidential, may be subject
to legal privileges, and is intended for the sole use of the addressee.
Any use, duplication, disclosure or dissemination of this communication,
other than by the addressee, is prohibited. If you have received this
communication in error, please notify the sender immediately and delete or
destroy this communication and all copies.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.